Menu
Talk with sales

Integration questions? [email protected]

Accept online payments without stitching a gateway to a separate merchant bank.

BazPay bundles the payment gateway and the regional acquirer into one contract. You accept payments online on cards, wallets and local methods through one REST API, authorise on our acquiring licence and settle into your own business settlement account. No aggregator on top, no separate merchant bank to open before you go live.

Built for merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms and professional-services businesses. Sandbox on day one, live keys after underwriting, named support during onboarding.

Talk with sales Read the API reference

Why merchants pick BazPay to start accepting payments

Four things stay true whether you take your first ten euros or your thousandth transaction of the day. They are the reasons a merchant new to accepting payments picks a direct regional acquirer over stitching a gateway to a separate bank.

  • One provider covers gateway and acquirer

    Traditional setups pair a gateway with a separate merchant bank account and a third acquiring relationship. BazPay bundles gateway and regional acquirer into one contract, so you accept payments online, authorise on our licence and settle into your regular business settlement account.

  • Accept the payment methods your shoppers already use

    Cards, Apple Pay, Google Pay and local payment methods share the same API call. Turn any method on from the dashboard — no new integration to add SEPA Instant or Bancontact for a new market.

  • Sandbox on day one, live keys after underwriting

    Sign up, get sandbox credentials immediately, integrate against production-parity data, then flip to live after merchant underwriting completes. No demo call gate on the sandbox.

  • Predictable regional compliance posture

    PCI DSS Level 1 on the gateway side, merchant SAQ A on yours, authentication with 3-D Secure 2.2 by default, GDPR under In-region data residency. The compliance floor is built in.

The payment methods you can accept on one contract

Four method families sit behind the same API call. Turn any of them on from the dashboard as you enter a new market or add a new checkout surface.

  • Cards

    Card acceptance on your own MID

    Visa, Mastercard, Cartes Bancaires and eftpos clear on BazPay's own regional acquiring licence. Your merchant identifier is named to your entity, so chargeback attribution and settlement reporting are clean.

    • Visa
    • Mastercard
    • Cartes Bancaires
    • eftpos

  • Wallets

    Apple Pay and Google Pay

    Device wallets ride the same card rails through a wallet-supplied network token. No PAN in the request, no extra credential to store on your side.

    • Apple Pay
    • Google Pay

  • Local methods

    Local alternative payment methods

    Local payment methods sit behind the same API call as card charges. Turn any of them on from the dashboard when you enter a new regional market.

    • iDEAL
    • Bancontact
    • BLIK
    • Pay by bank
    • PayTo
    • Interac

  • Bank rails

    Open banking and SEPA Instant

    For higher-ticket orders or subscription renewals, offer pay-by-bank via open banking; for outbound flows, SEPA and SEPA Instant carry payouts on approved corridors.

    • Open banking
    • SEPA
    • SEPA Instant

Method depth on card and APM processing. Bank-rail detail on open banking. Popular German method: iDEAL payments. Broader regional rails: Single Euro Payments Area processing.

From sign-up to your first accepted online payment

Six stages describe the path a merchant walks from signing up to receiving the first settled dollar. Sandbox and integration work happen in parallel with underwriting.

  1. Sign up

    Open a BazPay account and receive sandbox credentials in the same minute. Documentation and the API reference are self-serve.

  2. Choose a surface

    A storefront plugin, a hosted checkout page or hosted fields inside your existing checkout — pick the surface that matches your build.

  3. Wire the webhook

    Verify a signed webhook on charge.succeeded. That single event tells your system when to release goods, activate a subscription or send a receipt.

  4. Test in sandbox

    Replay approvals, declines and 3-D Secure 2 flows against production-parity data. Sandbox behaviour matches the live surface.

  5. Complete underwriting

    Submit KYC documents and a short business summary. Merchants across the EU, UK, Australia, Canada and New Zealand typically clear underwriting in days, not weeks.

  6. Go live

    Live keys enabled. Real-time analytics show approval quality from the first hour and payouts start settling to your local settlement account per scheme cycle.

Direct acquirer vs aggregator: what changes for the merchant

An aggregator lets you accept online payments in minutes on a shared MID. A direct acquirer takes a few more days at boarding and pays back in reporting quality, chargeback attribution and settlement timing. The comparison below shows where each model earns its keep.

BazPay direct acquirer compared with an aggregator model for online payments
Dimension BazPay (direct acquirer) Aggregator
Contract Direct with BazPay as acquirer Aggregator on shared MID
MID Named to your legal entity Shared across the aggregator's pool
Chargeback attribution Attributed to your MID Diluted across the pool
Reporting Interchange++ line detail Blended-rate summary
Payout To your own local settlement account, per scheme cycle Aggregated payout, common delay
Underwriting Merchants across the EU, UK, Australia, Canada and New Zealand, direct review Broad, few exclusions

Fees and settlement on the pricing page. Buyer's shortlist on payment processors; boarding on merchant acquiring. Breadth-of-coverage view on payment acceptance. Platform security posture on secure online payment systems and secure payment services.

