Instant payouts

Instant payouts, on every global rail — through one API.

topropay's orchestration layer pushes funds across the major instant rails worldwide — SEPA Instant, FPS, FedNow, RTP, PIX, UPI, OSKO — behind a single unified API. Same vault and same ledger as pay-ins, so payouts close the loop instead of opening a new one.

Book a payouts review Explore the platform
days same-day instant SEPA FPS PIX FedNow UPI* OSKO
Push funds in seconds, on the right rail per destination.
<30s
typical end-to-end on most instant rails
24×7
rails that run outside banking hours
1
API across every connected payout rail

Key benefits

What changes when global payouts become instant by default

Four outcomes that show up immediately once the orchestration layer is in place on the payout side, not just the pay-in side.

  1. Speed

    Funds arrive in seconds, not days

    Most connected rails confirm in under a minute end-to-end. Sellers, drivers, creators, suppliers and refunded customers see the money the same minute the merchant releases it — not the next banking day.

  2. Coverage

    A single API across global payout rails

    SEPA Instant in the EU, FPS in the UK, FedNow / RTP in the US, PIX in Brazil, UPI in India (via licensed partner gateways), OSKO in Australia. One integration; the routing engine picks the right rail per destination automatically.

  3. Cost

    Per-payout cost, not per-batch cost

    Where the underlying rail supports it, instant payouts are priced per transaction with transparent unit economics. The orchestration layer absorbs the per-rail fee structure into one normalised cost model in the operator dashboard.

  4. Operations

    Payouts and pay-ins in the same ledger

    Every payout sits next to the corresponding pay-in keyed off the same vault token. Reconciliation closes the loop in one ledger entry per cycle, not a separate export per rail or per direction of money.

Connected rails

Instant payout rails by region

The shape of "instant" varies per region — different schemes, different operating windows, different per-payment limits. A compact view of what the platform routes payouts across.

Region Rail Speed Notes
European Union SEPA Instant Credit Transfer (SCT Inst) <10s end-to-end 24×7; €100k payment cap; widely available across SEPA banks.
United Kingdom Faster Payments (FPS) <30s typical 24×7; £1m per-payment limit at most banks; the UK's default instant rail.
United States FedNow / RTP <20s typical 24×7; FedNow expanding coverage; RTP at $1m per-payment limit.
Brazil PIX <10s typical 24×7; near-universal coverage at Brazilian banks; QR + key (CPF / email / phone) addressing.
India* UPI / IMPS <30s typical 24×7; UPI via licensed partner gateways; IMPS available where UPI isn't applicable.
Australia OSKO / NPP <30s typical 24×7; PayID addressing; widely supported by AU banks.
Singapore FAST / PayNow <60s typical Near-instant during operating windows; address by PayNow ID.
Mexico SPEI <60s typical 24×7; near-universal at Mexican banks.

* India UPI / IMPS payout connectivity is delivered through licensed partner gateways rather than a direct topropay RBI licence.

How it works

From a single API call to confirmed funds on the rail

Five stages between the merchant calling the payouts API and the recipient receiving the funds. The slowest step is usually the recipient's bank, not the rail.

  1. 01

    Initiate

    Merchant calls the unified payout API with the destination identifier (IBAN, account / sort code, PIX key, PayID, UPI ID, etc.) and amount.

  2. 02

    Route

    The routing engine picks the right instant rail for the destination country, currency and identifier shape — no per-rail integration required on the merchant side.

  3. 03

    Settle

    The connected provider pushes the funds onto the rail; confirmation comes back in seconds on most rails, with an inline webhook to the merchant.

  4. 04

    Reconcile

    The payout posts to the unified ledger keyed off the vault token associated with the customer or recipient. One ledger, both directions.

  5. 05

    Notify

    Optional inline buyer / recipient notifications fire from the platform — email, SMS or in-app — so the receiving party knows the funds have landed.

Main use cases

Where instant payouts and a global payout platform earn their keep

