Card scheme acceptance · multi-acquirer

Card acquiring across a panel of licensed acquirers.

topropay routes every card authorisation across a panel of licensed acquirers, with PCI L1 tokenisation, network tokens, selective 3DS2 and one reconciliation feed underneath. Sub-merchants inherit the acquiring posture — no per-scheme licence required.

Book an acquiring review Read the API docs
60+
connected card acquirers across regions
Visa · MC · Amex · Discover · JCB · RuPay
schemes accepted on one API
PCI L1
vault inherited by every sub-merchant
1 ledger
across every connected acquirer

Key benefits

Why credit card acquiring on a panel beats a single relationship

Four properties that show up the moment card volume stops sitting behind one acquirer and starts running across a connected panel of them.

  1. Skip the per-scheme acquiring licence

    Sub-merchants inherit topropay's acquiring relationships rather than holding their own scheme licences. The merchant signs one contract; the platform owns the acquiring panel underneath.

  2. Lift approval across the panel

    Per-BIN, per-country and per-currency scoring picks the highest-EV acquirer for each authorisation. Soft declines cascade to the next ranked acquirer inside the same authorisation — the buyer sees one decision.

  3. Geographic coverage without per-region projects

    EU, UK, US, APAC and LATAM acquirers all sit behind the same unified API. Expanding into a new market is a connection, not a re-integration.

  4. One reconciliation feed across schemes

    Visa, Mastercard, Amex, Discover, JCB and RuPay settlements from every connected acquirer normalise into one ledger — by scheme, by acquirer, by currency, by BIN.

How card acquiring services run underneath

From card capture to one reconciliation row in five steps

What happens between the moment the cardholder enters their details and the moment the merchant's finance sees a normalised ledger row.

  1. 01

    Capture in the PCI L1 vault

    Card data captures into the platform vault from hosted checkout, embedded hosted-fields or low-level SDK. Vault tokens (with network tokens underneath where available) replace the PAN immediately.

  2. 02

    Score the authorisation

    The routing engine scores the auth on BIN, scheme, currency, country pair and risk. Each connected card acquirer is a ranked lane for that transaction.

  3. 03

    Route to the top-ranked acquirer

    The auth runs through the top-ranked acquirer for that authorisation. If it returns a soft decline, the next ranked acquirer receives the retry inside the same call — buyer sees one decision.

  4. 04

    Authenticate (selective 3DS2)

    EMV 3DS2 fires where SCA / PSD2 exemption logic requires it; frictionless flows pass through; step-up where issuer or amount need it.

  5. 05

    Capture, settle, reconcile

    Settlements from every connected acquirer normalise into one ledger; refunds, chargebacks and adjustments tag back to the original vault token and original acquirer.

Main use cases

Where a multi-acquirer card acquiring business model earns its keep

Six merchant shapes that benefit from card acquiring across a panel rather than a single direct acquirer relationship.

  • DTC

    Cross-border DTC with mixed BIN traffic

    DTC merchants serving cardholders across markets benefit from per-BIN routing — local acquiring where it's available, cross-border fallback where it isn't.

  • Sub

    Sub-merchants without their own MID

    Merchants without their own card acquiring contract ride the platform's MIDs as sub-merchants. Onboarding goes through KYB; underwriting handles per-merchant risk.

  • PSP

    PSPs reselling card acquiring downstream

    PSPs and resellers inherit the connected card-acquirer panel and route their downstream merchants across it; the PSP keeps the merchant relationship and pricing.

  • Plat

    Marketplaces routing card per seller

    Different sellers can land on different connected acquirers based on risk profile, geography and volume; reconciliation rolls up by seller and by acquirer.

  • Travel

    Travel & ticketing with delayed capture

    Auth-only at booking, capture at fulfilment, refunds on cancellation — all against the same vault token, the platform handles the auth-capture lifecycle across acquirers.

  • SaaS

    Recurring SaaS billing on stored credentials

    Network tokens and account updaters keep recurring card-on-file billing alive across re-issuance; renewals don't fall off the back of expired cards.

Platform features

Capabilities behind the credit card acquiring services on topropay

Twelve capabilities grouped into schemes & rails, platform mechanics, and operations & finance. Each applies across every connected card acquirer.

