Instant payouts on a global payout platform.
Instant payouts on BazPay send funds to a payee settlement account in seconds on SEPA Instant, push to a Visa or Mastercard card at scheme timing, and reach beneficiaries outside the SEPA Instant area over SWIFT on approved corridors. It is one balance, one REST API and one signed webhook stream — the same account you already use for acquiring.
Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services businesses. Underwriting scope is deliberately narrow. Coverage is defined per corridor, not promised as blanket global.
Why teams pick this global payout solution
Four things stay true whether you send twenty payouts a month or twenty thousand. They are the reasons product, engineering and finance teams stay after they migrate.
-
One balance funds every payout
Instant payouts draw on the same balance your card and open banking sales settle into. No pre-fund wallet to top up, no second reconciliation.
-
Coverage across four rails
Choose SEPA Instant for EUR beneficiaries, push-to-card where you hold a token, SWIFT for approved cross-border corridors, or batch for bulk runs.
-
Deterministic status model
Every payout emits accepted, sent, settled or returned as a signed webhook with the scheme reason code attached. No polling loops.
-
Finance-grade reporting
Interchange++ line detail on the acquiring side and per-payout scheme references on the money-out side keep month-end reconciliations short.
Five rails on one endpoint
Pick the rail that fits the payee. They share one endpoint and one status model, so your integration code does not fork per rail.
-
01Instant rail
SEPA Instant
Funds reach the payee settlement account in seconds, twenty-four hours a day, weekends included. The receiving bank must be a SEPA Instant participant. This is the instant payout rail for EUR beneficiaries.
- Seconds
- 24/7
- EUR
-
02Card push
Push to card
Send money straight to a Visa or Mastercard debit or reloadable card. Useful when you hold a token but no settlement account. Availability follows scheme OCT and issuer participation.
- Visa
- Mastercard
- Token
-
03SEPA Instant standard
Instant credit transfer
Same-day or next business cycle to any settlement account in the region. You pass the name, settlement account and reference; we build the scheme message and hand back the return codes.
- settlement account
- EUR
- Return codes
-
04Cross-border
SWIFT international
Pay beneficiaries outside the region over SWIFT on approved corridors. We build the message and return the correspondent-bank path. Settlement time follows the correspondents on the route — we quote the corridor rather than promise a date.
- SWIFT
- Non-EUR
- Approved corridors
-
05Bulk
Batch files
Upload one CSV and pay many people at once. Each row is treated as its own payout. Failures are reported per row, so a single bad settlement account never blocks the batch.
- CSV
- Per-row status
- Bulk
How an instant payout moves
Six stages from balance to settled. Each one leaves a record you can export and audit.
-
Fund from your balance
Card, wallet and APM sales settle into a single balance. Instant payouts draw on it directly — no separate account to top up.
-
Call one endpoint
POST an amount, a rail and the payee details. Idempotency keys make retries safe on network blips.
-
Screen and authorise
Sanctions and internal risk rules run before the message leaves. Approved payouts move to the rail; failures return a reason code.
-
Send on the rail
SEPA Instant leaves in seconds; Instant credit transfer at the next cycle; card push at scheme timing; SWIFT via the correspondent path.
-
Confirm by webhook
State changes fire as signed webhooks. You get accepted, sent, settled or returned, with the scheme reason attached.
-
Reconcile in the dashboard
Every payout shows next to the sales that funded it. Export any view as CSV for your ledger.
When teams reach for a payout
Most gateways treat money-out as an afterthought. Our payment gateway platform runs it on the same product line as acquiring — one balance, one reconciliation view and one support contact.
See the rest of the line on the products overview, or check corridor coverage for cross-border needs — Talk with sales.
-
Refunds beyond the card window
Some refunds land after the original card sale can be reversed. An instant payout closes the loop without a new card charge.
-
Marketplace and partner splits
Pay sellers, affiliates or agents out of settled funds. Each leg keeps its own reference for reconciliation.
-
Supplier and expense runs
Batch the weekly run into one file. Finance approves once, then every row settles on the same rail.
-
Subscription credits
Return a pro-rated amount when a plan changes mid-cycle. It pairs with the dunning logic in recurring billing.
-
Customer withdrawals
Ledger withdrawals from software products where the shopper cashes out an account balance to a bank account or card.
-
Contractor and payroll top-ups
Off-cycle top-ups to contractors on SEPA Instant when the standard cycle would be too slow.
Features engineered into the payout API
Every capability below is available on the standard integration — no enterprise gate on the primitives your engineering team will actually build against.
-
Idempotent API
Retry any create request with the same key and never send twice. Safe under partial-response conditions.
-
Signed webhooks
HMAC-SHA256 signature over the raw body, plus a timestamp header to prevent replay. Verify with the shared secret.
-
Sanctions screening
Every payee is screened before the message leaves. Hits pause the payout for review; clean payees pass through.
-
Per-row batch status
Batch outcomes come back per row, with the scheme reason attached to each failure. Rerun only the rows that need it.
-
Return-code handling
SEPA Instant return codes and scheme decline codes are exposed on the payout object. No opaque failure states.
-
Sandbox parity
Sandbox keys cover every rail. Replay accepted, returned and rejected outcomes before you send real money.
Rails, landing point and timing
Timing is set by the scheme and the receiving bank, not by us. This is what each rail does under normal operating conditions.
| Rail | Funds land | Timing | Note |
|---|---|---|---|
| SEPA Instant | Payee settlement account | Seconds, 24/7 | Both banks must join |
| Instant credit transfer | Payee settlement account | Next business cycle | Bank hours apply |
| Push to card | Card account | Scheme timing | Visa and Mastercard |
| SWIFT international | Payee account | Corridor-dependent | Correspondent path |
| Batch file | Mixed | Per row, per rail | Row-level results |
Platform coverage for plugins and shop systems is listed under plugins and shop integrations.
Unified gateway vs a separate payout tool
Bolt-on payout tools require a pre-funded wallet and a second reconciliation. A single global payment gateway platform funds payouts from the acquiring balance and reports them in the same view as sales.
| Dimension | BazPay (unified) | Standalone payout tool |
|---|---|---|
| Funding model | One balance — sales fund payouts directly | Pre-fund a separate wallet or bank account |
| Rail coverage | SEPA Instant, instant CT, card push, SWIFT, batch | One or two rails typical |
| Settlement view | Payouts sit next to the sales that funded them | Two systems, two reconciliations |
| Webhook contract | Signed, idempotent, per-row for batches | Varies; polling common |
| Reporting | Interchange++ in, per-scheme reasons out | Blended summary |
| Contract | Direct with BazPay as gateway and acquirer | Chained sub-processors |
See published rates on the pricing page. Pair payouts with recurring billing for subscription refunds and reversals, or with hosted checkout products for the shopper-side of the flow.
A REST API that reads like the rest of your stack
One endpoint creates a payout. The rail field selects SEPA, SEPA Instant credit transfer, card push, SWIFT or a batch reference. Idempotency keys make retries safe. Signed webhooks confirm every state change, even if your service was down when the event fired.
POST /v1/payouts
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 12500,
"currency": "EUR",
"rail": "ideal",
"beneficiary": {
"name": "Ada Contractor",
"iban": "DE44500105175407324931"
},
"reference": "INV-2027-0142",
"metadata": { "batch_id": "may-week-1" }
}The response returns a canonical payout object with a status field, the scheme reference and a webhook_id. Full schema in the API reference.
Industries we underwrite for payouts
BazPay is a global payment provider. Underwriting is scoped to businesses with predictable chargeback profiles and clean AML posture. If your model fits one of the four below, board within days.
-
E-commerce sellers
DTC brands and multi-country storefronts settling into EUR and paying refunds, marketplace legs and supplier runs from the same balance.
-
Subscription software
SaaS teams issuing pro-rated credits, partner referral payments and customer withdrawals off ledger balances.
-
Professional services
Agencies, consultancies and B2B services running weekly contractor and supplier batches on SEPA Instant.
-
Digital publishers
Membership and paywall businesses paying contributors, translators and licensing partners on schedule.
Out of scope: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. Those verticals are declined at application.
Security and compliance signals
Payouts sit inside the same PCI DSS Level 1 environment as our acquiring. Sanctions screening runs before every message leaves. Card tokens never move outside our vault, so pushing to a card does not widen your PCI scope.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment
- Card scope
- Merchant SAQ A — tokens stay in our vault
- Sanctions screening
- Pre-send screening on every payee record
- SEPA and SEPA Instant
- Direct participation where the corridor is supported
- GDPR
- In-region data residency; DPA on request
Instant payout questions we get asked
Short answers. The full detail lives in the API docs.
What counts as an instant payout on BazPay?
Any payout on SEPA Instant reaches the payee settlement account in seconds, twenty-four hours a day, provided the receiving bank participates in the scheme. Push-to-card is also near-instant on issuers that support Visa OCT and Mastercard MoneySend. Instant credit transfer and SWIFT run on standard cycles and are not classed as instant.
Is BazPay a global payout platform?
BazPay is an locally licensed payment gateway with cross-border reach through SWIFT on approved corridors and card push where scheme OCT is available. That means you can pay a large share of global beneficiaries from one balance, but coverage is defined per corridor rather than blanket. Sales can list the currently supported destinations.
How does an instant payout differ from a card refund?
A card refund reverses the original authorisation and only works inside the card scheme's refund window — typically 120 to 180 days. An instant payout is a new outbound transfer against your balance, independent of the original sale, so it works after the refund window has closed and for shoppers who paid by another method.
Do I need a separate account to send payouts?
No. Payouts draw on the same balance your card, wallet and open banking sales settle into. One account, one key, one dashboard. This is what makes the money-out side of the global payment gateway feel like part of the same product, not a bolt-on.
Does sending a payout put card data in my systems?
No. Card tokens stay in the BazPay vault. We hold PCI DSS Level 1 on the gateway environment, so your merchant return stays at SAQ A even when you push funds to cards.
What happens when a transfer is returned?
Funds return to your balance. The webhook carries the scheme return code — AC01 for wrong settlement account, AC04 for closed account, AM04 for insufficient funds on card push, and so on — so you can fix the detail and resend without guessing.
How does the platform compare with dedicated global payment processors?
Standalone payout tools require you to top up a separate wallet and reconcile two ledgers. Unified global payment providers like BazPay fund payouts from the acquiring balance, so you skip the transfer step, reduce idle cash and keep sales and payouts in the same report.
Can I test payouts before going live?
Yes. Sandbox keys cover every payout rail. Replay accepted, sent, settled, returned and rejected outcomes before you send real money — including SEPA Instant return codes and card-push failure codes.
Send your first test payout today
Open a sandbox account and get keys at once. Post a SEPA Instant test transfer in the same hour. Prefer to walk the rails through first? A payments specialist can map your flow, your corridor coverage and your batch cadence with you.