Whitepaper
The End of Header Enrichment: Protect Your Carrier Billing Revenue After Chrome 154

Chrome 154 makes HTTPS the default for every Chrome user worldwide. Header enrichment, the silent identification behind one-tap Direct Carrier Billing, only works over unencrypted HTTP. Once traffic is encrypted, operators can no longer pass the subscriber’s number to the service, and the two-tap payment flow breaks.
The exposure is significant. Around 90% of two-click DCB flows rely on header enrichment, and Chrome carries roughly 75% of mobile browser traffic. Our model puts $9–12.4 billion in annual DCB revenue at risk. That exposure is concentrated in markets where carrier billing fills the gap left by low card penetration, across Southeast Asia, Africa, the Middle East and Latin America.
Produced with the Mobile Ecosystem Forum (MEF), this whitepaper gives operators and DCB aggregators a clear way forward. It includes:
- A revenue-at-risk model you can apply to your own numbers
- Insights from MobileArts, Telefónica, Digital Virgo and other industry leaders
- A comparison of replacement approaches
- A five-step action plan to restore one-tap conversion