Schemes & rails

  • Visa acceptance

    Credit, debit, prepaid, commercial and Visa Direct push-to-card via the connected Visa-acquirer panel.

  • Mastercard acceptance

    Credit, debit, prepaid, commercial and Mastercard Send push-to-card via connected Mastercard acquirers.

  • Amex, Discover, JCB, RuPay

    Direct-and-OptBlue style Amex acceptance; Discover network; JCB; RuPay (India) via licensed partners.

  • Regional schemes

    Cartes Bancaires, Bancontact, Interac and other domestic schemes via the regional acquirers that carry them.

Platform mechanics

  • PCI DSS Level 1 vault

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

  • Network tokens & updaters

    VTS and MDES network tokens by default; scheme updaters keep saved credentials alive across re-issuance.

  • Smart routing & cascade

    Per-transaction scoring across the connected acquirer panel; soft declines cascade inside the same auth.

  • Selective 3DS2 / SCA

    Selective challenges per PSD2 exemption logic and per-issuer behaviour; frictionless flows pass through.

Operations & finance

  • Unified dispute queue

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

  • Operator-side refund controls

    Refunds against the vault token, justification required, full audit trail per refund event.

  • Webhook events

    Signed lifecycle events for authorise, capture, settle, refund and dispute — replay-safe and idempotent.

  • One reconciliation feed

    Settlements, interchange, scheme fees, refunds and chargebacks across every connected acquirer in one normalised ledger.

Industry relevance

Card acquiring fit for licensed EU, UK, APAC and LATAM merchants

topropay's card-acquiring posture targets licensed merchants operating across Europe, the UK, APAC and LATAM — DTC and retail with cross-border card volume, SaaS billing on recurring cards, marketplaces routing per seller, travel and ticketing with delayed capture, and licensed gaming where current operating licences exist. India connectivity is delivered through licensed partner gateways.

Trust & compliance

Compliance posture across every connected card acquirer

One audited environment for the orchestration layer; per-acquirer scheme-programme positions surfaced in the dashboard; sub-merchants inherit the posture 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 card acquirer.
Scheme programmes
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP positions surfaced per connected acquirer; routing weights can rotate around at-risk lanes.
EMV 3DS2 / SCA
Selective 3DS2 on the authorisation path keeps approval high in Europe without skipping the SCA bar.
Network token services
Visa Token Service (VTS) and Mastercard Digital Enablement Service (MDES) — PAN replaced by network tokens in the vault.
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 consolidate card-acquiring

Bring card acquiring onto a multi-acquirer orchestration API.

A 30-minute review covers the connected card acquirers relevant to your geographies and BIN mix, routing weights tuned to your traffic, scheme-programme posture per acquirer, and a sandbox to test against before any commercial commitment.

Book a card-acquiring review Read the API docs

Frequently asked

Buyer questions about card acquiring on topropay

