A card authorization normally reaches the issuer for a real-time decision. If the issuer or its processor is unavailable, stand-in processing may let the card network respond under predefined controls so every eligible purchase does not fail solely because one connection is down.
Stand-in begins when the normal issuer path cannot answer
A merchant sends an authorization through its acquirer and the card network toward the issuer. A timeout, planned maintenance, processor incident or network problem can prevent the issuer from returning an answer within the required period, even though the card and account may otherwise be usable.
For eligible transactions, the network can stand in for the unavailable issuer and return an approval or decline. The capability supports continuity at the authorization step; it does not move final settlement forward, resolve a dispute or guarantee that every transaction attempted during an outage will be accepted.
The issuer sets boundaries before an outage
Issuers configure participation, limits and decision parameters that reflect product, channel, geography, transaction type and risk appetite. Some transactions may be excluded or subject to conservative amounts because the stand-in service does not have every current account fact or every control available within the issuer's own systems.
Networks may also use transaction data and, for supported services, analytical models to approximate an issuer's decision. That can make the response more tailored than a single static rule, but the issuer still needs to understand the service, establish approved boundaries and govern any model or third-party dependency it relies on.
A stand-in decision uses a deliberately limited view
The service evaluates the data available in the authorization message along with applicable issuer parameters, network controls and supported account or transaction history. It returns a response quickly because card acceptance cannot wait for a full manual investigation.
The information may be less current or complete than the issuer's live view of balance, credit availability, recent activity, account restrictions and customer contact. For that reason, continuity and risk must be balanced: overly broad approval can create loss, while overly broad decline can unnecessarily disrupt legitimate purchases.
Recovery requires advice, posting and reconciliation
Stand-in activity is communicated back to the issuer through the applicable network messages and reports so account records, available funds or credit and fraud monitoring can be updated. The issuer and processor reconcile transactions approved or declined during the interruption and investigate missing, late or inconsistent records.
Normal routing should resume through controlled recovery rather than an untested switch. Teams confirm system health, message completeness and duplicate handling, then examine whether outage duration, transaction patterns or accumulated exposure require customer communication, additional monitoring or escalation.
Resilience depends on controls around the service
Banks test stand-in configurations, contact paths, reporting and recovery procedures before a disruption. They monitor approval rates, losses, fraud, false declines, parameter changes and occasions when stand-in was unavailable or produced results that differed materially from the issuer's normal decisions.
Stand-in processing is one layer within card resilience, alongside redundant connections, incident management, fraud controls, liquidity and settlement operations and customer support. Clear ownership is important because an external network may make the temporary decision while the issuer remains responsible for managing its card program and customer relationship.
Read the primary material
Banking Explained prioritizes regulators, official publications and first-party announcements.