A quiet Visa fee change that went live April 1 is turning crypto MCC costs into a per-transaction margin variable.
Visa's Integrity Risk Fee for certain crypto-related transactions went live April 1. It applies to MCC 6012 and 6051 (per Merchant Cost Consulting's 2026 interchange roundup).
If your portfolio touches Web3 programs, crypto exchanges, or any high-risk MSB activity, this is one of those "quiet" changes that can materially move portfolio math.
Here's the practical shift:
For years, a lot of the network (scheme) fee burden on these high-risk MCCs felt relatively known. You could treat it as a cost stack you planned around, then focus your energy on underwriting, monitoring, and staying inside the compliance lines.
Visa is now doing something different. They're pricing regulatory and compliance risk directly at the transaction level.
Meaning: it's not only the VIRP application fees and annual renewals anymore. Every qualifying crypto transaction on these MCCs can carry an additional Integrity Risk Fee on top of the existing scheme fee stack.
Why that matters:
When fees become transaction-level, your cost base isn't just "high." It's variable. And it can change quickly when the network's view of the category changes.
So if you're an issuer, BIN sponsor, or acquirer with exposure here, I'd be modeling a few things right now:
1) Interchange give-up: - What share of interchange on MCC 6012/6051 is now being offset by the Integrity Risk Fee plus VIRP costs? - (And at what volumes does that become a meaningful margin drag?)
2) Pass-through and pricing mechanics: - If you pass fees through to program managers, do your contracts actually allow clean pass-through here? - If you don't pass through, what pricing change preserves your margin without blowing up the relationship?
3) Portfolio unit economics - Under the new fee stack, do your program economics still clear? - If the answer is "yes, but barely," what's your trigger for repricing, pausing growth, or tightening MCC exposure?
And the broader signal is worth sitting with: Scheme fee tables aren't just pricing tables anymore.
They're becoming a regulatory guardrail. When networks want to discourage activity in a category, they don't always need to change the rules. They can just reprice the category until the economics stop working for someone in the chain.
High-risk card issuing and acquiring isn't "just" a compliance audit anymore. It's turning into a scheme-fee modeling exercise that you need to run continuously, not quarterly.
Curious: if your portfolio touches 6012/6051, are you treating these as fully pass-through fees, or absorbing some portion to keep program pricing stable?
