Menu
Talk with sales

Integration questions? [email protected]

Fintech payment solutions for SaaS and B2B tooling companies.

BazPay is a fintech payment gateway for regional software businesses — accounting, expense, treasury, insurance and wealth-adviser SaaS. One versioned REST API for acceptance, subscription billing and payouts, backed by direct regional acquiring and PSD2-compliant strong authentication.

The platform bills your fintech SaaS's own customers. It does not resell payments as embedded finance, does not act as a merchant of record and does not support crypto exchange, forex or CFD merchants.

Talk with sales Read the API reference

Why fintech engineering teams pick BazPay for their acceptance layer

A fintech SaaS building on payments needs the acceptance layer to feel like the rest of its stack — API-first, event-driven, versioned and small on operational surface. Four things are true here by default.

  • API-native, built for fintech engineering teams

    One versioned REST endpoint, idempotent writes, signed webhooks and a documented deprecation window. The primitives a fintech engineering team already runs on — nothing new to learn to accept cards for your own product.

  • Low PCI scope on a small team

    Hosted fields and gateway-side vaulting keep card data inside our PCI DSS Level 1 scope. Your fintech SaaS stays at merchant SAQ A instead of running a full PCI environment for the billing surface.

  • Renewal-safe subscription billing

    Network-tokenised card-on-file, MIT exemptions and dunning-aware retries. A card reissue does not silently churn a paying customer — the fintech SaaS renewal book stays intact.

  • Regional underwriting and In-region data residency

    Direct regional acquiring on our own licence. Authentication and GDPR run natively — no cross-border data hop and no offshore fallback to explain in a compliance review.

The fintech verticals the platform covers

Four fintech software categories sit inside BazPay's regional underwriting policy. Each one shares the same platform primitives — the specific configuration and reporting emphasis differ.

  • SaaS billing

    Fintech SaaS billing (subscription revenue)

    Accounting, expense-management, invoicing, close-the-books and reconciliation platforms billing their own customers for a monthly or annual subscription. BazPay handles the acceptance layer — your team keeps building the product.

    • Monthly
    • Annual
    • Trial-to-paid

  • Treasury tech

    Treasury and cash-management software

    SaaS platforms for CFO teams, cash-flow forecasting and treasury automation. BazPay charges the subscription; the platform itself remains the source of truth for the customer's own bank data.

    • Forecasting
    • Cash flow

  • Insurance tech

    Insurance and claims software

    Broker tooling, claims workflow and insurance-CRM software billed as a subscription. Underwriting scope covers the software business, not the underlying insurance policies.

    • Broker tools
    • Claims workflow

  • Wealth tech

    Wealth and advice software

    Portfolio-management dashboards, planning software and adviser CRM billed as SaaS. Boarding covers the software vendor charging its own customers — not brokerage or CFD execution.

    • Adviser CRM
    • Planning

The wider platform view lives on payment provider. The engineering-foundation view lives on payment infrastructure.

The life of a fintech SaaS subscription charge

Six stages from sign-up to reconciliation. Each stage is instrumented; each stage change fires a signed webhook so your billing and observability stack stays in sync.

  1. Sign up

    Your customer subscribes to your fintech SaaS through your existing checkout or self-serve flow.

  2. Collect

    Hosted fields or a hosted checkout page capture card details inside our PCI scope. Your servers never touch raw PAN.

  3. Authorise

    3-D Secure 2.2 runs only when the risk earns it. PSD2 exemption logic keeps most subscription checkouts frictionless.

  4. Store

    The gateway vault issues a stable token keyed to your merchant. Network tokens refresh automatically after card reissue.

  5. Rebill

    Renewals fire on the schedule you set with MIT exemptions where PSD2 permits. Dunning-aware retries handle soft declines automatically.

  6. Reconcile

    Signed settlement events land in your ledger with interchange++ line detail. Payouts hit your local settlement account per scheme cycle.

Fintech-shaped gateway vs generic e-commerce gateway

A fintech SaaS billing its own customers has different priorities to a DTC storefront — versioned APIs, renewal resilience and finance-grade reporting matter more than marketing pixel wiring. The comparison below shows where the trade-off lands.

BazPay fintech-shaped platform compared with a generic e-commerce gateway
Dimension BazPay (fintech-shaped) Generic e-commerce gateway
API contract Versioned REST, idempotent, HMAC webhooks Unsigned or per-vendor formats
Card scope Merchant SAQ A via hosted fields Full PCI where PAN passes servers
Renewals Network tokens + MIT exemptions default Rebills fail after card reissue
Reporting Interchange++ line detail Blended-rate summary
Sandbox Production-parity replay Best-effort mocks
Underwriting scope Regional fintech software Broad, few exclusions

Rate structure on the pricing page. Ongoing service envelope on gateway services. Recurring-billing depth on recurring billing. Buyer's shortlist on payment processors and the digital-goods sibling bundle on the payment gateway for digital goods.

Features engineered into the fintech payment platform

Every capability below is on the standard integration. No premium tier for the sandbox, the versioned changelog or the webhook signing scheme — the primitives are the platform.

  • Versioned REST API

    One versioned endpoint, one signature scheme, one idempotency contract. Fintech engineering teams onboard the platform in an afternoon.

  • Hosted fields

    Card, expiry and CVC inputs served from our PCI environment inside your checkout — merchant SAQ A instead of full PCI.

  • Gateway vault + network tokens

    Card-on-file for subscriptions. Automatic PAN refresh through Visa and Mastercard token services keeps renewals alive.

  • Authentication + exemptions

    3-D Secure 2.2 with automatic exemption logic — TRA, low-value, trusted-beneficiary, MIT — so rebills stay frictionless.

  • Signed webhooks

    HMAC-signed, replay-protected events for every state change. One handler covers charges, renewals, refunds, disputes and payouts.

  • Idempotent requests

    Retry-safe writes across create, capture, refund and payout. A network blip never becomes a double charge on a renewal.

  • Interchange++ reporting

    Every settled charge breaks out interchange, scheme fees and gateway margin — the finance-friendly reporting fintech teams expect from their own tooling.

  • Real-time decline data

    Approval, decline and retry outcomes visible within seconds; wire the stream into your existing observability stack via webhook or CSV.

