Hello all,
We've noticed there are times when a charge will have processed through Payment Express but has no corresponding charge in Tessitura. It is appearing as a duplicate charge quite often. We show the original charge in Tessitura and then it appears that another charge processes through Payment Express. We've also had an instance or two where there is a charge that is in Payment Express but nothing correlating in Tessitura.
Has anyone else noticed this or experienced this? Could this be auto-reversals not going through?
Chris Cuhel
We're on Vantiv, but have experienced issues similar to those you described after upgrading to Tessitura v14 -- a significant increase in the number of discrepancies where transactions would be processed through Vantiv, but have no corresponding Tessitura record and vice-versa (along with some duplicate refunds and charges). What version of Tessitura are you on, Chris? The latest Service Pack (14.0.8) appears to have resolved many of these issues for us, though we're still monitoring.
DGomez
Unknown said:We're on Vantiv, but have experienced issues similar to those you described
We are also on Vantiv and can also confirm that this issue occurs from time to time, before and after the v14 upgrade. Once the auth has been requested on the Tess side, cancelling or otherwise interrupting the charge process (sometimes? always?) removes all visible trace of the payment in the client, but the (possibly duplicate) charge remains at Vantiv.
I can usually see traces of these incidents in the T_PAYMENT_GATEWAY_ACTIVITY table, and it would be helpful if more of that data was somehow visible in the client so that operators are at least more aware of the lingering auth(s) before they re-try that charge.