Beta
Track payment and order status
Reconcile wallet evidence with the backend-owned order state before deciding that an order is funded, shipped, refundable, or complete.
Before you start
- Keep the order identifier or Guest Order token and the payment transaction ID.
- Use the same store and backend that created the order.
- Never paste private keys, recovery phrases, authenticated tracking URLs, or full customer details into support chat.
Tracking steps
- Open Orders for an authenticated purchase or the saved Guest Order tracking link.
- Confirm seller, item, amount, payment asset, and creation time before interpreting state.
- Compare the displayed payment destination and transaction ID with your wallet record.
- Read confirmations and required confirmations from the order page.
- Refresh through the product UI or authoritative API when an event announces a change.
- Preserve fulfillment, cancellation, refund, or dispute evidence before taking the next available action.
Expected result and verification
The order page should show a monotonic business-state view owned by the backend. A WebSocket event or wallet notification is only a refresh signal. For important decisions, verify the current order through the authenticated HTTP API or tracking endpoint.
| Observation | Safe conclusion |
|---|---|
| Transaction broadcast | A wallet attempted to publish a transaction |
| Transaction detected | The payment system observed a candidate transaction |
| Required confirmations reached | The configured confirmation gate may be satisfied |
| Backend state is funded | The order backend accepted the payment evidence for this order |
| Seller marked shipped | Fulfillment evidence was recorded; inspect it |
If something fails
- No transaction detected: verify asset, network, destination, amount, and expiry without sending a second payment.
- Confirmations stalled: inspect the payment network independently and preserve the transaction ID.
- Wallet confirmed but order awaiting payment: report exact order and transaction identifiers privately to the operator.
- State conflicts across screens: stop automated actions and report a consistency defect.
- Tracking link does not open: confirm it belongs to this deployment and was not truncated.
Recovery and escalation
Do not attempt database edits or direct settlement calls to repair a buyer order. Use actions offered by the order state, then get help with sanitized evidence.