Terms of service
These terms govern your use of the BazPay gateway. They cover card acquiring, open banking, payouts, subscriptions and fraud tools. One contract, one set of rules.
We wrote them to be read. Short sentences, named instruments, no hidden schedules. Where a commercial number belongs in your quote, we say so and point you to our pricing page instead of burying it here.
- Version
- v2.4
- Effective
- 28 July 2026
- Applies to
- Dashboard, API and sandbox
- Governing law
- EU / EEA
Who this agreement binds
Three parties, kept apart on purpose. Mixing them is how merchants end up unsure who owes what.
- You
The company named on the application. A signatory must be able to bind it. Sandbox users are covered too, from the first key issued.
- Us
The BazPay entity named on your contract. We run the gateway, the card vault and the payout rails, and we hold the PCI DSS Level 1 attestation.
- Not covered
Your acquirer or bank contracts, where they are separate. Those rates and rules live in that paper. We say which is which before you sign.
The clauses that matter
Each one opens with the position. The detail follows. Nothing here needs a lawyer to decode.
- 01 Onboarding
We check who you are before a live key is issued
You give us company records, owner details and a plain description of what you sell. We verify them. That is a legal duty, not a formality.
We underwrite low-risk categories only. If your model sits outside that appetite, we decline at application. We do not onboard you and end it ninety days later.
- 02 Acceptable use
What you may not sell or do on the platform
No adult, gambling, forex or CFD trading, crypto exchange, debt collection or multi-level marketing. No long forward-delivery models.
Do not store raw card numbers on your own systems. Do not resell gateway access as your own product. Keep your API keys secret.
- 03 Fees
Interchange++ is itemised, never blended into one rate
Every settled payment shows three lines: interchange, scheme fee, and our margin. Your quote sets the margin. It does not move without notice.
Refunds return the sale amount to the shopper. Interchange already paid is not returned by the scheme, so it stays a cost.
- 04 Security scope
Card data stays inside our environment, not yours
Hosted fields render from a BazPay origin. The card number is typed into our page and returned to you as a token. Your logs hold the token only.
That keeps your annual return at SAQ A. Capture card data in your own page and you move to SAQ A-EP. The choice is yours to make in writing.
- 05 Liability
What we answer for, and what we cap
We run the service with reasonable skill and care. We do not promise that any single authorisation will be approved. Issuers decide that.
Neither side is liable for lost profit or indirect loss. Our total liability is capped at the fees you paid us over the prior three months.
- 06 Changes
Thirty days' notice for anything that affects you
We give thirty days' written notice before a fee or term change takes effect. You may end the contract inside that window at no charge.
Security fixes and scheme-mandated rules can apply sooner. We still tell you what changed and why, on the same day it ships.
How a fee line is built
Who keeps each component, and how it reaches your statement. Amounts sit in your quote, not in this table.
| Component | Kept by | Charged | Note |
|---|---|---|---|
| Interchange | Issuing bank | Pass-through, itemised | 0.20% / 0.30% intra-EEA consumer cap |
| Scheme fees | Card scheme | Pass-through, itemised | Varies by scheme and card mix |
| Gateway margin | BazPay | Per your quote | Fixed until we give notice |
| Chargeback handling | BazPay | Per case, per your quote | Charged when a case is raised |
| Payouts | BazPay | Per leg, per your quote | SEPA credit transfer or card push |
The consumer caps come from Regulation (EU) 2015/751. They bind interchange only. Scheme fees and our margin stay separate lines in the settlement file.
Leaving, step by step
Exit terms tell you more about a payments provider than onboarding terms do. Here is ours in full.
-
Notice
Either side gives written notice. Yours takes effect at once. Ours runs thirty days, unless a scheme rule forces a faster stop.
-
Wind-down
New payments stop. Refunds, disputes and payouts keep running so your customers are not left stranded mid-order.
-
Token export
We export your card vault to your next provider under a scheme-approved migration. Tokens are portable. Lock-in is not our model.
-
Final settlement
We hold a balance until the scheme dispute window closes, up to 180 days. Then the remainder is paid out and the account is closed.
Questions on a clause?
Ask before you sign. We answer clause questions in writing, so your risk or audit team has something to file.
Related reading: privacy notice, cookie notice, and the API reference these terms govern.