Menu
Talk with sales

Integration questions? [email protected]

Online payment methods — cards, wallets and local APMs on one integration.

BazPay accepts the online payment methods local shoppers actually reach for at checkout — cards, Apple Pay, Google Pay, iDEAL, Bancontact, BLIK, pay by bank, PayTo, Interac and SEPA Instant bank rails. Every method sits behind the same REST endpoint and the same signed webhook, so adding one for a new market is a dashboard toggle, not a fresh integration.

Built for merchants across the EU, UK, Australia, Canada and New Zealand. International card acceptance is included on the same regional acquiring licence — cards issued outside the region authorise and settle alongside domestic volume.

Talk with sales Read the API reference

Why one platform for every online payment method

Stitching a card gateway, a SEPA Instant provider and a pay-by-bank vendor gives you three integrations, three portals and three reconciliation flows. Four properties keep it to one.

  • One integration reaches every supported method

    Cards, wallets, local payment methods and SEPA Instant bank rails share the same REST endpoint and the same signed webhook. Adding a new online payment method for a new market is a dashboard toggle, not a fresh integration.

  • International card acceptance on the regional acquiring licence

    The card networks are global. BazPay's regional acquiring contract authorises cards issued outside the region on the same MID; the money settles into your EUR settlement account alongside domestic volume.

  • Local payment methods the way local shoppers expect

    SEPA Instant for Germany, Bancontact for the United Kingdom, BLIK for Australia, EPS for France, Przelewy24 for the United Kingdom — each renders inside its native flow through the platform, no third-party PSP layer in between.

  • One reporting surface across every method

    Every settled charge — card, wallet, APM or SEPA Instant — flows through the same interchange++ statement and the same real-time analytics. The finance team reconciles against one source, not five.

The four families of online payment methods on the platform

Four method families cover regional acceptance end to end. Card networks and device wallets for international reach; Local payment methods for native checkout; bank rails for higher-ticket and account-to-account flows.

  • Card networks

    Card acceptance — Visa, Mastercard, Cartes Bancaires, eftpos

    Card acquiring on BazPay's own regional licence. International cards issued outside the region authorise on the same contract and settle into the same EUR balance as domestic volume. 3-D Secure 2.2 runs only when the risk earns it.

    • Visa
    • Mastercard
    • Cartes Bancaires
    • eftpos

  • Wallets

    Device wallets — Apple Pay and Google Pay

    Wallet-tokenised card payments ride the same card rail with no PAN in the request. Sits behind the same charge object as a raw card charge.

    • Apple Pay
    • Google Pay

  • Regional local methods

    EU, UK and Commonwealth APMs at native checkout

    Each local payment method opens the shopper's native bank flow — SEPA Instant bank selector, Bancontact code, BLIK QR, EPS bank list, Przelewy24 hub — from the same API call.

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

  • Bank rails

    Open banking and SEPA Instant

    For higher-ticket orders or account-to-account subscriptions, open banking and BACS Direct Debit carry payments on bank rails without a card in the flow.

    • Open banking
    • SEPA
    • SEPA Instant

Method-family deep-dives: card and APM processing, iDEAL payments, Single Euro Payments Area and open banking.

Method coverage by regional market

Which methods to enable depends on where your shoppers are. The reference below shows the typical primary method per market alongside the international card set that covers everyone else.

Typical online payment method coverage by regional market
Market Primary APM Cards Wallets
Germany SEPA Instant Visa, Mastercard, American Express Apple Pay, Google Pay
the United Kingdom Bancontact + P24 Visa, Mastercard, American Express Apple Pay, Google Pay
Australia BLIK Visa, Mastercard, American Express Apple Pay, Google Pay
France EPS Visa, Mastercard, American Express Apple Pay, Google Pay
Canada Cards + CB Visa, Mastercard, Cartes Bancaires Apple Pay, Google Pay
Rest of regional Cards + SEPA Instant Visa, Mastercard, American Express Apple Pay, Google Pay
International Cards Visa, Mastercard (cross-border issuance) Apple Pay, Google Pay

Full coverage matrix on payment methods coverage. Enablement is a dashboard toggle once you are boarded.

The checkout flow, whichever method the shopper picks

Six stages describe how a payment moves through the platform. The stage sequence stays the same whether the shopper pays with a card, a wallet or a bank redirect.

  1. Present

    Your checkout surfaces the methods available for that shopper's currency and market — hosted checkout, hosted fields or a custom UI on the API.

  2. Shopper picks

    The shopper picks a method. Cards and wallets stay on-page via hosted fields; APMs redirect to the native bank or wallet flow.

  3. Authorise

    Card charges post to the acquirer with 3-D Secure bound; APM payments authenticate inside the shopper's bank environment; SEPA transfers post with a mandate reference.

  4. Confirm

    The response returns a canonical charge object with the network selected, the exemption applied and any next action for the shopper.

  5. Fulfil

    A signed charge.succeeded webhook fires — the same event handler covers every method, so fulfilment code stays uniform.

  6. Settle

    Funds reconcile per scheme cycle and land in your local settlement account with interchange++ line detail on every row.

One platform vs one vendor per method

The alternative to a unified online payment methods platform is picking one vendor per method — a card gateway, a SEPA Instant specialist and an APM connector per market. The comparison below shows the operational cost.

BazPay unified methods platform compared with one vendor per method
Dimension BazPay (unified) One vendor per method
Integration surface One REST API for every method One SDK per method vendor
Event stream One signed envelope across every rail Different formats per vendor
Reporting Interchange++ across all methods Blended summaries per vendor
International cards Non-regional issuance on regional acquiring Region-specific acquirer per market
Refund UX One dashboard action per method Different vendor portals per method
Compliance floor PCI DSS Level 1 across the platform Varies per vendor

