Stakeholders in a Card Program

A single card transaction touches many parties, and a card program (the ongoing structure and multiparty relationship that issues and manages cards) involves even more. Understanding who's who, who's authorized to do what, and where liability sits, is essential context for understanding Axys's role and your own.

The cast

Card Network (Scheme)

Visa, Mastercard, and similar organizations operate the switching network (sometimes called a scheme) that routes transactions between acquirers and issuers, and they set the rules everyone else operates under:

• Interchange fee schedules (see Interchange & Platform Economics)
• Dispute rules and reason codes
• Brand standards (card design requirements, acceptable use)
• Technical standards for messaging and security (e.g. EMV chip specifications, 3-D Secure protocol versions)

Card networks do not hold cardholder accounts or issue cards themselves: they're the connectors between issuers and acquirers.

Network Member

One party from the issuing side must be a member of one or more of the card networks, in order to access the network infrastructure and rails. They might be a principal or affiliate member. A principal member must be a licensed financial institution. The network member that represents the issuer parties could be the issuer itself, issuer bank, or (less frequently) the issuer processor.

The network member is legally and financially liable for cards issued under its membership (identified by a Bank Identification Number (BIN)), whether or not they're issued by them directly or by any of the other issuer parties. Some network members sub-license their services to third parties on arms' length commercial terms, although this requires a different arrangement with the network.

Typical Requirements

A network member must hold a valid regulatory license, maintain capital adequate to satisfy both its prudential supervisor and the scheme's own financial soundness assessment, post collateral against risk exposure (waived only for investment-grade members), keep its settlement account funded to cover several days' net transaction flow, and meet minimum volume commitments under its scheme or processor agreement — with deficits either charged or carried forward against future surpluses. Most members will be required to present a suitable track-record, two or three years' audited accounts, and sound technical and regulatory compliance.

In the case of a multi-tenant network license, the financial burden is often pro-rated between the underlying programs that are organized under the network membership.

Issuer

"Issuer" is a deliberately loose, dual-lens term in the card industry, and Axys uses it the same way the industry does rather than narrowing it artificially. Depending on which party you ask, "the issuer" can mean two different things:

• The upstream sense — the regulated financial institution (a bank or EMI) that holds direct membership with the card network and the BIN. From the network's perspective, this licensed, capital-backed institution is the issuer.
• The downstream sense — the party with the actual cardholder relationship, whose name and brand the cardholder associates with the card. From the cardholder's perspective, whoever gave them the card is the issuer.

In many cases — most obviously a traditional bank — the same entity holds both senses at once: it's the network member and the party issuing cards directly to its own customers. In other structures, the two senses are held by different parties: one party has "issuer" status upstream as the network member, while a different party has "issuer" status downstream with the cardholder.

This is also why an entity that isn't itself a licensed deposit-taking institution — an issuer processor, for instance, even one that holds direct network membership — cannot issue cards on its own. It needs an Issuer Bank (or another correctly licensed financial institution) somewhere in the structure to hold cardholder funds and process transactions in a regulated capacity. Equally, a network member always needs an issuer processor to provide the infrastructure, connectors, and clearing — the two roles depend on each other, unless a single party performs both (American Express being the best-known example of a network that is also its own issuer and issuer processor).

A party holding "issuer" status (in either sense) typically:

• holds a direct or indirect membership/licensing relationship with the card network(s), and/or
• holds the cardholder relationship and issues cards under its own brand
• owns (or is allocated) one or more BIN ranges, which identify the network member, routing, and other details
• is the legally and financially liable party for cards issued under its BIN range(s)
• bears the credit risk of authorizing transactions before settlement completes

Becoming a card network member in the formal, upstream sense involves a substantial licensing, capital, compliance, and regulatory burden — which is why most companies that want to offer branded cards don't become network members themselves, but instead work with one.

Issuer Processor

The issuer processor is the technology platform that performs the operational work of issuing on the issuer's behalf: authorization decisions, ledger management, card lifecycle management (issuance, activation, status changes), and connectivity to the card networks. Axys aggregates and orchestrates this work.

An issuer processor operates closely with the issuer: the issuer processor is the engine, while the issuer is the authorized, liable entity. As above, the network member may be the issuer itself or, in some cases, the issuer processor. The issuer processor could be a member of the network(s) and provide services, including sub-BIN ranges, to multiple issuers. Alternatively, an issuer may be a member of the network(s) and in turn engage the services of an issuer processor.

