Visa and Mastercard Retry Limits: Avoid Excessive Reattempt Fees

On this page 8 sections

1. Why Aggressive Renewal Retries Now Trigger Excessive Retry Fees
2. Visa Reattempt Rules and How the Fees Work
3. Mastercard Merchant Advice Codes and Retry Bans
4. Do-Not-Retry Decline Codes vs. Retry-Later Codes
5. Building a Recurring Payment Retry Schedule by Decline Type
6. Timing Retries Around Paydays and Card Refreshes
7. Auditing Your Billing Platform's Retry Logic
8. Next Steps

Key takeaways

• Visa and Mastercard both limit how often a declined card can be retried, and both can charge fees for excessive or prohibited reattempts.
• Some declines mean "never retry." Others mean "try later." Your dunning logic has to treat them differently.
• An effective retry schedule uses fewer, better-timed attempts based on decline type, paydays and card updates.
• Audit every system that can retry a charge, including your billing platform, gateway and processor, so attempts aren't counted twice.

If your subscription billing system keeps retrying declined renewals until something goes through, it may be costing you twice: once in lost subscribers and again in excessive retry fees. Visa and Mastercard both limit how often a merchant can reattempt a declined card, and both treat certain declines as final. This guide explains how those limits work, which decline types should never be retried, and how to build a recurring payment retry schedule that recovers revenue without adding per-attempt charges to your statement.

Network rules, fee amounts and attempt caps change. The figures your processor applies to your account are what count. Treat this article as general guidance and confirm current terms with your processor before you change your billing logic.

Why Aggressive Renewal Retries Now Trigger Excessive Retry Fees

For years, subscription and membership businesses treated retries as free. A renewal failed, and the billing system tried again, sometimes daily and sometimes several times a day, until the card approved or the subscriber was canceled.

The card networks have pushed back on that habit for three main reasons:

• Issuer load. Repeated authorization requests on cards that will never approve consume issuer and network resources.
• Fraud signals. High-volume retries look a lot like card-testing attacks, which makes it harder for issuers to tell good merchants from bad actors.
• Cardholder experience. Repeated attempts on a closed or blocked account can trigger fraud alerts and confuse customers.

The result is a set of rules that cap reattempts and attach fees to retries that break those caps or ignore a "do not retry" response. For a subscription business with thousands of renewals each billing cycle, small per-attempt fees can add up quickly. The pattern can also draw attention from your acquirer, especially if your business already sits in a higher risk category. Our guide to why some businesses land in the medium-risk tier explains how recurring billing affects that classification.

Visa Reattempt Rules and How the Fees Work

Visa's reattempt rules rest on two ideas.

Some Declines Can Never Be Retried

Visa groups decline response codes into categories based on what the issuer is signaling. One category covers declines where the issuer is saying the transaction will never be approved. Typical examples are a closed account, an invalid card number, or a card reported lost or stolen. Retrying these is prohibited, and each prohibited reattempt can carry a fee.

Other Declines Can Be Retried, Within Limits

Other categories cover temporary or fixable problems, such as insufficient funds, a velocity limit or a general issuer decline. These can be retried, but only a limited number of times within a defined period. Visa's rules generally count repeated attempts on the same card by the same merchant. Attempts beyond the allowed number can be assessed fees.

What This Means in Practice

• Read the response code before deciding whether to retry. "It failed" isn't enough information.
• Track attempts per card and per transaction so you know where you stand against the cap.
• Look for related line items on your statement. Excessive reattempt fees often appear under a network fee label rather than as a clear "retry" charge, so ask your processor how they're labeled.

Visa publishes the exact attempt caps, time windows and fee amounts, and it updates them. Get the current figures from your processor in writing.

Mastercard Merchant Advice Codes and Retry Bans

Mastercard handles this differently. Along with many decline responses, Mastercard can return a merchant advice code (MAC), a separate field that tells you what to do next. Broadly, Mastercard merchant advice codes signal one of the following:

• Update the account information. The card may have been replaced. Get new credentials, through an account updater or from the customer, before trying again.
• Try again later. The decline is temporary. A retry after a reasonable delay may succeed.
• Do not try again. The cardholder or issuer has stopped this payment, for example after the customer canceled a recurring payment with their bank. Stop retrying.

Mastercard can charge fees for retrying after a "do not try again" advice code. It also monitors excessive attempts on the same card. The practical risk is that many billing platforms only read the main decline code and never look at the MAC field. A transaction that looks like a soft decline may carry a MAC that bans further attempts.

