Analogue ticket exchange systems and methods

Abstract

A system for providing frictionless transfer of tickets at a venue comprising: a server system comprising at least one server, a processor, and a database; at least one user device; and at least one unique ticket ID corresponding to a particular seat or ticket; wherein the server performs the following method: accessing the system via the user device and identifying a first ticket corresponding to an event, said first ticket having a unique ticket ID; validating ownership of the first ticket through a confirmation process by validating the unique ticket ID and storing the same within the database; identifying a second ticket for exchange; and confirming the exchange of the first ticket and the second ticket.

What is claimed is: 
     
         1 . A system for providing frictionless transfer of tickets at a venue comprising:
 a. a server system comprising at least one server, a processor, and a database; at least one unique ticket ID corresponding to a particular seat or a ticket; and at least one user device;   b. accessing the system via the user device and identifying a first ticket corresponding to an event, said first ticket having a unique ticket ID;   c. validating ownership of the first ticket through a confirmation process by validating the unique ticket ID and storing the same within the database;   d. identifying a second ticket for exchange; and   e. confirming the exchange of the first ticket and the second ticket.   
     
     
         2 . The system of  claim 1  wherein the step of identifying a first ticket comprises providing an image of the ticket, providing the unique ticket ID, scanning a machine-readable code comprising the unique ticket ID, or manually inputting ticket information. 
     
     
         3 . The system of  claim 1  wherein the user device comprises a device ID. 
     
     
         4 . The system of  claim 1  wherein the process of validating the ownership of the first ticket further comprises a step selected from the group consisting of: providing an image of the ticket, confirming a device ID, confirming an e-mail address, confirming a phone number, confirming a credit card number, providing an image of the seat, scanning the ticket, certifying the ownership of the ticket, providing verification from a user profile, and combinations thereof. 
     
     
         5 . The system of  claim 1  wherein an image of the ticket is stored within the database and an image of the second ticket is provided to the user device upon exchange of the first ticket for the second ticket. 
     
     
         6 . The system of  claim 1  wherein the first ticket has a value different than the second ticket and wherein a payment is made to offset the difference in value. 
     
     
         7 . The system of  claim 1  wherein the exchange of the first ticket and the second ticket is provided by transferring the first ticket and the second ticket through the system and providing the unique ticket ID and/or an image of the ticket to the user device. 
     
     
         8 . The system of  claim 1  wherein after the exchange, the server updates the database with a new ticket ID for each of the first ticket and the second ticket. 
     
     
         9 . The system of  claim 1  wherein the database stores a transaction history for the exchange of the first ticket and the second ticket. 
     
     
         10 . The system of  claim 1  wherein the ticket exchange is confirmed by scanning either of the first or second ticket after the ticket exchange. 
     
     
         11 . The system of  claim 1  wherein a difference in price exists between the first and second tickets and wherein an exchange of funds is held in escrow until confirmation of the ticket exchange. 
     
     
         12 . The system of  claim 1  wherein the exchange of the ticket comprises appending a new character to the unique ID to define a new unique ID, which is stored within the database. 
     
     
         13 . The system of  claim 1  further comprising wherein the unique ID corresponds to a ticket, wherein the ticket defines a geolocation, and wherein the ticket is verified when a geolocation of the user device matches the geolocation of the ticket. 
     
     
         14 . The system of  claim 1  further comprising wherein the unique ID is modified by appending at least one additional alphanumeric character to the unique ID to define a new unique ID after a transaction is completed and storing the new unique ID in the database with a timestamp corresponding to the time of the ticket exchange. 
     
     
         15 . The system of  claim 1  wherein an exchanged ticket is provided with a time based access to the ticket. 
     
     
         16 . The system of  claim 1  wherein the values of the first and second tickets are priced according to any one of dynamic pricing, the first and second tickets being valued by auction, the first and second tickets being set at a value by the user, and combinations thereof. 
     
     
         17 . The system of  claim 1  wherein the ticket exchange occurs after scanning one or both of the tickets for entry into a venue. 
     
     
         18 . A system for exchange of at least two tickets within an app-based system, the system comprising:
 a graphical user interface (GUI), at least one server, at least one database, and at least one user device;   a first ticket and a second ticket, each defined within the system; and   a value ascribed to each of the first ticket and the second ticket;   the system performing the following method to effectuate the exchange of the at least two tickets:   a. defining a first unique ticket ID to the first ticket and a second unique ticket ID to the second ticket within the database;   b. determining a difference in value between the first ticket and the second ticket;   c. performing a request through the app-based system to request the exchange of the first ticket for the second ticket;   d. receiving an approval of the request to exchange; and   e. exchanging the first ticket for the second ticket.   
     
     
         19 . The system of  claim 18  wherein step (e) further comprises sending the unique ticket IDs for the first and second tickets to a user device connected with the exchange. 
     
     
         20 . A system for exchange of at least two tickets within an app-based system, the system comprising:
 a graphical user interface (GUI), at least one server, at least one database, and at least one user device;   a first ticket and a second ticket, each defined within the system; and   a value ascribed to each of the first ticket and the second ticket;   the system performing the following method to effectuate the exchange of the at least two tickets:   a. receiving a request from the server within the database to input a first unique ticket ID to the first ticket and a second unique ticket ID to the second ticket;   b. updating the database with the first and second unique ticket IDs with a timestamp corresponding to the time of receipt;   c. requesting a price for each of the first ticket and the second ticket from the server;   d. determining a difference in value between the first ticket and the second ticket;   e. performing a request through the app-based system to request the exchange of the first ticket for the second ticket and defining the difference in price between the value of the first ticket and the second ticket in the request;   f. receiving an approval of the request to exchange;   g. providing a transfer of value based on the difference in the price between the first ticket and the second ticket and updating the same within the database;   h. creating a new database entry comprising a new unique ticket ID; and   i. exchanging the first ticket for the second ticket.