Networked barcode verification system

Abstract

Systems and methods are described for barcode verification. Optionally, a barcode scanner/imager is coupled to a verification system over a network. The verification system receives over the network barcode data associated with an item, such as a ticket, and associated information. The verification system uses the barcode data and associated information to determine if the barcode is valid and corresponds to an identified event. The verification system transmits a verification result.

What is claimed is: 
     
         1 . A method of verifying a ticket for transfer using a ticket system, comprising:
 receiving a first barcode associated with the ticket for offering transfer for the ticket by a first user, who had previously purchased the ticket, for a ticketed event;   determining if the received first barcode, associated with the ticket for offering transfer for the ticket, is in accordance with a first specified format;   determining if the received first barcode, associated with the ticket for offering transfer for the ticket, corresponds to the first barcode stored in a data store;   determining if event data, including at least an event identifier, received in association with the first barcode, associated with the ticket for offering transfer for the ticket, corresponds to stored event data, including at least a stored event identifier of the ticketed event, associated with an issued ticket for the ticketed event; and   transmitting verification indication based at least in part on the determination that:
 the received first barcode, associated with the ticket for offering transfer for the ticket, is in accordance with the first specified format; 
 the received first barcode, associated with the ticket for offering transfer for the ticket, corresponds to the first barcode stored in the data store; and 
 the received event data including at least the event identifier, associated with the ticket for offering transfer for the ticket, corresponds to the event data, including at least the stored event identifier of the ticketed event, associated with the issued ticket for the ticketed event; 
   sending a notification over a network, the notification including an ticket identifier (ID) assigned by the ticket system to facilitate the ticket being transferred;   determining a second barcode associated with the ticket transfer request by the ticket system, wherein the second barcode is different than the first barcode; and   sending barcode data corresponding to the second barcode and the event data to a second user.   
     
     
         2 . The method as defined in  claim 1 , the method further comprising:
 providing an interface configured to receive event data, including at least the event identifier, including at least a name, provided by the first user offering the ticket;   determining if the received event data, including at least the event identifier, corresponds to the first barcode stored in the data store; and   wherein the verification indication is based, in part, on the determination that the received event data, including at least the event identifier, corresponds to the first barcode stored in the data store.   
     
     
         3 . The method as defined in  claim 1 , wherein the stored event identifier is chosen from a group consisting of event name; event time; event day; ticket seating information; venue; and ticket price. 
     
     
         4 . The method as defined in  claim 1 , wherein the first or second barcode is a two dimensional barcode. 
     
     
         5 . The method as defined in  claim 1 , the method further comprising determining if the ticket is transferable based at least in part on an indication that the event date has passed or that there is insufficient time before the event to process a ticket transfer. 
     
     
         6 . The method as defined in  claim 1 , wherein the ticket ID is used to access the ticket by the second user. 
     
     
         7 . A ticket system of verifying a ticket for transfer, comprising:
 an interface configured to receive a first barcode associated with the ticket for offering transfer for the ticket by a first user who had previously purchased the ticket, for a ticketed event;   non-transitory memory storing program code, that when executed by a computing system is configured to cause the computing system to:
 determine if the received first barcode, associated with the ticket for offering transfer for the ticket, is in accordance with a first specified format; 
 determine if the received first barcode, associated with the ticket for offering transfer for the ticket, corresponds to the first barcode stored in a data store; 
 determine if event data, including at least an event identifier, received in association with the first barcode, associated with the ticket for offering transfer for the ticket, corresponds to stored event data, including at least the stored event identifier of the ticketed event, associated with an issued ticket for the ticketed event; 
 transmit a verification indication based at least in part on the determination that:
 the received first barcode, associated with the ticket for offering transfer for the ticket, is in accordance with the first specified format; 
 the received first barcode, associated with the ticket for offering transfer for the ticket, corresponds to the first barcode stored in the data store; and 
 the received event data including at least the event identifier, associated with the ticket for offering transfer for the ticket, corresponds to the event data, including at least a stored event identifier of the ticketed event, associated with the issued ticket for the ticketed event; 
 
 send a notification over a network, the notification including an ticket identifier (ID) assigned by the ticket system to facilitate the ticket being transferred; 
 determine a second barcode associated with the ticket transfer request by the ticket system, wherein the second barcode is different than the first barcode; and 
 send barcode data corresponding to the second barcode and the event data to a second user. 
   
     
     
         8 . The ticket system as defined in  claim 7 , wherein the program code is further configured to cause the computing system to:
 provide an interface configured to receive event data, including at least the event identifier, including at least a name, provided by the first user offering the ticket;   determine if the received event data, including at least the event identifier, corresponds to seating data stored in the data store; and   wherein the verification indication is based, in part on the determination that the received event data, including at least the event identifier, corresponds to the seating data stored in the data store.   
     
     
         9 . The ticket system as defined in  claim 7 , wherein the stored event identifier is chosen from a group consisting of event name; event time; event day; ticket seating information; venue; and ticket price. 
     
     
         10 . The ticket system as defined in  claim 7 , wherein the first or second barcode is a two dimensional barcode. 
     
     
         11 . The ticket system as defined in  claim 7 , wherein the program code is further configured to cause the computing system to determine if the ticket is transferable based at least in part on an indication that the event date has passed or that there is insufficient time before the event to process a ticket transfer. 
     
     
         12 . The ticket system as defined in  claim 7 , wherein the ticket ID is used to access the ticket by the second user. 
     
     
         13 . The ticket system as defined in  claim 7 , wherein the program code is further configured to cause the computing system to determine if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the ticket has already been transferred by a user. 
     
     
         14 . A non-transitory, tangible computer readable memory storing program code that when executed by a computing system is configured to cause the computing system to perform verification operations comprising:
 receive a first barcode associated with the first barcode of a ticket associated with a ticketed event;   receive event data provided by a first user offering the ticket, for the ticket by a first user who had previously purchased the ticket, for the ticketed event;   determine if the received the first barcode is in accordance with a first specified format;   determine if the received the first barcode corresponds to the first barcode stored in a data store;   when the received the first barcode corresponds to the first barcode stored in the data store, determine if the received event data, including at least the first user supplied event identifier, corresponding to that of the ticket for offering transfer, corresponds to the event data, including at least a stored event identifier corresponding to the ticketed event;   transmit a verification and transfer right indication based at least in part on the determination that:
 the received the first barcode is in accordance with the first specified format; 
 the received the first barcode corresponds to the first barcode stored in the data store; 
 the received event data, including at least the first user supplied event identifier, corresponding to the ticket for offering transfer, corresponds to the event data, including at least the stored event identifier corresponding to the ticketed event, associated with an issued ticket for the ticketed event; and 
   send a notification over a network, the notification including an ticket identifier (ID) assigned by a ticket system to facilitate the ticket being transferred;   determine a second barcode associated with the ticket transfer request by the ticket system, wherein the second barcode is different than the first barcode; and   send barcode data corresponding to the second barcode and the event data to a second user.   
     
     
         15 . The non-transitory, tangible computer readable memory as defined in  claim 13 , wherein the program code is further configured to cause the computing system to:
 provide an interface configured to receive event data, including at least the event identifier, including at least a name, provided by the first user offering the ticket;   determine if the received event data, including at least the event identifier, corresponds to seating data stored in the data store; and   wherein the verification indication is based, in part on the determination that the received event data, including at least the event identifier, corresponds to the seating data stored in the data store.   
     
     
         16 . The non-transitory, tangible computer readable memory as defined in  claim 13 , wherein the first or second barcode is a two dimensional barcode. 
     
     
         17 . The non-transitory, tangible computer readable memory as defined in  claim 13 , wherein the stored event identifier is chosen from a group consisting of event name; event time; event day; ticket seating information; venue; and ticket price. 
     
     
         18 . The non-transitory, tangible computer readable memory as defined in  claim 13 , wherein the program code is configured to cause the computing system to determine if the ticket is transferable based at least in part on an indication stored in computer readable memory that the event date has passed or that there is insufficient time before the event to process a ticket transfer. 
     
     
         19 . The non-transitory, tangible computer readable memory as defined in  claim 13 , wherein the ticket ID is used to access the ticket by the second user. 
     
     
         20 . The non-transitory, tangible computer readable memory as defined in  claim 13 , wherein the program code is configured to cause the computing system to determine if the ticket is transferable based at least in part on an indication stored in computer readable memory that the ticket has already been transferred by the first user.