We're updating the issue view to help you get more done. 

Non-personal Barclays endpoints are broken.

Description

Various non-personal Barclays endpoints are effectively non-functional, returning various errors.

Here's an example run against Barclays Business with our in-house conformance test harnesses:

Starting harness: Accounts- Done! -
Name: Accounts Description: Exercises the Accounts Read/Write API Endpoint

  • Pass count: 1 Fail count: 1
    (10000000000000143340 - got a 400 HTTP status (400 Bad Request);10000000000000117311 - got a 400 HTTP status (400 Bad Request)

  • Account list is retrieved passed: Yes

  • Individual account information is retrieved passed: No
    Starting harness: Balances- Done! -
    Name: Balances Description: Exercises the Balances Read/Write API Endpoint

  • Pass count: 0 Fail count: 2
    (got a 404 HTTP status (404 Not Found))
    (10000000000000143340 - got a 400 HTTP status (400 Bad Request);10000000000000117311 - got a 400 HTTP status (400 Bad Request)

  • Balance list is retrieved (bulk) passed: No

  • Individual balance information is retrieved passed: No
    Starting harness: Products- Done! -
    Name: Products Description: Exercises the Products Read/Write API Endpoint

  • Pass count: 0 Fail count: 2
    (got a 404 HTTP status (404 Not Found))
    (10000000000000143340 - got a 400 HTTP status (400 Bad Request);10000000000000117311 - got a 400 HTTP status (400 Bad Request)

  • Product list is retrieved (bulk) passed: No

  • Individual product information is retrieved passed: No
    Starting harness: Transactions- Done! -
    Name: Transactions Description: Exercises the Transactions Read/Write API Endpoint

  • Pass count: 0 Fail count: 2
    (got a 404 HTTP status (404 Not Found))
    (10000000000000143340 - got a 400 HTTP status (400 Bad Request);10000000000000117311 - got a 400 HTTP status (400 Bad Request)

  • Transaction list is retrieved (bulk) passed: No

  • Individual transaction information is retrieved passed: No

We see similar issues with Barclaycard endpoints, where transactions currently consistently return a 500 error code.

Technical Impact

This is a major issue for us as we are effectively blocked from properly testing our business account users before migrating to Barclays' Open Banking API's.

Workaround

None

Resolution Notes

None

Impact Assessment

This is a major issue for us as we are effectively blocked from properly testing our business account users before migrating to Barclays' Open Banking API's.

Status

Assignee

Unassigned

Reporter

Service Desk

Reference

None

Service Desk Reference

OBSD-9815

ASPSP

Query Type

None

TPP Impact

None

TPP

Business Impact Severity

Level 1

Share

Yes