A Guide to Open Banking APIs
How account-data and payment-initiation providers such as Plaid, Tink, and TrueLayer differ by region, product, and regulatory model.
By FintechToolkit Editorial Team · Methodology 1.0
Open banking APIs let an application read bank account data or initiate payments from a bank account with the account holder's consent. Providers differ mainly in which banks and countries they reach, whether they return raw or enriched data, and whether they also initiate payments.
Regulation shapes coverage
In the EU and UK, PSD2 requires banks to provide access to licensed third parties, so European providers connect through regulated bank APIs. In the US, access has run largely on bilateral data agreements and the Financial Data Exchange (FDX) API standard. Coverage claims are therefore regional, and a provider's strength in one market says little about another.
North America
Plaid has its broadest coverage across US and Canadian financial institutions, with products for account verification (Auth), transaction history (Transactions), and account-holder identity (Identity), connected through its Link flow.
Yodlee (owned by private equity firm STG since Envestnet's 2025 divestiture) offers broad account aggregation with a traditional financial-institution focus, with most use in wealth management and financial wellness.
Europe and the UK
Tink, owned by Visa since 2022, connects to banks across Europe for account information and payment initiation, with data enrichment on top. TrueLayer and Yapily provide account data and bank payments across the UK and Europe. GoCardless uses bank connectivity for bank debit and bank payments.
Embedded finance
Embedded-finance providers sit one layer further down: instead of reading accounts at other banks, they let a product offer accounts of its own. Unit, Treasury Prime, and Increase provide API access to accounts and cards held at partner banks, while Column is itself a nationally chartered bank that offers developer APIs.
Synapse Financial Technologies, previously a significant provider in this space, filed for bankruptcy in 2024, and end users lost access to funds. In embedded finance the partner bank rather than the platform holds customer deposits, so the deposit relationship and reconciliation model differ by provider.
Self-hosted
Apache Fineract is an open-source core banking engine with a REST API, run self-hosted. Operating it means taking on deployment and upgrades in place of a vendor relationship.
How to choose
The differentiating factors are bank coverage in the target countries, whether payment initiation is needed as well as data, whether the provider returns raw account data or an enriched, categorised product, and how reconnection and consent renewal are handled when a bank connection lapses.
Editorial note
This guide explains evaluation considerations and links to directory records. It does not constitute legal, compliance, procurement, or investment advice. Use the linked primary sources to validate time-sensitive details.
Tools covered in this guide
- PlaidConnect bank accounts and access transactions, balances, and identity via one open banking API.

- TinkPSD2-compliant open banking for account aggregation, payment initiation, and finance data.

- TrueLayerOpen banking payments and data across the UK and Europe, built on PSD2 rails.

- YapilyOpen banking infrastructure with no end-user interface — a pure API layer.

- GoCardlessBank debit and open banking payments for recurring and invoice collection.

- UnitEmbedded finance platform for adding banking, cards, and lending to any product.

- ColumnA nationally chartered bank with its own developer API, no intermediary.

- Apache Fineract (Mifos X)Open-source core banking engine for microfinance and community finance, with a full REST API.
