Domain Order Renewal Auto-Payment Error

[autolux]

Hi,

 

i've recently had a customer accidentally processed renewal for multiple years on a handful of .com & .net domains, whos understandably a bit confused and annoyed.

 

for my WHMCS clients with credit cards i have automatic payments enabled.

 

as this customer had a credit card on file, when he selected MyDomains->Details-> Renew Domain, to be taken to the 'Order Renewal' options for his domain name, he was unsure of the durations he wished to renew.

 

he has first selected 1 year, clicked "Order Renewal" and the invoice has been generated and it has displayed the invoice listed a "UNPAID" with paypal/credit card options and pay now link.

 

However, in the background WHMCS has actually automatically processed his payment.

 

The client not knowing this thinking it is unpaid, has closed this invoice window, gone back to "Order Renewal" and chosen a different period, clicked again, been taken to an UNPAID invoice, when infact WHMCS has processed the payment.. resulting in some unwanted payments and renewals.

 

The client has around 40 domains. For two others he wished to renew, I offered to test with him. For myself in my browser (FireFox), when i clicked "Order Renewal" specifying 1 year, it went through and displayed the invoice listed as "PAID".

 

For the customer in his browser (IE8, with Norton Net Security are the only details I can see on his browser) he clicked "Order Renewal" and was taken to an invoice marked as "UNPAID" presenting payment options, when i could clearly see in WHMCS payment was automatically processed with his credit card on file.

 

Obviously this is two different behaviours in two browsers which has cost this customer a lot of money and confusion.

 

I have tested for another customer, also with credit card on file for auto billing however, and WHMCS does not automatically take money out of his account. It displays the "UNPAID" invoice, with payment options and does not process anything automatically.

 

Just wondering on why there is different behaviour going on here, the accounts should be subject to the same billing settings. Along with the differences in behaviours between what was displayed for me, and what was displayed for this client.