Menu
Talk with sales

Integration questions? [email protected]

Payment gateway for ecommerce sites — storefronts on one direct acquirer.

BazPay is a payment gateway for ecommerce built for regional storefronts. Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware install in minutes; cards, wallets and local payment methods share the same charge object; settlement lands in your own local settlement account under a named merchant identifier.

Built for EU, UK and Commonwealth e-commerce sellers of every size — DTC brands, multi-country storefronts, digital-goods sellers and subscription-based shops. One contract, one dashboard, one signed webhook stream across every method you accept.

Talk with sales See storefront integrations

Why merchants pick BazPay for their ecommerce checkout

An ecommerce site's payment gateway needs four things at once: plugin coverage that drops in, method breadth that matches every market, a checkout UX that stays on your site, and clean acquiring economics that finance can reconcile.

  • Drop-in plugins for the four regional commerce stacks

    Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware install into your existing storefront in minutes. Checkout, refunds, capture, webhooks and recurring billing configured on install — no custom integration required.

  • Every regional payment method your shoppers reach for

    Cards, Apple Pay, Google Pay and local payment methods share the same charge object. Turn SEPA Instant, Bancontact, BLIK, EPS or Przelewy24 on from the dashboard as you enter a new market — no re-integration per country.

  • Cart-friendly UX with low PCI scope

    Hosted fields render card inputs inside your existing checkout so the shopper never leaves your site. Merchant SAQ A stays intact regardless of how deep the embed goes — no full PCI environment to run for the storefront.

  • Direct regional acquirer, no aggregator layer

    You contract with BazPay directly for card acceptance. Your merchant identifier is named to your entity, settlement lands in your own local settlement account, and chargeback attribution stays clean instead of diluting across a shared pool.

Four integration surfaces for any storefront stack

Pick the integration surface that matches your build — a maintained plugin, a hosted checkout page, hosted fields inside your own checkout, or a custom REST integration for headless commerce.

  • Plugins

    Maintained storefront plugins

    Install a plugin, enter your API keys, save. The plugin exposes cards, wallets and enabled APMs inside the storefront's own checkout. Refunds, captures, dispute events and recurring billing are wired through the plugin's admin screens.

    • WooCommerce
    • Magento 2
    • PrestaShop
    • Shopware 6

  • Hosted

    Hosted checkout page

    Redirect to a BazPay-hosted checkout that presents every enabled method — the fastest way to add a compliant payment page to a bespoke storefront without touching card data.

    • Hosted page
    • Branded
    • PSD2-ready

  • Embedded

    Hosted fields inside your checkout

    Card, expiry and CVC inputs served from our PCI environment inside your own checkout form. The shopper never leaves your site; the raw PAN never touches your servers.

    • Hosted fields
    • Drop-in JS
    • 3DS 2 render

  • API

    Custom REST integration

    For headless commerce and custom checkout stacks, call the REST API directly. One versioned endpoint accepts a payment on any rail; the response shape is stable across cards, wallets and APMs.

    • Versioned
    • Idempotent
    • Signed webhooks

Full plugin directory on the integrations page. Hosted and drop-in primitives on hosted checkout products.

From cart to reconciled order

Six stages describe the path an ecommerce order walks through — cart, checkout, method selection, authorisation, fulfilment webhook and reconciliation. Each stage is visible in the dashboard and each stage change fires a signed webhook.

  1. Cart

    The shopper adds items to the cart in your storefront. Nothing about the cart layer changes when you enable BazPay.

  2. Checkout

    The shopper reaches the storefront's checkout. Plugin, hosted fields, hosted page or custom API — whichever surface you picked shows the enabled payment methods.

  3. Method + 3-D Secure

    The shopper picks card, wallet or a regional APM. 3-D Secure 2.2 runs on cards only when the risk earns it; APMs run their own bank-authenticated flow.

  4. Authorise

    The charge posts on BazPay's own regional acquiring licence with the authentication result bound. International-issued cards route through the same contract.

  5. Fulfil

    A signed charge.succeeded webhook fires to your storefront's fulfilment endpoint — the plugin or your custom handler releases the order.

  6. Reconcile

    Settlements land in your local settlement account per scheme cycle. Refunds, chargebacks and disputes fire signed events keyed to the same charge ID.

Direct-acquirer gateway vs aggregator for ecommerce

Aggregators go live fast and pay for it on the reporting, chargeback and settlement side. A direct acquirer takes a few days at boarding and pays back on every metric that matters after go-live.

BazPay direct-acquirer ecommerce gateway compared with an aggregator model
Dimension BazPay (direct acquirer) Aggregator
Contract Direct with BazPay as regional acquirer Aggregator on shared MID
MID Named to your legal entity Shared across pool
Plugin coverage WooCommerce, Magento 2, PrestaShop, Shopware One or two of the four
Regional APM breadth iDEAL, Bancontact, BLIK, pay by bank, PayTo on toggle Per-vendor SDK per method
3-D Secure 3-D Secure 2.2 with exemption logic Blanket 3DS or none
Reporting Interchange++ per order Blended summary
Underwriting scope Regional storefronts Broad, few exclusions

Rate structure on the pricing page. Getting-started walkthrough on accept online payments. Acceptance breadth on payment acceptance.

Features engineered for ecommerce checkout and back-office

