Menu
Talk with sales

Integration questions? [email protected]

A payment network gateway for EU merchants.

BazPay is a network payment gateway that reaches card networks, tokenisation services, wallets, EU local payment methods and bank rails through one platform. One REST endpoint authorises against any network; one signed webhook stream reports every state change.

Built for EU e-commerce sellers, subscription software firms and professional-services businesses. You wire the platform once, then switch networks on as you grow into new markets and channels.

Talk with sales Read the API reference

Why merchants choose one platform for every network

Four things stay true whether you accept one card scheme or all five families. They are the reasons product, engineering and finance teams stay with us after go-live.

  • One integration, many networks

    Card networks, tokenisation services, EU local schemes and bank rails share a single REST endpoint and a single dashboard. You wire the platform in once, then activate networks from a toggle.

  • Network tokens by default

    Card credentials are replaced with Visa and Mastercard network tokens at storage time. Saved cards keep working after reissue, and no PAN moves through your stack.

  • International card reach

    EU acquiring on our own licence covers domestic and cross-border card authorisation. Cards issued outside the EU authorise on the same contract and settle into the same balance.

  • One event catalogue

    Every network's approval, decline, refund, dispute and settlement event flows through the same signed webhook. Your integration reads network payment systems as one stream, not five.

The networks the platform reaches

Four network families run through one connection. Turn any of them on from the dashboard — no new contract per network, no separate integration per rail.

  • Card networks

    Direct card network membership

    Visa, Mastercard, Cartes Bancaires and Maestro authorise on our own EU acquiring licence — a card payment network reachable through one BazPay charge object. International-issued cards route through the same contract.

    • Visa
    • Mastercard
    • Maestro
    • Cartes Bancaires

  • Wallets

    Device-wallet networks

    Apple Pay and Google Pay ride the card rail with a wallet-supplied network token. No PAN in the request, no extra credential to store.

    • Apple Pay
    • Google Pay

  • Local methods

    EU APM connectors

    Local payment method networks clear through the same platform and reconcile into the same settlement balance as card volume.

    • iDEAL
    • BLIK
    • Bancontact
    • EPS
    • Przelewy24

  • Bank rails

    Account-to-account rails

    SEPA and SEPA Instant for euro-denominated pulls and payouts. Open banking authentication runs bank-side, keeping cards out of the flow entirely.

    • SEPA
    • SEPA Instant
    • Open banking

Payment-method depth on card and APM processing. The acquiring contract itself lives on merchant acquiring.

The life of a network-routed charge

Six stages sit between checkout and reconciliation. Each stage is visible in the dashboard and each stage change fires a signed webhook keyed to the same charge ID.

  1. Initialise

    The checkout script loads hosted fields or the mobile SDK and gathers device signals before any network hop.

  2. Route select

    The platform picks a network — card, wallet, APM or account-to-account — based on the payment_method flag on the request.

  3. Tokenise

    Card credentials become network tokens at first storage. Wallet payments arrive already tokenised end-to-end.

  4. Authorise

    The tokenised charge posts to the chosen network. 3-D Secure 2.2 runs only when the risk earns it.

  5. Confirm

    The response returns the network authorisation code and the exemption applied. The same shape for every network.

  6. Reconcile

    Settlement events, refunds and disputes fire as signed webhooks per network, keyed to the same charge ID.

One platform vs one integration per network

Building against several vendors — one for cards, one for wallets, one for APMs — adds an integration surface per network and multiplies your reconciliation work. A single network payment gateway collapses that surface.

One platform compared with multiple per-network integrations
Dimension BazPay (one platform) Per-network integrations
Integration surface One REST endpoint Per-network SDK per PSP
Event stream Signed webhooks per network, one catalogue Different envelopes per vendor
Tokenisation Network tokens default Vendor-specific vault formats
Auth response shape One canonical charge object Varies per gateway
Fraud engine Inline, PSD2 exemption logic built in Bolt-on per network
Settlement Reconciled per rail, one dashboard Aggregated across pool

Statement structure on the pricing page. Plugin coverage on integrations. Prefer the network platform pre-configured per business type? See the packaged payments solutions bundles.

Features engineered into the network platform

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.

  • Network payment gateway API

    One REST endpoint reaches every connected network. The response object shape does not change between rails.

  • Network tokenisation

    Visa and Mastercard network tokens replace PAN at storage. Automatic PAN refresh keeps saved cards alive after reissue.

  • Gateway-side vault

    Stored credentials sit inside our PCI DSS Level 1 scope, portable between integrations, keyed to your merchant.

  • Mobile SDKs

    iOS and Android SDKs plug the mobile payment network — Apple Pay, Google Pay and card entry — into your app with the same charge object.

  • Hosted fields

    Card, expiry and CVC inputs served from our PCI environment inside your web checkout, keeping your annual return at SAQ A.

  • 3-D Secure 2.2 engine

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

  • Signed webhooks

    HMAC-signed, replay-protected events per network — approval, decline, refund, dispute and settlement — one signature scheme across all.

  • Idempotent requests

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

