Acquirer & issuer

Acquirer and issuer — the pair that decides approval.

The acquirer-issuer pair is the most important pair in card payments. topropay reads the issuer BIN on every authorisation and routes to the acquirer most likely to win that specific pair across the connected acquiring panel — and reports on every pair's outcomes for tuning afterwards.

Book a pair-routing review Read the API docs
MERCHANT M-9421 ACQUIRER merchant bank SCHEME Visa / MC ISSUER cardholder bank cardholder · BIN 4012• issuer BIN → acquirer choice (routed by topropay) approval, cost, dispute outcomes all rest on the pair
The 4-party model · routed per pair by topropay.
4-party
model — merchant, acquirer, scheme, issuer
Per pair
routing by issuer BIN × acquirer
<200ms
routing decision
1 ledger
across every acquirer · every issuer pair

Key benefits

Why orchestrated acquirer-issuer pair routing wins on net revenue

Four outcomes that show up consistently once routing scores the acquirer + issuer pair per authorisation instead of running every transaction through one default acquirer.

  1. 01

    Acquirer and issuer pair routing per transaction

    The acquirer and issuer pair matters more than any other single factor for approval rate. topropay's routing engine reads the issuer BIN on each authorisation, looks up the merchant's historical outcomes for that BIN range across the connected acquirer panel, and picks the route most likely to win that specific issuer-acquirer pair. Cross-region pairs benefit disproportionately.

  2. 02

    Issuer and acquirer transactions in one ledger

    Every authorisation tags the issuer BIN, the issuing-bank country, the scheme and the acquirer ID it landed on. Issuer and acquirer transactions roll up into one normalised reconciliation feed — finance can pivot by issuer country, by acquirer, by pair to find the routes that win and the ones that leak.

  3. 03

    Merchant acquirer issuer flow shrinks to one API

    The merchant acquirer issuer flow — merchant fires an authorisation, the acquirer sends it through the scheme to the issuer, the issuer approves and settlement flows back — is the universal card-payments shape. topropay collapses the merchant side into one REST surface; the acquirer-scheme-issuer side runs behind it transparently.

  4. 04

    Acquirer issuer processor handled across the panel

    Where the acquirer issuer processor pattern shows up — separate technology providers running message exchange on the acquirer's behalf — topropay's panel covers both shapes. The merchant doesn't manage processor relationships per acquirer; the platform handles the per-provider message format and surfaces one consistent event model.

How it works

From issuer BIN read to settlement in five stages

Five concrete stages between the merchant's authorise call and the funds landing in settlement. The issuer-BIN read happens first and shapes every downstream choice.

  1. 01

    Map the acquirer panel

    A discovery surfaces the connected acquirers most likely to fit your traffic — geography, scheme split, BIN bands, MCC, average ticket and chargeback profile.

  2. 02

    Sub-merchant onboarding once

    Underwriting and KYC happen through topropay's sub-merchant model. The merchant integrates once; the platform handles per-acquirer paperwork that would otherwise repeat per relationship.

  3. 03

    Authorise — issuer BIN reads first

    Every authorisation goes through the routing engine. The issuer BIN tells the engine which issuing bank holds the cardholder relationship; the engine picks the acquirer most likely to win that issuer + acquirer pair across the connected panel.

  4. 04

    Scheme messaging, issuer approval

    The chosen acquirer sends the authorisation through the relevant scheme (Visa, Mastercard, Amex, JCB) to the issuer. The issuer approves or declines against the cardholder's account; the response flows back the same path.

  5. 05

    Settlement and reconciliation

    Funds settle from the issuer to the acquirer on the scheme's clearing cycle, then from the acquirer (or aggregator) to the merchant on the agreed cycle. topropay normalises every settlement across acquirers into one ledger keyed off vault tokens.

Main use cases

Where acquirer-issuer pair routing earns its keep

Six merchant shapes that share the same routing model but stress the issuer-acquirer pair differently — cross-border DTC, SaaS, marketplaces, travel, PSPs and licensed high-risk.

  • Cross-border

    Cross-border DTC and online retail

    EU-issued cards clear better through EU acquirers; US-issued through US acquirers. topropay reads the issuer BIN and routes the pair automatically, keeping interchange and approval profile intra-region wherever possible.

  • SaaS

    Subscriptions and SaaS

    Renewal-recovery rate is acquirer-issuer-pair-sensitive. A card that declined on one acquirer-issuer pair may clear on a different acquirer with the same issuer — cascading across the connected panel converts a per-provider retry script into a routing policy.

  • Plat

    Marketplaces and platforms

    Per-seller buyer mix often spans issuer countries that no single acquirer covers cleanly. Routing by issuer BIN sends each authorisation to the acquirer most likely to win that pair while keeping per-seller reporting straight.

  • Travel

    Travel and ticketing

    Disputes on high-ticket bookings can pivot on which acquirer handled the original authorisation against a given issuer. Keeping the option to route to the acquirer best-equipped for that BIN and dispute window is a margin-protection move.

  • PSP

    PSPs and ISVs reselling capacity

    Resellers ride the platform's acquirer-issuer-pair-aware routing downstream. Their merchants inherit the per-pair scoring; the PSP keeps the relationship and pricing.

  • Risk

    Licensed high-risk verticals

    Verticals where direct acquirer underwriting is selective benefit most from a curated multi-acquirer panel where the routing engine can pick the right issuer-acquirer pair per transaction. Licensed operators only.

