TNEW and Duplicate Payments with WorldPay

Hello Everyone,

We have been noticing a marked increase in duplicate transaction in TNEW transactions. We use hosted payments with WorldPay. We are seeing multiple duplicate transactions a week. I wanted to see if anyone else has been having issues with payment that appear in WorldPay but don't transit to Tessitura (that seems to be the biggest issue) as well as WorldPay having multiple charges for the same purchase.

- Chris

Parents
  • Hi Christopher

    We are in the UK, use TNEW, have our hosted page with Windcave and are experiencing issues with payments  - 4 issues this week where the customer was charged 2x for the same order and issues since early October where the customer is charged but the order never makes it into Tessitura.  One the latter issue we are seeing in the logs that the sessionkey is being declared invalid and Tessitura is issuing a new one.  However the payment continues through the Windcave portal on the old session.  When it returns to Tessitura as payment successful, Tessitua rejects it because the session key does not match the new session key Tessitura issued.  

    When I look in the web tables, I see the old session key and the new one but all the order details have the original session key.  Even though the cart had not timed out, the order was not moved to the newly issued session key when it was issued.

    This has been escalated to Sara Nemeth.  I think they are struggling finding the root cause but believe it is a session sharing issue.  Our vendor Substrakt does grab the session key so the customer can move back and forth between our CMS and our TNEW sides of the website without needing to login to both but they use the Tessitura approved API method of grabbing the session key.

    Where the customer is charged twice we know that 2 of the 4 had the first card declined but charged and the second card charged as well.  We are looking at the logs on those.


    Regards
    Roberta

Reply
  • Hi Christopher

    We are in the UK, use TNEW, have our hosted page with Windcave and are experiencing issues with payments  - 4 issues this week where the customer was charged 2x for the same order and issues since early October where the customer is charged but the order never makes it into Tessitura.  One the latter issue we are seeing in the logs that the sessionkey is being declared invalid and Tessitura is issuing a new one.  However the payment continues through the Windcave portal on the old session.  When it returns to Tessitura as payment successful, Tessitua rejects it because the session key does not match the new session key Tessitura issued.  

    When I look in the web tables, I see the old session key and the new one but all the order details have the original session key.  Even though the cart had not timed out, the order was not moved to the newly issued session key when it was issued.

    This has been escalated to Sara Nemeth.  I think they are struggling finding the root cause but believe it is a session sharing issue.  Our vendor Substrakt does grab the session key so the customer can move back and forth between our CMS and our TNEW sides of the website without needing to login to both but they use the Tessitura approved API method of grabbing the session key.

    Where the customer is charged twice we know that 2 of the 4 had the first card declined but charged and the second card charged as well.  We are looking at the logs on those.


    Regards
    Roberta

Children
No Data