Yapily provides gateway connectivity between bank’s APIs and third party providers (TPPs) who build services that need access to financial data and to issue payments on behalf of their customers. With direct connectivity, Yapily is able to monitor each bank in real-time, allowing TPPs to know when a particular endpoint is down, slow, or even if the entire bank is experiencing any issues.

Starling Bank upholding the fastest response times with 61ms

Last month, I took a deep dive into the average response times of the top performing banks with a focus on our transactions endpoint. A full month has passed since then, so let’s see how these banks have performed in the month of May vs the previous data from last month (April).

Here are some of the highlights:

• The top 5 have maintained their positions with Starling still upholding the fastest response times
• The difference between 5th and 9th place is almost negligible and in comparison to April, some of these banks have slightly shuffled their positions
• The average response times for Natwest and BOI UK have slightly increased whereas Halifax and RBS have slightly decreased
• HSBC Business no longer makes the list with the average response times for getting transactions in May just over a second at 1247ms

The 1 second club

Here are some institutions that had an average response time of less than 1 second for retrieving transactions last month.

As we approach July, it will be interesting to see if the trend of decreasing average response times for the larger banks continues into the second half of the year. It will also be useful to identify how increased volumes as Open Banking adoption continues may affect the response times and whether the likes of Monzo, Revolut and Starling can maintain such response times under these new conditions.