Monitoring Module
Catch the merchant that's no longer selling what you approved
Merchants rarely announce a category change. A wellness retailer starts listing kratom. A restaurant adds gambling content. A fashion shop pivots to pharmaceuticals. MCC drift detection compares the actual content of each scan against the merchant's approved Merchant Category Code and raises a dedicated alert the moment the match drops.
How it works
Anchor every merchant to an approved category
Every merchant has a declared Merchant Category Code captured at onboarding or bulk upload. The approved MCC is the baseline the platform compares against for the life of the merchant.
Classify on every scan
Every website scan produces a dominant content classification: the category the scan actually sees on the site today. This runs independently from the declared MCC.
Compare and raise
When the classified content drops outside the approved category, especially into a higher-risk BRAM family, an MCC drift alert is raised as a distinct alert class with its own severity and analyst queue.
MCC Drift Alert
highnewScan classified content outside the merchant's approved MCC family.
Pho Minh TradingPho Minh Trading Co Ltd
Quarterly scan completed · 27 pages analyzed
Approved Category
Grocery & Retail
Standard risk tier
Detected Category
Pharmaceuticals & Health
High risk tier
Category Match
31%Threshold for this merchant tier: 60% minimum match
An alert class of its own
MCC drift isn't just another content change. It is a structured mismatch between what the acquirer underwrote and what the merchant is actually selling. Treating it as a dedicated alert class (with its own severity rules, routing, and resolution codes) lets compliance teams track it separately from generic site changes.
Mapped to the 17 BRAM families
Merchant Category Codes are grouped into 17 BRAM content families. When drift moves a merchant into a prohibited family, the alert is escalated in severity automatically. When drift stays within adjacent low-risk families, the signal is dampened to reduce noise on routine product-line changes.
Backed by scan evidence
Every MCC drift alert links back to the scan that detected it: the classified category, the pages the classification is based on, and the full-page screenshots captured on that scan. The evidence is pre-assembled for investigation. Analysts don't need to re-crawl to decide.
Built for re-underwriting workflows
An MCC drift alert is not a silent pass. It is a prompt to re-underwrite. Resolutions include marking the alert as a confirmed legitimate pivot and re-categorizing the merchant, warning and monitoring, suspending processing, or terminating and MATCH-listing. Each resolution is recorded with a structured reason code.
Frequently asked questions
- How is MCC drift different from web change detection?
- Web change detection surfaces any material content change on the site. MCC drift is a specific subclass of change: the change moves the merchant into a different approved category than the one they were underwritten as. That makes MCC drift a much higher-signal alert that deserves its own queue and its own SLA.
- How is the drift threshold set?
- Thresholds are configurable per merchant risk tier. High-risk portfolios can alert at a smaller divergence from the approved category; standard retail portfolios can tolerate more movement before flagging. In both cases, drift into a prohibited BRAM family always raises an elevated alert regardless of threshold.
- What does the analyst do with an MCC drift alert?
- The analyst reviews the evidence (approved category, detected category, the scanned pages) and resolves the case with a structured reason code. Options include re-underwriting with the new category, warning the merchant, suspending processing, or terminating and listing in the MATCH file. Every resolution is retained in the merchant's case history.
- Does this replace MCC classification at onboarding?
- No. Onboarding still captures the declared MCC. MCC drift detection is the ongoing check that the merchant is still operating in that category. The two work together: onboarding sets the baseline, drift detection watches it.