Get Order Status
Orders
Get Order Status
Fetch the current status of an order by ID. Use this to poll for async completion after a payment is submitted.
GET
Get Order Status
Overview
After creating an order withPOST /v1/order and directing the user through an external payment flow, use this endpoint to poll for the outcome. The order status will progress from STARTED to one of the terminal states: COMPLETED, FAILED, or EXPIRED.
Request
Headers
Bearer token for the authenticated user. Format:
Bearer <userAccessToken>Your application’s client ID, issued during onboarding.
Path Parameters
The unique ID of a previously created order, as returned by
POST /v1/order. Example: "abcd_1234"Example Request
Response
200 — Success
The payment request identifier, correlating this order to a payment gateway transaction. Example:
"payment_1234"The unique identifier of the order.
The current state of the order.
| Value | Description |
|---|---|
STARTED | Order created; payment not yet confirmed. Continue polling. |
COMPLETED | Payment received and order fulfilled successfully. |
FAILED | Payment failed or was rejected. Check metadata.note for context. |
EXPIRED | Order was not paid within the allowed time window. |
Timestamp of when payment was confirmed. Only present when
status is COMPLETED.Additional context about the payment outcome. Individual fields may be absent depending on the result.
Error Responses
401 — Authentication Error
401 — Authentication Error
The bearer token is missing, expired, or invalid.
403 — Authorization Error
403 — Authorization Error
404 — Order Not Found
404 — Order Not Found
No order exists with the given
orderId. Verify the ID matches one returned by POST /v1/order.498 — Invalid Client Key
498 — Invalid Client Key
The
X-Client-ID header value is not recognised.499 — Missing Client Key
499 — Missing Client Key
The
X-Client-ID header is absent from the request.500 — Internal Server Error
500 — Internal Server Error
An unexpected server error occurred. Retry with exponential backoff.
Polling Pattern
Order completion is asynchronous. Poll this endpoint after the user completes the external payment step, stopping whenstatus reaches a terminal value (COMPLETED, FAILED, or EXPIRED).
Related Endpoints
Create Order
Initiate a new order and receive the
orderId to track here.Get Available Products
Discover which products are available and eligible before ordering.