# Transaction statuses


Payment or payout API responses, callbacks, and status requests include two related fields:

- `status` — numeric code;
- `status_description` — text literal (Latin, uppercase).

Values always come **as a pair**. **Do not translate** or replace machine codes in integration.

## `status` and `status_description` mapping

| `status` | `status_description` | Description |
| --- | --- | --- |
| `1` | `INIT` | Transaction initiated. |
| `2` | `PENDING` | Transaction in progress. |
| `3` | `SUCCESS` | Transaction completed successfully. |
| `4` | `FAILURE` | Transaction declined. |
| `5` | `REFUND` | Refund completed successfully. |
| `9` | `REFUND_PENDING` | Refund in progress. |

## How to use in integration

| Status | Action |
| --- | --- |
| `INIT`, `PENDING` | Wait for final status: poll the status method or handle callback on `notify_url`. |
| `SUCCESS` | Credit the order / close the operation on your side. |
| `FAILURE` | Do not treat payment as successful; if `status_code` is present in the callback, see [Error codes (declines)](./decline-error-codes.md). |
| `REFUND`, `REFUND_PENDING` | Account for the refund; wait for `REFUND` when status is `REFUND_PENDING`. |

Final statuses for payments: `SUCCESS`, `FAILURE`; for refunds: `REFUND` (intermediate — `REFUND_PENDING`).

## Related sections

- [Error codes (declines)](./decline-error-codes.md)
- [Error codes (API)](./error-codes-api.md)
- [API request format](./init-request.md)