Payout Lifecycle
Payouts follow this state progression:
draft: Payout without a fixed exchange rate or fees- Transitions to:
preparedwhen manually switched by the merchant - Takes longer to transition to
expiredthanpreparedpayouts. Payouts can be recovered fromexpiredstate back todraft.
- Transitions to:
prepared: Newly created payout awaiting merchant confirmation- Transitions to:
confirmed(merchant accepts exchange rate) orexpired(confirmation timeout) - Payout can also be moved to
canceledby merchant
- Transitions to:
confirmed: Payout with exchange rate accepted by merchant- Transitions to:
sending(scheduled for processing) orcanceled
- Transitions to:
sending: Payout queued for processing in the next batch- Transitions to:
done(successful processing)
- Transitions to:
done: Payout successfully processed with transaction ID assigned- Final state, represents successful completion
pending_verification: Merchant accepted the exchange rate but more information from the customer is required to satisfy the Travel Rule documentation- If the requested information is provided the funds are sent to your customer and the payout moves to state
confirmed - If the information is not provided in time the payout moves to state
expired - Payout can also be moved to
canceledby merchant
- If the requested information is provided the funds are sent to your customer and the payout moves to state
expired: Payout that wasn't confirmed within the required timeframe- Can be recovered and transitioned back to
draft
- Can be recovered and transitioned back to
canceled: Payout canceled by merchant- Final state
Data purging
Similar to invoices, payouts which transition directly from prepared to expired status are subject to data purging after some retention period (e.g. a year).
Updated 7 days ago
What’s Next
