Hooray! Balance now shows correctly and I’ve at least learned my lesson about disconnecting it from not being able to reconnect. Transactions up to 17th December are showing so hopefully just a matter of time
Edit: All the other transactions came through now after I made another one today
Hmm.. After it started working earlier, I’m now getting a connection broken message, and I can’t reconnect it - though I wonder if that’s related to my fraud report earlier.
Mine’s just asked me to renew access to barclaycard. All recent transactions and balance are showing correctly again. The banner still shows about the issue though. However, all previous transactions assigned to custom categories are back to the original defaults which is a right pain to go back and change them all to where I had them all
Hey Joe Sorry for the delayed reply. I think there’s a bit of a misunderstanding here about what changed and where the constraint is.
For Barclaycard credit cards, Barclays don’t provide a stable transaction identifier at all That means any reconciliation across fetches has to rely on a derived identifier.
In our case, that identifier was built from the booking date and amount, for example: 2025-12-02T20:41:14Z§GBP 15.00
Barclays then changed the data they return so the booking date no longer included a time component, which means the derived identifier now looks like: 2025-12-02T00:00:00Z§GBP 15.00
At that point, previously stored transactions can no longer be reliably matched with newly fetched data — there isn’t enough stable information in the payload to do so. This isn’t something that can be fixed purely by “changing our logic” without risking incorrect reconciliation.
We spent a fair amount of time exploring alternative approaches, but without a stable identifier from the provider, there isn’t a safe way to uniquely identify transactions across fetches.
If working on exactly these kinds of problems sounds interesting, we are always hiring: Careers at Monzo
Hey @Urpert I’m not close enough to the complaints team to give a detailed answer. My understanding is that each complain is assessed individually which means even if customers are running into the same issue, the complaint outcome can be different. If you have further questions you can also chat to use via the in-app chat
Hey @dinosm I’d assume that NatWest aren’t attempting to reconcile transactions that they fetch from Barclays across different days. They’ll display in their app whatever data Barclays in that fetch. This does mean that customers can pretty much always see their latest transactions, but limits how “native” those transactions feel.
At Monzo we want connected account transactions to feel like Monzo transactions and part of that means we can’t just do what NatWest is doing. I hope that gives you some useful information
I understand your issue. You should be getting a transaction ID from Barclays rather than deriving an identifier from any of the other data! If Barclays are genuinely not providing this then they’re not following OBIE. Otherwise, it’ll be an integration issue on the Monzo side. Given it’s not affecting other banks, that does seems more likely.
Thanks for the role signpost too. I’m currently heading up a data team at another FS organisation but will keep you in mind
Balance is updating but transactions aren’t showing again. Anyone else? I’ve just upgraded my card but after a disconnect/reconnect it’s still the case.
Meanwhile, my M&S (not Barclays) credit card transactions are still not coming through. The last one showing was on 26th November! And I usually have 20-30 transactions a week!
This means I’ve been unable to do my household accounts or budgeting for two months.
Aaaand no new transactions again since Monday. The fact it keeps working then stopping again is quite confusing. Anyone else having the same? Seems to be very little consistency