Barclays - get request on accounts endpoint, response bad request, error due to invalid data

Description

Hi there,

We are currently experiencing an issue with some of your customers accounts. Overnight when refreshing their accounts we performed the get request on the accounts endpoint and then go on to receive the response bad request with a 400 error, with the error message 'accounts request could not be processed due to invalid data'. On your developer portal I've seen you've put that 'Some Barclays accounts may have a flag or marker which impacts the customers’ ability to use Open Banking services. An error message confirming ‘the request could not be completed due to invalid data’ will be received in these instances. Customers will need to contact Barclays through their traditional channels of Branch or Telephony to have the flag updated or removed before they are able to progress further'.

The problem here is the fact that the consents affected had numerous accounts connected, some having up to 96 accounts attached and around 30-40 of them refreshed fine then the rest received this message. When attempting to refresh this same consent again the number that received this error went down to around 5. I wanted to check whether this was a problem that happened overnight or whether this is an issue that needs reporting, I've attached below an example of the get request and the response of an affected account.

2019-11-25 10:12:07.534 +00:00
HttpConnectRequest: [GET] https://telesto.api.barclays/open-banking/v3.1/aisp/accounts/10000000000000305697
Message: Request Headers: "Authorization: Bearer xxxxMhFQ
Accept: application/json
x-fapi-financial-id: 0015800000jfAW1AAM
"
Request Body: ""
Properties: {"ConsentId":"xxxx5aac","Scope":["ConsentId: xxxx5aac","5041bd78-8ae7-4750-b2f6-15ace799aaaf","GET:https://telesto.api.barclays/open-banking/v3.1/aisp/accounts/10000000000000305697"]}

Here we are performing the get request on the accounts endpoint.

2019-11-25 10:12:08.380 +00:00
HttpConnectRequest: [GET] https://telesto.api.barclays/open-banking/v3.1/aisp/accounts/10000000000000305697
Message: RESPONSE BadRequest
"Connection: keep-alive
Date: Mon, 25 Nov 2019 10:12:07 GMT
Server: Apache
X-Frame-Options: DENY,DENY
X-Content-Type-Options: nosniff
X-Download-Options: noopen,noopen
Referrer-Header: no-referrer,no-referrer
Strict-Transport-Security: max-age=31536000;includeSubDomains,max-age=5184000
X-Xss-Protection: 1; mode=block
Cache-Control: no-cache, no-store, must-revalidate,no-cache;no-store
X-Application-Context: zuul-gatewayrod:32bdf27b9595640901019d6a23719f74
x-fapi-interaction-id: 09915d81-f8c8-4d16-9762-c5f2c48a92a6
Set-Cookie: 09cc08b965e567968f2b5dc4f6ea9dcf=d8f759f515f76f4aff282053eb164bde;path=/;HttpOnly;Secure
Content-Type: application/json
"
"{\"Code\":\"400 Bad Request\",\"Id\":\"09915d81-f8c8-4d16-9762-c5f2c48a92a6\",\"Message\":\"Request cannot be fulfilled. \",\"Errors\":[{\"ErrorCode\":\"UK.OBIE.Field.Unexpected\",\"Message\":\"Accounts request could not be processed due to invalid data. \"}]}"
Properties: {"ConsentId":"xxxx5aac","Scope":["ConsentId: xxxx5aac","5041bd78-8ae7-4750-b2f6-15ace799aaaf","GET:https://telesto.api.barclays/open-banking/v3.1/aisp/accounts/10000000000000305697"]}

However the response is bad request with this message of account requests could not be processed due to invalid data.
This results in us being unable to receive the information we need and as such we can't provide the service your customer is expecting.

Technical Impact

This results in us being unable to refresh some of the accounts, stopping us from being able to get the most recent information and as such not being able to provide the service your customer is expecting. I'm aware that we have raised a similar ticket about this error message coming up on the accounts access consent endpoint however since this is affecting the accounts endpoint I thought it would be best to raise on a separate ticket.

Workaround

None currently.

Resolution Notes

None

Impact Assessment

Fairly high impact as it affected quite a few accounts and want to know whether this is an issue with the accounts or whether there is something else that has happened. Any help or guidance would be appreciated.

Status

Assignee

Unassigned

Reporter

Service Desk

Reference

None

Service Desk Reference

OBSD-12361

ASPSP

Query Type

None

Created (Original)

Nov 25, 2019, 11:05 AM

TPP Impact

None

Issue Summary

None

OB Environment

None

Business Impact Severity

Level 2

Share

Yes
Configure