Acquiring bank

Acquiring bank — many licensed banks behind one integration.

topropay connects to many licensed acquiring banks across the EU, UK, APAC and LATAM. You integrate once, as a sub-merchant. From there the routing engine picks the bank most likely to clear each payment, and folds every settlement into one ledger.

Book a bank-panel review Read the API docs
Three licences in the panel · one routed per authorisation.
Many
connected acquiring banks
All
major schemes (Visa, MC, Amex, JCB)
<200ms
routing decision
1 ledger
across every acquiring bank

Key benefits

Why orchestrated bank acquiring wins on every axis

One panel of acquiring banks beats one direct relationship. Here are four outcomes that show up again and again once orchestration sits in front of your traffic.

  1. 01

    Many acquiring bank licences behind one integration

    An acquiring bank is the licensed institution that clears card payments for a merchant under one or more scheme licences. topropay connects to many of them, across the EU, UK, APAC and LATAM. One unified API exposes the whole panel. You integrate once, and inherit the scheme licences as a sub-merchant.

  2. 02

    Per-transaction routing across the acquiring-bank panel

    Every card payment runs through the routing engine in under 200ms. The bank most likely to clear that BIN, scheme and country wins the traffic. If it soft-declines, the request cascades to the next ranked bank — inside the same authorisation.

  3. 03

    Acquiring bank and issuing bank pair tuned per transaction

    The pair of acquiring bank and issuing bank shapes approval rate more than any other single factor. The routing engine reads the issuer BIN. It checks how that BIN range has performed across your connected banks. Then it picks the route most likely to win. Cross-region pairs gain the most.

  4. 04

    Scheme-programme tracking per acquiring-bank relationship

    Each acquiring bank runs Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP monitoring on its merchants. topropay tracks your position against each limit, per relationship, and raises alerts in the dashboard. You get time to respond before the bank's own monitoring kicks in.

How it works

From acquiring-bank panel mapping to live processing in five stages

Five concrete stages take you from picking the right set of banks to live multi-bank traffic in production. Most merchants go live in weeks. The rest is iteration.

  1. 01

    Map the panel to your traffic

    A short discovery finds the banks that fit your traffic best. We look at geography, scheme split, BIN bands, MCC, average ticket and chargeback profile.

  2. 02

    Sub-merchant onboarding once

    Underwriting and KYC run through topropay's sub-merchant model. You integrate once. We handle the per-bank paperwork that would otherwise repeat for every relationship.

  3. 03

    Drop in the unified API

    You get a JSON-over-HTTPS REST surface plus SDKs. The same /v1/payments endpoint routes across the whole panel. There is no separate SDK to learn per bank.

  4. 04

    Route, cascade, capture

    Every payment runs through the routing engine. Soft declines cascade to the next ranked bank. Captures, refunds and dispute responses all run against vault tokens through the same API.

  5. 05

    Reconcile across acquiring banks

    Each bank settles on its own schedule. topropay normalises them into one ledger, keyed off vault tokens. Daily exports drop straight into your ERP.

Main use cases

Where a multi-acquiring-bank setup earns its keep

Six merchant shapes share the same orchestration layer but stress it in different ways: cross-border DTC, SaaS, marketplaces, PSPs, travel and licensed high-risk verticals.

  • Cross-border

    Cross-border DTC and online retail

    Merchants who sell worldwide need banks in each region to keep interchange and approval rates local. A US-issued card flows through a US-licensed bank. An EU-issued card flows through an EU-licensed one. topropay routes each pair automatically.

  • SaaS

    Subscriptions and SaaS

    Renewal recovery depends on the bank. A card that declined on one bank may clear on another, for reasons that have nothing to do with the card. Cascading across the panel turns a per-provider retry script into a simple routing policy.

  • Plat

    Marketplaces and platforms

    Some marketplaces have sellers in countries that no single bank covers well. Multi-bank routing helps them most. Each seller's payments route to a sensible regional bank, with one reconciliation on the platform side.

  • PSP

    PSPs and ISVs reselling capacity

    Resellers ride the platform's acquiring-bank portfolio downstream. Their merchants inherit the routing, BIN-level reporting and unified reconciliation; the PSP keeps the relationship and the pricing.

  • Travel

    Travel and ticketing

    Disputes on high-ticket bookings can turn on which bank handled the original payment. Keep the option to route to the bank best equipped for that BIN and dispute window. It protects your margin.

  • Risk

    Licensed high-risk verticals

    In verticals where banks underwrite selectively, a curated multi-bank panel helps. Routing is chargeback-aware and tuned to each MCC and chargeback band. Licensed operators only.

