Menu
Talk with sales

Integration questions? [email protected]

Subscription payment gateway for SaaS, memberships and content businesses.

BazPay is a subscription payment gateway built to defend the renewal, not just to charge the first card. Network tokens refresh on issuer reissue, MIT exemptions keep rebills frictionless, dunning-aware retries recover soft declines, and every subscription event flows through one signed webhook stream.

Built for regional subscription businesses: SaaS platforms, membership and content sites, DTC subscription boxes and professional-services firms on recurring retainers. One direct regional acquirer, one dashboard, one interchange++ statement.

Talk with sales Read the recurring billing page

Why subscription businesses pick a purpose-tuned gateway

A subscription book lives and dies on the renewal. Four properties keep renewals warm and reporting honest — the difference between silent churn and durable ARR.

  • Renewals survive card reissues

    Card-on-file is stored as Visa or Mastercard network tokens. When a shopper's issuer reissues their card, the token refreshes automatically — the next renewal charges through without a fresh checkout.

  • MIT exemptions on rebills, not blanket 3-D Secure

    PSD2's merchant-initiated-transaction exemption applies to legitimate renewals of a stored subscription. BazPay claims it automatically; the shopper does not see a 3-D Secure challenge on every monthly charge.

  • Dunning-aware retry cadence

    Soft declines are re-attempted on a schedule you configure per plan. The retry logic reads the reason code so recoverable declines get a second chance and unrecoverable ones drop straight into your dunning flow.

  • One reporting surface for subscription revenue

    Every renewal, upgrade, downgrade, refund and dispute rides through the same signed webhook stream keyed to your subscription reference. Finance closes the book against one schema; the growth team reads MRR against one ledger.

The subscription payment model on the platform

Four objects and event types make up the subscription-payment surface. Everything from a first charge to a mid-cycle plan change to a card reissue ends up on the same subscription reference.

  • Subscriptions

    Subscription objects and plans

    Define plans with amount, currency and cycle. Attach a customer, a payment method and a subscription reference. The platform runs the renewal schedule; you receive a signed webhook on each successful invoice.

    • Plan
    • Customer
    • Subscription reference

  • Card-on-file

    Vault + network tokens

    Card credentials sit inside the PCI DSS Level 1 environment. Network tokens replace stored PAN and refresh automatically on reissue. Portable if you ever migrate infrastructure.

    • Gateway vault
    • Network tokens
    • Portable

  • Invoices

    Invoice events per cycle

    Every cycle produces a signed invoice.paid or invoice.failed event with the plan, seats, tax metadata and the interchange++ line. Your billing service updates entitlement in the same handler that processes charges.

    • invoice.paid
    • invoice.failed
    • Metadata

  • Alternate rails

    BACS Direct Debit for enterprise plans

    For higher-ticket plans where a bank-mandate cadence fits better than a card, BACS Direct Debit runs against a stored mandate. Same subscription reference, different rail on the same platform.

    • BACS mandates
    • Enterprise tiers

Recurring-billing primitives on recurring billing. The acceptance breadth on payment acceptance.

A subscription's lifecycle, end to end

Six stages describe how a subscription moves from the first sign-up charge to a settled monthly renewal. Each stage fires a signed webhook keyed to the subscription reference.

  1. Sign-up

    First charge runs interactively with 3-D Secure 2.2 if the risk earns it. The card is tokenised for future renewals.

  2. Store credential

    The gateway vault issues a stable token keyed to your merchant. Network-token services keep it warm across reissues.

  3. Wait for cycle

    The subscription schedule fires on cadence. Trial-to-paid conversions, add-on charges and proration all sit on the same object.

  4. Rebill

    Renewals fire as merchant-initiated charges. MIT exemptions default; step-up only where the issuer or your rules require it.

  5. Handle declines

    Soft declines retry on a schedule you configure. Hard declines drop into the dunning flow with a signed invoice.failed event.

  6. Settle + report

    Successful renewals land in your local settlement account per scheme cycle. Interchange++ line detail per invoice for finance reconciliation.

Subscription-tuned gateway vs generic e-commerce gateway

Generic gateways can charge a card once. A subscription-tuned gateway defends the second, third and twelfth charge. The comparison below shows where the gap lands on a renewal book.

BazPay subscription-tuned gateway compared with a generic e-commerce gateway
Dimension BazPay (subscription-tuned) Generic e-commerce gateway
Renewal safety Network tokens refresh on reissue Rebills fail after a card reissue
3-D Secure on rebills MIT exemption default Blanket 3DS or none
Retry logic Reason-code-driven, per-plan cadence Single fixed schedule
Proration Automatic on upgrades/downgrades Manual invoice adjustments
Reporting Interchange++ per invoice Blended-rate monthly summary
Bank-rail alternative BACS Direct Debit on the same subscription Card-only
Underwriting scope Regional subscription merchants Broad, few exclusions

Rate structure on the pricing page. Ecommerce sibling on payment gateway for ecommerce. Card-method depth on card and APM processing.

Features engineered into the subscription payment software

