It would be cool if this number only reflected the number of US customers
If Joint Accounts don’t keep their own count, I don’t see why US ones should. 
4 Likes
The aim is to get to 1bn globally, so it’s good to see where you are on that overall journey. I was one of the first non-staff on Android, but my number is in the thirty thousands, cos it was launched so long after iOS. Breakdowns of any sort just add complexity.
1 Like
Highly unlikely - Monzo won’t have multiple customer tables in the DB, they’ll have one.
1 Like
I wonder if compliance with US banking regulations involves having data stored on servers within the US? Probably. In which case there would be a second set of data, independent of the current UK database.
3 Likes
What he said. This isn’t the reason. Even if it were, it’s trivial to manipulate DB data, that’s kinda the point.
2 Likes
You could easily create views that would show the sequence within different groups
4 Likes
Yes but why have two customers with customer number 1? Even if you have a separate customer reference, there’s just no point.
6 Likes
It’d likely just be @anon77247897 that is number 1 on both, anyway! 
Because they are the first US customer and the first UK customer obviously. It’s basic database architecture.
1 Like
There is the overall customer number and then internally there is probably a 2nd number of the product UK/US/Joint/Business it would be nice if they displayed that I guess.
1 Like
I mean it in a way that it would be pure curiosity and joy rather anything functional. Sometimes the former is more important 
3 Likes
i was poking around the app today when i noticed that my user count is now in the hundreds instead of the millions 
1 Like
Looks like it might have happened then!
1 Like
I presume as a result some UK ones will have had their user number drop too?
2 Likes
Interesting point!
1 Like