Charges for a payment gateway, broken down line by line.
Payment gateway charges are made of three components: interchange, scheme fees and the gateway margin. BazPay prices card acceptance on interchange++, so all three appear as separate lines on every settled transaction. Local payment methods and event-level fees have their own lines too — nothing is blended into a single monthly number.
The live rate schedule lives on the pricing page. This page explains the structure of the fees, how a card charge accrues them, and how interchange++ compares with blended-rate models.
Why transparent charges matter more than a headline rate
A blended rate looks tidy on the first page of a proposal and less tidy on the last day of the month. Four properties keep the payment-gateway charges auditable and forecastable.
-
Every fee has a name and a line
Interchange (the fee the issuer receives), scheme fees (what Visa or Mastercard charge for using the network) and the gateway margin (what BazPay earns) appear as separate lines on every settled transaction. Finance teams reconcile against the source, not against a monthly summary.
-
Interchange++ instead of a blended rate
Blended pricing hides where the money went by rolling everything into a single headline percentage. Interchange++ shows it — the same three components that make up the cost either way, but visible per charge. Your rate posture stays auditable when a card mix changes.
-
Method-specific pricing where it applies
Local payment methods, wallets and instant rails carry their own per-method scheme rates, not a card-style interchange. BazPay prices those on their own lines rather than blending them into a card headline — a change in method mix does not silently change your unit economics.
-
Rate schedule published in the open
Actual rates and any monthly minimums live on the pricing page rather than in a sales deck. What appears there is what a merchant with a matching profile pays; boarding confirms the specific tier for your business type and volume.
The four fee components in card processing
Every card charge on any acquirer breaks into interchange, scheme fees and the gateway margin. Local payment methods carry their own scheme rates. This is the anatomy of the fees you actually pay — whether or not they are shown to you.
-
Interchange
Interchange (paid to the issuer)
Interchange is the fee the acquirer pays the issuer for accepting the card, defined by the scheme rulebooks and varying by card type, region and merchant category code. It is not a BazPay fee — it is a scheme-defined cost that any acquirer pays. Interchange++ makes it visible on every charge.
- Scheme-defined
- Per card / region / MCC
- Paid to issuer
-
Scheme fees
Scheme fees (paid to Visa, Mastercard, CB, eftpos)
The card scheme networks charge fees for using the rails — assessments, cross-border fees, integrity fees. These are also scheme-defined and beyond any acquirer's control. Interchange++ shows them per transaction alongside interchange.
- Assessment
- Cross-border
- Integrity
-
Gateway margin
Gateway margin (what BazPay earns)
The margin BazPay adds on top of interchange and scheme fees. This is the only component either party can negotiate; boarding confirms your tier based on business type, volume and mix. Published on the pricing page.
- Per merchant tier
- Confirmed at boarding
-
Method + event
APM and event-level fees
Local payment methods carry their own per-method scheme rates. Refunds and chargebacks may carry event-level fees under the scheme rules. Every event fee lands on its own line in the statement — no per-cycle catch-all.
- APM rate
- Refund fee
- Chargeback fee
Live rates on the pricing page. Card-method depth on card and APM processing. Acquiring contract on merchant acquiring.
How a charge accrues fees, end to end
Six stages sit between a shopper hitting pay and the net amount landing in your regional settlement account. Each stage adds a specific, named component to the fee stack.
-
Charge
A card charge posts to the acquirer with the MCC, card type and region attached. Those inputs determine the interchange bucket.
-
Authorise
The issuer approves; interchange applies according to the scheme rulebook for the card + MCC combination.
-
Scheme fees
Visa or Mastercard adds its scheme fees — assessments, cross-border where applicable, integrity fees. Both are captured on the settlement line.
-
Margin
BazPay's gateway margin is calculated per the merchant tier confirmed at boarding. It sits on top of interchange + scheme fees as a separate value.
-
Settle
The transaction lands on the interchange++ statement with all three components split out and the net amount that arrives in your local settlement account calculated.
-
Export
Every line is exportable as CSV and streamed via signed webhooks — your finance stack reconciles against the same values BazPay does.
Interchange++ vs blended-rate charges
The two dominant pricing models for a payment gateway are interchange++ and blended rate. Both express the same underlying costs. The difference is what your finance team gets to see.
| Dimension | BazPay (interchange++) | Blended-rate model |
|---|---|---|
| Card pricing model | Interchange++ | Blended-rate percentage |
| Fee visibility | Interchange, scheme, margin per transaction | Single monthly summary |
| APM pricing | Per-method scheme rate on its own line | Rolled into card headline or opaque |
| Refund fees | Own line, linked to charge ID | Bundled into monthly totals |
| Statement export | CSV per transaction | PDF summary only |
| Aggregator margin | None — direct regional acquirer | Reseller stacks its own margin on top |
| Rate discovery | Published pricing page | Under NDA in a sales conversation |
Rate schedule on the pricing page. Buyer's shortlist on payment processors. Acceptance breadth on payment acceptance.
Reporting features that expose the charges
Interchange++ is only useful if the tooling around it shows the numbers cleanly. Every capability below ships on the standard integration.
-
Interchange++ reporting
Every settled charge breaks out interchange, scheme fees and gateway margin. No blended rate, no monthly rebate to reconcile.
-
Per-method pricing
iDEAL, Bancontact, BLIK, pay by bank, PayTo, Interac and other local APMs carry their own scheme rates on their own lines — never blended into a card headline.
-
Refund and chargeback fees
Event-level fees appear on their own lines with the linked charge ID, so refund and dispute economics stay clean.
-
Dashboard fee explorer
Filter settled charges by card type, region, method or MCC to see how a segment of traffic actually costs — before renegotiating anything.
-
CSV export for finance
Full settlement export per period covers every fee line for the accounting team. No black-box numbers on the monthly invoice.
-
Signed settlement webhook
HMAC-signed events fire on each settlement cycle with the aggregated fees attached; your ledger can auto-reconcile without a manual pull.
-
No aggregator delay
Direct regional acquirer settles per scheme cycle to your local settlement account. Aggregated payouts and holdbacks common on reseller models do not apply here.
-
Published pricing page
Rate schedule for card processing, local APMs and payouts on the pricing page — no sales-call gate to see the numbers.
Fee data on the settlement webhook
The charge.settled event carries the interchange, scheme fees and
gateway margin values as separate fields on the settled charge. Your ledger reads the
same numbers the interchange++ statement is built from — no reconciliation drift
between the dashboard and your accounting system.
BazPay-Signature: t=1717257600,
v1=8b3f1c...9d2e
{
"id": "evt_02H9",
"type": "charge.settled",
"data": {
"object": {
"id": "ch_5F9k",
"amount": 4990,
"currency": "EUR",
"fees": {
"interchange": 0,
"scheme": 0,
"gateway": 0,
"currency": "EUR"
}
}
}
}The exact values on the settled charge depend on your tier, the card type and the transaction. Zeros in the example above are placeholders — the schedule that fills them in is on the pricing page.
Where transparent gateway charges earn their place
Four merchant profiles pay attention to fees at a level of detail interchange++ supports. Each uses the same reporting surface — interchange++ is not a premium tier.
-
Finance teams closing the book
Reconciliation against source data instead of a blended monthly rebate. CSV export or signed webhook streams every fee line to your ERP.
-
High-volume, low-ticket merchants
Subscription and paywall businesses where interchange dominates the unit economics; interchange++ makes the cost floor visible so you can price accordingly.
-
Multi-country e-commerce
Cross-border and multi-scheme traffic where interchange varies by region and MCC; interchange++ makes the mix effect visible before it moves the P&L.
-
Professional-services and B2B invoicing
Higher-ticket invoices where a small percentage change matters in absolute terms; interchange++ keeps the per-invoice cost auditable.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a merchant of record.
Compliance and audit context for the fees
Charges are only auditable if the underlying platform is. BazPay's payment environment is assessed to PCI DSS Level 1 annually; hosted fields and gateway vaulting keep your annual return at merchant SAQ A. Authentication runs on every card charge with 3-D Secure 2.2 and automatic exemption logic. Every dashboard action is audit-logged so a fee dispute has an evidence trail.
- 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 stack
- Authentication
- 3-D Secure 2.2 with automatic exemption logic on every card charge
- GDPR
- In-region data residency; DPA on request
- Scheme registrations
- Visa VIRP and Mastercard SPoC/PCI-CP where required
Questions merchants ask about payment gateway charges
What charges does a payment gateway actually apply to a card transaction?
Three components: interchange (paid by the acquirer to the shopper's issuing bank, defined by the scheme rulebook), scheme fees (paid to Visa, Mastercard, CB or eftpos for using the network), and the gateway margin (what the acquirer or gateway earns). Interchange++ pricing shows all three per settled transaction; blended-rate pricing rolls them into a single percentage that hides the mix.
What are the online payment gateway charges on BazPay?
The live rate schedule lives on the pricing page, including card interchange++ ranges, per-method APM rates and any monthly minimums. This page explains the structure of the fees; the pricing page shows the numbers by tier. Boarding confirms your specific tier for the business type and volume.
How do gateway charges for a credit card differ from other payment methods?
Cards run on interchange++ — three components, defined by the scheme and the tier. Local payment methods (iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac) carry per-method scheme rates on their own line. Instant rails carry SEPA scheme fees. Nothing gets blended into a card headline; a change in method mix is visible in the statement rather than a surprise on the invoice.
How do payment gateway charges for a website depend on traffic mix?
Interchange depends on card type (consumer credit, commercial, prepaid), region (domestic regulated vs inter-regional), and the merchant category code. That means your website payment gateway charges vary as your traffic mix does — a shift from consumer credit to commercial cards, or a bump in cross-border traffic, changes the cost per transaction. Interchange++ makes this variability visible instead of hiding it inside a blended rate.
Is BazPay the payment gateway with less charges than others?
That is a comparison you should run against your own traffic mix — no gateway is universally cheapest across all card types, regions and MCCs. What BazPay does provide is a transparent breakdown that lets you compare like for like: the interchange and scheme components are scheme-defined and identical across any direct acquirer, so what varies is the gateway margin. Ask any vendor for an interchange++ quote before comparing.
Are there hidden fees or setup costs?
The published rate schedule on the pricing page covers processing, APM rates, refund and chargeback event fees, and payouts. There is no separate setup fee at boarding for the standard integration; if a bespoke contract term (higher-volume tier, specific corridor, custom payout schedule) requires an additional line, it appears in the contract before you sign. No mid-year adjustments arrive by email.
How do refunds and chargebacks affect payment gateway charges?
A refund typically returns the interchange portion (as governed by scheme rules) while scheme fees and gateway margin may or may not refund depending on the scheme; the exact treatment is disclosed per event in the statement. Chargebacks carry an event fee where the scheme applies one — visible on its own line linked to the disputed charge.
Which merchant profiles can access these charges?
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. Boarding confirms your tier based on business type and monthly volume.
See the live rate schedule and confirm your tier
The current schedule for card interchange++, regional APM rates, event fees and payouts is on the pricing page. Share your business model and monthly volume and a named engineer will confirm the specific tier and any bespoke corridor economics inside one working day. See also payouts, recurring billing and card and APM processing.