Scored per authorisation · cascade in-flight

Intelligent payment routing — one scored panel per authorisation.

Every authorisation runs through a scored panel of connected acquirers, PSPs and rails. Signals include BIN, scheme, currency, country pair, risk and live scheme-programme position. Soft declines cascade to the next ranked lane inside the same authorisation.

Book a routing review Read the API docs
BIN
issuer identification & approval history
Scheme
Visa · Mastercard · Amex · JCB · RuPay
Currency
settlement + interchange band
Risk
device · velocity · list · vertical

Key benefits

Why per-transaction payment routing beats static routing

Four properties that show up the moment routing stops being a fixed policy and starts being a scored decision per authorisation.

  1. 01

    Higher approval rate per authorisation

    Every authorisation runs through the highest-EV lane at that moment — chosen from a scored panel rather than pinned to one acquirer.

  2. 02

    Soft-decline cascade inside the same auth

    When a lane returns a soft decline, the next ranked lane picks up the retry in-flight — the buyer sees one final decision, not a chain of failures.

  3. 03

    Effective landed cost, per-tx

    Interchange band, scheme fee band and acquirer take are all inputs to the scoring — the routing engine can favour margin on price-sensitive verticals.

  4. 04

    Compliance-aware routing

    Scheme-programme position per acquirer (VDMP/VAMP/VFMP, ECP/EFMP) can automatically down-weight at-risk lanes without a human touching the policy.

How the payment routing solution works

From signal collection to routed outcome in four steps

What actually happens between the buyer's checkout submit and the acquirer's authorisation response — and where the scoring engine sits in that chain.

  1. 01

    Signals collected

    Every authorisation carries BIN, scheme, amount, currency, country pair, device fingerprint, list-hit flags and vertical tags into the routing engine.

  2. 02

    Providers scored

    The engine scores every connected provider on that signal set — a real number per lane per authorisation — using per-merchant weights layered on the platform defaults.

  3. 03

    Top lane picks up

    The top-ranked lane receives the authorisation. If a soft decline comes back, the next ranked lane picks up the retry inside the same authorisation.

  4. 04

    Outcome feeds back

    The approval / decline outcome updates the rolling per-lane metrics that feed the next authorisation's scoring — the engine learns from production traffic.

Signals

What the payment routing platform actually reads

Six signal families feed the scoring. Each is a live input, not a static tag — the weights adapt to production behaviour.

  • Issuer BIN and bank health

    Live approval-rate percentiles per issuer BIN feed the engine; underperforming BINs get shifted to the acquirer that clears them best.

  • Scheme + product family

    Visa vs Mastercard vs Amex vs Discover vs JCB vs RuPay; consumer vs commercial vs prepaid BIN ranges — each has its own optimal lane.

  • Currency and interchange band

    Domestic vs cross-border interchange; scheme-fee bands vary by settlement currency; the engine can favour locally-acquired lanes to compress cost.

  • Country pair (issuer × acquirer)

    Cross-border authorisations often clear better through a locally-domiciled acquirer for the issuer's country — the engine tags acquirers accordingly.

  • Device & velocity signals

    Repeated declines from a device fingerprint, unusual velocity from a card, or list hits down-weight the auth or route it through a stricter lane.

  • Scheme-programme posture

    Each acquirer's live position vs VDMP / VAMP / VFMP (Visa) and ECP / EFMP (Mastercard) is surfaced; policies can rotate around at-risk lanes.

Policy shapes

Four ways to shape dynamic payment routing per merchant

Four policy shapes cover the range from deterministic weights through production-metric-adaptive routing to cost- and compliance-aware behaviour.

Static weights

Per-merchant weights per BIN-range, per-scheme, per-currency and per-country. Simple, deterministic, dashboard-editable — good for merchants with predictable traffic.

Dynamic scoring

Weights adjusted by rolling per-lane metrics (approval rate, dispute rate, response time). The engine reacts to production behaviour without a human touching the policy.

Cost-optimising

Effective landed cost per authorisation (interchange + scheme + acquirer take) enters the scoring. Useful for high-volume, thin-margin verticals — subscriptions, DTC.

Compliance-aware

Scheme programme position (VDMP / VAMP / VFMP, ECP / EFMP) automatically de-weights at-risk acquirers so merchants don't tip programme thresholds.

Main use cases

Where international intelligent payment routing earns its keep

