Go live on the platform you already run

BazPay connects to the EU storefronts low-risk merchants actually use. Take a pre-built plugin, drop hosted fields into a custom checkout, or call the REST API server-to-server. All three routes reach the same gateway, share one set of keys and settle into one file.

Reviewed against API version 2026-04-01.

Three routes in

  1. Install a plugin Your storefront is one of the five below. Keys in, methods on, live this week. Fastest
  2. Drop in hosted fields Custom checkout, our iframes for the card inputs. Your layout, our PCI scope. Most control per hour spent
  3. Call the API direct Server-to-server REST. You own routing, exemptions, payouts and reconciliation. Platforms and marketplaces

Undecided? Compare what each route costs you in PCI scope, control and engineering days.

What each connector actually does

Published as a matrix rather than as five feature lists, because the useful question is not "does it support refunds" — it is "which of these does the thing my finance team needs on a Tuesday". Where a connector is limited, the limit is printed in the cell.

Capability by cart connector — reviewed 31 July 2026
Capability WooCommerceMagentoPrestaShopShopwareOpenCart
Hosted fields Card inputs are our iframes inside your own checkout, so the PAN never reaches your server. Supported Supported Supported Supported Supported
Hosted checkout redirect The fallback every plugin can use while a themed checkout is still being built. Supported Supported Supported Supported Supported
EU bank methods iDEAL, Bancontact, BLIK, Przelewy24 and EPS, each a toggle rather than a contract. Supported Supported Supported Supported Supported
Apple Pay and Google Pay In-page wallet buttons on the product, cart and checkout pages. Supported Supported Supported Supported With a limit Google Pay only; Apple Pay needs the 4.1 branch
Refunds from the admin Full and partial refunds worked from the order screen, without a second dashboard. Supported Supported Supported Supported With a limit Full refunds only; partials go through the API
Delayed capture Authorise at checkout, capture when the parcel actually leaves the warehouse. Supported Supported With a limit Capture in full; partial capture is API-side Supported Not in the plugin
Stored credentials Tokenised cards and SEPA mandates for subscriptions and repeat billing. Supported Via WooCommerce Subscriptions With a limit Vaulting yes; scheduling stays with your own job With a limit Mandates yes; no scheduler in the module Supported Not in the plugin
Multi-store keys A separate method mix, descriptor and key pair per storefront. With a limit One key set per site in a multisite network Supported Supported Supported With a limit Per store, but the method mix is shared
Webhook-driven order state The order moves when the signed event lands, not when the shopper comes back. Supported Supported Supported Supported Supported
Debug log in the admin Request ids you can paste into a support message instead of describing a symptom. Supported Supported Supported With a limit Written to var/log, not surfaced in the admin Supported

Every connector is free, source-available to merchants using it, and released under the same version cadence as the API. A capability marked as a limit is normally reachable through the API — the plugin simply does not put a control in the admin for it.

No plugin for your stack? Nothing is held back

The connectors above call the same public API you would. There is no private endpoint, no partner-only parameter and no capability reserved for the plugins. If you are on a bespoke storefront, a headless front end or a marketplace, you build against the same contract — and you get the same methods.

From test key to first live payment

Four steps, and no procurement cycle in the middle of them. Underwriting runs in parallel with your build rather than in front of it.

  1. Open a sandbox

    Sign up and the test keys are visible immediately. No sales call, no demo booking, no waiting list.

  2. Install or integrate

    Add the connector for your platform, or call the API from your own stack. Both hit the same endpoints.

  3. Turn on the methods

    Pick methods per market in the dashboard. Each one is a toggle, not a fresh contract with a new provider.

  4. Swap the keys

    Underwriting returns live keys. Your webhooks, routing rules and reports carry over unchanged.

The detail lives in the documentation: the quickstart for the first payment, sandbox behaviour for forcing named declines, and the go-live checklist for the twelve technical checks before cut-over.

Start in the sandbox today

Test keys arrive with the account, and you build against the same endpoints your live traffic will use. Pricing is published, so the cost model is settled before anyone writes a line of code.

  • PCI DSS Level 1
  • PSD2-compliant
  • 3-D Secure 2 certified
  • SEPA Instant participant