CA3182000A1 - A system and method for providing tickets for a game or event - Google Patents

A system and method for providing tickets for a game or event Download PDF

Info

Publication number
CA3182000A1
CA3182000A1 CA3182000A CA3182000A CA3182000A1 CA 3182000 A1 CA3182000 A1 CA 3182000A1 CA 3182000 A CA3182000 A CA 3182000A CA 3182000 A CA3182000 A CA 3182000A CA 3182000 A1 CA3182000 A1 CA 3182000A1
Authority
CA
Canada
Prior art keywords
game
event
ticket
validation
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CA3182000A
Other languages
French (fr)
Inventor
Christopher Kampen
Jennifer Kampen
Nathan Fecteau
Kimberley Fecteau
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to CA3182000A priority Critical patent/CA3182000A1/en
Publication of CA3182000A1 publication Critical patent/CA3182000A1/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B11/00—Apparatus for validating or cancelling issued tickets
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/018—Certifying business or products
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0609—Buyer or seller confidence or verification

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Tourism & Hospitality (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A system and method for providing tickets for a game or event is described. A central server that has a database with ticket information is provided. The central server is in communication with at least one user interface. The at least one user interface each have a user input for inputting information into the user interface. Information that is entered using the user input is sent to the central server for comparison to the database with ticket information. A ticket validator is provided that is used to confirm the validity of a ticket. The ticket validator has a first validation and a second validation. The first validation and the second validation are entered into the user interface and compared to the database to confirm a match of information between the ticket validator and the ticket information in the database.

Description

TITLE
[0001] A System and Method for Providing Tickets for a Game or Event FIELD OF THE DISCLOSURE
[0002] The present application relates generally to a system and method for providing tickets for a game or event and more particularly to a system and method for providing tickets for a game or event with ticket validations.
BACKGROUND
[0003] This section provides background information to facilitate a better understanding of the various aspects of the invention. It should be understood that the statements in this section of this document are to be read in this light, and not as admissions of prior art.
[0004] When purchasing a ticket for a game or event, there is always a risk that a purchaser could receive a forged or already used ticket. When this happens, there is rarely any recourse for the purchaser and the purchaser loses the purchase price of the ticket. This can lead to purchasers being wary of purchasing tickets for games and events that they might otherwise be willing to pay for.
BRIEF SUMMARY
[0005] There is provided a system for providing tickets for a game or event. A
central server is provided that has a database with ticket information, the central server is in communication with at least one user interface. The user interfaces each have a user input that allows a user to enter information into the user interface. The information entered using the user input is sent to the central server for comparison to the database with ticket information. A ticket validator is provided to confirm the validity of a ticket. The ticket validator has a first validation and a second validation. The first validation and the second validation are entered into the user interface and are then sent to the database to confirm that a match exists between the ticket validator and the ticket information in the database.

Date Regue/Date Received 2022-11-16
[0006] In one embodiment, a processor is provided for running a game when the information entered using the user input matches the ticket information in the database.
[0007] In one embodiment, the first validation is a OR code. The OR code may be entered into the user interface by scanning the OR code.
[0008] In one embodiment, the second validation is a randomly generated alpha-numeric code.
[0009] In one embodiment, a user received a visual notification of the authenticity of the ticket when the first validation and the second validation match the ticket information in the database.
[0010] In one embodiment, the visual notification further confirms if the ticket is playable, already played, lost, or stolen.
[0011] In one embodiment, a game code is provided on the ticket, the game code providing access to an online game.
[0012] In one embodiment, the user interface provides information related to the game or event including at least one of a title for the game or event, a date for the game or event, a location for the game or event, an organizer of the game or event, at least one prize associated with the game or event, a tutorial for the game or event, a preview for the game or event, or a set of rules for the game or event.
[0013] There is also provided a method for providing tickets for a game or event. A database containing ticket information is provided and at least one user interface is provided.
Each of the at least one user interfaces has a user input that allows information to be entered into the user interface. A plurality of tickets are provided. Information is set from the user interface to the database for comparison with the ticket information. One or more of the plurality of tickets can be validated using a ticket validator. The ticket validator confirms the validity of the tickets. The ticket validator has a first validation and a second validation. The first validation and the second validation are entered into the user interface and the information is sent to the database to confirm that a match of information between the ticket validator and the ticket information in the database exists.
[0014] In one embodiment, a processor is provided for running a game when the information entered into the user input matches the ticket information in the database.

Date Regue/Date Received 2022-11-16
[0015] In one embodiment, the first validation is a OR code. The OR code may be entered into the user interface by scanning the OR code.
[0016] In one embodiment, the second validation is a randomly generated alpha-numeric code.
[0017] In one embodiment, a user received a visual notification of the authenticity of the ticket when the first validation and the second validation match the ticket information in the database.
[0018] In one embodiment, the visual notification further confirms if the ticket is playable, already played, lost, or stolen.
[0019] In one embodiment, a game code is provided on the ticket, the game code providing access to an online game.
[0020] In one embodiment, the user interface provides information related to the game or event including at least one of a title for the game or event, a date for the game or event, a location for the game or event, an organizer of the game or event, at least one prize associated with the game or event, a tutorial for the game or event, a preview for the game or event, or a set of rules for the game or event.
BRIEF DESCRIPTION OF THE DRAWINGS
[0021] These and other features will become more apparent from the following description in which references are made to the following drawings, in which numerical references denote like parts. The drawings are for the purpose of illustration only and are not intended to in any way limit the scope of the invention to the particular embodiments shown.
[0022] FIG. 1 is a schematic view of a system for providing tickets for a game or event.
[0023] FIG. 2 is a schematic view of a ticket validator.
[0024] FIG. 3 is a top plan view of a ticket.
[0025] FIG. 4 is a top plan view of one page of level one of the user interface.
[0026] FIG. 5 is a top plan view of one page of level two of the user interface.
[0027] FIG. 6 is a top plan view of another page of level two of the user interface.

Date Regue/Date Received 2022-11-16 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0028] A system for providing tickets for a game or event, generally identified by reference numeral 10, will now be described with reference to FIG. 1 through FIG. 6.
[0029] Referring to FIG. 1, a system 10 for providing tickets for a game or event has a central server 12 and at least one user interface 14. The user interfaces 14 are in communication with central server 12.
While it is preferred that user interfaces 14 communicate with central server 12 wirelessly, it will be understood by a person skilled in the art that user interfaces 14 may be wired directly to central server 12. User interface 14 may include cellular phones, computers, kiosks, and any other suitable device known to a person skilled in the art. Central server 12 has a database 16 that contains information related to ticket information. Additional information about a game or event may also be stored within database 16. Each user interface 14 has a user input 18 that allows a user to enter information into user interface 14. User input 18 may include a screen, keyboard, camera, and any other suitable components known to a person skilled in the art. Information entered using user input 18 is sent to central server 12 for comparison to ticket information within database 16. Referring to FIG. 2, a ticket validator 20 is provided for confirming the validity of a ticket 22, shown in FIG. 3.
Referring to FIG. 3, ticket validator has a first validation 24 and a second validation 26. First validation 24 and second validation 26 are entered into user interface 14 and the information is sent to database 16 to confirm a match of information between ticket validator 20 and ticket information in database 16 exists. It will be understood by a person skilled in the art that first validation 24 and second validation 26 may be entered into user interface 14 simultaneously or one at a time. In the embodiment shown, first validation 24 and second validation 26 are both found on ticket 22 with first validation 24 being a OR
code and second validation 26 being an alpha-numeric code. In some embodiments, second validation 26 may be embedded within first validation 24, such as an alpha-numeric code embedded within a OR
code. A person interested in purchasing ticket 22 may use ticket validator 20 prior to finalizing a purchase to ensure the authenticity of ticket 22. Referring to FIG. 2, in the embodiment shown, when ticket validator 20 is used, potential purchaser uses user interface 14 to scan OR code (first validation 26) found on ticket 22, shown in FIG. 3. An image of the ticket appears on user interface 14 that allows user to compare an electronic version of ticket 22 to an electronic version.
Second validation 26, shown in FIG. 3, is also entered into user interface 14. Once the purchaser has completed their own comparison of the electronic ticket to the paper ticket, the validate ticket button 25 is pushed and the ticket Date Regue/Date Received 2022-11-16 information is sent to database 16 to confirm that ticket 22 has not been lost, stolen, or already played.
If a ticket is found to be invalid, the purchaser will receive a ticket invalid notification 27a. If a ticket is found to be valid, the purchaser will receive a ticket valid notification 27b.
[0030] Referring to FIG. 1, when system 10 is used in relation to games such as e-sports, lotteries, card games, slots, and any other suitable game, a processor 28 for running a game may be provided when the information entered using user input 18 matches ticket information in database 16. For events such as concerts, sporting events, and other events known to a person skilled in the art, processor 28 may provide access to a trailer or other promotional information. Referring to FIG. 3, a game code 30 may be provided on ticket 22. Game code 30 may provide access to an online game.
[0031] Referring to FIG. 2, when ticket validator 20 is used, a user may receive a visual notification 27a or 27b of the authenticity of ticket 22, shown in FIG. 3, when first validation 24 and second validation 26 match the ticket information in database 16. Visual notification 27a and 27b may also confirm if ticket 22 is playable, already played, lost, or stolen.
[0032] User interface 14 may provide information to a user related to the game or event to which ticket 22 relates. This may include, not is not limited to, a title for the game or event, a date for the game or event, a location for the game or event, an organizer of the game or event, at least one prize associated with the game or event, a tutorial for the game or event, a preview for the game or event, or a set of rules for the game or event.
[0033] System 10 may be used for a variety of games or events. As an example only, in one embodiment, system 10 is used in relation to a fundraising campaign that provides access to a skill-based game. In this embodiment, user interface 14 may provide access to different information and options depending upon the type of user entering information into user interface 14. The different information and options may require that specific access codes, usernames and passwords, or other authentications be provided to be shown. In the embodiment shown, user interface 14 provides links for fundraising consumers, purchasers, and administrators that require authentications to gain access to relevant information. It will be understood by a person skilled in the art that links for other types of information and options may also be provided.

