Visa Reason Code 12.7: Invalid Data

What Visa reason code 12.7 means

Reason code 12.7 is a Processing Errors dispute about the data behind the authorization, not the purchase itself. The issuer says the authorization request contained invalid or incorrect information, the kind that could have changed its decision if it had been correct.

Examples include:

• An incorrect merchant category code (MCC), the four-digit code that tells issuers what kind of business you are
• Incorrect merchant location data, such as the wrong country or state
• An incorrect transaction date
• Other authorization fields that misstate the type or circumstances of the transaction

The MCC case matters most. Issuers apply different risk rules, and some cardholders apply spending blocks, by category. An authorization obtained under the wrong MCC may have been approved only because the issuer couldn’t see what the transaction really was.

12.7 is a collaboration code. Unlike most 12.x codes, issuers generally have a shorter 75-day window to raise it.

Common causes

• A payment facilitator or marketplace boarding sub-merchants under a generic MCC
• A business that changed what it sells without updating its merchant account
• Gateway or terminal configurations copied from another merchant account
• A merchant location set to the acquirer’s country rather than where the business operates
• In high-risk verticals, MCC “laundering” to get around category-based declines, which breaches Visa’s rules

Evidence that wins a 12.7 dispute

Your acquirer usually evaluates 12.7 from the transaction data, so merchant-supplied evidence plays a smaller role than in other codes. What you can do:

1. Confirm your boarding details with your acquirer: MCC, legal name, location and descriptor.
2. Provide documentation of your business type if the MCC on file is correct and the issuer has misread it.
3. Provide transaction-date evidence (order and capture timestamps) if the date is in question.
4. Supply the transaction record matching the authorization, so your acquirer can verify each field.

Customer communication and delivery proof generally don’t help. The dispute isn’t about whether the customer got what they paid for.

How to prevent 12.7 chargebacks

• Review your merchant account profile once a year and whenever you change product lines.
• If you run on a payment facilitator, confirm the MCC you were boarded under matches your business.
• Check that gateway and terminal settings (location, MCC, descriptor) match the merchant account they process for.
• Never misstate your business category to improve approval rates. The disputes are the least of the consequences.

Should you fight or accept?

Fight only when your acquirer confirms the authorization data was correct.

Accept when the data was wrong, and treat the dispute as a warning about your account setup. A misconfigured MCC affects every transaction you process, so correcting it prevents both future 12.7s and the declines and compliance problems that come with it.