Credit Card payment form date field creates impossible dates
In the date field, for a credit card payment, almost all other payment apps will format the string "326" as "3/26", which is the only possible valid interpretation of that string as a M/Y format. Your date field, however, generates the impossible date: "32/6". A user should not have to prefix the month with a zero "03/26" if the initial digit for the month is in the range 2--9.
ANDREW A ANDA
shared this idea
-
Ramon Fritz
commented
It seems like the issue is with how the date input is being parsed and displayed. The form might be misinterpreting the input and creating invalid dates. It would be helpful to adjust the input validation to recognize that a "326" should default to "3/26" instead of "32/6." This can be fixed by tweaking the formatting logic for the month/year fields to ensure it handles the input properly.
Hope that helps! By the way, if you're interested in packaging solutions, you can check out Mailer Boxes from Birmingham Packaging. https://birminghampackaging.co.uk/mailer-boxes/