MCC (merchant category code)

Where it sits in a QR payload

Card networks invented MCCs to classify transactions, and payment QR standards inherited them. In a UPI payload the code rides as a query parameter:

upi://pay?pa=shop@upi&pn=Corner%20Store&mc=5411

In an EMVCo merchant-presented payload: the format behind PIX, PromptPay and BharatQR. It is tag 52, one of the mandatory data objects alongside the merchant name and currency. Common values: 5812 eating places, 5411 grocery stores, 5912 pharmacies, 4121 taxis; 0000 appears where no registered category applies, typically person-to-person codes.

Why the number matters

The MCC is not decoration: acquirers and apps use it for interchange pricing, transaction limits, cashback and rewards eligibility, tax reporting, and risk rules. A shop encoded with a wrong MCC can see payments declined by apps that block that category, or lose customers whose cards exclude it from rewards. When a payment provider issues your QR payload, the MCC inside was set at merchant onboarding; if you build the payload yourself for a personal code, omitting mc= (or using 0000) is the honest choice. Static personal codes and their trade-offs are covered in static vs dynamic UPI QR.

FAQ

What is mc in a UPI QR code?

The merchant category code, a four-digit ISO 18245 value describing the merchant's business type. Payment apps read it for limits, rewards and reporting. Personal codes usually omit it or carry 0000.

Do I need an MCC for my payment QR code?

Only if you are a registered merchant, and then your provider assigns it. A person accepting transfers does not need one; an incorrect self-assigned MCC causes more problems than a missing one.