> ## Documentation Index
> Fetch the complete documentation index at: https://docs.liquidramp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transaction Statuses

> Partner-visible order status values — in-flight vs terminal.

Order responses expose a single `status` field.

| Status                  | Meaning                                              |
| ----------------------- | ---------------------------------------------------- |
| `initiated`             | Order created, routing not started                   |
| `pending`               | Awaiting user action                                 |
| `processing`            | Active execution                                     |
| `awaiting_user_payment` | Pay-in instructions issued, waiting for the customer |
| `awaiting_lp_payment`   | Provider-side payment pending                        |
| `routing`               | Provider assignment in progress                      |
| `executing`             | Fulfilment in progress                               |
| `partially_completed`   | One leg complete, other pending                      |
| `settled`               | Funds settled                                        |
| `completed`             | Terminal success                                     |
| `cancelled`             | Terminal — cancelled                                 |
| `expired`               | Terminal — pay-in window elapsed                     |
| `failed`                | Terminal — unrecoverable failure                     |
| `refunded`              | Terminal — funds refunded                            |
| `reverted`              | Terminal — transaction reverted                      |

## Terminal vs in-flight

**Terminal:** `completed`, `cancelled`, `expired`, `failed`, `refunded`, `reverted`.

**In-flight:** everything else — poll or wait for webhooks.

On some offramp and swap flows, `status` may show `completed` once the customer-facing leg is done. For on-chain proof, use `?include=payout` and the `order.settled` webhook.

Pass `?include=timeline` on `GET /v1/orders/:reference` for event history.

| Status                               | Action                                      |
| ------------------------------------ | ------------------------------------------- |
| `pending`, `awaiting_user_payment`   | Show pay-in UI from `payin`                 |
| `processing`, `routing`, `executing` | Poll or wait for webhooks                   |
| `completed`, `settled`               | Show success; verify payout proof if needed |
| `cancelled`, `expired`, `failed`     | Show failure; check `refund` if applicable  |

## Related

* [Order lifecycle](/concepts/order-lifecycle)
* [Callbacks](/concepts/callbacks)
* [Orders](/concepts/orders)