Statuses
Payment statuses, leg states and kinds, and how provider errors are classified.
Payment status
pending → received → splitting → settled, with partial when a leg fails, and refund_partial → refunded for a refund.
| Status | Meaning | Next |
|---|---|---|
pending | Funding session created, nothing received | received or splitting on inflows.completed |
received | Inflow confirmed, legs computed | splitting |
splitting | The executor has run at least once | settled, or partial if a leg is rejected |
settled | Every split leg completed | refund_partial on refund |
partial | A leg failed or was rejected | splitting after a retry |
refund_partial | Refund started, reversals outstanding | refunded |
refunded | Refund finished and every reversal completed | final |
Status changes are guarded (compare-and-set), so concurrent webhooks cannot move a payment backwards or run a step twice.
Leg state
| State | Meaning |
|---|---|
pending | Not sent, or sent with an unknown outcome (the same reference is reused on retry) |
sent | Nuvion accepted the transfer; waiting for outflows.completed |
completed | Nuvion confirmed it |
failed | Definitively rejected; a retry uses a new reference |
cancelled | Cancelled by a refund before it was sent |
Leg kind
split: a parent's share, from the merchant's account to the parent's.reversal: created by a refund, from a beneficiary back to the paying organization.
Provider error kinds
Each Nuvion failure is classified so the executor knows whether it is safe to retry.
| Kind | When | Effect on the leg |
|---|---|---|
rejected | Nuvion refused it definitively (4xx, for example insufficient funds or validation) | failed; retry with a new reference |
ambiguous | Timeout, network error, 429, or 5xx; unknown whether it was created | stays pending; retry with the same reference |
duplicate | 409: the reference already exists | treated as sent; wait for its webhook |