Menu
Talk with sales

Integration questions? [email protected]

Payment gateway options: mobile, international and recurring.

This is the choice layer of the BazPay platform: the mobile, international and recurring payment options a merchant combines to fit their markets, devices and billing model. Every option below runs on the same charge object, the same webhook stream and the same regional acquiring contract.

Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services companies. Turn options on from the dashboard as you grow; no new SDK, no new contract, no second reseller in the chain.

Talk with sales Read the API reference

Why treat the options as one set

Buying mobile, international and recurring options from three vendors multiplies the integration and reconciliation surface without earning any of it back. Four things change once the option families sit on one platform.

  • One integration, every option

    Mobile, international and recurring payment options share the same charge object, the same webhook envelope and the same dashboard. Switching an option on does not add a second SDK or a second reseller.

  • Options tuned by rule, not by rewrite

    The behaviour of each option — 3-D Secure thresholds, retry cadence, exemption logic — is configured from the dashboard. Turning on a new option in a new market is a threshold change, not an engineering release.

  • Consistent reporting across the mix

    Interchange++ line detail on every settled transaction, regardless of the option that produced it. Finance teams reconcile mobile, cross-border and subscription revenue against the same statement shape.

  • Options that BazPay actually operates

    Every option below is on the same platform BazPay operates directly. No aggregated MID, no third-party PSP layer between you and the option you switched on.

The three families of payment options

Each family below has its own deep page with method-level detail. Use this page to see them side by side and decide which combination fits your business.

  • Mobile

    Mobile payment options

    Native iOS and Android SDKs render Apple Pay, Google Pay and card entry with the same charge object as the web integration. Wallet-issued network tokens mean no PAN in the request. Shoppers pay with the biometric flow they already trust on their device.

    • Apple Pay
    • Google Pay
    • iOS SDK
    • Android SDK
    See mobile payments

  • International

    International payment options

    Direct regional acquiring accepts cards issued outside the region on the same contract. Local payment methods clear alongside cards, so a checkout in the United Kingdom reads Przelewy24 alongside Visa. Multi-currency presentment; EUR settlement into your settlement account.

    • Regional acquiring
    • Non-regional issuers
    • SEPA Instant
    • Bancontact
    • BLIK
    • EPS
    See international payments

  • Recurring

    Recurring payment options

    Card-on-file with network tokens, merchant-initiated exemptions on renewals, SEPA Instant direct-debit mandates and dunning-aware retries. One rail per subscription — pick per plan.

    • Card-on-file
    • MIT
    • SEPA Instant DD
    • Dunning
    See recurring billing

Payment-method depth on card and APM processing. Outgoing side of the flow on payouts and open banking.

How to pick an option combination

Six stages describe how BazPay walks a merchant from a shortlist of candidate options to a live configuration that a finance team can reconcile.

  1. Shortlist options

    Pick the mobile, international and recurring options that match your markets, devices and billing model.

  2. Configure defaults

    Dashboard defaults per option — 3-D Secure behaviour, retry cadence, exemption logic — are set for you at boarding.

  3. Wire one endpoint

    The same REST endpoint creates a charge for every option. The payment_method field selects between them.

  4. Test in sandbox

    Sandbox replays production-shaped traffic for each option, including 3-D Secure 2 flows and dispute events.

  5. Tune from real data

    Real-time analytics show approval and decline patterns per option. Adjust thresholds from the dashboard, no release required.

  6. Add options later

    Any option you skip at go-live can be enabled from the dashboard when the market or product changes.

One platform for every option vs one vendor per option

Sourcing mobile, international and recurring options from three separate providers used to be the default. It stopped being the default when the reconciliation and integration costs became visible. The comparison below explains where each approach breaks.

One platform vs three vendors, per option family
Dimension BazPay (one platform) One vendor per option
Mobile options Native SDKs on the same platform Third-party mobile SDK bolted on
International reach Regional acquiring + local APMs One-market only, per-region resellers
Recurring rails Cards, SEPA Instant DD, MIT exemptions Cards only, blanket 3DS
Options config Dashboard thresholds, no release Engineering ticket per change
Reporting Interchange++ across every option Blended summary per vendor
Failure surface One signed webhook envelope Per-option event formats

Statement structure on the pricing page. Plugin coverage on integrations. Direct acquiring on merchant acquiring.

Features shared across every option

Everything below applies to every option you enable. Turn features on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives.

  • Hosted fields

    Card entry inside our PCI environment for every option that uses raw PAN. Merchant SAQ A scope is preserved regardless of which options are on.

  • Network tokens

    Visa and Mastercard network tokens across mobile wallets and card-on-file, so saved payment options survive card reissue automatically.

  • 3-D Secure 2.2 engine

    Frictionless flow first; PSD2 exemption logic claims TRA, low-value, trusted-beneficiary and MIT — the same engine across every option.

  • SEPA and SEPA Instant

    Account-to-account rails for higher-ticket international options where cards are not the preferred method, plus fast merchant payouts.

  • Dunning retries

    Retry cadence for failed recurring charges is a dashboard setting per plan; MIT exemptions keep renewals frictionless where PSD2 allows.

  • Signed webhooks

    HMAC-signed, replay-protected events for every option; one signature scheme end to end, one handler for every payment type.

  • Idempotent requests

    Retry-safe create requests across every option. A network blip during a mobile checkout is safe to retry with the same key.

  • Interchange++ reporting

    Interchange, scheme fees and gateway margin split on every settled transaction, whichever option produced it.

