Skip to main content
SmartRetry - Payment Recovery Platform

Mastercard

Mastercard Decline Code 30: Format Error

hard decline

Last updated: October 8, 2026

Key details

Brand
Mastercard
Code
30
Response
30
Detailed Response
Format error
hard decline
This transaction is not retriable

Payments failing with code 30 are hard declines and typically cannot be recovered by retrying. SmartRetry still helps you avoid future hard declines with smarter routing and validation.

But many other declines in your payment flow may still be recoverable. SmartRetry identifies which failed transactions have recovery potential and applies the right strategy to recover them.

Find out what you can recover >

What it means

Mastercard issuer response code 30 indicates that the issuer does not recognize the transaction details presented in the authorization request. It is a technical formatting or configuration error, most commonly triggered by an incorrect terminal ID (TID) or the presence of invalid characters in the transaction data. This decline is not related to the cardholder's available funds.

Why does code 30 occur?

  • The transaction request contains an incorrect or unregistered terminal ID (TID).
  • The authorization payload includes malformed or invalid characters that the issuer cannot process.
  • There is a persistent merchant integration or mapping defect causing improper transaction data formatting.

How to solve 30?

First, review the original authorization request to verify that the terminal ID (TID) and merchant identifier match your acquirer's registered configuration. Check the transaction data payload for any malformed fields, invalid characters, or encoding errors. Once the formatting or configuration errors are identified and corrected, submit a new authorization request. If subsequent attempts fail after corrections, escalate the issue to your acquirer or processor with the original request, response, TID, and transaction timestamp.

Solving as a merchant

Compare the submitted request with your acquirer's registered merchant and terminal configuration to validate field encoding, allowed characters, and routing parameters. Correct any improperly formatted data or incorrect TIDs in your payment gateway settings before attempting a retry. Suppress repeated identical attempts to avoid accumulating unnecessary declines.

Solving as a client

No action is required from the customer, as this is a technical formatting issue on the merchant or processor side.

Tip from SmartRetry Halt immediate automated retries on code 30, as repeating an identical payload will consistently fail and can trigger network penalty flags. Instead, hold the retry until your system applies automated character sanitization or reroutes the payment through a verified secondary acquirer connection.

See the full list of Mastercard's decline codes >Find code on Mastercard's website >

Frequently asked questions about this topic

Share this article

Share on XShare on FacebookShare on LinkedIn
Kyle Regacho

Author

Kyle Regacho
LinkedInFind me on Linkedin

Focused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue

Read all articles >

Articles you may find interesting:

View all
How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

Discover how automated risk reviews trigger gateway freezes and how payment teams can insulate revenue through multi-acquirer setups and smart retry logic.

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Payment rejections cost merchants billions in lost sales and unforced churn. Discover the root causes behind issuer declines and how intelligent recovery strategies salvage legitimate revenue.

Why Payment Tests Pass in Staging and Fail in Production

Why Payment Tests Pass in Staging and Fail in Production

Passing a sandbox check rarely guarantees live authorization success. Learn how real-world issuer ambiguity, webhook delays, and network retry rules impact revenue pipelines.

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Sandboxes verify API formatting, but live issuers determine transaction success. Discover how multi-layered testing, safe retry logic, and real-time observability safeguard authorization rates and reduce involuntary customer churn.

Decline codes tell you why. We fix it.

SmartRetry reads every decline reason and applies the right retry strategy for each one. Your recovery rate goes up without any changes to your payment provider.