Orchestration · multi-acquirer

An epayment system that collapses every provider into one API.

topropay sits in front of a panel of connected acquirers, PSPs and alternative payment methods. One unified API, smart routing per transaction, PCI Level 1 vault and one reconciliation feed — across cards, wallets, bank rails, BNPL and crypto.

Book an orchestration review Read the API docs
API
1 contract across every connected provider
Methods
300+ reachable globally
Acquirers
60+ in the connected panel
Ledger
1 normalised feed across every receipt
API entry

POST /v1/authorizations

One contract · scheme-agnostic · multi-rail

Acquirer A · EUcard · wallet · BNPL
Acquirer B · UKcard · Open Banking
Acquirer C · LATAMcard · PIX
Partner D · APACcard · wallet
Partner E · cryptostablecoin · majors
One API · many connected providers underneath.

Key benefits

Why merchants pick topropay for epayment services

Four properties that show up the moment processing moves from a single PSP to a multi-acquirer orchestration platform.

Approval

Lift on the auth side

Per-transaction scoring picks the strongest acquirer lane per BIN, scheme, currency and country pair; soft declines cascade within the same authorisation.

Coverage

Methods that follow the buyer

Cards, wallets, regional bank rails, BNPL and crypto rails sit behind the same endpoint — the merchant's per-market mix is dashboard-configurable, not a re-integration.

Scope

PCI burden held at the platform

Card data captures into the platform vault before any provider sees it. Sub-merchants run at SAQ A or SAQ A-EP rather than full SAQ D.

Finance

One ledger across the panel

Settlements, interchange, scheme fees, refunds and chargebacks normalise into one daily ledger. Exports tag every row by acquirer, currency and routing policy.

How epayment processing works on topropay

Six lifecycle stages from card entry to reconciled ledger

What happens between the buyer's submit-button click and the row in the merchant's ledger — split across six stages with topropay's responsibility in each.

  1. 01

    Capture into the vault

    PAN captures through hosted checkout, embedded hosted-fields or low-level SDK. Vault tokens issued; PAN never lands in merchant systems.

  2. 02

    Score & rank

    BIN, scheme, currency, country pair, amount and risk run through the scoring engine; the connected acquirer panel is ranked per transaction.

  3. 03

    Authorise

    The top-ranked acquirer carries the authorisation; selective 3DS2 / SCA fires only where issuer or PSD2 logic require it.

  4. 04

    Cascade on soft decline

    Soft declines drop down to the next ranked acquirer inside the same authorisation; the buyer sees one final result, not a chain of retries.

  5. 05

    Capture & settle

    Capture is automatic or merchant-triggered; settlement files arrive per acquirer; multi-currency receipts settle into the merchant's preferred treasury.

  6. 06

    Reconcile in one ledger

    Settlement, refund and chargeback rows from every acquirer normalise into one daily feed; tagged by acquirer, currency, BIN, scheme and routing policy.

Main use cases

Where epayment services pay off the integration

Six recurring merchant shapes — DTC, SaaS, travel, marketplaces, B2B and PSPs — that benefit from running their epayment processing on a multi-acquirer panel rather than a single provider.

  • DTC

    Cross-border DTC checkout

    EUR card volume routed to an EU acquirer, GBP to a UK one, multi-currency settlement into the merchant's treasury; one checkout, three acquirer lanes underneath.

  • SaaS

    Recurring SaaS billing

    Network tokens via VTS / MDES, account updaters, retry policies and cancel flows — running on the same engine as one-off charges.

  • Travel

    Travel with delayed capture

    Auth-only at booking, capture at fulfilment, refund on cancellation — vault tokens hold the auth across the whole lifecycle.

  • Plat

    Marketplaces routing per seller

    Per-seller routing policies — risk-tier-based, geography-based, volume-based; reconciliation rolls up per seller and per acquirer.

  • B2B

    B2B invoicing on card + ACH

    Card on small tickets, ACH / SEPA SDD on recurring contracts, stablecoin for cross-border counterparties; one merchant record across the rails.

  • PSP

    PSPs reselling the platform

    Resellers inherit the connected acquirer panel and route their merchants across it. The PSP keeps the relationship; the platform handles the per-acquirer message exchange.