Platform features

Capabilities behind issuer and acquirer processing on topropay

What the platform actually ships for issuer-aware routing — the API contract, the scoring engine, the dispute queue and the operator portal.

  • Issuer-BIN routing

    Per-BIN, per-scheme, per-currency routing weights — scored against your own outcomes per issuer + acquirer pair.

  • Unified acquirer API

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

  • Cascade & retry across pairs

    Soft declines cascade to the next ranked acquirer for that issuer BIN inside the same authorisation; nothing leaks back to the buyer.

  • Pair analytics

    Per-pair approval, cost and dispute analytics in the dashboard — surface which issuer-acquirer combinations win, which leak, which to re-route.

  • Issuer-country awareness

    The routing engine reads the issuing-bank country from the BIN and weighs cross-border vs intra-region interchange in the score.

  • Acquirer-ID reporting

    Every authorisation tags the acquirer ID and the issuer-BIN bucket; analytics roll up per bank, per scheme, per region, per pair.

  • PCI DSS Level 1 vault

    Card data captures into the vault before it touches any acquirer; vault tokens drive refunds, retries and recurring.

  • 3DS2 / SCA orchestration

    Selective challenges per transaction across the acquirer panel; PSD2-compliant in Europe without breaking conversion.

  • Dispute & chargeback queue

    Unified queue across acquirers and issuers; 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 acquirer relationship with dashboard alerts.

  • Settlement currency policy

    Settlement currency per acquirer relationship 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 issuer + acquirer pair.

Trust & compliance

Compliance posture across acquirer-issuer transactions

Every acquirer relationship runs inside the platform's audited environment. Sub-merchants inherit the posture rather than carrying separate certifications per relationship.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture across every acquirer relationship.
Scheme programme tracking
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP thresholds tracked per acquirer with dashboard alerts.
SCA & PSD2
Selective 3DS2 on the authorisation path keeps approval high in Europe without skipping the compliance bar; issuer-side step-ups respected.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical and per acquirer's appetite.
Data residency
Regional data-residency options for merchants under regulators that require it; issuer-country awareness preserved in audit trails.
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 route pairs

Route every authorisation to the right acquirer-issuer pair.

A 45-minute pair-routing review walks through the acquirer panel for your top issuer BINs, the routing policies that suit your traffic, and a sandbox to test against before any commercial commitment.

Book a pair-routing review Read the API docs

Frequently asked

Buyer questions about acquirer-issuer pair routing on topropay

