What FY2025 numbers tell us about the embedded finance opportunity for tier-1 mobile.

An anonymous read of public FY2025 results from a tier-1 EU/CIS mobile operator — and what they imply for the next 36 months of embedded finance.

Why we read public results before pitching

Every senior CFO knows the awkward moment when a vendor walks in with a pitch deck full of generic claims — "15% revenue uplift", "30 million unbanked", "transformational customer experience" — and zero numbers from the operator's own annual report. The deck reads as if any operator in any geography could plug it in. None of the numbers are defensible. None of them survive a 30-second cross-check against the FY filings.

This essay does the opposite. It takes the published FY2025 results of an anonymous tier-1 mobile operator in the EU/CIS corridor — figures filed with auditors, reported to investors, and verified against public regulatory filings — and reads them as a CFO would. The aim is to derive what the embedded finance opportunity actually looks like for an operator of this size and profile, and what a credible 36-month plan should produce.

No operator names. No corridor names. The numbers are real; they are sourced from public investor materials, NBU statistics, World Bank diaspora data and standard EU mobile sector benchmarks.

The operating profile

The reference operator we draw on has the following published figures for FY2025:

This is not a small operator and it is not a stressed operator. The OIBDA margin is healthier than the EU mobile median (the European Big Four operate around 32–38%). Net Debt / OIBDA below 1× is conservative for the sector. CAPEX-to-sales at ~30% includes a billing-system replacement project — a once-in-a-decade event — meaning underlying CAPEX intensity is closer to 22%.

The conclusion from the operating profile alone: this is an operator with cash flow, balance sheet capacity and digital infrastructure to fund and ship a financial product without external capital. The constraint is not money. The constraint is regulatory perimeter and engineering throughput.

What the numbers say about the addressable opportunity

The most common analytical mistake is to multiply the subscriber base by an aspirational ARPU uplift and call it a "revenue opportunity". CFOs do not believe these numbers because the model assumes 100% attach. Real telco-fintech attach rates fall in a narrower band:

Applied to the operating profile above, with monthly app-active rate of ~40% (a defensible mobile-operator figure), the realistic attach math looks like this:

15.4M subs × 40% MAU × 60% wallet attach × $0.80 ARPU/month × 12
= ~$36M wallet revenue / year (Year 3)

15.4M subs × 28% xborder attach × $4.20 fee × 6 transfers/year
= ~$108M xborder revenue / year (Year 3)

15.4M subs × 40% MAU × 60% wallet × 30% card attach × $1.50 interchange/month × 12
= ~$20M card revenue / year (Year 3)

Total Year-3 fintech contribution: ~$165M

Against the published service revenue of ~€620M, that lands at a Year-3 uplift of roughly 23–28% on service revenue — and that is the floor, not the ceiling. Crucially, the OIBDA contribution is asymmetric: wallet and remittance revenue carry 70–85% gross margins because the variable cost is mostly transaction-processing, which is a fraction of telco network cost. The OIBDA-margin impact is therefore not dilutive. The operator can ship a fintech product and maintain its 50%+ OIBDA margin commitment to investors.

Why the cross-border corridor matters more than the wallet

Most embedded finance analyses lead with the wallet. The numbers above suggest a different priority order. For a tier-1 EU/CIS operator, the cross-border remittance corridor is by far the largest single revenue line in the realistic Year-3 model — and it is the most defensible against a CFO Q&A.

Three reasons.

First, the corridor revenue is non-cannibalising. Wallet revenue partially substitutes existing prepaid/top-up flows. Remittance revenue is incremental — the customer is already sending money home through Western Union, Wise, or informal channels. The operator is taking share from external providers, not from itself.

Second, the diaspora is large and its destinations are concentrated. Public migration registries show that the EU/CIS diaspora corridor of ~4–5M people sends roughly $9–11 billion home each year, generating $500–700M in transfer fees at current market rates of 5–7%. An on-net (sender-app to recipient-app) transfer can land at 1.5–2.5% — three to four times cheaper for the customer, four to seven times more profitable for the operator than card interchange.

Third, the regulatory path is shorter than for a full neobank. A wallet with a remittance license, passported into the EEA via a partner EMI, can be live in 90 days. A full neobank requires either a banking license (5+ years) or a deep BaaS dependency that the operator's CTO will not accept on critical-path.

The corridor is the wedge. The wallet, card and savings products plug into it in Wave-2 and Wave-3.

The CTO question — what about the billing system?

