We started building this quite a while ago, but it was put on hold. Fingers crossed it’ll be picked up again soon.
Without a deep understanding for how mastercard works it’s quite hard to explain why it’s complicated. But in short, merchant data is fairly unreliable, the same merchants don’t always use the same codes and there is a lot of ambiguity with what different people would consider the same merchant.
For example: Imagine if every Tesco store in the UK used a different merchant code (it’s not quite like this but gives an idea). Then are Tesco express, Tesco, Tesco online and Tesco petrol all the same merchant?
For context - we have a weekly scheduled task to update our gambling block list because new merchant codes come along all the time. Now imagine scaling this up to every merchant in the UK.
It’s not complicated to the extent that it’s impossible - but we want to get it right and over the past year, i’m afraid there have been other priorities.
Revels, I have obviously read the thread before posting and I am contributing - if I wouldn’t put my point forward, y’all would have closed it simply by saying “seek help” or “not Monzo’s job” which is simply ridiculous. This can be fairly easily done for competent people and someone like Monzo who has a team competent team behind would have no problem integrating a simple, merchant blocking feature within the app.
I agree that explicit is usually better than implicitly, so let me take some time and put forwards my POV…
Firstly, as said by @redshift - “Merchant blocking was definitely being worked on in January, but I’ve not heard of anything since then.”
This means this is likely possible, otherwise, the team would have not spent time working on the feature - however, it sounds like it just fell through the cracks, quite possibly due to more urgent platform features needing to be added?
Secondly, everyone else in this thread keeps suggesting that “this forum shouldn’t be your main option for addressing the issue” and “Ultimately, you have to seek the help to solve your dependency on it.” and “The friction you seek honestly, does not lie within Monzo’s gift.” which although good advice in certain scenarios, we should mostly focus on resolving/working around the issues that would not allow us to implement such a feature which, so far, I cannot read any that stand a valid point in this thread.
Thirdly, we got to the point the OP has disabled their card, ordered a new one and have to chat support up to block certain merchants? Seriously, is this what “advantage” we offer over Barclays? (Which by the way has this feature already implemented)
Therefore, can we please stop trying to find a workaround/solution in the OP and rather focus, constructively, on why this feature cannot be implemented? What technical, infrastructural or legal/legislation issues are we facing here?
Hey @TheoGibson thanks for the reply. This is very useful - what I had in mind is a “ban list” where you could take these codes for example from past transactions (imagine an option from the past transactions view that could ban that specific merchant). This can possibly cater for the scenario where I order from my local Domino’s for example, but I agree it will not be fitting to all Domino’s outlets, or especially from other merchants which might be a franchisee - in which case I imagine would have different “code”?
I wonder if there’s any publicly available data sets for these “codes” that connects retailers/franchisee/parent companies that could be used?
Ultimately, this thread bacame one about merchant blocking (@cub’s original post). The crux, though, as pointed by a number of us, is not about what a bank (or bank forum) can do for you. Talking about merchant blocking obscures the issue. The solution should be sought elsewhere…
Thanks @Demmedelusive, however, this is the point I am trying to get across: whether it obscures the issue or not should not be very relevant, at least to us/Monzo?
See it this way: it’s not really our place to say whether Cub should seek help elsewhere for a problem/something that is not a problem yet/something he or she has not realised is a problem yet. We don’t know him/her and it could even be that with such a feature, him/her might not even have a problem at all. I know for one that with this feature I would stop ordering food online and actually get off my lazy ass and cook at home
So what I’m saying is that if we were to, for example, change the issue from ordering from fast food to spending money gambling, all that has happened so far in this thread is to suggest seeking help rather than support the addition of a feature to stop gambling transactions. Certainly not the best example, but you get the gist!
Therefore, that’s my problem - rather than focusing on supporting this feature, we’ve been mostly telling the OP to seek assistance somewhere else because it’s an “addiction” (not sure about the right word) and call it a day. Obviously, there were some other suggestions such as getting Monzo support to block xyz merchant via the chat or re-ordering a new card? In my opinion that creates so much friction and time/money lost (create new card, have Monzo support dealing with query to block a retailer) when a simpler feature to block xyz merchant from previous transactions view in-app could be implemented.
Finally just to reiterate, it’s not really our place to say whether or not this feature can “cure”/“solve” the problem, but it surely can help and that’s why I do not see any reasons for the community not to support it.