Skip to main content

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. Atum handles 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. Atum routes it to a settlement provider that delivers on the recipient’s rail, then returns a settlement receipt.

Shared responsibility

Atum handles delivery — you stay in control of payout decisions and timing.

Try it

Try it (CLI)

Send a payment from your terminal in minutes

Integrate (SDK)

Add payments to your backend service

Next steps