The orderHistory array is returned in the response of the following endpoints:It provides a timeline of all key events in the lifecycle of the transaction — including internal logic, gateway responses, and user interactions. This can help merchants analyze failed payments, fine-tune routing/cascading logic, and profile user behavior. Interpretation of the code structure#
Each action in the orderHistory has the format X.Y.Z.W, where:X — Source of the event (e.g., internal, gateway, user, etc.)
Y — Status code after the event:0 — Intermediate / non-final state
Z.W — Additional categorization of the action:::
The orderHistory array may be updated with a short delay after the final transaction status (Success or Failed) is received.Recommendation:
To ensure you receive the full and complete event history, we advise calling the status endpoint at least 10 minutes after the final status has been confirmed.This delay allows for all asynchronous callbacks, retries, and gateway logs to be properly recorded.
Example JSON#
{
"externalId": "ad66a2ff-97d1-47c5-8552-53752a51f031",
"orderStatus": "Success",
"amount": 2600.00,
"externalParams": {
"cardToken": null,
"cardStorageToken": null,
"cardHolder": null,
"cardNumber": null
},
"orderHistory": [
{
"time": "2025-07-28T09:29:51.339832",
"action": "1.1.0.0"
},
{
"time": "2025-07-28T09:29:51.339832",
"action": "4.1.0.0"
}
]
}
Action Codes Reference#
1. Internal Creation (1.Y.Z.W)#
| Code | Description |
|---|
| 1.1.0.0 | Payment created |
| 1.2.1.1 | Payment failed: Configuration – Limit issue |
| 1.2.1.2 | Payment failed: Configuration – Routing error |
| 1.2.1.3 | Payment failed: Configuration – Routing error |
| 1.2.1.4 | Payment failed: Configuration – No balance |
2. Gateway Creation (2.Y.Z.W)#
| Code | Description |
|---|
| 2.1.0.0 | Payment created on gateway |
| 2.2.1.1 | Payment failed: Tech – Failed connection |
| 2.2.1.2 | Payment failed: Tech – Server unavailable |
| 2.2.1.3 | Payment failed: Tech – Invalid response |
| 2.2.1.4 | Payment failed: Tech – Invalid request |
| 2.2.2.1 | Payment failed: Auth – Unauthorized (401) |
| 2.2.2.2 | Payment failed: Auth – Forbidden (403) |
| 2.2.3.1 | Payment failed: Configuration – No balance |
| 2.2.3.2 | Payment failed: Configuration – Limit issue |
| 2.2.3.3 | Payment failed: Configuration – GEO/currency/MCC |
3. User Activity (3.Y.Z.W)#
| Code | Description |
|---|
| 3.0.0.1 | External payform shown |
| 3.0.1.1 | Internal payform shown |
| 3.0.1.2 | User visited page |
| 3.0.1.3 | User left page |
| 3.0.1.4 | User entered personal data |
| 3.0.1.5 | User cancelled manually |
| 3.0.1.6 | User clicked "Pay" |
| 3.0.1.7 | 3DS verification failed |
| 3.0.1.8 | OTP verification failed |
| 3.0.1.9 | User left during verification |
| 3.0.1.10 | User left during verification |
4. Gateway Status (4.Y.Z.W)#
| Code | Description |
|---|
| 4.0.1.1 | Processing: Server unavailable |
| 4.0.1.2 | Processing: Invalid request |
| 4.0.2.1 | Processing: Unauthorized (401) |
| 4.0.2.2 | Processing: Forbidden (403) |
| 4.1.0.0 | Payment successful |
| 4.2.0.0 | Payment failed |
| 4.2.1.1 | Issuer: Declined without reason |
| 4.2.1.2 | Issuer: Card blocked |
| 4.2.1.3 | Issuer: Card not supported |
| 4.2.1.4 | Issuer: Card no balance |
| 4.2.2.2 | Acquirer: Declined by antifraud |
5. Gateway Callback (5.Y.Z.W)#
| Code | Description |
|---|
| 5.X.1.0 | Callback: Status update — Success |
| 5.X.2.0 | Callback: Amount update — Success |
| 5.0.1.0 | Callback: Invalid signature |
| 5.0.2.0 | Callback: Invalid payload |
7. Merchant Callback (7.Y.Z.W)#
| Code | Description |
|---|
| 7.X.0.0 | Merchant callback confirmed |
