I have a webhook set up to push transactions from Monzo to YNAB, which also handles settling/locking transactions based on the fact that Monzo pushes an update to the transaction when it gets settled by the merchant.
I’ve just reviewed my transactions in YNAB and it looks like transactions haven’t been clearing since around a month ago (24th July) - did something change on Monzo’s end to not push updates any more? I’m 100% sure this worked before (i.e. since at least January, when I originally developed and deployed the webhook). Unfortunately I recently recycled the function so have lost logs going back very far, but for the last week or so I’ve only received ‘transaction.created’ events with empty ‘settle’ values (except for direct bank-to-bank payments).
I’m keen to find out if transaction update webhooks have been disabled on purpose, or if I need to investigate this further on my end.
I don’t think Monzo webhooks have ever pushed updates to existing transactions.
This is the only pain point of using Monzo with YNAB, via Sync forYNAB for example. Every so often I have to manually go through and clean up any transactions which settled (or were removed).
I’m also working with webhooks and have them all set up relaying incoming transaction data to my server. Everything is working great, but I have a question about the data.settled value in the payload:
Unlike the data.created value, the time given in the payload is not the time as of the payment, or even a delayed payment. The time I receive for this is always a fixed very regular time.
For example for two payments that have data.created values of 09/10/2019 11:07 and 09/10/2019 10:52, I received that for both the data.settled time = the arbitrary time of 09/10/2019 13:45.
In fact, the settled time given is always one of the following three no matter when the payment was received:
08:00
16:30
13:45