Date Regue/Date Received 2022-11-16
[0034] In this embodiment, user interface 14 has three levels. Referring to FIG. 4, in the embodiment shown, level one provides marketing and information pages that are generally accessible to all and provides information about the game or event. The information about the game or event can include dates, locations where applicable, rules and regulations, prizes, advertisements, and any other information an operator may deem relevant to the game or event. Level one may provide information about the business utilizing system 10, details about how the fundraiser works, cost breakdowns, eligibility, geographical eligibility, age restrictions, legal information, frequently asked questions, and more. Referring to FIG. 5, in the embodiment shown, level two provides login access for game or event administrators and purchasers of tickets 22. Level two may allow for registration and secured sign in and can include more detailed information about the game or event. For fundraising consumers, referring to FIG. 6, level two provides access to make fundraising requests and provide necessary information for a fundraising request to be accepted. Fundraising requests may include information related to specific dates, details of the organization looking to fundraise, proof of eligibility of fundraiser, choosing of prizes, choosing the type of game or event, ticket design, payment options, tracking of ticket sellers, tracking of tickets, or any other suitable information that may be useful. For purchasers of tickets, level two allows them to play their tickets when connected to a game, register purchased tickets, choose prizes, or any other options set by an administrator. Level three provides administrative access to system 10. Level three requires a secure authentication for access and allows administrators to make changes to system 10, vet and approve fundraisers, set up a new fundraiser, confirm payments, generate tickets, provide statistics, complete fundraisers, provide prize options, set rules and regulations, set policies, look up financial statistics, or any other useful function for a system administrator. Generally, access to level two and level three will be found on level one but require an authentication to gain access to these levels.
[0035] Ticket validator 20 may be found on one or both of level one and level two of user interface 14.
When found on level one, ticket validator 20 is more easily accessed as generally there is no requirement for user authentication prior to use. However, for added security, ticket validator 20 may be found on level two after a potential purchaser has registered and signs into the more secure portion of user interface 14.
[0036] The type of game or event that relates to the tickets for the fundraiser may be chosen by a fundraising consumer, or game or event administrator when the tickets do not specifically relate to a Date Regue/Date Received 2022-11-16 fundraiser. The types of games or events may be limited by administrators. For fundraisers, it may be common to choose skill-based e-sport games, memory games, or other suitable nonrandom games.
However, it will be understood by a person skilled in the art that other types of games and random chance lotteries may be used. For games that are considered gambling, game or event administrators may be required to show proof of necessary permissions to run such a game.
[0037] Providing tickets 22 for a game or event that may be validated as authentic before purchase can be comforting for purchasers. This may be accomplished by providing a database 16 with ticket information that can be used to match information found on tickets 22 to information from database 16. Information on tickets 22 may be entered into a user interface 14 using a user input 18. Generally, this will include confirming that the ticket 22 has the correct information related to date, location, and type of game or event. The information entered into user interface 14 is send to database 16 for comparison with the ticket information found in the database 16. For greater security, a ticket validator is provided that allows for the validation of tickets 22 using a dual validation system. Ticket validator 15 20 has a first validation 24 and a second validation 26. Both the first validation 24 and the second validation 26 are entered into user interface 14 using user input 18 and the information is sent to database 16 to confirm a match of information between ticket validator 20 and ticket information in database 16. First validation 24 and second validation 26 may be randomly generated and may include taking a photograph of the ticket 22 for comparison purposes, scanning bar codes, scanning OR codes, 20 security tags, RFID detections, entering alpha-numeric codes, or any other means known to a person skilled in the art. Depending on the type of information being compared, user input 18 may include cameras, scanners, keyboards, screens, and other useful tools. Once ticket validator 20 has been used and information has been confirmed as matching, purchasers can make their ticket purchases with confidence. Visual notifications that confirm the authenticity of ticket 22 may be seen on user interface 14. Other notifications such as sound, tactile response, and any other suitable notifications known to a person skilled in the art may also be used. Notifications may also provide information detailing if ticket 22 is playable, already played, lost, or stolen.
[0038] A processor 28 for running a game may be provided when the information entered using user input 18 matches ticket information in database 16. This may allow immediate access to online games after a ticket 22 has been purchased. As a part of running the processor, a check may be made in database 16 to confirm payment for the ticket 22 has been received before access to a game is Date Regue/Date Received 2022-11-16 permitted. This can help to prevent a ticket from being used before it is purchased. A game code 30 may be provided on ticket 22 that allows for more simple access to an online game.
[0039] Any use herein of any terms describing an interaction between elements is not meant to limit the interaction to direct interaction between the subject elements, and may also include indirect interaction between the elements such as through secondary or intermediary structure unless specifically stated otherwise.
[0040] In this patent document, the word "comprising" is used in its non-limiting sense to mean that items following the word are included, but items not specifically mentioned are not excluded. A
reference to an element by the indefinite article "a" does not exclude the possibility that more than one of the element is present, unless the context clearly requires that there be one and only one of the elements.
[0041] It will be apparent that changes may be made to the illustrative embodiments, while falling within the scope of the invention. As such, the scope of the following claims should not be limited by the preferred embodiments set forth in the examples and drawings described above, but should be given the broadest interpretation consistent with the description as a whole.

