System and Process for Controlling and Verifying Transactions

Abstract

A system and process for controlling and verifying transactions has a central registry that includes one or more servers configured to retrieve and store registration information in a database. Registration terminals in communication with the central registry allow for registration of a participant in a program to track and limit consumption. Point-of-sale terminals communicate with the central registry to request authorization for a purchase. In an authorization request, the point-of-sale terminal communicates the identity of the prospective purchaser to the central registry, which in turn attempts to match the purchaser to a registered participant. In the case of a match, the central registry looks up the participant's purchase restrictions, and if the participant is restricted from a product or service that is being purchased, the central registry refuses authorization to complete the purchase, and the registered participant is prevented from purchasing the product or service.

Claims

1. A system for controlling and verifying transactions, comprising: one or more networks; one or more central registries; and one or more point-of-sale (POS) terminals, wherein the one or more POS terminals are configured to communicate with a central registry of the one or more central registries through a network of the one or more networks, send data corresponding to a registered participant to the central registry, request authorization for a transaction to be made to the registered participant, and deny the sale if the authorization is denied.

2. The system for controlling and verifying transactions of claim 1, further comprising means for selecting a designated driver from among a group of registered participants.

3. The system for controlling and verifying transactions of claim 2, wherein the one or more central registries are configured to deny authorization for a sale of alcoholic beverages to each registered participant of the group of registered participants until the designated driver is selected.

4. The system for controlling and verifying transactions of claim 3, wherein the one or more central registries are configured to authorize the sale of alcoholic beverages to all registered participants of the group of registered participants except the designated driver when a designated driver is selected.

5. The system for controlling and verifying transactions of claim 1, wherein the one or more central registries comprise a database associating prohibited and limited products and services with registered participants.

6. The system for controlling and verifying transactions of claim 5, wherein the central registries are configured to deny the authorization if the sale comprises a prohibited product or a prohibited service associated with the registered participant and provide a limited authorization if the sale comprises a limited product or a limited service associated with the registered participant.

7. The system for controlling and verifying transactions of claim 6, further comprising one or more registration terminals configured to communicate with a central registry of the one or more central registries through a network of the one or more networks, wherein the central registry is configured to receive information for a new participant and a new list of prohibited products and services from a registration terminal of the one or more registration terminals, and wherein the central registry is configured to add new entries to the database to associate the new participant with the prohibited products and services of the new list of prohibited products and services.

8. The system for controlling and verifying transactions of claim 7, wherein the database further associates surcharged products with the registered participants, and wherein the POS terminals are configured to add a surcharge when the sale comprises a surcharged product associated with the registered participant.

9. The system for controlling and verifying transactions of claim 7, wherein the registration terminals are further configured to receive updates to the prohibited and limited products and services associated with a registered participant and communicate the updates to a central registry of the one or more central registries, and wherein the central registry is configured to store the updates in the database.

10. A method for controlling and verifying transactions, comprising the steps of: providing one or more networks; providing one or more central registries; receiving identification information; sending the identification information to the central registry; receiving product information; sending the product information to a central registry of the one or more central registries; receiving a response from the central registry; and refusing transaction of a product if the response from the central registry comprises a denial of authorization to transact.

11. The method for controlling and verifying transactions of claim 10, further comprising the step of adding a surcharge if the response from the central registry comprises a surcharge requirement.

12. The method of controlling and verifying transactions of claim 10, further comprising the step of notifying the central registry of a completed transaction.

13. The method of controlling and verifying transactions of claim 10, wherein the step of receiving product information comprises scanning a barcode, QR code, or other printed code.

14. The method of controlling and verifying transactions of claim 10, wherein the step of receiving identification information comprises scanning an identification card or code based on an identification card.

15. The method of controlling and verifying transactions of claim 10, wherein the identification card is scanned with a magnetic stripe reader or chip reader.

16. A system for controlling and verifying transactions, comprising: one or more networks; one or more central registries, each central registry comprising: a database comprising a list of registered participants, one or more registration servers, and one or more verification servers; and one or more point-of-sale (POS) terminals, wherein each POS terminal of the one or more POS terminals is configured to communicate with a verification server through the network, send data corresponding to a registered participant of the registered participants to the verification server, request authorization for a transaction to be made to the registered participant, deny the transaction if the authorization is denied, and limit the transaction if a limited authorization is provided.

