Create Order
Orders
Create Order
Initiate an order for a product such as a premium account upgrade or metal card. Returns a unique order reference to pass to your payment gateway.
POST
Create Order
Overview
Use this endpoint to start a new order for a product — for example, a premium account upgrade or a metal card. The response includes anorderId and, where applicable, a paymentConfig object containing everything needed to route the user through an external crypto payment flow.
Once you have an orderId, pass it to your payment gateway. After payment is submitted, poll GET /v1/order/:orderId to confirm the final outcome.
Request
Headers
Bearer token for the authenticated user. Format:
Bearer <userAccessToken>Your application’s client ID, issued during onboarding.
Must be
application/json.Body
The unique identifier of the product to order. Valid values are partner-specific and returned by
GET /v1/order/products/available. Example: "PRODUCT_ID_ABC"The payment method to use for this order. Supported values:
CRYPTO_EXTERNAL_DAIMO
Example Request
Response
200 — Success
The order has been created. StoreorderId to track the order status. Use paymentConfig to initiate payment via your gateway.
An identifier for the payment request, used to correlate payment gateway callbacks back to this order. Example:
"payment_1234"Unique identifier for this order. Store this — you’ll need it to poll for the order outcome via
GET /v1/order/:orderId.Payment routing details for the external crypto payment. Pass these values to your payment gateway to initiate the transaction.
Error Responses
401 — Authentication Error
401 — Authentication Error
The bearer token is missing, expired, or invalid. Ensure a valid user access token is included in the
Authorization header.403 — Authorization Error
403 — Authorization Error
422 — Validation Error
422 — Validation Error
One or more required fields failed validation. Check that
productId and paymentMethod are both present and that paymentMethod is a supported enum value (CRYPTO_EXTERNAL_DAIMO).498 — Invalid Client Key
498 — Invalid Client Key
The
X-Client-ID header value is not recognised. Verify your client ID.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 error occurred on the server. Retry with exponential backoff. If the issue persists, contact Baanx support.
Related Endpoints
Get Available Products
Retrieve the products available and eligible for the current user before placing an order.
Get Order Status
Poll for the async completion of a payment and confirm the order outcome.