By Josh on Friday, 22 March 2019
Posted in General Issues
Replies 3
Likes 0
Views 813
Votes 0
Hi,

We have noticed a problem with a payment plugin Stripe.

When using the form not the pop up box.

The form asks for the expiry date in this format MM / YYYY and all our sales have been done over the phone and every singly person paying enters the expiry date in this format MM / YY Evan tho the example says YYYY I personally watch over 23 people do it with my own eyes. Which causes an error of invalid card expiry and they dont know what to do.

Is it possible to change the card expiry date format to MM / YY to stop people getting the error msg saying invalid expiry date

As its a really annoying issue, to avoid the problem at the moment we are using the pop up box as it asks the date format in MM / YY but the problem is, the CSS don't match out website. And also they say in there notes to not use the pop if possible.

Please help
Thanks for your input on this Josh. I am not entirely sure if this is only particularly happening with your users but we have customers who are using Stripe that does not encounter such issue. Not that I know of at least.

Perhaps it would be ideal for us to add this as a settings in the upcoming release of PayPlans. I have added a ticket for this internally and we'll see if we can add this on the next release.
·
Friday, 22 March 2019 18:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Is it possible for you guys to change ours so that it only asked in this date format

I think you don’t hear about it from other costumer because they have no idea it’s happening

I have watched every single transaction happen on ours over the past week and not a single person got it correct they all entered the date in as MM / YY

Because this is a generic way every merchant ask for this information so it is comon practice for peoppe to enter in this way.

Would it be possible for you guys to put a patch on ours or an override some how as for us it’s a issue as we are very picky in making our sales flow as simple as possible.
·
Friday, 22 March 2019 18:22
·
0 Likes
·
0 Votes
·
0 Comments
·
I am really sorry but this is beyond the scope of our support. We have already logged this into our internal issue tracker and we will see try to update this in the next release when possible.
·
Friday, 22 March 2019 23:04
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post