Contactless payment system for hospitality services

Abstract

System and methods for contactless payment for hospitality services are described. User and/or remote service provider computing systems in point-of-sale, electronic reservation book, payment gateway computer(s) action/events related to the hospitality service are handled in accordance with the user's physical location within a geofence-defined area and/or within proximity of an RF module. Request one or more biometric authentication methods based on received location data of the user's physical location in proximity to the geofenced area and/or RF module. After successful authentication, a user and/or remote service provider computing systems in point-of-sale, electronic reservation book, payment gateway computer(s) within a hospitality venue performs actions/events handled by operational states of the systems/methods, which provide venue specific contactless hospitality ordering and payment.

What is claimed is: 
     
         1 . A contactless payment system comprising:
 a computing system comprising one or more processors for executing computer-readable instructions;   one or more databases and/or digital ledgers for storing the computer-readable instructions,   a plurality of computing devices, the plurality comprising one or more point-of-sale (POS) computer(s), one or more electronic reservation book (ERB) computer(s), and one or more payment gateway computer(s);   one or more networks interconnecting the computing system and the plurality of computing devices by one or more internet and/or local connections;   a user computing device in data communication with the computing system, the user computing device comprising an application (including internet browser interface) configured to:
 receive, from a user, user login credentials for the contactless payment system; 
 select a venue providing the services; 
 provide location data to the computing system; and 
 perform one or more biometric authentication method(s); 
   a geofence located at the [hospitality venue] for defining a geofenced area for the service and/or an RF module located at the venue for defining a proximity to the service,   wherein the computing system determines whether a user computing device is within the geofenced area and/or in proximity to an RF module.   
     
     
         2 . The contactless payment system according to  claim 1 , wherein the system is for hospitality services for a hospitality venue, comprising:
 a computing system comprising one or more processors for executing computer-readable instructions;   one or more databases and/or digital ledgers for storing the computer-readable instructions,   a plurality of hospitality computing devices, the plurality comprising one or more point-of-sale (POS) computer(s), one or more electronic reservation book (ERB) computer(s), and one or more payment gateway computer(s);   one or more networks interconnecting the computing system and the plurality of hospitality computing devices by one or more internet and/or local connections;   a user computing device in data communication with the computing system, the user computing device comprising an application (including internet browser interface) configured to:
 receive, from a user, user login credentials for the contactless payment system; 
 select a hospitality venue providing the hospitality services; 
 provide location data to the computing system; and 
 perform one or more biometric authentication method(s); 
   a geofence located at the hospitality venue for defining a geofenced area for the hospitality service and/or an RF module located at the hospitality venue for defining a proximity to the hospitality service,   wherein the computing system determines whether a user computing device is within the geofenced area and/or in proximity to an RF module.   
     
     
         3 . The system of  claim 2 , wherein the data is stored in a database and/or digital ledger, (e.g., a blockchain database) and/or a plurality of guidelines for the computer system and/or plurality of hospitality computing devices. 
     
     
         4 . The system of  claim 3 , wherein the computer system and/or plurality of hospitality computing devices are set to a first, default guideline when the user computer device is not within the geofenced area and/or is not in proximity to an RF module, and wherein the computer system and/or plurality of hospitality computing devices are set to a second, alternate guideline when the user computer device is within the geofenced area and/or is in proximity to an RF module. 
     
     
         5 . The system of  claim 2 , wherein the data is stored in a database and/or digital ledger, (e.g., blockchain database) and/or a plurality of user states for the computer system and/or plurality of hospitality computing devices. 
     
     
         6 . The system of  claim 5 , wherein the computing system and/or plurality of hospitality computing devices are set to a first user state when the user has selected a venue providing the hospitality services and has performed one or more biometric authentication method(s), and wherein the user computing device and/or computing system are set to a second user state when the user has not performed one or more biometric authentication method(s). 
     
     
         7 . The system of  claim 6 , wherein the computer system does not allow for the hospitality service to be rendered to the user in the second user state (where the user has not performed the required biometric authentication). 
     
     
         8 . The system of  claim 2 , wherein the computer system and/or plurality of hospitality computing devices are set to one or more of a plurality of operational states, and wherein the operational states are selected or changed in accordance with events associated with the user computing device and/or plurality of hospitality computing devices. 
     
     
         9 . The system of  claim 8 , wherein the operational states are selected from
 (i) an entry state, where the user computing device has entered the geofence or is in proximity with an RF module;   (ii) an order request state, where the user utilizes the user computing device to begin an order (optionally, by communication with the POS computer);   (iii) a pending item state, where the user has selected particular hospitality services to be rendered but has not yet placed an order;   (iv) an identified seating state, where the system and/or plurality of hospitality computing devices are updated with the seating location for the user;   (v) a payment authorization state, where the user has pre-authorized payment for the hospitality services to be rendered, but the transaction has not yet occurred (the payment authorization is optionally required before the hospitality services may be rendered);   (vi) a check request state, where the user is presented with the option to complete the transaction for the hospitality services rendered;   (vii) a payment capture state, where the user may initiate the transaction for any pre-authorized or non-previously authorized balances;   (viii) an unsuccessful payment capture state, where the initiated transaction failed;   (ix) a successful payment capture state, where the initiated transaction succeeded; and   (x) an exit state, e.g., where the user computing device has exited the geofence or is no longer in proximity with an RF module, wherein the exit state may initiate a payment capture state if the user did not pay for the rendered hospitality services prior to the exit state being set (if user leaves the venue without paying).   
     
     
         10 . A method for contactless payment of hospitality services, comprising the steps of:
 communicating, over one or more networks, with a
 plurality of computing devices of a plurality of 
 point-of-sale (POS) computer(s), electronic reservation book (ERB) computer(s), and payment gateway computer(s) providing the hospitality service; 
   monitoring, in real-time, a location of each respective
 computing device of the plurality of computing 
 devices based on location data received from a 
 location monitor of the respective computing device; 
   determining whether to subject a respective point-of-sale (POS) computer,
 electronic reservation book (ERB) computer, and 
 payment gateway computer to either (i) a default 
 set of guidelines, or (ii) an alternative set of guidelines associated 
 with a geofenced area and/or RF module, based on the location of 
 the respective computing device relative to the 
 geofenced area and/or RF module; 
   for each subjected point-of-sale (POS) computer,
 electronic reservation book (ERB) computer, and 
 payment gateway computer of the plurality of 
 point-of-sale (POS) computer(s), electronic reservation book (ERB) 
 computer(s), and payment gateway computer(s) that is subject to 
 the alternative set of guidelines, input an 
 identifier of the subjected point-of-sale (POS) computer, 
 electronic reservation book (ERB) computer, and 
 payment gateway computer into a state, the identifier indicating 
 an operational state to subject the point-of-sale (POS) computer, 
 electronic reservation book (ERB) computer, and 
 payment gateway from a plurality of states for the geofenced area/or RF module, 
   receiving, over the one or more networks, indication of a location-based event
 from a computing device of a first user(s), the location-based event 
 indicating a user device has entered, exited, or performed some action 
 within the geofenced and/or RF module area; 
   arranging the hospitality service for the first user(s)
 by (i) selecting the point-of-sale (POS) computer, 
 electronic reservation book (ERB) computer, and 
 payment gateway computer from one of the plurality of states 
 and (ii) communicating, over the one or more networks, the set of instructions associated with the state to the selected point-of-sale (POS) computer, 
 electronic reservation book (ERB) computer, and payment gateway computer; 
   receiving, over the one or more networks, a second
 hospitality request from a computing device of a 
 second requesting user(s), the second hospitality request 
 indicating a request external to the 
 geofenced area and/or RF module; and 
   arranging the hospitality service for the second requesting
 user(s) by (i) selecting the point-of-sale (POS) computer(s), 
 electronic reservation book (ERB) computer(s), and payment gateway computer(s) based at least in part on a proximity of the service provider geolocation of the second hospitality request, and (ii) communicating, over the one or more networks, the set of instructions associated with the state to the selected point-of-sale (POS) computer, electronic reservation book (ERB) computer, and payment gateway computer 
   
     
     
         11 . The method of  claim 10 , wherein the executed set of instructions
 further cause the computing system to:   for each respective user, generate a record indicating a number of instances in which the respective user(s) enter and/or exit the service provider geolocation to receive the hospitality service.   
     
     
         12 . The method of  claim 10 , wherein the executed set of instructions further cause the computing system to:
 for each respective user, generate a record indicating a duration of time a user(s) has remained at a seating location within the service provider geolocation.   
     
     
         13 . The method of  claim 10 , wherein the executed set of instructions further cause the computing
 system to:   determine the alternative set of guidelines by accessing a database and/or digital ledger (e.g., blockchain database) that stores information   corresponding to the geofenced area and/or RF module, the information including an identifier of a point-of-sale (POS) computer(s), electronic reservation book (ERB) computer(s), and payment gateway computer(s) associated with the geofenced area and/or RF module.   
     
     
         14 . The method of  claim 10 , wherein the executed set of instructions further cause the computing system to:
 monitor, in real time, an operational state of a user application executing on each of the plurality of computing devices of each respective user, the operational state indicating at least one of (i) whether the respective user has selected a service provider and performed one or more biometric authentication method(s) to receive the hospitality service, or (ii) whether the respective user has failed to perform a successful biometric authentication method(s) to receive the hospitality service.   
     
     
         15 . The method of  claim 10 , wherein the executed set of instructions (in the alternative set of guidelines) further cause the computing system to:
 monitor, in real time, an operational state of a point-of-sale (POS) computer(s), electronic reservation book (ERB) computer(s), and payment gateway computer(s), the operational state indicating at least one of (i) an entry state, e.g., after the respective user has entered a service provider geolocation associated with the geofence and/or RF module, based on the location data provided by the user device, request the point-of-sale (POS) computer to generate and/or display a touch-sensitive moveable (e.g., drag and drop) open check in a region on the GUI screen display associated with corresponding user information (e.g., a user identifier (ID) associated with the user, a digital ledger identifier (ID) associated with the user, a name, a photograph, a phone number, e-mail address, a device (ID) associated with user device, an application (ID) associated with the user application), request the point-of-sale (POS) computer to generate and display an illuminable touch-sensitive transfer check button configured as a selectable GUI widget in a region on the GUI screen display, request the electronic reservation book (ERB) computer to generate and/or display a moveable (e.g., drag and drop) reservation in a region on the GUI screen display associated with corresponding user information, request the electronic reservation book (ERB) computer to generate and/or display a moveable (e.g., drag and drop) wait list entry in a region on the GUI screen display associated with corresponding user information, (ii) an order request state, e.g., after the respective user has indicated via user input on the user application a request to start an order, request the point-of-sale (POS) computer to generate and display an identifier corresponding to an identifier associated with the moveable open check corresponding to the user in a region on the GUI screen display with a distinctive illumination treatment (e.g., highlight, flash, colored, etc.), (iii) a pending item state, e.g., after the respective user has indicated via user input on the user application one or more menu line item(s) (e.g., food, beverage, or other products or services) and/or after the respective administrative user has indicated via admin user input in the point-of-sale (POS) computer one or more menu line item(s) (e.g., food, beverage, or other products or services), request the point-of-sale (POS) computer to generate and display one or more menu line item(s) (e.g., food and beverage or other products or services) as moveable widgets (e.g., drag and drop) in a region on the moveable open check corresponding to the respective user that when selected activate one or more modifiers, (iv) an identified seating state, e.g., after the respective administrative user has moved a moveable reservation and/or wait list entry in the electronic reservation book (ERB) computer to a seating location on the GUI screen display and/or entered a location identifier (e.g., seat, table number) in the point-of-sale (POS) computer, request the point-of-sale (POS) computer to generate and display the corresponding location identifier (e.g., seat, table number) in a region on the moveable open check and/or automatically transfer the moveable open check to the seating location associated with the corresponding location identifier, (v) a payment authorization state, e.g., after the respective user has indicated via user input on the user application one or more menu line item(s) (e.g., food, beverage, or other products or services) and/or after the respective administrative user has indicated via admin user input in the point-of-sale (POS) computer one or more menu line item(s) (e.g., food, beverage, or other products or services) totaling a pre-determined authorization limit, request the payment gateway computer to authorize but not yet capture a payment amount, (vi) a check request state, e.g., after the respective user has indicated via user input on the user application a request for a check, request the point-of-sale (POS) computer to generate and display a notification and/or alert indicating a request to pay a check in a region on the moveable open check and/or request the point-of-sale (POS) computer to generate and display a touch-sensitive send payment button in a region on the moveable open check, (vii) a payment capture state, e.g., after the respective user has selected a pay button via user input on the user application request the payment gateway computer to capture the previously authorized amount and request to authorize and capture the difference between the final total ticket amount (e.g., tax, gratuity, and any other current charges) and previously authorized amount and/or request to authorize and capture the final total ticket amount (e.g., tax, gratuity, and any other current charges) upon detecting no prior authorization, (viii) an unsuccessful payment capture state, e.g., in response to an unsuccessful final total ticket amount payment capture in the payment gateway computer, request the point-of-sale (POS) computer to generate and display a notification and/or alert in a region on the moveable open check indicating an unsuccessful payment capture and/or request for an alternate or backup payment source (e.g., another credit card on file), (ix) a successful payment capture state, e.g., in response to a successful final total ticket amount payment capture in the payment gateway computer, request the point-of-sale (POS) computer to generate and display a notification and/or alert in a region on the moveable open check indicating a provisional electronic receipt, request the electronic reservation book (ERB) computer to generate and display a confirmed payment message for the seating location corresponding to the provisional electronic receipt in a region on the GUI screen display, (x) an exit state, e.g., after the respective user has traveled a fixed distance and/or exceeded a given time duration outside the virtual perimeter of the service provider geolocation and/or RF module with a remaining balance on a moveable open check, request the payment gateway computer to capture the previously authorized amount and request to authorize and capture the difference between the final total ticket amount (e.g., tax, gratuity, and any other current charges) and previously authorized amount and/or request to authorize and capture the final total ticket amount (e.g., tax, gratuity, and any other current charges) upon detecting no prior authorization, request the point-of-sale (POS) computer to generate and display a notification and/or alert in a region on the moveable open check indicating a balance due message, request the point-of-sale (POS) computer to generate and display a capture payment button in a region on the moveable open check, request the point-of-sale (POS) computer to generate and display a notification and/or alert in a region on the moveable open check indicating an unsuccessful payment capture and/or request for an alternate or backup payment source (e.g., another credit card on file) in response to an unsuccessful payment capture in the payment network gateway computer, request the point-of-sale (POS) computer to generate and display a notification and/or alert in a region on the moveable open check indicating a provisional electronic receipt in response to a successful payment capture, request the point-of-sale (POS) computer to automatically close a moveable open check associated with a provisional electronic receipt, request the electronic reservation book (ERB) computer to generate and display a confirmed payment message for the seating location corresponding to the provisional electronic receipt in a region on the GUI screen display in response to a successful payment capture, request the electronic reservation book (ERB) computer to automatically remove a reservation and/or waitlist entry associated with user information.   
     
     
         16 . The method of  claim 2 , wherein the geofenced area and/or
 RF module corresponds to hospitality services, which can be selected from a restaurant, hotel, shopping mall, cruise ship, airline, theatre, gaming venue, stadiums, resort, theme park, and concert venue.   
     
     
         17 . The method of  claim 2 , wherein the geofenced area and/or
 RF module corresponds to a point-of-sale (POS) computer,   electronic reservation book (ERB) computer, and   payment gateway computer.   
     
     
         18 . A contactless payment system for hospitality services for a hospitality venue, comprising:
 a computing system comprising one or more processors for executing computer-readable instructions;   one or more databases and/or digital ledgers (e.g., blockchain database) for storing the computer-readable instructions,   a plurality of hospitality computing devices;   one or more networks interconnecting the computing system and the plurality of hospitality computing devices by one or more internet and/or local connections;   a user computing device in data communication with the computing system:   a geofence for defining a geofenced area and/or an RF module located for defining a proximity,   wherein the computing system determines whether a user computing device is within the geofenced area and/or in proximity to an RF module.   
     
     
         19 . A method for contactless payment utilizing the system of  claim 18 .