This is where most operator-led fintech projects die before they start. The CTO looks at the architecture diagram and sees a fintech vendor proposing to plug into the OCS / BSS / CRM stack — and immediately says no. The billing system is mission-critical. It runs the company's primary revenue engine. Touching it requires a 12-month change-management cycle and regulator notifications. A startup vendor with a 30-day promise sounds like a hostage situation, not a partnership.

The honest answer: fintech infrastructure should not touch the billing system on the write path. Period. Coreal subscribes to the billing event bus — read-only — receives charging triggers, plan-tier changes, recharge events, and posts to its own ledger in response. The BSS is never written to. The OCS is never modified. The integration can be reverted with a single configuration change because there is no schema migration, no stored procedure, no mainframe patch.

This is the difference between billing-replacement (which never happens at tier-1 operators) and billing-adjacent (which can ship in 30 days). Every embedded finance pitch that does not draw this distinction explicitly is hiding a future renegotiation.

The OIBDA-margin commitment

A tier-1 operator publicly commits to a 50%+ OIBDA margin floor in its investor presentations. Any embedded finance initiative that takes the margin below that floor is a non-starter — it does not matter how big the top-line opportunity is. The question is whether the fintech product can be delivered without OIBDA-dilutive cost.

The answer is yes — but only under specific structural conditions:

• Revenue-share, not capex. The fintech vendor takes a percentage of incremental revenue. The operator does not capitalise the platform. This keeps the build off the balance sheet and avoids the OIBDA hit from depreciation.
• Partner-bank licensing, not own-licence. Acquiring an EMI licence on operator balance sheet adds 18 months and a regulatory capital requirement. Partnering with an existing licensed bank or EMI keeps the operator out of the regulated perimeter — and out of the licensing capital draw.
• Read-only on BSS. Any cost incurred to integrate with the billing system needs to be variable, not fixed. Subscribing to an event bus is variable cost. Modifying the OCS is fixed cost — and is OIBDA-dilutive in the first 36 months.

When these three conditions are met, the embedded finance product behaves like a high-margin software business appended to the telco. OIBDA margin holds. Investor commitments hold. The CFO can present the numbers without retracting prior guidance.

What a 36-month plan should produce

We have walked the FY2025 numbers, the realistic attach rates, the corridor mathematics, the CTO objection, and the OIBDA constraint. The synthesis is a three-wave plan that is defensible to a CFO, signed-off by a CTO, and approvable by a Board:

Wave 1 — first 90 days. Cross-border remittance corridor, partner-bank licensed, billing-adjacent integration. One corridor, two destinations. KPI: 100k registered users, $20M in cumulative volume, single-digit-percent take rate.

Wave 2 — month 4 to month 12. Wallet and virtual debit card, plugged into the same partner-bank licence. Card-on-file functionality for utilities and recurring telco charges. KPI: 1M wallets, 250k active cards, 20% attach to monthly app users.

Wave 3 — month 12 to month 36. Investment and savings products under MiCA-and-MiFID-light wrappers. Cross-border B2B SME flows for diaspora-led businesses. KPI: 500k investing users, 50k SME accounts, 20–28% Year-3 uplift on service revenue.

Across all three waves, the OIBDA-margin floor of 50%+ is preserved, the billing system is never touched on the write path, and the operator retains brand ownership and customer relationship. The fintech vendor — Coreal — delivers the regulated infrastructure, the licensed entity, and the engineering throughput. The operator delivers the brand, the distribution, and the trust.

The defensible conclusion

The FY2025 results published by tier-1 EU/CIS mobile operators show three consistent patterns: ARPU is low and rising, OIBDA margins are strong and protected, and digital infrastructure (eSIM via national e-ID, self-service penetration above 70%) is mature enough to support a financial product without re-platforming. The operating profile says yes. The diaspora-corridor data says yes. The unit economics — wallet, card, and especially cross-border — say yes.

What the numbers do not say is that any vendor can deliver this. The combination of EU EMI passport, telco-billing-adjacent integration, war-resilient ops, and a regulatory perimeter that the operator's compliance team can defend on Day 1 — that combination is not common. There are perhaps five vendors in EU/CIS who can credibly bid on a project of this scope without taking the operator below its OIBDA commitment.

If you are reading the FY filings of a comparable operator and recognising the profile, the next 18 months matter. The first mover into the diaspora corridor takes the volume — and the unit economics — and the brand. The second mover takes whatever is left.

Numbers in this article are derived from anonymous public sources: NBU statistics, World Bank Remittance Prices Worldwide, EU mobile sector reports, and the FY2025 financial results of a single tier-1 EU/CIS mobile operator. No operator names appear in this analysis and no commercial relationship is implied.