Mass disbursements
Send one payout or thousands in a batch from a single API call pattern.
Payouts
Global Payout Infrastructure
No scheme membership. One API. Launched under your brand.
Pay anyone, anywhere, programmatically. One API to move funds to sellers, suppliers, affiliates, creators and employees across 150+ countries — with the tracking finance teams need.
Your program
- Mass disbursementsSend one payout or thousands in a batch from a single API call pattern.
- Multiple railsSEPA for euro recipients, SWIFT for global reach — chosen per corridor.
- Payout to cardsCombine with prepaid or debit issuing to deliver funds onto branded cards instantly.
- FX handledFund in your currencies, deliver in theirs, with conversion inside the flow.
Launch checklist
- Fund the float
- Submit payouts
- Rails do the work
- Track to completion
- PCI DSS Level 1 systems
- Visa & Mastercard programs
- 150+ countries
- 35+ currencies
The problem
Launching payments usually means building a bank first.
The product is rarely the hard part. The dependencies are: scheme membership, a sponsor bank, a certified PCI environment and a stack of vendors, each with its own queue.
Scheme membership is a project in itself.
Going to Visa or Mastercard directly means capital requirements, audits and a sponsor bank before a single card ships.
Compliance becomes a second product.
PCI DSS, KYC, AML monitoring and disputes each need their own people, vendors and audit cycles.
Every vendor is another integration.
Processor, ledger, KYC and payout providers each bring their own API, contract and failure modes.
Run it yourself
One program, two ways to launch it.
Launch payouts under your brand Ready
Building it with a bankIdle: press Launch the program
- Apply for card scheme membership
- Negotiate a sponsor bank and BIN
- Build and certify a PCI DSS environment
- Integrate processor, KYC and ledger vendors
- Wait for scheme certification
Every dependency sits in another team's queue, and you still own the audits.
Launching it on NetPayIdle: press Launch the program
- Fund the float
- Submit payouts
- Rails do the work
- Track to completion
Same program. One partner, one API and one contract.
Capabilities
Payouts as a product capability
Everything here runs on the same NetPay rails, API and dashboard.
Multiple rails
SEPA for euro recipients, SWIFT for global reach — chosen per corridor.
Payout to cards
Combine with prepaid or debit issuing to deliver funds onto branded cards instantly.
FX handled
Fund in your currencies, deliver in theirs, with conversion inside the flow.
Status webhooks
Created, processing, completed, returned — every state pushed to your systems.
Clean reconciliation
Payout references and events map one-to-one to your ledger entries.
How it works
How programmatic payouts run
A guided path. We carry the regulated heavy lifting so your team ships the product.
Fund the float
Hold balances in the currencies you pay out from.
Submit payouts
Send recipient, amount and currency via API — singly or in batches.
Rails do the work
Each payout routes over the right rail with conversion as needed.
Track to completion
Webhooks confirm delivery or surface returns for handling.
Who it's for
Built for teams that move money.
- Marketplaces & gig platforms
- Affiliate networks
- Forex brokers
- Creator platforms
- Payroll providers
- Insurance & claims
How we compare
How NetPay compares.
Every option gets you to a live program eventually. The rows show what each one asks of your team.
| Capability | NetPay | Build in-house | Legacy processor |
|---|---|---|---|
| Card scheme membership | Not needed, we sponsor | Required | Usually required |
| PCI DSS scope | On our Level 1 systems | Yours to certify | Shared with you |
| Cards, IBANs and payouts | One platform | Separate vendors | Cards only |
| Integration | One REST API and webhooks | Several vendor APIs | Batch files, legacy APIs |
| Sandbox before launch | Full sandbox | Build your own | Limited |
| Your brand | Every card, app and statement | Yes | Often co-branded |
How do mass payouts work?
You submit a batch of recipients and amounts through the API; the platform executes each payout on the appropriate rail and streams per-payout status events back, so partial failures are visible and retryable individually.
Can I pay out onto cards instead of bank accounts?
Yes. Paired with card issuing, funds can land on branded prepaid or debit cards instantly — popular for gig workers and affiliates who want immediate access.
How are failed payouts handled?
Returns and failures come back as webhook events with reason data, so your system can correct details and resubmit without spreadsheet forensics.
Launch payouts under your brand.
Tell us what you're building and we'll scope the right program and rails with you.