Tickera, Web app checkin

We are building a website [login to view URL] , but we have problems with the event manager tickera plugin for a site - checkin. TICKERA EXPERTISE IS A MUST. - the same product will be use to access the events (there are several events) 3,5 or 7 times.. it depends on the product validation is via QR Code. - social networking interfase for marketing purpose - documentation is online within the supported software developer [login to view URL] - show which event it has been assisted - they cannot assist the same event, the same date twice i want to know if you have tickera experience? SITE URL: [login to view URL] Imagine a citypass... Now.. you can use the same QR code to access different attractions (each attraction uses a unique API Key in the checkin app. We can have the selection of each one.. just after they checkin.. :: the problem is that we can only manage with the Tickera number of times to use.. (that's ok) but we cannot let the people.. get in the same attraction more than once.. // this is the main Issue..... The second one.. is that we need.. at least.. (if the main issue cannot be solved).. to have a web with the query of the information in the mysql created in our tickera, showing the attractions the user already redeem, and to be able to redeem again.. with a QR reader.. using a cell phone. some more details we have this website build over the WP platform, and we are using the DIVI theme to develop the static webpage for our customers, BUT WE need to buy the tickera plugin (we are now using it free), and when we buy the tickera pllugin the bridge is included. The main problema is that we are a city pass product, Our products are that you can buy 3, 5, 7 or 9 attractions in just one ticket, AND THE CHECKIN app that is provided freely with tickera, doesn`t gave us the information on which of this attractions have already been checked.. so we need to take out info from the mysql (we think is somehow hidden by tickera) but we need in case of giving access to the pass holder.. thats why we need tickera expertise. I am not clear about "somehow hidden by tickera) " we can`t find the data in the database.. we think is encrypted of hidden somehow.. to avoid.. using it in other way.. (but tickera support) doesn`t answer.. so you want know all attends name through email the first one is the app.. (we need info there).. through a web app with a QR code reader.. the second one is the detail.. where it says API Key,, is the name of every different atraction.. (and this can onlly be checkin once).. now it just.. gives access to anyone..with the only limit of the checkin times.. now by attraction and the third one is the information.. in the admin, but we need it.. on a webapp so the attractions can get the info all this information is in the database ok so after purchase you need  ticket details to send and api after purchase, customer receive a email with a QR. // but in the operations side we need ticket details and the attraction where the customer already make checkin in order to give or not access, because every pass is just for one access to every attraction