Program Manager

The program manager designs and commercially operates a card program, coordinating the orchestration layer across the issuer parties.

A program manager might also choose the target customer segment, design the product (card features, fees, rewards if any), build the customer-facing experience, and hold the direct commercial relationship with cardholders — although these roles and responsibilities can sometimes be fulfilled by other parties, such as issuers or issuer banks.

Program managers co-ordinate with issuers, issuer processors, issuer banks (where applicable), the networks, and other parties. A program manager doesn't need to be a licensed financial institution itself, though some are, or are becoming one. Axys facilitates and automates the program management role alongside issuing and issuer processing — see Issuer parties and Axys below.

Cardholder

The end user. As established in Program Architecture, in the platform model, a Cardholder is always a natural person, even when a Program serves corporate clients.

Issuer parties and Axys

In the context of Axys:

1. The Tenant is considered the issuer;
2. Each Program is designed and operated by a program manager (which could be the Tenant itself, or a third party in conjunction with the Tenant);
3. Cards are issued under a Program to cardholders; and
4. Axys programmatically automates and orchestrates both the issuer and program manager roles, together with the issuer processor.

See Program Architecture.

Acquirer

On the other side of the card networks, the acquirer is the merchant's bank (or acquiring institution). It holds the merchant's account, contracts with merchants to accept card payments, and bears risk on the merchant side (e.g. if a merchant becomes insolvent after taking payment but before delivering goods, creating chargeback exposure).

Acquirer Processor

The technology platform on the acquiring side. This is analogous to an issuer processor, but for merchant acceptance. Many well-known payment gateway companies operate as acquirer processors (or partner with acquirers to provide this layer).

Merchant

The business accepting the card payment — the entity at the other end of every transaction from the cardholder's perspective.

How a transaction flows through these parties

flowchart LR
    CH["Cardholder"] -->|pays with card| M["Merchant"]
    M --> AP["Acquirer Processor"]
    AP --> ACQ["Acquirer"]
    ACQ <--> NET["Card Network<br/>(Visa / Mastercard)"]
    NET <--> IP["Issuer Processor"]
    IP --> ISS["Issuer"]

How a card program is structured

The transaction-flow diagram above shows the real-time path of a transaction but the business relationships that make a card program possible are layered differently: sponsorship flows from the Issuer down to the Program Manager, while the customer relationship flows the other way:

flowchart TB
    NW["Card Network<br/>(provides card scheme<br/>and transaction rails)"]
    NWM["Member's BIN<br/>(authorized principal<br/>or affiliate member)"]
    ISS["Issuer<br/>(authorized card issuer)"]
    IP["Issuer Processor<br/>(operates payment infrastructure)"]
    CH["Cardholder"]
    PM["Program Manager<br/>(designs and manages the<br/>structure and product)"]
    
    NW -->|"authorizes"| NWM
    NWM -.->|" "| ISS
    NWM -.->|" "| IP
    IP -->|"provides platform to"| ISS
    ISS -->|"issues cards to"| CH
    CH -->|"transactions flow through"| IP
    IP <-->|"settlements flow through"| NW

📘

The network member for a given card program may be the issuer, issuer processor, an issuer bank, a program manager, or a third party. A chartered bank is required within the issuer parties, even if the bank is not the network member.

Licensing and liability

A useful way to think about this: the member has the regulatory relationship with the card network, and bears ultimate responsibility and liability for the program, but the issuer, issuer processor, and program manager do the day-to-day work of running it. Any one of those parties may be the member, and sometimes it's a third party. The program manager co-ordinates the issuer parties and sometimes fulfils other functions directly. Axys aggregates, orchestrates, and automates program management, issuing, and issuer processing.

This structure is also why the O (Organization) field on a Tenant's mTLS certificate — see Mutual TLS, Certificates & CSRs — identifies the authorized legal entity: it's establishing, cryptographically, which entity in this chain the Tenant represents as the Program issuer.

How this maps to Axys

📘

Axys provides automated, aggregated issuer, issuer processor, and program management services. The Tenant is considered the issuer, while the operator of each underlying Program (which may be the Tenant itself) is the program manager.

What's next

• Interchange & Platform Economics
• Program Architecture
• The Card Transaction Lifecycle