Every capability below is on the standard integration. No premium tier gates network tokens, MIT exemptions or the retry schedule — the primitives that defend renewals are the platform.

  • Plans and cycles

    Monthly, annual and custom cadences. Trial-to-paid, per-seat pricing and usage-metered add-ons attach to the subscription reference.

  • Card-on-file + network tokens

    Stored credentials inside our PCI Level 1 environment; automatic PAN refresh via Visa and Mastercard token services keeps renewals warm.

  • MIT exemption logic

    Merchant-initiated SCA exemption applied on eligible renewals so shoppers do not face 3-D Secure on every monthly charge.

  • Dunning-aware retries

    Reason-code-driven retry schedule you configure per plan — recoverable declines get a second chance without an angry email.

  • Proration and mid-cycle changes

    Upgrades, downgrades and seat changes compute proration automatically and fire the next invoice with the new amount.

  • Signed webhooks

    invoice.paid, invoice.failed, subscription.updated, refund.created — one HMAC signature scheme across every subscription event.

  • Real-time retention data

    Approval, decline, retry and dispute outcomes per subscription visible within seconds in real-time analytics.

  • BACS Direct Debit for enterprise

    Where a bank mandate suits the customer, BACS Direct Debit rebills against a stored mandate — same subscription reference, different rail.

The subscription-charge API is the same charge object

Subscriptions do not need a separate SDK. Attach a subscription reference to the charge and the platform applies the merchant-initiated behaviour — MIT exemption, stored-credential rebill, retry-on-decline. Signed invoice events fire per cycle. 

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
  "amount": 4900,
  "currency": "EUR",
  "payment_method": "card",
  "customer": "cus_5F9k",
  "subscription": "sub_2H9F",
  "capture": "auto",
  "off_session": true,
  "metadata": { "plan": "pro_annual", "seats": 12 }
}

The response returns the canonical charge object with the plan reference, MIT flag and any exemption applied. Read the full schema in the API reference.

Where subscription payment solutions land in the wild

The four merchant profiles below already run BazPay-tuned subscription flows. Each gets the same API surface, the same event catalogue and the same renewal-safety defaults.

  • SaaS platforms

    Monthly and annual plans, trial-to-paid conversions, per-seat billing and add-on charges — the acceptance layer that stays warm across card reissues so ARR does not silently churn.

  • Membership and content sites

    Publishers, courses and community memberships charging monthly or annual fees, with dunning-aware retries and metadata per SKU for finance.

  • DTC subscription boxes

    Physical-goods subscriptions on monthly or bi-monthly cadences, with card-on-file renewals and hosted-checkout signup pages.

  • Professional-services retainers

    Consultancies and agencies invoicing recurring retainers on card or BACS Direct Debit, with named-payer trust lists and enforced 3DS 2 over a ceiling you set.

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.

Compliance signals for subscription payment services

Card handling runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields and gateway vaulting keep your annual return at merchant SAQ A. Authentication runs on every card charge with automatic exemption logic — MIT on renewals, risk analysis and low-value on qualifying flows — so subscription rebills stay frictionless.

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 including MIT on renewals
GDPR
In-region data residency; DPA on request
SEPA and BACS rulebooks
BACS mandate storage adheres to the BACS mandate rulebooks

Questions subscription businesses ask before switching

What makes a subscription payment gateway different from a regular one?

A subscription payment gateway defends the renewal — network-tokenised card-on-file, MIT exemptions on rebills, dunning-aware retry logic and proration on plan changes. A regular gateway can charge cards, but the subscription-specific features that stop silent churn are either absent or bolted on. BazPay ships them as defaults.

How does BazPay's subscription payment processing handle card reissues?

Card credentials are stored as Visa or Mastercard network tokens rather than raw PAN. When the issuer reissues the shopper's card, the network token service refreshes the token automatically. The next renewal charges through without asking the shopper to re-enter their card — the most common source of silent subscription churn is removed.

Does the subscription payment platform require 3-D Secure on every renewal?

No. Open-finance regulation defines a merchant-initiated-transaction exemption that applies to legitimate renewals of a stored subscription; BazPay claims it automatically. Renewals rebill without a challenge. If the issuer or your risk rules demand a step-up on a specific transaction, the platform routes to 3-D Secure 2.2 for that charge only.

How does the subscription payment management surface handle declines and dunning?

Soft declines are re-attempted on a schedule you configure per plan; the retry logic reads the reason code so recoverable declines (temporary issuer errors, insufficient funds around payday, network blips) get a second chance. Hard declines drop into your dunning flow immediately with a signed invoice.failed event that your billing service handles.

Which subscription payment models does the platform support?

Monthly and annual cycles, custom cadences (weekly, bi-monthly, quarterly), trial-to-paid conversions, per-seat pricing with automatic proration on seat changes, usage-based metered add-ons and one-off charges layered on top of a subscription. All ride the same subscription reference and settle into the same balance.

Can I collect subscription payments online via BACS Direct Debit as well as cards?

Yes. For higher-ticket enterprise plans or customers who prefer a bank mandate, BACS Direct Debit runs against a stored mandate on the same subscription. The subscription reference stays the same; only the rail differs. Cards and BACS Direct Debit both feed the same invoice events.

Which merchant profiles fit BazPay's subscription payment services?

Merchants across the EU, UK, Australia, Canada and New Zealand: subscription software (SaaS), membership and content platforms, DTC subscription boxes on verticals and professional-services firms on recurring retainers. 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 does monthly subscription payment processing appear in reporting?

Every monthly renewal fires a signed invoice.paid event with the plan reference, seat count, tax metadata and the interchange++ breakdown. Real-time analytics show approval, decline and retry outcomes per subscription; interchange++ statements settle in your local settlement account per scheme cycle with per-invoice line detail.

Move renewals to a subscription payment gateway that defends them

Share your subscription model, monthly volume and existing gateway. A named engineer will confirm boarding fit and map the vault migration inside one working day. See also pricing, payment acceptance and merchant acquiring.

Talk with sales Read the developer docs