I’m really struggling to understand the amount of sleuthing that is required. Where are you shopping where this level of scrutiny is required so often? I’m not having a go here, I’m genuinely curious as this is so alien to me. I’m obviously not on the same wavelength at all.
Between live notifications, categorisation, a searchable feed and using the known transactions on either side of the mystery one(s) I’m really not understanding how hard it is to find the unknown transaction(s) shown on your statement within your transaction feed in app by comparing dates.
I know you mentioned earlier that you won’t always have an Internet connection but in those cases surely you would have access to your statements then either?
Sounds like the MCC in some cases will just add to the confusion.
I’m more inclined to think along the lines of what @Rika said…
That’s exactly what I’m trying to do but sometimes the best answer is to change tact and find new ways to use the tools you have available at the moment.
I didn’t say that. What I said was often it’s impossible to tell what the merchant was without additional metadata which Monzo have but which they don’t give me.
Er, what about my examples was hard to understand?
No as it allows you to work out the patterns and, again, as already mentioned multiple times, is necessary for troubleshooting cashback issues.
I appreciate Rika’s point. And again, I’m not saying it needs to be in the feed. But what possible circumstance is there where providing more information to those who want it is less useful?! I’m sorry, that claim is trivially completely bogus.
I’m pretty sure if there were another way I’d already be using it. And again this does not address the cashback issue.
This info is incredibly useful for gaining points.
And diagnosing why points were not dolled out.
In have always had this info and Monzo does not provide it so it is a reduction in features for me. something I have been used to since I got my first card at 12. These were US institutions.
If it’s the MCC in the top left then the Amex app shows these quite nicely. Interesting to see they can distinguish between Sainsbury’s fuel and Sainsbury’s groceries too. I also really like the way they display that the transaction was via Google Pay.
The problem for Monzo is that they already have their own categories so I’m not sure these could fit in the app easily. They could go into statements but having both Monzo categories and the MCC - even if only the MCC is displayed in the statement could cause a huge amount of confusion for your average user who got Monzo because they were stood in a bar and noticed that everyone else had an ‘orange’ card.
Perhaps the best solution is improving on the already existing Monzo categories and perhaps then having a way of clicking into the auto assigned category and seeing the MCC that powered the decision?
As for whether Monzo should build it and whether people will find it useful, I’m not going to go into that, but there have been numerous calls on here for better categorisation and this could easily be tacked onto any work done there.
Yeah don’t see any issue people could claim to have with this or any other obvious elegant ux solution.
It is the MCC in the top but that’s already been translated. It’s best to have the raw value too as translated databases can vary.
It’s clear several other providers give this information in a way that isn’t confusing customers so that tired argument can be laid to rest once and for all.
Sorry I thought the implied point was already clear without typing it all out. Point is Curve do pass the MCC through!
In addition to Curve cash, the way you use this for Monzo is to use the go back on time feature. That’s why it’s useful to have on your main spend card if you are full Monzo or whatever. At the moment I have to put my spending through other cards and can’t use Monzo because I don’t get told the MCC.
Anyway, how does that allow you to conclude that Monzo shouldn’t offer this?!
They just use a proprietary translation database and don’t give us any access to the actual value they use.
The proposition is simply to keep their proprietary translation but also tell us the data they originally derived it from! Allowing us to categorise more accurately can only be a good thing, surely?
I don’t think any of this is helping get votes for this suggestion, it’s causing the points to get lost amongst the circular bickering which is why people keep asking what they are.
I think everything has been said 10x over, so personally I’d let the votes do the talking from now
No idea how people are still querying the use or the possibility of an elegant ux solution when both have been made abundantly clear by now. Your original counterargument was that too much information with confuse people but I think that can be laid to rest now
I didn’t think it would be so hard for people to just accept it is useful for points and troubleshooting either…
It would help if the summary wasn’t clogged up with the least helpful votes. I think with all the people refusing to understand the point, a chance of a concise and convincing reason has been sabotaged.
