A credit payment processor built for EU, UK and Commonwealth merchants.
BazPay is a direct credit payment processor and regional acquirer. Cards, device wallets and local payment methods share one contract, one REST API and one dashboard. Cards issued outside the region authorise on that same contract, because the acquiring is local and the card networks are global.
Built for e-commerce sellers, subscription software firms and professional-services businesses. Underwriting scope is deliberately narrow — that is why approval rates hold steady across our book and why finance teams get clean, line-level reporting.
Why merchants choose BazPay as their credit payment gateway
Four things stay true whether you process a hundred euros a day or a million. They are the reasons product, engineering and finance teams stay with us after the migration.
-
One contract, one credit payment gateway
Cards, wallets and local methods sit behind a single REST endpoint. No brokered PSP layer between you and the acquirer, and no separate contract per scheme.
-
Reduced PCI scope
Hosted fields and gateway-side vaulting keep raw PAN data out of your infrastructure. Most integrations qualify for merchant SAQ A instead of full audit.
-
Higher authorisation quality
BIN-aware routing, PSD2 exemption logic and network-token refresh raise approvals on live traffic — not on synthetic tests.
-
EU, UK and Commonwealth settlement, global card reach
Funds settle from our regional acquiring balance into your named settlement account. Non-regional issued cards still authorise on the same contract.
What the card credit payment system accepts
Four method families run through one connection. Turn any of them on from the dashboard — no new contract is needed and no code change beyond a payment-method flag on the charge request.
-
Schemes
Credit and debit card acquiring
Visa, Mastercard and American Express clear on our own regional acquiring licence, alongside the domestic debit schemes that carry most of the volume in their own markets — Cartes Bancaires in France, eftpos in Australia, Interac Debit in Canada, Dankort in Denmark. One contract covers every scheme, and a card issued outside the region authorises against the same contract as a domestic one.
- Visa
- Mastercard
- American Express
- Cartes Bancaires
- eftpos
- Interac Debit
- Dankort
-
Wallets
Device wallets on card rails
Apple Pay and Google Pay ride the same credit payment rails. The wallet supplies a network token, so the PAN never touches your servers or ours in the clear.
- Apple Pay
- Google Pay
-
Local methods
Alternative payment methods, by market
Shoppers pay the way their market already pays: bank buttons in the Benelux and Poland, phone-number wallets across the Nordics, pay by bank in the UK, PayTo and BPAY in Australia, Interac in Canada, account-to-account in New Zealand. Each method sits behind the same API call as a card charge, so one integration covers cards and APMs.
- iDEAL
- Bancontact
- BLIK
- Przelewy24
- EPS
- Swish
- MobilePay
- Vipps
- TWINT
- MB WAY
- Pay by bank
- PayTo
- BPAY
- POLi
- Interac
- Account2Account
-
Credit
Buy now, pay later
The provider settles with you in full and carries the credit risk. Basket lift is real, the headline fee is higher than a card, and the dispute runs under consumer-credit rules rather than scheme ones — so it belongs in a margin conversation, not a checkbox.
- Klarna
- Clearpay / Afterpay
- Zip
- Laybuy
-
Tokens
Vault and network tokens
We store the credential, not you. Network tokens refresh when a card is reissued, so card-on-file charges and subscription renewals keep working through the credit payment system.
- 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. Reconciling all of it? Real-time analytics ties every authorisation, decline and settlement line back to the same charge ID, and all products lists the wider platform. New to online acceptance? Start with accept online payments. Single-method deep dive on iDEAL payments; coverage breadth across every method on payment acceptance.
The life of one authorisation
Six stages sit between a tap and a settled dollar. Each one is visible in the dashboard, and each one emits a signed webhook for your systems to consume.
-
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.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 range.
-
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.
Direct acquirer vs third-party processors and credit cards resellers
A reseller routes traffic through a downstream acquirer under an aggregated MID. That layer adds latency to settlement, blurs reporting and often blanket-applies 3-D Secure. A direct acquirer removes the middle layer.
| Dimension | BazPay (direct) | Third-party PSP (reseller) |
|---|---|---|
| Contract | Direct with BazPay as acquirer | Chain of third-party sub-processors |
| PAN handling | Hosted fields, gateway vault | Merchant-hosted fields common |
| 3-D Secure | 3-D Secure 2.2 with exemption logic | 3-D Secure often applied blanket |
| Settlement | Regional acquiring balance to your settlement account | Aggregated payouts on delay |
| Reporting | Interchange++ line detail | Blended-rate summary |
| Webhooks | Signed, idempotent, replayable | Varies by reseller |
See the full breakdown of settlement and fees on the pricing page, the merchant acquiring contract that underpins the direct MID, and the network payment gateway layer that unifies cards, wallets and APMs behind one API. For a buyer's-side view see the payment processors comparison and the underlying payment infrastructure.
Features engineered into the credit payment system
Every capability below is available on the standard integration. Turn them on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment inside your checkout.
-
Gateway-side vault
Store credentials once, charge them repeatedly across renewals, upgrades and one-clicks.
-
Network tokens
Automatic PAN refresh through Visa and Mastercard token services keeps saved cards live.
-
3-D Secure 2.2
Frictionless flow first, challenge only when the issuer or your risk profile requires it.
-
PSD2 exemption logic
TRA, low-value, trusted-beneficiary and MIT flags claimed automatically per rule set.
-
Signed webhooks
Every event carries an HMAC signature, a timestamp and a replay-safe idempotency key.
-
Idempotent API
Retry any create request with the same key — you will never double-charge on a network blip.
-
Interchange++ reporting
Scheme fees, interchange and gateway margin split on every line for finance reconciliation.
A REST API that reads the same as your other services
One endpoint creates a charge. The payment_method field decides whether the request runs as a card, a wallet or a local payment method. Idempotency keys make retries safe. Signed webhooks confirm every state change asynchronously — even if your service was down when the event fired.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"payment_method": "card",
"capture": "auto",
"three_d_secure": "required_if_needed",
"customer": "cus_5F9k",
"metadata": { "order_id": "ORD-10842" }
}The response returns a canonical charge object with the authorisation code, the interchange bucket, the exemption applied (if any) and a signed webhook_id. Read the complete schema in the API reference.
Decline reasons, and what we do next
A decline is data, not a dead end. The credit payment processor reads the reason code and acts on it. You see the same code in real-time analytics within seconds and can wire your dunning stack to the signed webhook.
| 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 | 3-D Secure required | Step up to 3-D Secure 2 | PSD2 SCA |
| 14 | Invalid card number | Return the shopper to checkout | Input |
Industries we underwrite for credit card processing
BazPay is a credit payment solutions provider. Our 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 running Shopware, Magento 2, WooCommerce or PrestaShop.
-
Subscription software
SaaS teams billing monthly and annual plans with saved-card renewals and dunning.
-
Professional services
Agencies, consultancies and B2B service firms invoicing recurring retainers.
-
Digital publishers
Media businesses selling memberships, single-issue purchases and paywall unlocks.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.
Security and compliance signals
The credit cards payment system runs inside a PCI DSS Level 1 environment audited each year. Hosted fields, tokenisation and signed webhooks are the primitives that keep your merchant scope at SAQ A. Encryption is end-to-end from the shopper's browser to the acquiring bank.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment
- Authentication
- 3-D Secure 2.2 with exemption engine on every card charge
- GDPR
- In-region data residency; DPA on request
- Least-cost routing
- Dual-network debit routed to the cheaper scheme per transaction
- Scheme compliance
- Visa VIRP and Mastercard SPoC/PCI-CP registered where required
Questions merchants ask first
What is a credit payment processor, and where does BazPay sit?
A credit payment processor moves an authorisation request from a merchant to the card scheme, back through the issuing bank, and returns funds on settlement. BazPay is the processor and the acquirer for its regional book, so there is no third-party PSP in between — cards, wallets and APMs run on one direct contract.
Do I need my own PCI audit to accept credit cards through BazPay?
No. We hold PCI DSS Level 1 on the acquiring and gateway environment. Hosted fields keep card data out of your stack, so most integrations qualify for merchant SAQ A. Your annual return stays short and your engineering team never handles a live PAN.
Can I keep saved cards if I migrate from another credit cards payment system?
Yes. The BazPay vault is gateway-side and portable. Stored credentials, network tokens and debit-order mandates can be imported from an incumbent processor under a scheme-approved migration, subject to the receiving bank's consent letters. Renewals continue without asking shoppers to re-enter their card.
How are local payment methods and cards priced together?
Every method is priced on its own line. Cards use interchange++, so scheme fees, interchange and the BazPay margin appear separately on each transaction. Local methods carry their own scheme rate and are never blended into a headline card rate. Current schedules live on the pricing page.
What happens on a soft decline through the credit payment gateway?
We read the reason code and act on it. Some codes earn an automatic retry on a second connection, some trigger a network-token refresh, and some go straight back to the shopper. Every decline is available in real-time analytics within seconds and via signed webhook for your dunning system.
How does BazPay compare with third-party processors and credit cards resellers?
Third-party processors typically resell a downstream acquirer under an aggregated MID, which can delay settlement and blur reporting. BazPay is the acquirer for the regional book. You get a named MID, interchange++ line-level reporting and regional settlement into your own settlement account.
Which currencies and settlement corridors are supported?
Card authorisation runs in EUR and more than twenty presentment currencies. Settlement lands in EUR into a regional settlement account by default; other named settlement currencies are available for approved corridors. SEPA Instant is used for payouts where the beneficiary bank participates.
Which merchant categories does BazPay decline?
No. BazPay is a regional credit payment solutions provider. Our underwriting is scoped to e-commerce, subscription software and professional services. We do not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM businesses.
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, your saved-card migration and your payouts corridors with you.