Do I need a license to use open banking APIs?

Answer from Open Banking Tracker

Do I need a license to use open banking APIs?

Summary

If you are the one accessing customer account data or initiating payments, you typically need to be a licensed AISP/PISP or an agent of one; many developers use a licensed aggregator instead.

Direct answer

It depends who is accessing the data or initiating payments. If your company is directly accessing customers' bank accounts or initiating payments on their behalf, you generally need to be an authorized or registered AISP and/or PISP (or equivalent under local law). If you integrate via an API aggregator (e.g. Plaid, TrueLayer, Tink, Yapily), the aggregator holds the license and you use their API under their terms—you do not need your own payment-services license for that integration.

Regulations differ by country (e.g. FCA in the UK, national authorities in the EU under PSD2). The Open Banking Tracker lists regulated aggregators and links to regulator directories so you can confirm licensing and decide whether to become a TPP or use an aggregator.

Related questions

Want to integrate Accounting & ERP data?

Connect to 30+ accounting platforms and ERPs through a single unified API with Apideck.