The Process Credit Cards task is used to batch commit multiple shipments and at the same time process the credit card transactions. If the Sage Exchange desktop (SED) is not installed prior to running this task; credit card processing will not be performed. Depending on the options in the
Setup Processor Accounts, the shipment commit process will also be halted. The options are "Stop shipment if Payment Fails" - Before
or During shipment commit.

For Microsoft, terminal server environments; the first time the user attempts a credit card transaction, there will be an attempt to automatically install the SED. This writes required entries to the users profile.  Because entries to each user's profile is required; it is recommended to login with each users T.S. credential and manuall install Sage Exchange rather than waiting for them to enter a transaction for the first time. This would avoid the result described in the first paragraph.

This is the same behavior which exhibits when internet connectivityor communications to the Sage Exchange Portal is lost.

If the option to stop shipments is not set and they are committed but the credit card processing fails; the workaround is to enter cash receipt transactions in order to process the sale transactions. In a high transaction volume business; this can mean several hours of additional work in researching the credit card information and manual entries. 

If you are a customer using Sage Exchange in v2013 or above and have a high credit card volume, using the Process Credit Cards task; please reply to this blog and let us know if you have encountered a loss of connectivity which required you to pursue the workaround described. What was your experience? How long ago was this and what general steps were taken to correct or mitigate the connectivity issue?