07-27-2023 09:36 PM
For context this post is not regarding my own Public Account but a friend Referral who I'll call Steve for this post. He is an older gentleman who just wants to pay his phone bill and use his phone. He's never signed in nor done anything himself online since he doesn't want to bother with it, I've always signed in and done everything on his behalf since Activation.
Today Steve called me and said his phone was not working for texts or calls, whenever someone tried calling him it told them that they needed a USA Add-on to call him. (Kinda weird that Public tells customers calling a disconnected Line that they need an add-on, it should just say the customer your calling is unavailable or something along those lines.)
Steve's account hasn't been signed into since the switch to EverSafe ID, so I signed in from my end and got the 2FA Code from him and complete his EverSafe ID Account Setup.
The issue was failed payment which is quite common since the new update and I've had a few Friend Referrals call to have it fixed and I've been able to fix it everytime. Usually it's an address issue, however in this case Steve's credit card Expiry was wrong.. it expires in 2026, and for some reason it wasn't taking payment as Public Mobile had his in the system with the Expiry being 2023.. I updated his payment method to the same card, with the correct Expiry and payment went through..
Now when i set up his account with him, we would have put in his Credit Card number for number... so I am wondering, how did this happen? Usually Public Mobile won't accept payment if there is even the smallest error, would it really have accepted the wrong Expiry if we actually put it in wrong during activation?
Solved! Go to Solution.
07-27-2023 09:41 PM
Yes, I'm guessing it would.
However once the incorrect date is reached it's likely the system wouldn't even try to withdraw from the registered card as it would have passed the date indicated on file.