The recent Chrome 154 update makes HTTPS-first the default, breaking the legacy HTTP mechanism that many Direct Carrier Billing flows use to identify subscribers seamlessly.
For operators still relying on it, this is a conversion and revenue problem.
Around 90% of two-click payment flows rely on header enrichment. Chrome accounts for roughly 75% of mobile browser traffic. And when users are pushed from silent identification to alternative flows, the potential conversion loss on Chrome traffic is estimated at 40–55%.
In our new whitepaper, The End of Header Enrichment, produced with the support of MEF, we look at the scale of that exposure and the replacement options available to MNOs and DCB aggregators.
The billing still works. The identity step gets complicated.
Chrome 154 does not break carrier billing itself. It breaks the HTTP-based identity step that identifies the subscriber that’s making the purchase.
To verify the user with traditional header enrichment, the operator inserts the subscriber’s phone number into an HTTP request.
For it to work, that request has to remain unencrypted. But, the user does not have to register, enter their number or wait for a PIN. Identification happens silently, allowing the payment to be confirmed in two taps.
HTTPS encrypts that request end to end. It’s more secure but it also means the operator can no longer read or modify it, rendering the identification impossible.
The operators have to come up with a replacement – ideally one that doesn’t introduce too much friction because that’s where conversions start to suffer.
How much revenue is actually at risk?
It turns out: more than was initially expected.
On the DCB aggregator side, removing header enrichment means lower conversion rates on the flows that relied on silent identification. On the MNO side, it can also affect mobile wallets whenever onboarding, top-ups or payment authorization depend on that identity layer.
Moving on to numbers: across current estimates, the global DCB market is worth roughly $40–55 billion in 2026.
Let’s use a deliberately conservative model to calculate the revenue risk:
$50B DCB market × 60% header-enrichment dependence × 75% Chrome traffic × 40–55% conversion loss
That puts $9–12.4 billion in annual DCB revenue at risk if no HTTPS-native identity layer is in place.
It’s important to note that this is a directional model based on public inputs, not a revenue forecast. But even the conservative end makes the scale of the problem difficult to ignore.
There are several fixes. Time to deployment is a consideration.
The most obvious alternative for mobile operators is moving their users to PIN/OTP. Those flows are unaffected by the Chrome update, although they add significant friction and that’s exactly what we’ve been trying to avoid.
Then there is TLS ClientHello enrichment. This flow can be implemented in around four to six weeks, but it does depend on compatible network equipment, meaning availability and implementation can vary from one MNO to another. It also has a longevity problem: packet fragmentation can break the mechanism, while encrypted ClientHello is set to remove the visibility it relies on.
API IP lookup and private-IP resolution offer another HTTPS-native alternative, but require integration between the operator and individual partners and can take three to six months. That means more engineering and testing for every partner, more fragmentation across the ecosystem, and a much higher risk of losing large revenue portions.
Operators can also build their own HTTPS-native identification platform. Building the team and gateway, integrating the platform with the operator’s underlying co re network systems, and then running and maintaining it would take an estimated 6–18 months.
Another option is to keep the existing DCB flow and move the identity layer to HTTPS.
IPification’s GMiDBox HE over HTTPS works as an HTTPS reverse proxy inside the operator environment, obtaining subscriber information from the mobile network and enriching the request without changing the existing DCB flow.
For the DCB aggregator, nothing would change. The work that needs to be done happens on the operator side, so existing partners do not need to rebuild or reintegrate their flows. GMIDBox can be deployed in weeks, with low upfront engineering effort and CAMARA alignment out of the box.
So yes, there are several ways forward, but the timeline narrows the field significantly. Some of these approaches would take months, others require separate integration work for every partner, and with an in-house build, the conversion revenue lost while the platform is being built, integrated and certified may ultimately be more important than the development budget itself.
The real challenge is finding a solution that can be deployed fast enough without sacrificing the seamless user experience (and conversions) we’re trying to protect.
And solving that problem opens up another opportunity.
Build beyond the immediate DCB fix
The immediate job is keeping DCB working without replacing one narrow mechanism with another.
The direction outlined in the white paper is an HTTPS-native identity layer based on network-level SIM/IP identification, aligned with CAMARA.
And this is where the DCB problem becomes part of a bigger network API conversation.
If the operator is already replacing the infrastructure used to identify subscribers, there is little sense in building something that only solves one payment flow. Done properly, the same work leaves the operator with an identity layer it can build on later, without having to start from scratch every time another API use case comes along – and they will be coming up.
With that, the goal becomes solving the identity problem in a way that also creates a foundation for future network APIs.
What operators need to do now
The first step is to find out exactly where the exposure sits: which aggregators, merchants and wallet flows still depend on header enrichment, and how much transaction volume runs through them.
Then quantify the risk. Apply the conversion impact to your own traffic and Chrome share, and work out what every month of inaction could cost.
From there, the focus shifts to execution: choosing the deployment path, coordinating the required operator-side work, and making sure partners can move over without creating a new integration burden.
Chrome 154 is already here. At this point, the question is now how much conversion operators are willing to put at risk while they replace it.
Header enrichment stops working.
The revenue it enabled doesn’t have to.
For the full discussion on what the change means for DCB and operator identity: