I've seen this message a few times. The card gets pre-authorized on the sales order just fine, then there is a problem at invoicing. I set the payment type to "None" instead of credit card and post the invoice. Then go into Customer Maintenance, and into the credit cards and click Edit on the card and that message comes up.

So I delete the card and re-enter it. Then process the card and it's fine.

I'm using Sage 100 2017 (soon to be upgrading to 2019 before 9/30).

If you're on 2013, I would highly suggest getting onto at least 2019 if not 2020 -- you're missing out on a lot of upgraded features.

Thanks - I've been deleting/re-entering the cards to get through this when we've hit this error, but the issue is that we put credit cards directly into Sage, so we'd have to contact the customer again, which isn't always easy and it creates a hold-up. 

Do you have another secure way you store credit card information, so it can be retrieved if something went wrong in Sage? 

I'm also interested in the types of features you're referring to in 2019 or 2020. We're definitely getting behind, but we have about 20 users and the upgrade can be costly...

It's probably best to call Paya support for this kind of error.  They run the vault.

All the cards are kept encrypted long enough to get them charged. This only happens every so often on cards imported into orders from our website.

Regarding the new features, you'd need to look at the "What's New" guides for all the versions since 2013 to see what applies to your company. Just google "Sage 100 What's new" and the version number.

I took a quick look back at the "what's new" lists and here are some examples:

• The auto-complete feature for customer and vendor names -- we use this every single day. It's great.
• Print "stay open" setting so you can print/preview something then stay on the print screen.
• One-click general ledger reversal entries.
• Vendor name 50 characters.
• Cash receipts list button.
• Purchase order "copy from" -- we use this all the time.
• They put in a new version of the desktop launcher that makes it easier to create a favorites list and has a "large font" version for our older workers.
• Spell checking
• Ability to make a warehouse code inactive.
• We don't use Job Cost or the Manufacturing modules but I believe those got completely re-done.

Hi Kevin,

I called Sage Exchange (Paya), but this is an issue with Sage 100.

Other cards are being charged correctly for the most part, but if they're not, we'll see an error message from Sage Exchange Paya popup from the Windows Notification Area (System Tray) next to the clock that says the card was declined.

In this case, the error is coming from Sage 100, not Sage Exchange. We're not using Sage Exchange to enter cards manually - we're using Sage 100 to run cards that are stored.

Any ideas about what this could be in Sage 100?

Thanks

If you were to call Sage, they would tell you that your version isn't supported anymore.

Like I said, I'm on 2017, and I see the error every once in a while, but we import credit cards. Some way or another, the Vault is "losing" these cards. Not sure why.

Starting with v2013 Sage 100 does not "store" any CC data, just a link to the Paya vault.  If the GUID (stored in AR_CustomerCreditCard) is gone from the vault, that would be something for Paya to answer.