Every capability below ships on the standard integration and inside the storefront plugins. No premium tier gates hosted fields, local APMs or the signed webhook contract.

  • Storefront plugin admin

    Refunds, captures, disputes and payout schedules are managed from the storefront's own admin — WooCommerce, Magento, PrestaShop or Shopware.

  • Hosted fields

    Card inputs served from our PCI environment inside your checkout — keeps your annual return at SAQ A and your shopper on your domain.

  • Regional APM support

    iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac render alongside cards. Dashboard toggle per market — no new plugin to install.

  • Apple Pay + Google Pay

    Wallet buttons render inside the storefront's checkout and clear on card rails with wallet-supplied network tokens.

  • 3-D Secure 2.2 with exemptions

    Authentication runs only when the risk earns it. Most storefront checkouts stay frictionless; risky orders step up to the issuer challenge.

  • Signed webhooks

    HMAC-signed, replay-protected events for order state changes — the plugin's fulfilment handler verifies once and routes on event type.

  • Refund + dispute flow

    Full and partial refunds from the storefront's order screen. Chargeback evidence is pre-assembled with the 3DS result and charge metadata.

  • Interchange++ reporting

    Interchange, scheme fees and gateway margin split per settled order — the finance team reconciles against the source, not a blended rate.

Custom checkout on the same charge object as the plugins

Headless storefronts and bespoke checkouts call the REST API directly. The charge object shape is stable across cards, wallets and local APMs; the same idempotency contract and signed-webhook envelope work regardless of the integration surface. 

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
  "amount": 4990,
  "currency": "EUR",
  "payment_method": "card",
  "capture": "auto",
  "three_d_secure": "required_if_needed",
  "return_url": "https://your-shop.example/checkout/return",
  "metadata": { "order_id": "ORD-10842", "shop": "example-eu" }
}

The response returns a canonical charge object with the authorisation code, network and any exemption applied. Full schema in the API reference.

Where BazPay runs as the payment gateway for ecommerce

Four ecommerce merchant profiles already run BazPay-powered checkouts across our markets. Each uses the same charge object and the same signed webhook.

  • DTC brands on WooCommerce or Shopware

    EU, UK and Commonwealth direct-to-consumer brands running one storefront, with card + Apple/Google Pay + SEPA Instant enabled per market from the dashboard.

  • Magento 2 / Adobe Commerce merchants

    Larger regional catalogues on Adobe Commerce with hosted fields inside the native checkout, refunds and captures wired into the admin.

  • PrestaShop stores across our markets

    Multi-language, multi-market PrestaShop shops with card, wallet and per-country APM acceptance on one contract.

  • Headless / custom-checkout ecommerce

    Composable-commerce storefronts calling the REST API directly, with signed webhooks fulfilling orders in the headless backend.

Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a crypto payment gateway and does not act as a merchant of record.

Security and compliance for the ecommerce checkout

Card handling runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields keep your annual return at merchant SAQ A. Authentication runs on every card charge with 3-D Secure 2.2 and automatic exemption logic — most storefront checkouts stay frictionless.

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 ecommerce merchants ask before switching

What makes a good payment gateway for ecommerce sites?

For a regional ecommerce site the shortlist is direct acquiring (named MID, not shared), plugin coverage for your storefront stack, regional APM breadth (iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac alongside cards), 3-D Secure 2.2 with PSD2 exemption logic and low PCI scope. BazPay ships all five on one contract for merchants in the EU, UK, Australia, Canada and New Zealand.

Which storefront platforms does the payment gateway for ecommerce website support?

Maintained plugins cover WooCommerce (WordPress), Magento 2 / Adobe Commerce, PrestaShop and Shopware 6. Each plugin exposes cards, wallets and enabled local APMs inside the storefront's own checkout and wires refunds, captures, webhooks and recurring billing through the storefront's admin. Custom checkouts integrate directly against the REST API — the same endpoints the plugins call.

How do I add a payment gateway ecommerce integration to my existing shop?

Install the plugin for your storefront platform, enter your BazPay API keys and webhook secret in the settings screen, enable the payment methods you want to accept, and place a test order in sandbox. Live keys switch on after underwriting. Existing shops with a bespoke checkout can use the REST API — the same charge object as the plugins.

Do you offer a crypto payment gateway for ecommerce?

No. BazPay is not a crypto payment gateway and does not board crypto-exchange merchants or accept cryptocurrency at checkout. The platform focuses on card, wallet, local payment method and SEPA Instant processing for EU, UK and Commonwealth e-commerce. Ecommerce sites that need cryptocurrency acceptance should look at a dedicated crypto-payment provider.

How does the payment gateway for ecommerce handle local payment methods?

SEPA Instant for German shoppers, Bancontact for British, BLIK for Australian, EPS for French and Przelewy24 for British acceptance all sit behind the same charge object as cards. Enable a method in the dashboard for the market you serve; the plugin or hosted checkout renders the appropriate option to eligible shoppers automatically.

How are refunds and disputes handled inside the storefront?

Refunds are issued from the storefront's own order screen — the plugin translates the click into a BazPay API call and fires a signed refund webhook back into the shop. Disputes surface as signed events with the reason code, evidence-due deadline and a pre-assembled evidence packet (3DS result + charge metadata) that you review and submit in the dashboard.

Which ecommerce merchant types can board?

Merchants across the EU, UK, Australia, Canada and New Zealand: DTC brands, multi-country storefronts, digital-goods sellers, subscription-based stores. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and does not act as a merchant of record.

How fast can an ecommerce storefront go live on BazPay?

Sandbox keys are available at signup, so integration and test transactions can start in the same afternoon. Production traffic depends on underwriting — regional storefronts typically clear in days once KYC documents and a short business summary are submitted.

Plug BazPay into your ecommerce checkout this sprint

Share your storefront platform, monthly volume and target markets. A named engineer will confirm boarding fit and map the plugin install inside one working day. See also pricing, hosted checkout products and payment acceptance.

Talk with sales Read the developer docs