Payment gateway for online business, on one integration
BazPay is a regional payment gateway that connects your website to card acquiring, open banking, payouts, recurring billing and fraud checks through one REST API. You wire it once. Then you switch products on as your business needs them.
Built for merchants in the EU, UK, Australia, Canada and New Zealand — e-commerce sellers, subscription software companies and professional-services firms. Pricing is published. Underwriting scope is deliberately narrow. Operated by NEWERA PAYMENT TECHNOLOGIES LTD, a locally registered entity.
What the payment gateway can do
Each product below has its own page with the technical detail. They all run off the same account, the same keys and the same webhook stream.
-
01Acquiring
Card and APM processing
Take Visa, Mastercard and every major regional wallet through one API contract. Routing scores each authorisation against your own history, then picks the connection most likely to approve. Soft declines get re-tried before the shopper sees an error.
- Visa
- Mastercard
- Apple Pay
- Google Pay
-
02Pay by bank
Open banking
The shopper approves in their own banking app. Funds move on SEPA Instant rails and land in seconds. No card, no token, no interchange.
- SEPA Instant
- Bancontact
- BLIK
- EPS
-
03Money out
Payouts
Pay out of the same balance you collect into. Send an instant credit transfer to a bank account, or push funds straight to a card. Batch files work too.
- SEPA Instant
- Card push
- Batch
-
04Subscriptions
Recurring billing
Plans, trials, proration and dunning run on the gateway. Failed renewals retry on a schedule you set. Mandates and stored credentials stay in our vault.
- Plans
- Dunning
- Mandates
-
05Risk
Anti-fraud
Rules and device signals score each order before it reaches the acquirer. You set the thresholds. 3-D Secure 2 steps in only when the risk earns it.
- Rules
- 3-D Secure 2
- Velocity
-
06Front end
Checkout products
Hosted pages, drop-in fields or a full server-to-server flow. Hosted fields render inside our PCI scope, so no card number ever touches your stack.
- Hosted page
- Drop-in
- S2S
-
07Reporting
Real-time analytics
Watch approval rates, decline reasons and settlement by rail as they happen. Filter by BIN country, scheme or currency. Export any view as CSV.
- Decline codes
- Settlement
- CSV
-
08Build
API reference
One REST API covers every product above. Keys, sandbox data and webhooks are self-service from day one. No sales call needed to start.
- REST
- Webhooks
- Sandbox
How to implement the payment gateway on your website
An online payment gateway integration should be short, testable and reversible. Here is the shape of a BazPay implementation, whether you land on hosted pages or run the full server-to-server flow.
-
Choose the checkout surface
Redirect to a hosted page, embed our drop-in fields, or call the API server-to-server. Hosted fields keep the card number inside our PCI scope, so your website never handles PAN data.
-
Wire one REST endpoint
Create a Payment Intent, pass amount and currency, return the client secret to your front end. Idempotency keys are respected on every write, so a retried request cannot double-charge a shopper.
-
Verify signed webhooks
Each event is signed with your endpoint secret using HMAC. Your server verifies the signature, then updates the order status. Duplicate deliveries are safe to ignore on the idempotency key.
-
Turn on 3-D Secure 2.2
PSD2 exemption logic is applied server-side. Clean transactions run frictionless; risky orders step up to a challenge in the issuer app. You do not have to code the exemption rules yourself.
Sample code, endpoint schemas and event payloads are in the API reference, and shipped as checkout product primitives. Buyer-side context on payment processors, payment services and transaction processing.
Gateway payment services and processing
The services listed below are the operational spine of the gateway. Every product pillar above depends on them, and every merchant on our platform gets them by default.
-
Card acquiring on interchange++
Interchange, scheme fees and the acquirer margin appear as separate lines on every settlement report. No blended pricing, no month-end surprises.
-
Gateway-side card vault
Card numbers are tokenised at first entry and stored in our PCI environment. Your website receives a token; charges, refunds and MITs all reference it.
-
Signed webhooks and retries
Every event carries an HMAC signature and a monotonic ID. Failed deliveries retry on an exponential schedule up to 72 hours, so a five-minute outage never loses a payment record.
-
Real-time decline data
Every authorisation response returns the raw scheme code, the issuer response and a normalised reason. Your team sees exactly why a shopper was turned away.
-
SEPA and SEPA Instant
Collect by direct debit, refund to settlement account, or push instant credit transfers back to a shopper's bank in seconds. All from the same balance you settle into.
-
Idempotent API
Send the same Idempotency-Key twice and the second call returns the first response byte-for-byte. Safe to retry on any network error without a duplicate charge.
See real-time analytics for the reporting side, payment fraud prevention for the risk layer that sits in front of every authorisation, and merchant acquiring for the direct regional contract the gateway settles into. Deeper tours of the same stack live on payment gateway services, online payment services and the electronic payment system primer.
A payment gateway service provider inside regional rails
We hold PCI DSS Level 1 on the gateway side. Hosted fields render inside our scope, so a card number skips your stack entirely. Your yearly return stays at SAQ A. That is the smallest scope a seller can hold.
Vaulting is gateway-side only. Stored credentials, mandates and network tokens live with us, and travel with you if you add a second rail. Authentication is applied server-side, with exemption logic that keeps clean baskets frictionless.
| Card data storage | Gateway-side vault only | never your servers |
|---|---|---|
| Your annual return | SAQ A | smallest scope |
| Our certification | PCI DSS Level 1 | audited yearly |
| Strong authentication | 3-D Secure 2.2 certified | Authentication |
| Data handling | GDPR-compliant | Regional processing |
| Operator | NEWERA PAYMENT TECHNOLOGIES LTD | Regional-registered entity |
Rails, methods and settlement in one payment gateway online
One contract covers all four rails. Pick the ones your shoppers already use, and drop the rest. Adding a new method later is a dashboard toggle, not a new integration.
| Rail | Methods | Settlement | Card scope |
|---|---|---|---|
| Card acquiring | Visa, Mastercard, Cartes Bancaires, eftpos | Scheme cycle | SAQ A |
| Wallets | Apple Pay, Google Pay | Scheme cycle | SAQ A |
| Open banking | iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac | SEPA Instant | No card data |
| Payouts | Instant credit transfer, card push | Same balance | No card data |
Want the full method list for your markets? See payment methods for coverage by country.
Website gateway plugins for the regional stack
If your store already runs on WooCommerce, Magento 2, PrestaShop, Shopware or OpenCart, the payment gateway drops in as a signed plugin. If it runs on something else, the REST API is the same one those plugins use.
-
WooCommerce
WordPress plugin, hosted fields
Set up on WooCommerce -
Magento 2
Adobe Commerce module
Set up on Magento 2 -
PrestaShop
Module for 1.7 and 8.x
Set up on PrestaShop -
Shopware
Shopware 6 plugin
Set up on Shopware -
OpenCart
Extension for 3.x and 4.x
Set up on OpenCart -
Custom API
REST for anything else
Set up on Custom API
A full directory of platform work and partner links lives on the integrations index.
Who runs on the gateway
The gateway is shaped for three merchant types. Each gets the same API surface, and a settlement flow that matches how their business books revenue.
-
E-commerce checkout
One gateway on the storefront handles cards, wallets and pay-by-bank. Guest checkouts and returning shoppers share the same vault, so a saved card works across sessions and devices.
-
SaaS and subscriptions
Recurring plans, trials, proration and dunning are gateway-native. Failed renewals retry on a schedule you set. Network tokens keep charges alive when a shopper's card is reissued.
-
Professional services
One-off invoices go out as a hosted payment page link. Cards and open banking clear the same day. Your accountant reconciles from a single CSV export.
From sandbox to live traffic
Most sellers move in days, not months. It is a self-service path from the first key.
-
Open a sandbox
Sign up and get test keys at once. Full API access, no demo call, no contract first.
-
Drop in a plugin or call the API
Pre-built plugins cover the major regional shop platforms. Prefer code? The REST endpoints are the same ones our plugins use.
-
Send test traffic
Replay approvals, declines and 3-D Secure 2 flows against sandbox data. Webhooks fire exactly as they will in production.
-
Submit underwriting
We underwrite a defined list of sellers. That focus is why approval rates stay steady across our book.
Payment gateway questions, answered
Common questions from merchants comparing gateways, developers scoping the integration, and finance teams reviewing scope and settlement.
-
What is a payment gateway and why does an online business need one?
A payment gateway is the piece of software that carries card and bank data from your website to an acquiring bank, and returns the authorisation result. Without a gateway, an online business cannot legally take card payments. BazPay is a payment gateway for online business that also handles vaulting, 3-D Secure 2.2 and settlement reporting in the same product.
-
How do I implement a payment gateway on my website?
Open a BazPay sandbox, pick a checkout surface (hosted page, hosted fields, or server-to-server), create a Payment Intent from your backend, and verify the signed webhook that confirms the charge. Our platform plugins do this in one install; a custom stack does it in a few dozen lines against the REST API. See the API reference for the exact endpoints.
-
Which industries does the BazPay payment gateway service support?
BazPay is designed for merchants in the EU, UK, Australia, Canada and New Zealand — e-commerce sellers, subscription software companies and professional-services firms. We do not underwrite adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM businesses.
-
How is the payment gateway priced?
Card processing runs on interchange++, so interchange, scheme fees and the acquirer margin appear as separate lines on every settlement report. Open banking, payouts and recurring billing carry their own per-transaction fees. Current rates and any monthly minimums are published on the pricing page.
-
What does the gateway do about PCI compliance?
BazPay holds PCI DSS Level 1 on the gateway side. Hosted fields and hosted pages render inside our PCI scope, so card numbers never reach your servers. That keeps your annual return at SAQ A, the smallest scope a merchant can hold.
-
Which payment methods can the gateway accept for a website?
The same integration accepts Visa, Mastercard, Cartes Bancaires, eftpos, Apple Pay, Google Pay, iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac. New methods roll out to every merchant on the same REST endpoints; you do not need a new integration to enable one.
-
How fast can a website go live with the gateway?
Sandbox access is available the minute you sign up. A shop on WooCommerce, Magento 2, PrestaShop or Shopware can be taking test traffic in an afternoon. Production traffic depends on underwriting; merchants in the EU, UK, Australia, Canada and New Zealand typically clear it in days.
-
Are webhooks reliable enough to rely on for order status?
Every event is signed with your endpoint secret using HMAC, carries a monotonic event ID, and retries on an exponential schedule for up to 72 hours if your endpoint is unreachable. Your server verifies the signature and updates the order idempotently.
More on scope and underwriting on the general FAQ and the about page. Related product families: the network payment gateway layer, the vertical payments solutions bundles, the underlying payment infrastructure and the digital-goods angle on the payment gateway for digital goods. Starting from zero? See the accept online payments getting-started guide, or integrated payment solutions if you are wiring payments inside an existing product. Bank rails on Single Euro Payments Area processing; German method up close on iDEAL payments; broad-coverage view on payment acceptance. Vertical fits: fintech payment solutions. Role explainer on issuing and acquiring.
Add the payment gateway to your website today
Open a sandbox and call the API in the same hour. Prefer to talk it through first? A payments specialist can walk your rails, your methods and your platform with you.