Moving to Element Payment Services

Hi,

We are in the process of moving to Element Payment Services, and I am wondering if the "account token" is supplied to us or if we should take the Merchant number and encrypt it in Tessi security.I'm assuming the Merchant number is the Account ID and the MID# is the Acceptor ID and the TID# is the Terminal ID.

Thank you,

Lou Ann

Parents
  • Hi Lou Ann,

    We've just recently completed our migration to Element (gateway only), so I will add in my two cents.

    The Account ID will be the ID supplied to you from Element to identify your organization.

    The Acceptor ID is Element-ese for your merchant number (MID).

    TID# is the Terminal ID.

    The Account Token will be supplied to you by Element, and that's what you encrypt via the Tessitura Security module.

    Once you supply Element with all the information from your bank, and they then set up your merchants, you'll be able to log into the accounts at the website and the information you need for the config file will be listed there. (What Tessitura version are you on?)

    Let me know if I can help further.

    Karen

  • Hi Karen,

    Thanks for your info it was very helpful. We hadn't logged into Element to get the Account token and AccountID. We've since switched to Element as a payment gateway and have implemented the SSRS report available on TASK.

    Some issues and observations:

    For V12.1.2, TIM encrypts the account token -- no longer need to do it thru Tessitura Security.

    We've had a couple of one-minute internet network connectivity issues since where internet for our call centre has been lost for a minute or so and then come back; however, Element has taken 15 min to get back online. There seems to be a timeout issue happening. Restarting the payment gateway service may be the only solution.

    Previously, when we hosted the credit card server we would close the batch at midnight our time every day and send the day's cc batch. Consequently our accountant could settle each day's cc transactions if necessary.  However now with Element the batch is closed between 1-1:30 central time so reconciling is more challenging to do on a day-by-day basis.

    Thank you,

    Lou Ann

     

     

     

Reply
  • Hi Karen,

    Thanks for your info it was very helpful. We hadn't logged into Element to get the Account token and AccountID. We've since switched to Element as a payment gateway and have implemented the SSRS report available on TASK.

    Some issues and observations:

    For V12.1.2, TIM encrypts the account token -- no longer need to do it thru Tessitura Security.

    We've had a couple of one-minute internet network connectivity issues since where internet for our call centre has been lost for a minute or so and then come back; however, Element has taken 15 min to get back online. There seems to be a timeout issue happening. Restarting the payment gateway service may be the only solution.

    Previously, when we hosted the credit card server we would close the batch at midnight our time every day and send the day's cc batch. Consequently our accountant could settle each day's cc transactions if necessary.  However now with Element the batch is closed between 1-1:30 central time so reconciling is more challenging to do on a day-by-day basis.

    Thank you,

    Lou Ann

     

     

     

Children
No Data