17. The system for controlling and verifying transactions of claim 16, wherein the database associates a list of prohibited and limited products and services with each registered participant of the registered participants.

18. The system for controlling and verifying transactions of claim 17, wherein the verification server is configured to deny the authorization if the transaction comprises a prohibited product or a prohibited service from the list of prohibited and limited products and services associated with the registered participant and to provide a limited authorization if the transaction comprises a limited product or a limited service from the list of prohibited and limited products and services associated with the registered participant.

19. The system for controlling and verifying transactions of claim 18, further comprising one or more registration terminals, each registration terminal configured to communicate with a registration server through the network, wherein the registration server is configured to receive information for a new participant, a new list of prohibited products and services, and a new list of limited products and services from a registration terminal of the one or more registration terminals, and wherein the registration server is configured to the new participant to the list of registered participants and associate the new list of prohibited products and services and the new list of limited products and services with the new participant.

20. The system for controlling and verifying transactions of claim 19, wherein the registration terminals are further configured to receive updates to the prohibited products and services associated with a registered participant of the list of registered participants and communicate the updates to the registration server, and wherein the registration server is configured to store the updates in the database.

21. The system of controlling and verifying transactions of claim 19, wherein the system is configured to adjust insurance rates and coverage for insurance comprising health, life, vehicle, personal injury, property, general, liability, disability, home owners, long term care, or umbrella insurance.

22. The system of controlling and verifying transaction of claim 19, wherein the system is configured to control use of substances to facilitate overcoming tobacco addiction, alcohol addiction, marijuana addiction, gambling addiction, video game addiction, internet addiction, medication dependency, diet-based addictions and behaviors or adhere to any agreement thereof.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The novel features of this invention, as well as the invention itself, both as to its structure and its operation, will be best understood from the accompanying drawings, taken in conjunction with the accompanying description, in which similar reference characters refer to similar parts, and in which:

[0039] FIG. 1 is a diagram of a system for controlling and verifying transactions;

[0040] FIG. 2 is a diagram of a central registry of a system for controlling and verifying transactions;

[0041] FIG. 3 is a diagram of a server of the central registry;

[0042] FIG. 4 is a diagram of a registration terminal configured for operation with a system for controlling and verifying transactions;

[0043] FIG. 5 is a diagram of a point-of-sale terminal configured for operation with a system for controlling and verifying transactions;

[0044] FIG. 6 is a flowchart illustrating a registration process performed with a registration terminal in communication with a registration server;

[0045] FIG. 7 is a flowchart illustrating the portion of the registration process performed by a registration server;

[0046] FIG. 8 is a flowchart illustrating a verification process performed with a point-of-sale terminal in communication with a verification server;

[0047] FIG. 9 is a flowchart illustrating the portion of the verification process performed by a verification server;

[0048] FIG. 10 is a diagram illustrating the designation of a designated driver through mobile computing devices; and

[0049] FIG. 11 is a diagram for a system for controlling and verifying transactions with multiple central registries and networks.

DETAILED DESCRIPTION

[0050] Referring initially to FIG. 1, a preferred embodiment of a system for controlling and verifying transactions is illustrated and generally designated 100. System 100 has a central registry 110 that receives registration data for participants in a program to track and control consumption and authorizes or rejects transactions for a registered participant.

[0051] A network 120, such as the Internet or another private or public network, allows registration terminals 134 and point-of-sale terminals 136 to communicate with central registry 110.

