Santander presents the transactions with 2 flags (1 of which is common with other banks).
The first one is the status of the transaction - “Pending” or “Booked”. Until it’s booked, we don’t import it because the transaction still remains unconfirmed and may change. For example, take a reauthorisation on the card which could be for £1, but the full transaction is for £99. It’s only when it’s booked does this update to £99.
The second one is basically a “may change” flag. This one seems somewhat unique to Santander (for now at least), but they send this to show that they may change any part of the transaction - the value, the description, the date, even the unique ID - and these fields are used to help prevent duplicates. Typically, they flag it as “may change” for 24 hours, even after it’s been booked.
As you can see, changing any of the behaviour here would cause issues, and previously did cause issues for some users with duplicates.
Very much so.
What would it take to have a flag in the bank feed settings so users can decide if they are happy to take the risk and accept transactions with a status of ‘may change’?
The delay is hugely frustrating for us compared with how it used to work.