Merchant acquiring for EU low-risk businesses.
BazPay is a direct merchant acquiring partner for e-commerce, subscription software and professional-services firms in the European Union. One contract covers scheme membership, authorisation, settlement and dispute handling — no aggregated MID, no reseller between you and the network.
Named merchant identifier, interchange++ reporting and EU settlement into your own IBAN. Cards, wallets and local methods share the same acquiring rail, the same charge object and the same signed webhook.
Why merchants choose BazPay for payment acquiring
Four things stay true whether you clear a hundred euros a day or a million. They are the reasons product, engineering and finance teams stay with us after boarding is done.
-
One acquiring institution, one contract
You contract with BazPay directly. No downstream reseller layer, no aggregated MID, no split boarding. The credentials that authorise your traffic and the ones that settle your funds belong to the same platform.
-
Named merchant identifier
Every merchant receives its own MID with the schemes. That means clean chargeback attribution, transparent scheme-fee reporting and no shared-MID risk from other people's traffic.
-
Interchange++ transparency
Scheme fees, interchange and the BazPay margin appear on every settled transaction. Finance teams reconcile against the source, not against a blended rate.
-
Rails you already run
Cards, wallets and local payment methods share the same charge object. Your acquiring, your fraud rules and your payouts all sit behind one REST API and one dashboard.
What the acquiring contract covers
Cards acquiring on our own EU licence, EU local payment methods alongside, multi-currency acceptance and tokenised device wallets — all on the same MID and the same reporting surface.
-
Schemes
Card networks
Direct scheme membership on the EU acquiring licence. Cards issued outside the EU authorise on the same contract and settle into the same balance.
- Visa
- Mastercard
- Maestro
- Cartes Bancaires
-
Wallets
Tokenised device wallets
Wallet-issued network tokens ride the same acquiring rail as raw PAN, without exposing card data to your servers.
- Apple Pay
- Google Pay
-
Methods
EU APMs alongside cards
Local payment methods clear through partner processors and reconcile into the same settlement balance as card volume.
- iDEAL
- BLIK
- Bancontact
- EPS
- Przelewy24
-
Currencies
Multi-currency acceptance
Authorise in the shopper's currency and settle in EUR into an EU IBAN. Named settlement currencies available for approved corridors.
- EUR
- GBP
- SEK
- DKK
- PLN
- 20+ more
Payment-method depth on card and APM processing. Bank rails and open-banking payments on open banking.
From board to first settlement
Six stages sit between the KYC pack and a settled euro on your bank account. Each stage is trackable in the dashboard and each stage change fires a signed webhook.
-
Board
KYC and merchant underwriting. Documents, ownership and business model reviewed against the low-risk criteria.
-
Provision
A named MID is opened with the schemes for your legal entity. Sandbox and live credentials issued for the API.
-
Integrate
One REST endpoint, one webhook signing secret and hosted fields for the checkout. Existing plugins cover common stacks.
-
Authorise
Every charge posts against your MID with the correct MCC, region and 3-D Secure result bound to the transaction.
-
Settle
Funds reconcile per scheme cycle and land in your EU IBAN. Every line ties back to its own transaction ID.
-
Reconcile
Interchange++ statements and signed webhooks feed your finance stack. Chargeback and refund events are first-class.
Direct acquiring vs aggregated PSP
A reseller routes your traffic through a downstream acquirer under a shared MID. It is fast to sign, and it costs you in every dimension that matters after go-live: reporting, chargeback attribution and settlement timing. The comparison below explains where each model earns its keep.
| Dimension | BazPay (direct acquirer) | Aggregated PSP (reseller) |
|---|---|---|
| Contract holder | Direct with BazPay as acquirer | Reseller PSP on aggregated MID |
| MID structure | Named MID per merchant | Shared MID pool |
| Chargeback attribution | Attributed to your MID | Diluted across the pool |
| Settlement | Per-scheme cycle to your EU IBAN | Aggregated payouts, common delay |
| Reporting | Interchange++ line detail | Blended-rate summary |
| Rule changes | Dashboard, effective on next order | Ticket to the reseller |
| Underwriting | Direct with your onboarding manager | Passed through the reseller |
Statement structure and rate cards on the pricing page. See how the acquiring contract feeds the wider network payment gateway layer and packaged payments solutions, and how each scheme cycle lands in real-time analytics.
Features engineered into the acquiring rail
Every capability below ships on the standard integration. Turn features on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives.
-
Named MID per merchant
Your own merchant identifier at each scheme. Chargeback ratios, decline data and settlement reporting attributed to your entity.
-
REST API and webhooks
One endpoint creates a charge. Signed, replay-protected webhooks confirm every state change.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment inside your checkout, keeping your scope at SAQ A.
-
Gateway-side vault
Store credentials once and reuse them across renewals, upgrades and one-clicks — portable if you ever change stack.
-
3-D Secure 2.2 engine
PSD2 SCA with automatic exemption logic. Liability shift where the scheme permits it, less friction where it does not.
-
Idempotent requests
Retry-safe create requests keyed to your idempotency header. A network blip never becomes a double charge.
-
SEPA and SEPA Instant
Direct participation for merchant payouts in supported corridors. SWIFT and push-to-card options for approved routes.
-
Interchange++ reporting
Every settled transaction breaks out interchange, scheme fees and acquirer margin for line-level reconciliation.
One API for every acquiring payment transaction
The charge object is the unit of work. One endpoint authorises, captures and refunds. The payment_method field selects the rail. Idempotency keys make retries safe. Signed webhooks confirm state changes 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",
"descriptor": "ACME EU LTD",
"metadata": { "order_id": "ORD-10842" }
}The response returns a canonical charge object with the authorisation code, the MID it posted against, the interchange bucket and any exemption applied. Read the complete schema in the API reference.
Who we underwrite for internet acquiring
BazPay is a low-risk EU acquiring institution. Underwriting is scoped to four merchant profiles with predictable chargeback ratios and clean AML posture.
-
Multi-country e-commerce
One acquiring contract for EU storefronts running Shopware, Magento 2, WooCommerce or PrestaShop. Local card acceptance without stitching regional PSPs.
-
Subscription software
SaaS billing with card-on-file, dunning-aware retries and MIT exemptions on renewals. Full interchange visibility on high-volume, low-ticket books.
-
Professional services
B2B invoicing with higher tickets, named-payer trust lists and enforced 3-D Secure 2 over a ceiling you set.
-
Digital publishers
Membership renewals, single-issue purchases and paywall unlocks on one MID with clean reporting per SKU.
Out of scope for BazPay acquiring: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a marketplace of third-party PSPs.
Security and compliance signals
The acquiring environment runs inside a PCI DSS Level 1 assessment renewed each year. Hosted fields and gateway-side vaulting keep your annual return at merchant SAQ A. PSD2 SCA runs on every card charge with exemption logic where the rules allow.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment
- Merchant SAQ A
- Hosted fields and gateway vault keep card data out of your stack
- PSD2 SCA
- 3-D Secure 2.2 with exemption engine on every card charge
- GDPR
- EU data residency; DPA available on request
- SEPA / SEPA Instant
- Direct participation for merchant payouts in supported corridors
- Scheme registrations
- Visa VIRP and Mastercard SPoC/PCI-CP where required
Questions merchants ask before signing
What is merchant acquiring, and where does BazPay sit?
Merchant acquiring is the contractual and technical relationship that lets a business accept card payments and receive the funds. The acquiring institution is the licensed entity that holds membership with the card schemes, processes authorisations and settles the merchant. BazPay is that acquiring partner for EU low-risk merchants on the platform operated by NEWERA PAYMENT TECHNOLOGIES LTD.
What is the difference between an acquiring bank and a payment processor?
An acquiring bank holds the scheme membership and the merchant contract. A payment processor moves the authorisation message between the merchant, the schemes and the issuers. BazPay combines both functions for its EU book — one direct contract covers acquiring in banking terms, plus the technical processing, so there is no intermediary reseller between you and the network.
Do you offer full acquiring or a gateway on top of another bank?
Full acquiring on our own EU licence for the card schemes we support directly. Selected local payment methods clear through named partner processors and reconcile into the same settlement balance. You will always see the actual routing on your interchange++ statement — nothing is hidden behind a wrapper.
How long does merchant onboarding take?
Standard EU low-risk boarding typically completes in a few business days once KYC documents, beneficial ownership evidence and the business model description have been received. Higher-ticket or multi-entity applications need longer for legal review. Sandbox credentials are available before boarding finishes so integration work can start in parallel.
Which currencies and settlement corridors are supported?
Authorisation runs in EUR and more than twenty presentment currencies. Settlement defaults to EUR into an EU IBAN. Named settlement currencies and SEPA Instant, SWIFT or push-to-card payouts are available on approved corridors — the current schedule is on the pricing page and confirmed during boarding.
How do chargebacks work on BazPay merchant acquiring?
Because you hold a named MID, chargebacks are attributed to your entity — never diluted across a pool. Scheme dispute events fire as signed webhooks and land in the dashboard with the transaction, the 3-D Secure result, the signals that scored it and any early-warning alert. Evidence templates are pre-assembled to the scheme's current format for one-click submission.
Which merchant types can BazPay board?
BazPay boards EU low-risk merchants: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, nor does it act as a marketplace of third-party PSPs.
Can I keep saved cards if I move my acquiring processing to BazPay?
Yes. The gateway vault is portable, and stored credentials plus network tokens can be imported from an incumbent processor under a scheme-approved migration, subject to the receiving bank's consent letters. Renewals and card-on-file charges continue without asking shoppers to re-enter their card.
Start the acquiring conversation
Share your business model and volumes and we will confirm boarding fit, likely rate structure and settlement corridor within one working day. Sandbox keys are available so integration work can begin in parallel — see also hosted checkout products, anti-fraud controls and payouts. Related reading: the network payment gateway, how BazPay compares as a payment provider, merchant services and international payment corridors.