Category consolidation

Popular payment gateways — consolidated under one API.

Rather than committing to one popular payment gateway, topropay lets merchants run a panel of them side-by-side. Per-transaction routing picks the best gateway per BIN, currency and country pair. Cascade covers soft declines. Reconciliation is one feed across the lot.

Book a panel review Read the API docs

Category leaders

The six categories of most popular payment gateways

'Popular' means different things per market and per merchant. Six category cards covering the shapes of connected gateway that appear most often in real-world evaluations.

  1. 01

    Global card gateways

    The most-recognised names in cross-border card acceptance. Broad scheme coverage, mature 3DS2 implementations, network-token support. On topropay these plug in as connected lanes; the routing engine picks the best one per BIN and country pair rather than the merchant committing upfront.

  2. 02

    Wallet-native gateways

    Apple Pay, Google Pay and Click to Pay-oriented gateways with strong tokenisation. Popular for mobile-heavy merchants. On topropay they surface alongside inline card entry through the same hosted checkout surface — no separate integration per wallet.

  3. 03

    Bank-rail specialists

    US ACH (NACHA-compliant), EU SEPA (SCT / SCT Inst / SDD) and UK Open Banking specialists. Popular for subscription and B2B billing where interchange cost matters. On topropay they ride the same authorisation engine as card.

  4. 04

    Regional bank rails

    PIX (Brazil), iDEAL (NL), Bancontact (BE), PayID / OSKO (AU), Interac (CA). Regionally dominant rather than globally 'popular' — but locally the highest-conversion option. topropay surfaces them per market on the same checkout.

  5. 05

    BNPL platforms

    Klarna, Afterpay, Affirm, Clearpay, Atome and friends. Popular for basket uplift on higher-ticket ecommerce. On topropay they plug into the same authorise endpoint as card — settlement and refund flows match the card-side shape.

  6. 06

    Crypto gateways

    Licensed stablecoin and majors specialists. A growing but still minority category. On topropay they run via partner crypto gateways with optional conversion-on-receipt so the merchant's treasury stays fiat-only.

One vs many

Committing to one popular gateway vs routing across the panel

Five axes that tend to flip between picking one popular gateway and running a panel behind an orchestration layer.

Axis Single popular gateway topropay panel
Choice of gateway Pick one 'popular' gateway upfront Route across a panel of connected gateways per transaction
Approval rate Locked to that gateway's BIN routing Per-transaction scoring across the panel; cascade on soft decline
Coverage Limited to that gateway's geographies Panel spans EU, UK, APAC, LATAM and US behind one contract
Reconciliation One settlement feed per gateway One normalised ledger across every connected gateway
PCI scope Per-gateway PCI integration PCI L1 vault inherited regardless of which gateway clears the auth

Key benefits

Why merchants stop picking one 'best' popular payment processor

Four properties that show up the moment a merchant stops trying to pick one perfect popular payment gateway and starts running a panel.

Don't pick just one popular gateway

Every gateway is 'the best' for some subset of BINs, currencies and country pairs. Running a panel means the merchant gets the best of each without pre-committing.

Change providers without re-integrating

Adding, removing or reweighting a popular payment gateway on the panel is a dashboard change. The merchant's checkout code never changes.

Insulate from vendor risk

A popular gateway with an outage, a scheme-programme excursion or an acquirer switch is a routing-weight adjustment — not an incident. Traffic reroutes automatically.

One reconciliation across the panel

Settlements, interchange, fees, refunds and chargebacks from every connected gateway normalise into one ledger for finance.

How the panel runs underneath most popular payment systems

From connected panel to settled authorisation in four steps

What actually happens between the connected panel being enabled and a settled row in the merchant's reconciliation feed.

  1. 01

    Select the panel

    topropay's onboarding identifies the popular payment processors relevant to the merchant's geographies, verticals and BIN mix. The connected panel is enabled per merchant.

  2. 02

    Define routing weights

    Per-BIN, per-currency and per-country routing rules rank the panel for each authorisation. Weights are dashboard-editable and can be pinned or A/B-tested.

  3. 03

    Route, cascade and settle

    Each authorisation runs the top-ranked route; soft declines cascade to the next-ranked gateway inside the same auth. Captures and settlements flow through per-gateway relationships.

  4. 04

    One ledger

    Settlement files from every gateway normalise into one reconciliation feed; daily exports tagged by gateway, scheme, currency and routing policy.

Main use cases

Where a panel of popular payment gateways earns its keep

