We are aware of a known issue with Lloyds Banking Group (LBG) which may mean Transaction IDs returned by the TrueLayer Data API are subject to change.
Why does this happen?
LBG have an internal fraud prevention process that checks each transaction. As a transaction moves through this process, the unique LBG transaction ID returned by their Open Banking API is subject to change.
TrueLayer generate unique transaction IDs from a number of fields returned by the Provider's API, including this unique LBG transaction ID.
What are we doing about it?
TrueLayer have been advocating with LBG to return immutable transaction IDs. LBG have committed to deliver this in Q1 2021.
After this change has been made we no longer expect this to be an issue.
While we wait for this change to be made, we appreciate your patience and apologise for any inconvenience.
How should I handle this?
You can introduce logic in your system that minimizes the impact of this issue.
See our related article: Why are Transaction IDs subject to change?