Menu
Talk with sales

Integration questions? [email protected]

Payment gateway software for EU, UK and Commonwealth merchants.

BazPay is a payment gateway software provider. The gateway runs as a managed SaaS platform on our own regional acquiring licence; the pieces that live on your side — plugins, SDKs, hosted checkout components — are signed downloads from a public source, wired to a versioned REST API.

Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services companies. One dashboard for engineering, finance and support — no self-hosted card server, no bolt-on modules to stitch together.

Talk with sales Read the developer docs

Why SaaS payment gateway software wins for merchants in the EU, UK, Australia, Canada and New Zealand

Four things stay true whether you accept a hundred euros a day or several million. They are the reasons product, engineering and finance teams stay on hosted gateway software after the switching cost is paid.

  • SaaS, not a server your team maintains

    The gateway runs on BazPay infrastructure inside a PCI DSS Level 1 environment. Your engineering team integrates against a REST API — no self-hosted binary, no OS patching, no PCI scope creep from a card server you operate.

  • Signed, versioned software

    Plugins, SDKs and the API itself ship with cryptographic release signatures, version headers and a documented deprecation window. Nothing changes under an integration silently.

  • One dashboard for every role

    The admin surface handles engineering (keys, webhooks, rule builder), finance (interchange++ statements, refunds) and support (case queue, dispute defence) without a plugin per role.

  • Downloadable where it belongs

    The gateway itself is a service, not an installer. What you do download are the storefront plugins, the mobile SDKs and the client libraries — signed builds from a public source.

What ships with the online payment gateway software

Four software components make up the platform. The backend runs on BazPay infrastructure; plugins, SDKs and hosted checkout components run inside your stack.

  • Platform

    The gateway backend

    The core payment gateway software runs as a multi-tenant SaaS platform on BazPay infrastructure. Card data lives inside a PCI-scoped vault; authorisation, tokenisation, 3-D Secure 2 and settlement are all backend responsibilities you never install or patch.

    • PCI DSS Level 1
    • REST API
    • Signed webhooks

  • Checkout

    Hosted checkout components

    Hosted fields and hosted payment pages served from our PCI environment — the visible half of the software, embedded in your storefront without exposing card data to your servers.

    • Hosted fields
    • Hosted page
    • Drop-in

  • Plugins

    Storefront plugins

    Signed builds for the four common regional commerce stacks. Downloaded through your platform's official marketplace or from the BazPay dashboard, updated through the same channel.

    • WooCommerce
    • Magento 2
    • PrestaShop
    • Shopware

  • SDKs

    Server-side and mobile SDKs

    Server libraries for common backend languages plus native iOS and Android SDKs for mobile checkouts. Webhook-signature helpers, retry-safe request builders and typed models included.

    • iOS
    • Android
    • Server SDKs

The wider product family lives on payment gateway. For the operational envelope around the software, see payment gateway services; for vertical bundles, payments solutions.

From sandbox to live traffic — the software install path

Six stages describe how a team goes from opening a sandbox account to posting real charges. Each stage is trackable in the dashboard and each stage change fires a signed webhook.

  1. Sign up

    Open a sandbox account and receive API credentials, webhook signing secret and dashboard invitations for your team.

  2. Choose surface

    Redirect to a hosted page, embed hosted fields, install a storefront plugin or call the API server-to-server — same platform, different surface.

  3. Download

    Pull the signed plugin from your commerce stack's marketplace, or the server-side / mobile SDK from the BazPay dashboard's downloads section.

  4. Integrate

    Verify signed webhooks, wire idempotency keys and enable 3-D Secure 2.2. Client-library helpers keep the code short and safe by default.

  5. Test

    Sandbox replays production-shaped traffic, decline codes, 3-D Secure 2 flows and dispute events, so tests match the live surface.

  6. Go live

    Board through underwriting, flip the API key and start posting real charges. Real-time analytics show approval quality from the first hour.

SaaS payment gateway software vs self-hosted card server

Both models exist, but they solve different problems. Self-hosted software gives full control at the cost of full PCI scope and full operational responsibility. SaaS gateway software trades a little control for a much smaller compliance and operations surface.

SaaS payment gateway software compared with self-hosted card server
Dimension BazPay SaaS software Self-hosted card server
Delivery model Managed SaaS, no server to run Self-hosted binary you maintain
PCI scope Merchant SAQ A (hosted fields, vault) Full merchant PCI on any card-processing server you host
Upgrades Rolled out under a versioned contract Manual patching, downtime windows
Fraud engine Inline, dashboard-configurable Bolt-on module per install
3-D Secure 2 Certified 3-D Secure 2.2 with exemption logic Depends on version and configuration
Reporting Interchange++ line detail in one place Assembled from downstream statements
Support and status Named integration manager, public status page Vendor support tickets per component

Rate structure on the pricing page. Buyer's shortlist on the payment processors page.

Software features that matter after the install

