Pay money out of the balance you collect into.
Payouts is the money-out side of the BazPay gateway. Send a SEPA credit transfer to an IBAN, reach a beneficiary outside the SEPA area over SWIFT, push funds to a card, or upload a batch file. It is the same account, the same key and the same webhook stream you already use.
Built for EU e-commerce sellers, subscription software firms and professional-services businesses. Underwriting stays low-risk on purpose. Pricing is published.
Four ways to send
Pick the rail that fits the payee. They share one endpoint and one status model, so your code stays the same.
-
01Bank transfer
SEPA credit transfer
Send funds to any IBAN in the SEPA area. You pass the name, the IBAN and a reference. We handle the scheme message and the return codes. Failed transfers come back with a reason you can act on.
- IBAN
- EUR
- Return codes
-
02Fast rail
SEPA Instant
Same message, faster rail. Funds reach the payee bank in seconds, around the clock. The receiving bank must take part in the scheme.
- Seconds
- 24/7
- EUR
-
03Card push
Push to card
Send money straight to a Visa or Mastercard card. Useful when you hold a card token but no bank details. The payee sees the credit on their card account.
- Visa
- Mastercard
- Token
-
04Cross-border
International transfer
Pay beneficiaries outside the SEPA area over SWIFT. You pass the account and bank identifiers; we build the message and hand back the return path. Settlement timing follows the correspondent banks on the route, not us — so we quote the corridor rather than promise a date.
- SWIFT
- Non-EUR
- Correspondent
-
05Volume
Batch files
Upload one file and pay many people at once. Each row is treated as its own payout. Failures are reported per row, so one bad IBAN never blocks the batch.
- CSV
- Per-row status
- Bulk
When sellers reach for a payout
Most gateways treat money-out as an afterthought. Ours sits in the same product line as acquiring. That means one balance, one reconciliation view and one support contact.
See the rest of the line on the products overview.
-
Refunds beyond the card window
Some refunds land after the original card sale can be reversed. A 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.
Rails, landing point and timing
Timing is set by the scheme and the receiving bank, not by us. This is what each rail does.
| Rail | Funds land | Timing | Note |
|---|---|---|---|
| SEPA credit transfer | Payee IBAN | Next business cycle | Bank hours apply |
| SEPA Instant | Payee IBAN | Seconds, 24/7 | Both banks must join |
| Push to card | Card account | Scheme timing | Visa and Mastercard |
| Batch file | Mixed | Per row, per rail | Row-level results |
Platform coverage for plugins and shop systems is listed under integrations.
How a payout moves
Four steps from balance to settled. Each one leaves a record you can export.
-
Fund from your balance
Payouts draw on the same balance your card and open banking sales settle into. No second account to top up.
-
Call one endpoint
Post the amount, the rail and the payee details. The response carries a payout ID you can track from then on.
-
Watch the webhook
State changes fire as 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.
Payout questions we get asked
Short answers. The full detail lives in the API docs.
Do I need a separate account to send payouts?
No. Payouts run off the balance you already collect into. One account, one key, one dashboard.
Does a payout put card data in my systems?
No. Card tokens stay in our vault. We hold PCI DSS Level 1 on the gateway side, so your return stays at SAQ A.
What happens when a transfer is returned?
The funds come back to your balance. The webhook carries the scheme return code, so you can fix the detail and resend.
Can I test payouts before going live?
Yes. Sandbox keys cover every payout rail. Replay accepted, returned and rejected outcomes before you send real money.
Send your first test payout today
Open a sandbox account and get keys at once. Send a test transfer in the same hour. Prefer to talk the rails through first? A payments specialist can map your flow with you.