We are aware of a known issue that may cause Transaction IDs to change between requests for transactions.
Why does this happen?
TrueLayer generate unique Transaction IDs from a number of fields returned by the Provider's API, including, but not limited to:
- The provider's internal ID
Unfortunately — due to factors outside TrueLayer's control — some of these fields are subject to change. This may happen for a number of reasons, including:
- Amendments to the provider's records, e.g. foreign exchange settlement or an adjustment
- Fraud prevention checks which may also amend a field
- Idiosyncracies of various legacy banking infrastructures
What are we doing about it?
TrueLayer have been working closely with all of our providers to identify fields that can be used to generate unique and immutable Transaction IDs.
Where these fields are not available - we are advocating for improvements that will allow us to implement this in the future.
This constitutes a significant change and will likely be included in a future version of the Data API.
How should I handle this?
Until Transaction IDs are fully stabilised - the best way to avoid listing duplicates in your system is to overwrite previously cached transactions instead of merging them.
While we work on this, we appreciate your patience and apologise for any inconvenience.
If you need support on this, please don't hesitate to contact us.