Online payment fees

Online payment fees, unblended: every component on its own line.

topropay exposes interchange, scheme, acquirer markup and platform fee as separate lines on every reconciled authorisation. Smart routing across multiple acquirers compresses the effective landed cost; cascade rescues sales that a single-provider flat-rate model would lose.

Platform fee 0.10–0.50% Acquirer markup 0.10–0.80% Scheme fee 0.03–0.20% Interchange 0.20–2.50% All-in landed cost
Every component on its own line — no blended rate.

The short version

Anatomy of payment fees, layer by layer

Four layers compose the landed cost of every card authorisation. Knowing which is which decides where commercial negotiation can — and can't — move the dial.

  1. Interchange

    0.20–2.50%

    Paid to the issuing bank. Set by the card schemes per country, scheme, product (consumer/premium/commercial) and presence (CP/CNP). The largest component of most card transactions and the one no provider can negotiate around.

  2. Scheme fee

    0.03–0.20%

    Paid to the card network (Visa, Mastercard, etc.) on top of interchange. Differs per scheme, region and transaction type. Small relative to interchange but adds up at volume.

  3. Acquirer markup

    0.10–0.80%

    Paid to the acquirer for taking the credit and operational risk. Negotiable per merchant, but bounded by the acquirer's underwriting appetite for the vertical and risk profile.

  4. Gateway / platform fee

    0.10–0.50%

    Paid to the gateway or aggregator for the orchestration, vault, routing, fraud and reconciliation layer. topropay's platform fee is a separate line — never blended into the interchange or acquirer markup.

Key benefits

What orchestration changes for online payment fees

Four outcomes show up consistently when the orchestration layer sits in front of the acquirer panel, instead of a flat-rate single-provider stack.

  1. Compress effective landed cost per authorisation

    When several connected acquirers cover the same scheme and BIN range, routing each authorisation to the route with the lowest landed cost compresses the effective rate. The shopper sees nothing different; the merchant sees the rate move on the same gross volume.

  2. Pass interchange-plus through cleanly

    Where the underlying acquirer supports interchange-plus, topropay passes the components through without blending. The merchant sees real interchange, real scheme fee, real acquirer markup and a separate platform line — not a single flat-rate number that hides where the cost actually sits.

  3. Cascade past declines instead of paying re-prompt cost

    Soft declines cascade to the next ranked acquirer inside the same authorisation. Re-prompt drop-off — and the cost of the lost sale — disappears from the unit economics, even if the second attempt carries a fractionally higher rate.

  4. Per-acquirer fee analytics, not vendor-supplied numbers

    Every authorisation is tagged with the acquirer ID and BIN it landed on. Per-acquirer cost rolls up in the dashboard so commercial reviews start from your own data, not a vendor's spreadsheet.

How it works

How the platform turns the gateway fees structure into a routing problem

Four stages between a shopper hitting "Pay" and a settlement line landing in the reconciliation feed — each stage exposing a place where fee economics can be tuned.

  1. 01

    Score per transaction

    Each authorisation is scored across the connected acquirers — approval likelihood × landed cost × dispute risk weight — in under 200ms.

  2. 02

    Route on composite score

    The route with the best composite wins. For cost-weighted policies the cheapest-clearing route wins; for approval-weighted policies the highest-clearing route wins; for composite policies net revenue wins.

  3. 03

    Cascade soft declines

    Hard declines stop. Soft declines cascade inside the same request — preserving the sale without re-prompt cost or shopper friction.

  4. 04

    Roll up the actual fees paid

    Daily reconciliation tags every settlement with the acquirer ID, scheme, BIN and per-line fee components. The cost surface is observed, not estimated.

Fee structures

Three gateway fees structures, compared

Where typical PSPs, direct aggregators and orchestration platforms differ on how fees are constructed and surfaced. The structure decides what you can negotiate, model and audit against.

Typical single PSP

Flat blended rate

  • One headline rate (e.g. 2.9% + 30¢) covering everything
  • Interchange, scheme and acquirer markup blended together
  • No visibility into where the cost actually sits per transaction
  • Renegotiation is annual and based on vendor-supplied numbers
Direct aggregator

Single-acquirer interchange-plus

  • Interchange and scheme fees pass through
  • Acquirer markup is one fixed number across all traffic
  • Per-transaction routing is static (one acquirer per merchant)
  • Per-BIN cost analytics are limited or absent

