How to Use Custom Fields for PINs, Security Questions and More

Most password managers store a username and a password per site. That works for simple logins. But plenty of websites ask for more than just two fields. Your bank might require a customer number before the password screen. An insurance portal might ask for a policy number. A corporate VPN might need a PIN in addition to your credentials.

Custom Fields in UnveilPass let you store and auto-fill these extra pieces of information alongside your regular credentials. They are encrypted with the same AES-256-GCM zero-knowledge encryption as everything else in your vault, and the browser extension fills them automatically on matching pages.

What Are Custom Fields?

A custom field is an additional data entry attached to a vault entry. Each field has three properties:

• Name: The identifier used to match the field on a web page. This should match the form field's name, id, placeholder or aria-label attribute.
• Type: The kind of data stored (Text, Hidden, Password, Checkbox or Tel).
• Value: The actual data to store and fill.

Custom fields are stored in the customFields array inside the encrypted vault entry JSON. They travel with the entry — if you share the entry with a team member or a contact, the custom fields are included in the encrypted payload.

Field Types Explained

The type determines how the value is displayed in the vault entry detail view and how the extension interacts with the matching form field on the page. Password-type fields are masked in the UI, checkbox fields toggle the matching checkbox element and tel fields target phone number inputs.

Common Use Cases

Here are real-world scenarios where custom fields solve problems that a simple username-and-password entry cannot:

Bank PIN codes. Many banks require a separate PIN during login — either on the same page as the password or on a subsequent step. Create a custom field named to match the PIN input field on the bank's page (for example, pin or accessCode). Set the type to Password so it stays masked in your vault. The extension will fill it automatically alongside your username and password.

Security questions. "What is your mother's maiden name?" and "What city were you born in?" are still used by many websites as a secondary authentication step. Store each question's answer as a custom field. Use random answers for better security — since the extension fills them automatically, you do not need to remember them.

Customer numbers and account IDs. Utility companies, insurance providers and government portals often require a customer number or account ID in addition to a password. Store it as a Text-type custom field and let the extension handle the filling.

Date of birth. Some sites ask for your date of birth as part of the login or verification process. Add it as a Text field. The extension will fill it into the matching input on the page.

Membership and loyalty IDs. Airline frequent flyer numbers, hotel loyalty program IDs and gym membership numbers can all be stored as custom fields. When you visit the loyalty program's website, the extension fills the ID automatically.

Software license keys. If you log into a software vendor's portal with a license key, store it as a custom field on the vault entry for that vendor. No more searching through old emails for activation codes.

How Auto-Fill Works with Custom Fields

When the UnveilPass browser extension fills a page, it does not just fill the username and password. It also scans the page for form fields that match your custom field names. The matching process checks four attributes on each form element:

1. name — the HTML name attribute of the input field
2. id — the HTML id attribute
3. placeholder — the placeholder text displayed in the empty field
4. aria-label — the accessibility label attached to the field

If any of these attributes match the custom field's name, the extension fills the value using the same robust injection method it uses for usernames and passwords — including React compatibility, native event simulation and framework-specific workarounds.

Adding Custom Fields: Step by Step

Here is how to add custom fields to a vault entry in the UnveilPass web console:

1. Open the vault entry. Click on an existing entry to edit it, or create a new entry with the "New Entry" button.
2. Go to the Fields tab. The entry form has three tabs: Credentials, Options and Fields. Click "Fields" — this is where custom fields live.
3. Click "Add Field." A new row appears in the custom fields table.
4. Enter the field name. This must match the target form field's name, id, placeholder or aria-label on the website. Be precise — customerNumber and customer_number are different names.
5. Select the type. Choose Text, Hidden, Password, Checkbox or Tel based on the kind of data.
6. Enter the value. Type the data you want auto-filled — your PIN, your security answer, your customer number.
7. Save the entry. The custom fields are encrypted alongside the rest of the entry data and stored on the server as ciphertext.

You can add multiple custom fields to a single entry. The fields are displayed in a paginated table (10 per page) within the Fields tab. You can edit or delete individual fields at any time.

Practical Example: Setting Up a Bank Login

Let us walk through a complete example. Your bank's login page has three fields:

• A customer number field (name="custId")
• A password field (name="password")
• A PIN field (name="pin")

Here is how to set up the vault entry:

1. Create a new vault entry with the bank's URL.
2. On the Credentials tab, enter your customer number as the username and your password in the password field.
3. Switch to the Fields tab.
4. Add a custom field: Name = pin, Type = Password, Value = your 6-digit PIN.
5. If the bank has a separate customer ID field that is different from the username field, add another custom field: Name = custId, Type = Text, Value = your customer number.
6. Save the entry.

The next time you visit your bank's login page, the extension will fill all three fields automatically — username, password and PIN — in a single action.

Tips for Getting the Most Out of Custom Fields

• Use the browser inspector. Always check the actual HTML attribute names of the form fields you want to fill. Guessing the name often leads to fields that do not match.
• Test after setup. After adding custom fields, visit the target website and verify that auto-fill works correctly. If a field is not being filled, the name probably does not match — inspect the element again.
• Use Password type for sensitive data. PINs, secondary passwords and security answers should use the Password type so they are masked in the vault UI.
• Use random security answers. Since the extension fills them for you, there is no reason to use real answers. Generate random strings — they are more secure and impossible to guess from your social media profiles.
• Keep field names exact. The matching is case-sensitive. Pin and pin are different names. Copy the exact attribute value from the page source.

Custom Fields and Sharing

When you share a vault entry with a contact or a team, custom fields are included in the encrypted payload. The recipient sees and can auto-fill the same custom fields you have. This is particularly useful for shared corporate accounts that require additional login fields — everyone on the team gets the full set of credentials in one share.

Permission levels apply to custom fields just like they apply to the rest of the entry. A team member with read-only access can view and auto-fill the custom fields but cannot modify them. A member with read/write access can update the values.

Summary

Custom fields extend your vault entries beyond the standard username and password. They let you store PINs, security question answers, customer numbers, license keys and any other form field data — all encrypted with the same zero-knowledge AES-256-GCM encryption as the rest of your vault.

The browser extension fills custom fields automatically by matching the field name against form element attributes on the page. Set it up once and never manually type a PIN or security answer again.