Sage 100

Existing customer on 4.3.0.19 switched last night from PC Charge to Sage Payments. Back end processor DID NOT CHANGE. Still is Sage Payments -- the only thing that changed is the integration. This morning they are receiving ""Authorization Expired"" even on new Sales Orders. I log in remotely and review the Payment Type Maintenance - Pree-Authorization Term. It is set to 30 on each payment type. They indicate this is happening for FRESH NEW ORDERS (aka I'm not dealing with ones which may be sitting in an already authorized state). Am I missing something?

Have you looked at the pre-authorizations in Virtual Terminal?

Found this: MAS has a setting called the ""pre-auth term limit"" that tells it how long to leave a pre-auth open before marking it as expired. This needs to be set to ""7"" to match our gateway. If it is less than seven, then even if the authorization is open in the gateway, MAS will assume it has expired and run a new Sale transaction. Here: https://support.sagepayments.com/ics/support/KBAnswer.asp?questionID=1794&hitOffset=301+285+252+153+140&docID=3576 No idea what happens if your limit is over 7 - there's very little KB info about setup of Sage Payments

Customer is using payment types setup as ""deposit"" which I believe immediately charges the card though if that were the case I'm unsure why they'd be getting an expired authorization warning.

And I suggested that they log into their VT and look at the term setup there - since they're just starting to use SPS for the back end integration it's possible something needs to be changed. Really not much I've found in the Sage KB so this is apparently not a widespread issue.

Update: Customer had the pre-authorization term set to 30 days (from when they used PC Charge). Changing this to 7 days appears to have fixed the issue. Note that in this case all CC transactions types were setup as ""Deposit"" (both before and after I migrated them to the SPS back end).

We had this issue in the past as well. Not sure what version as it was awhile back. It was also a mismatch in the expired authorization as well. I think 30 days is a magic number. We also had an issue where Sage was slightly longer than MAS. This was causing a problem where as it would clear ship data entry, but fail during the daily sales order updates since the authorization was expire but MAS thought it was valid. We would have to force the authorization which increased the client's exposure with charge backs.

The SPS is defaulted to 7 days and cannot be changed - least haven't found a way yet.