One REST call reaches any connected network

The charge object is the unit of work. One endpoint routes to a card network, a wallet, a local payment scheme or an account-to-account rail — the request differs by one field. Idempotency makes retries safe. Signed webhooks confirm state changes across every network in the same envelope. 

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
  "amount": 4990,
  "currency": "EUR",
  "payment_method": "card",
  "capture": "auto",
  "three_d_secure": "required_if_needed",
  "customer": "cus_5F9k",
  "metadata": { "order_id": "ORD-10842" }
}

Switch payment_method to ideal, apple_pay or sepa_debit and the request routes to the corresponding network. The response object retains the same shape. Read the schema in the API reference.

Where network payment solutions earn their keep

The default configuration already reflects these four merchant profiles. Turn on the ones you need from the dashboard and tune each network's behaviour against your own traffic.

  • Multi-country e-commerce

    Local card and APM acceptance across the EU on one integration. Shopware, Magento 2, WooCommerce and PrestaShop plug in through maintained connectors.

  • Subscription software

    Network-tokenised card-on-file, dunning-aware retries and MIT exemptions on renewals. One event catalogue reduces the surface area of your billing code.

  • Professional services

    Higher-ticket B2B charges with named-payer trust lists, enforced 3-D Secure 2 over a ceiling you set and reconciliation into your finance stack.

  • Mobile-first commerce

    Native iOS/Android checkout with Apple Pay and Google Pay wired to the same platform, reaching the mobile payment network without duplicated integrations.

Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay does not operate a cryptocurrency payment network.

Security and compliance signals

The network platform runs inside a PCI DSS Level 1 environment assessed each year. Network tokens, hosted fields and gateway-side vaulting keep your annual return at merchant SAQ A. PSD2 SCA runs on every card network with automatic exemption logic.

PCI DSS Level 1
Gateway and acquiring environment assessed annually
Merchant SAQ A
Hosted fields and network tokens keep card data out of your stack
PSD2 SCA
3-D Secure 2.2 with automatic exemption logic on every card network
GDPR
EU data residency; DPA available on request
Network compliance
Visa VIRP and Mastercard SPoC/PCI-CP registrations where required

Questions merchants ask first

What is a payment network, and what does BazPay do inside it?

A payment network is the set of contracts, message formats and clearing rules that move a payment from a shopper to a merchant. BazPay is a network payment gateway: it holds direct membership with card networks on its EU acquiring licence and provides the software layer that reaches wallet networks, EU local payment method schemes and bank rails through one platform.

How is a network payment gateway different from a bare payment processor?

A bare processor moves a single authorisation message. A network payment gateway is the software platform that reaches multiple networks through one integration — cards, wallets, APMs and account-to-account rails — with unified tokenisation, one event catalogue and one dashboard for reporting across every network.

How does payment network tokenization work on BazPay?

Card credentials are replaced with Visa or Mastercard network tokens at storage time and stored in the gateway vault. When a card is reissued, the token refreshes automatically through the scheme token service, so subscription renewals and card-on-file charges keep working without asking the shopper for a new PAN.

Does BazPay reach international card networks or only EU-issued cards?

Authorisation runs on our EU acquiring licence, so BazPay is an EU acquirer — but the card networks are international. Cards issued outside the EU authorise on the same contract and settle into the same balance. In that sense the platform gives EU merchants an international payment network reach without additional contracts.

Are there mobile SDKs for the mobile payment network?

Yes. iOS and Android SDKs render Apple Pay, Google Pay and card entry in your native app, produce the same charge object as the web integration and share the same signed webhook stream. There is no separate mobile back-office to maintain.

Does BazPay operate a cryptocurrency payment network?

No. BazPay is not a cryptocurrency payment network and does not board crypto-exchange merchants. The platform is focused on card, wallet, EU local payment methods and account-to-account rails for low-risk EU merchants.

Which merchant profiles are in scope?

Low-risk EU merchants: 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.

Can I migrate saved cards from an existing gateway?

Yes. Stored credentials and existing network tokens can be imported from an incumbent processor under a scheme-approved migration, subject to the receiving bank's consent letters. Renewals continue on the new platform without asking shoppers to re-enter their card details.

Reach every network with one integration

Open a sandbox account and post your first charge to any connected network in the same hour. Prefer a walkthrough? A payments specialist can map your networks, your anti-fraud controls, your recurring billing and your payouts with you. Also worth reading: merchant acquiring, payment orchestration, merchant services and international payments.

Talk with sales See all products