[iOS] Different names for Monzo contacts in RECENT and PAY CONTACTS ON MONZO sections in Payments tab


Issue: The name that a Monzo contact used to set up their account is shown in the “RECENT” section of the Payments tab instead of the name in your contacts.

NB: The name in your contacts is shown in the “PAY CONTACTS ON MONZO” section of the Payments tab.

Details to reproduce: Pay someone using Monzo P2P who’s name in your contacts is different from the name they used to open their Monzo account ==> got to the Payments tab ==> scroll down to the “RECENT” section and note their name ==> find the same person in the “PAY CONTACTS ON MONZO” and note their name here ==> compare the two names.

OS: iOS 12.1.2

Device: iPhone 6

App Version: 2.28.0

NB: not sure if this counts as a bug or not, but it can be momentarily confusing if you’ve P2P’d someone who goes by a name different from the one they used to open their Monzo account (eg: name on passport might be Henry, but everyone knows them as Harry).

NBB: I’ve moved this back to the Bugs category as I think it’s more a UX bug than anything else.

[iOS] Name issue when Bill Splitting (+ creating & adding to Shared Tabs)
(Peter Reid) #2

The same behaviour can be produced on Android

The behaviour is as follows:

The names and pictures in the ‘Pay Contacts on Monzo’ section of the payments tab are sourced from your phone’s address book (at least this is the behaviour on Android, from memory I recall it is the same on iOS)

The names and pictures under ‘Recents’ are sourced from Monzo based on recipients you have paid - the name displayed is the user’s full name associated with their account, and the profile picture displayed is that from their monzo.me profile.

My opinion:

It would be nice to have the ability to have these pictures and names source from the same pool in my opinion, the disparity is confusing - I have a few contacts who go by their middle name or a shortened version of their name e.g. Martin --> Marty. Annoys me as much as it annoys you.

(Adam Kendrew) #3

Hopefully the upcoming payee management changes should solve this.