Carrier billing consolidation: how studios should pick a DCB partner

Direct answer — What does carrier billing consolidation mean for a studio choosing a DCB provider? The direct carrier billing (DCB) aggregator layer has spent a decade folding into fewer, larger platforms: Bango bought Danal’s US BilltoMobile service in 2016, Boku bought Danal Inc. and Fortumo, and Bango took over DOCOMO Digital in 2022. For a game studio, that means fewer vendors to compare, deeper operator coverage per contract, and a real concentration risk if one aggregator carries all your phone-bill revenue in a market. Pick a partner on owned connections and contract protections, not on the length of its operator list, and dual-source your biggest markets.

One correction before anything else, because it shapes how to read the topic. The Bango–BilltoMobile deal is often quoted as if it were fresh news. It is not: Bango announced it on 9 May 2016. What makes it worth revisiting in 2026 is the pattern it opened, and what that pattern means for whoever signs your carrier billing contract today.

This piece is about the vendor landscape, not the payment method itself. If you need the case for DCB first, start with why carrier billing converts where cards fail; if you need to know which countries to switch on, read our 2026 carrier billing reach map.

What did Bango actually buy with BilltoMobile?

Bango bought operator integrations and contracts, which is the scarce asset in this business. Bango paid an initial consideration of $3.5m for the US carrier billing service of Danal Inc.: $3m in cash and $500,000 in Bango shares. In exchange it took on a service that, by Bango’s own figures, processed approximately $80m of end-user spend in 2015, and which Bango described as “the largest carrier billed payments processor in the US by volume.”

The strategic prize was coverage. Bango said the deal made it “the only processor of carrier billing transactions across all four major U.S. mobile network operators”, reaching more than 300 million connected devices. Digital Transactions named those four networks at the time: AT&T, Sprint, T-Mobile and Verizon. The same trade report opened with the line that “the direct carrier billing business has been consolidating for the last few years”, noting earlier Boku acquisitions such as mopay.

Read that as an operator would. A carrier billing connection is slow to build: commercial negotiation with each mobile network operator, technical certification, fraud controls, settlement terms. Once it exists, it changes hands cheaply. A few million dollars bought coverage of every major US network. The value sits in the connections, and the connections follow whoever buys them. That is why we treat the aggregator choice as part of distribution planning, next to stores, OEM channels and web shops, rather than as a payments afterthought.

How far has the DCB aggregator layer consolidated since?

The deals since 2016 keep pointing at the same two names, Bango and Boku, absorbing specialists and the exits of larger parents.

Date	Buyer	Asset	What the buyer’s own filing says
May 2016	Bango	BilltoMobile (Danal Inc.’s US carrier billing service)	$3.5m initial consideration; approximately $80m end-user spend in 2015
1 January 2019	Boku	Danal Inc., renamed Boku Identity Inc.	Mobile identity and compliance services, predominantly in the United States
1 July 2020	Boku	Fortumo, a direct carrier billing company	Maximum enterprise value of $41.0m; $114m of Boku’s 2020 processed value came from Fortumo
29 August 2022	Bango	Global payments business of NTT DOCOMO (DOCOMO Digital)	Gross consideration of €4M; over $3.5B of end-user spend (measurement period not stated by Bango); telco partners including Telefónica, América Móvil and Deutsche Telekom

Two observations matter for a buyer of these services. First, Danal’s US business went through both consolidators: the carrier billing service to Bango, then the company itself to Boku as an identity business. Second, the DOCOMO Digital deal shows a telco group exiting the aggregator role and selling it to a specialist. Bango also signed a long-term agreement with NTT DOCOMO to provide carrier billing and wallet integration services in Japan, so the operator became a customer of the platform that bought its unit.

None of this means the rail is shrinking. Juniper Research’s March 2026 forecast puts the global value of DCB transactions at $51 billion in 2026, rising to more than $87 billion in 2030. That figure covers all DCB transactions worldwide, not games alone. The point is narrower: more value flows through a layer controlled by fewer intermediaries.

What changes for a studio’s negotiating position?

Consolidation cuts both ways, and the trade-offs are easier to see side by side.

Dimension	What consolidation gives you	What it costs you
Coverage	One contract can reach operators across many markets	Breadth on a slide hides whether each link is direct or resold
Leverage	A large platform has more weight with operators on approval and fraud rules	Fewer credible alternatives when you negotiate your own rate
Integration	One SDK or API, one settlement and reporting flow	Migration risk each time the platform absorbs another stack
Concentration	Simpler vendor management	One commercial or regulatory event can switch off a market

