Mastercard Merchant Advice Codes Explained for Ecommerce Merchants

May 26, 2026

When a Mastercard payment fails, the hard part isn’t the decline itself. It’s knowing whether to retry, wait, or stop.

That choice affects revenue, customer trust, and future dispute risk. Mastercard merchant advice codes help by giving your payment stack a clearer next step, especially for recurring billing, stored cards, and other card-not-present transactions.

If your team handles failed payments by broad rules alone, these codes can help you recover more revenue with fewer bad retries.

What merchant advice codes actually mean

A merchant advice code, often called a MAC, is a short code returned with a declined Mastercard authorization. It tells the merchant what action makes sense after the decline.

That matters because the decline reason and the next action are not always the same thing. A response code explains what happened. The advice code tells you what to do now.

A merchant advice code is an instruction for the next step, not a full diagnosis of the decline.

For ecommerce merchants, this is most useful in recurring payments and card-on-file billing. A one-off decline might be simple. Subscription billing is not. You need to know whether to retry tonight, wait two days, refresh card details, or stop attempts altogether.

Some gateways expose these codes clearly. Others hide them behind internal retry logic or map them into broader categories. So if you don’t see MAC data in your processor dashboard, ask your PSP or gateway how Mastercard advice is passed through.

According to Solidgate’s payment guide, these codes are built to help merchants decide whether a failed payment should be retried and when. That sounds simple, but it fixes a common problem: too many merchants treat every decline the same way.

When that happens, teams either give up too fast or keep retrying when they shouldn’t. Both outcomes cost money.

The Mastercard codes ecommerce teams see most often

You don’t need to memorize every possible code. You do need to understand the patterns.

Here are some common Mastercard advice codes and the action they usually point to:

The pattern is straightforward. Some declines need patience. Some need fresh payment data. Some are a clear stop sign.

Code 03 is the one many merchants mishandle. If Mastercard says do not retry, repeated attempts usually waste fees, clutter reporting, and frustrate the customer when they see several failed payment notifications. For a subscription merchant, that means your dunning flow should switch from retries to outreach.

Code 01 can be valuable for saved-card models. If new account information is available, your card updater or token refresh flow may recover the payment without asking the customer to re-enter anything.

Timed retry codes, such as those in the 24 to 30 range, matter because they replace guesswork with a schedule. A merchant that retries too soon can fail again for the same reason. A merchant that waits as instructed has a better shot at recovery.

For a practical overview of how merchants use these codes, Chargebacks911’s explanation of merchant advice codes is a useful reference.

Why these codes matter beyond a failed payment

At first glance, MACs look like a decline-management tool. They are. But the effect reaches further into retention, support, and dispute prevention.

For subscription businesses, bad retry logic creates involuntary churn. If a valid customer hits a temporary decline and your system gives up, you lose revenue you could have recovered. On the other hand, if the cardholder canceled, replaced the card, or needs to update billing details, blind retries can create more confusion.

That confusion often lands in your support queue first. Then it can turn into a dispute.

Ecommerce merchants with stored cards face the same issue. A smart payment stack shouldn’t treat a temporary issuer problem like a dead card. It also shouldn’t hammer a card that Mastercard has already told you not to retry.

This is where merchant advice codes help clean up operations. They let you:

• match retry timing to the issuer’s guidance,
• separate retriable declines from dead ends,
• route some failed payments into account updater flows,
• trigger customer messages only when they are needed.

That improves recovery, but it also reduces noise. Your team spends less time chasing doomed retries. Customers get fewer confusing payment notices. Finance gets cleaner data on why revenue was lost or won back.

MACs won’t solve every failed payment problem. They do, however, make your retry logic less blunt.

Where merchant advice codes meet chargeback prevention

A merchant advice code is not a chargeback alert. It arrives earlier, at the authorization stage. Still, there is a real connection between the two.

Poor handling of declines can push customers toward disputes. Repeated billing attempts after a canceled subscription, confusing rebill timing, or failed retries that later turn into a manual charge can all spark complaints. In card-not-present commerce, a preventable complaint can become a chargeback fast.

So MACs work best as one layer in a wider dispute-prevention system. They help you handle declines well. Then you need tools that catch the cases that move beyond the payment stage.

That is where software like Chargebase fits. Chargebase is a chargeback prevention platform for ecommerce and SaaS merchants. It connects with payment providers quickly, monitors likely disputes, and sends real-time alerts while merchants still have time to act. As an Ethoca and Verifi partner, it helps teams refund or resolve issues before they become formal chargebacks. It also supports programs such as Ethoca alerts, Rapid Dispute Resolution, and CDRN, with automated rules and pay-per-alert pricing. For most companies, that means fewer chargebacks and less manual work.

In other words, merchant advice codes help you decide what to do with a failed payment. Chargeback prevention software helps you deal with the disputes that failed-payment logic alone can’t stop.

If you want the network view of how disputes move through the Mastercard system, Mastercard’s merchant chargeback guide gives helpful background.

How to use MACs in your payment workflows

The best setup is simple, but it has to be deliberate.

First, map your retry rules to the advice codes your gateway exposes. Don’t use one universal schedule for every Mastercard decline. A code that says “try later” should feed a timed retry queue. A code that says “do not try again” should suppress future attempts until the customer updates payment details.

Next, separate recurring billing from one-time checkout. Subscriptions need richer logic because retries happen without the customer present. That’s where MACs pay off most.

Then log the codes in a place your payments, support, and finance teams can review. If recovery is weak, you’ll want to know whether the issue is timing, bad card data, token problems, or customer churn.

It also helps to line MACs up with your customer messaging. If a card truly shouldn’t be retried, send a clear update request. If the advice says wait, you may not need to contact the customer at all.

Finally, connect decline handling to dispute handling. When payment retries fail and customer confusion rises, chargeback prevention tools should take over. That handoff matters for ecommerce brands with high order volume, global customers, or subscription rebills.

Good payment operations are rarely about one signal. They are about reading the right signal at the right time.

Conclusion

A declined Mastercard payment doesn’t always mean the same thing, and it should not trigger the same response every time. Merchant advice codes give ecommerce teams a better way to decide when to retry, when to wait, and when to stop.

Used well, they recover revenue, reduce wasted retries, and cut customer friction. Pair them with strong dispute prevention, including tools like Chargebase, and your payment stack gets a lot smarter where it counts most.