Order status

The status field of an Order reports where the transaction stands in its lifecycle. It is a free-form string passed through from the underlying payment processor, not a closed enum — the platform does not restrict it to a fixed list of values.

Observed values

These are the values seen in practice today:

Status	Meaning
ACCEPTED	The order was accepted and registered; execution has not started yet.
PENDING	The order is being processed; the payout has not been confirmed yet.
CONFIRMED	The payout was confirmed on the destination side.
COMPLETED	The order finished successfully end to end.
FAILED	The order could not be completed. See Failure details for failure_code and failure_reason.
COMPENSATING	The payout failed and the funds are being returned.
COMPENSATION_PENDING	The return of funds is queued.
COMPENSATED	The funds were returned.
REJECTED	The order was rejected before execution.
IN_PROGRESS	Execution is under way.
PROVIDER_FAILED	The payment network failed the operation.
LEG_1_SENT	The first leg of the transfer was sent; the payout is still in flight.

The set may evolve

Because status is a pass-through string, new values can appear as the underlying processing pipeline evolves. Treat unknown values gracefully — for example, fall back to a neutral "in progress" state in your UI — instead of hardcoding this list as exhaustive.

Each transition is also recorded in the order's events array (from_status, to_status, trigger, created_at), which you can use to render a timeline instead of relying on the current status alone.