Issuer
The issuer—or issuing bank—is the financial institution that provides payment cards, revolving credit lines, and demand deposit accounts to cardholders. As the institution with a direct financial relationship with the consumer, the issuer holds the ultimate authority to approve or decline any transaction presented against its card credentials.
Core responsibilities
Within the transaction lifecycle, the issuing bank executes several critical functions:
- Real-time authorization decisioning: When an authorization request arrives across the card network, the issuer evaluates account status, credit limits, available balances, historical spending velocities, and fraud risk scores before returning an approval or decline response.
- Reserving funds: When an issuer approves a transaction, it creates an authorization hold against the cardholder's available credit or account balance. This hold guarantees that funds will be available when the merchant captures the charge, although no actual money moves at this stage.
- Funding interbank settlement: Following end-of-day clearing, the issuer transfers settled funds across the card network to the acquiring bank, as described in clearing and settlement.
- Managing dispute claims: When a consumer challenges a statement charge—citing unauthorized fraud, damaged merchandise, or unfulfilled services—the cardholder contacts their issuing bank. The issuer evaluates the claim, credits the cardholder, and initiates a formal chargeback against the merchant's acquirer.
Economics of the issuing bank
The economics of consumer card issuance center on interchange. Interchange is the fee paid by the acquiring side to the issuing bank on every completed transaction.
Because the issuing bank assumes the credit risk of extending revolving credit lines, maintains 24/7 fraud monitoring platforms, and provides cardholders with interest-free billing periods and reward incentives, card network schedules allocate the vast majority of merchant discount fees directly to the issuer as interchange revenue.
Decline codes: interpreting issuer responses
Decline codes generated during authorization represent direct feedback from the issuer's decision engine. Scheme regulations mandate that issuers keep public decline descriptions deliberately generalized to prevent bad actors from using checkout forms as automated card-testing tools.
| Response family | Operational cause | Recommended retry strategy |
|---|---|---|
| Insufficient funds | Available credit limit or deposit balance is inadequate | Retry after a scheduled delay (e.g. 24–48 hours) using exponential backoff |
| Do not honor | Generic issuer rejection; risk scoring algorithm triggered | Prompt user for alternative payment method; automated retries rarely succeed |
| Invalid card / expired credentials | Transmitted PAN, expiration date, or CVV does not match | Request updated card details from the cardholder before reattempting |
| Suspected fraud | High-risk velocity or behavioral anomaly detected | Cease automated attempts; prompt for secondary verification or alternative tender |
Repeatedly attempting transactions against closed accounts or stolen cards can trigger network abuse fines from Visa and Mastercard. Intelligent retry policies must be implemented at the orchestration tier in the authorization flow rather than within frontend checkout forms.
Terms introduced
- Interchange: the fee the acquirer pays the issuer on each transaction. It is the main reason issuing is profitable.