Payment processors

Payment processors, orchestrated: one API in front of every one you use.

topropay sits in front of leading payment processors, card acquirers and alternative methods. One integration reaches them all. Smart routing picks the best processor for each sale, retries past declines, and pulls every settlement into one ledger — across Europe, the UK, APAC, LATAM and beyond.

60+
connected processors
300+
payment methods
40+
markets
<200ms
routing decision
topropay One settlement
Many processors connected. One ledger out.

The short version

Why best payment processors is a routing decision, not a vendor decision

For most teams, the phrase "payment processors" hides a messy reality. One processor wins on European card approvals. Another is the only real choice for bank transfers in Brazil. A third has the lowest fees on US debit. A fourth is the only one that supports a local method your buyers expect. Pick a single provider and you accept the average of those outcomes. topropay rejects that average.

The platform connects to a wide set of online payment processors. Which one runs a given sale is a routing decision. topropay makes that call in under 200 milliseconds, against your own traffic, on every transaction. The set of providers stays the same. What changes is which one you use, when, and why. The buyer sees one clean checkout. Finance sees one ledger. Engineering sees one API.

This page walks through how that works. It covers the use cases it fits, the compliance behind it, and the questions buyers ask before they commit — from website payment processors and ACH rails to nonprofit and Canadian flows.

Key benefits

What changes when payment processors for small business and enterprise share one orchestration layer

Route a few thousand sales a month or a few hundred per second. Once the orchestration layer is in place, the same four outcomes show up.

  1. 01

    Pick the right processor per transaction

    topropay scores each sale across connected payment processors in real time. It weighs BIN, scheme, currency, region and fraud signals. Then it sends the sale down the lane most likely to clear at the lowest cost. The buyer never sees the wiring.

  2. 02

    Cascade past soft declines automatically

    When a processor returns a soft decline, the sale cascades to the next ranked route in the same request. A network outage at one acquirer no longer costs you a day of revenue. The cascade absorbs it before checkout sees an error.

  3. 03

    Reconcile every processor into one ledger

    Settlements, fees, refunds and chargebacks from every processor land in one ledger, keyed off vault tokens. Finance closes the month from a single export. No more merging a CSV per provider.

  4. 04

    Negotiate from a position of evidence

    See approval, cost and dispute analytics side by side across your full payment processors list. Commercial reviews become a data exercise. Your own traffic replaces spec sheets, and rate cards get renegotiated against real outcomes.

How it works

From a single integration to a portfolio of payment processors, in five steps

The path from one API call to a live, multi-processor setup is short. Most merchants go live in days. The rest is tuning, not re-platforming.

  1. 01
    Connect

    One integration, every processor

    Drop in the unified payments API or the hosted checkout. Your acquirers and processors keep their contracts. topropay sits in front of them, not in their place.

  2. 02
    Configure

    Routing, methods and risk

    Pick the goal — approval, cost, currency or risk — from the dashboard. Turn on the methods and processors each market needs, with no new release.

  3. 03
    Authorise

    Real-time per-transaction scoring

    Every sale runs through the routing engine in under 200ms. The best route wins. Soft declines cascade to the next ranked provider in the same request.

  4. 04
    Settle

    Multi-processor settlement, normalised

    Each processor settles on its own schedule. topropay pulls the lot into one ledger, keyed by vault tokens. Finance can ignore the file-format differences.

  5. 05
    Improve

    Continuous tuning, no re-integration

    Adjust routing weights, switch a processor on or off, add a new acquirer. Every change ships from the dashboard. Engineering stays out of the loop after day one.

Main use cases

Where orchestrated payment processors earn their keep

Same orchestration layer, different shapes of merchant traffic. Open any row below for the specifics.

DTC Direct-to-consumer commerce at international scale

Storefronts that sell in more than one country soon outgrow a single processor. topropay routes cards and wallets to the best online payment processors in each market. It shows local methods at the checkout — iDEAL, BLIK, PIX, OXXO, Bacs. And it keeps one reconciliation feed, even as the processor mix changes by region.

Subs Subscriptions, SaaS and recurring billing

Recurring billing runs on vault tokens. Smart retries and account updaters make renewal recovery a setting, not a project. Network tokens and scheme updaters are shared across every connected processor. So a re-issued card no longer means a script per provider.

Plat Marketplaces, platforms and PSPs