Six recurring shapes where scored per-transaction routing produces a measurable approval and cost lift versus a fixed-lane setup.

  • Card

    Card acceptance with cross-border volume

    Cross-border card authorisations route to the acquirer with local presence for the issuer's country; interchange bands compress; approval lifts.

  • SaaS

    Recurring SaaS on network tokens

    Recurring authorisations use scheme-provided network tokens; the routing engine chooses the best lane per BIN even for silent renewals — declining renewals cascade.

  • APM

    APMs on a per-market lane

    Alternative payment methods (iDEAL, PIX, Bancontact) sit on the same routing engine — market-specific lanes chosen per shopper region.

  • ACH

    ACH routing across processors

    Different ACH processors have different approval profiles per bank (BIN). The routing engine picks the highest-clearing ACH lane for each merchant's traffic mix.

  • Crypto

    Crypto rails on partner gateways

    Multiple partner crypto gateways behind one API; per-currency and per-chain routing across the panel; stablecoin-vs-native preference dashboard-configurable.

  • HR

    High-risk with programme-aware routing

    Licensed high-risk verticals get scheme-programme-aware routing — the engine automatically shifts weight away from acquirers approaching VDMP / VAMP / ECP thresholds.

Platform features

Capabilities of the payment routing infrastructure

Twelve capabilities the platform ships once and reuses across every rail the routing engine touches.

  • Per-transaction scoring

    Every authorisation gets its own scored panel of connected lanes; nothing is pinned in advance.

  • In-auth cascade

    Soft declines cascade to the next ranked lane inside the same authorisation; the buyer sees one final decision.

  • Rolling metrics

    Per-lane approval rate, dispute rate and response time updated in real time from production traffic; weights react automatically.

  • Dashboard policy editor

    Per-BIN, per-scheme, per-currency, per-country weights editable in the dashboard; simulator shows the resulting routing for a test authorisation.

  • 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 challenges gated on PSD2 exemption logic and per-issuer behaviour.

  • PCI DSS Level 1 vault

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

  • Programme-position telemetry

    Live per-acquirer position vs Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP surfaced in the dashboard.

  • Fraud-engine plug-ins

    Partner-agnostic fraud-engine connectors feed scores into the routing engine per transaction.

  • Cost model input

    Interchange, scheme fee and acquirer take enter the scoring alongside approval; policies can bias toward margin.

  • Multi-rail support

    Same routing engine across card, ACH, SEPA, wallets, BNPL and crypto — one scoring surface, many rails.

  • Unified reconciliation

    Settlements from every routed lane normalise into one ledger tagged by acquirer, scheme, currency and routing policy.

Industry relevance

Intelligent payment solutions for licensed EU, UK, APAC and LATAM merchants

topropay's routing engine targets licensed merchants operating across Europe, the UK, APAC and LATAM — DTC and retail with international volume, SaaS billing on recurring, marketplaces routing per seller, travel and ticketing with delayed capture, and licensed high-risk verticals where scheme-programme-aware routing is critical.

  • DTC · cross-border card volume
  • SaaS · recurring on network tokens
  • Travel · delayed capture
  • Marketplaces · per-seller routing
  • Bank-rail merchants · ACH / SEPA
  • Licensed high-risk verticals (where licensed)
  • Adult · out of scope
  • Unlicensed gambling · out of scope

Trust & compliance

Compliance posture across every routed lane

One audited environment underpins the orchestration layer; scheme-programme positions per acquirer feed straight into routing weights so merchants don't tip programme thresholds.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture across every routed lane.
Scheme programmes
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP positions surfaced per acquirer; 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.

Ready to route smarter

Put intelligent payment routing in front of your acquirer panel.

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

Book a routing review Read the API docs

Frequently asked

Buyer questions about intelligent payment routing on topropay

