One batch, every recipient paid.
Submit one payout instruction — hundreds or thousands of recipients, any mix of currencies — and Infinite screens each recipient, picks the rail per payment, and closes the run with one reconciled report.
Draft — pending review
Payouts on Infinite (infinite.net) are batch disbursements from an Infinite Account: one API instruction pays many recipients across SWIFT, US rails, stablecoins, and FX. Every recipient is screened before the run starts, each payment takes the rail Transfer Routes selects, and the run reconciles to one ledger and one report.
- Marketplaces and platforms paying sellers, creators, or partners on a schedule
- Finance teams running supplier, contractor, or refund runs from one balance
- Businesses replacing a payout provider per country with one instruction
Built for the run, not the single payment.
Payouts, Links, Invoicing, and Checkout are capabilities of the same Infinite Account — one compliance review, one integration, one ledger.
One instruction, many recipients
A single request carries the whole run — recipients, amounts, currencies. No per-payment loop in your code and no per-country provider to call.
Screened before anything moves
Every recipient is screened before the run starts. Recipients already vetted on the network clear instantly; new ones are reviewed once, for everyone.
A rail per payment
Transfer Routes reads each payment’s destination, amount, and urgency and picks SWIFT, ACH, Fedwire, RTP, stablecoins, or an FX leg — inside one run.
Funded from one balance
The run draws on your Infinite Account — one balance behind every currency and rail, no separate float per corridor.
Per-recipient status, one report
Webhooks confirm each payout as it settles, returns reconcile against the original payment, and the whole run closes as one report on one ledger.
Month-end, end to end.
A software company pays 340 contractors in 22 countries on the last business day. One instruction — Infinite (infinite.net) does the rest.
Recipients onboarded once
Contractors are verified through Embedded Compliance when they join. A recipient already cleared on the network needs no second review.
Submit one batch
One request: 340 recipients, six currencies, no rail specified.
Each payout finds its rail
US contractors route to ACH or RTP by cutoff; EUR and GBP convert in flight; the rest settle over stablecoins or SWIFT by destination.
Exceptions surface inline
A recipient that trips screening is held for a named analyst with the case assembled — it never settles silently.
Reconcile once
Webhooks confirm each payout as it lands; the run reconciles as one ledger entry set, returns included.
Integrate once.
One request for the whole run. Leave the rail off and Transfer Routes chooses per payment; the reconciliation shape stays the same either way.
import { Infinite } from "@infinite/sdk"; const infinite = new Infinite({ apiKey }); const run = await infinite.payouts.create({ source: "acct_ops_usd", items: [ { destination: "acct_br_2201", amount: "1850.00", currency: "BRL" }, { destination: "acct_us_9313", amount: "4200.00", currency: "USD" }, // …338 more ], }); // one webhook per payout, one report per run
Answers before you ask
How is Payouts different from Global Mass Payouts?
This page is the product: how a run is submitted, screened, routed, and reconciled. Global Mass Payouts is the use case — what changes for a marketplace or platform paying thousands of sellers, with an interactive run to step through. The flow-of-funds walkthrough is at first-party payouts.
Can one run mix currencies and rails?
Yes. Each payout in a run carries its own destination and currency; Transfer Routes picks the rail per payment, and FX converts in flight where the destination currency differs from the funding balance.
What happens if one recipient is flagged?
The flagged payout holds for a named analyst — the case arrives assembled through Compliance AI — and nothing settles to that recipient until a human decides. Every step is logged in the case file.
How do we track each payout?
Webhooks fire on every transition — released, settled, returned — per payout, and the run reports as a whole. Returns reconcile against the original payment instead of appearing as a mystery credit in a bank file. The event model is in the documentation.
Do recipients need onboarding first?
Recipients are verified before they are paid — through Embedded Compliance in your brand, or through the network’s existing record if they have already been cleared elsewhere on it. Cleared once is cleared for every business on the network.
- PayoutsSend batch disbursements with one instruction
- LinksGet paid by link, reconciled on arrival
- InvoicingInvoice and settle in one flow
- SWIFT PaymentsSend global wires through one integration
- USD PaymentsMove dollars on every domestic rail
- Stablecoin PaymentsSettle in stablecoins on bank rails
- Foreign ExchangeConvert between currencies at settlement
- Transfer RoutesRoute money on the fastest compliant path
One instruction. Every recipient paid.
Talk to an engineer — bring a real payout file and we’ll walk the run end to end.