A subscription charge, in the shape a fintech engineer expects

One versioned REST endpoint creates a subscription charge. Attach your plan, customer reference and any tax metadata; the same fields ride through renewals, refunds and settlement events. Idempotency keys make retries safe end to end. 

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
BazPay-Version: 2026-04-01
{
  "amount": 4900,
  "currency": "EUR",
  "payment_method": "card",
  "customer": "cus_5F9k",
  "subscription": "sub_2H9F",
  "capture": "auto",
  "three_d_secure": "required_if_needed",
  "metadata": { "plan": "pro_annual", "seats": 12 }
}

The response returns a canonical charge object with the authorisation code, the plan reference and any exemption applied. Full schema in the API reference; handler samples in the developer docs.

Where fintech payment processing solutions land in the wild

Four fintech software categories already fit BazPay's regional underwriting. Each uses the same platform primitives — the difference is in the reporting emphasis and billing cadence.

  • Accounting and bookkeeping SaaS

    Monthly and annual subscriptions with card-on-file renewals, MIT exemptions and per-plan reconciliation into the software's own ledger.

  • Expense and spend-management tools

    SaaS subscription revenue for the tooling — not the customer's own card programme. BazPay bills the SaaS vendor's plans and add-ons.

  • Treasury and cash-flow platforms

    Enterprise SaaS billing with named-payer trust lists and enforced 3-D Secure 2 over a ceiling you set. Reporting matches finance-team expectations.

  • Insurance and wealth-adviser software

    Broker tooling, claims workflow, planning and CRM software billed as SaaS. Underwriting covers the software vendor, not the underlying regulated activity.

Out of scope for BazPay: crypto exchange, forex, CFD, consumer wallets, embedded-finance resellers, MOR-style payment platforms, adult, gambling, CBD, nutraceutical, debt-collection and MLM. Embedding acceptance inside your product: integrated payment solutions. New to online payments: accept online payments.

Security and compliance signals fintech buyers actually check

The acceptance layer runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields, gateway vaulting and network tokens keep your fintech SaaS at merchant SAQ A. Authentication runs on every card charge with exemption logic where the rules allow. In-region data residency and GDPR are 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 fintech teams ask before boarding

Which fintech companies can use BazPay's fintech payment gateway?

The fit is regional fintech software companies charging their own customers — SaaS billing for accounting, expense management, invoicing, treasury, insurance and wealth-adviser software. BazPay is the acceptance layer for the subscription revenue, not for the customer's underlying financial activity.

Does BazPay support crypto-exchange, forex or CFD fintechs?

No. BazPay does not board crypto-exchange, forex, CFD or consumer-lending merchants. Those verticals fall outside our regional underwriting policy and are not in scope for the fintech payment platform.

How is a fintech payment services provider different from a generic gateway?

The difference shows up on three axes fintech engineering teams care about: versioned APIs with a documented deprecation window, event-driven operations on signed HMAC webhooks, and reporting granular enough for the CFO's own reconciliation. A generic e-commerce gateway typically ships one or none of those. BazPay ships all three by default.

Can we resell BazPay to our own customers as embedded finance or a marketplace?

No. BazPay is not a marketplace of third-party PSPs, does not act as a merchant of record and does not support reselling as an embedded-finance offering. The merchant of record for every BazPay-processed transaction is your own legal entity, and the underwriting relationship is direct with BazPay.

Which billing patterns does the fintech payment system handle?

One-off charges, subscriptions (monthly, annual, custom), trial-to-paid conversions, plan upgrades and downgrades with proration, add-on charges and usage-based metered billing. Dunning-aware retries, MIT exemptions on rebills and network-token refresh are native — not bolt-on modules.

How is compliance handled for a fintech SaaS billing its own customers?

BazPay operates the acceptance layer under PCI DSS Level 1 with hosted fields and gateway vaulting, so your fintech SaaS stays at merchant SAQ A. Authentication runs on every card charge with automatic exemption logic. Compliance for your own product surface — KYC/AML on your customers, regulatory reporting on the financial activity you operate — remains with your legal entity.

What migration path is supported when switching from an existing fintech gateway?

Vault imports, network-token portability and debit-order mandate migration are supported under scheme-approved processes, subject to the receiving bank's consent letters. Old and new webhook streams typically run in parallel until traffic is proven on the new stack, so subscription renewals never miss a cycle.

Does the platform integrate with common fintech operational tools?

Signed webhooks push events into any observability, ledger or CRM stack that accepts HTTP callbacks — the platform is deliberately un-opinionated about downstream tools. CSV export covers the finance-team side. Storefront-style plugins for WooCommerce, Magento 2, PrestaShop and Shopware cover the sales-page side where a fintech SaaS uses one of those stacks.

Scope your fintech SaaS billing on a direct regional acquirer

Share your product, subscription model and monthly volumes. An integration manager will confirm boarding fit and map the wiring inside one working day. See also merchant acquiring, gateway services, payments solutions and card and APM processing.

Talk with sales Read the developer docs