One batch, every recipient paid.

One instruction pays many recipients, each screened and routed.

ONE ACCOUNT · A RAIL FOR EVERY RECIPIENTILLUSTRATIVE RUN

Who it’s for

  • Marketplaces paying sellers, creators, or partners
  • Finance teams paying suppliers and contractors
  • Businesses replacing a payout provider per country

One account. The right rail for each recipient.

Illustrative example
One instruction · every recipient screened · a rail per payoutILLUSTRATIVE

One run. A status for every recipient.

Developers

Workflow example, not executable API code. Integration details are scoped to your account and enabled products.

workflow.txtIllustrative example
1. Prepare the recipient list, currencies, and amounts.
2. Screen each recipient; hold flags for review.
3. Route eligible payouts for each destination.
4. Reconcile the run with each payout status.

Answers before you ask

FAQ

How is Payouts different from Global Mass Payments?

Payouts is the product. Global Mass Payments is the marketplace use case, with an interactive run, and first-party payouts shows the flow of funds.

Can one run mix currencies and rails?

Yes. Each payout has its own currency; Transfer Routes picks the rail and FX converts where needed.

What happens if one recipient is flagged?

That payout holds while the rest of the run settles. A judgment call routes to a named analyst, with the case assembled by Compliance AI.

How do we track each payout?

A webhook fires on every transition (released, settled, returned); returns reconcile to the original payment. See the documentation.

Do recipients need onboarding first?

They are verified before payment, through Embedded Compliance in your brand or the network’s existing record. Cleared once is cleared network-wide.

Walk a real run.

Bring a payout file; an engineer walks it end to end.

Ask an AI about PayoutsChatGPTClaudePerplexityGemini