Menu
Talk with sales

Integration questions? [email protected]

Online payment systems for EU merchants, on one platform.

BazPay is a single online payment system covering acceptance, risk, recurring billing, payouts and reporting. Cards, EU local methods, open banking and A2A rails all resolve into one charge object, one dashboard and one reconciliation surface.

Built for e-commerce sellers, subscription software firms and professional-services businesses. Also fits vertical online payment systems — course-fee portals, hotel booking sites, membership platforms — where the merchant profile stays low-risk under our underwriting rules.

Talk with sales See all products

Why merchants pick a single platform over stitched e payment systems

Buying acceptance, risk, subscriptions and payouts as separate components stitches four reconciliation surfaces together. A single platform collapses them into one — cheaper to run and easier to audit.

  • 01

    One system replaces a stitched stack

    Acceptance, risk, recurring billing, payouts and reporting share one API and one dashboard. Fewer vendors, fewer contracts, one reconciliation surface.

  • 02

    Direct EU acquiring, not resold

    BazPay operates the acquiring licence for its EU book. No third-party sub-processor sits between your traffic and settlement — you keep line-level fee visibility.

  • 03

    Real-time data on every event

    Every authorisation, decline, refund, dispute and payout emits a signed webhook. The dashboard mirrors the same stream in seconds, not overnight batches.

  • 04

    PCI scope kept at SAQ A

    Hosted fields and gateway-side vaulting keep PANs out of your infrastructure. The platform holds PCI DSS Level 1 on the acquiring and gateway environment.

Modules inside the payment platform

Eight modules make up the platform. Each one is available on the standard integration and each one links back to its own product page for detail.

How the platform runs, end to end

Eight stages sit between a merchant signing on and a payout landing in a supplier's account. Each one is visible in the dashboard and each one emits a signed webhook.

  1. Onboard

    KYC and merchant underwriting complete in days for the standard low-risk profiles. Named MID assigned on activation.

  2. Integrate

    Ship with a plugin, hosted checkout or the REST API. Sandbox keys are self-service, no demo call required.

  3. Accept

    Turn cards, wallets and APMs on from the dashboard. The response shape stays the same across methods.

  4. Screen

    The inline rule engine scores every order. 3-D Secure 2.2 fires only when the risk profile requires it.

  5. Authorise

    The acquirer clears the charge on the EU licence. Decline codes stream to analytics and webhook in seconds.

  6. Settle

    Funds reconcile from the EU acquiring balance to your named IBAN in the settlement corridor you selected.

  7. Pay out

    SEPA, SEPA Instant, SWIFT and push-to-card payouts move money to suppliers, partners or your own accounts.

  8. Report

    Interchange++ line detail, dispute reason codes and payout reconciliation exports feed your accounting stack.

Where merchants use the platform

The default configuration reflects six merchant profiles below. Every one of them fits our low-risk underwriting rules. Sign-off on your business model happens before activation, so there is no surprise deactivation later.

  • E-commerce and DTC brands

    Card acceptance, EU local methods and hosted checkout — with Shopware, Magento 2, WooCommerce and PrestaShop plugins already maintained. A full online payment system for cross-border catalogues.

  • Subscription software

    Recurring billing with card and SEPA mandates, saved-card renewals, dunning and MRR-aware webhooks. The dashboard reports on trial conversion and involuntary churn.

  • Professional services

    Higher-ticket B2B invoicing, corporate payment solutions with named-payer allow lists, and open banking for A2A payments that avoid card interchange on large tickets.

  • Digital publishers and memberships

    Paywall unlocks, membership renewals and one-time issue purchases with account-takeover heuristics on the sign-in flow.

  • Corporate bill payment flows

    For businesses running an online bill payment system for their customers — utilities-style monthly billing, service invoicing and split disbursements to partners.

  • Low-risk verticals that ship online

    School and course-fee portals, hotel booking sites, hospitality-linked laundry services and healthcare-adjacent subscription tools — where the merchant profile stays low-risk under our underwriting rules.

Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. If your profile does not fit low-risk underwriting, the platform is not the right fit — and we would rather say so upfront.

A REST API that reads the same for every method