Platform features

Capabilities behind a card acquiring bank panel on the platform

Here is what the platform actually ships for a panel of acquiring banks: the API contract, the routing engine, the dispute queue and the operator portal.

  • Unified API across acquiring banks

    One REST contract across every connected acquiring bank; SDKs for web, mobile and server.

  • BIN-level routing

    Per-BIN, per-scheme, per-currency routing weights — scored against your own outcomes across the bank panel.

  • Cascade & retry

    Soft declines cascade to the next ranked acquiring bank inside the same authorisation; nothing leaks back to the buyer.

  • Acquirer-ID reporting

    Every authorisation tags the acquiring-bank ID and BIN used; analytics roll up per bank, per scheme, per region.

  • PCI DSS Level 1 vault

    Card data captures into the platform's vault before it touches any acquiring bank; vault tokens drive refunds, retries and recurring.

  • 3DS2 / SCA orchestration

    Selective challenges per transaction across the acquiring-bank panel — PSD2-compliant in Europe without breaking conversion.

  • Network tokens & updaters

    Network tokens by default; scheme updaters keep saved cards alive across issuing-bank re-issuance events.

  • Dispute & chargeback queue

    Unified queue across acquiring banks; evidence-pack templates per vertical; automated representment for select scheme types.

  • Scheme programme tracking

    Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP thresholds tracked per acquiring-bank relationship with dashboard alerts.

  • Settlement currency policy

    Settlement currency per acquiring bank is a configuration choice; merchants don't carry FX they didn't ask for.

  • Operator portal

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

  • Sandbox parity

    Per-environment sandbox that mirrors production — routing, cascade, 3DS, settlement and chargeback scenarios across the panel.

Trust & compliance

Compliance posture across the acquiring-bank panel

Every bank relationship sits inside the platform's audited environment. Sub-merchants inherit that posture. They do not carry separate certifications per bank.

PCI DSS Level 1
Annual on-site assessment and quarterly ASV scans; sub-merchants inherit the posture across the connected acquiring-bank panel.
Scheme programme tracking
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP thresholds tracked per acquiring bank with dashboard alerts.
SCA & PSD2
Selective 3DS2 on the authorisation path keeps approval high in Europe without skipping the compliance bar.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical and per acquiring-bank appetite.
Data residency
Regional data-residency options for merchants under regulators that require it; EU-resident traffic stays in-region by default.
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 regardless of integration shape.

Ready to map the panel

One API in front of every acquiring bank that fits your traffic.

A 45-minute review walks through the panel for your regions and BIN mix, the routing policies that suit your traffic, and a sandbox to test against. All before any commercial commitment.

Book a bank-panel review Read the API docs

Frequently asked

Buyer questions about the acquiring bank model on topropay