Six merchant shapes that consistently surface in conversations once instant payout rails are in front of them — from marketplaces to insurance disbursements.

  • Marketplaces and platforms — instant seller payouts

    Sellers on marketplaces benefit disproportionately from instant access to their balance. The orchestration layer pushes payouts on the right rail per seller's country with one integration; reconciliation rolls up per-seller and per-platform automatically.

  • Gig economy and creator economy

    Drivers, couriers and creators expect intra-day or end-of-shift payouts. Per-payout cost-aware routing keeps the unit economics tight; instant rails replace what used to be a daily ACH batch.

  • Refunds at instant speed

    Refunding to a card takes days; refunding to a bank rail at instant speed takes seconds. The platform exposes 'refund to instant rail' as a method when the destination identifier supports it — substantially compressing customer-service refund cycles.

  • Insurance disbursements

    Claim payouts pushed onto an instant rail land before the claimant has hung up the phone. Useful where the merchant has its own claims-decision flow and just needs the disbursement to settle as fast as the decision.

  • B2B supplier payouts

    Supplier invoices paid the moment they're approved sit on the same orchestration as customer pay-ins. Cash-cycle compression for the supplier; a cleaner reconciliation for the merchant's finance team.

  • Global payouts for affiliates and partners

    Cross-border affiliate or partner payouts running on the right local rail per region — local currency, local addressing, local speed. The merchant manages one payout API; the platform handles per-region rail selection.

Model comparison

Traditional batched payouts vs orchestrated instant payouts

Same money, two different operational shapes. The instant shape is more than just faster — it changes when reconciliation closes, how the merchant manages cash and what the recipient sees.

Dimension Traditional batched payouts topropay instant payouts
Speed T+1 or T+2 batches via ACH / SEPA / Bacs Sub-minute on most connected instant rails, 24×7
Integration One integration per rail per country One unified API across every connected global payout rail
Addressing IBAN / account+sort code only IBAN, sort/account, PIX key, PayID, UPI ID, PayNow ID — abstracted into one schema
Cost model Batch fees + per-payout fees vary by rail Per-payout pricing surfaced in a normalised cost model in the dashboard
Reconciliation Payouts ledger lives in a separate file from pay-ins Payouts and pay-ins in the same ledger keyed off vault tokens
Outside-hours Batches paused outside banking hours Connected instant rails run 24×7; merchant traffic doesn't queue overnight

Platform features

Capabilities behind the global payment platform on the payout side

What the platform actually ships for instant payouts — beyond the general orchestration features shared with the pay-in side.

  • Unified payouts API

    One REST contract across every connected payout rail; SDKs for web, mobile and server.

  • Addressing abstraction

    Bank rails, PIX keys, PayID, UPI IDs, PayNow IDs all funnel through one destination schema with the right validation per rail.

  • Routing engine for payouts

    Destination country + currency + identifier shape decide the right rail per payout — no per-rail integration on the merchant side.

  • Retry & fallback

    Where instant fails, a configurable fallback to a same-day rail (or a deferred batch) keeps the payout going through rather than bouncing back.

  • Inline webhooks

    Signed, normalised events for accepted / settled / failed / refunded payouts; per-event-type subscriptions.

  • Two-direction ledger

    Pay-ins and pay-outs sit on the same normalised ledger keyed off vault tokens; reconciliation closes loops, not just files.

  • Limits & velocity controls

    Per-recipient, per-day and per-payout caps; velocity rules to keep operational risk inside the merchant's own policy.

  • Sanctions & screening

    Recipient screening on every payout; flagged payouts hold for operator review inside the dashboard before they release to the rail.

  • Operator portal

    One dashboard for payouts, refunds and reconciliation across every connected rail.

  • Sandbox parity

    A sandbox per environment that behaves like production — including rail-specific timing and fallback scenarios.

Trust & compliance

Compliance posture across pay-ins and payouts

Payouts touch the same audited environment as pay-ins. Merchants inherit the platform's posture rather than carrying separate certifications per rail.

PCI DSS Level 1
Inherited service-provider posture — payouts touch the same audited environment as pay-ins.
AML / KYB
Merchant KYB on onboarding; sanctions screening on every payout recipient.
Rail-side compliance
Each connected rail runs under the underlying provider's relevant licensing; topropay aggregates the lot under its sub-merchant relationships.
Data residency
Regional data-residency options for merchants under regulators that require it; signed event logs available for audit.
Resilient by design
Redundant rail connections per region; automatic failover keeps payouts flowing during single-provider outages.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported where current operating licences exist. Grey and black-market verticals are out of scope.

Ready to push faster

Run a payout-side review against your destination mix.

A 30-minute payouts review walks through the instant rails relevant for your recipient base, the addressing schema, the fallback policy and a sandbox to test against before any commercial commitment.

Book a payouts review Read the API docs

Frequently asked

Buyer questions about instant payouts and the global payment platform

