A bank payment system for merchants who need direct bank rails.
BazPay is a bank payment gateway that moves money directly between two accounts. Cards and open-banking charges share one contract, one API and one dashboard. Bank-rail funds clear on SEPA Instant, usually within seconds; card acquiring settles to the same named settlement account.
Built for regional sellers: e-commerce, subscription software and professional services. One key covers pay-by-bank, cards, wallets and local methods.
Why merchants pick a bank-rail payment gateway
Bank rails do things card rails cannot: instant clearing, no interchange, no scheme chargeback exposure. The four points below are the reasons finance, product and engineering teams turn the method on first.
-
One bank payment gateway, two rails
The same API and dashboard run open-banking A2A charges and card acquiring. One key, one webhook stream, one reconciliation file — you decide which rail each order takes.
-
Direct acquiring-bank settlement
Funds settle into your named settlement account, not into an aggregated omnibus. Line-level reporting ties every payment back to its own bank reference for finance reconciliation.
-
No card data in the flow
Pay-by-bank charges carry no PAN, no CVC and no token. Your PCI scope for that method is nil; card charges on the same integration stay at merchant SAQ A.
-
Refund on the same rail
Refunds go back to the account that paid over SEPA Instant. There is no scheme reversal, no dispute deadline and no fee schedule tied to a chargeback ratio.
How a bank payment moves
Four steps, start to finish. Your server only has to handle the last one.
-
Shopper picks pay by bank
At checkout they choose their own bank. We show only the methods live in their country.
-
They approve in the bank app
The bank runs login and strong customer authentication. You never see a credential.
-
Funds move on SEPA Instant
Money leaves their account and lands in yours. Most transfers clear within seconds.
-
A signed webhook confirms it
We post the final status to your endpoint. Release the order on that event, not on the redirect.
Local methods, one contract
Each regional market has its own habit. German shoppers reach for SEPA Instant. British shoppers reach for Bancontact. The bank payment system keeps them all behind one set of endpoints.
Turn a method on per country. The checkout then shows only what that shopper can actually use. See the plugin coverage on our integrations page.
| Method | Market | Flow | Note |
|---|---|---|---|
| SEPA Instant | Germany | Bank redirect | Dominant local method |
| Bancontact | the United Kingdom | Code or app push | Mobile-first |
| BLIK | Australia | Bank redirect | App or card mode |
| EPS | France | Bank redirect | Bank-issued flow |
| Przelewy24 | the United Kingdom | Bank redirect | Broad bank list |
| Instant credit transfer | Germany | Account to account | Also used for payouts |
| SEPA Instant (SEPA Instant) | Germany | Account to account | Sub-10-second clearing |
Features of the BazPay bank payment gateway
Everything below ships on the standard integration. Flip a feature on with a request flag or a dashboard toggle — no enterprise gate on the primitives.
-
Country-aware method picker
The checkout shows only the bank-rail methods live in the shopper's country. No dead options, no confused conversions.
-
SEPA Instant coverage
Where the beneficiary bank participates in SEPA Instant, funds land in seconds — not on the next business-day cycle.
-
Debit-order mandates
Store a mandate once, debit it on schedule. Suitable for subscription renewals and recurring service invoices.
-
Signed webhooks
Every state change carries an HMAC signature, a timestamp and a replay-safe idempotency key you can rely on server-side.
-
Idempotent API
Retry any create request with the same key. You will never double-charge on a network blip or a lambda retry.
-
Pay-by-link
Send a hosted payment link with your invoice. The client pays from their bank app; funds arrive the same day.
-
Bank-side authentication
Strong customer authentication is performed by the payer's bank. No 3-D Secure step, no card-scheme rules, no exemption logic.
-
Line-level reporting
Every settlement line ties back to its own bank reference and to the original charge ID for clean reconciliation.
One REST API for cards and bank rails
The same endpoint creates a charge on any rail. The payment_method field
decides whether the request runs as a card, a wallet or an open-banking A2A payment.
Idempotency keys make retries safe. Signed webhooks carry the state changes.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 14900,
"currency": "EUR",
"payment_method": "open_banking",
"country": "NL",
"return_url": "https://shop.example/return",
"metadata": { "order_id": "ORD-10842" }
}The response returns a canonical charge object with the redirect target for the payer's bank, the settlement reference and the signed webhook_id. Complete schema in the API reference; handler code samples in the developer docs.
Bank rails next to card rails
Neither one wins outright. They fail in different places, so most sellers run both. Here is the honest split.
| Bank-rail (A2A) | Card acquiring | |
|---|---|---|
| What the shopper uses | Their banking app | A card number |
| Card data in your scope | None | None — hosted fields keep you at SAQ A |
| Authentication | Bank-issued 3-D Secure | 3-D Secure 2.2 |
| Interchange | Not applicable | Scheme interchange applies |
| Chargeback rights | No scheme chargeback | Scheme chargeback rules apply |
| Typical settlement | SEPA Instant, seconds | Scheme settlement cycle |
| Recurring support | debit-order mandate based | Stored credential based |
Running both? Compare the full scheme setup on card and APM processing, and see how outbound transfers work on payouts.
Where sellers switch it on first
Four patterns come up again and again across our book.
-
E-commerce
High-value baskets
Large orders attract card risk checks. Pay by bank skips the scheme rails entirely, so the decline reasons that hurt big baskets never fire.
-
SaaS
Annual plan renewals
Charge the yearly plan by bank and the card renewal problem is gone. No expiry, no reissue, no dunning cycle for that invoice.
-
Professional services
Invoices and deposits
Send a pay-by-bank link with the invoice. The client approves in their bank app. You see the funds land the same day.
-
Digital publishers
Membership top-ups
Higher-ticket annual memberships settle in one bank transfer instead of a scheme-cycle wait, so entitlements go live the same session.
Billing on a schedule too? See how mandates work under recurring billing. Fraud posture across both rails lives in anti-fraud controls, and post-charge reporting sits in real-time analytics.
Security, compliance and settlement
The bank payment system runs under PSD2, with strong customer authentication performed by the payer's bank. Card charges on the same integration sit inside our PCI DSS Level 1 environment. Settlement lands in your named settlement account — never in an aggregated omnibus you do not own.
Refunds run on the same rail the payment took. For open-banking charges, that is a SEPA Instant transfer back to the account that paid; for card charges, the scheme's refund flow. In both cases the finance team gets a bank reference tied to the original charge ID.
Questions we get asked
Short answers from the team that runs the rail.
What is a bank payment system, and how does BazPay's differ?
A bank payment system moves money directly between two bank accounts, without card-scheme rails in the middle. BazPay's runs on SEPA and SEPA Instant with bank-issued strong customer authentication, and shares one API, one dashboard and one settlement account with the card side of the platform.
Do I still need card acquiring?
Most sellers run both. Pay by bank suits home markets, high-value baskets and annual renewals; cards still cover cross-border shoppers, wallets and lower tickets. BazPay is both the bank payment gateway and the card acquirer, so both rails ship on one contract.
Where does the money actually land?
For open-banking charges, funds move directly from the payer's account to your named settlement account over SEPA or SEPA Instant. For cards, funds settle from the BazPay acquiring balance into the same settlement account on the scheme's settlement cycle. Reporting reconciles both back to the original charge.
How does authentication work if there is no 3-D Secure?
The payer's own bank performs strong customer authentication when they approve the payment in-app. That satisfies authentication and shifts liability to the bank for authentication of the payer. There is nothing for you to integrate on the 3-D Secure layer.
Can I refund a pay-by-bank order?
Yes. Refunds go back to the account that paid over SEPA Instant. It is a transfer, not a scheme reversal, and it clears on the same rail. Full and partial refunds are supported from the dashboard and the API.
Is BazPay a commercial bank payment gateway or a bank itself?
BazPay is a licensed regional payment institution and a card acquirer, not a chartered bank. That means we hold the acquiring relationships and the open-banking connections a commercial bank payment gateway needs to route your traffic, but merchant funds settle into your own bank account, not ours.
How is my PCI scope affected?
Open-banking charges never touch card data, so the method itself has no PCI impact. Your gateway scope for the card side stays at SAQ A, the smallest return a seller can file, because hosted fields and gateway vaulting keep PAN data out of your infrastructure.
How fast can I turn the bank payment system on?
Open-banking methods run on the same key and the same API as your card traffic. Sandbox is self-service; one call flips a method live once your acquiring-bank payment gateway contract is signed. No separate integration.
Test a pay-by-bank flow today
Sandbox keys are self-service. Fire a test SEPA payment, catch the webhook and see the settled event in your dashboard. Fees for both rails are on the pricing page; hosted UI ships in checkout products. See also merchant acquiring, Faster Payments, the NPP payment system, the network payment gateway and international payments.