Resellers and platforms pass capacity downstream. Their sellers ride topropay's processor portfolio without touching the contracts. Split payments, seller payouts and account funding all flow through one orchestration layer, with reporting per tenant.

ACH Bank-rail flows and ach payment processors

Card is one rail of many. topropay connects ach payment processors and their SEPA, Bacs and PIX peers into the same layer. So account-to-account, payouts and bank top-ups get the same routing, retries and reconciliation as card traffic.

NGO Nonprofit, donation and fundraising flows

topropay supports nonprofit payment processors flows through the same unified API — recurring donations, gift-aid data, donor portals and tax-receipt fields. Routing keeps donor approvals high. Reconciliation maps every gift back to the right campaign, with no manual file work.

Platform features

A platform feature set built for multi-processor reality

What the platform actually ships. It is laid out so engineering, finance and ops readers can each find the rows that matter.

  • Unified payments API

    One REST contract, plus SDKs. Together they act as a single online payments brain across every connected processor and method.

  • Hosted and embedded checkout

    A drop-in checkout for fast launch, hosted fields and a low-level SDK when you want full control of the surface.

  • Smart routing engine

    Scores each transaction on BIN, scheme, currency, region and fraud signals. It measures against your real outcomes, not vendor claims.

  • Cascade and retry

    Soft declines fail over to the next ranked processor in the same sale. Nothing leaks back to the buyer.

  • PCI DSS Level 1 vault

    Card data lives in our vault, not your systems. Refunds, retries and recurring run on tokens.

  • Network tokens & updaters

    Network-token-by-default plus scheme account updaters keep recurring revenue alive through card re-issuance events.

  • 3DS2 and SCA orchestration

    Selective challenges per transaction. PSD2-compliant in Europe, without pushing every shopper through a step-up.

  • Unified reconciliation

    Settlements, fees, refunds and chargebacks land in one ledger. Export CSV, Parquet and signed event feeds on a schedule.

  • Risk and fraud controls

    Velocity rules, list management and a partner-agnostic 3rd-party fraud connector model — bring your own provider or ride ours.

  • Operator portal

    One dashboard for authorisations, refunds, disputes and chargebacks across every connected processor.

  • Webhooks and event streams

    Signed, normalised webhooks and an event stream that fits cleanly into your SIEM, warehouse or in-house tooling.

  • Sandbox parity

    A sandbox per environment that behaves the same as production, including routing and cascade scenarios.

Industry relevance

Industries running on the platform

The model fits any sector where one more approved sale is worth more than the work of comparing processors.

  • Retail & DTC
  • Subscriptions & SaaS
  • Marketplaces & platforms
  • Travel & hospitality
  • Ticketing & events
  • Financial services
  • Gaming & entertainment
  • Nonprofits & fundraising
  • PSPs & ISVs
  • B2B invoicing
  • Education & e-learning
  • Digital goods

topropay works with licensed, regulated operators only. Gaming and entertainment merchants join where a current licence exists in a permitted market. Grey and black-market sectors are out of scope, whatever the integration.

Routing policies

Cheapest, leading, best — pick the routing policy, not the processor

Most of the industry sells fixed processor tiers. The orchestration model sells routing policies instead. Same connected providers, three targets to optimise for, picked from the dashboard rather than a sales call.

Cheapest route

Optimise for cost

Lean on interchange++ pass-through and route by lowest landed cost. It fits when you already win on conversion and just want to cut fees on the routes you use.

  • Interchange++ where supported by the underlying processor
  • Cost-weighted routing per BIN, scheme and currency
  • No retainer, no minimum monthly fee
Best total cost

Optimise for net revenue

Weigh approval, cost, dispute risk and refund rate into one score per route. Most mature merchants land here after a few weeks of orchestration traffic.

  • Composite scoring on real outcomes
  • Per-segment policies (cards vs ACH vs wallets)
  • Quarterly model retraining built in

Trust & compliance

Compliance posture, inherited from the platform

Every authorisation runs through one audited environment. Merchants join as sub-merchants. They inherit the platform's PCI DSS, SCA and operational posture instead of carrying the certifications themselves.

