Data Import from Dashlane fails to capture and protect Payment Card details correctly

[Beweeted]

Steps To Reproduce

1. Create new account
2. Log in to BitWarden website
3. Use tool to import data from Dashlane (competing service)
4. Include credit card/payment data in data import

Note: issue occurred during account migration earlier this year, but only discovered today. Apparently I haven't been doing much online shopping lately.

Expected Result

Card data is imported, with correct data loaded into the correct field.

Additional protections for sensitive data are applied to these fields.

Actual Result

Card data fields are blank. Data import loads data into custom fields.

Issue applied on 5/5 payment cards in my account data.

Screenshots or Videos

Additional Context

No response

Operating System

Windows

Operating System Version

No response

Web Browser

Chrome

Browser Version

No response

Build Version

Unknown

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-43202
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-43202

[MarikaBW]

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time – our engineering team will be happy to review these.

Thanks once again!

[breken-ai]

Thanks for the report, @Beweeted. We root-caused this one: your screenshot shows the imported rows carry type=payment_card, which is Dashlane's current CSV export value for cards - the importer only recognized the legacy credit_card (and bank), so the row fell through, left every card field blank, and dumped everything into custom fields. The cardholder name also moved to a separate name column in the new export.

Fix is up here: #23064 - payment_card rows now import as fully populated cards again, with the legacy format unchanged.

Built by breken, your AI support engineer - breken.ai finds the bug, proves the fix with unmatched RCA, answers customers in your voice, and keeps your code and support docs clean - this one's on us.