Ask your gateway or processor whether merchant advice codes are passed through to your billing platform, and whether your retry logic actually uses them.

Do-Not-Retry Decline Codes vs. Retry-Later Codes

Your processor's documentation will list exact codes. The table below shows how common decline reasons usually sort. Use it as a starting map, not a definitive list.

Two rules keep do-not-retry decline codes from turning into fees:

1. Hard-stop these codes in software. Don't leave it to a support agent to notice.
2. Don't create a "new" transaction to restart the count. Changing the amount slightly, splitting the charge or resubmitting under different details to get around attempt limits breaks network rules. It can lead to fees, account reviews or termination. The only compliant route is new valid credentials or the customer's fresh authorization.

Building a Recurring Payment Retry Schedule by Decline Type

A good recurring payment retry schedule uses a few well-chosen attempts instead of many blind ones. The schedule below is illustrative only. Adjust it to your billing cycle, your processor's guidance and the current network caps, and keep total attempts well inside those caps.

A few design principles apply whatever schedule you choose:

• Pair retries with dunning messages. Many involuntary churn cases are resolved by the subscriber updating their card, not by another retry. Our guide to reducing failed subscription payments and churn covers grace periods and messaging.
• Set a clear end point. Decide when the subscription is paused or canceled, and make sure your cancellation and notice practices follow the automatic renewal laws in each state where you have subscribers. These rules vary, so confirm your obligations with a qualified attorney.
• Flag retries correctly. Renewals should be submitted as merchant-initiated recurring transactions linked to the original stored-credential agreement. Correct flagging helps issuers recognize a legitimate renewal.
• Treat annual plans differently. A large annual renewal declined for insufficient funds may deserve more patience and personal outreach than a small monthly charge.

Timing Retries Around Paydays and Card Refreshes

When you retry often matters more than how many times you retry.

Paydays

Insufficient-funds declines often clear once the cardholder is paid. Many U.S. workers are paid weekly, every other week or twice a month, often around the 1st and 15th or on a Friday. Spacing retries so at least one lands just after those dates usually works better than retrying every day. If your subscribers are mostly businesses, think about when they're likely to have funds available, such as after month-end receivables come in.

Card Refreshes

Cards expire, get reissued after a breach and get replaced when lost. Retrying a card the issuer has already replaced wastes an attempt. A card account updater service can pull new card details from participating issuers before a renewal runs, which helps prevent many expired-card declines in the first place. See our walkthrough on using card account updater to keep subscribers billing for setup tips. Network tokens, where your gateway supports them, can also keep credentials current automatically.

Batch Timing

If all your renewals run on the 1st of the month, your retries will cluster as well. Spreading renewal dates across the month, or anchoring each one to the subscriber's signup date, reduces volume spikes and makes payday timing easier.

Auditing Your Billing Platform's Retry Logic

Many billing tools advertise smart retries for subscriptions, using machine learning or rules to pick the best retry time. That can help, but "smart" doesn't automatically mean "compliant." Work through this audit at least once a year and whenever you change platforms.

1. Map every system that can retry. Your billing platform, your payment gateway and sometimes your processor may each have retry settings. If two are active, you could be doubling attempts without knowing it.
2. Confirm raw codes reach your logic. Check that both the decline response code and Mastercard's merchant advice code are passed to the retry engine, not just a generic "failed" status.
3. Check hard stops. Test that do-not-retry responses end all attempts immediately.
4. Verify attempt counting. Make sure attempts are counted per card and per transaction across the full window, and that counters don't reset when a subscriber changes plans.
5. Review stored-credential flags. Confirm renewals are submitted as merchant-initiated recurring transactions with the correct references to the original agreement.
6. Read your statements. Look for network fees related to reattempts or authorization misuse, and ask your processor to explain any you don't recognize.
7. Document your policy. Write down your schedule and logic so you can show your acquirer a controlled process if you're asked.

If you run online subscriptions through Authorize.net or NMI, MannyPay supports both through its Authorize.Net integration and NMI gateway integration, and offers merchant accounts for online payments.

Next Steps

Excessive retry fees are avoidable. Read decline codes and merchant advice codes, stop retrying when the issuer says stop, space the remaining attempts around paydays and card updates, and audit every system that can resubmit a charge.

Start by pulling a month of declined renewals and sorting them with the table above. That will show how many attempts you're making on cards that will never approve.

If you'd like to review your recurring billing setup or processing costs, you can request a free quote from MannyPay. A MannyPay specialist responds to quote requests within one business day.

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.