Rate structure on the pricing page. Direct-acquirer context on merchant acquiring.

Features engineered around the method surface

Everything below ships on the standard integration. Every capability applies to every method — no premium tier for the webhook contract, the sandbox or the refund flow.

  • Unified charge object

    Set payment_method on the same request to select any method; the response object shape does not change between rails.

  • Method presenter

    Hosted checkout and drop-in components present the right methods for the shopper's market and currency automatically — no per-method UI to build.

  • Hosted fields

    Card, expiry and CVC inputs served from our PCI environment inside your existing checkout, keeping card scope out of your stack.

  • 3-D Secure 2.2 + exemptions

    Authentication runs on cards only when risk earns it; APM authentication happens natively inside the shopper's bank environment.

  • Signed webhooks

    One HMAC-signed event catalogue covers every method — approval, decline, refund, dispute and payout share the same envelope.

  • Refund flows per method

    Refunds return through each method's native flow — to the card PAN, back to the settlement account via SEPA Instant or bank transfer — from the same API or dashboard action.

  • Metadata propagation

    SKU, order and buyer references on the charge metadata ride through settlement, refund and dispute events regardless of method.

  • Interchange++ reporting

    Interchange, scheme fees and gateway margin split per settled charge; APM lines break out per scheme so the finance team sees actual costs.

One request, any online payment method

The payment_method field selects the method. Change one string and the same request accepts a card, a SEPA Instant bank redirect or a BACS Direct Debit — the response shape does not change. 

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" }
}

// Swap payment_method to "ideal", "bancontact",
// "apple_pay" or "sepa_debit" — everything else stays the same.

The response returns a canonical charge object with the network selected and any next_action required for the shopper. Full schema in the API reference.

Where the online payment methods matter

Four merchant profiles use the multi-method surface every day. Each surfaces a different mix — the platform primitives underneath are identical.

  • Multi-country e-commerce

    DTC storefronts presenting cards + Apple Pay + Google Pay + SEPA Instant + Bancontact + BLIK per market on one integration, with instant payouts to one settlement account.

  • Subscription software

    SaaS platforms preferring card-on-file for self-serve tiers and BACS Direct Debit for enterprise plans, both under one subscription reference.

  • Professional services

    B2B invoicing surfaces cards and open banking on a hosted invoice page; higher-ticket buyers pick the method that suits their finance team.

  • Digital publishers

    Membership and paywall businesses accepting card renewals plus one-off SEPA Instant, Bancontact or BLIK payments for regional audiences.

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 across every method

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 cards with 3-D Secure 2.2; on local payment methods, strong authentication runs natively inside the shopper's bank environment. GDPR is default under regional data residency.

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
Scheme rulebooks
SEPA Instant + local-payment-method scheme adherence per market

Questions merchants ask about online payment methods

Which online payment methods does BazPay support out of the box?

Card networks (Visa, Mastercard, Cartes Bancaires, eftpos), device wallets (Apple Pay, Google Pay), local payment methods (iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac) and bank rails (open banking, instant credit transfer, BACS Direct Debit, SEPA Instant). Every method shares the same charge object — enabling a new one is a dashboard toggle, not a re-integration.

Can BazPay handle international online payment processing?

Yes for card acceptance — cards issued outside the region authorise on BazPay's regional acquiring licence and settle into your EUR settlement account alongside domestic volume. BazPay is a regional acquirer, so this is international *acceptance* rather than multi-region acquiring across other jurisdictions. For merchants whose business is in-region but sells to international shoppers, this covers the practical need.

How do international online payment methods compare with regional-only ones?

Cards are the international method by design — Visa and Mastercard authorise cross-border on the same MID. Local payment methods are country-specific (SEPA Instant in Germany, Bancontact in the United Kingdom, etc.) and only settle payments from shoppers with an account at a participating bank in that country. A checkout presenting both maximises coverage for local shoppers without extra work for international ones.

Do I need to code a separate integration per payment method?

No. The payment_method field on the standard charge request selects the method — card, ideal, bancontact, sepa_debit and so on. The response shape stays constant; hosted checkout and drop-in components render the appropriate UI for each method automatically.

How do refunds work across different online payment methods?

Refunds are initiated by the same API or dashboard action regardless of method. The refund routes back through the original method's native flow — refund to the card PAN via the scheme, return to the settlement account via SEPA Instant or bank transfer. Every refund fires a signed webhook so your fulfilment stack can revoke entitlements on the same handler that processes charges.

Which currencies can I accept online payments in?

Cards and wallets support authorisation in EUR plus a broad set of presentment currencies. Local payment methods settle in EUR only, since they are Local-currency by design. Merchant settlement lands in EUR into your local settlement account by default; named settlement currencies are available for approved corridors — discuss during boarding.

Which merchant types can accept the full set of methods?

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 or a marketplace of third-party PSPs.

Does adding more payment methods slow the checkout down?

The hosted checkout and drop-in components render only the methods relevant to that shopper's currency and market, so a German shopper sees SEPA Instant and card first without a scroll of unused options. The scoring engine runs inline before authorisation, so adding a method does not add a hop to the successful path.

Pick the online payment methods your shoppers already use

Share your target markets, monthly volume and existing stack. A named engineer will confirm which methods to enable at boarding inside one working day. See also payment methods by country, the payment gateway, merchant acquiring and SEPA area processing.

Talk with sales See pricing