A Merchant Advice Code is a card-network response value, most commonly used by Mastercard, that tells a merchant or payment processor how to handle a declined authorization. It adds retry guidance beyond the decline code, including whether to stop retrying, wait, or use a specific recovery action. For more in-depth analysis of decline handling and retry rules shaped by issuer logic, see Issuer Decline Codes: Retry Logic & Auth Recovery.
How does Merchant Advice Code work?
A Merchant Advice Code, often shortened to MAC, is returned alongside an authorization response when the card network wants to provide more specific handling instructions for a declined transaction. The standard decline code explains the broad reason for the failure. The Merchant Advice Code adds operational guidance about what the merchant should do next.
In practice, the code is passed through the issuer, network, acquirer, gateway, or PSP response chain. Depending on the integration, the merchant may receive a simplified MAC value or a raw network value that must be mapped into a retry instruction. That instruction can mean do not retry, retry after a defined waiting period, or route the customer into another recovery flow such as updating payment details.
Merchant Advice Codes are especially important for automated billing and recurring payments because they help distinguish between recoverable and non-recoverable declines. For example, a decline that looks generic at the response-code level may still carry a MAC that signals a required delay before the next authorization attempt. Payment teams use that guidance to shape retry logic, customer messaging, and compliance with card-network rules. To learn more about optimizing recurring payment retries with Merchant Advice Codes, see Merchant Advice Codes: Smarter Retries & Higher Auths.
Why does Merchant Advice Code matter for payment teams?
Merchant Advice Codes matter because they turn decline handling from guesswork into rules-based action. A payment team that ignores them may retry too soon, retry too often, or retry transactions that should not be retried at all. That reduces approval efficiency and can create avoidable network costs.
They also matter because card networks increasingly tie retry behavior to fees and compliance expectations. Mastercard charges an excess authorization fee of $0.50 for every retry after receiving MAC 03 or 21 within 30 days (Slicker, 2025). For merchants with large recurring billing volumes, misreading or ignoring MACs can quickly turn into a measurable revenue leakage problem.
Operationally, MACs help payment teams separate retries that are likely to recover from those that should be suppressed. That improves decline recovery rates, protects issuer trust, and reduces unnecessary authorization traffic across the PSP and acquirer stack.
What are common use cases for Merchant Advice Code?
-
SaaS and subscription merchants: Use MACs to schedule intelligent retries on failed recurring invoices instead of retrying every decline immediately.
-
Ecommerce retail merchants: Use MACs to decide whether to reattempt a checkout authorization or prompt the shopper for a new card or payment method.
-
Travel and OTA merchants: Use MACs to manage delayed retries on high-value bookings where timing and issuer sensitivity affect approval odds.
-
Digital goods merchants: Use MACs to suppress futile retries on low-ticket purchases and reduce unnecessary authorization volume.
-
Gaming merchants: Use MACs to distinguish issuer-advised wait periods from permanent retry stops during top-ups and recurring purchases.
-
Marketplace merchants: Use MACs to standardize decline recovery logic across many sellers, PSP connections, and regional acquiring setups.
Merchant Advice Code vs decline code
| Term | What it tells you | Main purpose | How payment teams use it |
|---|---|---|---|
| Merchant Advice Code | What action to take after a decline | Guide retries and recovery handling | Set retry delays, suppress retries, or trigger alternate recovery flows |
| Decline code | Why the authorization was declined at a high level | Classify the failure reason | Segment declines into categories such as insufficient funds, issuer rejection, or suspected fraud |
How is Merchant Advice Code measured?
-
MAC coverage rate: The share of declined transactions that include a Merchant Advice Code. Formula: MAC-tagged declines / total declines.
-
MAC compliance rate: The share of retries that follow the advised action or wait period. Formula: compliant retries / total retries on MAC-tagged declines.
-
Recovery rate by MAC: The percentage of declined transactions recovered after following MAC-specific retry logic. Formula: recovered payments / MAC-tagged declines.
-
Suppressed retry rate: The share of MAC-tagged declines that were intentionally not retried because the code indicated not to reattempt.
-
Excess authorization fee exposure: The count and cost of retries made in violation of network advice windows or do-not-retry instructions.
-
Approval lift from MAC-aware routing: The difference in recovered approvals between MAC-informed retry strategies and generic retry strategies.
What are best practices for Merchant Advice Code?
-
Store Merchant Advice Codes at the transaction level and keep the raw network value when available. This preserves auditability and supports accurate rule mapping.
-
Do not treat all soft declines the same. Use MAC-specific logic instead of broad retry rules based only on soft decline vs hard decline.
-
Honor advised wait periods precisely. Retrying too early can hurt approval performance and increase fee exposure.
-
Separate non-recoverable declines from delayed-recovery declines. A do-not-retry instruction should suppress authorization attempts and shift the customer into an update or outreach flow.
-
Measure recovery performance by MAC family, issuer, BIN, and PSP. The same advice pattern can perform differently across processors and card portfolios.
-
Keep retry orchestration centralized. Fragmented retry logic across billing systems, gateways, and internal tools often causes duplicate or non-compliant retries.
How does SmartRetry help with Merchant Advice Code?
SmartRetry helps merchants operationalize Merchant Advice Codes inside a controlled retry system. It can interpret decline outcomes, align retries to network-advised timing, and suppress attempts that are unlikely to recover. That helps teams reduce wasted authorizations while concentrating retry volume where approval probability is higher.
For recurring payments and invoice recovery, SmartRetry also helps unify response data across processors and billing workflows so that MAC-aware logic is applied consistently. This is especially useful when merchants need to balance revenue recovery, issuer acceptance, and authorization cost control at scale.
Go deeper with SmartRetry’s intelligent payment retry and failed payment recovery workflows.
