Pay thousands from one integration

With one batch instruction: post the run (recipients, amounts, currencies) via API, funded from a single USD balance. Each payout takes the best rail for its corridor, with FX converted in flight where needed. The full pattern is covered in the guide to stablecoin payments for marketplaces and platforms.

Local rails carry the last mile where Infinite runs them: SPEI in Mexico, Pix in Brazil, Faster Payments in the UK, SEPA across the eurozone. Stablecoins reach any wallet address, and SWIFT carries USD wires to the major corridors beyond them, confirmed per corridor. Transfer Routes picks per payout. Paying into a market is not the same as onboarding from one, so the supported-markets list is a different, shorter list.

Per rail, not per run. SPEI and Pix credit instantly, around the clock. Faster Payments is near-instant, and SEPA Instant clears in seconds where SEPA credit transfer takes the same or next day. A stablecoin leg settles in minutes at any hour, including weekends. SWIFT follows correspondent timelines, with status reported end to end instead of a trace request.

Judge platforms on four capabilities: recipient verification at scale, an account per recipient, corridor-by-corridor routing with currency conversion in flight, and exception handling that doesn’t stall the run. Infinite runs all four on one network: one batch instruction, funded from a single USD balance, reconciled once, with every recipient screened before funds move.

Most charge per payout, a platform fee, or both, but on cross-border runs the real cost driver is the corridor: FX spread plus the lifting fees correspondent banks deduct in flight. Stablecoin rails remove that intermediary leg (transfer cost doesn’t scale with the amount sent), leaving in-flight FX as the main corridor cost. Infinite publishes its own pricing; the guide on stablecoins vs SWIFT maps the full cost anatomy, and choosing a mass payout provider sets out what to ask a vendor.

Sellers complete onboarding through Embedded Compliance (KYB, KYC, and sanctions screening under your brand) before the first payout. A recipient vetted once is vetted for the whole network, so the review never repeats.

Yes. Managed Accounts give each seller a real demand deposit account with its own routing number, held at chartered, FDIC-insured partner banks and sub-ledgered to your structure. You pay out on your schedule; Infinite handles the reconciliation for every recipient across the run.

No. One flagged recipient holds one payout; the rest of the run continues. Screening happens before funds move, so a hit stops a payment rather than reversing one, and the case goes to a named human analyst working from a documented file instead of a queue that clears after settlement. The decision and its reasons stay on the record behind that payout. Why review belongs per instruction rather than per batch is set out in mass payouts at network scale.

Failures are flagged in flight with reasons, not discovered at month-end: you watch settlement per recipient in real time, retry the exceptions, and close the run with one audit-ready report. Because Transfer Routes picks the rail per corridor, a failed leg can be re-routed rather than re-keyed by hand.

That depends on your flow of funds (who holds the money, in whose name, and under whose control), and it’s a question for counsel. Infinite’s third-party funds flow gives every seller an account of their own; see the money transmitter glossary entry for how the question is framed.