Open Banking generally mean someone can build 3rd party integrations on top of banking APIs. It is generally not for individuals to get HTTP API access to your own "production" bank account so you can write a Python script to move money around.
I was very happy when it first appeared and my own bank made a big noise about supporting it, so went around to dig for the documentation. Had to sign up for a developer account first, that's all fine and dandy. Write some words about my use case, that's also fine I guess, not optimal but whatever. Finally arrived at the "Success" screen that said something like "Congratulations, we'll review your case and give you access to the sandbox if accepted" which was... Fiiiine.
Some days later, get sandbox + documentation access, write my ~20 line script to move 5 ImagineDollars from account 1 to account 2 within the same holder and want to see it working live but no, here comes a form with ~20 fields describing again the use case, how many users you expect, what you do in case there is errors and so on. I fill it out from the perspective that I'm just writing it for myself.
Wait ~2-3 weeks and receive a rejected email, they don't want individuals to write their own scripts, the service is for products to be built on top of their APIs, nothing more and nothing less.
If you do find a bank that lets you at least query balances and transaction history yourself, I would love to hear about it! Forget about actually initiating any transfers, I just don't want to type numbers into a spreadsheet by hand like a god damn troglodyte.
My small, local credit union lets me download spreadsheet files (not sure if they're CSV or Excel TBH) of all my transactions, I think up to 3 years back.
Presumably this is some kind of off-the-shelf software though it's white-label so I don't know how to figure out what it's called, or how to find a credit union that uses it. That said, I find such credit unions are easy to ask questions of and get satisfying answers: the people actually working there will pick up the phone, rather than farming it out to a call center states or oceans away. They will therefore probably be able tell you if they offer this functionality or not before you open an account.
I was very happy when it first appeared and my own bank made a big noise about supporting it, so went around to dig for the documentation. Had to sign up for a developer account first, that's all fine and dandy. Write some words about my use case, that's also fine I guess, not optimal but whatever. Finally arrived at the "Success" screen that said something like "Congratulations, we'll review your case and give you access to the sandbox if accepted" which was... Fiiiine.
Some days later, get sandbox + documentation access, write my ~20 line script to move 5 ImagineDollars from account 1 to account 2 within the same holder and want to see it working live but no, here comes a form with ~20 fields describing again the use case, how many users you expect, what you do in case there is errors and so on. I fill it out from the perspective that I'm just writing it for myself.
Wait ~2-3 weeks and receive a rejected email, they don't want individuals to write their own scripts, the service is for products to be built on top of their APIs, nothing more and nothing less.
Great.