This article is almost incoherent. I'm really surprised to see it rank here. It's useful neither to folks who know about open banking (because they would learn

This article is almost incoherent. I'm really surprised to see it rank here. It's useful neither to folks who know about open banking (because they would learn nothing new), nor to people new to open banking (because it doesn't explain even the basics of how it's meant to work). Open banking is meant to allow any third party to get your financial information if you agree, just like any app can implement social auth with Google/Twitter/GitHub. But (pasting a comment I wrote here 2 years ago): "By using Plaid or an Open Banking service from another party (e.g. Experian) you'll pay fees to get information you can get for free if you integrate directly with the banks. Even though the open banking APIs are uniform, any company wishing to use them still has to register with each and every bank, and test the integration works with each one. Until you've done it once, it's hard to know whether it will be easy (you write the code once, and it works flawlessly for all banks) or you have edge cases (e.g. some banks have funny timeout issues). So if you're a developer on a deadline, you will likely prefer to use a single API."