Payment services for EU, UK and Commonwealth merchants.
BazPay is a direct regional acquirer and payment gateway. Every service a merchant needs to run online payments — card acceptance, subscriber billing, payouts, fraud controls and reporting — is delivered under one master agreement, on one platform, with one API.
Built for e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. Underwriting scope is deliberately narrow. Approvals, settlement and dispute data belong to your merchant, not to a pooled reseller book.
Why merchants pick a single payment services provider
Four things stay true whether you take a hundred euros a day or several million. They are the reasons product, engineering and finance teams consolidate services onto one platform after boarding is done.
-
One provider, one contract
Acceptance, subscriber billing, dispute handling and reporting run under a single master service agreement. You do not sign separate MSAs, DPAs and pricing schedules for each capability.
-
Direct scheme relationship
Card acceptance clears on our own regional acquiring licence with a named MID for your entity. Chargeback attribution, decline data and settlement reporting belong to you, not to a pooled reseller book.
-
Services activated per merchant
Every service is toggled per merchant at boarding — payment methods enabled, billing model, payout cadence, fraud policy. Adjustments happen from the dashboard, not by ticket to a reseller.
-
One interface for every service
The REST API, the dashboard and the signed webhook stream cover every service. Your engineering team maintains one integration surface, not one per capability.
The service catalogue
Four service families cover most merchant needs. Activate the ones you use today and add the rest later from the dashboard — no new contract per service.
-
Acceptance
Card payment services and APMs
Direct card acquiring on our regional licence — Visa, Mastercard, Cartes Bancaires and eftpos — with Apple Pay, Google Pay and local payment methods behind the same charge object.
- Visa
- Mastercard
- Apple Pay
- Google Pay
- iDEAL
- Bancontact
-
Billing
Subscriber payment services
Recurring billing for one-off, subscription and metered plans. Card-on-file, network-tokenised renewals, MIT exemptions and dunning-aware retries built into the service.
- Card-on-file
- Dunning
- MIT exemptions
-
Payouts
Merchant payouts as a service
Payouts from the same balance you collect into. SEPA and SEPA Instant to your named settlement account by default, with SWIFT and push-to-card available on approved corridors.
- SEPA Instant
- SEPA Instant
- SWIFT
-
Risk
Fraud and dispute services
Inline scoring, PSD2 exemption logic and 3-D Secure 2.2 on every card charge. Dispute defence with early scheme alerts and evidence templates ready to submit.
- Rule engine
- 3-D Secure 2.2
- Dispute defence
Payment-method depth on card and APM processing. The acquiring contract itself on merchant acquiring. Sibling surface: online payment services, payment processors and gateway services.
From scoping to steady-state operations
Six stages sit between the first conversation and steady-state operations. Each stage is trackable in the dashboard and each stage change fires a signed webhook.
-
Scoping
A payments specialist maps the services you need against your business model, volumes, markets and existing stack.
-
Underwriting
KYC and merchant review against the acceptance criteria — documents, ownership and revenue model checked before boarding closes.
-
Provisioning
A named MID is opened with the schemes for your legal entity. Sandbox and live API credentials issued alongside dashboard access.
-
Integration
One REST endpoint, one webhook signing secret, hosted fields for the checkout. Maintained plugins cover four common regional commerce stacks.
-
Activation
Enable payment methods, billing model, payout cadence and fraud policy per merchant. Sandbox replays validate every path before go-live.
-
Operations
Real-time analytics, signed webhooks and interchange++ statements feed your finance stack. Adjust services from the dashboard as your book grows.
One services contract vs a stitched vendor stack
Buying acceptance, billing, fraud and payouts as separate services keeps every vendor focused on one thing — but it multiplies the integration and reconciliation load on your side. The comparison below explains where a consolidated payment services provider earns its keep.
| Dimension | BazPay (one provider) | Stitched vendor stack |
|---|---|---|
| Contract | One MSA with BazPay | Separate MSA per service vendor |
| Data model | One charge object across services | Different envelopes per vendor |
| MID structure | Named MID per merchant | Shared MID pool |
| Change control | Dashboard, effective on next order | Ticket routed to each provider |
| Reporting | Interchange++ line detail, one source | Reconcile across vendor summaries |
| Dispute evidence | 3-D Secure + signals auto-attached | Manual packet assembly per case |
Rate cards on the pricing page. Vertical bundles on payments solutions.
Features under the payment services agreement
Every capability below is available on the standard integration. Turn services on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives.
-
Direct card acquiring
Visa, Mastercard, Cartes Bancaires and eftpos on one regional acquiring contract with a named MID per merchant.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment inside your checkout, keeping your annual return at merchant SAQ A.
-
Gateway-side vault
Store credentials once, charge repeatedly across renewals and upgrades. Portable if you ever change stack.
-
3-D Secure 2.2 engine
Frictionless flow first; PSD2 exemption logic claims TRA, low-value, trusted-beneficiary and MIT where the rules allow.
-
Recurring billing service
Plans, trials, proration and dunning as a first-class part of the service. No separate biller with a token to keep in sync.
-
Fraud rule service
Allow, step-up, review and block verdicts you tune from the dashboard. Rule changes apply to the next order without an engineering release.
-
Signed webhooks
HMAC-signed, replay-protected events for every service — approval, decline, refund, dispute, payout — one signature scheme.
-
Interchange++ reporting
Every settled transaction breaks out interchange, scheme fees and gateway margin for line-level reconciliation.
One API for every payment service
The charge object is the unit of work across services. One endpoint authorises, captures and refunds — subscriptions and payouts share the same signing secret, idempotency contract and webhook envelope. Your engineering team maintains one integration surface, not one per service.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"payment_method": "card",
"customer": "cus_5F9k",
"subscription": "sub_2H9F...",
"capture": "auto",
"three_d_secure": "required_if_needed",
"metadata": { "plan": "pro_annual" }
}The response returns a canonical charge object with the authorisation code, the subscription reference and the exemption applied. Read the complete schema in the API reference.
Industries the services are built for
BazPay is a regional payment services provider with a defined acceptance list. Underwriting is scoped to four merchant profiles with predictable chargeback ratios and clean AML posture.
-
E-commerce sellers
Card and APM acceptance across our markets on one MID. Shopware, Magento 2, WooCommerce and PrestaShop plug in through maintained connectors.
-
Subscription software
Subscriber payment services for monthly and annual plans, with card-on-file renewals, dunning-aware retries and MIT exemptions.
-
Professional services
Higher-ticket B2B charges with named-payer trust lists, enforced 3-D Secure 2 over a ceiling you set and reconciliation into your finance stack.
-
Digital publishers
Membership renewals, single-issue purchases and paywall unlocks under one MID with clean reporting per SKU.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay does not act as a merchant of record or payment facilitator.
Security and compliance signals
The service platform runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields, network tokens and gateway-side vaulting keep your annual return at merchant SAQ A. Authentication runs on every card charge with automatic 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
- Authentication
- 3-D Secure 2.2 with automatic exemption logic on every card charge
- GDPR
- In-region data residency; DPA on request
- SEPA / SEPA Instant
- Direct participation for merchant payouts in supported corridors
Questions merchants ask first
What kind of payment services provider is BazPay?
BazPay is a direct regional acquirer and payment gateway operated by NEWERA PAYMENT TECHNOLOGIES LTD. Merchant payment services are delivered under one master agreement — card acceptance, subscriber billing, payouts, fraud controls and reporting sit on the same platform, one API and one dashboard.
How do BazPay's business payment services differ from a stitched vendor stack?
A stitched stack means separate contracts, separate data models and separate dashboards for acceptance, billing, fraud and payouts. BazPay ships those services on one platform, so the integration surface and reconciliation workload on your side are much smaller — one webhook signature scheme, one settlement report, one place to change policy.
Which merchant types can access these e payment services?
Merchants across the EU, UK, Australia, Canada and New Zealand: 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.
Does BazPay offer payment facilitation services or a merchant-of-record model?
No. BazPay is a direct regional acquirer with a named MID per merchant, not a payment facilitator or aggregator. Your legal entity holds the merchant contract, appears on the shopper's statement and remains the counterparty to the sale. Payment facilitation services, sub-merchant onboarding under a master MID and merchant-of-record functions are outside BazPay's scope.
How do the card payment services stay PCI compliant?
The acquiring and gateway environment holds PCI DSS Level 1, assessed annually. Hosted fields, network tokens and gateway-side vaulting keep card data out of your infrastructure — most integrations qualify for merchant SAQ A, the smallest merchant scope. Your engineering team never handles a live PAN.
What subscriber payment services are supported for recurring revenue?
Recurring billing native to the platform: plans, trials, proration, dunning-aware retries and MIT exemptions on renewals. Network-tokenised card-on-file keeps saved cards working after reissue, so renewals do not fail because the shopper never updated their card.
How are the services priced?
Card processing runs on interchange++, so interchange, scheme fees and the BazPay margin appear as separate lines on every settlement statement. Local payment methods, payouts, recurring billing and fraud tooling are priced per line — never blended into a headline card rate. Current schedules are on the pricing page.
How long does it take to activate the services?
Sandbox access is available immediately and the API is self-service from day one. Live traffic depends on underwriting — standard regional boarding typically completes in a few business days once KYC documents, beneficial ownership evidence and the business model description have been received. Integration work can proceed in parallel with underwriting.
Scope your services today
Share your business model and volumes. A payments specialist will confirm boarding fit and map the services — acceptance, recurring billing, payouts, fraud controls and reporting — within one working day. The underlying software layer sits on the network payment gateway platform.