Issuing bank
DEFINITION
The issuing bank is the financial institution that issued a subscriber's card and makes the final decision to approve or decline any charge on it, including recurring subscription payments.
TABLE OF CONTENTS
RELATED TERMS
The issuing bank is the financial institution that issued a subscriber's card and makes the final decision to approve or decline any charge on it, including recurring subscription payments.
When a subscription payment is submitted, it passes through several parties before it succeeds or fails. The payment gateway routes the request to a processor, the processor routes it to the card network (Visa, Mastercard, and similar), and the card network carries it to the issuing bank, which approves or declines it based on the cardholder's account status and the bank's own risk rules. Recurly and the payment gateway can surface the response that comes back, but neither one controls the approval decision itself. That decision sits with the issuing bank.
Types of declines
Declines generally fall into a few categories:
Hard declines come from an invalid card number, an expired card, an incorrect CVV, or a card reported lost or stolen. These typically require the subscriber to update their payment method, since automatic retries rarely succeed.
Soft declines come from insufficient funds, a temporary bank restriction, issuer-side fraud suspicion, or a required 3DS/SCA authentication step. They may succeed on a later retry, especially after the subscriber takes some action.
Validation errors are issues caught before the payment ever reaches the gateway or issuing bank, such as a missing billing field or an unsupported card type. These are not issuer declines at all.
Why the issuing bank matters
For a recurring billing business, the issuing bank is usually where the real friction lives, not the gateway or the platform processing the charge. Issuers can apply stricter rules to recurring, card-not-present transactions than they do to a one-time, in-person purchase, and those rules can change over time even for a card and merchant relationship that previously worked without issue. A renewal that succeeded last cycle can be declined this cycle purely because of a shift in the issuer's own risk posture, with no change on the merchant's side.
This is also why low-value charges can decline in ways that seem to make no sense. A decline coded as "insufficient funds" does not always mean the account balance is at zero. It can reflect a daily spending limit, an internal fraud check, or simply a stricter standard the issuer applies to recurring charges compared to a physical point-of-sale purchase.
How issuing bank behavior shows up in day-to-day operations
Confirm whether a failed transaction is a gateway or issuer decline (a real authorization attempt was made) or a Recurly validation error (no authorization attempt was made at all), since the fix is different for each.
Distinguish hard declines from soft declines, since hard declines usually need a new payment method while soft declines can sometimes succeed on retry.
When issuer behavior seems to have changed with no configuration change on the merchant side, treat that as a likely issuer-side risk-rule shift rather than assuming a platform or gateway bug.
Route soft declines into an automated retry and dunning process, since issuer-side risk decisions can vary attempt to attempt.
When a subscriber's card details change (a new expiration date, a reissued number), use Account Updater to recieve the most recent update to the issuing bank's current record before the next renewal attempt, since stale card data is one of the most common preventable causes of an issuer decline.
Benefits and examples
Separating issuer declines from gateway and validation errors keeps a support or payments team from chasing a platform bug that is actually a bank-side risk decision.
Recognizing that issuers treat card-not-present recurring charges more strictly than point-of-sale purchases explains declines on accounts that otherwise look healthy, including small-dollar renewal charges.
Knowing that some payment methods and digital wallets sit between the subscriber and the issuing bank (a wallet may return only an approved or declined result, without the underlying issuer reason) sets the right expectation for what a merchant or support team can diagnose directly versus what requires the subscriber to contact their bank.
How Recurly handles issuer declines
Recurly applies automated retries through Smart Retries, timed to improve the odds that a soft, issuer-side decline succeeds on a later attempt rather than requiring immediate subscriber action.
Recurly Account Updater services also refresh expired or replaced card details before they cause a failed renewal, addressing one of the more common preventable causes of an issuing bank decline.
When a decline is genuinely issuer-side, such as a card flagged for suspected fraud or blocked under the bank's own recurring-payment rules, Recurly does not have visibility into the issuer's specific internal reasoning and cannot override the issuer's decision. In those cases, dunning emails prompt the subscriber to update their billing information or contact their bank directly, which is typically the fastest path to resolution.
Frequently asked questions
What is the difference between an issuing bank and a payment gateway? The payment gateway routes and processes the transaction request. The issuing bank is the subscriber's own bank, and it makes the actual decision to approve or decline the charge based on the cardholder's account and its own risk rules.
Can a merchant or platform override an issuing bank's decline? No. Once a decline originates from the issuing bank, neither the merchant nor the billing platform can override that decision. The subscriber typically needs to update their payment method or contact their bank directly.
Why would a valid card get declined by the issuing bank? Common reasons include a daily spending limit, an internal fraud or risk check, stricter rules applied to recurring or card-not-present charges, or a temporary account restriction, even when the account is otherwise in good standing.
Does updating a card automatically fix issuer declines? Often, yes, since it refreshes the payment method record the issuer evaluates. But it is not guaranteed, and the subscriber may need to contact their bank directly to approve the merchant's recurring charges if declines continue.