[0052] Registration terminals 134 communicate with central registry 110 through network 120 in order to register a new participant in a program for tracking and controlling consumption, removing a participant, or updating the limitations placed on a participant. Exemplary use cases for terminals 134 are healthcare providers; health insurance companies, courts, auto insurance companies, life insurance companies, and consumers themselves, as well as other parties that might have an interest in a person's participation in a program. In an exemplary use case, a healthcare provider provides its clients the ability to register in a “quitter” program that results in vendors denying purchase of an addictive substance, such as tobacco products or alcohol, as non-limiting examples, to the registered client. In another exemplary use case, a court registers or requires registration of a person convicted of an alcohol-related crime, resulting in the denial of sales of alcohol to the person convicted. In yet another exemplary use case, an insurer offers registration to its customers and provides a lower rate in exchange for registration in a program that lowers the risk for the insurer; for example, an auto insurer would offer a lower rate to customers who register in a program to limit alcohol purchases, or require registration as a prerequisite to insurance for a potential customer with convictions for driving while intoxicated (DWI) or similar offenses.

[0053] Point-of-sale terminals 136 communicate with the central registry 100 through network 120 in order to verify that a customer is not restricted from purchase of an item or use of a service.

[0054] Referring now to FIG. 2, an exemplary preferred embodiment of central registry 110 is illustrated. A database server 142 contains registration data. A registration server 144 in communication with database server 142 provides registration services to registration terminals 134. A verification server 146 in communication with database server 142 provides verification services to point-of-sale terminals 136.

[0055] In a simple embodiment, central registry 110 is a single server acting as database server 142, registration server 144, and verification server 146. The single-server embodiment is useful as a low-cost implementation of a central registry 100 for consumption tracking and control programs with limited geographic scope and registered participants. For programs of larger scope, it becomes appropriate to use embodiments with separate server hardware for each of the roles of database server 142, registration server 144, and verification server 146; some embodiments have multiples of each server, as the system 100 allows for expansion of resources as a program grows in number of participants and geographic scope.

[0056] Referring now to FIG. 3, a diagram of exemplary components of a verification server 146 is shown. Database server 142 and registration server 144 have the same structure as far as relates to the illustrated components. More particularly, each verification server 146 has a central processing unit (CPU) 152, non-transitory memory 154, a mass storage device 156 such as a hard drive, flash storage, or other form of mass storage, and network connection hardware 158 enabling verification server 146 to connect to network 120. Similarly, each database server 142 and registration 144 has a CPU 152, non-transitory memory 154, a mass storage device 156, and network connection hardware 158.

[0057] Referring now to FIG. 4, a diagram of exemplary components of a registration terminal 134 is shown, including a CPU 160, non-transitory memory 162, a mass storage device 164, network connection hardware 166, and one or more human interface devices (HID) 168. Network connection hardware 166 enables terminal 134 to connect to network 120. A non-limiting list of exemplary HIDs 168 includes computer monitors, keyboards, mouses, touchscreens, keypads, and microphones. HIDs 168 facilitate the entry of data necessary to register a new program participant or update the registration of an existing program participant.

[0058] Referring now to FIG. 5, an exemplary point-of-sale (POS) terminal 136 for a retail store is illustrated. Terminal 136 has a controller 172 including a CPU and non-transitory memory, input devices 174, a receipt printer 176, a product database 178, and a network connection 180 allowing terminal 136 to communicate with a verification server 146. Exemplary input devices 174 include a keyboard or keypad, a scanner such as a universal product code (UPC) scanner to read codes from products, an ID card scanner or other scanner, such as a biometric scanner, for identifying program participants, and a credit card terminal for payment processing. Some embodiments of terminal 136 include a receipt printer 176. A product database 178 maintains product information matched to UPCs or other product codes; in some embodiments, product database 178 is external to terminal 136 and accessed through network connection 180 or another network connection.

[0059] Some of the described features will not be present in all embodiments of terminal 136. As a non-limiting example, a service provider such as a casino may use a simplified terminal 136 with an ID scanner, controller 172, and network hardware for a network connection 180 to a verification server 146, in order to determine whether to admit an individual into the casino. Such embodiments do not require a product database 178, product scanner, or receipt printer, and so some embodiments lack these and other features unnecessary to their particular use case.

[0060] An exemplary terminal 136 for an online store has the same structure as a verification server 146 illustrated in FIG. 3, including a CPU 152, non-transitory memory 154, mass storage device 156, and network hardware 158.

