Why is there no OpenBanking API for personal use?
https://shkspr.mobi/blog/2023/10/why-is-there-no-openbanking-api-for-personal-use/

The recent news that MoneyDashboard is suddenly shutting down has exposed a gap in the way OpenBanking works. It is simply impossible for a user to get read-only access to their own data without using an aggregator. And there are very few aggregators around.

Why is it impossible for me to get programmatic access to my own data?

There are two interlinked reasons which I'd like to discuss.Background

OpenBanking is a brilliant idea encoded in an excellent standard wrapped in some very complex processes and with some rather unfair limitations.

OpenBanking presents a standardised API to allow read and write access to a financial account. So I could give a smartphone app read-only access to my credit card and let it automatically tell me when I've spent more than £50 on sausage rolls this week. Or I could add all my bank accounts to one service which would let me see my net worth. Or any of a hundred ideas.

I could also connect my accounts in such a way that when Bank Account A drop below £100, an OpenBanking API request is sent to Bank Account B to transfer some money to A.

Nifty!Access

But here's the first problem. The only way you can get access to a bank's API is if you have a licence. And you only get a licence if you're a financial institution who can prove that they have robust security controls.  Which means that individuals have to go through an aggregator. Or, in OpenBanking terms, an "Account Information Service Provider".

Some OpenBanking providers will let individuals play in a "sandbox" to test out the API. There are no real accounts and no real money, it's just a way to test how the API works.

I can see why that makes sense for write access. You don't want a user's unpatched Raspberry Pi suddenly sending all their money to Russia.

And I can see why that makes sense for organisations which deal with data from multiple people. One leak and everyone is exposed.

But I'm not convinced that it makes sense to deny an individual read-only API access to their own account. Sure, I might accidentally leak my own data - but the same risk exists if I download a PDF statement from my bank.Coverage

The second problem is that not every OpenBanking consumer will talk to every OpenBanking provider.

For example, I have an account with Coventry Building society. They have an OpenBanking API which no one uses! They're not the largest financial institution in the UK, but have a fair few customers. And yet all the OpenBanking apps refuse to work with it.

So even if I did find an aggregator with an API, it may not work with all my financial institutions.What's next?

As much as I love using someone else's website or app, sometimes there's nothing better than writing something bespoke.

I was using MoneyDashboard as an unofficial API. I gave them read-only access to my accounts and then piggybacked off their API. But that's now closed.

Similarly, I was using Moneyed - which offered a personal OpenBanking API - but that shut down as well.

And now I can't find anything.

If you know of an Account Information Service Provider which provides read-only API access to connected accounts, please let me know!

https://shkspr.mobi/blog/2023/10/why-is-there-no-openbanking-api-for-personal-use/

#api #money #openbanking