Features you get on day one

Every capability below ships on the standard integration. Turn features on with a request flag or a dashboard toggle — no premium tier gates hosted fields, plugins or the sandbox.

  • Hosted checkout page

    Redirect to a BazPay-hosted page for the fastest way to start accepting payments online without touching card data.

  • Hosted fields

    Card, expiry and CVC inputs served from our PCI environment inside your own checkout, so you accept card payments without collecting PAN.

  • Storefront plugins

    Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware install into your existing storefront in minutes.

  • REST API + signed webhooks

    One versioned endpoint creates a charge; every state change emits an HMAC-signed, replay-protected event.

  • 3-D Secure 2.2 with exemptions

    Authentication runs only when the risk earns it — most checkouts stay frictionless, and liability shifts on the ones that don't.

  • Refunds and disputes

    Full and partial refunds by API or dashboard. Dispute evidence is pre-assembled with the 3-D Secure 2 result and charge metadata.

  • Real-time decline data

    Approval, decline and retry outcomes visible within seconds — see why a charge failed and act on the reason code inside the same hour.

  • SEPA / SEPA Instant payouts

    Settlement lands in your local settlement account per scheme cycle. Instant payouts available on approved corridors.

One REST call to accept a payment online

Once your API key is live, the request that accepts a payment is short. Attach amount, currency and payment method; the response returns a canonical charge object with the authorisation code and any next action required (a 3-D Secure challenge, for example). 

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

Full schema in the API reference, handler samples in the developer docs. Prefer to skip code? A hosted checkout page or a hosted checkout product accepts payments with no server-side integration at all.

Who accepts online payments through BazPay

Four merchant profiles fit BazPay's regional underwriting. Each accepts the same set of payment methods and shares the same API surface — the reporting emphasis differs by business type.

  • First-time online sellers

    A DTC brand launching a regional storefront. Install a plugin, wire the webhook, go live once underwriting clears. No prior payments experience needed.

  • Subscription businesses

    SaaS and membership sites billing monthly or annually with card-on-file renewals, MIT exemptions and dunning-aware retries.

  • Professional services

    Consultancies and B2B service firms sending hosted-page invoices with card and open-banking payment options.

  • Multi-country e-commerce

    Sellers expanding into new regional markets. One contract, one dashboard, local card acceptance and APMs turned on per market.

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 does not act as a marketplace of third-party PSPs.

Security and compliance the moment you start accepting payments

Card handling runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields and gateway-side vaulting keep your annual return at merchant SAQ A. Authentication runs on every card charge with 3-D Secure 2.2 and automatic exemption logic. Regional data residency is default, not tier-gated.

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 merchants ask before accepting their first online payment

How do I start to accept online payments with BazPay?

Sign up for an account, receive sandbox credentials in the same minute, integrate against a storefront plugin or the REST API, then submit KYC documents for underwriting. Merchants across the EU, UK, Australia, Canada and New Zealand typically clear underwriting in days and go live with card, wallet and regional APM acceptance in one integration.

Can I accept payment online without a merchant account in the traditional sense?

You do not need to open a separate merchant bank account before boarding. BazPay is the regional acquirer, so the merchant-account relationship is bundled into your BazPay contract. Settlement lands in your regular business settlement account once boarding is complete. BazPay is not an aggregator sitting on someone else's licence — it is a direct regional acquiring relationship in one step.

Which payment methods can I accept online through the platform?

Cards (Visa, Mastercard, Cartes Bancaires, eftpos), device wallets (Apple Pay, Google Pay) and local payment methods (iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac). Every method shares the same charge object, so "accept all payment methods" is a dashboard toggle, not a re-integration.

Is there a payment accept app I can use, or is it API-only?

BazPay is a payment gateway and API rather than a merchant-side app. The dashboard is web-based for staff to run refunds, review disputes and configure fraud rules. iOS and Android SDKs are available for merchants who build their own in-app checkout — those are integration SDKs, not stand-alone merchant apps.

How much does it cost to accept payment online with BazPay?

Card processing runs on interchange++, so the interchange, scheme fees and processor margin appear as separate lines on every settled transaction. Local payment methods carry their own scheme rates. The current schedule and any monthly minimums live on the pricing page.

Do I have to run a full PCI environment to accept card payments online?

No. Hosted fields and gateway-side vaulting keep card data inside our PCI DSS Level 1 scope, so your annual return stays at merchant SAQ A. Your engineering team never handles a live PAN.

Which merchant profiles can accept payments through BazPay?

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 does not act as a merchant of record.

How fast do funds actually reach my bank once we start accepting payments?

Card payments settle per scheme cycle into your local settlement account once boarding is complete. SEPA Instant is used for payouts on approved corridors, so funds arrive within seconds where both banks participate. Standard SEPA Instant settles the same or next business day.

Start accepting online payments in-region today

Share your business model, monthly volumes and existing stack. A named engineer will confirm boarding fit and map the integration inside one working day. See also gateway services, payments solutions, recurring billing and payouts.

Talk with sales See pricing