Date Regue/Date Received 2022-11-16

Claims (16)

What is claimed is:
1. A system for providing tickets for a game or event, comprising:
a central server having a database with ticket information, the central server being in communication with at least one user interface;
the at least one user interface each having a user input for inputting information into the user interface, information entered using the user input is sent to the central server for comparison to the database with ticket information; and a ticket validator, the ticket validator confirming the validity of a ticket, the ticket validator having a first validation and a second validation, the first validation and the second validation being entered into the user interface, the first validation and the second validation being sent to the database to confirm a match of information between the ticket validator and the ticket information in the database.
2. The system for providing tickets for a game or event of claim 1 further comprising a processor for running a game when the information entered using the user input matches the ticket information in the database.
3. The system for providing tickets for a game or event of claim 1 wherein the first validation is a QR
code.
4. The system for providing tickets for a game or event of claim 3 wherein the second validation is a randomly generated alpha-numeric code.
5. The system for providing tickets for a game or event of claim 1 wherein a user receives a visual notification of the authenticity of the ticket when the first validation and the second validation match the ticket information in the database.
6. The system for providing tickets for a game or event of claim 5 wherein the visual notification further confirms if the ticket is playable, already played, lost, or stolen.
7. The system for providing tickets for a game or event of claim 1 further comprising a game code on the ticket, the game code providing access to an online game.
8. The system for providing tickets for a game or event of claim 1 wherein the user interface provides information related to the game or event including at least one of a title for the game or event, a date for the game or event, a location for the game or event, an organizer of the game or event, at least one prize associated with the game or event, a tutorial for the game or event, a preview for the game or event, or a set of rules for the game or event.
9. A method for providing tickets for a game or event, comprising the steps of:
providing a database containing ticket information;
providing at least one user interface, each of the at least one user interfaces having a user input for inputting information into the user interface;
providing a plurality of tickets;
sending the information input into the user interface to the database for comparison with the ticket information; and validating one or more of the plurality of tickets using a ticket validator, the ticket validator confirming the validity of the one or more of the plurality of tickets, the ticket validator having a first validation and a second validation, the first validation and the second validation being entered into the user interface, the first validation and the second validation being sent to the database to confirm a match of information between the ticket validator and the ticket information in the database.
10. The method for providing tickets for a game or event of claim 9 further comprising the step of providing a processor for running a game when the information entered using the user input matches the ticket information in the database.
11. The method for providing tickets for a game or event of claim 9 wherein the first validation is a QR
code.
12. The method for providing tickets for a game or event of claim 11 wherein the second validation is a randomly generated alpha-numeric code.
13. The method for providing tickets for a game or event of claim 9 further comprising the step of a user receiving a visual notification of the authenticity of the ticket when the first validation and the second validation match the ticket information in the database.
14. The method for providing tickets for a game or event of claim 13 wherein the visual notification further confirms if the ticket is playable, already played, lost, or stolen.
15. The method for providing tickets for a game or event of claim 9 further comprising a game code on the ticket, the game code providing access to an online game.
16. The method for providing tickets for a game or event of claim 9 wherein the user interface provides information related to the game or event including at least one of a title for the game or event, a date for the game or event, a location for the game or event, an organizer of the game or event, at least one prize associated with the game or event, a tutorial for the game or event, a preview for the game or event, or a set of rules for the game or event.
CA3182000A 2022-11-16 2022-11-16 A system and method for providing tickets for a game or event Pending CA3182000A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CA3182000A CA3182000A1 (en) 2022-11-16 2022-11-16 A system and method for providing tickets for a game or event

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CA3182000A CA3182000A1 (en) 2022-11-16 2022-11-16 A system and method for providing tickets for a game or event

