openbankingspace / tpp-issues

34 stars 1 forks source link

Barclays - V3 invalid transaction Next link #174

Open lucas-s-work opened 5 years ago

lucas-s-work commented 5 years ago

In this situation when attempting to fetch transactions from multiple accounts the Next transaction link is invalid with missing account_id and incorrect path.

Expected

"Next":\"https://telesto.api.barclays/open-banking/v3.1/aisp/accounts/--account_id--/transactions?toBookingDateTime=--to-time--&offset=50&fromBookingDateTime=--from-time--0&limit=50&includePendingRecords=false

Received

"Next\":\"https://telesto.api.barclays/open-banking/v3.1/aisp/accounts?toBookingDateTime=--to-time--&offset=100&fromBookingDateTime=--from-time--&limit=50&includePendingRecords=false\

Impact

High, this prevents use of transaction data as it may be incomplete.

Submitted as: OBSD-9880

dan-vernon commented 5 years ago

Further to the previous issue related to pagination, we've encountered the following with the Barclays v3 endpoint today.

When queried, the /transactions endpoint (https://telesto.api.barclays/open-banking/v3.1/aisp/accounts/AcountID/transactions) returns a Next link to /balances (https://telesto.api.barclays/open-banking/v3.1/aisp/accounts/AcountID/balances...) rather than the next available page of transactions. This returns a 500 error:

{
      "ErrorCode": "UK.OBIE.UnexpectedError",
      "Message": "Unexpected Error occurred while processing the request "
}

For additional context - after an automated retry attempt at hitting the erroneous Next / balances endpoint we then received a 400 auth issue:

{
  "ErrorCode": "UK.OBIE.Field.Unexpected",
  "Message": "Consent validation failed because of invalid data. "
}