Per-method notes

How card payment fees, ACH and international payments differ

Same orchestration layer, different per-method cost surfaces. The notes below summarise how the platform treats each method's fee structure inside the routing engine.

  • Card payment fees

    Card payment fees are dominated by interchange. The platform routes per BIN to the acquirer offering the lowest landed cost for that specific scheme/product/country combination, and falls back through cascade if the chosen acquirer soft-declines.

  • Credit card payment fees

    Credit card payment fees usually carry a higher interchange band than debit equivalents, particularly for premium and commercial products. The routing engine reads the BIN tier and selects the acquirer whose effective rate is best for that specific tier.

  • ACH payment fees

    ACH payment fees are flat-rate per transaction rather than percentage-based, which makes them cost-efficient for high-ticket purchases. The platform exposes ACH on the same unified API as card; routing policies can prefer ACH where the merchant wants to suppress card fees.

  • International payment fees

    International payment fees compound interchange, FX margin and cross-border scheme assessments. Multi-acquirer routing helps by keeping cross-border traffic on regionally local acquirers where the BIN supports it, reducing the cross-border component of the landed cost.

  • Gateway fees on credit card processing

    Gateway fees on credit card processing are the smallest component for most merchants but the easiest to hide behind a blended rate. topropay's gateway/platform fee is always a separate line on the reconciliation feed — never merged into interchange or acquirer markup.

  • Wallet, BNPL and APM fees

    Wallets typically carry per-scheme fees similar to cards plus an additional wallet surcharge; BNPL providers price per transaction with a fixed plus percentage; bank-rail APMs run on flat-rate or interchange-equivalent models. Each surfaces on the unified API and reconciles into the same ledger.

Industry relevance

Verticals where payment fees decide unit economics

Some verticals can absorb a per-transaction rate that others can't. The list below covers the categories where fee structure has visible impact on margin.

  • Subscriptions & SaaS

    Renewal recovery economics are dominated by avoided re-authorisation cost.

  • Marketplaces

    Per-seller fee transparency is required so each seller's economics reconcile cleanly.

  • Travel & hospitality

    High-ticket plus FX-heavy — cross-border fee compression matters.

  • DTC retail

    Volume-sensitive — small per-transaction savings compound at scale.

  • Financial services

    Payouts and top-ups stress ACH and bank-rail fees more than card fees.

  • Government & utility billing

    Convenience-fee models common; per-method fee transparency required for compliance.

  • Ticketing & events

    Peak-load means fee outliers per acquirer surface visibly in monthly reports.

  • Education & e-learning

    International payment fees dominate when the student base is cross-border.

Trust & compliance

How fee transparency is enforced

Five posture points that decide whether a merchant can model their own unit economics from the reconciliation feed — without taking a vendor's word for it.

Transparent fee construction
Interchange, scheme, acquirer markup and platform fee on separate lines. No blended hidden margins; the cost surface is auditable.
Interchange-plus pass-through
Where the underlying acquirer supports interchange-plus, components pass through without blending.
PCI DSS Level 1
Annual on-site assessment and quarterly ASV scans, inherited by sub-merchants regardless of fee model.
Per-acquirer fee analytics
Dashboard rollups per acquirer, per BIN, per scheme, per region — built on your own production data.
No retainer
Platform pricing is per-authorisation. No mandatory retainer, no minimum monthly fee, no upfront integration charge.

Ready to model the fees

Run your traffic against the per-acquirer cost surface.

A 45-minute fee review walks through your BIN, scheme and geography mix, models the effective rate across the connected acquirer panel, and quantifies the upside before any commercial commitment.

Frequently asked

Buyer questions about online payment fees

