Payment processing for online business, built to drop into your stack.
BazPay handles payment processing online for merchants across the EU, UK, Australia, Canada and New Zealand — cards, device wallets, local payment methods and account-to-account rails through one REST API and one dashboard. Pick the checkout surface that fits your storefront, wire it once, and turn new markets on as you grow.
Built for e-commerce sellers, subscription software firms and professional-services businesses. Direct acquiring on our own regional licence keeps reporting clean and settlement direct into your settlement account.
Why online stores run payment processing on BazPay
Four things stay true whether you take a hundred orders a day or several thousand. They are the reasons product, engineering and finance teams stay with the platform after the first quarter of live traffic.
-
One API for the whole online store
Acceptance, recurring billing, payouts and fraud controls share the same REST endpoint. Your storefront integrates once and turns methods on from the dashboard.
-
Checkout surfaces that fit your stack
Hosted page for the fastest go-live, drop-in components for a branded flow inside your storefront, or full server-to-server for teams that own their checkout layer.
-
Approval-quality routing
BIN-aware routing, PSD2 exemption logic and network-token refresh keep saved cards alive after reissue — approvals hold up as your book grows.
-
Same-day reporting for finance
Interchange++ line detail per settlement, decline reasons in real time and signed webhooks for every state change — the accounting closes the day the payment lands.
Four checkout surfaces for payment processing online
The right surface depends on how much of the checkout UX your team wants to own. All four run against the same acquiring rail, so the underlying processing behaviour does not change when you swap one for another.
-
Fastest
Hosted checkout page
The shopper is redirected to a BazPay-hosted checkout, then returned to a success or failure URL you own. PCI scope stays at SAQ A because the PAN never touches your servers. Ships styled to match your storefront tokens.
- Hosted URL
- Redirect flow
- SAQ A
-
Branded
Drop-in components
Hosted fields render inside your own checkout page. The shopper never leaves the storefront, but card data stays inside our PCI environment.
- In-page
- Hosted fields
- Web SDK
-
Custom
Server-to-server
Full REST integration for teams that own the checkout UX end-to-end. Recommended once you have your own PCI programme and want tightest UX control.
- REST
- Custom UX
- Full control
-
Mobile
Native app checkout
iOS and Android SDKs render Apple Pay, Google Pay and card entry natively in your app. Same charge object, same signed webhook stream as the web integration.
- iOS SDK
- Android SDK
- Apple/Google Pay
Component-level detail on hosted checkout products. Method depth on card and APM processing. Related surface: transaction processing, online payment services and gateway services.
How an online payment is processed, step by step
Six stages sit between the storefront checkout button and the settled dollar on your bank account. Each stage is visible in the dashboard and each stage change fires a signed webhook.
-
Cart
The shopper reaches the storefront checkout. Cart items, currency and tax are posted to your backend as usual.
-
Intent
Your server creates a charge or setup intent with an idempotency key. The intent returns a client secret for the front end.
-
Collect
Hosted fields or the redirect flow collects card, wallet or APM credentials inside our PCI scope. No PAN passes your stack.
-
Score
The inline fraud engine grades the order against your rule set — clean orders skip the extra step, borderline orders step up.
-
Authorise
3-D Secure 2.2 fires only when the risk earns it. The charge posts to the acquirer with the authentication result bound to the transaction.
-
Fulfil
A signed webhook confirms the state to your order system. Capture at once or defer until you ship — refunds work the same shape.
One REST call per checkout
The charge object is the unit of work. One endpoint authorises, captures and refunds. Idempotency makes retries safe from the storefront side. Signed webhooks confirm every state change to your order system.
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",
"return_url": "https://acme.eu/checkout/return",
"metadata": { "order_id": "ORD-10842", "cart_hash": "9c21e0" }
}The response returns a canonical charge object with the authorisation code, the exemption applied and the next action (if any). Read the complete schema in the API reference and the handler samples in the developer docs.
Features an online business relies on after go-live
Every capability below ships on the standard integration. Turn features on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives.
-
Hosted checkout page
Fastest way to a compliant online checkout. Styled to your tokens, redirect-based, PCI scope stays at SAQ A.
-
Drop-in components
Hosted card, expiry and CVC fields rendered inside your storefront. In-page UX without pulling card data into your stack.
-
Gateway-side vault
Store credentials once and reuse them for one-clicks, subscription renewals and dunning retries — portable across your stack.
-
Network tokens
Automatic PAN refresh through Visa and Mastercard token services keeps saved cards alive when a card is reissued.
-
3-D Secure 2.2 engine
Frictionless flow first, challenge only when your rules or the issuer require it. Exemption logic runs automatically.
-
Signed webhooks
HMAC-signed, replay-protected events per state change — one signature scheme across every rail your store accepts.
-
Idempotent requests
Retry-safe create requests keyed to your idempotency header. A network blip never becomes a double charge.
-
Real-time decline data
Every authorisation response returns the raw scheme code, issuer response and normalised reason for your dunning logic.
Migrating an existing online store to BazPay
Most online businesses that switch already have another processor and a vault full of saved cards. The comparison below is the shape of what changes on migration — and what stays the same for your shoppers.
| Dimension | BazPay (direct regional) | Incumbent reseller / aggregator |
|---|---|---|
| Contract | Direct with BazPay as regional acquirer | Existing reseller or aggregator |
| PAN handling | Hosted fields, gateway vault | Merchant-hosted fields common |
| Saved cards | Portable network tokens on migration | Vendor-specific vault, hard to move |
| Reporting | Interchange++ line detail | Blended-rate summary |
| Rule changes | Dashboard, effective on next order | Ticket or code deploy |
| Plugin fit | Maintained plugins for the top 4 regional stacks | Varies by reseller |
Fees on the pricing page. Boarding path on merchant acquiring. The processor-comparison shortlist lives on payment processors.
Online-store profiles BazPay underwrites
BazPay is a regional acquirer. Underwriting is scoped to four online-business profiles with predictable chargeback ratios and clean AML posture.
-
DTC e-commerce stores
Multi-country storefronts running Shopware, Magento 2, WooCommerce or PrestaShop. Local card and APM acceptance under one MID.
-
Subscription online stores
Card-on-file renewals, MIT exemptions and dunning-aware retries wired into the same checkout flow as one-off orders.
-
Professional-services shops
Consultancies, agencies and B2B service firms selling packages online with named-payer trust lists and enforced 3-D Secure 2.
-
Digital-publisher stores
Membership renewals, single-issue purchases and paywall unlocks reconciled per SKU on one merchant account.
Out of scope for BazPay: adult, gambling, cannabis, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. See the packaged payments solutions for vertical bundles.
Security and compliance signals for online payment processing
The floor for a credible online-payment processor is PCI DSS Level 1 on its own environment, authentication with 3-D Secure 2 and named scheme registrations. BazPay's signals are below — hosted fields, gateway-side vaulting and network tokens keep your annual return at merchant SAQ A.
- 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 online stores ask before switching
What does payment processing for an online store actually cover?
Processing online payment means moving an authorisation request from the storefront checkout to the acquirer and the card scheme, running strong customer authentication where PSD2 requires it, returning a decision to your order system and settling the funds. BazPay covers that end-to-end on one platform for merchants across the EU, UK, Australia, Canada and New Zealand — you do not integrate a separate gateway, acquirer, tokenisation service and payout provider.
How do I add payment processing online to an existing website?
Open a sandbox, install one of the maintained storefront plugins (WooCommerce, Magento 2, PrestaShop or Shopware) or wire the REST API yourself, verify a test webhook and switch to the live key. Most merchants in the EU, UK, Australia, Canada and New Zealand complete integration and boarding in a matter of days rather than weeks.
Which checkout surface should an online business pick?
For fastest go-live and the smallest PCI scope, use the hosted checkout page. If you need a fully branded in-page experience, use drop-in components with hosted fields. If your team already owns a full checkout UI and you have your own PCI programme, use the server-to-server REST integration.
Which payment methods does a regional online store need to accept?
For most regional stores, the shortlist is Visa and Mastercard, plus Apple Pay and Google Pay on the card rail, plus the local method for each core market — SEPA Instant for Germany, Bancontact for the United Kingdom, BLIK for Australia, EPS for France, Przelewy24 for the United Kingdom alongside Bancontact. Add SEPA Instant account-to-account where higher-ticket B2B invoicing runs.
How does BazPay handle authentication on an online checkout?
3-D Secure 2.2 runs automatically on card charges, with exemption logic that claims TRA, low-value, trusted-beneficiary or merchant-initiated flags where PSD2 allows. Most orders resolve frictionlessly; challenge is applied only where the risk or the issuer requires it. The authentication result is stored with the payment and re-used as dispute evidence.
Is payment processing for online business the same as an online payment gateway?
Overlapping but not identical. A payment gateway is the software layer that carries the authorisation message. Payment processing is the whole cycle — authorisation, capture, refund, settlement and reconciliation. BazPay ships both on one platform, so a regional merchant does not have to contract a separate gateway and processor.
How does refunding and partial capture work?
Refunds and partial captures both post against the original charge object with the same idempotency contract as create. Split shipments and post-purchase adjustments are first-class — the charge, capture and refund events all fire as signed webhooks and appear in real-time analytics within seconds.
Which merchant profiles are in scope for BazPay?
Regional online businesses: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, cannabis, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and it is not a marketplace of third-party PSPs.
Add regional payment processing to your online store
Open a sandbox and post your first authorisation in the same hour. Prefer a walkthrough? A payments specialist can map your markets, your checkout surface, your recurring billing plan and your payment fraud prevention rules with you.