Still meet today 5/19 via Zoom

What a great meeting!  We really appreciate everyone who shared their experience going live with TMS!  It was very helpful to hear from consortiums who are hosted with TNEW and self-hosted with a custom website. 

Nancy Sheleheda went live on Monday, Henry Kelly on May 1st and Michael Dorsey last December. 

*I may not have captured everything we discussed, so I invite all the attendees to please add more details or provide clarification.  (Also, these are specific orgs experiences and does not mean this will happen to your organization.  Please refer to the documentation!)

**I also invite any Tessitura staff to clarify, confirm or address any issues.  Again, these are my quick notes from the meeting and there may be more information to further understanding.

Plan ahead

• Upgrade to 15.2.35 first.  There are enough fixes/enhancements from .33 and .34, that it is worth it.
• CVV requirement for all transactions, which impact any mailed-in credit cards.
• Unreferenced refunds have a 90-day limitation. 
• Development teams have to use uncontrolled batches.  Update procedures and train in advance.
• Deviceless entry does not tokenize cards and must have a device to do so. 
• All tokens will be removed before cutover, so plan on communicating with your donors to ask for the credit card number. Worldpay offers a token transfer, but there are risks.
• Going live can take a while depending on one org or consortium.  There are limitations on the time of day, so do not expect to do this overnight.  Work with your contact on that.

Challenges

• Tokenized cards coming over from Worldpay.  One had about half that did not come over correctly.  And another experienced a very slow upload.
• There is a pledge billing bug and there is no workaround, but a fix is coming.  (This may be specific to consortiums, but not sure.)
• Reporting out of the box is challenging.  There is a reconciliation helper, basically a spreadsheet with a 'super macro' to match transactions in Adyen vs. Tessitura gateway.  This helps find the discrepancies and do less manual investigating.
• Tessitura staff have a lot on their plate launching TMS for many orgs and response times seem a bit slower.

Benefits

• SOOOO Much better than Worldpay and Windcave!
• In version 15.2.35
  • Adyen no longer charge a $.01-1.00 as a pre-auth to use that token in the future. 
  • There is a cost savings of .09 per attempt too.
  • Easier set up for deviceless entry/back office since it will be based on Security and not machine name.

Hope this helps! Trini

Thanks for sharing these notes, Trini! We are currently in progress on transition and have been coming across an issue with grabbing a saved card to charge a subsequent payment.  The credit card saves fine to the constituent record, and the payment plan gets setup properly, but when I try to manually charge another payment (which is something we would do if there was an issue with the billing utility) I can't get any cards to come up.  I'm wondering if this matches the note you wrote here about a pledge billing bug? We are on v15.2.34.

Hi Kanani Reichlin That's a great question and I believe it's the same issue.  Henry had mentioned it and I believe Nancy tested while on the call and received an error.  Nancy Sheleheda and Henry Kelly would you like to add more details about your experiences regarding pledge billing?  Thank you!

Hi Trini Ramos and Kanani Reichlin"The error we see is when the utility is run and we see "Error retrieving Tessitura Merchant Services Api Credentials for OURACCOUNTCODE"  Once you've fully cutover your saved cards won't work until you re-tokenize with Adyen.  I'm not sure if that's part of your issue, though.

Yeah, that sounds like a different issue. But good to know and will anticipate that.  Thanks for sharing the details, Nancy!

Nancy ShelehedaThis is somewhat off-topic for this discussion, but...

The error you quote is exactly what our web developer is seeing when querying our Test environment, which has our initial setup for Tessitura Merchant Services. Did you learn anything new about that error, like how to make it go away?

HI Clarke.  In Test, are you set up to use Tessitura's Test merchant AUTUMN RIDGE? Danielle Greaves is our Lead Web Developer and she just did a presentation at TLCC and there's a slide about how you can't test in Test against your actual Adyen account.  You have to use Tessitura's test Adyen account.

I tried replying by email, but it did not show up here. Thank you Nancy, and I am sorry I missed your message a few weeks ago. You are right that we had the wrong account for Test. Now we have the correct "Autumn Ridge" test account, but we are still getting the same error, now with those credentials. I am hoping we will solve this today.