Blended
Standard
One rate per card type. Easiest to forecast.
- Hosted fields and hosted checkout
- iDEAL, Bancontact, BLIK, EPS and wallets
- Plugins for WooCommerce, Magento 2, PrestaShop
- Standard 3-D Secure 2.2 flow
BazPay prices EU card acquiring two ways. Take a blended rate for simple forecasting. Or take interchange++ and see each cost on its own line. Both plans carry the same gateway, the same plugins and the same fraud tools. You choose the billing model, not a feature tier.
Every plan runs on one integration. The difference is how the cost is broken out on your invoice.
Blended
One rate per card type. Easiest to forecast.
Cost plus
Interchange, scheme fee and our markup split out. You see all three.
Volume
For marketplaces and SaaS billing at scale.
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.
Blended pricing rolls all three into one number. That is simpler. It also hides which card types are costing you money.
See cost data in the dashboard| 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 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 payout | Per instruction sent | Flat fee, Instant or D+2 |
| Refund | Per refund processed | No BazPay fee |
| Chargeback | Per case raised | Scheme case fee, passed through |
Scheme case fees are passed through at cost. We do not mark them up.
These four things never sit behind a higher tier.
We hold PCI DSS Level 1 on the gateway side. Card data never touches your servers. You stay on SAQ A.
How we handle card dataYou pay per transaction. There is no monthly gateway rental and no charge for the sandbox.
Read the developer guideAcquiring, open banking, payouts, fraud and billing share one contract. Adding a product does not mean a new build.
Browse the product pillarsPre-built modules cover the major EU carts. Most merchants go live in days rather than months.
Check plugin coverageFour steps. Most merchants finish the first three in a week.
Sign up and test the full API. No card details needed.
Share card mix, average basket and monthly turnover.
We return a written quote with the markup on it.
Swap the sandbox key for a live one. Nothing else 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. It moves with card type, region and channel. A single headline rate would hide that. We quote your markup in writing instead.
Yes. Merchants often start blended, then switch once volume settles. The switch is a pricing change only. Your integration stays as it is.
No. The sandbox is free and open before underwriting. You can build and test the whole flow first.
Low-risk sellers only: e-commerce, subscription SaaS and professional services. We do not underwrite high-risk or restricted verticals. That choice keeps approval rates stable.
Build against the live API today. Pricing comes later, in writing.