Platform features

Capabilities behind a multi-acquirer epayment system

Nine capabilities the platform ships once and reuses across every connected provider — the primitives that make a multi-acquirer setup feel like one product.

  • Unified API

    One REST contract across cards, wallets, BNPL, bank rails, crypto and recurring.

  • Smart routing

    Per-transaction scoring on BIN, scheme, currency, country, risk and policy.

  • Cascade & retry

    Soft declines cascade across the connected acquirer panel inside one authorisation.

  • PCI L1 vault

    PAN captures into the platform vault before any acquirer; sub-merchants stay at SAQ A or SAQ A-EP.

  • Network tokens

    Visa Token Service and Mastercard MDES tokens kept aligned across re-issuance.

  • 3DS2 / SCA orchestration

    Selective challenges; PSD2 exemption logic applied per transaction.

  • Multi-currency settlement

    Settle into the merchant's preferred currency per acquirer or per route.

  • Unified dispute queue

    Chargebacks across every connected acquirer in one queue, with evidence-pack templates per vertical.

  • Operator-side reporting

    Daily exports tagged by acquirer, scheme, currency, BIN, vertical and routing policy.

Industry relevance

epayment system fit for licensed EU, UK, APAC and LATAM merchants

topropay's posture targets licensed merchants operating across Europe, the UK, APAC and LATAM. The platform is built for both mainstream and licensed high-risk verticals — DTC and retail with international card volume, SaaS billing on recurring cards and bank rails, marketplaces routing per seller, travel and ticketing with delayed capture, regulated financial services and licensed gaming where current operating licences exist. Grey and black-market verticals, healthcare claim adjudication and adult content sit explicitly outside the platform's scope regardless of integration shape.

Trust & compliance

Compliance posture across the connected acquirer panel

One audited environment underpins every connected provider. Sub-merchants inherit the relevant posture per channel without carrying separate certifications themselves.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture across every connected provider.
SCA & PSD2
Selective 3DS2 on the authorisation path keeps approval high in Europe without skipping the compliance bar.
Scheme programmes
Per-acquirer position vs Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP programme thresholds surfaced in the dashboard.
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 at onboarding; AML monitoring tuned per merchant vertical, volume and channel 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 consolidate

Run your epayment system on a multi-acquirer orchestration API.

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

Book a review Read the API docs

Frequently asked

Buyer questions about running an epayment system on topropay