Definitions, per-merchant tuning, cross-border currency handling, ACH-routing terminology, network-token mechanics and the practicalities of migrating on.

  1. 01

    What is intelligent payment routing on topropay?

    Intelligent payment routing on topropay is the per-transaction scoring engine that ranks every connected acquirer, PSP and rail for each authorisation and picks the best lane. Signals include BIN, scheme, currency, country pair, device / velocity risk, and live scheme-programme position per acquirer. Soft declines cascade to the next ranked lane inside the same authorisation.

  2. 02

    How is this different from static payment routing?

    Static payment routing pins each merchant / method to a fixed acquirer. Intelligent routing scores every connected lane on every authorisation and picks per-transaction. The result: cross-border authorisations reach locally-domiciled acquirers automatically, high-risk BINs shift to acquirers that clear them best, and scheme-programme-at-risk lanes get down-weighted without human intervention.

  3. 03

    What does topropay's payment routing solution actually cost the merchant?

    The payment routing solution is bundled into the platform pricing — merchants don't pay a separate per-transaction routing fee. The commercial upside comes from the higher approval rate and lower effective landed cost that per-transaction routing produces at scale, not from a routing add-on.

  4. 04

    Can a payment routing platform be tuned per merchant?

    Yes. The payment routing platform exposes per-merchant policies — different weights per BIN, per-scheme, per-currency and per-country, per-vertical exclusions, and simulator-tested overrides. Resellers (PSPs) inherit the panel and configure independent policies per downstream merchant.

  5. 05

    What makes routing dynamic in dynamic payment routing?

    Dynamic payment routing means the scoring inputs update in real time from production traffic. Per-lane approval rate, dispute rate and response time roll forward; weights react automatically to changes without the merchant editing a policy. Overrides remain available for merchants who prefer deterministic behaviour.

  6. 06

    Does topropay support global intelligent payment routing across regions?

    Yes. Global intelligent payment routing on topropay covers EU, UK, APAC and LATAM as a baseline. Cross-border authorisations pick a locally-domiciled acquirer for the issuer's country where available; where it isn't, cross-border lanes take the auth. Regional method routing (PIX for Brazilian buyers, iDEAL for Dutch, PayID for Australian) sits on the same engine.

  7. 07

    Is 'ach payment routing number' the same as topropay's ACH routing?

    That phrasing normally refers to the 9-digit ACH routing number identifying a US bank on the ACH network — a piece of the buyer's bank credentials, not a topropay concept. topropay's ACH routing selects between connected ACH processors per authorisation based on the buyer's BIN (bank), history and merchant preference. The 9-digit routing number stays in the mandate details; the topropay engine picks the ACH processor that clears that bank best.

  8. 08

    How does international intelligent payment routing handle currency?

    International intelligent payment routing scores lanes per authorisation currency. Local acquirers in the buyer's country typically clear domestic-currency authorisations at a lower interchange band; the engine picks the local lane when available, cross-border when not. Multi-currency settlement per merchant is supported.

  9. 09

    What does payment routing infrastructure include on the platform?

    Payment routing infrastructure on topropay includes the scoring engine, the per-merchant policy editor, the connected-provider panel, the vault + tokenisation layer, the signed-webhook event stream and the unified reconciliation feed. All infrastructure is platform-owned — the merchant doesn't run their own routing service.

  10. 10

    How do intelligent payment solutions defend against fraud?

    Intelligent payment solutions on topropay layer fraud signals into the routing engine — velocity rules, list management, device fingerprinting and partner-agnostic fraud-engine connectors. Suspicious authorisations can be down-weighted, step-up-authenticated or held for review; controls are configurable per-vertical and per-merchant.

  11. 11

    Does the routing engine work with network tokens?

    Yes. Network tokens (Visa VTS, Mastercard MDES) sit inside the vault; the routing engine reads scheme + BIN metadata off the token and scores lanes the same way it would for a live PAN authorisation. Recurring renewals get the same per-transaction routing as one-off authorisations.

  12. 12

    What happens when a soft decline can't be recovered?

    When a soft decline can't be recovered inside the same authorisation (all ranked lanes exhausted or the merchant's cascade budget hit), the engine returns the final decline to the merchant with per-lane response codes retained for reporting. Retry-later strategies (queued retries) sit on top of the in-auth cascade as a separate feature.

  13. 13

    Can the merchant see the routing decisions?

    Yes. Every authorisation carries a routing-log entry with the ranked lanes, the chosen lane, the cascade lanes attempted and the final outcome — visible per-transaction in the dashboard and exportable as CSV or via API. The log is audit-grade for scheme dispute or programme evidence.

  14. 14

    Is the routing engine deterministic or non-deterministic?

    Deterministic. Two identical authorisations at the same instant produce the same routing decision. Non-determinism enters only through the rolling per-lane metrics, which are versioned — a merchant can pin their routing to a specific metrics snapshot for a test environment.

  15. 15

    How long to migrate an existing merchant onto topropay's routing?

    Migration to topropay's routing typically runs 2–6 weeks depending on the merchant's KYB, sandbox testing needs and cutover strategy. Most merchants run topropay in parallel with their existing provider during migration so that approval, cost and dispute outcomes can be measured per-lane before full cutover.

Related

Related on the topropay platform