[0061] Referring now to FIG. 6, a registration process performed with a registration terminal 134 is illustrated and generally designated 200. Process 200 is performed for registering a new user of system 100 in order to limit or track purchases, and a variant of process 200 is also used to update a registration to add, remove, or change limits and tracked purchases.

[0062] In step 202 of process 200, registration terminal 134 receives identification data provided by a user. In preferred embodiments, identification data includes the name and other identifying information of a prospective participant in a program for controlling and verifying transactions. In preferred embodiments, identification data also includes data used to match the participant's records in database 142 of central registry 110 with the participant obtaining a product or service at a POS terminal 136. For example, preferred embodiments are configured to obtain data from a magnetic card stripe, such as a stripe on a government identification card, healthcare provider card, or other card with a magnetic stripe. A magnetic stripe reader attached to a registration terminal 134 is used to obtain the data during registration, and a magnetic stripe reader from the input devices 174 of a POS terminal 134 (see FIG. 5) is used to obtain the data and send it to a verification server 146, which in turn matches it with the participant's records in database 142.

[0063] In step 204, the registration terminal 134 presents a user interface to the user through which a product or service, or a class of products and services, is selected. Non-limiting examples include, “cigarettes,” “tobacco products,” and “gambling services.” When a registration is being updated, existing products can be selected for changes or removal, and new products can be selected to add tracking or limits.

[0064] In step 206, the registration terminal 134 presents a user interface to the user through which purchase limits, if any are to be applied, are selected. Non-limiting examples of exemplary limits include a complete prohibition on purchase of the selected product, service, or class; a quantity limit during a specified time period, e.g., two packs of cigarettes per week, or twenty ounces of liquor per day; and a decreasing limit over time, e.g. a pack of cigarettes per day for two weeks, followed by a pack every two days for two weeks, and so on until a complete prohibition on purchase. Another exemplary type of limit is a requirement in conjunction with a purchase, such as the selection of a designated driver as a requirement prior to purchase of alcohol.

[0065] A time limit is also selected, indicating the duration of participation in the program for the selected products or services. For the time limit, any duration can be selected, including an option for the participant's entire lifetime. When the time limit is reached, the purchase limits and additional fees will no longer be applied.

[0066] In step 208, the registration terminal 134 presents a user interface to the user through which additional fees to be added to purchases can be configured. Additional fees can be added in lieu of restrictions or in addition to restrictions. Moreover, preferred embodiments of system 100 (see FIG. 1) provide an option for both fixed and progressive additional fees. By increasing in amount with the number of purchases, a progressive fee discourages overconsumption of the products or services to which it is attached.

[0067] When the purpose of registration is only to track the participant's consumption, neither limits nor fees will be selected. When a limits, fees, or tracking is selected for deletion in an existing registration, the selected product, service, or class is marked for a deletion request to be made in step 212, and steps 206 and 208 are skipped for the selected item.

[0068] In step 210, registration terminal 134 provides the option to enter data for additional products, services, or classes of products and services to be tracked or limited. If the user selects the option to enter further data, steps 204, 206, and 208 are repeated until all the desired products, services, and classes of products and services have been entered along with any limitations and additional fees for each. Once the user indicates in step 210 that all data has been entered, the process proceeds to step 212.

[0069] In step 212, registration terminal 134 sends the collected information from steps 202, 204, 206, and 208 to a registration server 144 (shown in FIG. 2).

[0070] Referring now to FIG. 7, a process performed by a registration server 144 (shown in FIG. 2) is illustrated and generally designated 220. Process 220 operates on registration server 144 in conjunction with step 212 (see FIG. 6) of process 200 (see FIG. 6) operating on a registration terminal 134.

[0071] In step 222, registration server 144 receives a connection request from registration terminal 134. In a preferred embodiment, a secure sockets layer (SSL) or transport layer security (TLS) handshake (SSL/TLS handshake) is performed, or a similar procedure for creating a secured connection in which cryptographic keys are exchanged is performed. Thus, a secure connection is created between registration terminal 134 and registration server 144. Registration server 144 requires authentication in which registration terminal 134 provides its credentials to ensure that it is authorized to register users in system 100.

