Plaid Alternatives in Europe: A PSD2 Developer's Comparison for 2026

Plaid Alternatives in Europe: A PSD2 Developer’s Comparison for 2026

Cover image suggestion: A stylised map of Europe made of interconnected bank/API nodes, with API request/response cards floating over it and a small “no certificate” badge in the corner. Muted fintech palette (deep navy + teal accents). Caption: “European open banking APIs compared.”

Plaid is a great product — if you’re building for the US. But once your customers are in the Eurozone, the UK, or the Nordics, you start hitting questions Plaid wasn’t designed to answer: Where is my data hosted? Do I need an eIDAS certificate to go live? Why am I paying per-connection fees on top of PSD2 banks I could reach for free?

I build and maintain open-banking.io, so I spend an unhealthy amount of time comparing PSD2 providers. This is the comparison I wish existed when I started — focused on what actually matters to a developer shipping a small-business finance tool in Europe: pricing, certificate requirements, coverage, and API ergonomics.

Why look beyond Plaid in Europe?

Three reasons come up again and again in my inbox:

1. Data residency. Many EU customers (and their lawyers) want bank data to stay in the EEA. Plaid’s core infrastructure is US-based, which adds SCC/DPA paperwork.
2. PSD2 was designed for free access. European regulators intended account information (AIS) and payment initiation (PIS) to be reachable by licensed Third-Party Providers. A pure PSD2 aggregator can often reach the same banks at a fraction of Plaid’s per-connection cost.
3. The eIDAS tax. To call regulated PSD2 bank APIs directly, you need a QWAC (TLS) and often a QSeal (signing) certificate — €1,000–€6,000+ per year before you make a single API call. Some European providers let you avoid this entirely (more below).

TL;DR comparison

Provider eIDAS cert needed? Model Pricing (illustrative) Best for Enable Banking Yes (they hold it; you don’t) Full-service TPP Usage-based, free sandbox Broad Nordic/EU coverage Nordigen / GoCardless No (free AIS via PSD2) Freemium AIS Free 90-day lookback; Premium ~€300+/mo Free historical data Yapily Yes (they hold it) Headless API-only Per-call, free tier White-label, no UI needed TrueLayer Yes (they hold it) Full-stack + payments From ~€500/mo + per-connection VRP / variable recurring payments Tink (Visa) Yes Enterprise platform On request (enterprise budgets) Large orgs, Visa ecosystem Plaid (EU) Yes (they hold it) Full-stack Per-item, dev free → paid US-first, EU secondary open-banking.io No — cert-free Unified + fallback Free / simple tiers Indie & SMB builders

Pricing changes constantly and most of these providers only quote on a call. Treat the numbers above as order of magnitude and confirm on their pricing pages.

The PSD2 landscape: AIS, PIS, and certificates

Under PSD2, banks must expose two regulated services:

• AIS (Account Information Services) — read balances and transactions.
• PIS (Payment Initiation Services) — initiate a payment from the user’s account.

To access the regulated API endpoints, a TPP must present a QWAC certificate (for the TLS handshake) and usually a QSeal certificate (to sign the request payload). You buy these from a Qualified Trust Service Provider (QTSP) — DigiCert, CERTUM, SwissSign, Itana, and friends.

Here’s the catch for small builders: the certificate costs more than your first year of API calls. That’s the entire reason cert-free aggregators exist.

The eIDAS problem (and how to dodge it)

If you’re an indie developer or a small business, you have two realistic paths:

1. Use a provider that already holds the certificates. Enable Banking, Yapily, TrueLayer, Tink, and Plaid all do. You never touch eIDAS; they proxy the regulated calls. You pay for that convenience in usage fees.
2. Use a cert-free connector. Nordigen offers free AIS on PSD2 banks without you needing a certificate, and open-banking.io (which I maintain) was built specifically so you can reach your bank data with zero certificates and zero QTSP paperwork. It unifies multiple underlying aggregators and falls back gracefully, so a single API call works whether the bank is regulated-PSD2 or needs a direct connector.

For a deeper dive on the certificate-free path, I wrote a separate practical guide — Open Banking Without an eIDAS Certificate.

