Menu
Talk with sales

Integration questions? [email protected]

SaaS payments and subscription billing on a direct acquirer.

BazPay is a saas payment gateway for regional SaaS teams — network-tokenised card-on-file renewals, MIT exemptions on qualifying rebills, dunning-aware retries and proration on plan changes, all on the same charge object as one-off checkouts.

Built for regional B2B, prosumer and usage-based SaaS. Direct regional acquirer under the hood, merchant SAQ A on your side, GDPR-native data residency and one signed webhook stream across the whole billing surface.

Talk with sales Read the API reference

Why SaaS teams pick a purpose-tuned saas payment platform

SaaS revenue lives on renewals; a payment platform that silently churns them costs more than a few missed transactions. Four properties keep the subscription book warm.

  • Renewal-safe subscriptions

    Network-tokenised card-on-file keeps saved cards alive after issuer reissue. MIT exemptions on qualifying rebills avoid unnecessary 3-D Secure challenges. Dunning-aware retries recover soft declines automatically — a card renewal cycle that does not silently churn paying accounts.

  • Primitives your billing code already needs

    Plans, subscriptions, invoices, proration on upgrade or downgrade, trial-to-paid transitions, add-on charges and usage-based metered lines are all first-class on the same charge object your one-off checkout uses.

  • Low PCI scope for a small team

    Hosted fields keep raw PAN out of your stack; the gateway vault stores credentials inside our PCI DSS Level 1 environment. Your annual return stays at merchant SAQ A — no full PCI environment to build for the billing surface.

  • Finance-team-friendly reporting

    Every settled subscription charge splits interchange, scheme fees and gateway margin per line. MRR reconciliation against your product ledger uses the same schema as one-off orders — one source of truth across the revenue book.

Subscription-billing capabilities on the platform

Four capability families cover the subscription surface a SaaS team actually needs: plans and trials, proration on plan changes, dunning-aware retries and MIT exemption logic on rebills.

  • Plans + trials

    Plans, trials and pricing

    Monthly, annual and custom-cadence plans on the same subscription object. Free trials convert into paid subscriptions automatically at the end of the trial window; trial extensions are a single API call.

    • Monthly
    • Annual
    • Trial-to-paid
    • Custom cadence

  • Proration

    Proration on upgrades and downgrades

    Plan changes generate proration credits and charges automatically. Upgrades bill the difference; downgrades either credit the current cycle or defer to renewal, per your policy.

    • Prorate now
    • Credit later
    • Downgrade defer

  • Dunning

    Dunning-aware retry cadence

    Soft declines retry on a schedule you set; hard declines go straight to your dunning stack. Network-token refresh runs on issuer reissue so your renewal book does not silently churn.

    • Retry windows
    • Reason-code aware
    • Token refresh

  • MIT

    MIT exemptions on rebills

    Merchant-initiated transaction exemptions run on qualifying renewals — the subscription charge posts with the stored-credential flag under PSD2, avoiding an unnecessary shopper prompt.

    • MIT flag
    • Stored credential
    • Frictionless rebill

Deeper billing detail on recurring billing. The engineering foundation on payment infrastructure. The fintech-vertical variant on fintech payment solutions.

From sign-up to steady-state renewals

Six stages describe the life of a SaaS subscription on the platform — sign-up, first charge, renewal, retry on decline, plan changes and reconciliation. Each stage fires a signed webhook keyed to the subscription reference.

  1. Sign up

    The shopper signs up on your product. Hosted fields render the card inputs inside your existing checkout inside BazPay's PCI environment.

  2. Trial or first charge

    A free trial starts on the subscription object, or the first charge posts through 3-D Secure 2 with the credential stored for renewals.

  3. Renewal

    The subscription generates a renewal invoice on schedule. The charge posts with an MIT exemption where PSD2 allows, using the network-tokenised card-on-file.

  4. Retry on decline

    If a renewal soft-declines, the platform retries on the cadence you set. Hard declines fire a signed event to your dunning stack for shopper outreach.

  5. Plan changes

    Upgrades, downgrades and add-ons post proration credits or charges on the same subscription. Every change fires a signed event.

  6. Reconcile

    Settlements land in your local settlement account with interchange++ line detail per subscription and invoice — one schema for one-off and recurring revenue.

SaaS-tuned gateway vs generic e-commerce gateway

A generic e-commerce gateway can process a card and issue a token; a saas payment system needs the subscription primitives that live above that layer. The comparison below shows where the gap actually lands during operations.

BazPay SaaS-tuned platform compared with a generic e-commerce gateway
Dimension BazPay (SaaS-tuned) Generic e-commerce gateway
Billing primitives Native subscription object + proration Bolt-on billing SDK on top of one-off charges
Renewal safety Network tokens + MIT exemption engine Rebills fail after card reissue
Dunning Reason-code-aware retry cadence Manual retry or none
Reporting Interchange++ per subscription line Blended-rate monthly summary
Event stream One signed envelope for one-off + subscription Different formats per vendor
Underwriting scope Regional SaaS merchants Broad, few exclusions

Rate structure on the pricing page. Service envelope on gateway services. Security posture on secure payment services.

Features engineered for saas payment processing services