One endpoint creates a charge. The payment_method field decides whether the request runs as a card, a wallet, a local method or an open-banking A2A push. The response object shape never changes, so your order router and finance reconciliation code stay small. 

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
  "amount": 4990,
  "currency": "EUR",
  "payment_method": "card",       // "ideal" | "bancontact" | "open_banking" | ...
  "capture": "auto",
  "three_d_secure": "required_if_needed",
  "customer": "cus_5F9k",
  "metadata": { "order_id": "ORD-10842" }
}

Read the complete schema in the API reference and the handler samples in the developer docs. Idempotency keys make retries safe. Signed webhooks confirm every state change, even if your service was down when the event fired.

Integrations with the storefronts you already run

The platform ships with maintained plugins for the four most common EU commerce stacks. Each plugin covers checkout, refunds, capture, recurring billing and webhooks — so replacing an incumbent payment system takes hours, not a quarter.

  • WooCommerce — cards, wallets, EU local methods, subscriptions.
  • Magento 2 / Adobe Commerce — B2B and multi-store configurations.
  • PrestaShop — hosted checkout, saved cards, refunds.
  • Shopware 6 — cards, APMs, subscriptions, split payouts.

Full list on the integrations page. If your storefront is custom, the REST API is the same for everyone.

Unified platform vs stitched-together card payment systems

International merchants often assemble a gateway, a fraud vendor, a subscription tool and a payout provider. Each hop adds a contract, a reconciliation join and a place for data to drift. A unified platform keeps them on the same ledger.

BazPay platform vs a stitched-together payment stack
Dimension BazPay unified platform Stitched stack
Contracts One with BazPay Gateway + PSP + acquirer + risk vendor
Reconciliation One dashboard, one payout report Manual join across systems
PAN handling Hosted fields, gateway vault Often merchant-hosted or split
Fraud engine Native inline, tied to the acquirer Bolt-on, blind to scheme signals
Payouts SEPA, SEPA Instant, SWIFT, push-to-card Aggregated, delayed
Reporting Interchange++ line detail Blended-rate summary
Webhooks Signed, idempotent, replay-protected Varies by vendor in the chain

Questions decision-makers ask first

How do BazPay's online payment systems differ from a hosted checkout tool?

A hosted checkout is one layer. BazPay is the whole platform underneath it — the acquiring licence, the risk engine, the recurring-billing scheduler, the payout rails and the reporting stack. You can start with the hosted checkout and grow into the API without switching vendors.

Is this suitable as an e-payment system for cross-border e-commerce inside the EU?

Yes. Presentment runs in EUR and more than twenty currencies. EU local payment methods (iDEAL, BLIK, Bancontact, EPS, Przelewy24) sit behind the same API call as card charges. Cards issued outside the EU still authorise on the EU acquiring licence.

Can I use BazPay for corporate payment solutions and bill payment systems?

Yes, within our low-risk underwriting scope. B2B invoicing, retainer-style recurring billing and corporate bill payment flows work well. Higher-ticket orders can be routed to open banking to avoid card interchange on large tickets.

Do you support vertical online payment systems for schools, hotels and similar profiles?

Where the merchant profile stays low-risk, yes. A school portal collecting course fees, a hotel taking booking deposits or a hospitality-linked laundry service subscription can all run on the platform. What we do not board is adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants.

How is the platform priced?

Card charges are billed on interchange++ so scheme fees, interchange and the BazPay margin appear separately per line. Local methods, payouts and premium features are priced per line on the same statement. Current schedules live on the pricing page.

What does the integration path look like?

Three routes: a maintained shop plugin, hosted checkout, or a direct REST API integration. All three write to the same charge object shape, so you can start with a plugin and move to the API later without reworking your data model.

Does the platform handle payouts and split disbursements?

Yes. SEPA, SEPA Instant, SWIFT and push-to-card payouts run from the same balance the acquirer settles into. Split payouts to third-party beneficiaries reconcile on the same statement as the charge that generated them.

How do I know the acceptance stack is compliant?

The gateway environment is PCI DSS Level 1 assessed each year. 3-D Secure 2.2 covers PSD2 SCA on card charges. Data residency is European and a DPA is available on request. Scheme registrations are held where the schemes require them for our service model.

See the platform on your own data

Open a sandbox account and post a charge, run a payout and fire a webhook in the same hour. Prefer a walkthrough first? A payments specialist can map your acceptance, payouts and recurring billing requirements with you. For the wider context, see merchant services, merchant acquiring, how BazPay compares as a payment provider and real-time analytics.

Talk with sales Read the developer docs