Known Issues

Issue impacting ‘some’ GET /accounts/{AccountId}/statements requests – workaround(s) detailed below:

We have a known defect, which is causing some requests for Statements to fail and the fix is being worked on a priority.
In the meantime, If you experience a ‘500’ error response when making a request for Statements, please follow the known working solution(s) as below. If needed, please contact us for any questions or support with this matter and we’ll do our best to help.

Working solutions available for you to use.

Option 1:

When making a request for Statement(s), please add the two respective query parameters to the URL, as shown below. Please note, both the “from” and “to” date query parameters need to be included in the URL and should be provided with the correct capitalisation. If one parameter is sent only, the request will fail. Therefore, it’s important both parameters are sent (as shown below)

  • fromStatementDateTime parameter: Date Time to filter statements FROM (format like: fromStatementDateTime=2023-09-30T00:00:00)
  • toStatementDateTime parameter: Date Time to filter statements TO (format like: toStatementDateTime=2023-11-30T00:00:00)
  • Example: https://accounts/<<accountID>>/statements?fromStatementDateTime=2023-09-30T00:00:00&toStatementDateTime=2023-11-30T00:00:00
Option 2:

If you’d prefer, the Statement request can be made with NO query date parameters. For this scenario to work, it's important the Consent either contains both the TransactionFromDateTime & TransactionToDateTime parameters, or NONE of the Transaction date parameters (if one Transaction date parameter is set in the Consent, the request will fail)

500 Error when Requesting 15 Months of Current Account Transaction Data

Due to how we translate the date range you may receive a 500 error when requesting 15 months of transaction data. This is likely to occur when requests are made late evening or on weekends.

As a work around please retry your request with +/- 1 day in the date range.

Current Account Transactions Not Returned

Due to a system limit, if a member has a large number of transactions on their account an error will be returned, rather than returning the members' transactions.

**There is a work around for Third Parties, who will have to request the same data in smaller date ranges to avoid returning an error.

API Affected: GET /accounts/{AccountId}/transactions