Charges for payment gateway

Charges for payment gateway, line by line.

topropay invoices every authorisation with interchange, scheme, acquirer and platform fees on separate lines. No setup fee, no monthly minimum, no per-environment line. Cost-weighted routing picks the cheapest qualifying acquirer per transaction across the connected panel.

Per-authorisation invoice line
Interchange € 0.65 pass-through
Scheme fee € 0.04 pass-through
Acquirer fee € 0.28 routed: acq_eu_03
Platform fee € 0.09 topropay
Total per authorisation € 1.06
Sample · €89 authorisation · EU domestic Visa debit
Pass-through
interchange and scheme fees
No retainer
no monthly minimum on the platform fee
Routed
cheapest qualifying route per transaction
1 invoice
across every connected provider

Key benefits

Why orchestrated charges for payment gateway beat single-provider blended rates

Four outcomes that show up consistently once cost-weighted routing across the connected panel replaces a single-provider rate card.

  1. 01

    Charges for payment gateway broken down line by line

    Every authorisation invoice carries four explicit lines: interchange (issuer-side scheme fee), scheme fee (Visa / Mastercard / Amex), acquirer fee (the connected provider's margin) and topropay's platform fee. Nothing rolled up, nothing buried — the merchant sees exactly where each cent of cost comes from.

  2. 02

    Smart routing as a landed-cost lever

    Cost-weighted routing picks the cheapest qualifying acquirer per transaction across the connected panel. The merchant doesn't negotiate one rate card and accept the average — every authorisation routes to the lowest landed cost for that specific BIN, scheme, currency and country pair.

  3. 03

    No platform retainer, no monthly minimum

    topropay's platform fee is per-authorisation only. No setup fee, no monthly minimum, no per-environment fee, no PCI-compliance line item. The merchant's monthly invoice scales with traffic; a slow month doesn't trigger a fixed bill.

  4. 04

    One invoice across every connected provider

    Each connected acquirer settles on its own schedule; topropay rolls the per-acquirer settlement, fees and adjustments into one normalised invoice the merchant pays once. Finance closes the month from one PDF, not a stack of per-provider statements.

The cost stack

Every online payment gateway charge, by layer

Four discrete layers. Three of them pass through from the underlying scheme and acquirer; one is topropay's per-authorisation platform fee. Nothing rolled up.

  1. 01

    Interchange

    The fee the issuing bank charges the acquirer on every authorisation. Set by the scheme (Visa / Mastercard / Amex) based on card type, region pair and merchant category. topropay passes it through at cost — no markup.

  2. 02

    Scheme fee

    Visa / Mastercard / Amex's own per-transaction fee on top of interchange — fixed per scheme rule book. Passed through at cost.

  3. 03

    Acquirer fee

    The connected acquirer's margin for processing the authorisation under its scheme licences. Varies per acquirer; the routing engine picks the cheapest qualifying acquirer per transaction.

  4. 04

    Platform fee

    topropay's per-authorisation platform fee for routing, vault, reconciliation and the unified API. A single rate; no retainer, no monthly minimum, no per-environment fee.

How it works

From discovery to a transparent monthly invoice in five stages

Five stages between the first conversation and a finance-friendly invoice that breaks every line out — quick to set up, hard to gaming.

  1. 01

    Discovery

    A 30-minute discovery walks through the merchant's traffic shape — geography, scheme split, BIN bands, average ticket — and quotes the per-authorisation platform rate. Underlying acquirer rates depend on the connected provider's appetite for the merchant's vertical.

  2. 02

    Onboarding

    Sub-merchant onboarding once through topropay; the platform handles per-acquirer paperwork. No platform retainer applies during the onboarding window.

  3. 03

    Route per transaction

    Live traffic routes through the cost-weighted (or composite) policy. The cheapest qualifying acquirer wins each authorisation; the merchant's effective landed cost compresses vs. a single-acquirer rate card.

  4. 04

    Settle and invoice

    Each acquirer settles to topropay on its cycle; topropay aggregates the lot and invoices the merchant per authorisation. Interchange, scheme, acquirer fees pass through; the platform fee is a separate line.

  5. 05

    Reconcile and renegotiate

    Monthly analytics surface acquirer-level cost per authorisation across the panel. Where one acquirer's rates compress on real volume, the merchant has data to renegotiate or to shift routing weight.

Main use cases

Where website payment gateway charges compress under cost-weighted routing

Six merchant shapes that share the same per-authorisation pricing but benefit from it differently — DTC, SaaS, marketplaces, small online merchants, travel and PSPs.

  • DTC

    Online retail and DTC brands

    Cross-border DTC merchants pay measurably less landed cost via cost-weighted routing across the connected acquirer panel than via a single direct relationship. Payment gateway charges for website checkouts compress on each cross-region pair.

  • SaaS

    Subscriptions and SaaS at scale

    Per-authorisation pricing means a busy month and a quiet month invoice differently — there's no platform retainer dragging on a slow quarter. Renewal volumes get the routing engine's cost lever automatically.

  • Plat

    Marketplaces and platforms

    Per-tenant sub-merchant onboarding under one platform contract. The marketplace doesn't add a per-sub-merchant compliance line on each seller; topropay's platform fee scales with authorisations, not seller count.

  • SMB

    Small online merchants

    Website payment gateway charges for small online merchants typically include a setup fee, monthly fee and a per-transaction percentage. topropay's per-authorisation model removes the setup and monthly lines — small merchants pay only on real traffic.

  • Travel

    Travel and high-ticket

    Gateway charges for credit card processing on high-ticket bookings disproportionately benefit from interchange-plus pass-through — a small percentage point on a large authorisation matters more than on a small one.

  • PSP

    PSPs and ISVs reselling capacity

    Resellers pay the platform per-authorisation rate; their downstream pricing to merchants is independent. The PSP's margin sits on top of the platform fee, not on top of a retainer the platform charges.

Platform features

Capabilities behind the payment gateway with less charges on average

What the platform actually ships for transparent pricing — invoice format, cost analytics, the routing policies that move landed cost, and what's bundled vs. pass-through.

  • Interchange-plus pass-through

    Interchange and scheme fees pass through at cost where the underlying acquirer supports it; no markup on the scheme-level component.

  • Per-authorisation platform fee

    Single per-authorisation rate for the platform; no setup, no monthly minimum, no per-environment fee, no PCI / compliance line.

  • Cost-weighted routing

    Optional routing policy that picks the cheapest qualifying acquirer per transaction — measured against the merchant's own outcomes.

  • Composite routing

    Weight cost, approval and dispute risk into one composite score per route; balance landed cost against approval rate where strict cost-min would lose volume.

  • Unified invoice

    One PDF invoice per period across every connected provider — interchange, scheme, acquirer and platform fees on separate lines.

  • Per-acquirer cost analytics

    Dashboard analytics surface effective cost per authorisation per connected acquirer; useful for renegotiation and routing-weight tuning.

  • Settlement currency policy

    Settlement currency per acquirer is a configuration choice; merchants don't carry FX they didn't ask for.

  • Pass-through scheme adjustments

    Scheme rule-book updates that change interchange or scheme fees flow through to the invoice line; merchants see the change, not a re-priced platform rate.

  • Volume bands

    Per-authorisation platform fees compress at higher monthly authorisation counts, agreed up-front and surfaced in the dashboard.

  • Free sandbox

    The sandbox environment is unmetered; payment-gateway-api testing doesn't add a line to the invoice.

  • No cancellation fees

    No exit fees, no contract minimum term. The merchant can absorb topropay traffic, leave the integration in place dormant, or migrate elsewhere without a contractual penalty.

  • Audit-ready cost reporting

    Per-transaction cost lines exportable to ERP / warehouse on a daily cycle; finance has audit-grade evidence per authorisation.

Trust & transparency

Compliance posture included, not invoiced separately

PCI, scheme-programme tracking and SCA / PSD2 are bundled into the platform fee — no separate compliance line on the invoice.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans included in the platform posture; merchants don't pay a separate PCI compliance line on the invoice.
Scheme programme tracking
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP thresholds tracked per acquirer relationship — surfaced in the dashboard, not invoiced separately.
SCA & PSD2
Selective 3DS2 on the authorisation path keeps approval high in Europe without skipping the compliance bar.
Transparent invoice lines
Interchange, scheme, acquirer and platform fees on separate lines; no rolled-up 'processing fee' that hides per-component cost.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical and per acquirer appetite.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of integration shape.

Ready for a quote

Transparent charges per authorisation, no platform retainer.

A 30-minute discovery walks through your traffic, quotes the per-authorisation platform rate, scopes the relevant acquirers in the panel and outlines a parallel-running comparison against your existing provider.

Frequently asked

Buyer questions about charges for payment gateway on topropay

Questions buyers ask before committing — what's invoiced, what's pass-through, India connectivity, BNPL, FX, sandbox and how to compare against incumbents.

  1. 01

    What does topropay actually charge for payment gateway services?

    Charges for payment gateway services on topropay are: interchange and scheme fees passed through at cost, the connected acquirer's margin, and topropay's per-authorisation platform fee. No setup, no monthly minimum, no per-environment fee, no PCI line. The merchant's effective rate per authorisation depends on the underlying acquirer and the merchant's vertical / volume.

  2. 02

    What's typical for payment gateway charges in india?

    Payment gateway charges in india are a function of the connected partner gateway — topropay's India connectivity is delivered through licensed partner gateways rather than a direct RBI Payment Aggregator licence. Indian rates (UPI per-transaction caps, card MDR rates, NetBanking fees) pass through from the partner gateway; the platform fee sits on top per-authorisation. Pricing for India-resident merchants is typically scoped during onboarding.

  3. 03

    What's the typical range for online payment gateway charges?

    Online payment gateway charges on topropay typically land below comparable single-provider blended rates because cost-weighted routing picks the cheapest qualifying acquirer per transaction. Exact rate depends on the merchant's geography, vertical, scheme mix and volume — a precise quote follows the discovery call.

  4. 04

    How do gateway charges for credit card processing compare to debit?

    Gateway charges for credit card processing typically run higher than debit because credit interchange is higher (the issuing bank carries the credit risk). topropay passes the interchange difference through transparently; the platform fee is the same per authorisation regardless of credit / debit. For merchants with a heavy debit mix the effective landed cost compresses naturally.

  5. 05

    What are payment gateway charges for website checkouts specifically?

    Payment gateway charges for website checkouts on topropay are the same per-authorisation model as any other surface — there's no website-only premium. The hosted checkout, embedded fields and SDK paths share one rate card; what differs is the merchant's PCI scope (SAQ A vs SAQ A-EP), not the per-authorisation cost.

  6. 06

    How do website payment gateway charges break down on the invoice?

    Website payment gateway charges break down on the invoice as: per-authorisation interchange (pass-through at cost), per-authorisation scheme fee (pass-through), per-authorisation acquirer fee (the routed acquirer's margin) and per-authorisation platform fee (topropay's rate). Refunds, chargebacks and FX appear on separate lines with their own rate construction.

  7. 07

    Is topropay the payment gateway with less charges than other providers?

    Payment gateway with less charges is usually shorthand for 'lowest blended rate'. topropay's model is structurally different: cost-weighted routing picks the cheapest qualifying acquirer per transaction across the connected panel, so 'less charges' becomes a routing outcome rather than a flat rate-card claim. Real comparison happens on the merchant's own traffic during parallel running.

  8. 08

    Do you charge separately for chargebacks and disputes?

    Chargebacks carry a per-chargeback fee from the underlying acquirer (passed through) plus a small platform fee for handling representment, evidence-pack templating and the unified dispute queue. The fees are visible on the invoice on separate lines; we don't bury them in the per-authorisation rate.

  9. 09

    Are there volume discounts on the platform fee?

    Yes — the per-authorisation platform fee compresses at higher monthly authorisation counts. The bands are agreed up-front during onboarding and surfaced in the dashboard; once the merchant crosses a threshold the new rate applies prospectively without a re-negotiation cycle.

  10. 10

    Are refunds charged?

    Refunds typically carry no incremental platform fee on top of the underlying provider's refund-side economics (where the underlying acquirer charges a refund fee, it passes through). The platform doesn't double-charge the authorisation it's already invoiced.

  11. 11

    Are 3DS / SCA challenges charged separately?

    3DS / SCA challenges are bundled into the per-authorisation platform fee — there's no separate per-3DS fee. The underlying acquirer may pass through a scheme-side 3DS fee on certain transactions; that's transparent on the invoice line.

  12. 12

    Is there a fee for the sandbox or for API testing?

    No. The sandbox environment is unmetered; deterministic helpers for triggering specific decline / 3DS / iDEAL / PIX / ACH outcomes are all free. Merchants build and test the full integration against the sandbox before any live volume — testing doesn't add to the invoice.

  13. 13

    Are FX fees charged on multi-currency authorisations?

    FX fees on multi-currency authorisations are a function of the underlying acquirer's FX policy. Where the merchant settles in a currency different from the authorisation currency, the acquirer's FX rate applies; topropay passes that through on the invoice with the FX rate and the spread visible.

  14. 14

    Does the platform charge a separate compliance / PCI fee?

    No. The PCI DSS Level 1 service-provider posture is included in the platform fee — no separate compliance line. Scheme programme tracking (VDMP / VAMP / ECP) is similarly included; only where a scheme programme threshold is breached and the underlying acquirer charges a programme fee does that pass through.

  15. 15

    How can a merchant compare topropay against incumbent providers on charges?

    The most useful comparison is parallel-running on the merchant's own traffic. Integrate topropay alongside the existing provider, route a share of authorisations through topropay (cost-weighted or composite), and compare the effective landed cost per authorisation across the two providers over a month. The dashboard exports the data in a finance-friendly format.