Cards and local methods on one contract.
BazPay clears card traffic on its own EU acquiring licence. Wallets and local payment methods sit behind the same API call. Cards issued outside the EU authorise on that same contract — the acquiring is European, the card networks are global. You wire the integration once. Then you switch markets on as you grow.
Built for EU e-commerce sellers, subscription software firms and professional-services businesses. Underwriting stays low-risk on purpose. That is why approval rates hold steady across our book.
What you can accept
Four method families run through one connection. Turn any of them on from the dashboard. No new contract is needed.
-
Schemes
Card acquiring
Visa, Mastercard, Maestro and Cartes Bancaires clear on our own acquiring licence. One contract covers every scheme. The licence is European, but the schemes are not — a card issued outside the EU authorises on the same contract as a domestic one, and settles into the same balance you pay out from.
- Visa
- Mastercard
- Maestro
- Cartes Bancaires
-
Wallets
Device wallets
Apple Pay and Google Pay ride the same card rails. The wallet supplies a network token, so the card number never moves.
- Apple Pay
- Google Pay
-
Local methods
EU APM library
Shoppers pay the way their market already pays. Each method sits behind the same API call as a card charge.
- iDEAL
- BLIK
- Bancontact
- EPS
- Przelewy24
-
Tokens
Vault and network tokens
We store the credential, not you. Network tokens refresh when a card is reissued, so saved cards keep working.
- Gateway vault
- Network tokens
- Card-on-file
Paying by bank instead? See open banking for SEPA Instant rails, or recurring billing for saved-card renewals.
The life of one authorisation
Six stages sit between a tap and a settled euro. Each one is visible in the dashboard.
-
Collect
Hosted fields render inside our PCI scope. The card number skips your servers entirely.
-
Score
Risk rules and device signals grade the order first. Clean orders skip the extra step.
-
Authenticate
3-D Secure 2 runs only when the risk earns it. Exemption logic claims the rest.
-
Route
Routing picks the connection with the best recent approval record for that BIN.
-
Capture
Capture at once or later. Partial captures and partial refunds both post cleanly.
-
Settle
Funds reconcile per scheme cycle. Every line ties back to its own transaction ID.
Decline reasons, and what we do next
A decline is data, not a dead end. We read the reason code and act on it. You see the same code in real-time analytics within seconds.
| Code | Reason | Our next step | Source |
|---|---|---|---|
| 05 | Do not honour | Retry on a second connection | Issuer |
| 51 | Insufficient funds | Schedule a dunning retry | Issuer |
| 54 | Expired card | Refresh the network token | Scheme |
| 65 | SCA required | Step up to 3-D Secure 2 | PSD2 |
| 14 | Invalid card number | Ask the shopper again | Input |
Questions merchants ask first
Do I need my own PCI audit?
No. We hold PCI DSS Level 1 on the gateway side. Hosted fields keep card data out of your stack. Your yearly return stays at SAQ A.
Can I keep saved cards if I switch rails?
Yes. The vault is gateway-side and portable. Stored credentials and mandates move with your account.
How are local methods priced?
Each method is priced on its own line, not blended into a card rate. See the published pricing page for the current schedule.
What happens on a soft decline?
We read the reason code and act on it. Some codes earn a retry on another connection. Others go straight back to the shopper.
Send a test charge today
Open a sandbox account and post your first authorisation in the same hour. Want the rails walked through first? A payments specialist can map your markets with you.