Core App: Better payments

I think you can have both. A nudge to encourage users to use Monzo, but still provide the freedom to choose and make alternative options easy to use.

2 Likes

I agree with this.

I also think that Monzo do make it very easy to do this: if you go `Payments tab ==> Pay someone’ then the options to Pay via a link or to pay someone new via bank transfer are at the very top; if you already have the relevant details stored, it’s then easy to either search for the payee you want or to scroll down and find them.

2 Likes

Curiosity question: if you have a credit card do you have the card issuer e.g. Nationwide as a stand alone payee or do you put the credit card as one of your accounts within your own payee?

I do the former but pondering whether the change to the latter to tidy up my payees :thinking:

1 Like

I assume this can be generalised to any accounts where the account name for transfer purposes is an institution/provider and your personal account at that institution is identified by the transfer reference rather than the account name and number.

In this scenario I’m undecided.

An issue that has arisen for me when I’ve moved such accounts into own payee list/card is the location those accounts end up in your list may not be quite what you expect.

For example, once placed in my own payee list/card my Freetrade account seems to come under L rather than F for listing purposes (I assume because they use Lloyds Bank).

And i’m not sure what’s happening with NS&I. This has been placed at the top of my list rather than under N. But I can’t figure out why.

1 Like

I have all of my credit cards and other accounts under one payee. I have around a dozen accounts there so doing it this way keeps it neat and tidy. @o99 my accounts appear in alphabetical order based on the account description…

2 Likes

Just changed the description on my Freetrade account so that its Freetrade instead of Lloyds and this has moved it away from L, but its still appearing after H.

Also the description on my NS&I account is National Savings and Investments but it still appears at the top of my list

Also TSB is appearing above Transferwise despite both these names being in the description field

So … :man_shrugging:

1 Like

Are you using the new “Payees hub” in Monzo labs?

Yes

Done a bit more playing around.

It seems I need to edit the description and then come out of the payments hub and re-enter for changes to list order to be displayed.

But NS&I still above Nationwide and TSB still above Transferwise. I can force them into what I would consider their correct location if I don’t use all caps. So Ns&i moves below Nationwide and Tsb moves below Transferwise (after editing and then coming out of payee hub and re-entering). Seems caps supercede alphabetical ordering on the second and subsequent characters of the first word in the description. I don’t agree with this approach.

2 Likes

@o99 @caribo perhaps this is an iOS-Android parity issues ?

I’m on iOS for what its worth

That’s pretty standard in all the text editors I use. I am personally fine with that as a result of prior experience, but then that is maybe not for everyone

2 Likes

I guess my primary experience with sorting stuff is Sort & Filter in Excel. It ignores caps.

1 Like

Had never come across/noticed this.

Fair enough if it’s a thing - but initially seems quite odd.

Rationale that all caps means it’s an acronym? And so as if there’s a space or full stop after first letter?

2 Likes

When you pay one of those cards, I assume you’re name is the account name rather than the name of the credit card, do you still get the warning that the name doesn’t match?

2 Likes

Android here!

Maybe it’s a bug… I would expect the list to be in case insensitive alphabetical order… and I’m sure many others would…

4 Likes

Yes, I would, for one.

It shouldn’t matter whether a payee is called TSB or tsb. It seems odd if it does?

2 Likes

This sounds fixable, probably just the case that they need to change the type of field. It’s standard in a lot of computing data fields for the case to be important, so it may be that it got set to a standard type and making it disregard case wasn’t even thought of.

Now the issue has been identified and raised here (and possibly those to whom it matters should report the issue in-app to COPs as well?), hopefully it should be an easy fix. (Unless it’s not an easy fix because they have to check changing the type doesn’t break something else in the app…)

1 Like

I imagine that they would have to test to make sure it doesn’t break anything but it shouldn’t do, so hopefully that would be an easy test and reveal no issues.

1 Like