Bitwarden fills credit card expiration date with the wrong format

Ask the Community Password Manager
,
1

My credit card expiration date is 11 / 2026. When I fill the credit card data using Bitwarden, the expiration date is filled 20 / 26. This logically results in an error message because there is no month «20».

There are payment gateways that expect the year as a 4 digit number and other gateways expecting the year as a 2 digit number. Bitwarden seems to be unable to handle this circumstance automatically, right? Is there a solution on the roadmap?

1 Like
2

Hello,

You’re absolutely right. Bitwarden currently struggles with automatically filling expiration dates in the correct format (MM/YY vs MM/YYYY) due to limitations in how it detects the expected format from websites.

There isn’t a confirmed solution on the public roadmap yet, but there have been discussions about improvements.

Here are some workarounds until a fix is implemented:

Manually edit the expiration date in Bitwarden before filling the form.
Copy the entire expiration date (11/2026) and paste it into the form, letting the website handle the format.

I hope the information may helps you.

Best regards,
Dennis Leon

2 Likes
3

Problem persists.

4

I provided a more extensive response to your comment in the other thread.

Here are some examples:

5
  • CodeSandbox demo page: Works perfectly for me too.
  • Roboform demo page: Card Expiration Date field «year» was blank
  • Payform demo page: Card Expiration Date both fields are filled wrong
    By the way: I do not like this form, it feels somehow clumsy to enter the credit card data in two steps. In step 2 I do not see the credit card number any more.
6

@crimle What browser (including browser version) and what browser extension version are you using? And in your Bitwarden card item, what format are you using to store the Expiration Year?

7

I tried with both:

  • Microsoft Edge Version 130.0.2849.80
  • Firefox 132.0.1
  • Bitwarden Version: 2024.10.1
  • Server-Version: 2024.10.2
  • Expiration Year: was «26». Changing it to «2026» resolved the issue. Thank you for bringing this idea to my attention.
8

Yes, storing the expiration year in the format YYYY is required for the expiration date autofill to work reliably. Perhaps Bitwarden could do a better job of sanitizing the data stored in this field.

Glad the issue is resolved for you. There will still be certain payment forms that will not autofill correctly because of the way that they have been coded, but ensuring that the expiration year is stored in the correct format should greatly improve your experience with autofilling of card data.

9

Have noticed this issue for quite a while now and surprised it hasn’t been fixed yet as it makes autofill pretty useless. Really hope this can be fixed soon.

10

I agree that autofilling not working properly makes it useless and is a nuisance. On the other hand, there are so many paying gateways and they are using many different field formats. This obviously makes it difficult for any add-on to guess the format. I would appreciate if the paying gateways could agree on a uniform standard.

2 Likes
11

This use to be fine tho, and my old google password manager left overs still get it right if that option still appears for me.

I think previously, year use to be saved as only 2 digits, maybe that’s why it use to work in the past?