A unified online payment platform for growing businesses.
BazPay is an online payment platform that unifies acceptance, recurring billing, mass payouts, fraud controls and reporting behind one REST API. Product, engineering and finance teams build on top of it instead of stitching several narrow vendors together.
Direct regional acquiring, SEPA Instant settlement into your named settlement account, authentication with exemption logic and interchange++ line-level reporting. Sandbox keys and webhook secrets are self-service from the first sign-in.
Why teams pick a payment platform over a stack of vendors
Four things stay true whether you handle a hundred euros a day or several million. They are the reasons product, engineering and finance teams stay on one platform after the first integration is live.
-
Build on top, don't stitch underneath
Acceptance, recurring billing, mass payouts, fraud controls and reporting share one API surface and one signed-webhook stream. Product teams ship features on the platform instead of integrating five vendors.
-
Open API, open primitives
Every capability is exposed through the same REST endpoints our own dashboard uses. There is no private tier of features and no marketing-list of enterprise-only APIs — the platform is uniformly available.
-
One tenancy, many products
One key covers the whole platform. New product areas — a new checkout, a new payout run, a new subscription tier — turn on with a request flag or a dashboard toggle, keyed to the same merchant identity.
-
EU, UK and Commonwealth by construction
Direct regional acquiring, SEPA Instant settlement into your named settlement account, GDPR-compliant data handling and authentication. The platform is designed for merchants that operate inside the EU, the UK, Australia, Canada and New Zealand, not adapted from a US-first product.
What lives inside the e-payment platform
Four capability areas share the same API, the same signing secret and the same webhook envelope. You wire the platform in once and switch new areas on as your business needs them.
-
Acceptance
Cards, wallets and APMs
Visa, Mastercard, Cartes Bancaires, eftpos plus Apple Pay, Google Pay and local payment methods on one endpoint. Every rail returns the same canonical charge object.
- Visa
- Mastercard
- Apple Pay
- Google Pay
- iDEAL
- Bancontact
-
Billing
Recurring and metered
Card-on-file with network-tokenised refresh, dunning-aware retries and MIT exemptions on renewals. Metered and hybrid plans live on the same subscription object.
- Subscriptions
- Trials
- Metered
-
Payouts
Mass payout solutions
One-to-many payouts to bank accounts or eligible cards, from the same settlement balance you collect into. Batch files supported for larger runs on approved corridors.
- SEPA Instant
- SEPA Instant
- Card push
- Batch
-
Reporting
Real-time platform data
Approval quality, decline reasons, fraud verdicts, disputes and settlement lines visible within seconds — with interchange++ line detail for every card charge.
- Analytics
- Interchange++
- CSV export
Payment-method depth on card and APM processing. The acquiring contract itself on merchant acquiring. The network connectivity layer on network payment gateway. See also online payment services, payment processing platforms and payment processors.
Building on the platform
Six stages describe how teams typically go from a first sandbox key to production. Each stage is trackable in the dashboard and each stage change fires a signed webhook.
-
Provision
One key covers the sandbox and later the live environment. The dashboard exposes the same objects the API returns.
-
Model
Represent your customers, subscriptions, orders and payout beneficiaries as first-class objects on the platform.
-
Accept
Post a charge against any rail — card, wallet, APM or account-to-account — with one request shape.
-
Automate
Fraud rules, retry cadences, dunning and payout schedules run inside the platform, configured from the dashboard.
-
Report
Signed webhooks and CSV exports feed your finance and product stacks. Every event is idempotent and replay-safe.
-
Extend
New markets, new checkout surfaces or a new payout corridor add through the same API — no re-integration.
One platform vs a stack of narrow vendors
Buying a gateway, a subscription biller, a payout tool and a fraud engine separately keeps every vendor focused on one job — and multiplies the integration and reconciliation load on your side. A payment platform as a service collapses that surface.
| Dimension | BazPay (unified platform) | Vendor-per-capability stack |
|---|---|---|
| Surface | One unified REST API | Vendor-per-capability toolchain |
| Tenancy | Named MID per merchant | Shared MID or aggregated pool |
| Extensibility | Open primitives, uniform tier | Feature gating by contract size |
| Event model | Signed webhooks, one signature scheme | Different envelopes per vendor |
| Reporting | Interchange++ line detail on the platform | Blended summary per vendor |
| Fraud & billing | Native to the platform | Bolt-on subscriptions |
Rate cards on the pricing page. Vertical bundles on the packaged payments solutions page.
Features exposed by the open payment gateway
Every capability below is available on the standard integration. Turn features on with a request flag or a dashboard toggle — there is no enterprise-tier gate on the primitives.
-
Unified charge object
One object shape across cards, wallets, APMs and A2A rails. Your integration reads a unified payment platform as one API, not five.
-
Hosted fields and drop-in UI
Card entry served from our PCI environment inside your checkout, or a drop-in component that renders the full flow.
-
Recurring billing
Subscriptions with trials, proration, dunning and mid-cycle changes — first-class primitives on the platform.
-
Mass payouts
Fan out payments to many beneficiaries in one API call or as a signed batch file. Idempotency keys prevent duplicate credits.
-
Rule-driven fraud engine
Score every order inline, configure rules from the dashboard, and let PSD2 exemption logic run automatically.
-
Signed webhooks
HMAC-signed, replay-protected events for every acceptance, billing, payout and dispute state change.
-
Idempotent API
Retry-safe create requests keyed to your idempotency header. A network blip never becomes a double charge or a double payout.
-
Interchange++ reporting
Every settled card transaction breaks out interchange, scheme fees and platform margin for finance-team reconciliation.
One API for acceptance, billing and mass payouts
Every capability on the platform speaks the same request shape. Create a charge, create a subscription, create a payout — the endpoints share idempotency semantics, the same signing secret and the same signed-webhook envelope, so your engineering team maintains one integration surface across the whole platform.
POST /v1/payouts/batches
Idempotency-Key: 8f1c-2b3a-9e4d
{
"reference": "payouts-2026-08-03",
"currency": "EUR",
"items": [
{ "beneficiary": "ben_5F9k", "amount": 12000, "rail": "ideal" },
{ "beneficiary": "ben_5A2c", "amount": 4500, "rail": "ideal" },
{ "beneficiary": "ben_5D1x", "amount": 8750, "rail": "ideal" }
]
}The response returns a batch object with a per-item status. Read the full schema in the API reference.
Where teams build on the platform
The platform is scoped to merchants across the EU, UK, Australia, Canada and New Zealand. Four use cases already run on it — each shows a different combination of the primitives above.
-
E-commerce and DTC
One platform for storefronts on Shopware, Magento 2, WooCommerce or PrestaShop. Local card and APM acceptance across our markets on one integration.
-
Subscription software
SaaS teams billing monthly and annual plans with card-on-file renewals, dunning-aware retries and MIT exemptions.
-
Event ticketing
An event payment platform for conferences, workshops and paid trainings. High-throughput sales windows handled with idempotent requests.
-
Marketplace-style payouts
Pay affiliates, contributors or professional-services vendors on schedule using mass payout solutions from the same balance you collect into.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a consumer wallet, social payment app or marketplace of third-party PSPs.
Security and compliance signals
The 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. Authentication runs on every card charge with automatic exemption logic where the rules allow.
- PCI DSS Level 1
- Platform environment assessed annually
- Merchant SAQ A
- Hosted fields and vaulting 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 and beneficiary payouts on approved corridors
Questions merchants ask first
What kind of online payment platform is BazPay?
BazPay is a payment-platform-as-a-service operated by NEWERA PAYMENT TECHNOLOGIES LTD. It unifies acceptance, recurring billing, mass payouts, fraud controls and reporting behind one REST API and one dashboard, so a merchant can build on top of the platform instead of stitching several narrow vendors together.
How does a unified payment platform differ from a payment gateway?
A gateway typically covers acceptance only. A unified payment platform exposes acceptance, billing, payouts, fraud and reporting through the same API surface, with the same signing secret and the same webhook envelope. The integration and reconciliation load on your team is much smaller.
Is BazPay an open payment platform?
The API is open in the sense that every primitive is uniformly available — there is no private tier of endpoints and no marketing-list of enterprise-only features. Documentation, sandbox keys and webhook events are self-service. BazPay is not an open payment protocol or public-good scheme; it is a commercial platform run by a locally registered entity.
Can I use BazPay as a business payment platform for international sales?
Yes. Card acquiring runs on our regional licence, and the card networks are international — cards issued outside the region authorise on the same contract and settle into the same balance. Presentment currencies cover EUR plus more than twenty others, so a regional merchant reaches international shoppers through one international payment platform.
Do you support event payment systems?
Yes, for conferences, workshops and paid trainings — ticket sales, delegate registration, sponsor invoicing and refunds all sit inside the platform. High-throughput sales windows are protected by idempotent create requests and the fraud engine's velocity rules.
How do mass payouts work on the platform?
Post individual payouts through the API or submit a signed batch file with beneficiaries and amounts. Payouts settle on instant rails or, on approved corridors, SEPA Instant. Every payout event fires a signed webhook keyed to your idempotency header, so retries never duplicate a credit.
Is BazPay a social payment platform for consumer-to-consumer transfers?
No. BazPay is a business payment platform for merchants across the EU, UK, Australia, Canada and New Zealand, not a consumer wallet or peer-to-peer social payment app. Shoppers pay merchants; the platform is designed around that direction of flow.
Which merchant profiles fit this online payment platform?
Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses, event organisers and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and does not act as a marketplace of third-party PSPs.
Build on the payment platform today
Open a sandbox and post your first charge, subscription or payout in the same hour. Prefer a walkthrough? A payments specialist can map anti-fraud controls, recurring billing, payouts and real-time analytics against your business.