Payment status
Query payment state over POST
Use this endpoint to read the current state of a payment after you create a payment. It complements webhooks: webhooks push updates; status is for checks and reconciliation.
All merchant calls use POST, Content-Type: application/json, x-api-key, and x-api-secret.
Endpoint
Request
Headers
Body
Example
Response
Successful responses return transaction status information for the provided reference.
Example
All values in this response snippet are mock values.
Payment states
Interpret status in your integration. Common values:
Confirm enum values and extra fields (failure reasons, operator references) against your live API or OpenAPI definition.
Errors
Example (validation)
Operations
- Prefer webhooks for timely updates; use status to backfill missed events or to verify before shipping or crediting wallets.
- When polling, use bounded retries and exponential backoff; avoid tight loops against production.
- Make fulfillment idempotent (key orders or references) so duplicate status reads or duplicate webhooks never double-apply side effects.
