The five stages
Stage by stage
1
Submit a payment request
Your app builds the payment request (source account, destination account, amount) and signs it on your machine. On EVM, Tempo and Tron, the signature is a Permit2 authorization for up to
max_source_amount. Atum never sees your private key. See Prepare a payment.2
Atum accepts it
The Payment Gateway checks the request and the signature, and returns a
payment_id.3
Settlement operators send price quotes
During the quote window, independent settlement operators send price quotes for the route you asked for. When the window closes, the gateway selects one that has not expired. With auto accept, it selects the first valid quote as soon as it arrives. If none is usable, the payment fails; see Deadline errors. You never contact settlement operators directly.
4
The settlement operator delivers
The selected operator deposits your funds in the settlement vault on the source chain. Your balance drops here, before the recipient is paid. The operator then pays the recipient on the destination chain, before the delivery deadline.
What /status shows at each stage
What each status means: Payment status.
Who does what
You integrate only with the Payment Gateway. The roles in a payment are on Network participants, and who is responsible for what is on Who owns what.Next steps
- After submission — follow a payment to the end and retry safely
- Quickstart (using CLI) — send a real payment on testnet
- SDK quickstart — integrate payments into your app