Fintech

Open Banking Integration Stack (EU / UK PSD2)

Connect to bank accounts via open banking APIs to read transactions, verify identity, initiate payments, and run affordability checks — without asking users for their login credentials.

Fintech founders building lending, personal finance management, accounting, B2B payments, or identity products that benefit from direct bank connectivity in the EU or UK. $500–$5,000/month. TrueLayer: £0.10–0.25/API call or monthly subscription. Yapily: custom pricing. Plaid: $0.30–$1.50/connected account/month (US), similar for EU. Tink: custom. Salt Edge: $0.05–0.20/call. 📦 9 tools

Open Banking in the EU (PSD2) and UK (CMA Order) requires banks to expose standardised APIs for Account Information Services (AIS) and Payment Initiation Services (PIS). As a Third Party Provider (TPP), you can access these with user consent. Practical use cases include: account aggregation (see all bank accounts in one view), income/affordability verification for lending, instant bank transfers as an alternative to cards (lower fees, no chargebacks), bank account ownership verification for KYC, and financial data enrichment. The UK has the most mature ecosystem; EU implementation quality varies significantly by country and bank.

The Stack

TrueLayer

— Open banking API aggregator — UK and EU bank connectivity

TrueLayer is the leading UK open banking aggregator with 99%+ bank coverage in the UK and strong coverage in IE, FR, DE, ES, IT, NL. Provides unified API for AIS (account data) and PIS (payment initiation). Used by Freetrade, Revolut, Monzo, and 1000+ fintechs.

Alternatives: yapily, tink, plaid

Yapily

— Open banking with broadest pan-European bank coverage optional

Yapily covers 2,000+ banks across 18+ European countries with a single API. Stronger than TrueLayer for DE/AT/CH coverage. Provides both AIS and PIS with a developer-friendly sandbox. Best for truly pan-European products.

Plaid

— Bank connectivity for US + EU (Plaid Exchange) optional

Plaid is the default choice for US bank connectivity (10,000+ institutions) and is expanding in EU via open banking APIs. If your product spans US and EU, Plaid provides a single integration. Note: Plaid in EU is open banking compliant; in US it uses direct connectivity.

Alternatives: finicity, yodlee

Tink

— Open banking platform (owned by Visa) with strong Nordic coverage optional

Tink (Visa subsidiary) has the deepest Nordic bank coverage (SE, NO, DK, FI) and strong presence across EU. Provides account aggregation, payment initiation, and Tink Link (hosted UI for bank consent). Enterprise-tier reliability with Visa backing.

Salt Edge

— Open banking with Eastern Europe and CIS coverage optional

Salt Edge covers 5,000+ financial institutions across 50+ countries including Eastern Europe (PL, CZ, RO, BG, HU), Baltics, and CIS — regions where TrueLayer and Yapily have gaps. Important for products targeting these markets.

Moneyhub

— Financial data enrichment and categorisation layer optional

Moneyhub enriches raw bank transaction data with merchant categorisation, income identification, and affordability scoring. Built on top of open banking data, it provides a higher-level API for lending underwriting and PFM features.

Alternatives: finicity

Finicity

— Open banking and bank data for US lending and verification optional

Finicity (Mastercard) is the leading US bank data provider for mortgage and lending use cases. Provides Verification of Income (VOI) and Verification of Assets (VOA) reports accepted by Fannie Mae/Freddie Mac. Required for digital mortgage workflows.

Volt

— Open banking payment initiation (account-to-account payments) optional

Volt specialises in open banking payments (PIS) — account-to-account transfers that bypass card networks. No chargebacks, lower fees than cards (flat fee vs %). Covers UK, EU, and Brazil (Pix). Ideal as a card alternative for checkout or B2B invoices.

Alternatives: token-io, truelayer

Token.io

— Open banking payment initiation for B2B use cases optional

Token.io provides API-based bank payment initiation with a strong B2B focus (accounts payable, invoice payments, payroll). Used by enterprises replacing BACS or SEPA Credit Transfers with API-driven flows. Holds FCA and NB of Lithuania licences.

Gotchas

⚠️ Strong Customer Authentication (SCA): all PIS transactions in EU/UK require SCA. This means users must authenticate with their bank for each payment (redirection). Session caching (90-day exemption) only applies to AIS, not PIS.
⚠️ Bank coverage varies: even within the UK, smaller building societies and credit unions may not be covered. Always test your top 20 target banks before committing to an open banking provider.
⚠️ API quality is uneven: some banks implement PSD2 APIs poorly (missing pagination, incorrect error codes, inconsistent date formats). Your aggregator abstracts most of this but you will still see edge cases. Build retry logic and graceful degradation.
⚠️ Consent management: open banking consents expire (90 days in EU, variable in UK). You must build consent refresh UX and handle expired consent errors — this is often 10–20% of your backend surface area.
⚠️ Not a real-time payments system: AIS data is typically delayed 15 minutes to several hours depending on the bank. Do not use open banking account data for real-time fraud decisioning.
⚠️ PISP licence requirements: to initiate payments (PIS), you need your own Payment Institution licence or must operate under your aggregator's licence as an Agent. The agent route is faster but limits your go-to-market in some countries.
⚠️ UK regulatory divergence post-Brexit: UK open banking is regulated by the CMA and FCA (not PSD2). Variable Recurring Payments (VRP) exist in UK but not yet standardised across EU. Build separate UK and EU flows if you need VRP.