What buyers ask before they commit — definitions, per-method differences, gateway fee structures, ACH vs card, international cost compounding and government / utility collection.

  1. 01

    What components make up online payment fees on a card transaction?

    Online payment fees on a card transaction have four components: interchange (paid to the issuing bank), scheme fee (paid to Visa, Mastercard, etc.), acquirer markup (paid to the acquirer for credit and operational risk), and a gateway or platform fee (paid to the orchestration layer that handles vault, routing, fraud and reconciliation). The first two are set by the schemes; the last two are where commercial negotiation happens.

  2. 02

    How does the platform reduce payment fees overall?

    Two main ways: routing each authorisation to the acquirer with the lowest landed cost for that specific BIN/scheme/country, and cascading soft declines so the sale survives instead of needing a re-prompt. Neither tactic reduces the underlying interchange; they reduce the effective rate paid on the merchant's actual traffic mix.

  3. 03

    Are credit card payment fees always higher than debit?

    On most schemes and regions, credit card payment fees carry a higher interchange band than debit, particularly for premium, commercial and corporate products. The routing engine reads the BIN tier on each authorisation and selects the acquirer whose effective rate is best for that specific tier — including, where supported, debit-routing optimisations on the US Durbin networks.

  4. 04

    What about gateway fees as a separate line item?

    Gateway fees on the platform are always a separate line on the reconciliation feed — never blended into interchange or acquirer markup. The number is what you'd see on a contract spreadsheet; no hidden basis points are buried in another component.

  5. 05

    What is the platform's gateway fees structure?

    Gateway fees structure on topropay is per-authorisation, with optional volume tiers above defined thresholds. There is no mandatory monthly retainer, no minimum-fee floor and no upfront integration charge. Specific numbers are commercial — covered during onboarding once your traffic shape is mapped.

  6. 06

    How do gateway fees on credit card processing typically differ from ACH?

    Gateway fees on credit card processing are usually small percentage components on top of interchange and scheme fees; ACH equivalents are flat per-transaction. The platform shape is the same — one unified API, one reconciliation feed — but the per-method cost curves differ, which is why high-ticket merchants often route part of their volume to ACH where it's available.

  7. 07

    How are ach payment fees handled inside the platform?

    ACH payment fees are typically flat-rate per transaction rather than percentage-based. topropay exposes ACH on the same unified API as card and reconciles ACH settlements into the same ledger. Routing policies can prefer ACH for high-ticket purchases or for buyer cohorts that consent to bank-rail debit.

  8. 08

    What drives international payment fees up?

    International payment fees stack three things: a higher interchange tier (the cross-border component), a scheme cross-border assessment, and an FX margin. Multi-acquirer routing helps the first two by keeping authorisations on regionally local acquirers where the BIN supports it; FX margin is a settlement-currency policy choice rather than a routing decision.

  9. 09

    Can the platform power immigration fees online payment portals?

    topropay can power the merchant-side payment infrastructure behind government and immigration-fee collection portals — i.e. the platform that processes the card or bank-rail payment on the agency's behalf. For individuals paying immigration fees online directly, the correct path is the official government portal in the relevant jurisdiction; topropay does not sell B2C portals to end-users.

  10. 10

    Why publish a gateway fees structure rather than a single rate card?

    A single rate card hides the truth that landed cost depends on BIN, scheme, currency, country and routing policy. A gateway fees structure that exposes the components — interchange-plus, per-acquirer markup, separate platform fee — gives the merchant a model they can actually predict against, instead of a vendor headline.

  11. 11

    How are card payment fees reconciled across multiple acquirers?

    Card payment fees across multiple acquirers reconcile into one normalised ledger keyed off vault tokens. Each authorisation's settlement, scheme fees, acquirer markup, platform fee and any chargeback impact land in the same export, tagged with the acquirer ID it landed on. Finance closes the month from one file regardless of how many acquirers sat upstream.

  12. 12

    Do payment fees go down when volume scales?

    Payment fees do scale with volume, but the dominant driver is interchange, which the merchant cannot negotiate. What does scale: acquirer markup (with the right relationship), platform tiering above defined thresholds, and the effective rate through better routing as more historical data informs the routing engine.

  13. 13

    Where can I see actual fee numbers per authorisation?

    Inside the merchant dashboard, every authorisation is tagged with its acquirer, BIN, scheme and per-line fee components when the underlying acquirer supports the data. Roll-ups by day, week, month, acquirer, scheme, BIN range and merchant segment are all standard views; CSV and Parquet exports are scheduled per-merchant.

  14. 14

    What's the difference between a flat-rate and an interchange-plus model on this platform?

    Flat-rate is a single headline number per transaction with all components blended together; interchange-plus exposes the underlying components and adds the acquirer's markup and the platform's fee as separate lines. topropay defaults to interchange-plus where the underlying acquirer supports it because the model is auditable; a flat-rate model is available on request for merchants who prefer the simpler invoice.