Response Code 05: Do not honor
SOFT DECLINE
RETRIABLE
ISO 8583 FIELD 39
Generic refusal from the issuer. The most common decline code, covering everything from suspected fraud to temporary holds.
What Does Code 05 Mean?
Response code 05 is the catch-all decline. When an issuer declines a transaction but doesn't want to reveal the specific reason, they return code 05. It is by far the most common decline code in both card-present and card-not-present environments.
Because code 05 covers such a wide range of underlying reasons, it is one of the most recoverable codes through retry logic. The issuer may have flagged the transaction due to velocity checks, geographic anomalies, or temporary risk scoring. These conditions often resolve on their own within 24-48 hours as the cardholder makes other successful transactions that update the issuer's risk model.
For subscription billing, code 05 is the single most important code to get right. A significant percentage of involuntary churn from failed recurring payments carries this code. The difference between retrying it and not retrying it can translate directly into recovered revenue.
Should You Retry?
Recovery Guidance
The single most recoverable decline code. Retry timing, frequency, and context all influence recovery rates. Getting this right can meaningfully reduce involuntary churn.
Common Causes
- Issuer fraud model flagged the transaction but won't disclose why
- Velocity limits triggered by multiple transactions in a short window
- Temporary hold placed by the issuer for risk review
- Geographic mismatch between billing address and transaction origin
- New card that hasn't yet been activated for online transactions
Network Behavior
The same response code can mean different things depending on the card network. Here is how each network treats Code 05:
| Network |
Retry? |
Limit |
Notes |
| Visa |
Yes |
15 attempts in 30 days |
About 11% of all Visa declines. Visa Category 4 (generic response codes). Visa now caps generic codes at 5% of an issuer's total declines and fines issuers who exceed this. VisaNet also remaps all Code 59 (Suspected Fraud) responses to Code 05 before they reach acquirers, a legacy practice that inflates the Code 05 count. |
Mastercard
MAC 02 or 03 (varies) |
Yes |
10/day, 35/month |
Only about 4% of Mastercard declines use Code 05, the lowest of any major network. Always check the accompanying MAC code: MAC 02 means retry is appropriate, MAC 03 means never retry (penalty fee applies). The timed MAC codes (24 through 30) may also appear, specifying exact retry delays from 1 hour to 10 days. |
| Amex |
Yes |
|
The vast majority of Amex declines return Code 05. Because Amex operates as both the card network and the issuer (closed-loop), they have no incentive to share specific decline reasons with merchants. Industry reports and merchant data consistently show Amex using Code 05 at rates far exceeding Visa or Mastercard. Code-based retry decisions provide little signal on Amex volume. |
| Discover |
Yes |
|
Around 7% of Discover declines. Discover also operates as a closed-loop network (both network and issuer for most cards), but they return Code 05 less frequently than Amex. Note: Discover forbids merchants from contacting the cardholder about a disputed transaction. |
Platform Mappings
This code surfaces under different names depending on the payment platform:
| ISO 8583 | 05 - Do not honor |
| Stripe | generic_decline |
| Stripe | do_not_honor |
Related Decline Codes
Related Guides
Mastercard Merchant Advice Codes (MACs)
Complete reference for Mastercard MACs: MAC 01-42, retry windows, Stripe integration, TPE penalties, and how to use MACs to optimize payment retries
Visa Decline Code Categories Explained
Visa's 4-category decline system: which codes are retriable, retry limits, excess reattempt fees, and how to map Stripe network_decline_code to Visa categories
Hard vs Soft Declines: The Complete Guide
How to classify hard and soft declines across Visa, Mastercard, and Amex
ISO 8583: The Protocol Behind Every Card Payment
How ISO 8583 works: message structure, key fields, Field 39 decline codes, and why a 1987 standard still drives modern payment authorization
Mastercard Transaction Processing Excellence (TPE)
Mastercard TPE fee structure, retry thresholds, MAC 03/21 rules, and how to avoid excess authorization fees
Virtual Cards, Programmatic Limits, and Why Your Retry Logic Is Wrong
How virtual cards from Ramp, Brex, and corporate spend platforms create declines that traditional retry logic cannot recover
Why a 1987 Standard Still Processes Every Card Payment
How 33 pages written in 1987 became the messaging standard behind every card transaction on Earth
See This Code in Action
Watch how response code 05 flows through a complete ISO 8583 authorization lifecycle.
Open Transaction Simulator