Overview
Your buyer has USDC on one rail. You settle in USDT on another. Traditionally, that mismatch means either the buyer can’t pay or you take on conversion and multi-rail overhead. With Atum, your buyer sends what they have and you receive what you want.Commerce platforms
Accept tokenized currency without dictating which rail or token the buyer uses.
Payment service providers
Add multi-rail tokenized currency acceptance to checkout products.
B2B platforms
Accept invoiced payments from counterparties on different rails.
Problem space
Atum solves:- Rail lock-in — buyers on other rails can’t pay
- Token mismatch between buyer and merchant
- Multiple rail integrations, accounts, and maintenance
How it works
Your checkout or invoice flow initiates a payment request through the Atum Payment Gateway. A settlement operator, selected by price quote, deposits the buyer’s funds in the settlement vault on their rail and pays your preferred token to your account. See Atum payment lifecycle.Who does what
You choose the token and rail you receive on, start the payment request, and show the buyer the result. 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
- Agentic payouts — autonomous agents that trigger payments programmatically
- SDK quickstart — integrate Atum into your checkout or platform