What buyers ask before committing — covering definitions, the relationship to the pay-in side, rail-by-rail coverage and where this fits inside the wider global payment solutions catalogue.

  1. 01

    What does the platform mean by instant payouts?

    Instant payouts means pushing funds to a recipient over a rail that confirms in seconds rather than days. topropay aggregates the major instant rails worldwide — SEPA Instant in the EU, FPS in the UK, FedNow / RTP in the US, PIX in Brazil, UPI in India (via licensed partners), OSKO in Australia — and exposes them through one unified payouts API.

  2. 02

    How does instant payouts shape topropay as a global payment platform?

    A global payment platform that only covers pay-ins is half the picture. Instant payouts complete the loop: merchants accept on one side and disburse on the other, both through the same unified API, both reconciled into the same ledger. That makes topropay a global payment platform end-to-end rather than only on the merchant-receive side.

  3. 03

    Where do instant payouts fit inside the wider global payment solutions catalogue?

    Global payment solutions on the platform cover acceptance (cards, wallets, bank rails, BNPL, crypto), orchestration (smart routing, cascade), reconciliation (one ledger) and now payouts (instant rails). Instant payouts is the disbursement leg of that catalogue.

  4. 04

    Which global payment processors are involved on the payout side?

    Global payment processors on the payout side are mostly bank-rail-adjacent partner providers that already hold the right scheme membership for SEPA Instant, FPS, FedNow, PIX and similar. topropay's role is the orchestration layer that selects between them per payout — the merchant doesn't pick a processor, the routing engine does.

  5. 05

    Is this a global payment gateway in the payout direction?

    Functionally yes — a global payment gateway in the payout direction is an API that abstracts many bank-rail integrations into one call. topropay's payout API does exactly that, plus the routing logic to pick which rail to use per destination.

  6. 06

    How is this different from a traditional payment gateway global product?

    A traditional payment gateway global product almost always means card acceptance. Instant payouts is the opposite direction — pushing funds to bank-rail destinations. The two pair naturally: a merchant who already runs card acceptance on topropay now extends to push-to-bank disbursements with the same integration shape.

  7. 07

    Is topropay a global payment provider, end-to-end?

    topropay is a global payment provider in the orchestration sense — sitting in front of multiple licensed acquirers, PSPs and (for payouts) bank-rail providers, exposing one unified API to merchants. It is not a direct acquirer in every market, and it doesn't replace the underlying provider relationships; it abstracts them.

  8. 08

    How does the platform compare to other global payment gateway providers on instant payouts?

    Other global payment gateway providers typically focus on one direction (acceptance) or one rail family (cards, or one bank-rail provider). topropay's distinguishing posture is treating instant payouts as a peer to card acceptance — same API, same vault, same ledger, same operator portal.

  9. 09

    Can the platform handle global payouts at marketplace scale?

    Yes — global payouts at marketplace scale is one of the primary patterns the platform was designed for. Per-seller routing to the correct local rail, per-seller addressing schema validation, and per-seller analytics roll up into one platform-side reconciliation feed.

  10. 10

    Is there a dedicated global payout platform product, or is it part of the wider platform?

    It's part of the wider platform — there is no separate global payout platform SKU to buy. Payouts surface through the same API, dashboard, vault and webhooks as the rest of topropay. That keeps the operational shape consistent with the merchant's existing pay-in flow.

  11. 11

    How does the platform behave when an instant rail rejects a payout?

    When an instant rail rejects a payout (invalid recipient identifier, sanctions hit, per-rail limit), the platform exposes a configurable fallback policy: retry, downgrade to a same-day rail, or hold for operator review. Hard rejects (sanctions hits) never fall back automatically.

  12. 12

    What does global payout solution mean in topropay's terms?

    Global payout solution in topropay's terms is the combination of the unified payouts API, the addressing abstraction across rail formats, the routing engine that picks the rail per destination, and the unified ledger that reconciles payouts next to pay-ins. The four together are what makes it a 'solution' rather than just a rail aggregator.

  13. 13

    Does the platform act as one of the global payment processing companies for the back-office?

    topropay sits a layer above the global payment processing companies — it integrates with them and orchestrates traffic across them. For a merchant the operational shape is identical to working with one global processor (one API, one dashboard, one ledger), but the underlying capacity comes from a portfolio of providers.

  14. 14

    What about global payment processing and reconciliation at the same time as instant payouts?

    Global payment processing on the pay-in side and instant payouts on the pay-out side share the same vault, the same operator portal and the same reconciliation feed. A refund issued as an instant payout, for example, is one transaction lifecycle in the ledger — not two systems to merge.

  15. 15

    Is topropay a payment gateway platform or a payouts platform?

    Both. As a payment gateway platform it accepts pay-ins across cards, wallets, bank rails, BNPL and crypto; as a payouts platform it pushes funds onto instant bank rails worldwide. The same merchant contract covers both — they're two faces of the same orchestration layer.

Related

Related on the topropay platform