Visa Decline Code Changes Oct. 23–25: Fix Your Retry Logic Now

On this page 7 sections

1. What Visa Changed on October 23 and 25, 2026
2. Visa Response Code 57 Retry Rules: Joining the "Never Approve" Program
3. Visa Response Code 83 and the Reported Reclassification of Codes 12, 15 and 57 to 05
4. How Bad Retry Logic Leads to Visa System Integrity Fees
5. Card Decline Retry Rules: A Checklist for Subscription and Card-on-File Merchants
6. Questions to Ask Your Processor or Billing Platform This Week
7. Next Steps

Key takeaways

• Starting Oct. 25, 2026, Visa response code 57 is reported to move into the Issuer Will Never Approve reattempt program, so any retry on a 57 can trigger System Integrity Fees.
• Visa's new response code 83 marks transactions that Visa declined for fraud while standing in for the issuer. Don't put it into an automatic retry loop.
• Under Visa's April 2026 rules, Category 1 declines can never be retried, and other declines are capped at 20 attempts in 30 days. Older processor docs still say 15.
• Find out this week exactly how your gateway or billing platform maps Visa's raw codes and counts retries.

If your billing system handles a Visa response code 57 retry the same way it handles any other failed charge, fix that this week. Visa's decline-code changes take effect between Oct. 23 and Oct. 25, 2026. After that, retrying the wrong declines can cost you network fees. This brief covers what changed, which codes to stop retrying, how the fees work, and what to ask your processor. It's written for subscription, membership, e-commerce and gym merchants who keep cards on file.

Information current as of Oct. 23, 2026. Network rules change often, so confirm the details with your processor.

What Visa Changed on October 23 and 25, 2026

According to a roundup of October 2026 network updates from Merchant Cost Consulting, two Visa changes land this week:

• Oct. 23: new response code 83. Visa will use it only for transactions it blocks for network-level fraud during stand-in processing.
• Oct. 25: response code 57 ("Transaction Not Permitted to Cardholder") moves into Visa's Issuer Will Never Approve reattempt program. Retrying these declines can now trigger System Integrity Fees.

Industry briefings also describe a third change: issuer codes 12, 15 and 57 may be returned as 05 in some transactions. We explain that below, with a caveat.

Card brands other than Visa have their own retry rules. Nothing here changes them. If you're also watching other October costs, see our breakdown of Visa's October 2026 fee changes.

Visa Response Code 57 Retry Rules: Joining the "Never Approve" Program

Visa sorts every decline into one of four categories. The category decides whether you can retry and how often. Here's how the April 2026 rulebook breaks down, based on summaries from PayKings and DEV Community:

Two points about this table:

• The limit is now 20, not 15. PayKings notes that many processor help pages still say 15 reattempts in 30 days. The April 2026 Visa rules say 20. If your billing logic was built around 15, you're still within the limit, but confirm which number your processor actually enforces.
• Code 57 was already listed as "never retry." The reported change for Oct. 25 is about enforcement. Code 57 now falls under the fee program, so a retry on a 57 can actually cost you money. Whatever your system did with 57 before, it should stop retrying now.

Why Subscription Merchants See Code 57

A 57 means the issuer won't allow that card to be used for that type of transaction or at that type of merchant. The problem is a restriction on the card itself, not a lack of funds. According to Retries.com, it often shows up in subscription billing when:

• A customer switches to a corporate card that restricts certain merchant categories
• A customer uses a prepaid card that blocks recurring charges

Waiting won't fix either one. The fix is to contact the customer. Slicker's code 57 guidance suggests three steps: ask the cardholder to call their issuer, request another payment method, and check that your merchant category code (MCC) is correct. That last step matters. If you're seeing a lot of 57s, ask your processor whether your MCC matches what you actually sell. Never change your coding just to get around a card's restrictions.

Visa Response Code 83 and the Reported Reclassification of Codes 12, 15 and 57 to 05

What New Code 83 Means

When an issuer can't respond, Visa can authorize or decline on its behalf. This is called stand-in processing (STIP). Visa's April 2026 rulebook describes RC 83 as a Visa-only code for transactions it declines during stand-in because of high-risk or fraudulent conditions. The rulebook lists an effective date of July 25, 2026. The processor-facing summaries put the rollout on Oct. 23. Ask your processor when your gateway will actually start sending it.

One April 2026 summary puts 83 in Category 2, which would allow limited retries. Even so, retrying a fraud block automatically is a bad idea. The safer approach:

• Pause the account instead of retrying on a schedule.
• Contact the customer and ask them to confirm the charge with their bank, or to update their card.
• For online checkouts, have the customer pay again with authentication, such as 3-D Secure.

Don't confuse this with Visa dispute reason code 83, an older chargeback code for card-not-present fraud. Response code 83 is an authorization decline. The two are separate systems.

The Reported Reclassification to 05

Some industry briefings say that starting Oct. 23, issuer codes 12 (invalid transaction), 15 (no such issuer) and 57 may be returned as 05 in certain transactions. As of publication, we couldn't confirm the details in Visa's public rulebook. That includes which transactions qualify and how the change interacts with stand-in. Ask your processor directly before you change your logic around it.

What Do Not Honor Code 05 Means for Your Retry Counts

Do Not Honor (05) is a Category 4 generic decline, so retries are allowed within the 20-in-30-days limit. If some hard declines start arriving as 05, a retry engine that treats 05 as "try again later" will keep retrying cards that will never work. Here's how to protect yourself:

• Set your 05 retry limit well below the network maximum, and spread attempts across several days.
• Stop retrying once you hit that limit and switch to customer outreach.
• Look for cards that return 05 over and over across billing cycles, and flag them for a card update.

For a full code-by-code reference, see our guide to credit card decline codes and what to do about each one.

How Bad Retry Logic Leads to Visa System Integrity Fees

Visa charges acquirers for authorization behavior that breaks these rules. Your processor then passes the charges on to you. Two fees matter here:

• Issuer Will Never Approve fee: charged on every reattempt after a Category 1 decline. One retry is enough to trigger it.
• Excessive reattempt fee: charged on attempts beyond the limit for Category 2–4 declines.

Sources report different amounts. Chargebacks911 cites $0.10 per domestic attempt and $0.25 cross-border as of April 2026. An earlier Merchant Cost Consulting explainer listed $0.15 for international reattempts. Processors can also pass the fee through at a higher rate. Chargebacks911 points to one bank's published schedule as an example. Check your contract for your actual amount.

On your statement, look for descriptions like "VS RAF Excessive Reattempts" or wording that mentions Issuer Never Approve. The Segpay documentation shows domestic and cross-border versions.

One detail card-on-file merchants often miss: according to Pulse, the rule covers account verification requests as well as authorizations. A $0 verification on a card that already returned a 57 is still a reattempt.

Illustrative example: A martial arts studio bills monthly dues on the 1st and retries failed cards once a day for 10 days. One member's new corporate card returns a 57. The old logic sends nine more attempts, and every one of them now falls under the Never Approve program. Each fee is small. But the same pattern across dozens of accounts, every month, adds up. And it shows your processor that your billing isn't following network rules.

Card Decline Retry Rules: A Checklist for Subscription and Card-on-File Merchants

Work through this list with whoever owns your billing system:

1. Hard-stop Category 1 codes. 04, 07, 12, 14, 15, 41, 43, 46, 57, R0, R1 and R3 should never be retried on the same card. That includes $0 verifications.
2. Make sure stop rules use the raw Visa code. Many gateways translate codes into their own messages. Confirm that a 57 still triggers a stop after translation.
3. Handle 83 on its own. Pause the account and contact the customer. Don't send it into your normal retry queue.
4. Cap 05 and other soft declines conservatively. Count every attempt per card over a rolling 30 days, including customer-initiated retries if your platform tracks them.
5. Fix data-quality declines before retrying. For codes like 54 (expired card), update the card details first. Don't just resend the same charge.
6. Reduce declines at the source. Card updater services and network tokenization keep stored cards current.
7. Send hard declines to dunning. Customer outreach recovers payments that retries can't. Our guide to smart retries and dunning for failed subscription payments covers schedules and messaging.
8. Check every statement for reattempt fee lines, and trace any you find back to specific accounts.

Gyms and Martial Arts Studios

Dues are usually billed in a batch on the same day each month, so one bad rule repeats across the whole membership list at once. Ask members with failed cards to update their card at the front desk or through your member app. Don't let the system keep retrying. If you're reviewing hardware or billing setup too, see our payment options for boxing, combat sports and fitness businesses.

E-Commerce Stores and Digital Products

Digital goods and low-ticket online sales also attract card testing, so a sudden spike in declines can point to fraud rather than billing errors. Use rate limits and authentication at checkout, and don't auto-retry fraud-related declines. Our e-commerce payment processing guide covers the wider setup.

Questions to Ask Your Processor or Billing Platform This Week

• When will our gateway start sending Visa response code 83, and how will it appear in our reports?
• Do you return the raw Visa response code, or a translated one? Can we see the mapping?
• What happens to 12, 15 and 57 declines after Oct. 23? Could any arrive as 05?
• Does your retry engine block Category 1 codes automatically, including $0 verifications?
• Do you enforce 15 or 20 attempts in 30 days for Category 2–4 declines?
• What do you charge per Never Approve or excessive reattempt fee, and how is it labeled on our statement?
• Can we get a monthly report of reattempts by card and by decline code?

If your current payment gateway can't answer these questions, that's worth factoring into your next review. MannyPay supports gateways including Authorize.net and NMI, as well as integrations with platforms such as Shopify and WooCommerce.

Next Steps

The fix is straightforward. Stop retrying 57 and the other "never approve" codes. Handle 83 as a fraud signal. Cap 05 retries conservatively. Confirm with your processor how each code reaches your system. If you'd like a second opinion on your setup for online and card-on-file payments, request a free quote and a MannyPay specialist will respond within one business day. You can also contact the MannyPay team with questions.

This article is general information, not legal or compliance advice. Confirm current Visa rules and fees with your processor.

Sources

1. Merchant Cost Consulting: October 2026 Interchange and Network Updates
2. Visa Core Rules and Visa Product and Service Rules (18 April 2026)
3. PayKings: Visa and Mastercard Card Retry Rules
4. DEV Community: Card Decline Codes: Visa vs Mastercard Retry Rules
5. Chargebacks911: Visa Excessive Reattempts Rule
6. Merchant Cost Consulting: Visa Issuer Never Approve Fee
7. Pulse: Visa and Mastercard Authorization Retry Rules 2026
8. Segpay: Merchant Advice and Response Codes
9. Retries.com: Decline Code 57
10. Slicker: Visa Code 57

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.