mkern

Hi Dave, For me, I ran the following in MySQL CLI, this would be the equivalent to running a SQL statement in PHPMyAdmin. select * from tblclients where id=47 \G; In this example, id=47 was one of the clients profiles that had the problem. For the 3 tables below, there was erroneous data, possible encrypted, I am not sure, but it was special characters. cardnum: startdate: expdate: I backed up the database and then ran an update statement for each of the tables: update tblclients set cardnum="" where id=47; update tblclients set startdate="" where id=47; update tblclients set expdate="" where id=47; This cleared out the fields and then I was able to properly charge the card without the previous error. This data was apparently breaking the migration process WHMCS is trying to perform on the backend. As I had multiple clients with this problem and none of this field data was needed for me I executed the following to fix all of the clients. update tblclients set cardnum=""; update tblclients set startdate=""; update tblclients set expdate=""; This solved the problem for me for all clients, now there is a secondary issue where WHMCS thinks there is a "default" card ahead of the real one, but I was instructed that deleting that when the problem occurs will solve the problem. I haven't bothered with that yet, as I have just manually selected the correct card. If recurring billing breaks due to the secondary issue this is what they said I needed to do:

Hi All, I just ran into this issue yesterday and wanted to share what I did to resolve it. I was running a little behind on WHMCS versions because I had some integration I needed to split up and once I completed that I updated to 7.9.2 on 4/2. I was super worried that this was going to completely break Quantum Vault because in previous attempts to upgrade I had serious conflicts with SiteOx's Quantum Vault plugin. I removed that plugin prior to upgrade and everything seemed to work perfectly. All credit cards were automatically charging and life seemed good. However, apparently certain users had problems that I did not notice until yesterday. I escalated to WHMCS and paid for the FastTrack support. They investigated and they told me how the new system works and that there was an error in the migration process of moving the data from the tblclients table to the new location. They requested a review of a previous backup prior to 4/2 which was presumable when the issue occurred because the new method was introduced in 7.8+ I believe. In any case, between this post and their feedback on the new mechanism, I was able to review the tblclients table for the customer I was having problems with and I noticed erroneous data in the cardnum/startdate/expdate fields. I also noticed in the Activity Logs that WHMCS Support tried to clear the encrypted data from these fields. I manually cleared the cardnum/startdate/expdate fields for the problem customer (we don't store the cards anyway) and the problem was resolved. Also worth noting, I had no errors in the Gatewaylog, the errors were only showing up in the Activity log. Pay Method migration failed. Card number must be at least 13 chars - User ID: XX I had upgraded to 7.10.x prior to escalating to support, so it works on that version as welll. Thanks, Michael Kern Admin on Demand, LLC