[0072] In step 224, the registration server 144 receives identification data and product data sent from the registration terminal 134 in step 212 of process 200 (see FIG. 6).

[0073] In step 226, the registration server 144 checks the database to ensure that the participant is not already registered. If the participant is already registered, a message is sent to registration terminal 134, causing registration terminal 134 to display an error message, and in some embodiments, allow the user the option of updating the existing registration with the new data. Alternatively, when process 200 (see FIG. 6) was performed for the update of an existing registration, the registration server 144 looks up the registration in database 142 in order to associate the new data to the existing registration.

[0074] In step 228, the registration server 144 saves the data received in step 224 to database 142 (shown in FIG. 2).

[0075] Referring now to FIG. 8, a preferred embodiment of a verification process performed by a POS terminal 136 (shown in FIG. 5) is illustrated and generally designated 240. Process 240 occurs when a purchaser attempts to purchase goods or services. Process 240 is illustrated in the context of purchasing products, but it will be apparent to one of ordinary skill in the art that the same process can also be used with the purchase of services or both goods and services.

[0076] In step 242 the purchaser is identified. In a preferred embodiment, this step is performed by scanning a magnetic strip identification card and sending the scanned data to a verification server 146 (shown in FIG. 2).

[0077] In step 244, a product to be purchased is identified. In preferred embodiments, the product identification is performed by the ordinary product identification mechanism of a point-of-sale terminal, e.g., by scanning a barcode, entering a product code, or selecting a product from a user interface.

[0078] In step 246, the product information is sent to verification server 146 in order to determine whether the purchaser is restricted from purchasing the product.

[0079] In step 248, POS terminal 136 receives a response from verification server 146 indicating whether the purchaser is permitted to purchase the product. If so, POS terminal 136 also receives information about whether an additional charge is to be applied to the purchase, and, if so, how much, illustrated as step 250.

[0080] If there is an additional charge, it is applied in step 252. The product is added to the purchaser's purchase in step 254. If, however, the verification server 146 indicated that the purchase is not authorized, POS terminal 136 performs step 256 of notifying the operator of terminal 136 and the verification server 146 that an unauthorized purchase is being attempted, and the product is not added to the purchaser's purchase.

[0081] In step 258, if more products are being purchased, the prior steps from step 244 are repeated; otherwise, the sale is completed in step 260, and the POS terminal 136 notifies the verification server 146 of the purchased products in step 262.

[0082] Referring now to FIG. 9, a preferred embodiment of a process performed by a verification server 146 (shown in FIG. 2) is illustrated and generally designated 270. Process 270 is performed cooperatively with process 240 in order to track and control transactions.

[0083] After a secure connection is made and a POS terminal 136 (shown in FIG. 2) is authenticated, verification server 146 receives identification data, such as magnetic stripe data or other identifying data, for a purchaser in step 272.

[0084] In step 274, verification server 146 looks up the purchaser's record in the database. If a registered participant matching the purchaser's identification is not found, the POS terminal 136 is notified, allowing the merchant to request alternate identification or to determine that the purchaser is not a registered participant and allow the sale to go forward without verification.

[0085] In step 276, verification server 146 receives information identifying a product that the purchaser seeks to purchase. In step 278, verification server 146 determines whether purchase limits are in place, including a complete restriction on purchases of the product or service, and whether they would be exceeded by the attempted sale. If the sale would violate a restriction or limit, the verification server 146 notifies the POS terminal 136 in step 280 that the sale of the product or service should be refused. Otherwise, in step 282, verification server 146 determines whether a surcharge or other additional charge should be applied. If so, step 284 is performed, in which the amount is determined and the POS terminal 136 is notified to add the extra fee.

[0086] In step 286, if all products and services have now been reviewed, verification server 146 receives confirmation of the sale and the products or services and quantities sold, and process 270 ends. Otherwise, steps 276 onward are repeated until all products and services that the purchaser is attempting to purchase have been reviewed by verification server 146.

