What a bank brings and what a telco brings — and why neither is enough alone.
A structural analysis of capital, distribution, license and the ledger that joins them.
The problem with the word "synergy"
Synergy is a word that gets used when two parties want to announce a partnership without being specific about what they are actually doing together. In fintech, "bank-telco synergy" has been a press release phrase for fifteen years. The first wave produced wallets that nobody used, APIs that went nowhere, and branded products that died when the relationship soured.
The reason most of those partnerships failed wasn't distribution or technology. It was that neither side understood what the other side actually brought — structurally, contractually, legally — and neither side had built the thing that sits between them. That thing is the ledger. That thing is Coreal.
What a bank actually brings
A bank has three things that are almost impossible to build: a license, a capital base, and a regulator relationship. The license alone takes two to five years and costs between £500k and £3M to obtain in most EU markets. Once you have it, you have access to payment scheme membership, IBAN issuance, card issuing rails, safeguarding accounts, and correspondent banking relationships. You can hold customer funds legally.
The capital base matters for a less obvious reason: safeguarding. Under EU EMI regulations, you must hold customer funds in a ring-fenced account, segregated from operating capital. A telco without a banking license cannot hold customer funds — full stop. Every wallet you have seen that 'worked' was sitting on top of a licensed partner behind the scenes. The telco was the brand; the bank was the foundation.
A bank's license is not an asset you can buy. It is a permission structure — for what you can hold, what you can issue, what schemes you can join, and what you have to prove to a regulator on demand.
What a telecom operator actually brings
A tier-1 telecom operator in a medium-sized market reaches 10–20 million subscribers. A meaningful fraction — often 40–60% — opens the telco app at least once a month. More importantly, the telco already has a billing relationship with each of those customers. They pay every month. The telco knows when they last recharged, what device they use, whether they have been roaming, and whether they have ever missed a payment.
That billing relationship is the single most underrated asset in fintech. A challenger neobank spends £30–150 in customer acquisition cost per activated account. The telco already has an authenticated, verified, monthly-paying user. The problem the telco has is that it cannot turn that relationship into a financial product without a license. It can offer a top-up wallet under certain regulatory interpretations — but it cannot offer a card, an IBAN, a savings account, a credit product, or a cross-border transfer without either obtaining a license or partnering with someone who has one.
The structural gap: why neither builds this alone
Banks have started trying to build fintech products internally. The success rate is low, and the reason is almost always the same: a bank's engineering culture is optimised for reliability and audit, not for product velocity. Banks are good at being banks. They are not good at building the telco-aware wallet experience that a 22-year-old expects when they open their phone.
Telcos, meanwhile, have built wallet products. Orange Money, Vodafone M-Pesa, a dozen others. These work — in markets where the alternative to a wallet is no banking at all. In markets where there is already banking infrastructure, a telco wallet that cannot offer a debit card, a savings yield, a cross-border transfer or an IBAN cannot compete with the existing banks, let alone with the neobanks.
The gap between what each side brings and what a modern embedded finance product requires is not small. It is the entire ledger layer, the entire workflow engine, the entire compliance and KYC stack, the entire card and IBAN issuance infrastructure, and the entire provider gateway. That is Coreal.
The ledger as the joining layer
The ledger is not an accounting afterthought. In a properly built financial system, the ledger is the primary system of record. Every event — every top-up, every card auth, every SEPA transfer, every KYC check, every AML flag — is a posting. The ledger is the source of truth that a regulator will ask to see. It is what your reconciliation runs against. It is what your audit firm reviews.
When a telco and a bank try to build together without a shared ledger, what they get is two separate ledgers with a synchronisation problem. The bank's core banking system records what it sees. The telco's billing system records what it sees. And somewhere in the middle there is a settlement reconciliation that runs at T+1, T+2, or T+3, and produces a delta file that ops teams spend their lives trying to zero out.
Coreal's ledger is the joining layer. Bank, telco, and product events all post to the same double-entry structure in real time. The reconciliation delta is zero — not by design of a reconciliation process, but because there is no gap to reconcile.
What a working JV structure looks like
The structure we have seen work is: the bank provides the license and the regulated entity. The telco provides the distribution and the customer relationship. Coreal provides the ledger, the BPM engine, the KYC/KYT stack, the provider gateway, and the operator workspace. The commercial structure is a joint venture, with revenue pools divided by contribution: card interchange, wallet fees, autopay margin, FX spread.
Time to Wave 1 — the first production flows, typically wallet top-up and autopay integration — is 90 days when all three parties have their responsibilities clearly separated. The bank does not try to build the product. The telco does not try to get a license. Coreal does not try to be the brand. Each side brings what only it can bring.
The partnerships that fail are the ones where the telco decides it wants to own the stack, or the bank decides it wants to own the customer, or neither side names what sits between them. The thing that sits between them has a name: the control plane.