💰 Why Don't Banks Share Their 'Bad Actor' Lists? The Game Theory Behind Compliance
> Paper: Compliance Moral Hazard and the Backfiring Mandate > Authors: Jian Ni, Lecheng Zheng, John R Birge > arXiv: 2604.21789 | 2026-04-29
---
1. The 'Every Bank for Itself' AML System
Bank A discovers a client is involved in money laundering and freezes the account. But Bank B never learns about this—because banks cannot (or will not) share information about suspicious client activity.
The result? The client moves to Bank B and keeps laundering money.
This is not a technology problem. It is an incentive problem.
Anti-money-laundering (AML) regulations require banks to monitor and report suspicious transactions. But each bank only sees its own customers' activity—a launderer's activity is scattered across multiple banks' records, with each bank seeing only fragments.
---
2. 'Compliance Moral Hazard'
The research introduces a core concept: Compliance Moral Hazard.
What does it mean?
- If one bank bears the entire cost of AML compliance (staffing, technology, compliance risk) while the benefit (catching money launderers) is shared by all banks, then every bank has an incentive to free-ride
- Worse, if regulation *mandates* information sharing, it can backfire—banks may adopt more conservative reporting strategies to avoid exposing their own customer-management failures
- Risk-sharing: if a money launderer moves from Bank A to Bank B, both banks jointly bear the regulatory penalty
- Internalizing the benefits of sharing: reduced risk from information sharing is converted into quantifiable economic gains
- Reputation mechanisms: a cross-bank 'compliance reputation' score
- If banks are forced to share all suspicious activity reports, they may lower reporting sensitivity to avoid reputational losses from 'false positives'
- If penalties target only 'missed reports' and not 'false reports,' banks may over-report, drowning out genuinely important leads
- If the legal risk of sharing information is too high, banks may become 'overly conservative' and share nothing
Mandating cooperation does not necessarily produce real cooperation.
---
3. Mechanism Design: Making Cooperation the Self-Interested Choice
The paper's contribution is a mechanism design framework:
Instead of forcing banks to share information, design incentives so that banks voluntarily share the information that benefits them.
Key ideas:
It's like designing game rules so that each player's optimal strategy is also the socially optimal strategy.
---
4. Why Mandates Can Backfire
A key finding: poorly designed mandates can backfire.
For example:
---
5. A Feynman-Style Judgment: Good Policy Understands Incentives
Though Feynman was primarily a physicist, his insistence on 'understanding the essence of a problem' applies equally to policy design:
> "If you don't understand incentives, you don't understand behavior."
Banks are not charities. Their behavior is driven by incentives. If AML policy ignores banks' self-interest, no regulation—however strict—will achieve its intended effect.
---
6. Takeaways
If you're designing a system that requires multi-party cooperation, ask yourself:
1. "What is each participant's self-interested motivation?" 2. "Is cooperation genuinely beneficial for each party?" 3. "Could mandating cooperation backfire?" 4. "Can you design incentives so that self-interested behavior automatically leads to the social optimum?"
The AML lesson: technology can solve the information-integration problem, but only the right incentives make parties willing to share information.
In the AI era, similar incentive problems are everywhere—data sharing, model collaboration, privacy protection—all demand deep thinking about mechanism design.
---
*From Zhichai Finance Lab.*