Definitions, integration timeline, recurring billing, regional coverage and the practicalities of running epayment processing on a connected acquirer panel.

  1. 01

    What is an epayment system?

    An epayment system is the combination of software, accounts and connections that let a business take money over the internet — typically through cards, wallets, bank rails, BNPL and crypto. On topropay the epayment system is delivered as an orchestration platform: one unified API in front of a panel of connected acquirers and payment methods, with smart routing, vault, tokenisation and reconciliation behind it.

  2. 02

    How do topropay's epayment services compare with a single-PSP setup?

    epayment services on topropay are delivered as a multi-acquirer orchestration layer rather than a single-PSP gateway. A single-PSP setup ties the merchant's approval rate, fee structure and risk-programme exposure to one provider; topropay's orchestration spreads the same volume across a connected panel of acquirers and PSPs, with the merchant's routing policy choosing per-transaction.

  3. 03

    What does epayment processing look like end-to-end?

    epayment processing on topropay starts at the buyer-facing surface (hosted page, hosted fields or SDK), runs through the platform's vault and routing engine, lands at the chosen acquirer for authorisation, then settles back into the merchant's treasury through the unified reconciliation feed. Every step is logged; the merchant integrates one API rather than one per provider.

  4. 04

    Who runs an epayment system on topropay?

    Both merchants and PSPs run epayment systems on topropay. Merchants use it as their primary processing platform across geographies; PSPs use it as the backbone they resell to their downstream merchants, inheriting the connected acquirer panel and the unified API.

  5. 05

    What payment methods does the platform's epayment system support?

    The platform's epayment system supports cards (Visa, Mastercard, Amex, Discover, JCB, RuPay), wallets (Apple Pay, Google Pay, Click to Pay, Alipay+, WeChat Pay), regional bank rails (SEPA, ACH, Bacs, Open Banking, PIX, iDEAL, Bancontact, Interac), BNPL (Klarna, Afterpay, Affirm, Clearpay), and crypto rails via licensed partner gateways.

  6. 06

    How long does it take to integrate?

    Most merchants integrate in 1–3 weeks. The variables are KYB depth, the PCI scope choice (hosted vs hosted-fields vs SDK), the number of acquirers being connected on day one, and any scheme-programme registrations the connected acquirers need to file. Sandbox covers the full flow from day one.

  7. 07

    Does the epayment system handle both online and in-person acceptance?

    The online side is fully platform-owned through the unified API. In-person (POS terminal, SoftPOS / Tap-to-Pay) is delivered via licensed partner acquirers; topropay's orchestration handles the cross-channel vault and reconciliation so the merchant runs one stack across channels.

  8. 08

    How is the platform priced?

    Pricing is per-transaction with acquirer pass-through plus a platform fee — interchange-plus where the acquirer makes interchange visible, blended where it doesn't. Volume tiers, vertical and risk profile shape the platform fee component; there's no per-API-call or per-vault-token fee.

  9. 09

    What about recurring billing inside the epayment system?

    Recurring is a first-class capability — card-on-file recurring with network tokens, SEPA Direct Debit, recurring ACH, and PIX-Recorrência where supported. Cycle scheduling, smart retries, scheme account updaters and cancel flows run server-side on the platform.

  10. 10

    Which markets does the platform's epayment processing cover?

    epayment processing covers Europe (EU + UK), APAC (with partner connectivity for India), LATAM (with strong PIX coverage in Brazil), and other global markets via the connected acquirer panel. New geographies are added as partner relationships expand.

  11. 11

    How does the platform protect against fraud on epayment services?

    epayment services on topropay layer risk controls on top of the PCI L1 vault: velocity rules, list management, selective 3DS2 / SCA, device-fingerprinting signals from partner fraud engines, KYB / KYC at onboarding and sanctions screening. The operator-side dashboard surfaces flagged transactions for review.

  12. 12

    Can the platform reach traffic in India?

    Yes, via licensed partner gateways. topropay does not hold a direct RBI Payment Aggregator licence; Indian acceptance runs through licensed partners with topropay's orchestration handling routing, vault and reconciliation on top.

  13. 13

    How are disputes handled across the connected acquirer panel?

    Disputes from every connected acquirer flow into one unified queue. Evidence-pack templates per vertical (DTC, SaaS, travel, gaming) speed up representment; vault-token-based receipts simplify evidence; per-acquirer position against scheme programme thresholds (VDMP / VAMP / ECP) is surfaced in the dashboard.

  14. 14

    Is the platform suitable for high-risk merchants?

    Yes, for licensed high-risk verticals operating where their licences are valid — regulated financial services, licensed gaming, regulated nutraceuticals and similar. Adult content, unlicensed gambling, healthcare claim adjudication and other grey- or black-market verticals are out of scope.

  15. 15

    What's the migration path from an existing epayment system?

    Most migrations parallel-run: topropay takes a percentage of traffic on day one alongside the existing system, then ramps up as the approval and reconciliation match-up is verified. The vault accepts pre-tokenised cards from a previous PSP through a one-off import where the PSP supports token portability.

Related

Related on the topropay platform