Payment gateway cost
Payment gateway cost, transparently broken down.
topropay prices the payment gateway as four pass-through components: interchange, scheme assessment, acquirer markup and a transparent platform fee. No monthly retainer, no bundled blended rate, no surprise mid-month adjustments.
- Interchange 0.30% €0.30
- Scheme assessment 0.10% €0.10
- Acquirer markup 0.15% €0.15
- topropay platform 0.20% €0.20
No retainer · no monthly minimum · sandbox unmetered
- 0 retainer
- no monthly minimum
- Pass-through
- interchange + scheme fees
- 1 line
- platform fee per authorisation
- Free
- sandbox for testing
Anatomy of the cost
What the four components of a card-authorisation gateway cost actually are
Most of the payment gateway cost sits in interchange and scheme fees — both of which are scheme-set, the same number every provider in the world pays. The differences between providers live in the acquirer markup and the platform fee on top.
-
Issuer-side scheme fee — the largest single component on card authorisations. Set by Visa / Mastercard / Amex by scheme tier (consumer, premium, commercial), country pair and product. Passes through transparently.
-
Visa / Mastercard / Amex assessment fee — small per-transaction component. Set by the scheme; same as interchange, passes through transparently.
-
The connected acquirer's per-authorisation fee. Varies per acquirer; the routing engine picks the lowest-cost route per BIN, scheme and country pair where the merchant policy allows.
-
The platform's per-authorisation fee, on a separate line on the invoice. Pricing compresses at volume bands agreed up-front; the platform never bundles interchange or scheme fees into this number.
Key benefits
Why the cost of payment gateway falls with orchestration
Four outcomes that show up consistently once the merchant moves from a bundled blended-rate single provider to topropay's transparent pass-through pricing.
- 01
No platform retainer, no monthly minimum
The cost of payment gateway access on topropay is per-authorisation. No fixed monthly fee, no per-environment fee, no sandbox metering — merchants pay when they process. Small and growing merchants don't subsidise a contract floor.
- 02
Interchange and scheme fees pass through
Interchange and scheme assessments — by definition the largest cost on a card authorisation — pass through transparently where the underlying acquirer supports interchange-plus pricing. The platform doesn't bundle them into an opaque blended rate.
- 03
Routing reduces effective landed cost
The routing engine picks the route with the lowest landed cost per BIN, scheme and country pair on every authorisation. On real merchant traffic this typically saves more on cost than the platform fee adds — net effect is often lower than the merchant's previous single-provider arrangement.
- 04
Lower-cost rails for the right traffic
Where local bank rails — iDEAL, PIX, BLIK, ACH, SEPA Direct Debit — cost less than card for a given authorisation, the platform surfaces them next to card on the same checkout. Low cost payment processing for the right segment becomes a routing-policy choice.
Integration cost
Cost of payment gateway integration on topropay
The platform doesn't charge an integration fee — the merchant's cost is engineering time. Four shapes, four engineering footprints.
- 01
Hosted checkout
Drop-in redirect or iframe with a signed session token plus one webhook handler. Cost of payment gateway integration on this path is in days — a sprint of engineering, no specialist payments hire required.
- 02
Embedded SDK
Hosted card fields inside the merchant's own checkout with full UI control around them. Integration cost is in weeks; the team builds the surface, the platform handles vault and PCI scope.
- 03
Low-level SDK / API
Full custom checkout against the REST API. Integration cost scales with surface complexity; a competent payments engineer ships it in a few sprints.
- 04
Sandbox
Sandbox is free and unmetered. The full integration builds against the sandbox before any live volume — no cost of payment gateway integration testing line on the invoice.
How it works
How low cost payment processing actually works inside the platform
Five concrete levers that reduce the per-authorisation cost on real merchant traffic — without sacrificing approval rate, dispute outcomes or settlement timing.
- 01
Pick a routing policy
Approval-, cost-, or composite-weighted — set per region from the dashboard. Cost-weighted routing optimises specifically for lowest landed cost per authorisation.
- 02
Enable interchange-plus where supported
Where the underlying acquirer supports it, the merchant runs on interchange-plus pricing — interchange and scheme fees pass through transparently, the acquirer markup is a separate line.
- 03
Surface the cheapest rail per shopper
iDEAL in NL, PIX in BR, BLIK in PL, ACH in US — bank rails often beat card on flat-fee economics. The checkout surfaces them per market without per-method plug-ins.
- 04
Cascade and retry intelligently
Soft declines cascade to the next ranked acquirer inside the same request — no double-charge, no retry cost on the merchant side. The cost of a recovered authorisation is the routing decision plus the underlying provider's standard fee.
- 05
Settle into one reconciliation feed
Settlements, fees, refunds and chargebacks normalise into one ledger keyed off vault tokens. Daily exports drop straight into ERP — no separate cost-recon tool to bolt on.
Main use cases
Where the cost story lands hardest
Six merchant shapes that benefit disproportionately from a transparent cost model with cost-weighted routing on top.
- DTC
DTC brands on tight unit economics
Per-authorisation fees compound at scale; the low cost payment gateway shape on topropay (no retainer, interchange-plus pass-through, cost-weighted routing) protects margin on every transaction without sacrificing approval rate.
- Subs
Subscription merchants and recurring billing
Recurring traffic benefits from low ACH payment cost on US flows and SEPA Direct Debit on EU flows — both flat-fee instead of percentage-based. The same recurring engine handles card-on-file too.
- Mkt
Marketplaces with thin take-rates
Marketplaces operating on thin take-rates need fee predictability. Pass-through interchange + a transparent platform fee make the per-transaction P&L line item calculable to four decimal places.
- B2B
B2B invoicing with bank-rail emphasis
Where a B2B merchant pays through invoice-driven flows, ACH and SEPA Direct Debit dramatically beat card on landed cost. The ach payment cost angle on US bills makes a measurable difference at scale.
- Cross-border
Cross-border merchants exposed to FX
Cross-border interchange and FX fees compound; per-BIN routing across the acquirer panel reduces the effective fee on every cross-border authorisation by picking the route that minimises landed cost per country pair.
- Mobile
Mobile-first merchants
Cost of payment gateway for website checkouts and native mobile pay-sheets is the same — Apple Pay and Google Pay routes typically clear at lower landed cost than card form, because tokenisation lowers interchange tier.
Pricing model comparison
Bundled blended rate vs transparent pass-through
Two valid pricing models. The bundled rate is the simpler buy; the pass-through model costs less in practice but requires the merchant's finance team to read four lines instead of one.
| Dimension | Bundled blended rate | topropay pass-through |
|---|---|---|
| Headline pricing | Blended monthly rate (one number, opaque) | Interchange + scheme + acquirer + platform — four transparent lines |
| Monthly retainer | Often required to access the gateway | None — pay per authorisation |
| Interchange visibility | Bundled into the blended rate | Pass-through line on the invoice |
| Acquirer cost | Hidden inside the blend | Visible per-authorisation per BIN, with routing across multiple acquirers |
| Sandbox / testing | Sometimes metered or rate-limited | Free and unmetered |
| Volume bands | Discounts at one volume threshold | Compression at multiple volume bands, agreed up-front |
Platform features
Capabilities behind the cost story
What the platform ships specifically for the cost angle — invoice transparency, routing levers, volume-band economics and audit-ready reconciliation.
-
Transparent invoice lines
Every authorisation row shows interchange, scheme, acquirer and platform fees separately. Finance reads the cost stack without a decoder.
-
Cost-weighted routing
Routing policy that picks the route with the lowest landed cost per authorisation across the connected acquirer panel.
-
Per-rail price visibility
Card, ACH, SEPA, iDEAL, PIX, BLIK and crypto all surface their per-rail cost in dashboard analytics.
-
Volume-band compression
Per-authorisation platform fee compresses at agreed volume bands; the compression schedule is in the contract, not a sales conversation.
-
No platform retainer
No monthly minimum, no per-environment fee, no sandbox metering.
-
Interchange-plus pass-through
Interchange and scheme fees pass through transparently where the underlying acquirer supports it.
-
FX as a policy
Settlement currency per market is a policy choice — merchants don't carry FX they didn't ask for.
-
Refund / chargeback economics
Refunds and chargeback fees surface on the same per-authorisation row as the original; no opaque adjustment lines.
-
Sandbox parity
Sandbox mirrors production for testing routing decisions and cost outcomes against representative traffic.
-
Operator portal
Per-method, per-acquirer, per-BIN cost analytics in the same dashboard as authorisation analytics.
Trust & compliance
Posture behind the pricing model
Transparent pricing only works if the rest of the posture — interchange compliance, audit-ready invoicing, contracted volume bands — is solid.
- PCI DSS Level 1
- Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture regardless of method mix.
- Interchange transparency
- Interchange and scheme assessments pass through transparently per scheme rules — the merchant sees the same number the acquirer sees.
- Audit-ready invoicing
- Every authorisation row references the BIN, scheme, acquirer ID and routing policy that ran it; cost lines are reconcilable to scheme reports.
- Volume-band contracts
- Volume-band compression sits in the merchant contract; commercial reviews reference the contract, not ad-hoc adjustments.
- No hidden fees
- Refund-of-refund fees, mid-month rate changes, surprise platform fees — out of scope on the topropay contract.
- 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 pricing model.
Ready to compare
See your traffic on a transparent cost stack.
A 30-minute pricing review takes a sample of the merchant's authorisation traffic, breaks down the current effective cost into the four-component stack, and compares it against the orchestrated equivalent on topropay. No sales pitch — a working model.
Frequently asked
Buyer questions about payment gateway cost
Questions buyers ask before they commit — invoice anatomy, integration cost, build vs buy, volume bands, FX and crypto rails.
- 01
What does payment gateway cost actually consist of?
Payment gateway cost consists of four components on a card authorisation: interchange (the largest, paid to the issuer; set by Visa / Mastercard / Amex), scheme assessment (small per-transaction fee paid to the network), the connected acquirer's markup, and the platform fee. On non-card rails (ACH, SEPA, iDEAL, PIX) the cost structure simplifies — typically a flat per-authorisation rail fee plus the platform fee.
- 02
How is cost of payment gateway typically presented on the invoice?
Cost of payment gateway on topropay's invoice is presented as four transparent lines per authorisation row: interchange, scheme, acquirer markup, and platform fee. The merchant's finance team can reconcile each line to the underlying scheme report or acquirer statement without a decoder ring.
- 03
What's the ach payment cost compared to card?
Ach payment cost is typically a flat per-transaction fee rather than percentage-based — meaningfully lower than card for higher-ticket authorisations and slightly higher than card for very low-ticket ones. The crossover usually sits in the low-tens-of-dollars range; ACH wins above it, card sometimes wins below.
- 04
How does cost of payment gateway integration work on topropay?
Cost of payment gateway integration is the merchant's engineering cost — there is no platform-side integration fee. Hosted-checkout integration costs days of engineering; embedded SDK or low-level SDK costs weeks. The sandbox is free; sandbox usage doesn't appear on the invoice.
- 05
Is there a low cost payment gateway tier for small merchants?
Low cost payment gateway pricing on topropay is the default for small merchants — no platform retainer, no monthly minimum, pay per authorisation. Volume-band compression kicks in as the merchant grows; small merchants pay the entry-band per-authorisation fee until they hit the next band.
- 06
What's the gateway cost difference between high and low ticket merchants?
Gateway cost differs by ticket size because interchange and scheme fees are percentage-based on card. A high-ticket merchant benefits more from routing optimisation (cost-weighted routing per BIN); a low-ticket merchant benefits more from surfacing flat-fee bank rails (ACH, SEPA) and wallets at checkout.
- 07
How does low cost payment processing actually work in practice?
Low cost payment processing comes from three levers: pass-through interchange (no bundling), cost-weighted routing (lowest landed-cost route per authorisation), and rail substitution (surfacing cheaper rails where they fit the buyer profile). topropay supports all three; the merchant configures the policy from the dashboard.
- 08
What's the typical payment gateway cost for website checkouts?
Payment gateway cost for website checkouts on topropay is per-authorisation, with the four-line cost stack described above. The headline platform fee compresses at agreed volume bands; the underlying provider economics depend on the merchant's vertical, geography mix and method mix.
- 09
How does cost of payment gateway for website at scale compare to a single provider?
Cost of payment gateway for website at scale on topropay typically beats a single-provider arrangement because routing reduces the average landed cost per authorisation. The platform fee on top of the pass-through stack is usually smaller than the routing savings on real merchant traffic — net effect is lower total cost.
- 10
What's the payment gateway cost to build in-house vs use topropay?
Payment gateway cost to build in-house is heavy and recurring: PCI DSS Level 1 certification ($150-300K initial, $50-100K annual), per-acquirer underwriting (months per acquirer), engineering for routing, vault, dispute, reconciliation (a multi-engineer team for 12+ months), plus ongoing scheme programme tracking. Using topropay collapses all of that into a per-authorisation platform fee.
- 11
Is the sandbox metered into the gateway cost?
No. Sandbox is free and unmetered. Merchants build the full integration against the sandbox — routing, cascade, refund and chargeback scenarios — without anything appearing on the invoice. Production volume is the only billed traffic.
- 12
How are chargebacks priced inside payment gateway cost?
Chargebacks are priced as a per-case fee from the underlying scheme / acquirer, passed through on the same invoice line as the original authorisation. The platform doesn't add its own chargeback margin. Successful representments refund the case fee where the scheme rules support it.
- 13
How does FX affect cost of payment gateway?
FX affects cost of payment gateway on cross-border authorisations where the settlement currency differs from the authorisation currency. topropay's settlement-currency-per-market policy lets merchants hold the currency they want; FX conversion happens on receipt at the rail's quote, surfaced as a separate line on the invoice rather than bundled into the headline rate.
- 14
Are volume discounts automatic or negotiated?
Volume-band compression is contracted up-front — the schedule is in the merchant agreement, with the platform fee compressing as the merchant crosses each band. Bands and thresholds are negotiated during onboarding; the compression itself is automatic once contracted.
- 15
How does the cost compare for crypto rails?
Crypto rails carry the underlying partner crypto gateway's per-transaction fee (typically lower than card on high-ticket flows) plus the platform fee. Conversion-on-receipt FX appears as a separate line where the merchant has opted in. Total landed cost is often the lowest of any rail for cross-border B2B and high-ticket flows.
Related
Related on the topropay platform
- Fees Online payment fees: structure and cost The wider fee structure — interchange, scheme, acquirer and gateway components explained per method.
- Cards Credit card processing fees Card-specific fee dynamics — interchange tiers, scheme assessments and the acquirer markup.
- Routing Smart routing & cascading The routing engine that turns the cost story into a per-transaction policy decision.
- Finance Reconciliation & reporting How the four-component cost lines surface in the daily reconciliation export.
- Aggregation Payment aggregator overview The aggregation pattern that makes pass-through pricing across many providers possible.
- Catalogue Payment services catalogue Every service category the same pricing model applies to — card, ACH, crypto, facilitation and subscriber.