Publications (1)

Publication Number Publication Date
CA3182000A1 true CA3182000A1 (en) 2024-05-16

Family

ID=91070386

Family Applications (1)

Application Number Title Priority Date Filing Date
CA3182000A Pending CA3182000A1 (en) 2022-11-16 2022-11-16 A system and method for providing tickets for a game or event

Country Status (1)

Country Link
CA (1) CA3182000A1 (en)

Similar Documents

Publication Publication Date Title
US10726656B2 (en) Identification verification system
US6755344B1 (en) Systems and methods for determining an authorization threshold
US7761384B2 (en) Strategy-driven methodology for reducing identity theft
US20130288768A1 (en) Method for tracking lottery purchases and notifying winners electronically
US20070152043A1 (en) Systems and methods for determining a need for authorization
KR100292837B1 (en) online ticket sales system and method for the same
US20010018660A1 (en) Electronic ticketing system and methods utilizing multi-service vistior cards
US20100325009A1 (en) Internet and mobile technologies based secured lottery system and method
JP2021058628A (en) Computing device and method for allowing user to play game
US9378514B2 (en) Secure tokenless transaction system and method
CN102742211A (en) Improvements relating to multifunction authentication systems
US11544640B2 (en) Method for providing online ticket service by using blockchain network and server using the same
JP2020009194A (en) Ticket management system and operation method thereof
US8473351B1 (en) Systems and methods for verifying authorization
JP2004126898A (en) Authentication and settlement system
CA3182000A1 (en) A system and method for providing tickets for a game or event
KR20090008012A (en) System for selling lottery ticket or race ticket using handy terminal
KR20000054685A (en) electronic merchandise coupon circulation method
KR102509972B1 (en) Genuine item verification system and method
US20150012392A1 (en) Method of ownership certification and authenticating commodity of value purchases via such ownership certification using currency serial numbers
AU2016204443A1 (en) Internet and mobile technologies based secured lottery system and method
KR20000037293A (en) System and method for providing gift by lottery through Internet
McGregor Consumer education and the OECD electronic commerce consumer protection guidelines
AU2014227522A1 (en) Internet and mobile technologies based secured lottery system and method
WO2002046984A1 (en) Method for secure transaction between a buyer and a seller