Expiration date – maxlength issue

  • Resolved obrienjc2020

    (@obrienjc2020)


    2 years, 4 months ago

    The braintree plugin allows for inputting cc expiration month / year in up to 6 digits, i.e. 04 2025, but it on submittal, it expects the result to have been input in the format of 4 digits, i.e. 04 25.

    Error notice when this value is input incorrectly is blank to the customer.

    Is there a workaround for this?

Viewing 5 replies - 1 through 5 (of 5 total)

  • Hi there. I’ve set up a test site on my end and was able to checkout using both formats(25 and 2025). Does any error gets logged on your site?

    You can see the logs by going to **WP Admin → WooCommerce → Status → Logs**. You’ll need to select the correct log file which is created dynamically so you’ll have to try the different files available.

    Thread Starter obrienjc2020

    (@obrienjc2020)

    Unfortunately, no error is in our logs. This issue was reported to us by a customer. He sent us a screenshot showing the woocommerce notice area, but it was blank after the !. Normally if there’s an error with the credit card info, it’s displayed in some detail. We went through his entered information, and the one change he made was the expiration date, shortening it to 2 digits, and the order processed successfully.

    Edit: I would add that this customer was using AMEX, if that might be an issue.

    • This reply was modified 2 years, 4 months ago by obrienjc2020.

    I’ve tested again using both amex and visa cards and both worked with both formats. Can you still reproduce that problem?

    Thread Starter obrienjc2020

    (@obrienjc2020)

    I too tested this in sandbox mode, and the order processes with either 2 or 4 digits entered. Customer swears up and down it was that one change (4 to 2 digits on exp.). I do not see any other way they could have caused this ‘blank’ error to display.

    I’ve enabled the debug logging so if it happens again, I might be able to provide more information. Thank you,

    Plugin Support Leonardo Albuquerque a11n

    (@leonardolopesalbuquerque)

    No problem.

    I’ll mark this as resolved for now. If the problem happens again you can reopen it and we’ll be glad to help you.

    Bear in mind that this type of bug could happen only in production mode. So please also test in a production environment just to make sure.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Expiration date – maxlength issue’ is closed to new replies.