Boku’s Payment Volume Surge Signals Local Rail Opportunity

TL;DR: Boku posted $8.6 billion in H1 2026 payment volume — up 16% — while its Stripe partnership opens local payment method access to a new merchant tier. New product chief Karim Ahmad, ex-Trustly and Paysafe, arrives October 1. For operators in iGaming, forex, and crypto, this signals that the fragmented local payments problem is being consolidated at the infrastructure layer, and acquisition strategies need to account for it now.

The Numbers Behind the Headline

Boku’s reported H1 2026 revenue landed at $66.5 million, up 5% from $63.3 million a year earlier. That headline number, however, carries a distortion: H1 2025 included $3.4 million in one-off launch pricing that was never going to repeat. Strip that out and underlying revenue growth was 11%, from $59.9 million to $66.5 million.

Adjusted EBITDA came in at $19.6 million on an underlying basis, up 7%, with a margin of 29.4% — slightly down from 30.6% a year ago. Profit before tax rose 20% to $12.8 million. Total payment volume reached $8.6 billion, compared to $7.4 billion in H1 2025. Volume is clearly growing faster than revenue: the blended take rate fell 4 basis points to 77 bps on an underlying basis, which is the mathematical outcome when you add volume at lower price points.

For operators evaluating payment infrastructure partners, the take rate compression matters. It means Boku is prioritizing network scale over margin expansion right now. That is a deliberate choice, and one that tends to pay off when the network effects compound.

Stripe Partnership Opens a New Distribution Layer

The most operationally significant development in this report is not the revenue number — it is the Stripe partnership. Boku’s first channel deal means Stripe merchants can now accept selected local payment methods through Boku’s network. The first merchants are already live.

This matters because Stripe has deep penetration across e-commerce, SaaS, and digital services. Routing local payment method access through Stripe’s merchant base gives Boku a distribution channel it did not build itself. For operators who already process through Stripe infrastructure, this is a concrete reason to revisit which local rails are now accessible without a direct Boku integration.

Boku also processed its first transactions on Brazil’s PIX and India’s UPI during the half. Both are government-backed instant payment rails with enormous transaction volumes and near-zero marginal cost per transfer. Getting live on those rails — even at initial scale — is a signal of where the company’s geographic expansion priorities sit.

Segment Breakdown: Where the Growth Actually Is

Direct carrier billing (DCB) — charging purchases directly to a mobile phone bill — grew 3% to $35.3 million and still accounts for more than half of total revenue. It is the legacy core of the business, and 3% growth at that base size is stable, not exciting.

The more interesting line is bundling, which climbed 39% to $9.2 million. Boku served 51 million subscribers in this segment, up from 42 million a year earlier. Bundling ties Boku’s payment network into carrier subscription services — a recurring revenue model with low churn. That 39% growth rate on an expanding subscriber base is the fastest-moving part of the business.

Digital wallets and account-to-account payments reached $22.0 million, up 15% on an underlying basis. The reported figure came in slightly below the prior year’s $22.5 million because the one-off pricing from H1 2025 fell into this segment. Adjusted for that distortion, wallet revenue is growing at a healthy pace, which aligns with global consumer behavior across every high-growth digital market.

During the half, Boku added 10 local payment methods and 47 new payment connections across 14 merchants. That is the kind of methodical network expansion that makes the platform more defensible over time.

Operational Friction: Delays and Suspended Connections

Not everything ran smoothly. One key merchant had planned market launches slip from H1 into H2 because of a dual-sourcing policy — the merchant was hedging across multiple payment providers before committing. Boku says all affected markets are now live. The merchant was not named.

Local authorities in one unnamed country also suspended two of Boku’s direct carrier billing connections. Boku confirmed it has no remaining exposure in that market. Two suspended connections out of a network this size is not material, but it is a reminder that DCB operates in a regulatory environment where local telecom regulators have real power to interrupt service.

Group cash fell to $186.8 million from $245.6 million at December year-end. Boku attributed this to seasonal unwinding of December balances, dual-sourcing settlement dynamics, and share buybacks. The company repurchased 9.5 million shares for $23.6 million in the half. Own cash (excluding merchant float) stood at $84.6 million, down from $102.9 million.

New Product Chief: What the Hire Signals

Karim Ahmad joins as chief product officer on October 1, replacing Adam Lee, who held the role for 15 years and is moving to an advisory position. Ahmad’s background is a deliberate signal about where Boku’s product roadmap is headed. He was previously chief product and technology officer at Trustly, CPO at Paysafe, and EVP of global product and innovation at TSYS. Most recently, he advised payments businesses at Bain and Company.

Trustly is an account-to-account payment specialist with significant presence in regulated gambling markets across Europe and North America. Paysafe runs a network of digital wallets and pay-by-cash options used heavily by iGaming operators. TSYS is a card processing giant with merchant acquiring operations at global scale. Ahmad has held senior product roles at all three. That is not a coincidence — Boku’s CEO Stuart Neal has explicitly said the company’s goal is to turn “the complexity of fragmented local payment systems into a platform for growth” for the largest merchants. Ahmad is the hire you make when you want to productize that complexity, not just survive it.

What This Means for High-CAC Vertical Operators

Operators in iGaming, forex, and crypto spend real money acquiring depositing users. When a player or trader hits a deposit screen and their preferred local payment method is not available, they do not switch methods — they leave. That abandoned deposit is a lost customer acquisition cost with no return.

Boku’s network expansion — PIX in Brazil, UPI in India, 10 new local payment methods in a single half — directly addresses this. iGaming acquisition campaigns targeting Brazil or Southeast Asia need to account for whether the platform’s payment stack supports local rails at checkout. If it does not, the best media buying in the world does not recover the lost deposit rate.

The same logic applies to forex broker lead generation in emerging markets. A trader acquired through paid search or paid social in India who hits a deposit wall because UPI is not supported is a wasted CPL. Crypto exchange acquisition teams in LatAm face the same issue with PIX. Payment method coverage is a conversion rate problem before it is a payment operations problem.

For operators who have not audited where payment friction is killing post-click conversion, a full marketing audit should include checkout flow analysis alongside media efficiency metrics. Paid media management that stops at the click and does not track through to first deposit is measuring the wrong thing. And for operators scaling into new geographies, geo-level precision targeting needs to be paired with payment method availability mapping — otherwise you are buying traffic you cannot monetize.

Boku’s full-year guidance of $135 million to $142 million in revenue and $38 million to $42 million in adjusted EBITDA implies second-half acceleration. The medium-term target remains 20%-plus organic revenue growth with 30%-plus EBITDA margins. The company is not there yet, but the infrastructure is being built to get there.

Originally reported by Finance Magnates, September 2026.