🚧 Display credit card numbers in groups of 4

Currently, in the Bitwarden mobile app (Android/iOS), when viewing payment card details, the card number is shown as a continuous string (e.g., 6374892012345678).
This makes it hard to read or verify the numbers quickly.

On the Bitwarden desktop app and browser extension, the card number is displayed as 6374 8920 1234 5678, which is much more readable.

Suggestion

  • Please display the card number in the mobile app in the same grouped style as the desktop and browser extension versions, making it easier to read.

Copying should still copy only the digits, as it does now.

@Owen Welcome to the forum! I have moved your post to an existing feature request on the same topic.

Any timeline when this will be on the roadmap? Looks like it’s been 4 years since initial request.

@Kiet Welcome to the forum!

This was reported as a bug on GitHub a few weeks ago and it seems they “acknowledged” it:

(though in the Android section reported, it was mentioned, the iOS app should be checked and fixed also)

PS: FWIW, I changed the tag app:all to app:mobile now, as it’s only (still) missing in the mobile apps.

1 Like

Long time paid subscriber here. I have a feature request for the Desktop/Mobile apps that I think would be invaluable for UI.

When storing a card in BW, the Card number is displayed as:
4XXXXXXXXXXXXXXX

It would be great if the UI formatted it and displayed it as:
4XXX XXXX XXXX XXXX

That way when manually copying it is far easier to ‘chunk’ the numbers for easier memory. When copying the number via copy/paste, it would still copy as the raw number without any spaces.

Thanks if this can be considered. Currently it is hard to read when manually copying and reviewing a card number, especially with repeating numbers.

@PracticedCommiter Welcome to the forum!

I merged your request with an existing feature request to the same topic.

At last, after a minimum of five years we see Card numbers in groups of four digits (iOS). :partying_face: :tada:
Well, I am happy to see that this feature request from May 2020 is implemented.

But, I am sorry, I still wonder: Why 5 years for implementing it?!

Not yet on Android…

2 Likes