Another Expiry Date Issue

  • Resolved tthompson82

    (@tnolan82)


    5 years, 4 months ago

    Hi.

    I can see there is already a Topic on this board with regards to Expiry Date issues and looking at the update file, I can see that the format was changed from MM/YYYY in previous plugin versions to MM/YY

    However the new format is also giving serious problems.

    It’s still very common for customers to mistakenly type the full expiry year (YYYY) and when doing so, only the first two digits are entered with the cursor on the text block still blinking as if typing is taking place.

    For example if someone were to type in 08/2023, it would be only be entered as 08/20

    The customer is then able to proceed with placing the order and then get returned back to the shopping cart page with a generic “declined transaction” message. They are not made aware then and there that the expiry date has been entered incorrectly. Thus they try again and experience exactly the same scenario.

    We then have to log into the Secure Trading tportal to check the payment and find that the expiry date year ends in “20”

    This plugin has been live since this past weekend and this has occurred more than 30 times in the past few days so it’s obviously a serious UI/UX issue that needs to be resolved ASAP

    If you could please advise.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Josh Bedford

    (@joshbedford)

    Hi,

    I’m sorry to hear about the problem you’re having with the plugin. I’ve spoken to Secure Trading and they have given the go ahead to add YYYY as an option back into the plugin.

    This will be released in the next update which is coming very soon.

    Thanks,

    Thread Starter tthompson82

    (@tnolan82)

    Thanks, is there an estimate of when this new plugin update will be released?

    We are experiencing several customers encountering this issue on a daily basis…as a result many are leaving the checkout process in frustration which is causing losses in sales everyday.

    If the update is not due in the very imminent future if you could please advise how we can get in touch to manually change the source code in order to resolve this on the current plugin.

    Thanks

    Plugin Author Josh Bedford

    (@joshbedford)

    Hi,

    The updated version has been developed and is with the Secure Trading team for full UAT, so I’d imagine this will be released to the repo next week once the team there have confirmed.

    Thanks,

    Thread Starter tthompson82

    (@tnolan82)

    It seems that despite having sent the updated plugin to Secure Trading almost 2 months ago, they still have not released the updated version and claim it is still undergoing testing….Very disappointed in their level of service.

    At this stage is there a way to get in touch to manually change the source code in order to resolve this expiry date issue on the current plugin?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Another Expiry Date Issue’ is closed to new replies.