The questions buyers ask before they commit: what the terms mean, how issuing and acquiring differ, how scheme programmes and pricing work, and what it takes to run many banks behind one API.

  1. 01

    What is an acquiring bank in plain terms?

    An acquiring bank — sometimes called the acquirer or merchant bank — is the licensed financial institution that processes card transactions on behalf of merchants under one or more scheme licences. It receives the authorisation from the merchant's gateway, sends it through the scheme (Visa, Mastercard, etc.) to the issuing bank, and ultimately settles the funds to the merchant (or to an aggregator that settles to its sub-merchants).

  2. 02

    What does bank acquiring usually refer to?

    Bank acquiring is the service the acquiring bank provides: receiving card-authorisation requests, sending them through the scheme rails to the issuing bank, capturing the funds and settling to the merchant. topropay sits across many bank-acquiring relationships — one integration on the merchant's side, many acquiring-bank relationships on the platform side.

  3. 03

    What's the difference between an acquiring bank and an issuing bank?

    The acquiring bank holds the merchant relationship and the scheme acquirer licence; the issuing bank holds the cardholder relationship and the scheme issuer licence. On every card authorisation, the merchant's gateway sends the request to the acquiring bank, which sends it through the scheme to the issuing bank for approval. Funds settle back the same path on the scheme's clearing cycle.

  4. 04

    Does the order matter when we say acquiring bank and issuing bank?

    Convention is to write acquiring bank and issuing bank when describing the merchant-side perspective, and issuing bank and acquiring bank when describing the cardholder-side perspective. Either ordering is acceptable in industry usage; the underlying flow is the same. topropay's routing engine reads both sides per transaction.

  5. 05

    How does issuing bank and acquiring bank pairing affect approval rates?

    Issuing bank and acquiring bank pairing affects approval rates more than any other single factor outside fraud signals. A US-issued card running through a US-licensed acquiring bank typically clears better than the same card running through an EU acquiring bank; a UK debit card through a UK acquiring bank typically clears better than through a US one. topropay's routing engine reads the issuer BIN and picks the acquiring bank most likely to win that specific pair.

  6. 06

    What is the acquiring bank credit card flow specifically?

    The acquiring bank credit card flow is the standard four-party model: the cardholder presents a credit card at the merchant, the merchant's gateway sends the authorisation to the acquiring bank, the acquiring bank sends it through the scheme (Visa, Mastercard, Amex) to the issuing bank, and the issuing bank approves or declines against the cardholder's account. Funds clear back the same path on the scheme's settlement cycle.

  7. 07

    How is credit card acquiring bank selection handled in routing?

    Credit card acquiring bank selection on topropay is per-transaction. The routing engine scores the connected acquiring-bank panel by approval likelihood, landed cost and dispute-risk weight for the specific BIN, scheme, currency and country pair — and picks the highest-scoring route. The selection re-runs every authorisation; cascade rotates around it on soft decline.

  8. 08

    Is topropay itself a card acquiring bank?

    topropay is not a direct card acquiring bank in every market — it is an aggregator that integrates with several licensed acquiring banks and orchestrates traffic across them. Merchants integrate as sub-merchants on the platform's acquiring-bank relationships and inherit the underlying scheme licences rather than holding direct acquiring-bank contracts themselves.

  9. 09

    How does the acquiring-bank model differ from being a payment facilitator (PayFac)?

    An acquiring bank holds the direct scheme licence; a PayFac is a non-bank entity that onboards sub-merchants under a master merchant account with an acquiring bank. topropay sits in the latter shape — sub-merchants onboard once and inherit the underlying acquiring-bank licences via the platform's master relationships across the panel.

  10. 10

    Can a merchant keep an existing acquiring bank relationship and add topropay on top?

    Yes. Most merchants with an existing direct acquiring-bank relationship integrate topropay in parallel — the platform sits in front and routes additional traffic across the rest of the connected portfolio while the existing acquiring-bank relationship stays in place. The orchestration adds optionality without forcing a contractual exit.

  11. 11

    How does the acquiring bank handle cross-border interchange?

    Cross-border interchange is the higher fee acquiring banks pay when the cardholder country differs from the merchant country. Routing the authorisation to an acquiring bank in the cardholder's region (where the merchant has a relationship there) keeps the transaction intra-region and the interchange domestic. topropay's routing engine weighs that into the per-transaction score.

  12. 12

    What scheme programmes does topropay track per acquiring bank?

    The platform tracks Visa VDMP (chargeback monitoring), VAMP (acquirer monitoring), VFMP (fraud monitoring) and Mastercard ECP and EFMP per acquiring-bank relationship. Dashboard alerts surface when a merchant approaches the programme thresholds — the merchant responds before the acquiring bank's monitoring kicks in.

  13. 13

    What is a card acquiring bank in modern industry usage?

    Card acquiring bank is shorthand for an acquiring bank licensed on at least one card scheme — typically Visa and Mastercard at minimum. The narrower 'card acquiring bank' phrasing usually surfaces when distinguishing from non-card acquirers (bank-rail processors, BNPL providers, crypto gateways). topropay's connected card acquiring banks cover all major schemes across the supported regions.

  14. 14

    How is the acquiring-bank panel priced for merchants?

    Acquiring-bank traffic is priced per-authorisation on top of the underlying bank's interchange and scheme fees. Interchange and scheme fees pass through where the underlying acquiring bank supports it; topropay's platform fee is a separate line on the invoice. No platform retainer, no monthly minimum.

  15. 15

    What happens if an acquiring bank exits the merchant's vertical?

    If a connected acquiring bank exits the merchant's vertical or de-risks a particular MCC, the routing engine simply rotates traffic to the rest of the panel — the merchant doesn't need to do an emergency migration. Where the panel itself thins out for a specific vertical, topropay works with the merchant on alternative connectivity or a sub-merchant move to a partner-licensed route.

Related

Related on the topropay platform