Hello All,
This may need to be a support ticket, but just curious if anyone else has seen this. The Box Office initially told me it was happening on one device, but it now seems to be happening on all of them. What happens is that, during a normal in person window order, everything will go according to plan and work correctly, except that during the transaction process the patron will get an error that says something like "Card Expired", even though the transaction completes successfully (just checked with Finance to be sure). I am still working on getting the exact text in case it gives me a different error message, but the fact that the payments are still processing correctly has me confused.
Anyone seen this before?
John
Okay, so FYI, I tried upgrading to 5.15.0, but I am still getting that same error message. In doing some searching on the web, it looks like this might have to do with Visa extending their public key through 2022 and it is somehow about getting a new file onto the machines.
I suppose the next step is for me to reach out to Worldpay.
I believe our IT was redirected to Tessitura from World Pay-- we are also still experiencing the issue If they have any updates I'll make sure to share them here.
-ultima
I talked to someone at Worldpay on Friday because apparently I wanted to frustrate myself with 45 minutes of hold time and the new identification procedure they apparently have in place now.
But when I finally got the right person on the phone, the answer I got was that the issue apparently affects a lot of people; not just Tessitura peoples. Their current solution is either to a) buy brand new EMV readers (this person really liked telling me that one), or else to b) just wait it out as apparently someone, somewhere IS working on a solution to the issue. But it might come tomorrow or six months from now from the impression I got.
Given everything... I might wait and see, at least for a little bit, on this one. Thanks anyway for your input on this. It at least sped up the process to get to where we are now.
Sorry for the delayed reply-- thanks for the additional info! We also encountered the same issue you did, so still no fix for us.