At an online checkout, TrueLayer would prefer that you forget sixteen digits you never truly memorised. Choose Pay by Bank, pick your bank, approve with a face or fingerprint, and the money travels directly from account to account. There is no card number for the merchant to store, no separate wallet to install and, in the cleanest version of the journey, no form to type. The experience looks simple because the difficult parts - bank connectivity, regulation, authentication, payment status and reconciliation - have been pushed behind one integration.
That is the useful way to understand TrueLayer. It is a regulated translation layer between the uneven machinery of European banks and the tidy interfaces that merchants and software developers want. Its customers are not people opening a TrueLayer current account. They are businesses such as Revolut, eBay, Coinbase, Trading 212, Nutmeg, Smarkets and bet365, which insert TrueLayer into account linking, deposits, checkouts, refunds, withdrawals or onboarding. Consumers encounter the service as a button inside somebody else's product.
The bank keeps the login. TrueLayer carries permission, instructions and confirmation between the checkout and the banking system.
Six months to a demo, twelve to a customer
TrueLayer began in 2016, just as UK and European rules were prying open bank systems to regulated third parties. Co-founders Francesco Simoneschi and Luca Martinetti had met at school in Rome at 14, bonded over computers and already built and sold companies together. When Britain announced its open-banking initiative, they moved to London. Their initial thesis was developer-shaped: complicated financial services could be exposed as simple code.
The first product was a data API. It took about six months to put in front of developers and roughly a year to produce a paying customer. That pace is more instructive than the later unicorn headline. The pair entered before the market was settled, when bank implementations varied and the idea that a software company should sit between banks and apps still needed explaining. TrueLayer's early job was to absorb the inconsistency so a fintech could connect accounts, retrieve balances and read transaction histories without maintaining hundreds of bank-specific integrations.
Revolut shows how the wedge widened. It first used the Data API to let customers connect external bank accounts. It later added the Payments API so users could top up directly from those accounts rather than wrestle with manual transfers or card fees. Revolut reported twice as many weekly active users, more than £1 billion in payment volume and account verification in under two seconds in TrueLayer's case study. The product was no longer just fetching information. It was moving money.
“When our customers say it’s easy to connect accounts using TrueLayer, that’s a huge tick for us.”Joshua Fernandes, then Revolut open-banking product owner
The first thing to fail was repetition
Single bank payments proved the rail could work. Repeating them exposed the limit. Open-banking rules made one-off account-to-account payments possible, and later enabled “sweeping” between accounts held by the same person. They did not initially give merchants the flexible recurring charges that cards had normalised. That meant Pay by Bank could handle a deposit or purchase but not every subscription, utility bill or one-click return visit.
This missing repeat button changed the ambition. TrueLayer had started by aggregating APIs; it came to describe itself as a network. That required merchant accounts, hosted and embedded checkout pages, mobile SDKs, instant refunds, payouts, verification, retries, routing and reporting. In 2026, after banks and fintechs agreed a commercial variable-recurring-payments framework, TrueLayer launched Bank on File. The deliberately plain name translates policy jargon into a familiar promise: link a bank once, then permit future payments within limits.
The technical distinction is sharp. A card-on-file arrangement stores a reusable credential that can expire or be stolen. Bank on File stores programmable consent. A customer specifies what a merchant may charge, and authentication remains tied to the bank. The first launch covered firms including Trading 212, IG Group, InvestEngine and East Lothian Housing Association. Wider subscriptions and one-click ecommerce still depend on bank participation and the rollout of later commercial phases.
The expensive middle chapter
Payments infrastructure is a costly way to discover whether shoppers will change a habit. TrueLayer has raised at least $321.8 million in disclosed funding. A $130 million Series E led by Tiger Global, with Stripe participating, valued it above $1 billion in 2021. Three years later, a $50 million extension led by Northzone reportedly reset that valuation to roughly $700 million. Around the same period, the company reduced operating costs and headcount; reporting put the September 2024 reduction at 71 roles.
The underlying business was growing, but not cheaply. TrueLayer reported 2024 group revenue of £20.3 million, up 63 percent, gross profit of £14.2 million, up 82 percent, and £46.4 million of year-end cash. Its 2025 summary said payment volume rose 52 percent and revenue 39 percent while operating cash outflow fell 27 percent. Management's diagnosis was candid: 2025 carried the cost of building the network; 2026 was supposed to begin showing the return.
Revenue kept climbing through the reset
Indexed to 2023. The 2024 bar reflects reported 63% growth; 2025 applies the reported 39% increase to that base.
Merchants buy that infrastructure through negotiated commercial contracts rather than a public production price card. TrueLayer markets Pay by Bank fees as potentially up to 50 percent lower than cards, alongside instant settlement and lower exposure to card chargebacks. Those are sales claims, not a universal tariff. The actual arithmetic changes with transaction value, card mix, geography, fraud profile, refunds, integration work and the share of customers willing to choose the bank option.
Two acquisitions complete the checkout
TrueLayer's 2026 acquisitions reveal what “network” now means. Zimpler brought Nordic bank coverage, regional merchant relationships and millions of consumers. Dutch fintech in3 brought account-to-account buy-now-pay-later. With the second deal, TrueLayer could offer shoppers debit or credit through the same Pay by Bank experience. The company says in3 serves millions of consumers and thousands of merchants; it plans longer-duration credit products after BNPL. Neither acquisition had a disclosed price.
This puts TrueLayer in several contests at once. Plaid, Tink and Yapily also aggregate open-banking connections. Trustly and GoCardless compete in bank payments. Stripe distributes a broad suite of payment methods and is also a TrueLayer investor and partner. Above them sit Visa and Mastercard, the networks TrueLayer ultimately wants merchants to rely on less. TrueLayer's distinction is the attempt to package data, verification, deposits, payouts, recurring consent and now credit in one European bank-rail system.
The customer list has accordingly moved beyond fintech. eBay introduced TrueLayer's Pay by Bank at UK checkout in February 2026, while eBay Ventures invested an undisclosed amount. Stripe uses TrueLayer for UK Pay by Bank distribution and worked with it on Kustom Checkout in Finland. In regulated sectors, Signup+ combines registration, account verification and a first deposit; Verified Payouts checks that a withdrawal returns to the account used to fund it. TrueLayer says the latter reaches a 99.7 percent payout success rate for returning users.
“The first 10 years were assembling the network.”Francesco Simoneschi, co-founder and CEO
The useful bits are surprisingly ordinary
There is a copyable playbook here, even for companies that will never touch a banking licence. Start with one expensive abstraction problem. Let customers test it before the category language settles. Translate the infrastructure into the job people recognise. TrueLayer moved from “payment initiation” to “Pay by Bank,” and from “commercial variable recurring payments” to “Bank on File.” The names describe an action, not a regulation.
Normalise the messy supplier layer once, then give every customer the same integration and status model.
Lead with settlement, conversion, fraud and reconciliation. Infrastructure terminology belongs in the documentation.
The bank controls authentication, so measure each screen and route instead of treating the external step as a black box.
Data led to payments; payments exposed the need for payouts, recurring consent and credit. Each layer followed a visible gap.
The limits are equally practical. Pay by Bank works best where open-banking rules are mature, bank coverage is broad, mobile authentication is good and users already trust their banking apps. It is less persuasive for offline purchases, markets with patchy bank APIs, shoppers attached to card rewards, or transactions where familiar card disputes and global acceptance matter most. A merchant that buries the option, labels it with regulatory jargon or serves mostly first-time desktop users will not inherit TrueLayer's best conversion figures merely by adding an API.
The company still has to prove that impressive volume becomes durable profit and that a bank button can become a default rather than a backup. Yet its decade explains why the attempt is credible. TrueLayer did the unglamorous work first: licences, bank connections, error handling and developer tooling. The elegant checkout came later. That order is easy to overlook, which is exactly what good infrastructure is designed to make happen.