I don’t get it - why not just tie the ticket to a name and address at time of purchase? Then verify that matches the person using government issued ID upon entry?
replies(2):
* I buy a ticket for a friend (maybe as a present) but don't actually want to go to the concert
* I buy more than one ticket for a group of people (I'll be attending the concert)
* I buy a ticket but have to cancel at the last minute and want to give it to a friend
* I don't have an easily available government ID (maybe I never got a drivers license, maybe my drivers license expired, etc.)
* People attending the event aren't American. They will have their passports from other countries. How will you verify each passport is valid?
* The event draws of people from a majority of the 50 states in the USA, with each state having different government IDs (driver's license) with different versions of the IDs within each state. What are the logistics of validating the IDs presented?
In the base case of one ticket per individual that has a valid government ID that has their current address printed on the ID, what service are you using to validate this ID and to validate that the presenter of the ID is associated with the ID? What is the cost and how many transactions can it handle per second?
This way a platform also does not need to handle any sensitive data.
A ticket provider would have to allow reassigning tickets to other people through their platform - make it a "maximum 3 people for automatic approval".