Hello,
We are building a new web that constituent can save their payment method into their account for later retrieve to pay for tickets, donations, contributions, membership .. is there any API methods to handle this kind of works? Thanks,
-Harry
Hi Harry,
Card tokenization is slated to be fully functional via the Tessitura APIs in version 14. Currently in version 12.5.1 of Tessitura's APIs (REST and SOAP) there isn't an effective way to use card tokenization during checkout because tokens are not consistently stored for transactions, even though they can be retrieved via the Accounts service in the Rest API.
Once this functionality is complete with v14 of Tessitura, we plan to incorporate it fairly quickly into TN Express Web and make saved cards for patrons a standard TNEW feature, and it will be also be fully available via the REST and SOAP APIs.
Thanks,
Chris Szalaj
Thanks, Chirs for your reply. You mean the Tessitura Version 13? Since you mention version 14 here, since the Tessitura is still in version 12.5.1
They're skipping version 13 because Triskaidekaphobia.
I've gotten a couple of follow ups on this post so I wanted to put a few more details out - While Tessitura is tokenizing the card number in the current release in some cases, it isn't consistently tokenizing and storing it for for all supported payment processors, via both web and client. In Version 14, tokens will be collected and stored when orders are processed via the client or the REST API, and there will be support for Notifying Tessitura whether or not it is the patron's preference that we store the token for future checkout.
As a result, there isn't a graceful way to currently build a "store my card" feature via the APIs, until v14 is released. But, as of v14, this will be fully supported in the REST API.
Thanks again Chris