On this page
- How it works
- Scope
- Rollout dates (as-of 2024-01-01)
- MAC 24–30 retry windows
- Distinction from issuer-assigned MACs
- Mastercard-generated decline codes
- Fees
- Authorization Optimizer fee (as-of 2024-01)
- Transaction Processing Excellence (TPE) excessive authorization fee (as-of 2025-01)
- EU-specific excessive authorization fee (as-of 2025)
- Relationship to Transaction Processing Excellence (TPE)
- PSP API exposure
- Smart retry suites (adjacent programs)
- European and fashion/retail context
- 2025–2026 programme evolution
- Payment Optimization Platform (POP) — October 2025
- On-Demand Decisioning (ODD) — September 2025
- Possible developer portal rebranding
- Visa comparison
- Governing documents (as-of 2026-02-03)
- Key terms
- Next frontier
Authorization Optimizer
Authorization Optimizer
Mastercard's network-layer program (Core Release AN 6042) that intercepts authorization responses for recurring card-not-present (CNP) insufficient-funds declines and appends one of seven Merchant Advice Codes (MAC 24–30) specifying the optimal retry window — before the response reaches the acquirer.
How it works
When a cardholder's bank (issuer) returns decline code 51 (insufficient funds) on a recurring CNP transaction, the Mastercard network intercepts the authorization response in transit. Mastercard's algorithm appends a network-generated MAC value to the ISO 8583 field DE48 SE84 and then forwards the enriched response to the acquirer. The issuer sends the Code 51 decline; Mastercard — not the issuer — selects which specific MAC value within 24–30 to attach. (Braintree/PayPal Developer Docs, Mastercard Fall 2023 Network Updates, developer.paypal.com, published 2023-10)
The program's stated purpose is to reduce unnecessary authorization retry traffic on the Mastercard network while giving merchants precise guidance on when to retry. (Braintree F23, 2023-10)
Who determines the MAC 24–30 value?
- Slickerhq (2026-08): "MAC 24 through 30 tell the merchant to retry after 1 hour, 24 hours, 2, 4, 6, 8, or 10 days respectively, based on the issuer's view of when the account is likely to be funded." (slickerhq.com/resources/blog/code-51-soft-decline-retry-timing-mac-codes)
- Braintree F23 (2023-10): the MAC 24–30 value is appended by the Mastercard network before the response reaches the acquirer; the issuer has no direct control over which value is selected. (developer.paypal.com/braintree/articles/risk-and-security/compliance/network-updates/2023/mastercard-f23) No public source resolves whether Mastercard's algorithm incorporates issuer balance-prediction signals in selecting the specific MAC value.
Scope
- Eligible transactions: recurring CNP only — subscriptions, instalment billing, unscheduled credentials-on-file; NOT applicable to one-off CNP payments or card-present transactions. (Braintree F23, 2023-10)
- Trigger decline code: 51 (Insufficient Funds) only for MAC 24–30; separately, decline codes 79, 82, and 83 trigger MAC 01 or 03.
Rollout dates (as-of 2024-01-01)
| Region | Effective date |
|---|---|
| United States | 9 October 2023 |
| European Union | 1 January 2024 |
| Canada | TBD 2024 (unconfirmed) |
(Braintree F23, developer.paypal.com, 2023-10)
MAC 24–30 retry windows
The seven MAC codes introduced by Authorization Optimizer map to minimum retry intervals (as-of 2026-08-13):
| MAC code | Minimum retry window |
|---|---|
| MAC 24 | 1 hour |
| MAC 25 | 24 hours |
| MAC 26 | 2 days |
| MAC 27 | 4 days |
| MAC 28 | 6 days |
| MAC 29 | 8 days |
| MAC 30 | 10 days |
(TabaPay Developer Docs, developers.tabapay.com; Braintree F23, developer.paypal.com, 2023-10; Slickerhq, 2026-08 — three sources consistent)
Distinction from issuer-assigned MACs
| Code range | Who assigns | Mechanism | Examples |
|---|---|---|---|
| MAC 01–22 | Issuer (cardholder's bank) | Bank populates DE48 SE84 directly in its authorization response | MAC 01 (new account info), MAC 02 (retry permitted), MAC 03 (do not retry), MAC 21 (fraud suspected) |
| MAC 24–30 | Mastercard network | Network intercepts Code 51 response in transit, appends MAC before forwarding to acquirer | See retry table above |
(Braintree F23, developer.paypal.com, 2023-10; TabaPay Developer Docs)
Mastercard-generated decline codes
The same 2023 AN 6042 update introduced three Mastercard-network-only decline codes:
- Code 79 — Lifecycle decline (Mastercard use only)
- Code 82 — Policy decline (Mastercard use only)
- Code 83 — Fraud/Security decline (Mastercard use only)
These accompany MAC 01 or MAC 03 and represent Mastercard acting as the effective decision-maker rather than the issuer. (Braintree F23, developer.paypal.com, 2023-10)
"Authorization Optimizer" — two distinct Mastercard products share this name:
- The MAC-based CNP retry guidance program (AN 6042, 2023 launch): compliance-driven; assigns retry windows to Code 51 declines on recurring CNP. Documented in acquirer/PSP compliance notes (Braintree, Worldpay). (developer.paypal.com, 2023-10)
- The Payment Optimization Platform (POP) (October 2025 launch): AI/data enrichment; uses network intelligence to enrich authorization messages broadly and boost approval rates — distinct from the retry-guidance program. (mastercard.com, 2025-10-13) Both are described as "authorization optimization" in different Mastercard communications; they are different products that can operate in tandem.
Fees
Authorization Optimizer fee (as-of 2024-01)
- 3bps (0.03%) per qualifying transaction — minimum $0.0003, maximum $0.075
- Applies when: recurring CNP transaction + decline code 51 + MAC 24–30 received
- Applies whether or not the merchant uses the MAC guidance in their retry logic
- Asia-Pacific region rollout confirmed in Mastercard Summer 2024 network updates (Braintree SU24, developer.paypal.com, 2024)
Transaction Processing Excellence (TPE) excessive authorization fee (as-of 2025-01)
Retrying a transaction after receiving MAC 03 or MAC 21 — or exceeding 35 retry attempts in a rolling 30 days — triggers the TPE Excessive Authorization fee:
| Effective date | Fee per excess transaction |
|---|---|
| November 2022 | $0.10 |
| November 2023 | $0.15 |
| January 2024 | $0.30 |
| January 2025 | $0.50 |
(Braintree F23 + SU24, developer.paypal.com, 2023–2024; Merchant Cost Consulting, merchantcostconsulting.com)
Fee ladder sourced from Braintree F23 (2023-10) and confirmed in SU24 (2024). The $0.50/transaction figure reflects January 2025 enforcement. Mastercard may have updated fees since — check the current SPME Manual (last confirmed: 2026-02-03 at mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/SPME-Manual.pdf) for the operative rate.
EU-specific excessive authorization fee (as-of 2025)
- €0.55 per transaction when a merchant exceeds 35 declined authorization attempts on the same account, same card acceptor, and same amount within a 30-day window
- Effective from 1 August 2024 in the EU
- Creates a dual-layer compliance cost for European ecommerce operators alongside the global 3bps MAC fee
(IXOPAY, "Card Scheme Penalty Fees in 2025," ixopay.com, published 2025)
Relationship to Transaction Processing Excellence (TPE)
Authorization Optimizer sits within Mastercard's Transaction Processing Excellence (TPE) programme — a suite of compliance and network-efficiency initiatives. The wider TPE programme also covers:
- Excessive Authorization Attempts — retry limit enforcement (35/30-day, 10/24-hour)
- Nominal Authorization — fees on micro-authorizations (≤2 currency units, from Sep 2024)
- Excessive Declines monitoring
The Authorization Optimizer addresses Code 51 soft declines (timing problem); the Excessive Authorization programme addresses retrying hard-declined transactions (compliance problem). Both use MAC codes as the signalling mechanism. (Braintree F23; Merchant Cost Consulting)
PSP API exposure
| PSP | Field name | Notes |
|---|---|---|
| Adyen | additionalData.merchantAdviceCode | Automatic — no Customer Area setting required (as-of live docs, docs.adyen.com/online-payments/auto-rescue/cards) |
| Checkout.com | partner_merchant_advice_code | In API payment response; guidance updated 2025-10-01 (support.checkout.com) |
| Worldpay (WPG) | <MAC> XML tag | Requires explicit activation via Relationship Manager; applies to Mastercard/Maestro on SAS routing (docs.worldpay.com) |
| Braintree | Documented in compliance bulletins | No explicit SDK field name found in public docs (Braintree F23, 2023-10) |
| Stripe | Not explicitly named | Stripe uses Adaptive Acceptance + Smart Retries internally; no public merchantAdviceCode-equivalent field named in public docs (gap) |
Note on Adyen: a GitHub issue (issue #115, adyen-go-api-library) reported merchantAdviceCode missing from returned payloads for some API versions — field availability may depend on Adyen API version or processor routing. (as-of filing date, GitHub)
Smart retry suites (adjacent programs)
PSPs have built proprietary AI retry programs that run alongside or instead of direct MAC-code handling:
- Adyen Auto Rescue — automatically retries refused shopper-not-present transactions; rescue window up to 48 days (default ~30 days) for cards, 42 days for SEPA; reported rescue rate >40%; Pinterest case study: 4% improvement in recovery rate expected to reach 10%. (Adyen Docs, docs.adyen.com/online-payments/auto-rescue, live)
- Adyen Uplift (launched ~Jan 2025) — AI payment optimization suite; pilot results: up to 6% overall uplift in payment conversion, 3% improvement in authorization rates for network tokenization users. (Adyen, adyen.com/uplift, ~2025-01; vendor-stated figures)
- Stripe Smart Retries — AI-driven retry timing for failed subscription/invoice payments; default 8 tries within 2-week window; average recovery rate 57% of originally failed recurring payments; vendor claims $9 revenue recovered per $1 spent on Billing. (Stripe Docs, docs.stripe.com/billing/revenue-recovery/smart-retries, live; vendor-stated ROI)
- Stripe Adaptive Acceptance — broader false-decline recovery; $6B in falsely-declined transactions recovered in 2024 (+60% YoY); by May 2025, further 27% YoY increase with 35% fewer retry attempts. (Stripe Blog, stripe.com/blog/ai-enhancements-to-adaptive-acceptance, ~2025-05; vendor-stated)
European and fashion/retail context
The EU rollout (1 January 2024) means all EU/UK Mastercard and Maestro recurring CNP payments have been subject to MAC 24–30 guidance for over 18 months as of August 2026. (Braintree F23, 2023-10)
Tokenization reduces Authorization Optimizer triggers: three in five Mastercard ecommerce transactions in Europe are now processed using tokens rather than static card credentials (as-of 2026-06). Tokenized transactions reduce unnecessary Code 51 declines because tokens are updated automatically via Account Updater, directly lowering Authorization Optimizer MAC frequency. Merchant tokenization (Secure Card on File) is live in 45 European countries as of mid-2026. (Mastercard Europe Newsroom, 2026-06)
Fashion/retail sector scope: the Authorization Optimizer's primary relevance for fashion ecommerce is through stored-card recurring billing — loyalty programme billing, BNPL instalment plans, subscription services (e.g., rental fashion), and Click & Collect pre-authorizations on Mastercard. Standard one-off checkout transactions are not in scope. No fashion-specific impact data (e.g., UNIQLO, Zara, H&M) was found in public sources. (gap)
Mastercard 48% insufficient-funds stat: Mastercard states that 48% of declines in subscription-based services are attributed to insufficient funds, making MAC 24–30 guidance directly relevant to the majority of subscription payment failures. (Mastercard Global Insights, mastercard.com/global; as-of retrieval date — vendor-published, no independent verification found)
2025–2026 programme evolution
Payment Optimization Platform (POP) — October 2025
Mastercard launched POP on 13 October 2025 — a network-based AI service that enriches authorization messages with real-time network intelligence to boost approval rates broadly. Distinct from the MAC-based Authorization Optimizer (which targets only Code 51 recurring declines), POP operates across authorization types. (Mastercard US Newsroom, mastercard.com, 2025-10-13)
- Pilot results: 9%–15% increase in transaction conversions (as-of 2025-10)
- Launch partners: Adyen, NEOPAY, Tap Payments, Worldpay
- Evaluates over one trillion combinations of data elements in near real-time
- Part of Mastercard Merchant Cloud; designed to integrate without rearchitecting existing payment infrastructure
(Mastercard Press Release, mastercard.com, 2025-10-13; PYMNTS, pymnts.com, 2025-10)
On-Demand Decisioning (ODD) — September 2025
Mastercard unveiled ODD on 11 September 2025 — allowing issuers to define their own decisioning criteria directly on the Mastercard network, enforcing automated approvals/declines in real time without routing back to the issuer's own systems. Made globally available by 11 October 2025. (Mastercard US Newsroom, mastercard.com, 2025-09-11)
Possible developer portal rebranding
Searches for the legacy URL developer.mastercard.com/authorization-optimizer/documentation/ returned no live results; the current Authorization Management product documentation lives at developer.mastercard.com/authorization-management/documentation/. The Authorization Optimizer may have been absorbed into a broader Authorization Management product suite. (as-of 2026-08-13, gap — not confirmed)
Visa comparison
| Dimension | Mastercard (Authorization Optimizer) | Visa |
|---|---|---|
| Retry guidance mechanism | Network-generated MAC 24–30 with specific hour/day windows | Decline categories 1–4 with category-level retry rules |
| Category 1 equivalent | MAC 03/21 — do not retry | Category 1 — zero retries permitted |
| Soft decline retry ceiling | MAC 24–30 timing guidance (no fixed count ceiling per code) | Up to 15 re-attempts in 30 days (categories 2–4) |
| Named time-window codes | Yes (MAC 24 = 1hr, MAC 25 = 24hr, etc.) | No — category labels only, no hour/day intervals |
| Excess retry fee | $0.50/transaction (Jan 2025); EU €0.55/transaction (Aug 2024) | $0.10 domestic / $0.15 international per excess retry |
| Fee trigger threshold | 35 attempts / 30 days; 10 / 24 hours | 15 attempts / 30 days (certain categories) |
(Slickerhq, "Visa and Mastercard Payment Retry Rules," 2026-06; IXOPAY, 2025; Braintree F23, 2023-10)
Notable Visa update (as-of 2024): Visa reclassified decline codes 62, 78, and 93 from Category 1 (never retry) to Category 2 (retryable) in April 2024, and introduced new code Z5. (CardPointe Support, support.cardpointe.com; confidence: med)
Governing documents (as-of 2026-02-03)
- Mastercard Transaction Processing Rules (TPR) — last updated 2025-12-09; governs Authorization Optimizer programme rules
- Mastercard Security Rules and Procedures — Merchant Edition (SPME Manual) — last updated 2026-02-03; operative compliance source for merchants
(Mastercard, mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/)
Key terms
| Term | Meaning |
|---|---|
| AN 6042 | Mastercard Core Release identifier for the Authorization Optimizer Service Enhancement |
| DE48 SE84 | ISO 8583 data element / sub-element where the MAC is written in an authorization response |
| Code 51 | Issuer decline code: Insufficient Funds — the trigger for MAC 24–30 assignment |
| TPE | Transaction Processing Excellence — Mastercard's suite of network-efficiency compliance programmes |
| POP | Payment Optimization Platform — Mastercard's October 2025 AI-based authorization enrichment service |
| ODD | On-Demand Decisioning — Mastercard's September 2025 issuer-side automated decisioning service |
| CNP | Card-Not-Present — transaction type where the physical card is absent (ecommerce, subscriptions) |
Next frontier
- Transaction Processing Excellence — no dedicated page; TPE is the parent programme
- Payment Optimization Platform (POP) — no page; October 2025 Mastercard AI service
- Account Updater — no page; automatically refreshes stored card credentials on tokens
- Adaptive Acceptance — no page; Stripe's false-decline recovery program
- Excessive Authorization Attempts — no dedicated page; the adjacent TPE sub-programme