### Transaction states

Transactions accepted by the API can be in one of the following states.
As soon as the order is accepted, you will get unique id in the response, which can base
used to track the transaction.

Please note that orders rejected up-front by the API with 4xx (authentication or
validation errors) are not represented in the state table, since they've never been accepted
for processing.

| Status Category | Status | Description | Notes |
|  --- | --- | --- | --- |
| **In Progress** | `queued` | Payment order accepted | Order is accepted and waiting to be submitted for processing |
| **In Progress** | `pending` | Payment order pending | DEPRECATED (see `processing`) |
| **In Progress** | `processing` | Payment order is processing | Payment submitted and accepted by processor |
| **Success** | `succeeded` | Payment executed successfully |  |
| **Failed** | `failed` | Payment failed | Payment failed by the processor |
| **Failed** | `rejected` | Payment rejected | Payment rejected by processor or by API during processing (e.g API could not route) |
| **Failed** | `canceled` | Payment is canceled | DEPRECATED (see `reversed`) |
| **Failed** | `reversed` | Payment is reversed | Payment reversed (and refunded) on the processor side |
| **Call Support** | `unknown` | Payment state is unknown | Payment has encountered uknown status by the processor, needs manual intervantion |