Sage 100

I'm a little confused. Just came back from performing a version 4.50 to v2014 PU3 upgrade. Client never used Credit Card Processing or has entered any credit card info into the 4.50 system. During the conversion of the main company code data, the system started a process called ""CI_SageExchange processing"" and went up to the internet and downloaded a 4MB file onto the server. Is this something to do with SData and on-line services or does the Credit Card Processing\Sage Exchange Vault get installed even though the customer does not use it?

yes. Sage Exchange is now needed, even if the Client does not do integrated credit card processing. And the customer can remove the install later if they like. However, when copying a company to a backup company, the CC Sage Exchange is required so it will be installed again, before the copy will complete.

@MadelineStefanou Thank you for your response. Yes I can see on the 3.Credit Card tab in Company Maintenance there is a Sage Exchange Vault-Only ID field and a Vault-Only Key field. My question still is why. Is it because SAGE wants EVERY company code (even though some are just backup or test companies) in ALL SAGE 100 ERP v2014 installations to have a Sage Exchange Vault connection just in case that someday the ""live"" company codes might use the Credit Card Processing module? Seems like a lot of overhead to set up for a ""just in case"" or is there something else that CI_SageExchange does now or will be doing in the future.

I am just guessing here but wouldn't it be because there's no provision for local storage of credit cards. Therefore Sage probably initializes this online for all companies.

Thanks @WayneSchulz - My concern here is --- Does SAGE Exchange Vault in the cloud work like the SAGE PEP program? Can we expect to receive calls someday from our clients when their SAGE 100 ERP system cannot talk with the SAGE Exchange Vault (mothership) and ERP stops working? Or am I just paranoid?

@MichaelMcDonald my guess is you're right on. I imagine it would be similar to a MAS 500 installation which periodically phones home to a Sage registration server to verify a valid license exists, and that server needs to always be up and running. Similarly the SPS vault server (whatever it's called) needs to always be up and running (and not be broken by installing Windows Security Updates) else CC txns in MAS 90/200 will fail.

Thanks @AlnoorCassim