Remote order authentication on a kiosk
A kiosk maintains a list of pre-paid orders. A first authentication process enables a consumer to select their order on the kiosk so as to receive the product or service that was remotely paid for via a mobile application. Authentication of the consumer selecting the order is performed based upon sending an order authentication notification to the mobile application that completed the order. If the user of the mobile application provides a positive authentication reply, the kiosk is unlocked to fulfill the order. The consumer may alternatively be authenticated by providing a personal identification number (PIN) that is associated with the order or associated with a user of the mobile application. Authentication using the PIN enables a consumer to interact with the kiosk to receive the previously ordered product or service without having to access their mobile phone or mobile application that was used to place the order.
1. A beverage vendor, comprising:
a nozzle configured to dispense one or more beverage ingredients of a beverage associated with an order;
a user interface configured to display a list of pending orders;
a plurality of pumping or metering devices, each configured to supply a beverage ingredient from an ingredient source to the nozzle; and
a controller configured to receive a selection of an order from the list of pending orders and authenticate the order for being dispensed from the nozzle, wherein upon authenticating the order, the controller is configured to initiate a pour operation of the order from the nozzle, wherein the controller is configured to update the list of pending orders to remove an order that is associated with a mobile device that is determined to not be proximate to the beverage vendor.
2. The beverage vendor of claim 1 , wherein authenticating the order comprises receiving a personal identification number (PIN) code on the user interface.
3. The beverage vendor of claim 2 , wherein the controller is further configured to authenticate the PIN code based on comparison with an authentic PIN code maintained with the order in the list of pending orders.
4. The beverage vendor of claim 2 , wherein the controller is further configured to request authentication of the PIN code from a server in communication with the beverage vendor and receive an authentication reply from the server.
5. The beverage vendor of claim 1 , wherein the controller is further configured to send an order notification of the selected order to a server in communication with the beverage vendor.
6. The beverage vendor of claim 5 , wherein the controller is further configured to receive an authentication reply from the server in response to the server receiving an authentication reply from a mobile device that placed the order.
7. The beverage vendor of claim 1 , wherein the list of pending orders include orders that have been purchased, but not fulfilled.
8. The beverage vendor of claim 7 , wherein the controller is configured to update the list of pending orders to add an order associated with a mobile device that is proximate to the beverage vendor.
9. The beverage vendor of claim 8 , further comprising:
a beacon configured to broadcast a beacon message with a unique identifier of the beverage vendor.
10. The beverage vendor of claim 9 , wherein the mobile device is determined to be proximate to the beverage vendor upon receiving the beacon message.
11. The beverage vendor of claim 7 , wherein the controller is configured to update the list of pending orders to remove an order that has been fulfilled at the beverage vendor.
12. The beverage vendor of claim 7 , wherein the controller is configured to update the list of pending orders to add an order that designates the beverage vendor for fulfillment of the order.