Hi there--
Strathmore is currently undergoing a migration to Tessitura Merchant Services, but we have some concerns about the inability to save credit cards that are input through Secure Deviceless Entry (SDE). Outside of web sales, the majority of patron transactions in the ticket office are done over the phone, where the credit card would not be present.
I understand that after moving to TMS we will ONLY be able to save tokenized card information that has been input through an EMV reader or through a TNEW transaction. And, furthermore, that when we migrate from our current merchant processor we will need to re-tokenize every existing card in our database all over again, essentially "starting from scratch."
I'm wondering how other organizations have navigated the reality of this? Particularly for those high value patrons who might request tickets through a Development team member as opposed to the ticket office and where it might be inappropriate/awkward to have to repeatedly ask them for their credit card information until we can get ahold of their physical card.
Some ideas that have been floated are doing a $1 dummy transaction in those instances where we would like to tokenize the card for future use, perhaps through a link on TNEW?
Any advice you can give about processes you adopted, or things that just didn't work, would be much appreciated.
Even if you have the card saved to their account, you will have to enter the CVV every time you charge it and you aren't supposed to save the CVV anywhere. It's definitely not ideal in your situation.
Yikes, thank you for saying something, somehow I missed this piece of information. So, essentially it doesn't really matter whether or not we're able to store the tokenized card on their account at the time of the transaction/conversation. We're going to need either their full card number + CVV or their CVV code every time we talk to them?
Yes, that is correct. We are in the middle of implementation and I had a call with Tessitura yesterday and started testing today. It will save the credit card number and the expiration date, but you will have to manually enter the CVV every time.
Just to be clear, this happens to cards taken through SDE? It can't be universal, otherwise the billing utility wouldn't work.
I could be incorrect, but my understanding is that this all went back to PCI rules, and PCI rules are different for billing than they are for regular, single event card not present transactions. Been a while since I looked at the details on this, though.
This is not correct. CVV is required when entering cards to save them through Keyed Entry, but it is not required when using a saved card. Once the card is saved you just select it and don't need to enter anything extra. See the Using and Adding On-File Credit Cards section of the Payments Window topic for details on how you use an on-file card.
CVV is also required to process a payment in Secure Deviceless Entry, and we are making a point of clarifying that you no longer have the option to skip CVV when processing a transaction (like when someone orders on the phone) so I'm guessing that was the mixup.
To reiterate, once a card is saved, you don't need the CVV to use that saved card in the Payments window or when running a billing utility.
I am testing today and when I pulled in a card saved via TNEW, the application made me enter the CVV to process a ticket order. Is that now how it is supposed to work?
I did a bit more digging, and the Secure Deviceless Entry window will present saved cards, and if you choose a saved card in that window you will have to enter a CVV. However, if you access saved cards through the Accounts button on the Payments window then you do not have to enter a CVV. A saved card that's listed in the SDE window should also be accessible through the Accounts button.
Anne, I also reached out to your Tessitura Merchant Services cutover project manager, and she's updated your project ticket too regarding all of this.