Questions buyers ask before committing — definitions, ordering, cross-region interchange, scheme programmes and the four-party model in practice.

  1. 01

    What does acquirer and issuer mean in payments?

    Acquirer and issuer in payments refers to the two licensed-bank roles in the four-party card model. The issuer is the bank that issued the card to the cardholder; the acquirer is the bank that processes card transactions on behalf of the merchant. Every card authorisation travels between them via the scheme rails (Visa, Mastercard, Amex, etc.) — the merchant's gateway sends it to the acquirer, the acquirer sends it through the scheme to the issuer, the issuer approves, the response comes back the same path.

  2. 02

    Is the order significant when we write acquirer issuer or issuer acquirer?

    Convention varies. Acquirer issuer is often written when describing the merchant-side perspective (the merchant deals with its acquirer first); issuer acquirer is often written when describing the cardholder-side perspective (the cardholder deals with its issuer first). Either ordering is acceptable in industry usage; the underlying four-party flow is identical.

  3. 03

    How does the merchant acquirer issuer flow work end-to-end?

    Merchant acquirer issuer end-to-end: (1) the merchant sends the authorisation to its acquirer via the gateway, (2) the acquirer forwards through the scheme to the issuer, (3) the issuer approves or declines against the cardholder's account, (4) the response flows back to the merchant, (5) funds clear on the scheme's settlement cycle from issuer to acquirer to merchant. topropay sits in front of the acquirer step — the merchant talks to one API; the platform handles step 2 across many connected acquirers.

  4. 04

    What does the issuer acquirer merchant ordering describe?

    Issuer acquirer merchant is the cardholder's-view ordering: the cardholder's issuer at the start, the merchant's acquirer in the middle, the merchant at the end. Functionally it's the same flow as merchant-acquirer-issuer — just narrated from the other direction.

  5. 05

    Why does the acquirer and issuer pair matter so much for approval rate?

    The acquirer and issuer pair matters because card-issuing banks evaluate authorisations partly on the acquirer that sent them and the country pair that resulted. An EU issuer typically approves higher on EU-acquirer-domestic traffic than on US-acquirer-cross-border traffic for the same merchant. Routing the pair to its most-likely-to-clear combination is the single largest lever on approval after fraud signals.

  6. 06

    What does acquirer and issuer in payments add beyond just 'gateway' or 'processor'?

    Acquirer and issuer in payments is the licensed-institution layer beneath the gateway and the processor. The gateway carries the message; the processor runs the technology; the acquirer holds the scheme licence and the merchant contract; the issuer holds the scheme licence and the cardholder relationship. All four matter in different ways for approval, cost and dispute outcomes.

  7. 07

    How are merchant issuer acquirer pair relationships exposed in the platform?

    Merchant issuer acquirer pair relationships are exposed in the operator-portal analytics — per-pair approval rate, average landed cost, dispute rate and net-revenue contribution. The merchant can sort by pair to find the routes that consistently win and the ones that leak; the routing engine acts on the same data per transaction.

  8. 08

    What's the difference between acquirer and issuer bank in practice?

    An acquirer and issuer bank are two separately-licensed institutions playing distinct roles on every card authorisation. The acquirer bank serves the merchant: it processes the authorisation, handles the chargeback / dispute representment, and ultimately settles funds to the merchant. The issuer bank serves the cardholder: it approves the authorisation against the cardholder's available credit / balance, applies 3DS / SCA where required, and ultimately funds the settlement.

  9. 09

    How does topropay handle issuer and acquirer transactions across regions?

    Issuer and acquirer transactions across regions are routed by the engine on a per-transaction basis. The issuer-country (read from the BIN) and the available acquirer-country options (read from the connected panel) form a pair; the engine scores each candidate pair on historical outcomes and picks the highest-scoring route. Cross-region pairs see the largest uplifts because they're the noisiest on default routing.

  10. 10

    Is topropay an acquirer issuer processor itself?

    topropay is not directly an acquirer or an issuer — it is an orchestration layer that integrates with many acquirers (and the processors running on their behalf). The merchant integrates as a sub-merchant on the platform's acquirer relationships; the platform handles the message exchange and reconciliation. Issuer-side functions (card issuing) are not in scope.

  11. 11

    What does issuer and acquirer processing typically cover?

    Issuer and acquirer processing covers the technical message exchange between issuer-side and acquirer-side systems — the protocol formats, the settlement files, the dispute interfaces. Most merchants don't deal with this directly; their acquirer's processor handles it. topropay sits above that layer and abstracts the per-processor differences into one consistent API.

  12. 12

    Can a merchant see the issuer of each authorisation in the dashboard?

    Yes — the dashboard surfaces the issuer BIN, the issuing-bank country and (where the scheme metadata supports it) the issuer name on every authorisation. Per-issuer roll-ups are available so merchants can analyse which issuers win and which lose across the connected acquirers.

  13. 13

    How does the platform handle cross-region interchange between acquirer and issuer?

    Cross-region interchange — the higher fee acquirers pay when the cardholder's issuer is in a different region from the merchant — is one of the factors the routing engine weighs per transaction. Routing the authorisation to an acquirer in the issuer's region (where the merchant has a relationship there) keeps the transaction intra-region and the interchange domestic. That's a margin lever in addition to the approval-rate lever.

  14. 14

    What scheme programmes does topropay track per acquirer-issuer relationship?

    The platform tracks Visa VDMP (chargeback monitoring), VAMP (acquirer monitoring), VFMP (fraud monitoring) and Mastercard ECP and EFMP per acquirer relationship. Issuer-side equivalents (cardholder-side programmes) sit with the issuing bank and aren't merchant-facing; the platform just respects the issuer's step-up decisions on 3DS / SCA.

  15. 15

    What's the role of the scheme between acquirer and issuer?

    The scheme (Visa, Mastercard, Amex, JCB, Discover) is the rails between the acquirer and issuer. It defines the message format (ISO 8583 historically, ISO 20022 increasingly), the clearing cycle, the interchange rates, the dispute / chargeback calendar and the scheme-side programmes (VDMP, ECP). Both the acquirer and the issuer hold scheme licences; the merchant inherits scheme rules via its acquirer / aggregator relationship.

Related

Related on the topropay platform