Six recurring merchant shapes that benefit from routing across popular gateways rather than committing to one.

  • DTC

    Cross-border DTC brands

    DTC brands that need to accept card + wallet + regional bank rail per market surface all three from the same checkout, backed by a panel of popular payment gateways.

  • SaaS

    SaaS with global card volume

    Global SaaS routes recurring cards across a panel; account updaters and network tokens keep renewals alive without the merchant integrating each popular gateway's token API.

  • Plat

    Marketplaces / two-sided platforms

    Different sellers land on different connected gateways based on volume, risk and geography; reconciliation rolls up by seller and by gateway in one feed.

  • Travel

    Travel and ticketing

    Auth-only + delayed capture across the panel; refunds on the original vault token even if the underlying gateway changed since the sale.

  • B2B

    B2B and invoicing

    Card on small tickets, ACH or SEPA SDD on recurring contracts — the merchant doesn't need to know which popular gateway carries each authorisation.

  • PSP

    PSPs & resellers

    PSPs offer their downstream merchants the connected popular gateways under one API; PSP keeps the merchant relationship and pricing, platform handles per-gateway message exchange.

Platform features

Capabilities shared across every connected popular gateway

Twelve capabilities the platform ships once and reuses across every connected popular gateway — the primitives that make the panel feel like one product.

  • Unified API across gateways

    One REST contract for card, ACH, SEPA, wallet, BNPL and crypto gateway connectivity.

  • Hosted, embedded & SDK surfaces

    Three integration shapes share the same back-end — picked per merchant's PCI and UI constraints.

  • Smart routing engine

    Per-transaction scoring on BIN, scheme, currency, country pair and risk across the connected panel.

  • Cascade & retry

    Soft declines cascade to the next-ranked gateway inside the same authorisation; nothing leaks back to the buyer.

  • PCI DSS Level 1 vault

    Card data captures into the platform vault before any gateway sees it; PAN never lands in merchant systems.

  • Network tokens & updaters

    Network tokens (VTS, MDES) by default for card; scheme updaters keep saved credentials alive across re-issuance.

  • 3DS2 / SCA orchestration

    Selective EMV 3DS2 per authorisation — PSD2-compliant in Europe without breaking conversion.

  • Unified dispute queue

    One queue across gateways; evidence-pack templates per vertical; automated representment for select scheme types.

  • Risk & fraud controls

    Velocity rules, list management and partner-agnostic fraud-engine connectors layered on top of routing.

  • Per-merchant routing policies

    Independent routing weights per merchant or per merchant-group; resellers configure their downstream merchants individually.

  • One reconciliation feed

    Settlements, fees, refunds and chargebacks across every connected gateway normalised into one ledger.

  • Webhooks & accounting connectors

    Signed lifecycle events; connectors for popular ERPs and accounting systems for downstream ingestion.

Industry relevance

Popular gateway consolidation for licensed EU, UK, APAC and LATAM merchants

topropay's panel approach targets licensed merchants operating across Europe, the UK, APAC and LATAM — DTC brands with cross-border card volume, SaaS billing on recurring cards, marketplaces routing per seller, travel and ticketing, B2B invoicing, and licensed gaming where current operating licences exist.

Trust & compliance

Compliance posture across every connected popular gateway

One audited environment plus per-gateway scheme-programme positions surfaced in the dashboard.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture across every connected gateway.
Scheme programmes
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP positions surfaced per gateway; routing weights can rotate around at-risk lanes.
SCA & PSD2
Selective 3DS2 on the authorisation path keeps approval high in Europe without skipping the SCA bar.
Bank-rail mandate posture
NACHA authorisations for ACH, SEPA mandate IDs for SEPA Direct Debit; captured and retained per scheme rules.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical, volume and country mix.
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 which popular gateway clears the auth.

Ready to consolidate

Stop picking one popular payment gateway. Run the panel.

A 30-minute panel review covers the popular payment gateways relevant to your geographies and BIN mix, routing weights tuned to your traffic, and a sandbox to test against before any commercial commitment.

Book a panel review Read the API docs

Frequently asked

Buyer questions about popular payment gateways on topropay

