Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Yeah, open banking is designed so other (supposedly trusted) organisations can write apps that work across banks in Europe to do things such as analyse your account data, take payments, setup standing orders, that sort of thing.
It's basically impossible for you to use it as an end user - and it's a very odd (and backwards) definition of an Open API.
All it really means is that "banks must have a way to integrate with this specific type of API request on some level" even though it's not an API you can meaningfully access.
stop52698dAnd HBCI has another advantage: its theoretically possible to implement a static webpage to communicate with the bank, since its also specified for https. The current Version is FinTS 4.0, but most banks use FinTS 3.0 aka HBCI 3.0.
I feel your pain man, I had a very similar experience with my bank. Their api had just enough docs to get you sorta started but no actual usage examples or clear info on how to actually use it. Fun times.
Aldar4478d@LucaScorpion I mean... That's probably what aggravated me the most.
My bank had all the detailed documentation in their main developer portal.
ALL OF IT. INCLUDING ALL THIS OPEN BANKING STUFF.
Seeing that, how I could have known that it was locked behind a frickin blast-door of laws like that? -_-"
Haxk20428308dI had the same with my project. Not limited by technology but by law.
Going through bank certification for my code right now with a large bank in US meetings 2 times a week and i keep raising issues with bugs in there integration I've found. They keep telling me well it's deployed on other platforms just fine so it must be my code (management) get response on ticket from their devs accepting responsibility few hours later. Is not fun dealing with infallible financial institutions.