Why we monitor, and why you should to… CMA9 Open Banking Edition

Fresh from congratulating a UK CMA9 bank on keeping their V1 and V2 APIs going for a decent period beyond the February switchover, we had a deeper look to see if the two APIs performed differently.

For the most part, they did not, in fact, they were almost identical, except for this period between May 1st and May 5. During that 5 day window the V2 API dramatically improved, speedwise, so we decided to take a look at that. Afterall, who wouldn’t always want to have a faster API?

The data showed that rather than actually getting faster, the API simply returned less data, rather than returning, as the regulations call for, all the ATMs in the United Kingdom, the API returned exactly 1 ATM, located at a branch in a town with an A in it. Essentially, for almost a week, the API was returning only one location. And here’s the problem with many monitoring solutions – the API never failed, it was, if anything, performing MUCH better than it had been. But without a content validation check on the items returned, you’ll not notice.

So, if you’re a CMA9 Bank (Allied Irish, Bank of Ireland, Nationwide, Halifax, Lloyds, Royal Bank of Scotland, HSBC)¬†for example, reach out and we can let you know which is was, if you don’t know, and how to avoid being caught out again!

Contact Us for Details
By |2018-05-17T11:56:01+00:00May 17th, 2018|News, Opinion|0 Comments

Leave A Comment