“Merchant Advice Code”

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

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.