Every capability below is on the standard integration. No premium tier gates the subscription object, network-token renewal, dunning cadence or MIT exemption logic — the primitives are the platform.

  • Subscription object

    One resource models plans, trials, renewals, upgrades, downgrades and cancellations. Metadata rides through every event linked to it.

  • Network tokens on renewals

    Visa and Mastercard network tokens replace PAN on stored credentials; automatic refresh after issuer reissue keeps renewals warm.

  • MIT exemption engine

    Merchant-initiated exemptions requested on qualifying rebills — the 3-D Secure prompt fires only when the rules require it.

  • Dunning-aware retries

    Configurable retry windows on soft declines with reason-code-aware backoff. Hard declines go to your dunning outreach immediately.

  • Invoicing + proration

    Invoices are first-class objects with line items, credits and taxes. Proration runs automatically on plan changes.

  • Hosted checkout for SaaS

    Prebuilt subscription-signup pages render your plan mix and collect the card credential without any front-end code on your side.

  • Signed webhooks

    HMAC-signed, replay-protected events for every subscription state change — subscribed, renewed, upgraded, cancelled, disputed.

  • Interchange++ reporting

    Every settled subscription charge breaks out interchange, scheme fees and gateway margin. MRR reconciliation lines up with the ledger.

A subscription in the shape a SaaS engineer expects

One versioned REST endpoint creates the subscription. Attach the plan, customer reference, seats and any tax metadata; the same fields ride through every renewal invoice, proration credit and dispute event. 

POST /v1/subscriptions
Idempotency-Key: 8f1c-2b3a-9e4d
BazPay-Version: 2026-04-01
{
  "customer": "cus_5F9k",
  "plan": "pro_annual",
  "quantity": 12,
  "trial_days": 14,
  "payment_method": "pm_02H9",
  "metadata": { "workspace": "acme-eu" }
}

The response returns the subscription object with the trial-end date and the next billing anchor. Read the full schema in the API reference.

Where SaaS teams run BazPay for their subscription revenue

Four SaaS profiles already rely on BazPay to bill their own customers. Each uses the same subscription object and the same signed event stream.

  • B2B SaaS with annual contracts

    Enterprise plans on annual billing with card-on-file renewals or BACS Direct Debit mandates for higher-ticket buyers, and MIT exemptions on the automatic renewal cycle.

  • Prosumer / self-serve SaaS

    Monthly plans with self-serve upgrades, downgrades, trial-to-paid conversions and add-on charges — all on the same subscription reference.

  • Usage-based / metered SaaS

    Usage lines added to invoices during the cycle, prorated cleanly against seat-based or feature-based fees when the plan changes mid-cycle.

  • Multi-currency regional SaaS

    Regional SaaS vendors serving buyers across the union; card acceptance across every country with BACS Direct Debit for enterprise plans on the same platform.

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 resell payments as embedded finance.

Security and compliance for a SaaS billing surface

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 first charges through 3-D Secure 2.2; MIT exemptions apply to qualifying rebills. In-region data residency and GDPR are default, not a tier upgrade.

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 on first charges; MIT exemption on qualifying rebills
GDPR
In-region data residency; DPA on request
SEPA / SEPA Instant
Direct participation for merchant payouts in supported corridors

Questions SaaS teams ask about subscription payments

What kind of SaaS payments does the BazPay platform handle?

Subscription revenue for regional SaaS teams — monthly and annual plans, trial-to-paid conversions, upgrades and downgrades with proration, add-on charges and usage-based metered lines. Everything runs on the same charge object as one-off checkouts, with a subscription reference that ties events together.

How does the saas payment gateway keep renewals from silently churning?

Two layers. Network tokens replace the stored PAN and refresh automatically through Visa and Mastercard token services when an issuer reissues a card, so the credential stays valid. Dunning-aware retries pick up soft declines with reason-code-aware backoff. Hard declines fire a signed event so your dunning outreach starts immediately.

What is a merchant-initiated (MIT) exemption, and how does it apply to saas payment processing?

MIT is one of the SCA exemptions the scheme rules allow for stored-credential transactions where the shopper does not initiate the payment — for example, an automatic renewal on file. BazPay's engine claims the exemption on qualifying rebills so the 3-D Secure prompt fires only when the rules require it. Approval quality on renewals stays high without a shopper interruption.

How does the platform handle proration on plan upgrades and downgrades?

Proration runs on the subscription object. Upgrades generate an immediate prorated charge for the delta on the current cycle; downgrades either credit the current cycle or defer to renewal, whichever your policy sets. Each proration line appears on the invoice with its own SKU-level metadata for reconciliation.

Is this a payment processing SaaS in the merchant-of-record sense?

No. BazPay is a direct regional acquirer and gateway, not a merchant of record. Your SaaS entity remains the seller of record on the shopper's card statement, is responsible for tax collection and filing, and holds the customer contract. BazPay processes the payment; the commercial relationship stays with you.

Can we mix card and BACS Direct Debit on the same subscription?

Yes. Enterprise plans often prefer BACS Direct Debit with a stored mandate; self-serve tiers typically use card-on-file. The subscription reference is the same object either way — dunning-aware retries and reporting cover both rails.

Which merchant profiles fit the saas payment platform?

Regional SaaS: accounting, expense management, invoicing, treasury, insurance-tech, wealth-tech, dev tools, project management, CRM, workflow automation, security tooling and similar categories. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants; those verticals fall outside our underwriting scope.

How do we migrate an existing subscription book to BazPay?

Vault imports and network-token portability are supported under scheme-approved migration processes. Existing card-on-file credentials transfer across (subject to the receiving bank's consent letters), and old and new webhook streams can run in parallel through the cutover to prove traffic on the new stack before switching entirely.

Move SaaS billing onto a direct regional acquirer

Share your subscription model and monthly recurring revenue. A named engineer will confirm boarding fit and map the migration inside one working day. See also pricing, fintech payment solutions and gateway services.

Talk with sales Read the developer docs