Take payments on your website with the integration path that fits.
Every website is different — some run on WordPress, some on custom PHP, some on a static front-end. BazPay ships four integration paths so you take payments on your website without rebuilding it: a storefront plugin, a hosted checkout page, a drop-in JavaScript embed, or a REST API for custom flows.
Built for merchants across the EU, UK, Australia, Canada and New Zealand — direct acquirer under the hood, one dashboard for every path, interchange++ reporting and SEPA Instant settlement to your own settlement account.
Why merchants pick BazPay to take payment on a website
Four things stay true whichever integration path your website uses. They are the reasons a merchant new to taking payment on a website picks a direct regional acquirer over an aggregator wrapper.
-
Works on the website you already have
WordPress, Magento, PrestaShop, Shopware, a custom PHP site, a headless front-end, a one-page invoice site — BazPay ships an integration path for each. Nothing about accepting payment on your website forces a rebuild.
-
Low PCI scope regardless of the path
Whether you redirect to a hosted page or embed a drop-in field, raw card data never touches your website's server. Your annual return stays at merchant SAQ A.
-
One webhook to react to
The signed charge.succeeded event tells your website when payment is safe to fulfil. That single hook covers hosted-page redirects, embedded checkouts and API-driven flows alike.
-
Direct regional acquirer under the hood
You get a named MID with the card schemes, interchange++ line reporting and SEPA Instant settlement into your own settlement account. No aggregator wrapping the payments on your website.
Four ways to add payment to your website
Pick the path that matches what your website already runs on. All four share the same charge object, the same dashboard and the same signed webhook — switching later does not mean re-integrating from scratch.
-
Plugin
Install a storefront plugin
Fastest option when your website already runs on WooCommerce (WordPress), Magento 2, PrestaShop or Shopware 6. The plugin installs from your platform's marketplace, you paste API keys, and payment for the website is live in one afternoon. Checkout, refunds, capture, webhooks and recurring billing come out of the box.
- WooCommerce
- Magento 2
- PrestaShop
- Shopware
-
Hosted page
Redirect to a hosted checkout page
When your website is a custom build, a marketing site, a one-page invoice tool or anything where you cannot install a plugin. Add a link, redirect the shopper, receive them back on your success URL after payment. Zero card data ever touches your website.
- Any stack
- No card data
- Fastest custom path
-
Embed
Embed a drop-in checkout on your website
A short script tag renders hosted card fields inside your existing checkout. The shopper never leaves your website; the payment form is served from BazPay's PCI environment. Best when brand and conversion metrics matter.
- Hosted fields
- Drop-in JS
- Themed
-
REST API
Build a custom flow against the API
One versioned REST endpoint for merchants who want to control the shape of the flow — for example a subscription upgrade inside a customer portal, or a checkout that runs on a mobile SDK alongside the website.
- Versioned
- Idempotent
- Signed webhooks
Ready-made checkout surfaces on hosted checkout products. Plugin list on integrations. Custom-integration primitives on integrated payment solutions.
From plugin install (or script tag) to a live payment
Six stages describe the path from picking an integration to a live shopper flow. Steps two through four run in parallel with underwriting so nothing waits on paperwork.
-
Pick a path
Plugin, hosted page, embed or REST — the four options map cleanly onto what your website already runs on.
-
Install or wire
Install the plugin from your storefront marketplace, paste an API key or drop the script tag. Sandbox credentials are live at signup.
-
Verify the webhook
Verify a signed charge.succeeded event on your server. That is the single hook that tells the website when payment is safe to fulfil.
-
Test in sandbox
Replay approvals, declines and 3-D Secure 2 flows against production-parity data. The live surface matches byte for byte.
-
Underwriting
Submit KYC documents. Merchants across the EU, UK, Australia, Canada and New Zealand typically clear underwriting in days, in parallel with your integration work.
-
Go live
Live keys enabled. Real-time analytics show approval quality from the first payment your website takes.
Embed vs redirect: which suits your website
The two most common ways to take payment on a website are an embedded checkout that keeps the shopper on your page and a hosted redirect that sends them to a BazPay page. Both are safe, both are low-PCI — the trade-off is brand consistency vs setup effort.
| Dimension | Embed (drop-in / plugin) | Hosted page (redirect) |
|---|---|---|
| Shopper stays on your website | Yes | No — redirect required |
| PCI scope on your website | Merchant SAQ A | Merchant SAQ A (hosted page) |
| Setup effort | Short JS include or plugin install | Add a link / redirect |
| Brand consistency | Full — themed inside your checkout | Limited — hosted page branding |
| Fits a static site | Yes, with a small JS include | Yes, with a link |
| Fits a WordPress / Magento site | Better via storefront plugin | Works but plugin is cleaner |
| 3-D Secure rendering | Inside the embed | On the hosted page |
Fees and settlement on the pricing page. The getting-started companion is accept online payments.
Features every integration path ships with
The primitives below are on the standard integration whichever path you pick. No premium tier gates the plugins, the hosted page or the drop-in.
-
Storefront plugins
Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware 6. Install from your marketplace, paste keys, done.
-
Hosted checkout page
A link-based redirect flow that puts zero PCI scope on your website. Ideal for custom sites without a plugin path.
-
Drop-in JS embed
A single script tag renders hosted fields inside your checkout. The shopper stays on your website; card data does not.
-
REST API + signed webhooks
One versioned endpoint for custom flows; every state change fires a HMAC-signed, replay-protected event.
-
Apple Pay and Google Pay
Device-wallet buttons render on both hosted pages and the embed, so returning shoppers convert with one tap.
-
3-D Secure 2.2 handled
Authentication runs only when the risk earns it — challenges are rendered inside the embed or on the hosted page automatically.
-
Refunds and disputes
Full and partial refunds by dashboard or API. Dispute evidence is pre-assembled with the 3-D Secure result.
-
One dashboard for all paths
Whichever path your website uses, the dashboard, analytics and payout reporting are the same product surface.
The smallest embed to take payment in a website
Below is the minimum HTML plus JavaScript to render hosted card fields on any page of your website. The shopper enters card details inside BazPay's PCI-scoped iframe; your code receives a charge ID through the success callback and confirms the payment server-side through the signed webhook.
<div id="bp-checkout"></div>
<script src="https://js.bazpay.com/v1/checkout.js"></script>
<script>
const bp = BazPay('pk_live_...');
bp.mount('#xb8a-x915', {
amount: 4990,
currency: 'EUR',
onSuccess: (charge) => location.assign('/thanks?ch=' + charge.id)
});
</script>Prefer no code at all? Generate a hosted checkout link from the dashboard and drop it on any button. The complete API and drop-in schema live in the API reference with handler samples in the developer docs.
Website types and the path that fits each
The four profiles below cover most websites BazPay onboards. Each gets the same API surface, the same signed webhook and the same interchange++ reporting — only the integration effort differs.
-
WordPress + WooCommerce sites
One plugin install covers checkout, refunds, capture, webhooks and recurring billing. Payment for the website is live the same afternoon.
-
Custom PHP or Node.js sites
Redirect to a hosted checkout page for the fastest zero-PCI setup, or embed the drop-in JS if you want the shopper to stay on your website.
-
Headless / JAMstack front-ends
Drop-in JS renders inside a React, Vue or Svelte checkout without pulling raw PAN into your DOM. Server-side webhook confirms payment.
-
One-page invoice or landing sites
A hosted checkout link on a call-to-action button lets a static site take payment on the website without a server backend at all.
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.
Security and compliance across every integration path
Card handling runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields, drop-in components and the hosted checkout page all keep raw PAN out of your website. Merchant SAQ A stays intact whichever path you pick. Authentication runs on every card charge with 3-D Secure 2.2 and automatic exemption logic.
- 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 website
- 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 website owners ask before wiring payments
What is the fastest way to take payment on my website?
If your website runs on WooCommerce, Magento 2, PrestaShop or Shopware, install the BazPay plugin from your storefront marketplace and paste API keys — payment for the website is live the same afternoon after underwriting. For a custom site with no plugin path, a hosted checkout link is faster still: add a button, redirect the shopper, receive them back on your success URL.
How do I embed payment on a website that isn't a storefront?
Include a small script tag from BazPay in the page where you want to take payment. A drop-in JavaScript component renders hosted card fields inside your existing markup, styled to match your site. Card data never touches your DOM or your server — the shopper stays on your website, but the sensitive inputs are served from our PCI environment.
Do I need a full development team to take payments on my website?
No. If your website runs on a supported storefront, no engineering effort is required beyond installing the plugin. If you use the hosted checkout link, you only need to add a button and a return URL. Only the drop-in embed and the custom REST integration need engineering time — and both are documented so a single developer can get a shopper flow live in a day.
Which payment methods can my website accept?
Cards (Visa, Mastercard, Cartes Bancaires, eftpos), device wallets (Apple Pay, Google Pay) and local payment methods (iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac). Every method shares the same charge object; turning a new method on for your website is a dashboard toggle, not a re-integration.
What happens on my website when 3-D Secure is triggered?
Authentication runs only when the risk earns it. If a challenge fires, it renders inside the embed or on the hosted checkout page — the shopper does not have to leave your website unnecessarily. Once authentication completes, the flow returns to your success URL or the drop-in fires its success callback with the charge ID.
Can I take recurring payments on my website?
Yes. Card-on-file, dunning-aware retries and MIT exemptions are native. The first charge uses one of the integration paths above; subsequent renewals fire against the stored credential and confirm through the signed webhook. Storefront plugins expose recurring billing directly in the platform's subscription UI.
Which merchant profiles are eligible to take payments through BazPay?
Merchants across the EU, UK, Australia, Canada and New Zealand: 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 does not act as a merchant of record.
How does the payment on the website settle to my bank?
BazPay is the direct regional acquirer. Once boarding is complete, card payments settle per scheme cycle into your business local settlement account. SEPA Instant is used for approved-corridor payouts. Reporting is interchange++, so interchange, scheme fees and gateway margin appear on every settled line.
Get payments live on your website this week
Share the platform your website runs on and what you sell. A named engineer will recommend the integration path and confirm boarding fit inside one working day. See also merchant acquiring, hosted checkout products and payment fraud prevention.