Hi,
We are about to convert to 12.5 and are very excited about the possibility of using tokenization for auto renewals. Is anyone out there using this functionality who would be willing to share their stories on how the process of tokenization is or is not helping their business model?
Thank you,
Sadie
(Cross posted to Membership)
Hi Nich,
I am surprised to hear that. Tessitura’s tokenization FAQ seems to contradict the “by design” response you received. Here is the statement I’m referring to:
How will tokenization affect my website? Tokenization should have no effect on your website. Any credit cards that are saved through your website (because you are saving credit cards for payment plans or are a user of Payment Express with automatic credit card storage turned on) are automatically tokenized.
That statement comes from this document: http://www.tessituranetwork.com/~/media/Documentation/System%20Administration/Tokenization%20FAQ.ashx. I interpreted “automatically tokenized” as meaning that T_ACCOUNT_DATA would be written to, as a token that isn’t retained is not useful. Based on what you experienced, it sounds like that statement in the FAQ is inaccurate?
Thanks,
David
For clarification, what we are addressing with Nich in his TASK ticket is related to passively saving authorized cards as tokens when the authorization comes thorough on the web when using Payment Express. This issue is resolved in v14 and we are reviewing it for v12.5.1 .The functionality related to explicitly saving tokens as part of a payment plan using either Payment Express or Vantiv is working as outlined in the quoted FAQ in v12.5.1.
Best,
Anna
Happily Tessitura has back ported the fix for the issue we had so we now have Tokenisation live at STC with Payment Express in production.
If anyone has any particular questions about it let me know?