A payment provider built as one integrated platform.
BazPay is a direct EU payment provider for low-risk merchants and fintech products. Gateway, acquiring, fraud rules, recurring billing and payouts belong to the same platform, sit behind one REST API and reconcile against one dashboard.
Operated by NEWERA PAYMENT TECHNOLOGIES LTD, boarding is scoped to EU low-risk sellers: e-commerce, subscription software, professional services and digital publishers. That focus is deliberate — it is why the platform stays stable and the reporting stays clean.
Why merchants choose BazPay as their payment provider service
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 payment provider for the whole flow
Gateway, acquiring, fraud rules, payouts and recurring billing belong to the same platform. You sign one contract, integrate one REST API and reconcile against one dashboard.
-
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 merchants' traffic.
-
Interchange++ transparency
Scheme fees, interchange and BazPay's margin appear on every settled transaction. Finance teams reconcile against the source, not against a blended rate.
-
Built for fintech-grade integration
Idempotent requests, signed webhooks and a stable versioned API. The primitives your engineering team already expects from a payment system provider.
What the platform ships in one contract
Four capability areas make up the BazPay payment system provider stack. Turn any of them on from the dashboard — no separate boarding, no new integration.
-
Acceptance
Card and APM processing
Cards, device wallets and EU local payment methods share one charge object. A single integration covers every rail.
- Visa
- Mastercard
- Wallets
- EU APMs
-
Acquiring
Direct EU acquiring
Contract directly with BazPay as an EU acquiring institution. No reseller sits between you and the network.
- Named MID
- Scheme membership
- Interchange++
-
Risk
Fraud rules and 3-D Secure 2
Score every order in real time. Step up to 3-D Secure 2 only when the risk profile earns it.
- Rule engine
- Velocity
- PSD2 SCA
-
Money out
Payouts and recurring billing
Settle to your EU IBAN and pay beneficiaries. Renew subscriptions on stored credentials with dunning support.
- SEPA
- SEPA Instant
- Card-on-file
Depth on each area: card and APM processing, merchant acquiring, anti-fraud controls, payouts and recurring billing.
From boarding to first settlement
Eight stages sit between the KYC pack and a settled euro on your bank account. Each stage is visible in the dashboard and each state change emits a signed webhook.
-
Board
KYC, ownership and business-model review. Low-risk merchants complete boarding in days, not weeks.
-
Provision
A named MID opens with the schemes. Sandbox and live API keys are issued for your entity.
-
Integrate
Hosted fields, one REST endpoint and a signing secret. Plugins cover common commerce stacks.
-
Accept
Cards, wallets and local methods run through one charge object. The response shape never changes.
-
Screen
The rule engine scores every order before authorisation and stamps the verdict on the payment.
-
Authorise
The charge posts against your MID with the SCA result and CAVV bound to the transaction.
-
Settle
Funds reconcile per scheme cycle and arrive in your EU IBAN with an interchange++ statement.
-
Report
Signed webhooks and real-time analytics feed your ledger, your CRM and your finance dashboard.
One integrated provider vs stitched-together vendors
The alternative to a single payment provider is a stack of merchant service providers, fraud tools and payout partners glued together. It is fast to assemble and expensive to maintain. The comparison below shows where each model earns its keep.
| Dimension | BazPay (one provider) | Multi-vendor stack |
|---|---|---|
| Contract | One direct contract | Contracts per PSP and per acquirer |
| MID structure | Named MID per merchant | Shared MID pool |
| Reporting | Interchange++ line detail | Blended-rate summary |
| Fraud rules | Inline engine, per-merchant tune | Bolt-on tool, separate contract |
| Payouts | SEPA / SEPA Instant to your IBAN | Delayed aggregated payouts |
| Vendor count | One | Two to four |
| Reason-code data | Real-time via webhook | Batch export |
Rate structure and settlement details on the pricing page.
Platform features engineered into the API
Every capability below is on the standard integration. No enterprise-tier gate on the primitives, no bolt-on module for signed webhooks or hosted fields.
-
Hosted fields
Card, expiry and CVC inputs served from BazPay's PCI environment inside your checkout — SAQ A scope for your entity.
-
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
Frictionless flow first, challenge only when your rules or the issuer require it. Exemption logic runs automatically.
-
Rule engine
Compose triggers on 30+ enriched fields. Publish changes from the dashboard, no engineering release.
-
Idempotent REST API
Retry-safe create requests keyed to your idempotency header. A network blip never becomes a double charge.
-
Signed webhooks
HMAC-signed, replay-protected events for every state change: authorise, capture, refund, dispute, payout.
-
Interchange++ reporting
Every settled transaction breaks out interchange, scheme fees and acquirer margin for line-level reconciliation.
-
Real-time decline data
Reason codes surface in the dashboard and via webhook within seconds — feed them into your dunning system.
One REST API for the whole flow
The charge object is the unit of work. One endpoint authorises, captures and refunds. The payment_method field selects the rail — card, wallet or EU APM. Idempotency keys make retries safe. Signed webhooks confirm every state change asynchronously.
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 MID it posted against, the risk verdict and any SCA exemption applied. Read the complete schema in the API reference.
Who this payment provider is built for
The platform is tuned for four merchant profiles with predictable chargeback ratios and clean AML posture. If your model fits one of them, boarding is straightforward.
-
E-commerce merchants
DTC brands and multi-country storefronts on Shopware, Magento 2, WooCommerce or PrestaShop needing a single provider for cards and EU APMs.
-
Subscription software
SaaS teams billing monthly and annual plans with saved-card renewals, MIT exemptions and dunning-aware retries.
-
Professional services
Agencies, consultancies and B2B service firms invoicing higher-ticket retainers with named-payer trust lists.
-
Fintech and embedded flows
Vertical fintech products that need a payment provider for fintech workloads: hosted checkout, tokenised card-on-file, signed webhooks and stable versioning.
Out of scope: adult, gambling, CBD, nutraceutical, forex, CFD, crypto and altcoin processing, debt-collection and MLM. BazPay is not a marketplace of third-party PSPs.
Security and compliance signals
The provider 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 decision-makers ask first
What is a payment provider, and where does BazPay sit?
A payment provider is the licensed entity that lets a business accept payments online — issuing merchant credentials, moving the authorisation to the schemes and settling funds back. Some providers are pure gateways in front of another bank; some are aggregators; BazPay is a direct EU payment provider operated by NEWERA PAYMENT TECHNOLOGIES LTD, combining acquiring, processing, fraud tooling and payouts on one contract.
How is a payment provider service different from a merchant service provider or reseller?
A traditional merchant service provider often resells a downstream acquirer under an aggregated MID, which delays settlement and blurs reporting. BazPay is the acquirer for its EU book, so you get a named MID, interchange++ line-level reporting and EU settlement into your own IBAN. There is no third party sitting between you and the network.
Do you support international payment provider use cases?
BazPay's acquiring licence is European. Cards issued outside the EU authorise on the same contract and settle into the same EU balance, so multi-country e-commerce with international cardholders is a standard scenario. Cross-border corridors for merchant payouts are approved case by case at boarding.
Is BazPay a suitable payment provider for fintech products?
Yes, for vertical fintech products in the low-risk profile — SaaS with in-product billing, embedded checkout, marketplace-style seller flows within a single legal entity. The API is idempotent, webhooks are signed, versioning is stable and the platform ships hosted fields, card vaulting and PSD2 exemption logic out of the box.
Do you offer an altcoin payment gateway, altcoin payment processor or altcoin payment solution?
No. BazPay is a euro-denominated, EU low-risk payment provider. It does not process altcoin, cryptocurrency, stablecoin or wallet-to-wallet transfers, and it does not act as an altcoin payment provider for any merchant category. Card, wallet, EU APM and open-banking rails only.
Do you provide payment systems in healthcare — for example a point-of-service health plan payment system?
BazPay serves e-commerce, subscription software, professional services and digital publishers. It is not sold as a healthcare-billing or point-of-service payment system for health plans, and it is not certified for clinical or claims-processing workflows. Healthcare merchants that fit the low-risk e-commerce or SaaS profile can still board on standard terms.
Can I become a merchant service provider by reselling BazPay?
No. BazPay is not a white-label marketplace of third-party PSPs and does not board resellers or sub-aggregators. Merchants contract with BazPay directly. If you operate a platform and need to charge on behalf of your own single legal entity, that is a standard integration — talk with sales about the boarding fit.
Which merchant categories does BazPay board?
EU low-risk merchants: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. Out of scope: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.
Start the provider conversation
Share your business model, 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 — see also hosted checkout products and real-time analytics. Related: merchant acquiring, merchant services, the network payment gateway and payment orchestration.