Sage 100

_**Alert! Sage Mobile Payments Service Interruption**_ From: do.not.reply@sagepayments.com <do.not.reply@sagepayments.com> Sent: Monday, June 4, 2018 7:39 AM Subject: Sage Mobile Payments Service Interruption ALERT! Sage Mobile Payments Service Interruption We are working closely with our vendor to resolve a connectivity issue that is causing all transactions attempted using Sage Mobile Payments to return ""Transaction Declined by Processor."" The issue began at approximately 3:00 pm EDT on Friday, June 1, 2018. We will post additional updates on our Knowledgebase at https://support.paya.com/44510-knowledgebase/308786 as they become available. For now, please access our Virtual Terminal to submit any credit card payments by visiting https://www.sagepayments.net/virtualterminal. To retrieve your login credentials, click Forgot Password, then click Chat with Boomtown. To reset your password, you will need your 12-digit Virtual Terminal ID, which will also be your Username for this site, and your email address. Follow these steps: https://support.paya.com/44648-login-help/310260 To process a payment; follow these steps: https://support.paya.com/44616-paya-virtual-terminal-all-articles/315936 We apologize for this inconvenience and we are actively working to restore service as quickly as possible. Best Regards, Paya

There are a few more issues that have been added since Brett posted this.

Like what, @WayneSchulz? My v2013 client (SED 1.x) can't process credit cards. They get the message, ""You must wait while Sage Exchange..."" even though it was already installed. Previously when we got this message we would shut the workstation down, re-start, and try again - and that usually worked, but not now.

found it: ALERT: ExpressPay checkout page returning a Processing Error Our IT teams are investigating the cause of an error in our ExpressPay checkout page. Users attempting to submit a payment using this page are receiving this error message: An error occurred on the server when processing the URL. Please contact the system administrator. If you are the system administrator please click here to find out more about this error. We apologize for this inconvenience and we are actively working to restore service as quickly as possible. ALERT: Virtual Check Automatic Settlement did not process between June 1 and June 3, 2018 Our IT teams are resolving an issue that resulted in automatic settlement for Virtual Check (ACH) transactions to not process over the last few days. We expect to have a fix in place today and all transactions will settle in tonight's automatic settlement. We apologize for this inconvenience.

x-reference - https://90minds-com.socialcast.com/messages/38864651?ref=stream

Also just noticed this in that Paya notification: ALERT: Sage Exchange Desktop 1.0 returning ""Unable to complete registration"" on launch Beginning at approximately 5 pm EDT on Friday, June 1, 2018, users attempting to launch Sage Exchange Desktop 1.0 began receiving an error message, ""Unable to complete registration."" We recommend installing Sage Exchange Desktop 2.0 to address this issue and continue processing payments. **This installation requires full admin rights to your PC!** Download the latest version of the Sage Exchange Desktop Bootstrapper from https://www.sageexchange.com/install/#/sedv2x/en Extract and run SageExchangeDesktopBootstrapper.exe Navigate to the SageExchangeDesktopBootstrapper.exe file Right click and Run as Administrator Follow installation prompts

I just spoke with Sage (Vickie) who found out from Ronnie Aspe that SED 2.x should be fine with v2013+, i.e. apparently 2.x _**is**_ now compatible with versions it previously wasn't. I'm going to try it on my client's system and will let you know how I make out.

Hmmmm, I wonder if it will work with v4.4???

Oh, I didn't think Sage Exchange applied to 4.4, @JeffSchwenk.

I don't either but you never know......

2013 customer who declined last two upgrades just emailed with

@WayneSchulz - I would wager they don't have the 2.x SED installed. My user is on v2016 and they are getting this note as well.

I think the pain point is that all the local workstations have to individually install SED 2.0 and this requires local admin.

Correct, I'm in the process of installing 2.x on a v2013 workstation. However, the cc swipe setting didn't come over. They have ""Magensa card swipe"" selected in 1.x but that's not an option in 2.x; on hold with Paya.

FYI I am having to log on as each user on the terminal server and ""run as admin"" to get it to work. Installing logged on as administrator didn't work.

I successfully installed and tested 2.x on a v2013 workstation. And for the 1.x ""Magensa card swipe"" setting that was being used in 1.x, I had to select the ""Magtek DynaMag/DynaPad"" option under Non-EMV Devices.

From: do.not.reply@sagepayments.com <do.not.reply@sagepayments.com> Sent: Tuesday, June 5, 2018 4:36 PM Subject: **Please Note: Paya has updated our TLS security protocols** The PCI DSS council mandated the transition from Secure Sockets Layer (SSL) and Transport Layer Security (TLS) v1.0, to TLS v1.2 or higher, which offers an overall increased level of security. This transition occurred on June 1, 2018. During this transition some customers using electronic solutions to process transactions experienced an issue processing payments. If you are experiencing any issues processing payments, please visit our support.paya.com webpage and click on the maintenance and alerts section to get the latest information about this transition, including FAQs. We apologize for any inconvenience this may have caused. Thank you for being a valued Paya customer. Maintenance ad Alerts: https://support.paya.com/44510-knowledgebase/308786-maintenance-and-service-interruption-alerts?from_search=24353507 Best Regards, Paya Inc

From: do.not.reply@sagepayments.com <do.not.reply@sagepayments.com> Sent: Wednesday, June 6, 2018 2:27 PM Subject: **RESOLVED -_Shopping Cart, Donate Now and ExpressPay Checkout Page Error_** ALERT! RESOLVED -Shopping Cart, Donate Now and ExpressPay Checkout Page Error We have resolved the issue that was causing transactions attempted through our Shopping Cart, Donate Now and ExpressPay checkout pages. We apologize for the inconvenience caused by this issue. Best Regards, Paya