Where does the MCC come from on a payment platform?

It is set when the merchant is onboarded, based on its business activity, and confirmed by the acquirer. KYB forms collect the information that determines it, and the onboarding workflow carries it to each acquiring partner.

Set at onboarding, confirmed by the acquirer

The merchant category code describes what the merchant sells. It is assigned when the merchant account is created, from the business activity declared in the application, and the acquirer confirms it when it approves the merchant. The code then travels with every transaction and drives interchange, fraud rules, monitoring programs and sometimes whether the activity is accepted at all.

On a platform

• KYB forms collect the activity, the products, the website and the business model.
• The onboarding workflow proposes an MCC from those answers and lets the operator's team confirm it.
• Each acquiring partner receives the MCC in the merchant application, in its own format.
• The MCC is stored on the merchant account, so routing rules and reporting can use it.

Why operators should care

A wrong MCC is expensive in both directions. Too low-risk, and the acquirer can reclassify the merchant, apply fines or terminate. Too high-risk, and the merchant pays more interchange than it should. Operators that review MCCs at onboarding and when a merchant changes activity keep both problems away. Reporting by MCC also shows which categories drive disputes and fraud in the portfolio.