Mastercard Payment Decline Code

Mastercard Decline Code 82: Policy Decline

Category Transaction RestrictionsRetry Guidance Conditional Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026

What Mastercard Decline Code 82 Means

Mastercard decline code 82 (Policy Decline) indicates that the issuer declined the transaction based on an internal policy rule. It is returned during authorization to tell the merchant the payment could not be approved as submitted.

Where the Response May Come From

Mastercard code 82 (Policy Decline) is returned by the card issuer during authorization and signals that an issuer policy rule blocked the authorization. Issuers rarely disclose the precise internal cause, so treat it as a directional signal rather than a full explanation.

Common Reasons for This Response

Common causes include an issuer policy on the transaction type, merchant category, or account behavior. The exact trigger depends on the issuer, the account, and how the transaction was submitted, so the same code can appear in several different situations.

Should the Merchant Retry the Payment?

Whether a retry helps depends entirely on the fact that an issuer policy rule blocked the authorization; retry only once that condition is genuinely resolved, and avoid immediate repeat attempts that conflict with network retry expectations.

Recommended Merchant Action

Confirm the cause first, since an issuer policy rule blocked the authorization, then review the declining policy condition with the issuer or processor, and ask the customer to contact their issuing bank if the response points to their account.

What to Tell the Customer

Let the customer know the payment did not go through because an issuer policy rule blocked the authorization, and suggest contacting their bank or trying another payment method. Keep the wording neutral and avoid asserting issuer details you cannot confirm.

How to Reduce Similar Payment Failures

Segmenting how often an issuer policy rule blocked the authorization appears by issuer and BIN, monitoring policy-driven declines for recurring patterns, and submitting clean, correctly formatted authorization data can reduce avoidable occurrences of this decline over time.

Important Limitations

Decline-code meanings vary by processor, gateway, and payment environment, and issuers do not always disclose the specific reason behind a response. The retry classification on this page is Payment Defender editorial guidance, not an official Mastercard rule. Merchants should confirm handling with their processor or gateway.

Related Decline Codes

Sources and Review Information

Last reviewed July 17, 2026

Raw network-response codes are supplemental to the complete processor or gateway response. Meanings and recommended actions can vary by issuer, processor, gateway, card network, payment method, region, and merchant configuration.

Turn the Code Into Action

Know What to Do Next

Payment Defender helps merchants connect reason codes to transaction history, dispute alerts, refunds, evidence, fraud activity, VAMP exposure, and payment-performance decisions.