I’d hope no one is offended by anything written here. That’s sort of the point I was trying to make!
4 Likes
Interesting note, I had an email from bulb apologising for their payments showing as stripe
"Just so you know, your payment to Bulb on 18 November might be showing on your bank statement as “Stripe”, rather than the normal “Bulb Energy”. This was a mistake, and we’re very sorry if this has caused any confusion.
Stripe is the FCA regulated company that manages our card payments. There was a hiccup that caused a few of the payments to be named after them, rather than after us. Don’t worry, we successfully received your payment, and everything else looks absolutely fine.
We’ve fixed the issue that caused this, so we shouldn’t see this problem again in future. We’re very sorry for any trouble that this might have caused."
2 Likes
I’ve explained why that type of statement makes no sense & the potential harm it causes -
as for this comment -
the team has acknowledged the issue & the fact that it’s been fixed earlier in this thread -
I could be wrong but criticising Monzo for not doing something that they’ve done seems likely to cause people to disagree with you.
1 Like
What I took from this, was that I called the bank (Lloyds) to query the Stripe charge and they could not tell me anything about it and yes part my fault that I did not connect the dots but when I call a bank regarding a transaction I would think they would be able to help me understand the payment. I would say it was them that panicked and they decided to cancel my card and because I had money on my Monzo I just agreed.
They have not done it properly though. No email or in-app alert sent to anyone just to assure people concerned to see this happening
That’s a separate point to the one I was making.
Since we don’t know how many users were impacted, we can’t judge whether or not a notification (which is annoying if irrelevant) is was needed. It looks like it wasn’t. Personally, I wasn’t affected by this issue.
2 Likes
Some of you may have been affected by a bug causing Monzo debit card top ups to appear under the name Stripe on your bank statement.
Most top ups made from the 16th-21st of November have appeared under the name ‘Stripe’ (our third party top ups processor) rather than Monzo.
If you made a Monzo debit card top up during this time, and have noticed a transaction of equal value on your statement with the name ‘Stripe’, this is very likely to be an incorrectly named Monzo top up.
It’s worth mentioning that top up debits can take a couple of working days to appear on your bank statement, so if you’re unsure if this bug has impacted on a recent top up you’ve made, you can compare the date of the credit in your Monzo app to the transaction date on your bank statement. Or message us for some extra clarity 
The issue has now been resolved and shouldn’t impact any future top ups made after the 21st of November.
Apologies for any confusion caused! If things still look at bit unclear, let us know and we’ll be happy to investigate further for you 
3 Likes
Sorry it took us so long to investigate this! As you fine folks already worked out (above), this was an issue on Stripe’s end, not ours.
We only heard back from Stripe with a list of affected top ups yesterday. We’ve now messaged all affected users to explain the issue: hopefully this will avoid any further confusion 
8 Likes
This was a specific issue that has now been resolved. As a result, should this occur again it should be reported in its own thread as a new incident.