PCI DSS L1
Service-provider posture is validated on-site every year. Quarterly ASV scans run on the platform's cycle, and merchants inherit them.
SCA & 3DS2
Selective authentication on the authorisation path — PSD2-compliant in Europe without breaking conversion.
Data residency
Regional data-residency options for merchants who need them. Signed event logs are available from the dashboard for audit.
Resilient by design
Redundant acquiring zones and automatic failover keep authorisations available through outages and seasonal peaks.
Transparent fees
No hidden mark-ups. Interchange and scheme fees pass through, and topropay's fee sits on a separate line. The cheapest route is the one on your terms, not ours.

Ready to compare

See the connected processors list and route your traffic against your own outcomes.

A 30-minute review covers the processors that fit your regions and methods, the routing policies for your traffic, and a sandbox to test in — all before any commitment.

Frequently asked

Buyer questions about payment processors and orchestration

The questions buyers ask before they commit. They cover pricing, regions, sectors and what it takes to run several processors behind one API.

Are you a processor, or a layer in front of payment processors?

topropay is the orchestration layer that sits in front of payment processors, acquirers and alternative methods. We do not replace your processors. We connect them, route between them and consolidate their reporting. You keep your existing contracts, and the platform makes them feel like one.

Which are the best payment processors for small business operators?

The best payment processors for small business match the markets you sell in and the methods your buyers expect. They are rarely the ones with the loudest marketing. topropay lets small businesses route to several connected processors at once. You compare approval, cost and dispute outcomes side by side and let the data choose. The orchestration removes the lock-in that makes 'best' so hard to answer up front.

Are there genuinely cheapest payment processors, or is it a moving target?

The cheapest payment processors for one BIN range, scheme, currency and country are rarely the cheapest for another. So we treat 'cheapest' as a routing policy. We optimise each sale against your own cost surface, with interchange-plus pass-through where the processor supports it. That usually beats picking one provider on a sticker price.

Can topropay deliver the cheapest payment gateway experience?

In the orchestrated model, the cheapest payment gateway is the one that runs each sale down the route with the lowest cost for that transaction. topropay's routing engine does exactly that. There is no per-gateway sticker price — just a cost score across your real traffic.

Do you serve payment processors canada and cross-border North-American flows?

Yes. payment processors canada flows run through connected Canadian acquirers and Interac for account-to-account. Cross-border North-American card traffic routes through US and CA processors in parallel. Settlement currency is a policy choice, so CAD merchants don't carry FX they never asked for.

Are there truly free payment processors on the platform?

Free payment processors usually means 'no monthly fee', not 'no per-sale fee'. Interchange and scheme fees always apply. topropay charges no platform retainer, and several connected providers have no monthly minimum. So a low-volume merchant pays only per sale. For nonprofits, we also expose discounted-route policies that cut fees on donation flows further.

Do you publish a payment processors list?

The connected payment processors list lives inside the merchant dashboard, scoped to your region and method mix. The full matrix changes by the week. We don't publish a marketing-page list that goes stale. What you see in the dashboard is the live state, with status, latency and approval analytics for each.

What kind of website payment processors integration is involved?

Website payment processors integration is a single API call from your checkout, or a drop-in hosted checkout. The surface is the same whether you send the sale to one connected processor or let the routing engine choose. SDKs cover JavaScript, server-side languages and mobile. There is no separate plumbing per processor. That's the point.

How does the platform handle ach payment processors and bank rails?

ACH and bank-rail processors plug into the same orchestration layer as cards. Routing, retries, reconciliation and reporting work the same way. The only difference is the per-rail metadata in the API. SEPA, Bacs, PIX and Interac all flow through the same shape, and their webhooks normalise into one event model.

Are nonprofit payment processors handled differently?

Nonprofit payment processors flows get their own routing policies. Recurring donation retries are more patient. Gift-aid data is kept end to end, and reporting groups gifts by campaign. Several connected providers offer nonprofit pricing, and the layer routes eligible sales into them by default.

What separates leading payment processors connected here from the rest?

We connect leading payment processors that clear three bars: PCI DSS Level 1 posture, clear fee construction, and an API stable enough for real production traffic. Beyond that, the platform makes 'which one leads for you' a data question. Your own approval, cost and dispute analytics rank them — not the marketing.

What's the difference between online payment processors and a card processor?

Online payment processors is the wider category. It covers anything that authorises an online payment — cards, wallets, bank rails and BNPL. A card processor is one shape inside it. topropay treats them as one orchestration surface, so 'best online payment processors' becomes a routing question per sale, not a buying question per category.