One REST call switches between options

The charge object is the unit of work across every option. Selecting between mobile, international and recurring options is one field on the request. The response object, the webhook envelope and the reconciliation report keep the same shape whichever option handled the transaction. 

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
  "amount": 1900,
  "currency": "EUR",
  "payment_method": "card",
  "customer": "cus_5F9k",
  "subscription": "sub_2H9F...",
  "off_session": true,
  "three_d_secure": "required_if_needed",
  "metadata": { "plan": "pro_monthly" }
}

Switch payment_method to apple_pay for a mobile option, or sepa_debit for a dollar account-to-account recurring option — the rest of the request is unchanged. The complete schema lives in the API reference.

Where option combinations differ by business type

The default option mix that ships to a merchant depends on the vertical. Four common profiles are below; every combination is dashboard-tunable after go-live.

  • Mobile-first commerce

    Native app checkouts using Apple Pay and Google Pay, wired to the same account and reporting as the web storefront — the mobile payment options and web options share a vault.

  • Multi-country e-commerce

    One acquiring contract for regional storefronts on Shopware, Magento 2, WooCommerce or PrestaShop. Local card acceptance and local APMs without stitching regional PSPs.

  • Subscription software

    Card-on-file and SEPA Instant DD options per plan, MIT exemptions on renewals and dunning-aware retries — the recurring options a SaaS billing team actually needs.

  • Professional services

    Higher-ticket invoices with named-payer trust lists and enforced 3-D Secure 2 over a ceiling you set. International payer scenarios covered on the same contract.

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

Security and compliance across every option

Compliance signals are not per-option add-ons — they are floor-level requirements that every option below runs against. PCI DSS Level 1 on the platform, merchant SAQ A on your side, and authentication with automatic exemption logic on every card charge.

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 option
GDPR
In-region data residency; DPA on request
SEPA / SEPA Instant
Direct participation for supported corridors

Questions merchants ask about payment gateway options

How should I decide which payment gateway options to turn on?

Start with the option families your shoppers already use — mobile payment options where a large share checks out from a phone, international payment options where you sell across borders, recurring payment options where the business model is subscription or membership. BazPay's boarding conversation runs this exercise for every merchant, and every option is a dashboard toggle so a wrong call at go-live is recoverable.

Which mobile payment options are supported?

Apple Pay and Google Pay on native iOS and Android SDKs, plus hosted card entry that renders inside our PCI scope on mobile browsers. Wallet payments use network tokens, so the shopper's PAN never touches your app. The same charge object handles a mobile authorisation as a web one.

How do international payment options work on a regional acquiring contract?

The BazPay acquiring licence is local, but the card networks are global. A card issued outside the region authorises on the same contract as a domestic one and settles into the same balance. Alongside cards, local payment methods clear through the same platform for markets where a bank-issued APM is the dominant checkout option.

Which recurring payment options fit a subscription business?

Card-on-file with network tokens is the default. MIT (merchant-initiated transaction) exemptions apply automatically on renewals where PSD2 allows. BACS Direct Debit is available as an alternative option for local-currency books. Dunning retries and grace-period settings are configured per plan from the dashboard.

Can I switch options on and off after go-live?

Yes. Adding a new option or turning one off is a dashboard action for authorised users. Underlying underwriting policy is unchanged; the API surface does not move. Rule-level behaviour — 3-D Secure thresholds, retry cadence, exemption logic — is dashboard-configurable per option.

How are these options priced together?

Every option is priced on its own line. Card options run on interchange++, so scheme fees, interchange and the BazPay margin appear separately on each transaction. Local payment methods carry their own scheme rate; Instant rails have their own line. Nothing is blended into a headline card rate. Current schedules live on the pricing page.

Are there option combinations BazPay will not underwrite?

Options themselves are not the constraint — the merchant profile is. BazPay boards EU, UK and Commonwealth e-commerce, subscription software, professional services and digital publishers. Any combination of mobile, international and recurring options within that scope is available. Out of scope: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.

Do you offer more exotic options like BNPL or crypto?

No. BazPay is focused on card, wallet, local payment methods and SEPA Instant account-to-account rails. Buy-now-pay-later, cryptocurrency and consumer wallet products are not in scope for the current option set. If a market you sell in requires a specific method not covered here, the acquiring team can confirm whether it is on the near-term roadmap during boarding.

Shortlist your option combination

Share your business model, markets and billing pattern. An integration manager will map the option set for you within one working day — see also mobile payments, international payments and recurring billing for method-level detail.

Talk with sales See all products