Menu
Talk with sales

Integration questions? [email protected]

We built the gateway that makes payments boring

BazPay is a regional payment gateway for e-commerce, SaaS and professional-services merchants. Card acquiring, open banking, payouts and fraud sit in one platform. We started it because the basics were still hard to buy. Pricing was blended and vague. PCI scope leaked into the merchant stack. Plugin gaps forced costly custom work.

So we picked a narrow lane. We serve EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services businesses. Everything on this page follows from that one choice.

Talk with sales

Three decisions that shape the whole platform

Each one costs us something. Narrow underwriting turns business away. Gateway-side scope is expensive to hold. We think the trade is worth it.

  • 01

    We underwrite one TRA

    We board a defined list of sellers and nothing else. No adult, no restricted verticals, no grey traffic. A clean portfolio keeps scheme monitoring quiet. Quiet monitoring keeps approval rates steady for everyone on the book.

  • 02

    Card data never lands on your servers

    Hosted fields render inside our PCI DSS Level 1 scope. The card number goes to us, not to you. Your annual return stays SAQ A. That removes the audit work most gateways quietly push downstream.

  • 03

    One contract, thirteen product pillars

    Acquiring, open banking, payouts, fraud and subscriptions share one API and one dashboard. You reconcile a single settlement file. Nothing here is a partner redirect you have to chase.

What we hold, and what it removes from your desk

Compliance is a product feature here, not a badge row. Read the detail in the compliance hub.

BazPay attestations and the merchant-side effect
StandardWhat it coversEffect on you
PCI DSS Level 1 Card data, vaulting and hosted fields You file SAQ A
Open-finance regulation Strong customer authentication and exemptions Exemption logic is built in
3-D Secure 2 Challenge and frictionless authentication Certified flows, no plugin
GDPR Payment and shopper data handling In-region data residency
SEPA Instant Pay-by-bank credit transfers Settles in seconds

From sandbox key to live traffic in four moves

No demo is required to start building. The API docs and the sandbox are open. Underwriting runs beside your build, not before it.

  1. Step 1

    Open a sandbox

    Sign up and get keys the same day. No sales call gates the test account. Build against real API responses first.

    Open a sandbox account
  2. Step 2

    Send us the file

    Company papers, ownership and a look at what you sell. We tell you fast if the vertical is outside our band.

    Read who we serve
  3. Step 3

    Wire the integration

    Use a CMS plugin or the REST API. Most teams finish in days. Webhooks are versioned and safe to replay.

    See the CMS plugins
  4. Step 4

    Go live and watch

    Live keys, real-time decline reasons and an itemised settlement file. You see the raw issuer reason, not a generic error.

    See the analytics view

Boring software, on purpose

Every write endpoint takes an idempotency key. Retry a payment safely after a timeout. Endpoints are versioned, so a new field never breaks your build. We hold a 99.9%+ uptime target on the payment path.

Webhooks are signed and replayable. Decline reasons come back raw from the issuer. Payment and shopper data stays in-region. The team's background is regional payments rules, scheme requirements and merchant operations. That shows up in the defaults we ship, not in a slide deck.

Start with the API reference or read how open banking settles on SEPA Instant.

Test it before you talk to anyone

Keys are free and instant. Bring a question about your vertical, your CMS or your settlement file. Write to [email protected].

Talk with sales