Overview
Your platform decides who gets paid, how much, and when. Getting money to recipients across different payment rails — especially internationally — traditionally means FX intermediaries, correspondent banks, and recipients who may not have access to traditional banking at all. Settlement operators on the Atum network handle the delivery, so you can focus on the payout logic.Marketplaces and platforms
Paying out gig workers, creators, or sellers after a job, sale, or approval event.
Payroll processors
Disbursing to employees or contractors across different payment rails.
Remittance providers
Sending funds to recipients where traditional rails are slow, expensive, or inaccessible.
Government and aid organizations
Disbursing funds to recipients who may not hold accounts on a single rail.
Problem space
Atum solves:- SWIFT delays and correspondent bank fees on international transfers
- No delivery path for unbanked or underbanked recipients
- Rail mismatch between sender and recipient tokens or chains
How it works
When a payment event fires — job complete, invoice approved, batch ready — your payout service submits a payment request to Atum. A settlement operator, selected by price quote, delivers on the recipient’s rail, and Atum verifies the delivery. See Atum payment lifecycle.Who does what
You decide when to pay, how much and to whom, and you store the result and handle retries. Settlement operators move the funds, and Atum verifies the delivery. The full split: Who owns what.Try it
Quickstart (using CLI)
Send a payment from your terminal in minutes
SDK quickstart
Add payments to your backend service
Next steps
- Merchant acceptance — accept any tokenized currency from buyers
- Agentic payouts — let an AI agent make the payment decision autonomously