Create order
POST/orders/create
Creates a separate purchase on every call and charges the current price. Choose exactly one module request variant. api_user_id identifies your customer; optional partner_order_id links the order to your system but does not deduplicate requests. There is no request_id or client price field. HTTP 200 with processing means accepted, not delivered. Read status even when success=false: review is an uncertain result, refunded means funds were returned. Use /orders/status or final webhooks for the outcome and codes. Never automatically repeat this request after a timeout or uncertain result; see Purchase flow.
Request
Responses
- 200
- 400
- 401
- 404
- 422
- 429
- 500
- 502
- 503
- 504
Operation result; inspect success and status/valid.
Request cannot be fulfilled (for example insufficient balance, invalid recipient or unavailable nominal).
Missing/invalid API key, wrong integration ID or inactive integration.
Product, nominal or order not found in the requested scope.
Request validation failed, including unknown fields or an invalid module variant.
Integration rate limit exceeded: 100 requests per 60 seconds across all public endpoints.
Unexpected server error.
Invalid upstream response or recipient verification response.
Service unavailable or creation result uncertain. If detail is an object with order_id, check /orders/status; do not repeat the purchase.
Catalog or recipient verification timed out.