Accept online payments on your website.
BazPay is an EU payment gateway for accepting online payments on any website. Cards, device wallets, SEPA online payments and EU local methods sit behind one API. Choose hosted checkout for the shortest path or hosted fields for a checkout you fully own.
Built for EU e-commerce sellers, subscription software firms and professional-services businesses. Sandbox is available immediately; boarding for live acceptance typically completes in a few business days.
Why merchants pick BazPay for accepting online payments
Four things stay true whether you sell your first hundred euros or your first million. They are the reasons product, engineering and finance teams stay after go-live.
-
Start taking online payments in days, not months
KYC boarding, sandbox credentials and hosted checkout give you a live-tested integration well before your first sale. No dedicated engineer required if you use one of the stock plugins.
-
Cards, wallets and SEPA on one API
Accepting online payments through several vendors multiplies your reconciliation work. BazPay puts every rail behind one REST endpoint and one signed webhook stream, so your checkout code stays small.
-
Reduced PCI scope by default
Hosted fields and hosted checkout keep the card number inside our PCI DSS Level 1 environment. Your annual return stays at merchant SAQ A instead of a full audit.
-
Predictable EU settlement
Funds settle from our EU acquiring balance into your named IBAN on a per-scheme cycle. Interchange, scheme fees and margin are broken out on every line so finance can reconcile against the source.
Four ways to take online payments on your website
Pick the path that matches your team. Every option lands on the same acquirer, produces the same charge object and reports through the same dashboard.
-
Fastest
Hosted checkout
A BazPay-hosted page collects card, wallet or APM details and returns the shopper to your site. Ideal when you want to take online payments on your website without hosting the checkout form yourself.
- No card fields on your site
- Automatic PSD2 SCA
- Custom logo and colours
-
Balanced
Hosted fields (drop-in)
PCI-scoped inputs render inside your own checkout page through iframes we serve. You keep the layout; we keep the card data.
- Your checkout UX
- Merchant SAQ A
- One SDK
-
E-commerce
Stock plugins
Certified modules for WooCommerce, Magento 2, PrestaShop and Shopware ship with checkout, refunds, capture, webhooks and recurring billing out of the box.
- WooCommerce
- Magento 2
- PrestaShop
- Shopware
-
Custom
REST API and mobile SDKs
For teams building a bespoke web or native checkout. iOS and Android SDKs share the same charge object and signed webhook stream as the web integration.
- REST API
- iOS SDK
- Android SDK
- Webhooks
Product depth on hosted checkout products. The full module overview lives on online payment systems.
Setting up online payments for your website in six steps
Six stages sit between the boarding email and your first settled euro. Sandbox credentials are available from step one, so integration and testing run in parallel with underwriting.
-
Open a merchant account
Submit KYC, ownership and business model. Low-risk EU merchants typically complete boarding within a few business days.
-
Pick an integration path
Hosted checkout (redirect), hosted fields (drop-in inside your site) or a stock plugin for WooCommerce, Magento 2, PrestaShop or Shopware.
-
Wire the webhook endpoint
One HTTPS URL receives every event — approvals, refunds, disputes, settlements — signed with an HMAC secret you store in your app.
-
Test in sandbox
Replay approvals, declines, 3-D Secure 2 challenges and refund flows on synthetic card numbers before flipping to live.
-
Turn on live keys
Swap sandbox for production credentials. Your first authorisation lands in real-time analytics within seconds of posting.
-
Reconcile settlement
Interchange++ statements and payout webhooks feed your finance stack. Every euro on the bank ties back to a transaction ID.
BazPay vs a self-hosted card form
You can technically build a card form on your own domain and post PANs to a bare processor — the trade-off is scope, compliance overhead and reporting depth. This comparison shows where the hosted approach earns its keep.
| Dimension | BazPay hosted acceptance | Self-hosted card form |
|---|---|---|
| PCI scope | Merchant SAQ A | Full SAQ D common |
| 3-D Secure 2 | Automatic exemption logic | Blanket step-up common |
| SEPA rails | Bundled — SEPA and Instant | Separate contract typical |
| Reporting | Interchange++ line detail | Blended-rate summary |
| Boarding | Direct with the acquirer | Chain of resellers |
| Webhook contract | One signed catalogue | Vendor-specific envelopes |
Rate cards on the pricing page. Plugin coverage on integrations.
Features shipped on the standard integration
Every capability below is on every account by default. Turn features on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives.
-
Hosted checkout
PCI-hosted page that handles card, wallet and APM entry, PSD2 SCA and success/failure redirects to your site.
-
Hosted fields
Drop-in card, expiry and CVC inputs inside your own checkout page — you keep the layout, your scope stays at SAQ A.
-
Saved cards
Gateway-side vault stores credentials as network tokens for one-click checkout, subscription renewals and card-on-file charges.
-
SEPA online payments
Euro pulls and payouts on SEPA and SEPA Instant, with open-banking authentication where the shopper's bank supports it.
-
3-D Secure 2.2
PSD2 SCA with automatic exemption logic. Frictionless first, challenge only where the rules or risk demand it.
-
Signed webhooks
HMAC-signed, replay-protected events for approvals, refunds, disputes and settlements — one handler, one secret.
-
Idempotent requests
Retry-safe create requests keyed to your idempotency header. A network blip never turns into a double charge.
-
Real-time decline data
Reason codes and decision paths appear in the dashboard within seconds — including which rule fired and whether SCA was invoked.
One REST call per online payment
The charge object is the unit of work. One endpoint authorises against a card, a wallet,
an EU local payment method or a SEPA pull. The payment_method field selects
the rail. Idempotency keys make retries safe. Signed webhooks confirm every state change
even if your service was down when the event fired.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"payment_method": "card",
"capture": "auto",
"three_d_secure": "required_if_needed",
"return_url": "https://example.com/order/thanks",
"metadata": { "order_id": "ORD-10842" }
}
Switch payment_method to ideal, sepa_debit or
apple_pay and the request routes accordingly. The response object keeps
its shape. Full schema in the API reference.
Merchant profiles we tune for
The default configuration already reflects these four profiles. Turn on the ones you need from the dashboard and adjust for your own traffic.
-
New online stores
First-time merchants setting up online payments for their website through Shopware, Magento 2, WooCommerce or PrestaShop, with hosted checkout out of the box.
-
Subscription software
SaaS teams billing monthly and annual plans with card-on-file, dunning-aware retries and MIT exemptions on renewals.
-
Professional services
Agencies, consultancies and B2B service firms invoicing recurring retainers, with SEPA online payments as an alternative to card for higher-ticket work.
-
Digital publishers
Membership renewals, single-issue purchases and paywall unlocks — same platform, same reporting per SKU.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.
Security and compliance signals
Accepting online payments carries an inherent PCI and PSD2 burden. BazPay's hosted surfaces move most of that inside our environment — hosted fields and hosted checkout keep card data out of your stack, and PSD2 SCA runs on every card charge with automatic exemption logic where the rules allow.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment
- Merchant SAQ A
- Hosted checkout and hosted fields keep card data out of your stack
- PSD2 SCA
- 3-D Secure 2.2 with exemption engine on every card charge
- GDPR
- EU data residency; DPA available on request
- SEPA / SEPA Instant
- Direct participation for merchant payouts in supported corridors
Questions merchants ask first
How quickly can I start accepting online payments with BazPay?
Sandbox credentials are available immediately for integration work. Live acceptance depends on KYC and merchant underwriting — standard EU low-risk boarding usually completes within a few business days once documents, beneficial ownership and business-model information have been received.
What is the simplest way to accept online payments on my website?
For most merchants, hosted checkout is the shortest path. You redirect the shopper to a BazPay-hosted page that collects card, wallet or APM details, runs PSD2 SCA and returns them to your success URL. No card fields ever render on your domain, which keeps you in merchant SAQ A scope.
Do I need a technical team to take online payments on my website?
No, if you use a stock plugin. Certified modules for WooCommerce, Magento 2, PrestaShop and Shopware install and configure through the store admin. If you have engineers, hosted fields and the REST API let you build a custom checkout with the same PCI scope reduction.
Can I accept SEPA online payments alongside cards?
Yes. SEPA and SEPA Instant sit behind the same charge object as cards. For a pull, the shopper authenticates on their bank's own screen through open banking; for a payout, BazPay pushes the euro amount to a supported EU bank account, typically within seconds on SEPA Instant.
How does setting up online payments for my website affect PCI scope?
Hosted checkout and hosted fields both keep raw card numbers inside our PCI DSS Level 1 environment, so most integrations qualify for merchant SAQ A rather than a full audit. Your engineering team never touches a PAN in the clear, and your annual return stays short.
Which currencies and settlement corridors are supported?
Authorisation runs in EUR and more than twenty presentment currencies. Settlement defaults to EUR into an EU IBAN. Other named settlement currencies and SEPA Instant, SWIFT or push-to-card payouts are available on approved corridors — the current schedule is on the pricing page and confirmed during boarding.
Can I take online payments recurringly?
Yes. The gateway vault stores card credentials as network tokens, and merchant-initiated exemptions run on renewals with a stored mandate so trusted repeat charges stay frictionless. Dunning-aware retries handle soft declines automatically.
Which merchant types can BazPay board?
BazPay boards EU low-risk merchants: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and is not a marketplace of third-party PSPs.
Start accepting online payments this week
Open a sandbox account and post your first authorisation in the same hour. Boarding for live acceptance runs in parallel. A payments specialist can map your rails, your anti-fraud controls, your recurring billing and your payouts before your first live shopper hits checkout.