BazPay prices domestic card acquiring two ways. Take a blended rate for simple forecasting, or take interchange++ and see every cost on its own line. Open banking pay-ins, instant payouts and refunds have their own flat fees — never rolled into a headline card rate. You choose the billing model, not a feature tier.
The gateway cost you actually pay is interchange (set by the issuing bank), the scheme fee (set by Visa or Mastercard) and the BazPay markup — quoted in writing after we see your volumes. No setup fee, no monthly rental, no charge for the sandbox.
Every plan runs on one integration. The difference is how the cost of the payment gateway is broken out on your invoice — blended for simplicity, interchange++ for transparency, or a platform contract for volume.
Blended
One rate per card type. Easiest to forecast in a monthly P&L.
Cost plus
Interchange, scheme fee and our markup split out. You see all three on every line.
Volume
For SaaS and marketplace teams billing at scale on a single MID.
The two plus signs are not decoration. They are two separate costs that we never set. Interchange goes to the issuing bank. The scheme fee goes to Visa or Mastercard. Only the third line is ours, and it is fixed for the term of your contract.
Blended pricing rolls all three into one number. That is simpler for a forecast — it also hides which card types are costing you money, and which markets are quietly the most expensive to serve.
See cost data in the analytics dashboardPer-product pricing sits on each product page: card and APM processing, open banking, payouts and recurring billing each list the scheme rate, the interchange bucket and what a settled charge looks like end to end.
| Component | Set by | Varies with |
|---|---|---|
| Interchange Passed through at cost. We add nothing to it. | Issuing bank | Card type, region, channel |
| Scheme fee Passed through at the rate the scheme charges us. | Visa or Mastercard | Published scheme tables |
| BazPay markup One fixed figure, agreed in writing before you sign. | BazPay | Your risk profile and volume |
| Rail | Charged on | Model |
|---|---|---|
| Card acquiring | Per authorised transaction | Blended or interchange++ |
| Open banking pay-in | Per completed payment | Flat fee per payment |
| SEPA Instant payout | Per instruction sent | Flat fee, Instant or D+2 |
| BACS Direct Debit | Per collection | Flat fee, first collection higher |
| Refund | Per refund processed | No BazPay fee |
| Chargeback | Per case raised | Scheme case fee, passed through |
Scheme case fees on chargebacks are passed through at cost. We do not mark them up.
Four things never sit behind a higher pricing tier. They are the reason merchants keep the total cost of the payment gateway predictable, whether monthly volume runs ten thousand euros or ten million.
We hold PCI DSS Level 1 on the gateway. Card data never touches your servers, so your annual return stays at merchant SAQ A.
How we handle card dataYou pay per transaction. There is no monthly gateway rental, no per-user seat cost and no charge for the sandbox environment.
Read the developer guideAcquiring, open banking, payouts, fraud and billing share one contract. Adding a rail does not mean a new build or a new fee schedule.
Browse the product pillarsPre-built modules cover the major regional carts. Most merchants go live in days rather than months, avoiding a costly build phase.
Check plugin coverageA greenfield gateway is not just an engineering project. It is a PCI DSS Level 1 environment, a direct acquiring contract with a regional bank, scheme certifications, an ongoing 3-D Secure 2.2 integration and a permanent team on the code. Six to nine months is a common minimum before the first live authorisation.
Buying a gateway from BazPay collapses that timeline into days on plugins, or one to three sprints on the raw REST API. The cost of payment gateway integration is measured in engineering days, not headcount years.
| Dimension | Buy: BazPay | Build: in-house |
|---|---|---|
| Time to first live payment | Days on plugins, weeks on custom API | Six to nine months typical for greenfield |
| PCI DSS scope | Merchant SAQ A (hosted fields) | Full PCI DSS Level 1 audit required |
| Acquiring contract | Included with BazPay | Separate contracts per bank / scheme |
| 3-D Secure 2.2 integration | Native, with exemption logic | Certified integration project |
| Ongoing engineering cost | Plugin updates by BazPay | Team of 2–4 engineers permanent |
| Scheme fee negotiation | Included in interchange++ | Merchant negotiates directly |
BazPay is priced for regional businesses with predictable chargeback profiles. That underwriting scope is what keeps the gateway cost stable across our book.
DTC brands and multi-country storefronts on Shopware, Magento 2, WooCommerce or PrestaShop.
SaaS teams billing monthly and annual plans with saved-card renewals and dunning.
Agencies, consultancies and B2B service firms invoicing recurring retainers.
Media businesses selling memberships, single-issue purchases and paywall unlocks.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.
The cost of payment gateway compliance — PCI, PSD2, GDPR, scheme audits — sits with BazPay, not with you. Hosted fields keep raw PAN data off your servers. 3-D Secure 2.2 runs with an exemption engine so friction only lands where the rules require it.
See anti-fraud controls in detailFour steps. Most merchants finish the first three in a week.
Sign up and test the full API. No card details or invoice needed.
Share card mix, average basket, refund ratio and monthly turnover.
We return a written quote with the markup and every rail fee on it.
Swap the sandbox key for a live one. Nothing else in your code changes.
Still unsure which model fits? Write to [email protected] and we will model both against your volumes. Settlement timing, rolling reserves and what a refund costs you are answered on the gateway FAQ.
Interchange is set by the issuing bank and moves with card type, region and channel. Scheme fees are set by Visa and Mastercard. A single headline rate would hide both. We quote your markup in writing after we see your card mix and volume — that is the only part BazPay actually sets.
For an EU, UK and Commonwealth e-commerce site, the payment gateway cost for a website on BazPay is the sum of interchange, the scheme fee and our markup on cards, plus a flat per-transaction fee on open banking and instant rails. There is no setup fee, no monthly rental and no charge for the sandbox. The exact numbers are quoted per merchant after underwriting.
Yes. Merchants often start on the blended plan for forecasting, then switch to interchange++ once volume settles and they want line-level visibility. The switch is a pricing change only — your API keys, webhooks and plugin stay exactly as they are.
No. The sandbox is free and open before underwriting, so you can build and test the whole flow with no commitment. There is no monthly gateway rental, no per-user seat cost and no charge for issuing extra API keys or webhook endpoints.
BazPay is a regional gateway, so the equivalent to US ACH is SEPA Instant. BACS Direct Debit collections are priced per collection with a slightly higher fee on the first pull. Instant credit transfer and SEPA Instant payouts are priced per instruction sent. All three appear as their own line on your invoice — never blended into a card rate.
The cost of payment gateway integration on BazPay is the engineering time to swap in our plugin or wire the REST API — typically days on WooCommerce, Magento 2, PrestaShop or Shopware, and one to three sprints on a custom stack. Building your own gateway means a PCI DSS Level 1 audit, direct acquiring contracts, scheme certifications and a permanent engineering team on the code.
BazPay sits in the low-cost band for merchants in the EU, UK, Australia, Canada and New Zealand because we are the acquirer, not a reseller — there is no third-party markup layer between you and the scheme. That said, we do not undercut on rate at the expense of settlement quality or PCI scope. You pay for direct regional acquiring, not for a chain of sub-processors.
A defined list of sellers: e-commerce, subscription SaaS and professional services. We do not underwrite restricted verticals such as adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM. That underwriting choice keeps approval rates and pricing stable across our book.
Build against the live API today. Pricing comes later, in writing, with the markup and every rail fee on the page.