Status Codes
The numeric status codes returned for a payment and their meanings
Every payment carries a numeric statusCode. The same value appears in the Proceed and Check responses, and as remoteStatusCode in webhooks. Always use the numeric code for programmatic logic — the human-readable text may change.
All status codes#
| Code | Status | Meaning |
|---|---|---|
1 | Processing | The payment is registered and being processed, but not yet paid. |
2 | Succeeded | The amount was captured successfully. Terminal success state. |
3 | Rejected | The payment was rejected or the card was declined. Terminal failure state. |
4 | Refunded | A refund was processed — full or partial. The same code is used for both; compare the refunded amounts to tell them apart. |
6 | Authorization declined | The authorization was declined by the provider. |
9 | Initialized | The payment intent has been created and is awaiting a payment method. This is the initial state. |
10 | Reversed / Canceled | A pre-authorization was reversed and the reserved funds released. |
11 | Insufficient amount | The payment failed because of insufficient funds. |
12 | Requires authentication | User action is required — redirect the buyer to the payUrl to enter card details or complete a 3D Secure / OTP challenge. |
13 | Pre-authorized | Funds were reserved but not captured. Awaiting capture or release. |
14 | Auto-refunded | An automatic refund was processed. |
Codes you will see for card payments
For Visa / Mastercard card payments, the common codes are
12 (requires card entry or 3D Secure), 2 (succeeded), 3 (declined), and 4 / 14 (refunded). Pre-authorization codes (13, 10) apply to the reservation flow.Grouping by outcome#
If you want to bucket payments into high-level states (for dashboards or reporting), these are the groupings Yassir uses internally:
| Group | Status codes |
|---|---|
| Success | 2 |
| Processing | 1, 12 |
| Failed | 3, 6, 11 |
| Refunded | 4, 14 |
| Canceled | 10 |
| Initialized | 9 |