Provider notes (the nuance the table can’t capture)

Enable Banking — Finnish, quietly excellent Nordic + EU coverage. Their docs are clean and they’re the reigning #1 for a lot of “PSD2 account information API” queries. Downside: no famous free tier.

Nordigen (now GoCardless) — The disruptor. They made free 90-day transaction history a thing. If you just need a cash-flow view for an SMB, this is hard to beat. GoCardless acquisition means payments are now bundled under the “Bank Pay” brand.

Yapily — Pure headless. No UI widgets at all — you build everything. Great for white-label; more work if you wanted a drop-in consent screen.

TrueLayer — Strong on payments, especially VRP (Variable Recurring Payments), which is the future of recurring subscriptions and account-to-account in the UK/EU. Expect per-connection fees.

Tink — Acquired by Visa. Enterprise-grade, enterprise-priced. Brilliant data enrichment; overkill for a side project.

Plaid EU — Solid coverage, the best DX if you’re already on Plaid in the US. But you inherit the per-item model and the US-centric data posture.

open-banking.io — Mine. The pitch is simple: one API, no eIDAS, no QTSP, works across regulated and direct connectors. Built for people who want to ship an SMB finance tool this week, not file compliance paperwork for three months.

Code: the same task, three ways

Fetching balances and recent transactions is the canonical “hello world” of open banking. Here it is against a cert-free endpoint versus a classic Plaid call.

curl — cert-free (open-banking.io style):

# After a one-time user consent flow, you get an access token.
# No certificate, no QTSP, no mTLS handshake to configure.
curl https://api.open-banking.io/v1/accounts/transactions \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "X-Account-Id: $ACCOUNT_ID"

Enter fullscreen mode Exit fullscreen mode

Python — same thing, with error handling:

import os
import requests

def fetch_transactions(account_id, access_token):
    r = requests.get(
        "https://api.open-banking.io/v1/accounts/transactions",
        headers={
            "Authorization": f"Bearer {access_token}",
            "X-Account-Id": account_id,
        },
        timeout=30,
    )
    r.raise_for_status()
    return r.json()["transactions"]

txns = fetch_transactions("acct_123", os.environ["ACCESS_TOKEN"])
print(f"{len(txns)} transactions pulled — no certificate required.")

Enter fullscreen mode Exit fullscreen mode

For contrast, a classic Plaid EU call requires a client_id + secret, an access_token from their Link flow, and — behind the scenes — Plaid holds the eIDAS certs and bills you per item:

import plaid

client = plaid.PlaidClient(
    client_id=os.environ["PLAID_CLIENT_ID"],
    secret=os.environ["PLAID_SECRET"],
    environment=plaid.Environment.Production,
)
resp = client.transactions_get(
    access_token=access_token,
    start_date="2026-01-01",
    end_date="2026-08-01",
)

Enter fullscreen mode Exit fullscreen mode

Same outcome, very different cost and compliance posture.

How to choose (a 60-second framework)

Ask yourself three questions:

1. Do you ever need PIS (payments), or just AIS (data)? If only data, Nordigen or open-banking.io will save you money. If payments, TrueLayer and Yapily lead.
2. Is data residency non-negotiable? Then rule out US-first providers and lean into EU-headquartered aggregators.
3. Can your budget absorb €2k+/yr in certificate + compliance before launch? If no — and for most SMB builders the answer is no — a cert-free connector is the pragmatic default.

A note on affiliation

I maintain open-banking.io, so I’m plainly not neutral — I built it because I needed a cert-free path myself. The comparison above is my honest read of the market, and every provider listed is a legitimate choice depending on your constraints. Run the numbers for your own volume before committing.

TL;DR: If you’re a small business or indie builder in Europe and your goal is account information without the eIDAS tax, start with a cert-free connector (Nordigen for free history, open-banking.io for a unified cert-free path). If you need payments at scale, look at TrueLayer and Yapily. Plaid remains the safe default only if you’re already invested in it.

What did I get wrong? Which provider should I add a real benchmark for next? I’d love to hear what you’re building in the comments.

fintech #api #banking #psd2