It is a known issue, it’s known that its Tesco at fault.
1 Like
As I said, I know it’s a known issue. I was simply outlining my experience for others and providing my thoughts on the situation 
Yep, so I’d sort of expect that this
wouldn’t [need to] happen.
Edit: added bracketed words for clarity.
We’ll you don’t have to believe me, but I’m just giving an overview of the experience I just had.
Edit: crossed wires from the reply above!
I do believe you. I believe it happened to you, and I believe it has happened before. So I’d expect Monzo CS to have come across it often enough to be able to sort it out without playing pass the parcel.
Sorry if I wasn’t clear enough
1 Like
Ahh I misunderstood your reply, thanks for clarifying. We’re agreed then that as this has been happening for a while, I wouldn’t have expected it to get moved around.
On the positive side, the first reply on chat was super-speedy 
1 Like
I could almost understand one person not knowing, maybe they are new (but I’d expect a list of common problems in the training) but no2 doesn’t and then on to no3.
Did you go through to chat via the help section or reported that actual transaction?
Via the transaction. To me, it almost seemed like the system was bouncing it around agents as it came at odd times in the chat (rather than the agent explicitly transferring) - not sure how their back-end works on this.
Update: Monzo have now logged this as a complaint (even though I never asked for them to). Let’s see what the outcome is!
2 Likes
Intresting to see the outcome.
1 Like
3 Likes
From the article linked above your post:
We have seen a handful of complaints about double-charging since Tesco said the problem was fixed. When we put this to the supermarket it told us (on 23 February) there are rare occasions where individual tills temporarily go offline and customers make several attempts to pay. It says these instances are not linked to the widespread issue outlined above but it will still reverse any duplicate transactions.
Also, see this very recent explanation from someone who works at Monzo:
Tesco’s card acquirer is Worldpay aka the old Natwest Streamline… And having dealt with them in a professional capacity they are an absolute nightmare, and to be fair they don’t just do it to Monzo customers…
1 Like
Not Tesco so slight deviation from the thread, however the payment gateway in this instance is WorldPay
At least Tesco haven’t quite had this issue yet 
2 Likes
Came here to post the same thing! 
2 Likes
Hi, Ruben from Monzo here (again).
I just wanted to drop a note to say that this should all be fixed now.
We put a patch live on our side on the 29th June (with a couple improvements that went live on the 5th and 6th) that made most if not all duplicate transactions to stop.
Then on the 21st July we were told that a fix had been applied by WorldPay. When we looked closer into it we noticed this appears to have gone live on the 19th July. By that point our patch should’ve made the problem vanish pretty much entirely, but it’s good to know that this is also now fixed at the root.
If you see any more instances of this happening, please let our support team know and they’ll be able to help out via our usual routes.
15 Likes
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.