When an Open Banking integration stops working, the cause is often somewhere between three parties: your code, the API aggregator, and the bank. Each one points at the others, and a call with all of them can burn a day without finding the fault.
We can join your troubleshooting sessions, with banks, API aggregators and your own development team, as the person in the room who has seen this kind of failure before. We read the traces, ask the questions that narrow it down, and help everyone agree where the fault actually is.
What this can include
- Joining a screen-share with your team, a bank, or an API aggregator.
- Reading requests, responses and error traces to locate the fault.
- Telling you which party needs to change what, in plain English.
- A short written summary of what was found and what to do next.
How it works
Get in touch with a short description of the failure and who is involved. We will tell you honestly whether we can help. If we can, we agree the scope and terms up front, in writing, before any session starts.
If the problem is bigger than one fault, for example a design that needs rethinking, see Open Banking consulting.