When I started building a budgeting app in 2026, I thought I had a clear picture of the technical work: connect to banks, normalise transactions, render charts, ship. I had built fintech in the US before. How different could Europe be?
The answer turned out to be: different in twenty-seven specific ways, plus a few that span all of them.
This is the field report I wish I had read six months ago.
In theory, the Payment Services Directive opened bank data to licensed third parties. In practice, “PSD2 access” is a phrase that has done more damage to indie fintech timelines than any other technical decision.
Every bank had to expose an API. Almost no two banks chose to interpret the spec the same way. Field names drift. Pagination is implemented four different ways. Refresh-token lifetimes range from minutes to months. Strong Customer Authentication flows differ per bank, per country, per app version. The Berlin Group standard helps a little — but it’s a standard about what can be implemented, not what must be.
The aggregators (TrueLayer, Tink, GoCardless Open Banking, Yapily) exist precisely because nobody wants to maintain this matrix in-house. They charge per connected account per month. That cost lands on your unit economics before you have any users.
The Eurozone is one currency union and twenty different banking ecosystems. Outside the Eurozone — UK, Poland, Sweden, Czechia, Denmark, Hungary, Romania, Bulgaria — there are seven more banking ecosystems on top, each with their own currency and their own national equivalents of “the four big banks.”
A budgeting app that wants to serve “Europe” has to choose: launch narrowly and grow horizontally, or try to support a long tail of small banks from day one. The first path is honest. The second is impossible.
Even within a single country, the support gap between the top three retail banks and the next ten is enormous. PSD2 access for a credit union, a community bank, or a regional savings bank is often technically real and operationally unusable.
Half of Europe earns in euro. The other half doesn’t. Plenty of people earn in one currency and spend in another — UK contractors working for German clients, Italians paid in CHF for Swiss work, Portuguese remote employees of US companies.
A “multi-currency” budget is not a feature you add later. It’s an architectural choice. Either every transaction is stored in its native currency and converted only for reporting, or your totals quietly lie to you as the FX rate moves. The apps that took the first path are rare. The apps that took the second are most of them.
GDPR is a real selling point for European users — especially for budgeting, where you’re handing a stranger every line of your financial life. “Built in the EU under GDPR” is a phrase that lands.
It is also a phrase that makes your launch slower. Privacy-by-design isn’t a checkbox you flip on after the MVP. Data minimisation, retention defaults, processor agreements with every sub-vendor, DPIA documentation before you ship a new integration — all of it has to be there before any user logs in. The cost shows up in calendar weeks, not euro.
The trade-off is worth it. But pretending it costs nothing is dishonest.
Plaid is essentially absent. Stripe Connect exists but doesn’t solve the data side. The vast US ecosystem of fintech-as-a-service vendors — Pinwheel for payroll, Atomic for tax, Argyle for income verification — either doesn’t operate here or operates with materially less coverage.
The corollary: a lot of US fintech-startup playbooks (“just use Plaid”) translate to “build it yourself, or pay a European aggregator a lot.” There is no shortcut here.
Revolut, N26, Bunq, Wise, Trade Republic, Monese — every neobank with a million European users has built a “savings goals” or “spending categories” feature in the last two years. They are not great features. But they are free, already installed, and good enough for most people.
Standalone budgeting apps in Europe have to be either dramatically better or aimed at people who explicitly want a tool that isn’t tied to one bank. The second framing is the honest one. It also limits your top of funnel.
European fintech Series A rounds in 2026 are smaller, slower, and more dilutive than their US equivalents. There are good European fintech investors — there are simply fewer of them, and a fintech that needs to support twenty markets and twelve currencies pre-Series-A reads to them as “expensive.”
The realistic path is bootstrap-and-narrow, not raise-and-conquer. Plan the product around that.
The reason a European budgeting app makes sense in 2026 is precisely the reason it’s hard: nobody has built the one that respects the actual shape of European money. Multi-currency natively. EU data residency by default. Zero-based budgeting because percentage rules don’t survive contact with a four-currency life.
The fight is real. So is the gap.
If you’re building something similar, get in touch — hello@cooperae.com.