Since the Open Banking APIs were first made available on 13 January 2018 we have been working closely with the 9 participating banks and the Open Banking Implementation Entity (OBIE) to make Open Banking work.
In order to help deliver our and the OBIEs vision for Open Banking, OpenWrks have been monitoring the performance and stability of each of the banks' APIs as they became available. We’ve been doing this via both our own internal testing, alongside our rapidly growing live customer base who are using the OpenWrks Open Banking toolkit to securely access detailed bank account information.
A spokesperson for the OBIE commented. "The UK's Open Banking standards will, if implemented as intended, create a dynamic, reliable and flexible platform on which banks, fintechs, retailers and others can build an entirely new, more competitive and customer-focused, marketplace for financial services. The industry is, however, barely halfway through the process of implementation and there has been some variability in execution and performance.”
The OBIE continued.“The key is to address any issues that arise rapidly and effectively and hold to the published standards, which are evolving but are widely regarded as being world-leading.”
"The OBIE is working closely with ASPSPs and TPPs to do just that with API performance and to improve the degree of conformance to the standards. While we still have some way to go, we have seen significant improvements since January this year and we expect that to continue."
"OpenWrks have made a valuable contribution to this work and we would encourage all participants to review this data."
The ability to retrieve rich, financial information fast and reliably is key to the success of the Open Banking ecosystem, we will be sharing our insight into the speed of response from each bank's API endpoints. The chart below breaks out the response time, in seconds, for the key stages of retrieving data through an Open Banking API:
We are pleased to be able to start sharing our findings and provide businesses looking to utilise Open Banking some objective clarity around the performance of the Open Banking APIs. We will continue our work with our partners at the OBIE, all of the Banks and the wider Financial Services market to ensure Open Banking works to truly improve people's everyday lives.
In order of appearance; Allied Irish Bank (AIB), Bank of Scotland (BOS), Barclays, Danske Bank, Halifax, HSBC, Lloyds Bank, Nationwide, NatWest, Royal Bank of Scotland (RBS), Santander and Ulster Bank.
You can get exclusive insight into the performance of the CMA9 before anyone else by clicking the button below.
This is likely to be of interest to you if you are from; a Third Party Provider (TPP) regardless of whether you are, or are thinking about developing against Open Banking APIs, if you're from a Bank or a Payment Account Provider.
At OpenWrks we’re developers and credit practitioners, so we use our own technology to create brand new customer experiences ourselves.
Because we eat our own dog food, our developer docs are really easy to understand and our Sandbox means you can get up and running with the OpenWrks API in minutes. Simply click the button below to request Sandbox access and you’ll be able to make requests, receive responses and understand the type of Open Banking data OpenWrks can provide.
Q: What is this data?
This graph contains the median Open Banking endpoint response time from each CMA9 bank and sub-brand. This data tracks how long it takes for the bank to successfully respond to OpenWrks with access tokens, account requests, accounts, balances and transactions.
Q: What does this data mean?
When a customer consents to sharing their data with OpenWrks, we’ll call each of these endpoints in turn, sometimes multiple times in cases where someone has a large number of transactions. So as a rough guide, these numbers are indicative of the amount of time it will take us to return data to our clients for each bank.
Q: Why are you sharing this information?
We want to make Open Banking work. We believe a key part of that is being open and providing honest and objective information about the performance of our own service and the services we use to make them work, especially our bank partners. The services our clients use rely heavily on the performance of the banks’ Open Banking endpoints, so for our clients to offer an exceptional service to their customers, they need to understand the speed at which OpenWrks can retrieve information from the banks.
Q: How are you measuring this?
We’re tracking anonymous usage statistics throughout our own application using Microsoft Application Insights. Every time we make a call out to a bank API endpoint, the response times and outcome are logged. The raw logs are then aggregated and analysed to produce the metrics you can see above. We don't interpret the data or change it in anyway. This is the objective data we're seeing back from every bank endpoint.
Q: How often will you be sharing this?
In the immediate term we will be sharing this information on our blog once a month. In the near future it will become a new live feature on our systems health page.
Q: What will you be doing with this data long-term?
In time, we will be sharing this data live on our system health page, along with each bank’s up time. We also intend to expose this data over our API. This will be updated in real time so our clients and their teams will always know precisely what OpenWrks overall operational status is.
Have another question? We'd love to hear your thoughts, let us know in the comments.