I've configured settings.ticketevolution.com to use sandbox Samurai merchant keys and payment processor. When a site visitor buys tickets, the payment form is generated via the Samurai API so the credit card info never touches our site. My question is, how does the customer order and associated client records get created on TicketEvolution? Does this somehow happen automatically? Is there anywhere to see this in action (i.e. a sandbox version of the broker exchange)? Thanks!
3 comments
-
Permanently deleted user I’m not sure what you mean by “the payment form is generated by the Samurai API”.
In order to create the order (which in turn causes Samurai to charge/authorize the card if you have it configured that way) you need to create a customer order via the TEvo API.
-
Brad Carson To integrate Samurai I have been following the steps described here: https://samurai.feefighters.com/developers/ruby/api-reference#creating-a-payment-method-via-transparent-redirect. Their code generates the payment form and pretty much handles everything except validation of non-credit card fields. But, I'm guessing from your comment that this is entirely incorrect and that I will have to develop my own custom payment form and implement SSL since the credit card will be passed to our site before being passed to TE. I thought the benefit of Samurai was that all of this was all handled for you.
-
Permanently deleted user Hi Brad,
The API is very tightly integrated with Samurai so that you do not have to work directly with the Samurai API. Meaning all of the interaction between Samurai will take place as a result of the create/accept/reject order actions so that all you have to do is pass the credit card info and order info to the Ticket Evolution API and everything will happen automatically. If you have addiitonal questinos regarding these interactions please reeach out but you do not need to work directly with the Samurai API.