11-14-2017 12:57 AM - edited 01-05-2022 03:35 AM
the credit i want to use expires after 2024, which is the longest year on the payment list.
How does it work out?
Probably have a mod to take payment manually?
Anyone tried it before?
11-14-2017 12:39 PM
@srlawren, okay you got me on this, and I'm not a delveloper, but in my past when a value (which could be valid) was not listed, 99% of the time, adding the value (in this case the year of expiry) was the list. This is why I say it's a 2 minute fix.
At least it's not something complicated like 1 year past February 29th. In one system I still use, it doesn't know to go to March 1st in a non-leapyear.
11-14-2017 12:27 PM
@srlawren, I agree, if the validation is on the client only this will work, but if there is server-side validation it will fail. In any case, I don't see harm in trying, at worst @MoreYummy will be where he is now (if it fails) and at best the system will accept his CC (if this is sucessful).
Anyway, it is up to @MoreYummy to decide if he wants to try this or not.
11-14-2017 12:12 PM
@Dan interesting approach... I'm a developer and I never thought of trying that! If the available dropdown values are the only validation (and/or it's only validated client-side against that list of valid values) then this might just work! If there's server-side validation applied as well then it will almost certainly fail. The other point of failure is the processing service that PM uses might not accept a card that expires that far into the future (thus being the reason the list is restricted so in the self-serve system).
@stonechucker LOL are you new here? There's no such thing as a 2 min fix at Public Mobile. Based on the past year or so, a 2 min fix is a minimum 2 month fix. However, as I alluded to above there may be other complexities and reasons that the list doesn't include later years--I'd bet the processing service won't accept greater than x days and that's what's used to generate the dropdown. But @Dan's approach is definitely worth a try!
@MoreYummy out of curiosity, what kind of card is this? Visa or MC? And what is the issuing instutition? It is unusual to get an expiry date that far out I believe.
11-14-2017 10:24 AM
lol, this is interesting!
would like to see how it panned out.
11-14-2017 09:55 AM
Hi @MoreYummy,
It sucks that you are having this problem. My expectation is that the system isn't really preventing a date beyond 2024, it just doesn't list an option to allow you to do it, and you cannot enter it manually.
If you are willing to play around with how the page itself works, you can try to use the F12 key (to open the Web Developer Tools), go to the Console tab in Web Developer tools, and manually add the year to that field (this would add year 2026, paste this line in the console command line and hit enter):
$('#ExpiryYearDropDownList').append($('<option>', {value:2026, text:'2026'}));
Then, enter your CC data and see if it will accept the year you manually added. It will either work or not, you have nothing to loose really.
11-14-2017 09:07 AM
@stonechucker wrote:It wouldn't be a software improvemnet, it's an addition of a value (or values) to a list. 2 minute job at most.
It could be a 2 second software change. How many updates to correct deficiencies have you seen in recent times?
11-14-2017 07:55 AM
It wouldn't be a software improvemnet, it's an addition of a value (or values) to a list. 2 minute job at most.
11-14-2017 06:07 AM
@MoreYummy, you need to try a different credit card or use vouchers. The moderators can't manually apply payment for you due to security reasons. This was previously discussed. BTW, I won't suggest putting in a labs suggestion again given the track record with making software improvements in the self serve portal.
11-14-2017 02:39 AM
Another item for the to do list. You could always buy vouchers, if only the web search worked properly...
But in all seriousness I can't recall seeing any of my credit cards lasting so long 6 years seems not normal I thought average was 3-4 years.