What issuer processing actually covers

When a card is tapped, the visible event is a payment. Behind it sits a chain of processing that determines whether the transaction is allowed, how it is cleared, what the cardholder sees and how the institution reconciles its position.

Programme configuration

Before the first card exists, the programme is defined: the product type, BIN range, currencies, limits, permitted channels and merchant categories. These are not settings applied after launch; they are the rules against which every future transaction is judged. Getting them right at design stage is cheaper than correcting them in production.

Authorisation

An authorisation request arrives and must be answered in real time. The processing platform checks the card status, the available balance or credit line, velocity and programme rules, and returns a decision with a response code. Where the issuer host is unavailable, stand-in processing applies pre-agreed limits so that transactions continue within controlled risk.

Good authorisation processing keeps the reasoning. When a transaction is declined, the institution should be able to explain which rule produced that outcome — to the cardholder, to the scheme and, if asked, to a regulator.

Clearing and settlement

Authorisation is a promise. Clearing is the accounting. Transaction files are received, matched to authorisations, adjusted where necessary, and presented for settlement. This is where amounts are finally posted to the cardholder account and where fees, chargebacks and adjustments appear.

Servicing and disputes

Cards are lost, compromised and disputed. A complete issuing capability includes blocking and replacement, PIN and credential management, dispute workflows with provisional credit rules, and the operational tooling to resolve cases within scheme deadlines.

Tokenisation

Most cardholders now transact through a wallet. Provisioning network tokens, managing their lifecycle and handling token-based authorisations is part of the issuer's responsibility, not an optional extra.

What to ask a provider

• Can the platform explain every decline against a named rule?
• How does stand-in processing behave, and who sets the limits?
• Are clearing, disputes and tokenisation in scope, or separate systems?
• What does the institution need to see for scheme and regulatory reporting?

Issuing is not a single product. It is a set of obligations that must operate as one system — and the quality of that system shows up in the first month of live traffic.