Pay thousands from one integration
Pay sellers and contractors across countries from one batch request.
A 240-recipient run, end to end. Click through it.
- 01UploadOne batch file: 240 sellers, 14 currencies. Recipients were onboarded and vetted once; the batch just references them.
- 02ScreenEvery recipient screens before anything moves. Name matches go to human review; duplicate accounts stay held for confirmation.
- 03Fan outOne click. Infinite picks the rail per corridor: local rails and stablecoin legs, no per-country providers.
- 04ReconcileOne report records eligible payments and the recipients still held for review.
Screened, accounted for, reported.
With InfiniteFor a handful of large suppliers, see Crossborder Payments.
- Add a country without a new provider
- Every corridor, one API. Transfer Routes picks the rail per destination, with FX in flight.
- Clear sellers before their first payout
- Screened before the run. Embedded Compliance onboards sellers in your brand, once for the network.
- Give each seller somewhere to hold funds
- An account per recipient. Each seller gets a USD account with its own routing number at a bank partner.
- Close a run without stitching exports
- One report per run. Per-recipient status and retries in one ledger.
How the money moves.
Funds flow- One USD balanceFunds the batch
- One batch requestOne API instruction
- Recipients screened before the runCleared once, payable across the networkCleared
- Best route per payoutStablecoin, local rails, or FX in flight
- An account per recipientA USD account with its own routing number
- One report per runPer-recipient status and retries
- Collect
- One USD balanceFunds the batch
- Hold and convert
- One batch requestOne API instruction
- Recipients screened before the runCleared once, payable across the networkCleared
- Pay out
- Best route per payoutStablecoin, local rails, or FX in flight
- An account per recipientA USD account with its own routing number
- One report per runPer-recipient status and retries
Each rail and corridor here, with its status, is in the coverage matrix.
Onboard once, reconcile once.
Example workflow- 01
Onboard recipients once.
Cleared once, payable across the network.
- 02
Submit one batch.
One API instruction, funded from one USD balance. See the documentation.
- 03
Infinite fans it out.
Each payout takes the best route, with FX in flight.
- 04
Reconcile once.
Retry the exceptions and close with one audit-ready report.
Where a run lands, and how fast it clears.
Payout reachYou submit one batch, and Transfer Routes picks the rail per payout.
| Destination | Delivered on | Local settlement |
|---|---|---|
| Mexico · MXN | Delivered onSPEI | Local settlementInstant, 24/7 |
| Brazil · BRL | Delivered onPix | Local settlementInstant, 24/7 |
| UK · GBP | Delivered onFaster Payments · CHAPS | Local settlementNear-instant, 24/7 · CHAPS for high-value |
| Eurozone · EUR | Delivered onSEPA Instant · SEPA credit transfer | Local settlementSeconds · SEPA credit transfer: same/next day |
| Any wallet address | Delivered onStablecoins | Local settlement24/7, including weekends |
| Major SWIFT corridors | Delivered onSWIFT | Local settlementCorrespondent timelines, status reported end to end |
Businesses onboard from the supported markets; a run reaches recipients beyond them. Currency converts en route, quoted on the payment object. Recipient types and geographies are confirmed per corridor when a programme is scoped.
Answers before you ask
FAQHow do we pay thousands of sellers in different countries at once?
One batch instruction via API, funded from a single USD balance. Recipients are screened before the run, each corridor picks its rail and FX, and the batch closes with one reconciled report. See the guide to stablecoin payments for marketplaces and platforms.
What is the best way to send bulk payouts to sellers in other countries?
Look for verification at scale, an account per recipient where needed, per-corridor routing, and exceptions that do not stall the run. Infinite runs all four: every recipient is screened before funds move, payouts fan out across local rails and stablecoins, and a single flag holds one payment while the rest of the run continues.
What do bulk payout platforms charge?
Most charge per payout, a platform fee, or both; across borders, FX spread and correspondent lifting fees often drive the real cost. Compare providers on an all-in quote per recipient for your corridors. See our pricing, stablecoins vs SWIFT, and choosing a payout provider.
How fast does a bulk payout settle?
Per rail, not per run. SPEI, Pix, Faster Payments, and SEPA Instant clear in seconds; a stablecoin leg settles in minutes at any hour. SWIFT follows correspondent timelines. Transfer Routes picks the rail per corridor so the run does not wait on the slowest leg.
If one recipient is flagged, does the whole run stop?
No. Screening happens before funds move; one flag holds that single payout for a named analyst while the rest of the run continues on schedule. See why payouts scale on vetting.
Make the next run boring.
Bring a payout file and an engineer will walk it with you.
Ask an AI about Global Mass PaymentsChatGPTClaudePerplexityGemini