Sage 100

Have a client on 4.5 PU3 that is getting corrupted credit card numbers in the AR_CustomerCreditCard file. When the corrupted card is charged in SO, if its the first one in the batch, it will error out so they can see its an issue, but if its not the first one, it just replaces the corrupted card number with the last card number approved & charges that one. Sage has reviewed the data & says the table just needs to be wiped clean & manually re-entered. Has anyone else had this happen? I think upgrading them to 2013 will prevent it from continuing, but until then I know I am going to get asked why this is going on.

I had something similar happen with a client, but it happened when they created an invoice in SO without first having a sales order and it only happened on one workstation. We had to workaround by having all SO invoices start with a Sales Order. Could never figure out why it was a problem only on one PC.

Dana sorry to answer with more questions. Related to what @JaneCavanaugh said. 1. Can you screenshot the error msg and post it here? 2. Is the msg appearing in S/O Entry when order is being pre-auth'd or when printing the Sales Journal and it's authorizing? 3. Did Sage say the card no is not being stored (encrypted) properly?

Here's an example. Back in 4.30 and before, the EncryptedCreditCardNo was a 24-digit field. Since 4.40 it's 64 digits because the encryption scheme is tighter. If you're coming from 4.30 or less it's the job of the Level Conversion program to expand the field, decrypt the 24-digit no, then re-encrypt it as a 64-digit no. But if there was data corruption in the old version OR you had conversion issues then you could have all these card numbers sitting in today's AR_CustomerCreditCard encrypted using the old scheme. Do you know if these bad card numbers were entered prior to 4.40?

If that card is placed on a SO & no other card has been ran yet, it comes up as ""Invalid card number"", but if a card was already ran that day, it just grabs the last card so the user doesn't notice it. We only see the corruption in Customer Maintenance, see screen shot attached.