Bank cards + type of payment system (including international and local ones) + expiry date + CVV/CVC

Regarding Tax ID - it is very dangerous thing, as every country has it's own format for Tax ID, so Tax ID itself without country's name is nothing. Or one will need to implement arbitrary text field for it (as tax id could be number or numbers + letters). The same for passport numbers.

Item types and templates are the biggest issues for me, trying to migrate from Datavault. There surely are some very common ones, like bank account, software activation keys, local user accounts and logins to encrypted volumes...
Notes are a workaround for some of that data, but it would be nicer with dedicated fields in a vault record. Very often there always is a basic "login name" and "password" situation and some extra fields that vary. Maybe the most elegant solution is to let users create their own custom vault record types.

Also SSH Keys would make sense. 1Password has this and it works great.

One could create their own vault, but in particular the option to create and share Wifi-QR codes would be a helpful new feature!

This would be HUGE especially with some older video games/programs need a serial key or subscription authorization.

Allow users to store Wi-Fi passwords in the app.

I'd suggest a broader approach : let users add custom fields and. sections to all types of items including notes. Better even, user defined templates.

Yeah honestly I also have non-Credit card payment options which I'd like to store. Here in germany we have Girocards which allow you to pay but they have different field which makes it impossible to store. I could maybe use a dummy login for my card but when I switched over from 1Password I was able to use the normal card type there. No idea why it's so restrictive

Yes, in my country there's a couple of extra fields that are usually asked for when using cards, and it'd be more convenient to have that information in the entry.

Today I needed to store extra information for one of my cards, and I realized cards don't support custom fields.

Obviously manually filling in credit card numbers on a website sucks. Or even copying them in. Not the end of the world, but is a basic feature in probably every other major password manager.

Just noticed these don't exist. Didn't come over on my import from 1Password as a result. Can always look back to 1Password for these, but never sure if something had custom fields or not. Also, as I add new credit cards there's nowhere to put any custom fields since 1Password is only there for me now for what was there when I dropped it for Pass. Can't update it anymore.

This would be very nice as having Pass Monitor flag all my pins as weak passwords reduces the usefulness of Pass Monitor

I miss all the points mentioned and are almost essential and critical for me. Unfortunately, I'm thinking about staying with the competitor again.

Forms often require separate first name and last fields. It would be nice to have Proton Pass fill these in from the identity. Currently, it places the full name in the first name fields on a website

I have an idea for a new feature that I believe could greatly enhance the security and convenience of managing our personal documents.

Feature Idea:

I propose adding a feature to the Proton app that allows users to securely store their ID photos, driver's licenses, and other important documents. Additionally, users should be able to generate attachments with watermarks specific to the recipient (e.g., "Assurance XYZ") when they need to share these documents with third-party services. This would help prevent the misuse of these crucial documents if they are stolen or lost.

Benefits:

Enhanced Security: By storing documents in the Proton app, users can protect their personal information from theft and loss.
Convenience: Users can access their documents anytime, anywhere, without the need to carry physical copies.
Authenticity and Fraud Prevention: Watermarks ensure that the documents are authentic and unaltered. Moreover, if a document is stolen, the watermark (e.g., "Assurance XYZ") prevents it from being used fraudulently with another service (e.g., "Bank ABC").

How It Could Work:

Users upload their documents to the Proton app, where they are securely stored.
When a document needs to be shared, users can generate an attachment with a watermark specific to the recipient directly from the app.
The app ensures that the documents are easily accessible but also protected against unauthorized access.

I believe this feature would align well with Proton's commitment to privacy and security. I would love to hear your thoughts and feedback on this idea!

Thank you for considering this feature request.

All others pwd managers have AT LEAST bank accounts

This feature will be great , to have the ability to manage your software license

It would be useful to insert additional fields in card type records. Banks add a two-factor system with 3DS security code but it is not possible to add it in the card data