Definitions, category vs vendor, BYO-acquirer patterns, pricing and the practicalities of running a panel of connected gateways instead of one.

  1. 01

    Which popular payment gateways does topropay actually connect to?

    topropay's connected panel spans the popular payment gateways across the card, ACH, SEPA, wallet, BNPL, regional-bank-rail and crypto categories. The specific vendor list is shared under NDA during onboarding — the panel changes as new providers are added and weights rotated. What stakeholders care about — geographic coverage, scheme support and scheme-programme posture per gateway — is shared in writing as part of underwriting.

  2. 02

    Aren't the most popular payment gateways just card gateways?

    In global CNP volume the most popular payment gateways are card-scheme-oriented, yes. But 'popular' varies by market — PIX is the most popular rail in Brazil, iDEAL in the Netherlands, Bancontact in Belgium, ACH for US recurring. topropay's panel spans all of them so the merchant doesn't have to pick per market.

  3. 03

    Are popular payment processors the same as popular payment gateways?

    Colloquially yes, but there's a technical distinction. A payment gateway is the front-end surface that captures and encrypts the card. A payment processor is the back-end acquirer relationship that clears the authorisation with the scheme. Popular payment processors and popular payment gateways often overlap in one vendor; on topropay both roles are unified behind one API.

  4. 04

    Who are the most popular payment processors for cross-border merchants?

    The most popular payment processors for cross-border merchants are the global-scale acquirers with wide scheme licences and mature 3DS2 implementations. On topropay's connected panel these appear as ranked lanes; the merchant's authorisations route across them per BIN and country pair rather than being pinned to one.

  5. 05

    What about the most popular payment systems more broadly?

    The most popular payment systems globally are card schemes (Visa, Mastercard), bank rails (ACH, SEPA, PIX) and wallets (Apple Pay, Google Pay). BNPL platforms and crypto rails are growing categories. topropay's unified API surfaces all these payment-system categories through the same integration — the merchant enables the mix relevant to their buyers.

  6. 06

    How do I know which popular payment gateway would suit my business?

    The right popular payment gateway depends on the merchant's geographies (which acquirers hold the right licences), vertical (whether the acquirer will underwrite the MCC), BIN mix (which issuers approve well with which acquirer) and volume (which gateway offers cost-competitive pricing at that tier). topropay's onboarding review identifies the relevant popular gateways for the merchant's profile.

  7. 07

    Can I compare popular payment gateways head-to-head on topropay?

    Yes. The routing-policy editor supports A/B splits — the merchant can weight two popular payment gateways 50/50 for a defined BIN range and compare approval rate, decline reason mix and effective landed cost after fees. Results drive the routing weights going forward.

  8. 08

    Do popular payment gateways charge extra when accessed through an orchestration layer?

    Pricing depends on the merchant's contract with the connected acquirer / gateway. Some are direct-billed, some are billed via the orchestration layer with a pass-through fee. In both cases the merchant sees the full cost breakdown in the unified ledger — no hidden margin between what the gateway charges and what the merchant pays.

  9. 09

    What happens if a popular payment gateway I use isn't in the connected panel yet?

    If a popular payment gateway relevant to the merchant isn't in the connected panel yet, the platform can typically add it as a new connector — subject to the gateway's certification requirements and licensing constraints. Onboarding a new connected gateway typically takes weeks, not months.

  10. 10

    Do popular payment gateways all support 3DS2?

    The most popular payment gateways all support EMV 3DS2 in some form, but implementation quality varies. topropay's selective 3DS2 orchestration abstracts the differences — the merchant integrates the platform's 3DS API once and the platform handles per-gateway variations.

  11. 11

    Can I use topropay purely as a routing layer in front of the popular payment processors I already work with?

    Yes. If the merchant has existing contracts with popular payment processors, those relationships can be brought into the connected panel (subject to gateway-side approval) so the routing engine can rank them alongside the platform's baseline connections. This 'BYO-acquirer' pattern preserves the merchant's negotiated pricing.

  12. 12

    Do the most popular payment systems require different SDKs on the client side?

    Historically yes — each of the most popular payment systems shipped its own SDK. On topropay one client-side SDK covers card, wallet (Apple Pay, Google Pay, Click to Pay), bank rails and BNPL surfaces. The merchant's front-end code doesn't need per-system integration.

  13. 13

    How does topropay handle branding when the connected popular gateway shows on statements?

    The cardholder-side statement descriptor is configured against the connected acquirer's rules — usually the merchant's brand plus a short suffix, not the gateway's name. The gateway identity surfaces only on settlement statements and dispute documentation, not in the buyer flow.

  14. 14

    Is topropay itself a popular payment gateway?

    topropay is best described as the orchestration layer sitting above popular payment gateways rather than being one itself. It exposes one unified API in front of the connected panel — vault, routing, tokenisation, dispute queue and reconciliation are platform-owned; per-region acquiring licences and scheme relationships sit with the connected gateways.

  15. 15

    What if popularity shifts and a different gateway becomes the leader?

    The connected panel is designed to rotate. If a new gateway becomes popular in a given market or category, it can be added to the panel and given routing weight; if an incumbent loses market share or scheme-programme standing, its weight can be lowered. The merchant doesn't re-integrate — they re-tune.

Related

Related on the topropay platform