Sage 100

I received an email from a consultant who said their customer's import of credit cards broke on Friday. Maybe related to either the SED 1.x retirement or the outage Brett posted or both. Just as an FYI in case anyone else takes a report the message was: Could not set SO_SalesOrderPayment_bus column CreditCardGUID$:*******guid/token****** is not on file

Any follow up on this? We had a client have the same thing. It stopped when Paya turned off TLS1.0 on 6/1, but just started working again on 6/7 after Paya turned it back on 6/6. So, we went through the process of updating their server & workstations to use TLS 1.2 & SED 2.0 on 6/20, but then the imports stopped working again. Any idea if this is TLS or SED related? I am wondering if its their website TLS or if an import setting changed for the CreditCardGUID from SED 1.x to 2.0? They are on Sage v2016. I would think TLS, but I don't think Paya turned the 1.0 back off yet, I thought it was going to be again on 6/30. They are also able to process credit cards from Sage fine.

I haven't heard anything further from my customer on this. Is it possible that this fix is required? https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=91715&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_DOWNLOAD_1&stateId=35711&cmd=displayKC&dialogID=1329029&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true

I can give it a shot