Definitions, panel-routing mechanics, sub-merchant model, lifecycle (auth-only / capture / refund / dispute), fees transparency and the practicalities of running card acquiring across a panel.

  1. 01

    What does card acquiring actually mean on topropay?

    Card acquiring on topropay means accepting Visa, Mastercard, Amex, Discover, JCB and RuPay payments through a panel of licensed card acquirers — without the merchant needing their own scheme licences. Sub-merchants inherit the platform's acquiring relationships and ride one unified API, one PCI L1 vault and one reconciliation feed.

  2. 02

    What's the difference between credit card acquiring and card acquiring more broadly?

    Credit card acquiring is the credit-rail slice of the broader card acquiring picture — Visa credit, Mastercard credit, Amex etc. Debit cards (Visa Debit, Maestro), prepaid cards and commercial cards sit alongside credit on the same acquirer relationships. On topropay both ride the same unified API; the acquirer routing engine handles per-product BIN behaviour underneath.

  3. 03

    How do card acquiring services on topropay compare to a direct acquirer relationship?

    A direct acquirer relationship gives the merchant one acquiring lane with the underwriting and contracting in their name. Card acquiring services on topropay give the merchant access to a panel of licensed acquirers behind one integration — useful when geographic, scheme-programme or approval-rate constraints make a single acquirer insufficient. Sub-merchants inherit the acquiring posture rather than negotiating it themselves.

  4. 04

    What is acquiring credit card volume across a multi-acquirer panel actually like?

    Acquiring credit card volume across a multi-acquirer panel means each authorisation gets scored on BIN, scheme, currency, country pair and risk, then routed to the top-ranked acquirer for that specific transaction. Soft declines cascade to the next acquirer inside the same authorisation; settlement files from every connected acquirer normalise into one reconciliation ledger.

  5. 05

    Which credit card acquiring services on the platform are scoped per region?

    Credit card acquiring services on the platform are scoped per region by the acquirer's licensing footprint. EU acquirers carry EU and UK BIN traffic, US acquirers handle US and Canadian BIN traffic, APAC acquirers carry the local APAC schemes, LATAM acquirers handle PIX-and-card combinations. The routing engine respects per-acquirer scope automatically.

  6. 06

    Is topropay a card acquiring business in its own right?

    topropay is not a card acquiring business in the sense of holding its own scheme acquiring licences. The platform is the orchestration layer above licensed card acquirers — providing the unified API, the PCI L1 vault, the routing engine and the reconciliation feed. The acquiring licences sit with the connected licensed acquirers in each geography.

  7. 07

    What does running a credit card acquiring business look like for a PSP using the platform?

    PSPs running a credit card acquiring business on top of the platform inherit the connected acquirer panel and resell it to downstream merchants. The PSP keeps the merchant relationship, contracting, branding and pricing; the platform handles the per-merchant routing policy, vault, dispute queue and reconciliation across the panel.

  8. 08

    How long does it take to start acquiring credit card volume?

    From contract signing to first credit card transaction typically runs 2–6 weeks. Variables: KYB depth, the merchant's PCI scope choice (hosted vs embedded vs SDK), and any scheme-programme registrations the connected acquirers need to file for the merchant's MCC. Sandbox covers the full card-acquiring flow from day one.

  9. 09

    What card acquiring schemes does the platform support?

    The platform supports Visa, Mastercard, Amex (direct and OptBlue style depending on acquirer), Discover, JCB and RuPay across the global panel. Regional domestic schemes — Cartes Bancaires, Bancontact, Interac, ELO, Hipercard — sit behind the regional acquirers that carry them. All ride the same unified API at the surface.

  10. 10

    What's the dispute / chargeback posture across the connected card acquirers?

    Dispute / chargeback posture is exposed through a unified dispute queue spanning every connected acquirer. Per-acquirer position vs Visa's VDMP / VAMP / VFMP programmes and Mastercard's ECP / EFMP is surfaced in the dashboard; routing weights can rotate around at-risk acquirers to keep aggregate dispute ratios inside scheme limits.

  11. 11

    Does the platform handle authorisation lifecycle (auth-only, capture, void, refund)?

    Yes — the full authorisation lifecycle is exposed through the unified API. Auth-only at booking with capture at fulfilment (travel / hospitality pattern), void before settlement, partial captures, partial refunds and chargeback events all flow through the same endpoints, regardless of which connected card acquirer cleared the original auth.

  12. 12

    How does the platform integrate with my existing acquiring contract if I already have one?

    If a merchant already holds a direct acquiring contract, that acquirer can be connected to topropay alongside the platform's existing panel — the merchant's MID continues to settle directly, while topropay layers the unified API, vault, routing and reconciliation across the wider connected set.

  13. 13

    What about card acquiring fees — is there transparency across the panel?

    Fee structure across the connected card acquirer panel — interchange (passed through), scheme fees, acquirer markup and platform markup — is exposed in the reconciliation feed per row, per acquirer, per scheme. The merchant sees the all-in cost per authorisation rather than a blended monthly statement.

  14. 14

    Can high-risk merchants run card acquiring on this platform?

    Licensed high-risk merchants (subscriptions, ticketing, licensed gaming, regulated financial services, nutraceuticals) can run card acquiring on the platform via the high-risk-tuned acquirer subset. Grey and black-market verticals are out of scope regardless of acquirer routing — the platform's underwriting filters them at onboarding.

  15. 15

    What happens if a connected card acquirer has an outage?

    If a connected card acquirer has an outage, its real-time error rate causes its score in the routing engine to drop automatically; authorisations route to the next ranked acquirer. Manual provider-disable in the dashboard takes the lane offline immediately for any merchant who wants to force the bypass.

Related

Related on the topropay platform