Failed Payments with CC are not logged anymore

[yggdrasil]

In the past, when someone tried to pay with their CC and it failed, the user would receive an email and as an admin you could see a payment failed from the user account based on that email and it was also logged in the user account as a failed payment.

But when WHMCS updated the CC module, not it seems to make the remote calls with JavaScript on the user side (stripe) and failures are not logged anymore, no wonder because in the past it used CURL or PHP and as such as properly logged and passed to WHMCS, not it does not, its on the user side only. I see constantly failed payments on my stripe console, but on the WHMCS user account, no email is sent that any payment failed. It seems this only works now for automated payments executed with the cron but not when the user tries to pay manually or just added a new card. This is also bad for fraud, someone registers and tries multiple different cards, you can see that on the stripe console but on WHMCS no activity of payments appears which is bad.

Personally, while its nice the user gets an error immediately on the screen without reloading the page this is a drawback for me as admin. Failed payments should be logged for security, debugging and support reasons.

I also noticed that people get blocked more easily for several attempts as most people click the button several times and it sends multiple attempts to stripe, eventually that users is blocked from any further attempts for a few days. In the past, they didn't do this because each attempt loaded a new page and displayed an error afterwards. Sometimes the new JS ajax method does not return a proper error from stripe, so the people keep hitting this without understanding why the payment is not being applied. Its just horrible how this works now and its causing me tons of problems with payments.

While its nice that customers can now have more than one CC on their accounts with different billing details, the way CC charges are executed on WHMCS are much worse over the old approach. I would rather prefer the old way, on which there is a clear page load on each attempt instead of the new ajax JS call that most people, in particular in mobile phones seem to trigger multiple times or get different errors thinking it's not working.

The problems started when WHMCS introduced the option to have multiple CC on the account. The whole CC payment page was redone, but it seems for the worse. Visually and in features, its much better, but its buggy and the way it works is not robust. I never had problems with CC on WHMCS for years, this was one of the reason I always trusted WHMCS, it had bugs on other things but never on payments or missed invoices. Now, sadly this changed. I'm seriously not considering upgrading WHMCS anymore ever, because every time they change something that worked fine in the past, it's for the worse. Adding new features is nice, but they should be added on top of things that already exists, instead of trying to make them from scratch.