Skip to main content
GET
Get Order Status

Overview

After creating an order with POST /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

string
required
Bearer token for the authenticated user. Format: Bearer <userAccessToken>
string
required
Your application’s client ID, issued during onboarding.

Path Parameters

string
required
The unique ID of a previously created order, as returned by POST /v1/order. Example: "abcd_1234"

Example Request

Response

200 — Success

string
The payment request identifier, correlating this order to a payment gateway transaction. Example: "payment_1234"
string
required
The unique identifier of the order.
enum
required
The current state of the order.
string
Timestamp of when payment was confirmed. Only present when status is COMPLETED.
object
Additional context about the payment outcome. Individual fields may be absent depending on the result.

Error Responses

The bearer token is missing, expired, or invalid.
The authenticated user does not have permission to access this order.
No order exists with the given orderId. Verify the ID matches one returned by POST /v1/order.
The X-Client-ID header value is not recognised.
The X-Client-ID header is absent from the request.
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 when status reaches a terminal value (COMPLETED, FAILED, or EXPIRED).

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.