Error codes
Soft decline
Stripe
call_issuer
The card was declined for an unknown reason.
What does call_issuer mean?
The call_issuer decline code indicates that the issuing bank has refused the transaction and is directing the cardholder to contact them directly. The bank typically has an internal flag on the account that requires cardholder verification — but the specific reason is not disclosed to the merchant or communicated to the cardholder automatically.
Is it a soft or hard decline?
call_issuer is classified as a soft decline. The card may be valid once the issue is resolved, but recovery typically requires the cardholder to speak with their bank.
Common root causes
Temporary account verification required by the issuer
Suspicious activity flag requiring cardholder confirmation
Internal policy checks on specific transaction types
Address or identity mismatch on file
Pending card reissue or account update
Recommended recovery steps
Retry once after 24–48 hours — some issuer flags clear automatically.
If retries fail, route the customer to update their payment method or provide clear dunning messaging.
Use network tokens to reduce false positive issuer holds.
Avoid repeated retries — they continue to fail and can flag the merchant as aggressive.
How FlyCode handles call_issuer
FlyCode's AI retry engine distinguishes between transient issuer holds (recoverable with time) and persistent account flags (requiring customer action). Using network-level authorization data, FlyCode times retries to maximize recovery on temporary holds, and routes customers to payment update flows only when automated recovery is unlikely to succeed — minimizing friction and maximizing retention.
What does call_issuer mean?
The call_issuer decline code indicates that the issuing bank has refused the transaction and is directing the cardholder to contact them directly. The bank typically has an internal flag on the account that requires cardholder verification — but the specific reason is not disclosed to the merchant or communicated to the cardholder automatically.
Is it a soft or hard decline?
call_issuer is classified as a soft decline. The card may be valid once the issue is resolved, but recovery typically requires the cardholder to speak with their bank.
Common root causes
Temporary account verification required by the issuer
Suspicious activity flag requiring cardholder confirmation
Internal policy checks on specific transaction types
Address or identity mismatch on file
Pending card reissue or account update
Recommended recovery steps
Retry once after 24–48 hours — some issuer flags clear automatically.
If retries fail, route the customer to update their payment method or provide clear dunning messaging.
Use network tokens to reduce false positive issuer holds.
Avoid repeated retries — they continue to fail and can flag the merchant as aggressive.
How FlyCode handles call_issuer
FlyCode's AI retry engine distinguishes between transient issuer holds (recoverable with time) and persistent account flags (requiring customer action). Using network-level authorization data, FlyCode times retries to maximize recovery on temporary holds, and routes customers to payment update flows only when automated recovery is unlikely to succeed — minimizing friction and maximizing retention.
What does call_issuer mean?
The call_issuer decline code indicates that the issuing bank has refused the transaction and is directing the cardholder to contact them directly. The bank typically has an internal flag on the account that requires cardholder verification — but the specific reason is not disclosed to the merchant or communicated to the cardholder automatically.
Is it a soft or hard decline?
call_issuer is classified as a soft decline. The card may be valid once the issue is resolved, but recovery typically requires the cardholder to speak with their bank.
Common root causes
Temporary account verification required by the issuer
Suspicious activity flag requiring cardholder confirmation
Internal policy checks on specific transaction types
Address or identity mismatch on file
Pending card reissue or account update
Recommended recovery steps
Retry once after 24–48 hours — some issuer flags clear automatically.
If retries fail, route the customer to update their payment method or provide clear dunning messaging.
Use network tokens to reduce false positive issuer holds.
Avoid repeated retries — they continue to fail and can flag the merchant as aggressive.
How FlyCode handles call_issuer
FlyCode's AI retry engine distinguishes between transient issuer holds (recoverable with time) and persistent account flags (requiring customer action). Using network-level authorization data, FlyCode times retries to maximize recovery on temporary holds, and routes customers to payment update flows only when automated recovery is unlikely to succeed — minimizing friction and maximizing retention.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
What does call_issuer mean?
Can I retry a call_issuer decline?
One or two spaced retries can recover temporary holds, but most call_issuer declines require the cardholder to contact their bank. Persistent retries will not succeed if the account has an internal flag.
How does FlyCode handle call_issuer?
FlyCode uses network-level data to identify which call_issuer declines are recoverable through timed retries versus those that genuinely require cardholder action. This minimizes customer friction while recovering transient issues automatically.
