We cutover to TMS last month and we are seeing an increase in rejected transactions. The reject messages are more varied than WolrdPay which were mostly of the rejections were "declined" or "stolen card" .We did transfer tokens from WorldPay.
Here is a list of the sample rejections
I am looking to see how other organizations are dealing with the less obvious rejections. I get Expired and Invalid CC#, but I am looking for methods for dealing with the other messages.
Have other people seen this issue with transferred tokens?
Hi Seth,
Although we are still on v15.1.21, we do experience an issue with expired cc, however; as we identified, there is a bug present in v15.1 all the way through some versions of v16 where the cc expiration number is not accurrately captured unless if manually entered each time a cc is processed.
See: release id "DEV-3918"
"expiration date" being stored in Tessitura, release id: "DEV-3918" appears to refer to the transmission of the expiration date to the service provider in this case WindCave.
Just maybe this has some correlation to some of the issues you are seeing in TMS.