Note: This article has been archived. It relates to a historical event that has been resolved.
During data sharing, a Data Holder’s (DH) Get Transactions For Account API was not returning the most recent posted transactions.
A consumer was able to view all posted transactions on the DH’s Online Internet Banking Application dated until D-1 ('D' being today’s date). However, only D-2 posted transactions were returned by the DH when the ADR called the Get Transactions for Account API on today’s date. The transactions dated D-1 were not retuned by the DH and were not visible on the ADR’s application.
This issue occurred for a consumer holding a joint account but is valid for all type of accounts.
The issue was caused by a batch processing job which posts transactions every day to the ADRs. The batch processing implementation was time-bound and in some cases was not able to complete the processing of all transactions and hence creating a misalignment between the DHs Online Internet Banking Application and the ADR’s application.
To resolve the issue, the DH scaled-up the compute resources available to the batch processing job and allowing it process all posted transactions (up to D-1).
D-1 posted transactions are not available to the ADR when a call to the DH’s Get Transactions For Account API is made by the ADR on today’s date (D).
Misalignment between the transactions visible on the DH’s Online Internet Banking Application and the ADR’s application.
ADR & DH