---
description: Learn how Merchant Advice Codes help payment teams decide when to retry, update card details, switch methods, or stop resubmitting declines.
title: Merchant Advice Code: Definition and Next Steps
image: https://cdn.smartretry.com/cdn-cgi/image/width=1200,height=630,quality=85,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Fog-image.0z0q4_5kazzzo.jpeg
---

[Skip to main content](#main-content)

# Merchant Advice Code

MAC, merchant advice response, merchant guidance code, network advice code

Published

July 8, 2026

Last updated

July 27, 2026

![Reading time](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Fclock.337f-cmnyb532.svg)6 min

## Still letting failed transactions slip through?

SmartRetry turns declines into approvals - automatically, intelligently, and without changing your payment provider.

Table of Contents

A Merchant Advice Code is a card-network or issuer-provided indicator that tells a merchant how to handle a declined or completed payment next, such as whether to retry, update account details, use a different payment method, or stop resubmitting the transaction.

## How does Merchant Advice Code work?

Merchant Advice Codes, often shortened to MACs, are returned alongside certain card transaction responses through the payment stack. They add instruction to the main response by signaling the recommended next action after an authorization attempt or account status event.

In practice, the decline code explains what happened at a high level, while the Merchant Advice Code helps explain what the merchant should do next. For example, a response may indicate that a retry is allowed after a temporary issue, that account credentials should be refreshed, or that no further authorization attempts should be submitted.

The exact values and meanings depend on the card network and on how the acquirer, processor, or PSP passes that data through. Some providers normalize the codes into internal categories, while others expose raw network values. Payment teams therefore need to map Merchant Advice Codes carefully and verify whether the code came directly from the network, from the issuer, or from a processor interpretation layer.

Merchant Advice Codes are most useful when they are tied to decisioning logic. A merchant can use them to suppress harmful retries, trigger account updater workflows, route the customer to another payment method, or schedule a delayed retry only when the code supports it.

## Why does Merchant Advice Code matter for payment teams?

Merchant Advice Codes matter because they turn vague decline handling into action-based decisioning. Without them, merchants often apply broad retry rules that increase issuer friction, create unnecessary authorization traffic, and lower recovery efficiency.

For payment operations teams, the main value is precision. A Merchant Advice Code can indicate whether a decline is recoverable, whether a credential update is more appropriate than a retry, or whether the transaction should be abandoned to avoid repeated soft decline pressure on the issuer relationship.

For engineering and revenue teams, Merchant Advice Codes support better retry orchestration. They help separate temporary failures from hard stops, reduce blind resubmission, and improve the quality of recovery flows across subscription billing, card-on-file transactions, and other recurring payment programs.

They also matter for network compliance and issuer trust. Ignoring advice signals can lead to excessive retries on transactions that should not be resubmitted, while using them correctly improves approval strategy and protects long-term payment performance.

## What are common use cases for Merchant Advice Code?

* **SaaS and subscription merchants:** Use Merchant Advice Codes to decide whether to retry a recurring invoice, trigger account updater, or ask the customer to replace an expired or closed card.
* **Ecommerce retail merchants:** Use Merchant Advice Codes to distinguish between temporary issuer issues and do-not-retry outcomes before launching post-checkout recovery attempts.
* **Travel and OTA merchants:** Use Merchant Advice Codes to manage reattempts on high-value bookings where timing matters and repeated declines can create inventory and customer service problems.
* **Digital goods merchants:** Use Merchant Advice Codes to automate fallback to another saved payment method when issuer guidance suggests the original credential will not succeed.
* **Gaming merchants:** Use Merchant Advice Codes to reduce rapid-fire retries on card-on-file transactions and apply issuer-friendly spacing between attempts.
* **Marketplace platforms:** Use Merchant Advice Codes to standardize decline recovery policies across many sellers and PSP connections while preserving network-specific handling rules.

## Merchant Advice Code vs decline code

| Aspect          | Merchant Advice Code                                                        | Decline code                                                                           |
| --------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Primary purpose | Advises the merchant on the next action to take.                            | States why the authorization was not approved.                                         |
| Typical meaning | Retry later, update credentials, use another method, or stop retrying.      | Insufficient funds, do not honor, expired card, suspected fraud, and similar outcomes. |
| Decision value  | High for retry orchestration and recovery workflows.                        | High for root-cause classification, but less specific on next steps.                   |
| Source          | Usually card network or issuer guidance delivered through processor layers. | Issuer authorization response code delivered through the network.                      |
| Operational use | Controls retry timing, suppression, updater triggers, and fallback actions. | Supports reporting, customer messaging, and broad decline categorization.              |

## How is Merchant Advice Code measured?

* **MAC coverage rate:** Merchant Advice Code-present transactions divided by total eligible declined or relevant transactions.
* **Recoverable MAC rate:** Transactions with retry-eligible or update-eligible advice divided by total MAC-tagged transactions.
* **Suppressed retry rate:** Transactions where a planned retry was blocked due to do-not-retry advice divided by total retry candidates.
* **Advice-to-recovery conversion:** Successfully recovered payments following a MAC-driven action divided by total MAC-driven actions.
* **Retry waste rate:** Retries submitted against non-retryable advice divided by total retries.
* **Provider pass-through quality:** Share of raw network Merchant Advice Codes that are correctly exposed and mapped by the PSP or processor.

## What are best practices for Merchant Advice Code?

* Map Merchant Advice Codes separately from issuer decline codes. They answer different operational questions and should not be merged into one generic decline bucket.
* Build action classes such as retry now, retry later, update credentials, use fallback payment method, and stop retrying. Then map each Merchant Advice Code into one of those decision paths.
* Validate pass-through behavior by PSP, acquirer, and region. The same transaction may expose different levels of advice detail depending on the provider connection.
* Use Merchant Advice Codes together with payment history, billing cycle timing, and customer value. A retry-allowed signal should still be filtered through merchant-side risk and recovery logic.
* Suppress retries aggressively when advice indicates no further attempt. This protects issuer relationships and prevents avoidable decline loops.
* Monitor recovery outcomes by advice category. If a code consistently underperforms, adjust retry timing, messaging, or fallback routing rather than treating all soft declines the same.

## How does SmartRetry help with Merchant Advice Code?

SmartRetry helps merchants operationalize Merchant Advice Codes instead of just logging them. It can use advice signals, decline context, network responses, and historical recovery performance to decide whether to retry, when to retry, and when to stop.

This is especially useful when processor data is inconsistent or when multiple PSPs expose advice signals differently. SmartRetry can normalize decision inputs, reduce non-productive retries, and align recovery flows with issuer-friendly logic.

For subscription and card-on-file merchants, SmartRetry makes Merchant Advice Codes actionable inside automated revenue recovery. Go deeper with SmartRetry’s intelligent retries and payment recovery workflows.

### Frequently asked questions about this term

What is a Merchant Advice Code?

A Merchant Advice Code is an indicator from a card network or issuer that tells a merchant what action to take after a payment response.

What does a Merchant Advice Code tell merchants to do?

It can indicate whether to retry, update account details, use a different payment method, or stop resubmitting the transaction.

How is a Merchant Advice Code different from a decline code?

A decline code explains what happened at a high level, while a Merchant Advice Code signals the recommended next action.

Where do Merchant Advice Codes appear?

They are returned alongside certain card transaction responses through the payment stack after an authorization attempt or account status event.

Do Merchant Advice Code values mean the same thing everywhere?

No. The exact values and meanings depend on the card network or issuer providing the response.

#### Share this article

[![Share on X](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Ftwitter.21z6yr9njnznr.svg)](https://twitter.com/intent/tweet?text=Merchant%20Advice%20Code&url=https%3A%2F%2Fwww.smartretry.com%2Fglossary%2Fmerchant-advice-code-2 "Share on X")[![Share on Facebook](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Ffacebook.3sbfjbsxa26qg.svg)](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.smartretry.com%2Fglossary%2Fmerchant-advice-code-2 "Share on Facebook")[![Share on LinkedIn](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Flinkedin.09sdc8tnlrn4a.svg)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.smartretry.com%2Fglossary%2Fmerchant-advice-code-2 "Share on LinkedIn")

Make us your preferred source

## Join our newsletter!

Real strategies to recover lost revenue - straight to your inbox

---

## You might also find interest in those terms:

[View all](/glossary)

["Account Updater"](/glossary/account-updater) ["Decline Code"](/glossary/decline-code) ["Soft Decline"](/glossary/soft-decline) ["Hard Decline"](/glossary/hard-decline) 

## Articles you may find interesting:

[View all](/blog)

[![How payment teams decode generic declines to recover approvals and reduce failed payments](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F07%2Fdecode-generic-declines-recover-approvals.jpg) July 4, 2026 The Mystery of the Generic Decline: Decoding Vague Payment Failures This article explains how payment teams can interpret vague issuer responses, use AVS, CVV, BIN, and timing clues, and apply smarter recovery tactics to reduce lost revenue and improve approval performance.](/blog/generic-decline-payment-failures)[![Mastercard Merchant Advice Codes for smarter decline recovery and better authorization performance](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F03%2Fimage-63.jpg) March 8, 2026 The Secret Language of Issuers: Decoding Merchant Advice Codes This article explains how issuer advice codes turn vague declines into clear retry actions, helping payments teams recover revenue, cut unnecessary retries, and reduce involuntary churn.](/blog/merchant-advice-codes)[![How intelligent decline recovery improves approvals and protects recurring revenue](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F03%2Fimage-26.jpg) March 8, 2026 Why Card Declines Happen and How Intelligent Recovery Protects Revenue This article explains why card payments fail, how issuers classify declines, and how smart retry logic improves approvals, reduces involuntary churn, and protects merchant revenue.](/blog/card-declines-guide)

---

```json
{"@context":"https://schema.org","@type":"DefinedTerm","@id":"https://www.smartretry.com/glossary/merchant-advice-code-2","name":"Merchant Advice Code","termCode":"merchant-advice-code-2","description":"Merchant Advice Code is a payment response indicator that guides merchants on whether to retry, update payment details, use another method, or stop resubmitting a transaction.","url":"https://www.smartretry.com/glossary/merchant-advice-code-2","alternateName":["MAC","merchant advice response","merchant guidance code","network advice code"],"inDefinedTermSet":{"@type":"DefinedTermSet","name":"SmartRetry Glossary","url":"https://www.smartretry.com/glossary"}}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://www.smartretry.com/glossary/merchant-advice-code-2#webpage","url":"https://www.smartretry.com/glossary/merchant-advice-code-2","name":"Merchant Advice Code: Definition and Next Steps","description":"Merchant Advice Code is a payment response indicator that guides merchants on whether to retry, update payment details, use another method, or stop resubmitting a transaction.","datePublished":"2026-07-08T08:26:06.000Z","dateModified":"2026-07-27T04:21:20.000Z","author":{"@type":"Organization","@id":"https://www.smartretry.com/#organization","name":"SmartRetry","url":"https://www.smartretry.com","logo":{"@type":"ImageObject","url":"https://cdn.smartretry.com/logo.png","width":{"@type":"QuantitativeValue","value":175,"unitCode":"PX"},"height":{"@type":"QuantitativeValue","value":29,"unitCode":"PX"}},"description":"SmartRetry is a smart payment recovery platform that helps businesses save revenue from failed payment transactions and reduce false declines.","sameAs":["https://x.com/smartretry","https://www.facebook.com/smartretry","https://www.instagram.com/smartretry","https://www.linkedin.com/company/smartretry","https://www.youtube.com/@smartretry"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","availableLanguage":["Hebrew","English"],"url":"https://www.smartretry.com/contact"},"address":{"@type":"PostalAddress","streetAddress":"Menachem Begin","addressLocality":"Tel Aviv-Yafo","addressCountry":"IL"}},"isPartOf":{"@type":"WebSite","@id":"https://www.smartretry.com/#website","name":"SmartRetry","url":"https://www.smartretry.com","description":"Payment recovery guides, tools and reference data from SmartRetry - failed payment recovery, false decline prevention and authorization rate optimization.","inLanguage":"en","publisher":{"@type":"Organization","@id":"https://www.smartretry.com/#organization","name":"SmartRetry","url":"https://www.smartretry.com","logo":{"@type":"ImageObject","url":"https://cdn.smartretry.com/logo.png","width":{"@type":"QuantitativeValue","value":175,"unitCode":"PX"},"height":{"@type":"QuantitativeValue","value":29,"unitCode":"PX"}},"description":"SmartRetry is a smart payment recovery platform that helps businesses save revenue from failed payment transactions and reduce false declines.","sameAs":["https://x.com/smartretry","https://www.facebook.com/smartretry","https://www.instagram.com/smartretry","https://www.linkedin.com/company/smartretry","https://www.youtube.com/@smartretry"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","availableLanguage":["Hebrew","English"],"url":"https://www.smartretry.com/contact"},"address":{"@type":"PostalAddress","streetAddress":"Menachem Begin","addressLocality":"Tel Aviv-Yafo","addressCountry":"IL"}}},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".term-definition"]}}
{"@context":"https://schema.org","@type":"FAQPage","author":{"@type":"Organization","@id":"https://www.smartretry.com/#organization","name":"SmartRetry","url":"https://www.smartretry.com","logo":{"@type":"ImageObject","url":"https://cdn.smartretry.com/logo.png","width":{"@type":"QuantitativeValue","value":175,"unitCode":"PX"},"height":{"@type":"QuantitativeValue","value":29,"unitCode":"PX"}},"description":"SmartRetry is a smart payment recovery platform that helps businesses save revenue from failed payment transactions and reduce false declines.","sameAs":["https://x.com/smartretry","https://www.facebook.com/smartretry","https://www.instagram.com/smartretry","https://www.linkedin.com/company/smartretry","https://www.youtube.com/@smartretry"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","availableLanguage":["Hebrew","English"],"url":"https://www.smartretry.com/contact"},"address":{"@type":"PostalAddress","streetAddress":"Menachem Begin","addressLocality":"Tel Aviv-Yafo","addressCountry":"IL"}},"mainEntity":[{"@type":"Question","name":"What is Merchant Advice Code?","acceptedAnswer":{"@type":"Answer","text":"Merchant Advice Code is a payment response indicator that guides merchants on whether to retry, update payment details, use another method, or stop resubmitting a transaction."}}]}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.smartretry.com/"},{"@type":"ListItem","position":2,"name":"Glossary","item":"https://www.smartretry.com/glossary"},{"@type":"ListItem","position":3,"name":"Merchant Advice Code","item":"https://www.smartretry.com/glossary/merchant-advice-code-2"}]}
```