[0087] Referring now to FIG. 10, a system for selecting a designated driver in connection with system 100 for verifying and controlling transactions is illustrated and generally designated 300. System 300 includes one or more computing devices through which registered participants select a designated driver, thus enabling each of the involved registered participants, except for the designated driver, to purchase alcohol when such purchases are otherwise restricted by system 100.

[0088] In a preferred embodiment, the computing devices are mobile devices 302 running software that communicates with central registry 110 over the Internet. In another embodiment, the computing devices are simply registration terminals 134 or POS terminals 136. In some preferred embodiments, both mobile devices 302 and terminals 134, 136, or both, are operable to select a designated driver.

[0089] Participants interact with the prospective designated driver by logging in together to the same terminal 134 or 136, through the software on mobile devices 302 operating to broadcast the presence of registered users looking for other nearby registered users through the communications hardware of mobile devices 302, e.g., Bluetooth, through predetermined “friends” lists, through sharing a code such as an alphanumeric code, QR code, or other form of identifying code, or through some other mechanism for identifying registered users.

[0090] Registered participants who seek to purchase alcoholic beverages engage user interfaces 304 to select a designated driver. The registered participant who will act as designated driver is than presented with a user interface 306 which enables the participant to accept the designation as designated driver. If the participant accepts the role of designated driver, the participant's mobile device 302 sends the acceptance and list of participants to central registry 110, e.g. to a registration server 144, verification server 146, or another server connected to database 142 and having the structure illustrated in FIG. 3.

[0091] The system functions similarly when a terminal 134 or 136 is used, with users logging in and selecting a designated driver, who accepts the role. The terminal then sends the acceptance and list of participants to central registry 110.

[0092] Once the designated driver is accepted and the central registry 110 receives the designation and list of participants, system 100 permits participants except for the designated driver to purchase alcoholic drinks for a predetermined amount of time. If the designated driver was otherwise unrestricted from alcohol purchases, system 100 imposes a temporary restriction on alcoholic purchases during the aforementioned time period.

[0093] Referring now to FIG. 11, an exemplary preferred embodiment of a system for controlling and verifying transactions is 100 illustrated, showing capabilities and features present in some embodiments of system 100. System 100 is illustrated with multiple networks 120 and multiple central registries 110. These features are independent, such that some embodiments have multiple central registries 110 operating on a single network 120, and some other embodiments have a single central registry 110 operating on multiple networks 120, while yet other embodiments have multiple central registries 110 operating on multiple networks 120, as illustrated. In some embodiments, one of the networks 120 is the internet.

[0094] The use of multiple central registries 110 offers backup and load balancing capabilities. The central registries 110 are in communication with each other in order to keep data synchronized and otherwise perform their operations. As illustrated, central registries 110 can communicate directly with each other, e.g. through a private network such as a LAN or private mesh network, or communicate with each other via a network 120. The illustrated embodiment has both types of communication connections.

[0095] As illustrated, some embodiments have one or more networks 120 exclusive to registration terminal 134 communication with central registries 110, one or more networks 120 exclusive to POS terminal 136 communication with central registries 110, or both. Such networks 120 exclusive to a particular type of terminal 134 or 136 allow for greater security and are particularly useful where protection of private data is a concern. Moreover, where security is a significant concern, a network 120 can be private between a single terminal 134 or 136 and a central registry 110 (or multiple central registries 110). Where a network 120 is exclusive to a registration terminal 134, a central registry 110 connected to it may lack a verification server 146. Likewise, where a network 120 is exclusive to a POS terminal 136, corresponding central registries 110 may lack registration servers 144.

[0096] In embodiments in which one of the networks 120 is the internet, the cost of operating system 100 is reduced where there is an existing internet connection, since terminals 134 and 136 can be joined to the system through the already-existent internet connection. The additional networks 120 are capable of allowing terminals 134 and 136 to join the system where an internet connection is unavailable, or where it would be undesirable to connect a terminal 134 or 136 to the internet.

[0097] While there have been shown what are presently considered to be preferred embodiments of the present invention, it will be apparent to those skilled in the art that various changes and modifications can be made herein without departing from the scope and spirit of the invention. Moreover, embodiments containing the various possible combinations of the features disclosed in the above-described embodiments are fully contemplated.