The concentration line is not theoretical. Boku’s trading update for the first half of 2026 names “the suspension of two Direct Carrier Billing connections by local authorities in a single market” as one reason it cut its full-year outlook. A connection can disappear for reasons neither you nor your aggregator controls. If that connection is your only phone-bill route in that country, your DCB revenue there stops with it.

The same update shows how large merchants answer that risk: “A key merchant’s move to dual sourcing reduced Boku’s share of volume in one market.” That is the move a studio with meaningful DCB volume should copy in its top markets. It costs a second integration; it buys continuity and a price reference.

Boku’s update also records its first contract with Stripe, “a major global Payment Service Provider (PSP)”, with two merchants already live through it. For smaller studios this matters more than any acquisition: DCB is increasingly reachable through a payment provider you may already use for your web shop, which changes who you negotiate with. Map these routes against your full channel plan before you pick a direct aggregator by default.

Which questions should you ask a DCB partner before signing?

The questions below separate a robust partner from a long operator list. Ask them in writing, market by market, for the countries that will carry most of your revenue.

1. Is each connection direct or via a sub-aggregator? A direct contract with the operator means fewer parties taking a cut and fewer points of failure. A resold link means you inherit someone else’s contract.
2. Which connections came through an acquisition, and are they migrated? After a deal, platforms run legacy and new stacks in parallel for a while. Ask for the migration status and the date any legacy endpoint will be retired.
3. What happens when an operator or a regulator suspends a connection? Ask for the notice you will receive, the fallback route, and whether any minimum commitment is waived while the route is down.
4. How does settlement work per operator? Payout timing, currency, refund and chargeback handling, and who carries fraud losses all vary by operator. Get the matrix, not an average.
5. What anti-fraud tooling sits on the network side? Juniper’s 2026 forecast argues operators must deploy standardised anti-fraud APIs to keep DCB competitive with digital wallets, and that high API call costs can erode the benefit for merchants. Ask whether fraud screening uses network signals, and who pays for it.

Then write the answers into the contract. The clauses worth fighting for:

• Change of control: notice, and a right to terminate without penalty, if the aggregator is acquired or sells the business serving your markets.
• No exclusivity, or exclusivity limited to markets where the partner holds direct connections.
• Migration protection: advance notice and integration support at the vendor’s cost when it moves you to a new stack.
• Data and termination assistance: transaction history, subscriber references and a wind-down period so you can move volume to a second provider.

What should a studio do next?

Start from your revenue map, not from the vendor’s coverage map. List the markets where phone-bill payments carry or could carry a meaningful share of your spend. Note that inside Google Play and the App Store, carrier billing is the store’s checkout, not your contract; our MENA distribution playbook shows how that works operator by operator. Your own DCB partner choice applies to the routes you control: web shops, alternative stores and OEM storefronts.

For those routes, shortlist two providers per priority market, run the five questions above, and sign with one primary and one secondary in your top one or two markets. Re-run the questions whenever your provider announces a deal. In this layer, the next acquisition is a question of when, and your contract should already say what happens to you.

FAQ

When did Bango acquire BilltoMobile?

Bango announced the acquisition of BilltoMobile, the US carrier billing service of Danal Inc., on 9 May 2016. The initial consideration was $3.5m, made up of $3m in cash and $500,000 in Bango shares. It is a 2016 deal, not a recent one, but it set the pattern for the consolidation that followed.

Who are the main consolidators in direct carrier billing?

The recurring buyers in the deals reviewed here are Bango and Boku. Bango bought BilltoMobile in 2016 and NTT DOCOMO’s global payments business in 2022; Boku completed the acquisitions of Danal Inc. on 1 January 2019 and of Fortumo on 1 July 2020.

Should a game studio use more than one carrier billing provider?

Yes, in the one or two markets where phone-bill payments carry real volume. Connections can be suspended by local authorities, as Boku reported for two connections in a single market in its first-half 2026 trading update, and large merchants already dual-source to manage that risk.

What contract clauses matter most with a DCB aggregator?

Change of control, limits on exclusivity, migration protection when the vendor moves you to a new platform, clear notice and fallback when a connection is suspended, and termination assistance with your transaction data. Settlement timing and fraud-loss allocation should be stated per operator.

---

If you are weighing carrier billing partners for a web shop, an alternative store or an OEM channel and want a second opinion on coverage and contract terms, talk to our distribution team. Early-stage studios can also apply to the Founding Developer Program.