Every capability below is available on the standard integration. Turn features on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives.

  • Versioned REST API

    Every breaking change ships behind a version header with a documented deprecation window. An integration built against v1 does not break when v2 lands.

  • Idempotent requests

    Retry-safe create requests keyed to your idempotency header. A network blip never becomes a double charge.

  • Signed webhooks

    HMAC-signed, replay-protected events for every state change; delivery retries on an exponential schedule for up to 72 hours.

  • Hosted fields

    Card, expiry and CVC inputs served from our PCI environment inside your checkout, keeping raw PAN out of your infrastructure.

  • Gateway-side vault

    Store credentials once and re-use across renewals, upgrades and one-clicks — portable if you ever change stack.

  • 3-D Secure 2.2 engine

    Frictionless flow first; PSD2 exemption logic claims TRA, low-value, trusted-beneficiary and MIT where the rules allow.

  • Rule builder in the dashboard

    Compose fraud triggers on 30+ enriched fields. Publish rule changes from the dashboard — no engineering release required.

  • Interchange++ reporting

    Every settled transaction breaks out interchange, scheme fees and processor margin for line-level finance reconciliation.

One REST call, whichever software surface you use

The charge object is the unit of work across the whole platform — the storefront plugin, the mobile SDK, the server SDK and a raw HTTP call all produce the same request shape and read the same response object. The request below is what a server SDK builds under the hood. 

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
BazPay-Version: 2026-04-01
{
  "amount": 4990,
  "currency": "EUR",
  "payment_method": "card",
  "capture": "auto",
  "three_d_secure": "required_if_needed",
  "descriptor": "ACME EU LTD",
  "metadata": { "order_id": "ORD-10842" }
}

The BazPay-Version header pins your integration to a specific contract version. Non-breaking additions land under the current version; breaking changes get a new one with a documented deprecation window. Complete schema in the API reference.

Which merchants run on this gateway software

BazPay is a regional platform. Underwriting is scoped to four merchant profiles with predictable chargeback ratios and clean AML posture — the software is shaped to those profiles by default.

  • E-commerce sellers

    DTC brands and multi-country storefronts on Shopware, Magento 2, WooCommerce or PrestaShop — the plugin is the whole install.

  • Subscription software

    SaaS teams billing monthly and annual plans use the server SDK to wire recurring charges, MIT exemptions and dunning cleanly.

  • Professional services

    Agencies and consultancies using hosted payment pages for invoiced work — the fastest install of the platform.

  • Mobile-first commerce

    Native iOS/Android checkouts through the mobile SDK — Apple Pay, Google Pay and card entry with one charge object.

Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a merchant of record and not a marketplace of third-party PSPs.

Security, signing and change management

The gateway runs inside a PCI DSS Level 1 environment assessed each year. Plugins and SDKs ship as signed releases from a public source. API changes go through a versioned release with a documented deprecation window, so an integration built against v1 keeps working when v2 lands.

PCI DSS Level 1
Annual assessment on the acquiring and gateway software environment
Merchant SAQ A
Hosted fields and gateway vault keep card data out of your infrastructure
Authentication
3-D Secure 2.2 with automatic exemption logic on every card charge
GDPR
In-region data residency; DPA on request
Signed releases
Plugins and SDKs distributed with cryptographic release signatures
Change management
Versioned API, published deprecation policy, audit-logged dashboard actions

Questions merchants ask about payment gateway software

Is there a payment gateway software download for a self-hosted install?

No. BazPay is delivered as a SaaS payment gateway, not as a binary you install and run. What is downloadable are the pieces that live on your side — the storefront plugins (WooCommerce, Magento 2, PrestaShop, Shopware), the mobile SDKs (iOS and Android) and the server-side client libraries. Every download is signed and versioned. The gateway backend itself runs on BazPay infrastructure inside a PCI DSS Level 1 environment.

What does a payment gateway software provider actually ship?

In BazPay's case: the backend gateway platform (multi-tenant SaaS), the hosted checkout surfaces (hosted fields, hosted page, drop-in), the storefront plugins for common regional commerce stacks, the mobile and server SDKs, the merchant dashboard for engineering, finance and support roles, and the operational envelope around all of it — status page, changelog, versioned API, signed webhooks.

How is online payment gateway software different from a self-hosted card server?

A self-hosted card server processes and stores card data on infrastructure you operate — which puts you in full merchant PCI scope with the audit obligation that comes with it. Online payment gateway software delivered as SaaS keeps card data inside the provider's PCI environment. Your annual return stays at SAQ A because your servers never handle a live PAN.

Which languages are supported by the server SDKs?

Common server-side languages have maintained client libraries with typed request/response models, webhook signature verification, retry-safe request builders and pagination helpers. Any language with a modern HTTP client can call the REST API directly against the same versioned contract.

How are plugin updates delivered?

Plugins are distributed through each commerce platform's official marketplace and the BazPay dashboard's downloads section. Updates ship as signed releases with a changelog entry and — when a change requires action — a migration note. Nothing auto-updates a live storefront without your operator flipping a switch.

What versioning guarantees does the gateway software make?

The REST API uses version headers with a documented deprecation window for breaking changes. Non-breaking additions land under the current version. Every deprecation is announced in the changelog before it takes effect, and integrations built against an older version continue to work through the window.

Can I use the software without installing anything?

Yes. If you use the hosted checkout page, the integration on your side is a redirect and a webhook handler — no plugin, no SDK. If you build against the REST API directly, no client library is required. Plugins and SDKs are conveniences, not obligations.

Which merchants can use this payment gateway software?

Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and it is not a marketplace of third-party PSPs.

Try the payment gateway software in a sandbox

Open a sandbox account and post your first charge in the same hour. Prefer a walkthrough of the download surface — plugins, SDKs and hosted components — with a named integration engineer? See payment gateway services.

Talk with sales Read the API reference