Payment orchestration platform

Route every transaction to its highest-approval path.

topropay is the routing layer for high-volume merchants. Connect once. We route each payment across acquirers, PSPs, and wallets. We retry soft declines. Every sale gets its best shot.

  • PCI DSS Level 2
  • 99.99% uptime
  • 300+ connectors
Orchestration, measured

Hard numbers behind every routed payment

topropay sits between your checkout and every acquirer. It scores, routes, and cascades each payment in real time. Results land exactly where your finance and tech teams watch.

Live connectors
300 +
Acquirers, PSPs, and local APMs. All reachable through one connection.
Approval uplift
+ 12 %
Typical lift when smart routing picks the best path per payment.
Declines recovered
38 %
Soft declines retried and cleared. No extra code needed.
Routing decision
47 ms
Real-time scoring and acquirer selection on every transaction.
Unified Payments API

One API call, routed across every acquirer

Your team sends one request to one endpoint. topropay scores acquirers in real time. It cascades past soft declines on its own. You get one clean result back. Add markets without touching a single PSP.

POST/v1/payments
{  "amount": 4990,  "currency": "EUR",  "capture": true,  "routing": "auto",  "customer": { "country": "DE" }} # scores acquirers · cascades on decline acquirer·DE  declined  do_not_honor acquirer·NL  approved  captured
One request in, one settled result out. Cascading is automatic.
// one integration — every acquirer behind a single endpoint

On every request

  1. One request, one endpoint

    Send one standard payment to /v1/payments. No per-PSP SDKs. No custom builds to maintain.

  2. Real-time acquirer routing

    The engine scores every acquirer on cost, region, and approval odds. It picks the strongest path.

  3. Automatic decline cascade

    A soft decline retries on the next-best acquirer. It saves revenue that would else drain away.

  4. One reconciled result

    You get one clean, settled response. Data is matched and ready to report.

The orchestration layer

All the steps from auth to settlement

topropay sits above your acquirers as one API. It re-routes declines, checks routing rules per transaction, matches every settlement file, and handles PSD2 and PCI scope. Four systems you'd otherwise build and own.

Explore the platform

01 Intelligent cascading

Recover declines inside the same request

When an acquirer returns a soft decline, topropay tries the next acquirer in a ranked list. The retry keys on the ISO-8583 code, BIN, currency, and issuer pattern. It runs server-side. Your checkout never sees the failure.

Trigger
soft declines · 05 · 51 · 91
Strategy
ranked waterfall, configurable hop depth
Surfaced
one clean authorisation result

02 Multi-acquirer routing

Routing as policy, evaluated per transaction

Set routing as plain rules, not code. Each payment is scored on BIN, MCC, currency, card brand, and live approval rates. It goes to the route most likely to clear. Edit a rule in the dashboard. It applies on the next transaction. No redeploy.

Signals
BIN · MCC · currency · amount · 3DS
Optimises
live approval rate per acquirer
Deploy
instant, no engineering release

03 Centralised reconciliation

One ledger across every acquirer

topropay pulls settlement files, fees, chargebacks, and payouts from every acquirer. It maps them into one ledger. Captures are auto-matched to settlements. Fees are listed per transaction. Mismatches are flagged and pushed to your ERP or data store.

Ingests
settlement files · fees · chargebacks
Matches
capture ↔ settlement, automatic
Exports
ERP · warehouse · API

Compliance, as infrastructure

PSD2, 3DS2, and PCI. Handled below your stack.

SCA

PSD2, built for PSD3

SCA (Strong Customer Auth) runs on every transaction. Exemptions like TRA, low-value, and trusted beneficiary are checked in real time. This cuts needless friction.

3DS2

Auth routing

Frictionless and challenge flows run in-band. Each payment routes to the issuer ACS. It picks the best auth rate for that card range.

PCI DSS

Scope reduction by default

PANs are stored as tokens the moment they reach our PCI DSS Level 2 vault. Raw card data never hits your servers. Your audit scope shrinks.

Connector ecosystem

The providers you run on are already on the network.

We cover global card schemes and the local methods your customers expect. We maintain every connector. Keep your existing acquirer contracts or add new ones. Then route, retry, and cascade across all of them from one connection.

  • Acquirers & PSPs
  • Card schemes
  • Local payment methods
  • Digital wallets
  • Visa
  • Adyen
  • iDEAL
  • Mastercard
  • PayPal
  • Worldpay
  • Bancontact
  • Checkout.com
  • Apple Pay
  • SEPA Direct Debit
  • Stripe
  • American Express
  • Klarna
  • Nuvei
  • Sofort
  • Google Pay
  • Worldline
  • Giropay
  • Cartes Bancaires
  • Nexi
  • BLIK
  • Trustly
  • Przelewy24
  • Multibanco

Don't see a provider you need? New acquirers and local methods are added on request. Your setup stays the same.

Talk to our payments engineers

Turn declined payments into recovered revenue.

Book a discovery call. In one session, we map your acquirer setup. We model the approval-rate lift from smart routing. We scope a single-API build across your EU markets. No PSP changes. No stack rebuild.

  • PCI DSS scope reduction
  • PSD2 SCA & 3DS2
  • One API, every acquirer
POST · /v1/payments
$ curl https://api.topropay.com/v1/payments \  -H "Authorization: Bearer $TOPRO_KEY" \  -d amount=4999 -d currency=EUR \  -d routing=cascade # declined at acquirer A → retried → approved at acquirer B# one settlement · one reconciliation feed
Cascading recovers the decline on its own. No extra work.