How long to fix this? I have reset the app and cleared cache.
I’ve generally found that when in the ‘Home’ display, simply tapping on ‘Payments’ and then on ‘Home’ forces a refresh of the Home screen (
)
Didn’t work unfortunately 
I fixed this the other night, if it’s still showing incorrectly it’s likely a caching issue on your device. Try deleting and reinstalling the app and it should be look all good 
One thing that I’ve discovered, which is probably because the tooling isn’t sophisticated enough, is that transactions through a third party with a prefix (like Curve with *CRV) are usually in different merchant groups.
So the Co-op is still called “The Co-operative Food” when you pay with Curve. Correct logo, though.
(Curve transactions also got changed from online to geolocating by what’s presumably Curve’s head office a year or so ago. Which really messed things up).
“Fenton”
Haha literally came to mind as well so glad you posted this.
Are there any further updates on PayPal transactions to Patreon still ignoring the transaction info and just listing them as PayPal?
Most or all other PayPal transactions are being categorised just fine, it’s only Patreon ones, even though the detail is in the same format (PAYPAL *MERCHANT_NAME other_stuff). It used to work fine unti November last year, even though the detail is in the same format as before and other PayPal transactions are fine. It almost seems like someone manually changed it to give less specific enrichment.
This has been reported a couple of times and was also being looked into here but I guess it got lost along the way somewhere.
I have some merchant names that are misleadingly incorrect, so i sent a message in chat. The very kind COps offered to correct it there and then, and asked me to DM her the correct names. I spent time going through them, getting the names and logos for her.
Then someone else replied and told me that wasn’t the right way to do it, and I’d have to submit them in app.
I understand that staffing priorities mean they can’t work on these - fair enough. But then don’t make me do work and then shut the door in my face. It’s a waste of everyone’s time.
Yet another classic example of Monzo’s left arm having completely no comprehension what the right arm is doing, sadly.
I’ve said it over and over, from what I’ve witnessed, there is something fundamentally wrong with the way Monzo customer service is structured. It began around the time the bank built its own chat engine, and I suspect that has entrenched the inability to do anything easily.
I agree that problems seemed to start when they moved to their own one-thread chat system.
They’ve not touched ones from months ago, if you’re not going to be fully invested in ensuring the enriched data is kept up to date then what’s the point.
I get for the majority they might never see a problem, for them I’m jealous of them 
Ouch. That kind of behaviour is one of my pet peeves sometimes in my own work - don’t make a colleague’s mistake the customer’s problem. Generally we can finish dealing with the customer, explain (if caught in time and if necessary) that whatever we did we would not be able to do again, and use it as a teaching moment for staff later (making mistakes isn’t necessarily a problem; they are opportunities to learn and do better next time).
In this case, it sounds like you may have DMd the information after the first COp had gone off shift, and instead of the message waiting for her to clock back on, it got sent to a different COp instead who misread the room and decided to be a rules lawyer about it. One of the many problems with having a One True Chat Thread instead of a multi-messaging system. Even if they’re technically right, it’s not a great look to follow up a colleague’s offer of help by metaphorically crossing your arms and being like “Well I’m not going to go above and beyond, mate”.
In some respect, what potentially makes it worse is that in the past, Monzo staff have said that when old submissions from months ago don’t appear to have been touched, it’s usually because they can’t see from the report what’s actually wrong (or they can’t verify that the new information is correct). So if someone’s sending a message for that reason and then gets told to self-report… that’s not going to go down well.
Ach.
I just don’t see any evidence that this bothers monzo 
Have a look at a later reply:
All fair points, except that not ALL of my changes were from years ago (in fact all of the ones i dmed the COps were a few weeks old). And also also also: the rules change from one COp to another. Don’t ask me to resubmit if you’ve already decided you don’t want to input the changes.
I’m fine with them not prioritising merchant data. But don’t encourage me to do Monzo’s work AND THEN tell me to get lost.
I know this a ridiculous thing to get angry about (I’m very very aware!) but I can’t remember an incident at Monzo that has infuriated me like this has.
Raise a complaint. I think that’s a fair response, given you did what was asked in good faith, then dismissed.
Sadly, that’s what happens when too many COps looking at the same case 
Newbie COps need better training on such matters 
If COps not sure about something 
, they should report it to senior staff member(s) instead of winding up customers throughout the app chat 
I’ve submitted quite a few suggestions recently, including one for card payments to my company (which also has a Monzo business account) - none of the changes I submitted have been applied…
It’s such a shame that one of the “key features” Monzo launched with is now done better by some high street banks…
Still a bit shocked that Revolut seem to have no way to submit corrections
Do these other banks, or are they just getting the main ones correct as well?