Most discussions of mobile payment technology centre on the obvious players: Apple Pay, Google Pay, PayPal, the major card networks. There is, however, a parallel payment infrastructure that handles billions of pounds in transactions every year and operates almost entirely below the consumer-facing layer most people interact with. It is called direct carrier billing, often abbreviated as DCB, and it is the technology behind pay-by-phone payments.
Direct carrier billing is one of those technologies that has matured quietly while attention focused elsewhere. It uses telecom network infrastructure rather than the card networks, it processes transactions through the SS7 and Diameter signalling protocols that have been part of mobile networks for decades, and it has become a strategically significant payment rail in markets where smartphone penetration is high but card or banking infrastructure is patchy.
This piece walks through how direct carrier billing actually works under the surface, the security model it operates within, and where the technology is being used today.
The Architecture in Plain Terms
In a card payment, the merchant connects to an acquiring bank, which routes the transaction through Visa or Mastercard to the cardholder’s issuing bank, which approves or declines based on available credit. The whole journey takes seconds and crosses multiple commercial entities, each taking a small fee.
Direct carrier billing replaces all of that with a single connection between the merchant’s payment processor and the user’s mobile network operator. The merchant submits a billing request keyed to the user’s phone number. The network operator authenticates the user, typically through a short-code SMS verification, and either adds the charge to the user’s monthly bill or deducts it from prepaid credit. The transaction settles between the merchant and the network operator on a delayed basis, similar to traditional billing settlement.
The technical advantage is simplicity. There is no card to enter, no payment app to maintain, no merchant account in the traditional sense. The phone number itself is the payment credential. The disadvantage is that the network operator becomes a critical dependency, and operator coverage limits define the geography of the payment method.
Authentication and the Two-Channel Model
DCB systems use a two-channel authentication model that pre-dates most modern app-based two-factor authentication schemes. The user initiates a transaction in one channel, typically a mobile browser or app, and confirms it in another channel, the SMS network. The two channels are technically independent and use different authentication paths.
This produces a security profile that is meaningfully different from card-not-present transactions. A stolen card number can be used remotely with no further verification beyond the CVV; an attacker who has compromised a user’s email or browser session cannot complete a DCB transaction without also having access to the user’s SIM, since the SMS confirmation is required.
The model is not without weaknesses. SIM swap fraud, where an attacker convinces a network operator to transfer a victim’s phone number to a SIM the attacker controls, has emerged as the most significant threat vector. Network operators have responded with stricter SIM swap procedures, but the underlying vulnerability of phone number based authentication remains an industry concern.
Where DCB Has Found Product-Market Fit
Direct carrier billing has not displaced cards or e-wallets as a general-purpose payment method. Where it has thrived is in specific use cases where its particular trade-offs are well-suited to the underlying transaction pattern.
Digital content micro-purchases were the original killer app. App stores, ringtone services, and mobile-first content platforms found that DCB removed the registration friction that killed conversion on small-value purchases. Apple, Google, and Microsoft all support DCB on their respective stores in markets where the technology is operationally available.
Online gaming, including the regulated UK casino sector, has become another significant DCB use case. The method’s £30 to £40 daily transaction caps are well-suited to small recreational deposits, and the absence of card details has both convenience and security benefits for users transacting on mobile networks. Pay-by-phone deposits, available at sites like PlayUK, route through the major UK DCB providers and settle through the user’s network operator. The UKGC’s regulatory framework requires withdrawals to be made via a separate registered method, which gives DCB a deliberately one-directional payment role in this context.
Subscription services, parking apps, and charity donations have also found DCB useful for the same reasons. The unifying theme is small transaction sizes, mobile-first user contexts, and a need to minimise friction at the point of payment.
UK Provider Landscape
| Provider | Daily Cap | UK Networks | Typical Use |
|---|---|---|---|
| Fonix | £40 | EE, O2, Vodafone, Three, Virgin | Gaming, charity, transit |
| Payforit | £30 | All major UK networks | Digital content, gaming |
| PayViaPhone | £30 | Major UK networks | App stores, gaming |
| Boku | £30 | Global; UK availability varies | Subscriptions, app stores |
UK direct carrier billing is overseen by the Phone-paid Services Authority (PSA), which sets the regulatory framework for premium-rate and DCB transactions. The £240 monthly cap that applies across all DCB providers combined is a PSA-set limit, intended to prevent the channel from becoming a vehicle for unmanaged spending. According to Ofcom’s Communications Market Report, UK mobile network coverage now reaches more than 99% of the population, which means DCB availability is effectively universal for any UK consumer with a contract or PAYG SIM on a major network.
The Geographic Story
Direct carrier billing has a geographic distribution that reflects the underlying telecom infrastructure of different markets. In countries where card and banking penetration is high, DCB tends to be a niche method used for specific content categories. In countries where mobile network coverage outpaces card or banking infrastructure, DCB has become a primary payment rail for substantial parts of the digital economy.
Across much of South and Southeast Asia, sub-Saharan Africa, and parts of Latin America, DCB and adjacent mobile money systems handle a meaningful share of digital payments. The pattern correlates strongly with operator-driven mobile network rollout that arrived ahead of widespread card or banking deployment, leaving the phone number as the most universally recognised consumer credential.
The underlying technical architecture, the SS7 signalling networks and the operator billing systems that DCB depends on, is the same global infrastructure used for SMS, voice calls, and roaming. This means a DCB platform built in one country is technically deployable elsewhere with relatively limited operator-by-operator integration work, which has driven significant cross-border consolidation among the major DCB providers.
Limitations and Open Issues
DCB is not a general-purpose payment solution and is not trying to be. The transaction caps, set by regulators in most major markets, mean it is unsuited to high-value purchases. The one-directional nature of the technology, deposits in but no withdrawals out, makes it a deposit channel rather than a full account funding mechanism. The dependency on phone number based authentication remains a real concern in an era of growing SIM swap fraud.
There are also the structural questions that DCB has not yet answered. Most network operators take meaningful margin on DCB transactions, which makes it a higher-cost method for merchants compared to direct card payments. The settlement timing, which can be 30 to 60 days from transaction to merchant settlement, is a working-capital headwind for smaller merchants. Cross-border DCB transactions remain operationally complex despite the underlying technology being technically capable of supporting them.
These constraints have kept DCB as a strategically important but specialised technology rather than a mainstream payment method in markets with strong card infrastructure. They have also kept the field competitive, with the major DCB platforms continuing to invest in better security, faster settlement, and broader operator coverage as differentiating features.
A Quietly Important Layer of the Stack
Direct carrier billing is one of the technologies that operates as part of the infrastructure most users never think about. The pay-by-phone option that appears at checkout on a mobile site is the consumer-facing surface of a globally interconnected stack of telecom protocols, operator billing systems, and regulatory frameworks that have been built up over more than two decades.
For tech-aware audiences, the interesting layer is everything beneath that surface: the SS7 message routing, the operator authentication paths, the regulatory caps, the settlement networks, and the geographic distribution that mirrors mobile network coverage rather than financial infrastructure. The technology is not flashy, but it has quietly become a meaningful part of how digital commerce works on mobile.
Responsible Use Note
Direct carrier billing makes payments fast and frictionless, which is a feature in some contexts and a consideration in others. For use cases involving recreational gaming or gambling, the convenience of DCB combined with the relatively small transaction caps can mask cumulative spend over time. UK-licensed operators are required to provide deposit limits, session reminders, and self-exclusion tools. Setting personal deposit limits within a casino account, in addition to the regulatory PSA caps, is sensible practice.
BeGambleAware offers free support and information at begambleaware.org. The National Gambling Helpline is available 24 hours a day on 0808 8020 133. GamStop national self-exclusion is available at gamstop.co.uk and applies across all UKGC-licensed operators.