Sage 100

I had a customer get this two days ago and a Nuvei/Paya desktop update fixed it.

And speaking of a Nuvei/paya desktop update, on three different workstations, I have tried to install the update after receiving a notification that one was waiting.  Not one of the installs completed.  Please contact Paya Support,.,,,,,

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!
------------------------------


Original Message:
Sent: 02-13-2026 12:55
From: Phil McIntosh
Subject: Any Nuvei/Paya Users Receiving: Error 200 AR_CreditCardCommon.PVC Line 1643?

I had a customer get this two days ago and a Nuvei/Paya desktop update fixed it.

------------------------------
Phil McIntosh
Friendly Systems

This started to pop up as an issue about a year ago. From memory I think the bulk of the "won't install" errors could be traced back to requiring ocal admin to install at least one of the paya desktop.

Here's one of the links from Paya - here

Here's another from the Sage Community

And speaking of a Nuvei/paya desktop update, on three different workstations, I have tried to install the update after receiving a notification that one was waiting.  Not one of the installs completed.  Please contact Paya Support,.,,,,,

I had a customer get this two days ago and a Nuvei/Paya desktop update fixed it.

Thanks @Wayne Schulz.

Another one today!

This started to pop up as an issue about a year ago. From memory I think the bulk of the "won't install" errors could be traced back to requiring ocal admin to install at least one of the paya desktop.

Here's one of the links from Paya - here

Here's another from the Sage Community

And speaking of a Nuvei/paya desktop update, on three different workstations, I have tried to install the update after receiving a notification that one was waiting.  Not one of the installs completed.  Please contact Paya Support,.,,,,,

I had a customer get this two days ago and a Nuvei/Paya desktop update fixed it.

Yep, admin mode.  You may have to uninstall existing software.  It finally installed as admin and by uninstalling for me

Thanks @Wayne Schulz.

Another one today!

This started to pop up as an issue about a year ago. From memory I think the bulk of the "won't install" errors could be traced back to requiring ocal admin to install at least one of the paya desktop.

Here's one of the links from Paya - here

Here's another from the Sage Community

And speaking of a Nuvei/paya desktop update, on three different workstations, I have tried to install the update after receiving a notification that one was waiting.  Not one of the installs completed.  Please contact Paya Support,.,,,,,

I had a customer get this two days ago and a Nuvei/Paya desktop update fixed it.

From what I recall - up until a certain version the Paya Connect Desktop did NOT require local admin. Then it changed at one point and that's when we started seeing a bunch of these messages which is a PITA because most IT departments do not grant local admin rights to users.

Yep, admin mode.  You may have to uninstall existing software.  It finally installed as admin and by uninstalling for me

Thanks @Wayne Schulz.

Another one today!

This started to pop up as an issue about a year ago. From memory I think the bulk of the "won't install" errors could be traced back to requiring ocal admin to install at least one of the paya desktop.

Here's one of the links from Paya - here

Here's another from the Sage Community

And speaking of a Nuvei/paya desktop update, on three different workstations, I have tried to install the update after receiving a notification that one was waiting.  Not one of the installs completed.  Please contact Paya Support,.,,,,,

I had a customer get this two days ago and a Nuvei/Paya desktop update fixed it.

I'm taking other support cases from different clients who are seeing the prompt to update their PCD ( Paya Connect Desktop ) and who cannot do so without having local administrative rights. Just be on the watch for this because if they try to accept the update it invariably fails (unless IT has given users local admin rights).