Merchant services on one platform for EU businesses.
BazPay merchant services bundle EU acquiring, the payment gateway, hosted checkout, recurring billing, fraud controls, payouts and reporting behind one REST API and one dashboard. One contract, one MID, one bill — not a stitched stack of four vendors.
Built for EU e-commerce sellers, subscription software firms and professional-services companies. Boarding, licensing and settlement all live in the European Union, so the teams that run your payments are the teams that answer the regulator.
Why merchant services on a single platform matter
A stitched stack costs at the seams. Reporting drifts between vendors, chargebacks land in the wrong inbox, and rule changes wait for a support ticket. Consolidating on one platform removes those seams.
-
One provider, one bill
Acquiring, gateway, checkout, recurring billing, payouts and reporting are the same platform under the same contract. No second vendor to reconcile against, no split boarding, no shared MID.
-
Software your teams actually use
The dashboard is built for the people who run the day. Ops see the review queue, finance see interchange++ statements, developers see logs and event replay, executives see a live cohort of settled volume.
-
Move at the pace of a config change
New payment method, new fraud rule, new descriptor, new webhook endpoint — most changes ship from the dashboard in minutes. Engineering time is reserved for the things that actually need it.
-
EU-native, from KYC to settlement
Underwriting, licensing and settlement all sit in the European Union. Data lives in the EU. Support and boarding managers speak the regulator's language, not a call-centre script.
What sits inside BazPay business merchant services
Six product surfaces, one platform. Turn any of them on from the dashboard — no new contract, no second-vendor procurement.
-
Rails
Acquiring and processing
Direct EU acquiring on a named MID with card, wallet and APM processing bound to it. One authorisation surface for every rail.
- Cards
- Apple Pay
- Google Pay
- iDEAL
- BLIK
- Bancontact
-
Checkout
Hosted and embedded checkout
Drop-in checkout, hosted fields and full hosted-page flows. Each keeps PAN outside your servers and inside merchant SAQ A scope.
- Drop-in
- Hosted fields
- Hosted page
-
Billing
Recurring billing
Plans, mandates, dunning and MIT exemptions on stored credentials. Renewals stay on card-on-file or SEPA Direct Debit.
- Plans
- Dunning
- SEPA DD
-
Payouts
Payouts and settlement
SEPA and SEPA Instant participation for merchant payouts, plus SWIFT and push-to-card on approved corridors.
- SEPA
- SEPA Instant
- SWIFT
-
Risk
Fraud controls and disputes
Inline rule engine, 3-D Secure 2.2 with exemption logic, pre-dispute alerts and evidence assembly — inside the same platform.
- Rules
- 3DS 2.2
- Dispute defence
-
Insight
Reporting and analytics
Interchange++ statements, real-time decline data, cohorted approval rates and CSV exports for the finance stack.
- Interchange++
- Real-time
- CSV exports
Deep-dives live on merchant acquiring, card and APM processing, hosted checkout products, recurring billing, anti-fraud controls and payouts.
From boarding to first settlement
Six stages sit between the KYC pack and a settled euro on your bank account. Each stage is visible in the dashboard and each stage change fires a signed webhook.
-
Board
KYC, beneficial-owner review and low-risk merchant underwriting. Sandbox keys issued at day one.
-
Configure
Choose your MCC, descriptor, payment methods and payout schedule from the dashboard.
-
Integrate
Ship on the REST API or drop in a maintained plugin. Idempotent requests, signed webhooks.
-
Go live
Live credentials unlock after the compliance review closes. First charge posts against your named MID.
-
Operate
Ops team runs the review queue and refunds. Finance team reconciles interchange++ statements.
-
Iterate
Change fraud thresholds, add payment methods and edit descriptors without an engineering release.
Unified platform vs a stitched stack
The comparison below sits at the level teams care about after go-live: how many logins they carry, whether their bill reconciles cleanly and how long a rule change takes.
| Dimension | BazPay (unified platform) | Stitched multi-vendor stack |
|---|---|---|
| Contract | One MSA with BazPay | Separate acquirer + gateway + billing + fraud vendors |
| MID structure | Named MID per merchant | Shared or aggregated MID |
| Software surface | One dashboard, one API, one webhook stream | Multiple portals, separate APIs, disparate webhooks |
| Reporting | Interchange++ line detail | Blended-rate summary |
| Rule changes | Dashboard, live on next order | Ticket to the reseller |
| Team access | Role-based, one login | Shared credentials across vendors |
Rate cards and settlement structure on the pricing page.
The software features every merchant services team leans on
All of the primitives below ship on the standard integration. Feature-gating on the platform is limited to add-on services, not to the operational tools your team needs on day one.
-
Unified dashboard
Payments, disputes, payouts, fraud rules and API keys under one login. Role-based access for ops, finance, dev and executive users.
-
REST API
One endpoint per resource. Idempotent create requests, cursor pagination and a stable versioning contract.
-
Signed webhooks
HMAC-SHA256 signature and timestamp on every event. Replay from the dashboard when your service was down.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment inside your checkout — merchant SAQ A stays intact.
-
Gateway-side vault
Store credentials once, charge them across upgrades, renewals and one-clicks. Portable if you ever change stack.
-
3-D Secure 2.2 engine
PSD2 SCA with automatic exemption logic — TRA, low value, MIT, trusted beneficiary.
-
Interchange++ statements
Scheme fees, interchange and gateway margin broken out on every settled line for reconciliation.
-
Role-based access
Fine-grained permissions per team and per API key, with SSO on request. Every action is audit-logged.
One API for the whole merchant services processing surface
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. Every state change fires a signed webhook — the same event stream powers your ledger, your CRM and your data warehouse.
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 and any exemption applied. Read the full schema in the API reference and the sample handler code in the developer docs.
Who we underwrite for online merchant services
The BazPay merchant services industry footprint is deliberately narrow. Four merchant profiles with predictable chargeback ratios and clean AML posture — that is the book that stays healthy over time.
-
E-commerce sellers
DTC brands and multi-country storefronts running WooCommerce, Magento 2, PrestaShop or Shopware. Named MID, local acceptance, EU settlement.
-
Subscription software
SaaS teams billing monthly and annual plans with saved cards, dunning and MIT exemptions on renewals.
-
Professional services
Agencies, consultancies and B2B service firms invoicing recurring retainers with higher-ticket cards and SEPA options.
-
Digital publishers
Membership sites, paywalled media and single-issue purchases with clean SKU-level reporting.
Out of scope: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.
Security and compliance signals
The merchant services platform runs inside a PCI DSS Level 1 environment assessed 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. Data is resident inside the European Union.
- PCI DSS Level 1
- Annual assessment on the gateway and acquiring environment
- Merchant SAQ A
- Hosted fields and gateway vault keep card data outside your stack
- PSD2 SCA
- 3-D Secure 2.2 with automatic exemption engine
- 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 are merchant services, and what does BazPay provide?
Merchant services are the contractual and technical arrangement that lets a business accept, process and reconcile payments. BazPay provides that as one platform — merchant acquiring, payment gateway, hosted checkout, recurring billing, fraud controls, payouts and reporting — for EU low-risk merchants on the platform operated by NEWERA PAYMENT TECHNOLOGIES LTD.
How is this different from just a payment gateway?
A gateway alone moves the authorisation message. A merchant services platform pairs the gateway with the acquirer, the risk engine, the vault, the billing scheduler and the settlement path. With BazPay it is one contract, one MID and one API — not a gateway stitched to a separate acquirer, a separate fraud vendor and a separate billing tool.
Who is BazPay's merchant services online offering built for?
EU low-risk businesses: e-commerce sellers, subscription software firms, professional-services companies and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and it is not a marketplace of third-party PSPs.
How do I start merchant services with BazPay?
Send us a short business description, expected volumes and the countries you sell into. Boarding runs on standard EU low-risk KYC — legal-entity docs, beneficial-owner evidence and business-model detail. Sandbox credentials are issued at the start of the process so integration work can run in parallel with underwriting.
Does BazPay act as both the merchant services acquirer and the gateway?
Yes. BazPay operates the payment gateway and the EU acquiring relationship on the same platform. That removes the reseller layer that would otherwise sit between the merchant and the network, and it keeps chargeback attribution, interchange++ reporting and settlement all inside one system.
How does merchant services payment processing look at run time?
Your checkout posts a charge to one REST endpoint. Our platform scores it, authenticates it if 3-D Secure 2.2 is required, routes it to the scheme, captures on your rules and posts a signed webhook when the state changes. Funds reconcile per scheme cycle and settle into your EU IBAN with an interchange++ statement.
Which platforms plug in directly?
Maintained plugins for WooCommerce (WordPress), Magento 2 / Adobe Commerce, PrestaShop and Shopware 6. Each covers checkout, refunds, capture, webhooks and recurring billing. Full plugin listing lives on the integrations page; anything outside that list runs on the REST API.
How is pricing structured?
Card volume is billed on interchange++ — scheme fees, interchange and the BazPay margin appear on every settled transaction. Local payment methods are billed on their own line rather than blended. The current schedule sits on the pricing page and is confirmed in the merchant services agreement.
Bring your merchant services under one roof
Share your business model, expected volumes and target markets. A payments specialist will confirm boarding fit, likely rate structure and settlement corridor within one working day. Sandbox keys are self-service so integration work can start in parallel — see also real-time analytics and open banking. Related pages: merchant acquiring, how BazPay compares as a payment provider, the network payment gateway and processing a payment.