WO2015023713A9

WO2015023713A9 - Mobile application check-in and payment systems and methods of their operation

Info

Publication number: WO2015023713A9
Application number: PCT/US2014/050799
Authority: WO
Inventors: Jeffrey Mcgregor; Gennady Spirin
Original assignee: Dash Software, LLC
Priority date: 2013-08-13
Filing date: 2014-08-13
Publication date: 2015-05-28
Also published as: WO2015023713A2; WO2015023713A3

Abstract

A method and system for allowing a customer and/or user to link a ticket to a table in a bar, restaurant and/or any other business establishment. The user may make a reservation at a venue through any reservation system, which may be built into the mobile application, a third party reservation system, or via any other computing system. The user may check-in as present at the venue on the mobile application. The server may query the reservation system for table number and table ID associated with the users reservation. The check-in data and payment account data associated with the user may be transmitted to the system.

Description

MOBILE APPLICATION CHECK-IN AND PAYMENT SYSTEMS

AND METHODS OF THEIR OPERATION

TECHNICAL FIELD

[0001] Generally, the present disclosure relates to mobile application check-in and payment system. More particularly, the present disclosure relates to a technology for checking into a reservation system and making a payment using a mobile computing device.

BACKGROUND

[0002] Many business establishments, such as bars or restaurants, serve food and drinks to customers for consumption on the premises in exchange for money. When a customer visits one of these establishments, the customer generally sits down at an empty table, while waiting for a waiter to arrive and take the customer's order. Typically, after the waiter arrives and takes the customer's order, the waiter enters the order into a point-of-sale (POS) system so that the order can be timely prepared and tracked for payment. When the order is ready, the waiter brings the order to the customer. At some point, the waiter, either upon the customer's request or through the establishment's serving procedure, brings a bill for the order to the customer. If the bill is correct, then the customer pays by handing cash, a check, a prepaid card or a credit card to the waiter. Subsequently, the waiter takes the proffered form of payment and manually pays the bill via the POS system. If the bill is incorrect, then the waiter uses the POS to correct the bill and provide the bill, as corrected, to the customer for payment.

[0003] One drawback of the above is that prior to the bringing of the order, unless the customer asks the waiter or views the order in the POS system, the customer is unable to verify that the order, as placed by the customer, was correctly entered into the POS system. Because the waiter is serving many patrons or tables simultaneously, this situation can be particularly frustrating to the customer. Incorrect orders, especially if reoccurring, are inefficient for the establishment's operation, reduce the establishment's profitability if detected after the order has been prepared, harm the establishment's reputation, and can be grounds for the waiter's termination.

[0004] Another drawback of the above is that the manual payment of the bill is relatively slow and prone to errors, fraud and/or chargeback. If the waiter is serving many patrons or tables simultaneously, then this can be particularly frustrating to the customer. Quick bill payment improves the establishment's operation as more customers can be served, while increasing time for attending to new customers, who often wait for service or open tables. Similarly, billing errors and fraud are inefficient for the establishment's operation, harm the establishment's reputation, reduce the establishment's profitability and can expose the establishment to lawsuits.

[0005] Yet another drawback of the above is that the customer is unable to easily pay a portion of the bill in sequential portions. Since some establishments, like bars, have running tabs, especially for groups of customers, when the customer periodically pays the bills in sequential portions, these establishments reduce the occurrence of unpaid large bills, while increasing their profitability. Similarly, the customer's ability to pay in sequential portions allows the customer to budget accordingly and prevent many payment-related mishaps.

[0006] Still another drawback of the above is that the customer is unable to accurately determine, in real-time, the total amount of charges incurred by the customer at any given moment. Knowledge of one's bill, in real-time, enables the customer to budget accordingly, prevent many payment-related mishaps and perceive the establishment in better light. Likewise, the establishment's reputation is enhanced and business operation improved when its employees are able to accurately determine, in real-time, the total amount of charges incurred by any of its customers at any given moment. [0007] Yet still another drawback of the above is that during the manual payment of the bill, the waiter is often unable to perform other tasks, such as taking a new order from a new customer or bringing the order to another customer. Efficiency of waiter operations is important to the operation of the establishment as the establishment's profitability and reputation are improved when the waiters are constantly serving the customers and the customers feel cared for.

[0008] Any of the above or permutations thereof are made more complex if the bill is long or complicated or when a group of customers dine together and each member of the group desires to pays separately. As a result, there is room for error. Cumulatively, such occurrences can ruin the establishment's reputation and reduce visits from other customers. This is becoming especially common when the customers post comments on their experience in the establishment on popular social networking sites or review sites.

[0009] Accordingly, there is a need to address at least one of the above. While certain aspects of conventional technologies have been discussed to facilitate the present disclosure, no technical aspects are disclaimed and it is contemplated that the claims may encompass one or more of the conventional technical aspects discussed herein.

BRIEF SUMMARY

[0010] An aspect of an example embodiment of the present disclosure is to provide a technology for checking into a reservation system and making a payment using a mobile computing device.

[0011] An example embodiment of the present disclosure is a method and system for allowing a customer and/or user to link a ticket to a table in a bar, restaurant and/or any other business establishment. A host server may receive check-in data regarding the presence of a mobile computing device of a first user in the business establishment. The host server may query the client server for a reservation associated with the first user. The host server may receive transmittal of a reservation for the first user in a business establishment from a client server of the business establishment, the reservation comprising a table selection indicating a table identification and a time and date of dining. Upon receiving the transmittal of the reservation, the host server may associate the mobile computing device of the first user with the reservation. The host server may transmit to the mobile computing device of the first user, the table identification based on the reservation associated with the first user. The host server may transmit to the point of sale (POS) system, the check-in data and payment account data associated with the first user. The host server may request generation of a ticket on the POS system based on the reservation associated with the first user. The host server may associate in a database the ticket corresponding to the reservation, the payment account data, and an order placed by the first user.

[0012] Another example embodiment of the present disclosure is a method and system for linking an existing ticket to a mobile application ticket in a bar, restaurant and/or any other business establishment. A host server may check-in data regarding the presence of a mobile computing device of a first user in a business establishment. The host server may transmit to a POS system the check-in data and payment account data associated with the first user. The host server may receive from the POS system, a record of a first order placed by the first user prior to receiving the check-in data regarding the presence of the mobile computing device of the first user in the business establishment. The host server may request generation of a ticket corresponding to the payment account data and the record of the first order placed by the first user prior to receiving the check-in data of the first user. The host server may receive from a POS system, a record of a second order placed by the first user. The host server may link the record of the second order placed by the first user to the ticket corresponding to the payment account data and the record of the first order placed by the first user. The host server may transmit a bill including the first and second order of the first user. The host server may receive from the POS system, at least partial payment of the bill using the payment account data.

[0013] An additional exemplary embodiment of the present disclosure is a method and system for a user splitting a bill with another user in a bar, restaurant and/or any other business establishment. The system allows for splitting the bill amongst two or more patrons directly through the mobile application. The host server may receive check-in data regarding the presence of a mobile computing device of a first user in the business establishment. The host server may query user profile information associated with the first user, the user profile information containing payment information related to the first user. The host server may receive an identification, from the mobile computing device of the first user, of a presence of a second user in the business establishment. The host server may open on the POS system a ticket based on an order placed by the first user and the second user. The host server may transmit to the POS system a bill for display on the mobile computing device of the first user and a mobile computing device of the second user. The host server may allocate the bill among the first user and the second user based on input from the first user. The host server may receive, at least partial payment for the bill according to the validated payment information in response to the host server authorizing the at least partial payment from the mobile computing device of first user and the mobile computing device of the second user.

[0014] As described herein, an application (or "app") may be installed on a mobile device of a patron, customer, or user. The application may communicate with a server through a communication network such as a local area network, Wi-Fi, cellular network, or any other communication network. The server may be hosted by a business establishment (e.g., a restaurant, bar, hotel, salon, airline, gas station) and/or a third party that can communicate with the business establishment and/or patron, customer, or user. The server may also communicate with payment systems, such as credit card processing systems or other banking systems to process payments. The "host server", "client server", and "POS system" may be implemented interchangeably.

[0015] The business establishment may have a POS system, which is a venue point of sale system that may communicate with a server of the business establishment or may directly communicate with a third party, patron, customer, or user. The POS system may be configured to open a tab or a ticket for each table, party, customer, patron, user, or other entity submitting a request for a product or service. The mobile device, one or more server, and the POS system may be referred to herein as a system, which may also include other servers and databases to provide the described functionality.

[0016] The patron, customer, or user may use a mobile device, such as a mobile phone, cellular phone, smartphone, personal data assistant, tablet computer, laptop computer, or other computing device that can connect to a communication network. For the purposes of this description, these terms may be used interchangeably.

[0017] The present disclosure may be embodied in the form illustrated in the accompanying drawings. Attention is called to the fact, however, that the drawings are illustrative. Variations are contemplated as being part of the disclosure, limited only by the scope of the claims. The above and other features, aspects and advantages of the present disclosure will become better understood to one skilled in the art with reference to the following drawings, detailed description and appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated into and form a part of the specification, illustrate example embodiments of the present disclosure. Together with the detailed description, the drawings serve to explain the principles of the present disclosure. The drawings are only for the purpose of illustrating example embodiments of the present disclosure and are not to be construed as necessarily limiting the disclosure. Like numbers can refer to like elements throughout. The above and other aspects, advantages and features of the present disclosure will become better understood to one skilled in the art with regard to the following description, appended claims and accompanying drawings where:

[0019] FIG. 1 is a diagram of an example embodiment of a network environment for checking into a reservation system and making a payment using a mobile computing device according to the present disclosure.

[0020] FIG. 2 illustrates method of allowing the system to link the ticket to a table from the reservation system according to the present disclosure.

[0021] FIG. 3 illustrates method of allowing the system to link an existing ticket to a mobile application ticket according to the present disclosure.

[0022] FIG. 4 illustrates method of allowing the system to split the bill among multiple users according to the present disclosure.

[0023] FIG. 5A is a flowchart of an example embodiment of a process for table selection according to the present disclosure.

[0024] FIG. 5B is a user interface of an example embodiment of displaying a list of nearby venues according to the present disclosure.

[0025] FIG. 5C is a user interface of an example embodiment of displaying a single venue with general information and allowing a user to open a tab according to the present disclosure.

[0026] FIG. 5D is a user interface of an example embodiment of determining where the user is looking to open a tab inside of the venue according to the present disclosure.

[0027] FIG. 5E is a flowchart of an example embodiment of a process for ticket/employee assignment according to the present disclosure. [0028] FIG. 5F is a flowchart of an example embodiment of a process for linking the application to a ticket by an ID according to the present disclosure.

[0029] FIG. 5G is a flowchart of an example embodiment of a process for linking a ticket to a table from the reservation system according to the present disclosure.

[0030] FIG. 5H is a user interface of an example embodiment of displaying a list of tables, as queried from the system for the user to select where they are seated according to the present disclosure.

[0031] FIG. 51 is a user interface of an example embodiment of showing a real time list of items that have been placed on the ticket according to the present disclosure.

[0032] FIG. 5J is a user interface of an example embodiment of allowing the user to set a tip by sliding an indicator across a bar and setting the percentage and tip amount according to the present disclosure.

[0033] FIG. 5K is a user interface of an example embodiment of displaying a confirmation of charges before the payment is processed and allowing social sharing of interactions occurring within the mobile application according to the present disclosure.

[0034] FIG. 5L is a user interface of an example embodiment of displaying a confirmation that the payment has processed, allowing a rating of the venue by the user, showing rewards earned by the user, and emailing a receipt confirmation of the charge according to the present disclosure.

[0035] FIG. 5M is a flowchart of an example embodiment of a process for linking an existing ticket to a mobile application ticket according to the present disclosure.

[0036] FIG. 6A is a flowchart of an example embodiment of a process for identification verification according to the present disclosure. [0037] FIG. 6B is a user interface of an example embodiment of allowing a user to snap a picture of the user's photo identification through a mobile application according to the present disclosure.

[0038] FIG. 6C is a user interface of an example embodiment of allowing a user to implement a built in camera to photograph the user's photo identification according to the present disclosure.

[0039] FIG. 6D is a user interface of an example embodiment of showing age verification in the account information screen according to the present disclosure.

[0040] FIG. 6E is a user interface of an example embodiment of displaying age verification in the system according to the present disclosure.

[0041] FIG. 7A is a flowchart of an example embodiment of a process for checking in to a hotel system according to the present disclosure.

[0042] FIG. 7B is a flowchart of an example embodiment of a process for checking in to a gas system according to the present disclosure.

[0043] FIG. 7C is a flowchart of an example embodiment of a process for checking in to a retail system according to the present disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0044] The present disclosure will now be described more fully with reference to the accompanying drawings, in which example embodiments of the disclosure are shown. The disclosure may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the disclosure to those skilled in the art. [0045] Any verbs as disclosed herein can imply direct or indirect action or inaction. For example, when an element is referred to as being "on," "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements present.

[0046] It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms are only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the present disclosure.

[0047] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be necessarily limiting of the disclosure. As used herein, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "includes" and/or "comprising," "including" when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0048] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0049] If any disclosures are incorporated herein by reference and such incorporated disclosures conflict in part or whole with the present disclosure, then to the extent of conflict, and/or broader disclosure, and/or broader definition of terms, the present disclosure controls. If such incorporated disclosures conflict in part or whole with one another, then to the extent of conflict, the later-dated disclosure controls. Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings.

[0050] FIG. 1 illustrates a system 100 configured for allowing a user to check into a reservation system and make a payment using a mobile computing device. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, system 100 may include one or more server(s) 102, 114. The server(s) 102, 114 may be configured to communicate with one or more client computing platform(s) 128 according to a client/server architecture. The users may access system 100 via client computing platform(s) 128.

[0051] In some implementations, server(s) 102, 114 may be configured to execute one or more computer program modules. The computer program modules may include one or more of a reservation module 106, a user profile module 118, a link module 120, a bill splitting module 122, and/or any other modules.

[0052] The reservation module 106 may be configured to access and/or manage one or more reservations. Reservations may be made in numerous ways including through calling a business, emailing the business, and/or through software. The reservation module 106 may manage any reservations comprising time, date, location, and service requested of a business.

[0053] The a user profile module 118 may be configured to access and/or manage one or more user profiles and/or user information associated with users of the system 100. The one or more user profiles and/or user information may include information stored by server(s) 102, 114, one or more of the client computing platforms 128, and/or other storage locations. The user profiles may include, for example, information identifying users (e.g., a username or handle, a number, an identifier, and/or other identifying information) within the virtual space, security login information (e.g., a login code or password), virtual space account information, subscription information, payment account information, relationship information (e.g., information related to relationships between users in the virtual space), usage information, demographic information associated with users, interaction history of the user with the system, information stated by users, purchase information of users, browsing history of users, a client computing platform identification associated with a user, a phone number associated with a user, and/or other information related to users.

[0054] A link module 120 may be configured to link an application to a ticket by identification and/or link a ticket to a table from a reservation system. In some implementations, the user may be provided a list of tabs to select. The user may select a table number and/or may select a from a list of tabs. The tabs may be shown by table number, last name, first name, check number, and/or items on the tab. Patrons may not always check-in using the client computing platform(s) 128 before they order their first items. The client computing platform(s) 128 may comprise a mobile application and/or any other type of interface application. In some implementations, the mobile application allows an individual to use a receipt number printed on a physical receipt to access a tab that was opened without using the mobile application. The server(s) 102, 114 may use the number input from the patron to search the point of sale system for the appropriate ticket to display on the mobile application. Once a match is found, the ticket is presented to the user on the mobile application for payment. [0055] Many patrons make a reservation at a venue prior to entering the establishment. Patrons may make the reservation using a reservation system, a third party application, calling via a telephone, or using a reservation feature in the mobile application. The mobile application may request that the server to connect with a reservation system to link a reservation made by the patron prior to entering the venue with a table number entered on the reservation system. The server would then open the ticket on the point of sale system using the proper table number based on this information. The user would no longer be required to select their table number on the mobile application, as the server was able to source this information from the reservation system.

[0056] A bill splitting module 122, may be configured to split the bill amongst two or more patrons directly through the client computing platform(s) 128. The client computing platform(s) 128 may comprise a mobile application. The mobile application which may have various ways of adding friends to a shared tab. Because the application has access to the phones contact list, as well as third party social networks, it can display a list of contacts that can be added to the shared tab. When a user decides to invite friends to their tab, they are presented with this list, and can tap one or more contacts that should be granted access. The mobile application allows for an even split of the bill, an itemized bill split and/or a random bill split through the application. In some implementations, user may be allowed to split coupons and/or any promotional codes. In some implementations, user may have promotional credit in their accounts which they can user instead of paying with real currency. In some implementations, the users may share this promotional credit with others, and/or just use it to pay for their own tab. Any user who has access to the shared tab can initiate the bill split and the method of the bill split (User A). All of the other users who have access to the shared tab receive a notification that User A suggests the bill be split evenly, itemized and/or randomly. This notification may also include the total amount each user will be paying if they approve the bill split.

[0057] The server(s) 102, 114, client computing platform(s) 128, and/or external resource(s) 130 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network 126 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, 114, client computing platform(s) 128, and/or external resource(s) 130 may be operatively linked via some other communication media.

[0058] The server(s) 102, 114 may comprise electronic storage 112, 124, one or more processors 104, 116, and/or other components. The server(s) 102, 114 may include communication lines, or ports to enable the exchange of information with a network 126 and/or other computing platforms. The processors 104, 116 may be configured to execute computer program modules. The processors 104, 106 may be configured to execute the computer program modules via one or more of hardware, software, and/or firmware. The computer program modules may include reservation module 106, a user profile module 118, a link module 120, a bill splitting module 122, and/or any other computer program modules. Although system 100 may be described in certain sections herein as including server(s) 102, 114 , this is not intended to be limiting. The server(s) 102, 114 may be separate and distinct from system 100, and may be provided by an entity that is separate from, for example, the entity providing system servers. In some implementations, the functionality attributed herein to server(s) 102, 114 may be provided by system servers.

[0059] The server(s) 102, 114 may be incorporated on any point of sale (POS) system. The POS system includes a processor in communication with a memory storing data, which includes the order and the payment account data. The POS system can be an electronic cash register machine, which includes a credit card processing unit and cash storage. The POS system can include a means for wired or wireless communication over a network. The means are in communication with the processor. For example, such means can be a dock, a port or an antenna. The POS system can be linked to a website capable of receiving orders or processing payment. The POS system can include a sensor for remote detection of the mobile device. The processor can be a single core, dual core, a multi-core or a system-on- chip. The memory can be random-access memory (RAM), virtual storage, real storage, cloud storage, flash memory or physical disk storage, such as an internal or external hard drive. The data stored in the memory can be encrypted and stored in the memory in an encrypted state. The data can be received in an encrypted state and then be decrypted, either on-the-fly or on-demand, and stored in a decrypted state in the memory.

[0060] The mobile device includes a processor in communication with a memory, an input means, such as a keyboard, a touchscreen or a microphone, and an output means, such as a display or a speaker. The mobile device can be a smartphone or a tablet computer.

[0061] A given client computing platform(s) 128 may include one or more processors configured to execute computer program modules. The computer program modules may be configured to enable an expert or user associated with the given client computing platform(s) 128 to interface with system 100 and/or external resource(s) 130, and/or provide other functionality attributed herein to client computing platform(s) 128. By way of non-limiting example, the given client computing platform(s) 128 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms. The external resource(s) 130 may include sources of information, hosts and/or providers of virtual environments outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resource(s) 130 may be provided by resources included in system 100. In some implementations, the point of sale (POS) system may be within external resource(s) 130. In some implementations, the POS terminal may be located within server(s) 102, 114. A user may check-in by sending location information to a POS system which includes a central processing unit (CPU) in communication with a memory and a display. The check-in can be wirelessly performed via direct communication with POS system or via GPS, cellular network, Wi-Fi network, or a social networking service. The check-in can be performed via a wired technology as well. Upon successful check-in, the mobile device may appear as physically present in the business on the POS system.

[0062] The server(s) 102, 114 may include electronic storage 112, 124, one or more processors 104, 116, and/or other components. The server(s) 102, 114 may include communication lines, or ports to enable the exchange of information with a network 126 and/or other computing platforms. Illustration of server(s) 102, 114 in FIG. 1 is not intended to be limiting. The server(s) 102, 114 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102, 114. For example, server(s) 102, 114 may be implemented by a cloud of computing platforms operating together as server(s) 102, 114.

[0063] Electronic storage 112, 124 may comprise electronic storage media that electronically stores information. The electronic storage media of electronic storage 112, 124 may include one or both of system storage that is provided integrally (i.e., substantially nonremovable) with server(s) 102, 114 and/or removable storage that is removably connectable to server(s) 102, 114 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 112, 124 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. The electronic storage 112, 124 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 112, 124 may store software algorithms, information determined by processor(s) 104, 116, information received from server(s) 102, 114, information received from client computing platforms xx, and/or other information that enables server(s) 102, 114 to function as described herein.

[0064] Processor(s) 104, 116 is configured to provide information processing capabilities in server(s) 102, 114. As such, processor processor(s) 104, 116 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 104, 116 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 104, 116 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 104, 116 may represent processing functionality of a plurality of devices operating in coordination. The processor(s) 104, 116 may be configured to execute modules 106, 118, 120, 122, and/or any other modules. Processor(s) 104, 116 may be configured to execute modules 106, 118, 120, 122, and/or any other modules by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 104, 116.

[0065] It should be appreciated that although modules 106, 118, 120, 122, and/or any other modules are illustrated in FIG. 1 as being co-located within a single processing unit, in implementations in which processor(s) 104, 116 includes multiple processing units, one or more of modules 106, 118, 120, 122, and/or any other modules may be located remotely from the other modules. The description of the functionality provided by the different modules 106, 118, 120, 122, and/or any other modules described below is for illustrative purposes, and is not intended to be limiting, as any of modules 106, 118, 120, 122, and/or any other modules may provide more or less functionality than is described. For example, one or more of modules 106, 118, 120, 122, and/or any other modules may be eliminated, and some or all of its functionality may be provided by other ones of modules 106, 118, 120, 122, and/or any other modules . As another example, processor(s) 104, 116 may be configured to execute one or more additional modules that may perform some or all of the functionality attributed below to one of modules 106, 118, 120, 122, and/or any other modules.

[0066] FIG. 2 illustrates method 200 of allowing the system to link the ticket to a table from the reservation system according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. The operations of method 200 presented below are intended to be illustrative. In some embodiments, method 200 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Some elements of this figure are described above. Thus, any repetitive detailed description thereof will hereinafter be omitted or simplified in order to avoid complication. Additionally, the order in which the operations of method 200 are illustrated in FIG. 2 and described below is not intended to be limiting.

[0067] In some embodiments, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.

[0068] At operation 202, check-in data regarding the presence of a mobile computing device of a first user in the business establishment may be received. In some implementations, the check-in data may be based upon GPS on the mobile phone of the first user. In some implementations, the server may transmit to the POS system, a location of the first user based upon check-in data received from the mobile phone of the first user.

[0069] In some implementations, the server may communicate via a social networking service, a location of the first user based upon check-in data. The method allows for deep integration into third party social media services for ease of check-in to an establishment. Many users utilize social media services like Facebook, Foursquare, Path, Instagram, and others to check-in to venues or locations. The server may monitor these location based social networking features when the user connects these accounts inside of the mobile application. The server can associate a check-in on a third party network with a check-in to a venue accepting payment through our mobile application. These allows the user to check-in on only one social network, and subsequently have a ticket opened on the venues point of sale system automatically.

[0070] In an exemplary embodiment, a user may open mobile application and connect third party social media services to their account. The user may check-in on a third party social media account to a venue that participates in the mobile payment service. The server may monitor check- ins on third party services, and associate the check- in with the user's account. The server may open a ticket on the appropriate venues point of sale system based on check-in data from third party. The user may open the mobile payment application and sees that they have an active tab available for use. [0071] In some implementations, the method allows for sharing of in-app interactions on third party social media services. The user may have the ability to attach their social media accounts inside of the mobile application for ease of sharing these interactions. When the user chooses to share, a message is sent to the server, which can share seamlessly amongst one or more social media services by transmitting a request to the appropriate social media server. The user has the ability to share items including, but not limited to: which venue they're currently checked-in to; friends that they are checked-in with; items that they are ordering at the venue; amount they are spending at the venue (tip, tax, subtotal, total); awards and credits earned through the application; check-out status; time spent in venue; location inside the venue; reservation status and confirmation; and/or an other information.

[0072] At operation 204, the client server for a reservation associated with the first user may be queried. The table id may be based on a previous table selection made by the user when creating the reservation. The data to be queried may be stored in a database on the client electronic storage and/or the host electronic storage and/or any other storage location.

[0073] At operation 206, transmittal of a reservation for the first user in a business establishment from a client server of the business establishment, the reservation comprising a table selection indicating a table identification and a time and date of dining may be received. The reservation may comprising a table selection indicating a table id and a time and date of dining and selection of a service (e.g., pre-ordering a type of food). In some implementations, the table selection may be based on displaying, by the computer, a list of tables present in the business establishment to the first user and allowing the first user to select a particular table.

[0074] At operation 208, upon receiving the transmittal of the reservation, the host server may associate the mobile computing device of the first user with the reservation. Many patrons make a reservation at a venue prior to entering the establishment. Patrons may make the reservation using a reservation system, a third party application, calling via a telephone, or using a reservation feature in the mobile application. The mobile application requests that the server to connect with a reservation system to link a reservation made by the patron prior to entering the venue with a table number entered on the reservation system. The server may then open the ticket on the point of sale system using the proper table number based on this information. The user would no longer be required to select their table number on the mobile application, as the server was able to source this information from the reservation system.

[0075] In an exemplary embodiment, the user makes a reservation at a venue through any reservation system, this could be built into the mobile application, a third party reservation system, or via any other computing system. The user checks-in as present at the venue on the mobile application. The server queries the reservation system for table number and table ID associated with the users reservation. The server opens a ticket and associates the ticket on the POS system with the table ID.

[0076] At operation 210, the host server may transmit to the mobile computing device of the first user, the table identification based on the reservation associated with the first user.

[0077] In an exemplary embodiment, when a user opens a tab on their mobile device, a common issue is determining where the user is in the specific venue. Typically, the wait staff would manually select at the POS system which table the patron is seated. Because the mobile application allows the user to open a tab, this process can allow the patron to select the table for entry into the system. When a user checks-in on the mobile application, the server may query the point of sale system for a list of tables present in the restaurant's database. The tables are presented to the user, who can then select which table they are currently seated. In some implementations, the table may be pre-selected for the user by the wait staff. This can be done through a visual queue, verbally asking wait staff, scanning a QR code, transmitting using an near field communication (NFC) device, etc. After the table number is selected by the user, the server opens the ticket appropriately on the POS system by associating the ticket with the correct table ID in the POS system, and labeling that ticket with the correct table number.

[0078] In some implementations, a user may select a venue on the mobile application and check-in as present at the venue. The server may query the POS system to see if the venue offers table service. If the venue offers table system, the server queries the venue system for the table layout of the venue, including table name, and table ID as referenced in the POS system. The server may return a list of table names to the users mobile device. The user may select the table they are currently seated at on the mobile device. The server may open a ticket on the POS system and associates this ticket on the POS system with the table ID selected by the user. The ticket is labeled on the POS system with the corresponding table name of the table ID on the POS system.

[0079] At operation 212, the host server may transmit to the point of sale (POS) system, the check-in data and payment account data associated with the first user.

[0080] At operation 214, the host server may request generation of a ticket on the POS system based on the reservation associated with the first user.

[0081] At operation 218, the host server may associate in a database the ticket corresponding to the reservation, the payment account data, and an order placed by the first user.

[0082] The payment account data can be stored before the user checked-in, such as where user has a preexisting account in POS system, or the payment account data can be stored after the check-in. The payment account data may be data that allows a vendor, such the restaurant, the bar, and/or any other business establishment, to place a charge onto an account associated with a domestic or a foreign financial institution. Although typically, the account will be the account of the user of the mobile device, other accounts can be used as well. For example, a user of the mobile device may provide information of the account associated with the user's parent, a spouse, a child or a friend.

[0083] The payment account data can be credit card information, such as a credit card account number, a name associated with the credit card account, an expiration data and a security code. The payment account data can be debit card information, such as a debit card account number, a name associated with the debit card account and a personal identification number (ΡΓΝ). The payment account data can be a gift card account data, such as a gift card number and a ΡΓΝ. The payment data can be real or virtual currency or rewards points. The payment account data can be financial institution website login data or data stored on a website, such as a payment account data aggregator. In some implementations, the user may pay through a checking/savings account, debit card, credit card, and/or pre-paid card. For example, the user logs onto such website and manually inputs or imports the payment account data from the website into the software application. In some implementations, the software application is programmed to automatically login into the website, access the payment account data and either communicate the payment account data to the POS system without permanently locally storing the payment account data or import the payment account data information into the software application and then transmit the payment account data to the POS system.

[0084] The payment account data can be stored in or accessible via the memory of the mobile device. For example, the user manually inputs the payment account data into a software application running on the mobile device. The user can manually input the data before or after entry into the restaurant or the bar. Alternatively, the payment account data is stored in a NFC chip in communication with the mobile device, which includes the NFC chip. For example, a software application running on the mobile device accesses the payment account data stored on the NFC chip. Alternatively, the software application accesses the payment account data from a payment account data aggregator. The payment account data can be stored in another mobile device and the mobile device accesses the another mobile device to retrieve/import the payment account data onto the mobile device. Alternatively, the payment account data can be stored remotely for remote access, such as via a website or web accessible service.

[0085] Upon access of the payment account data, the software application, directly or indirectly, communicates with the POS system via the wireless or the wired means. If the software application is capable of directly communicating with the POS system, then if the mobile device is present within a detection range of the POS system, then the mobile device or the POS system, either manually or automatically, detects the location/presence of the POS system or the mobile device, respectively. If the software application is capable of indirect communication with the POS system, such as over the Internet or cellular networks, then, upon the user's action, such as logging into a website or a service associated with the POS system, the POS system detects the presence of the mobile device. As a result, the mobile device appears local or as within the detection range on a display of the POS system and the waiter can take the order from the user. In some implementations, if the user's mobile device leaves the area of the business entity, an automatic payment may be initiated. For example, when the user checks in, the user's bill may be automatically tabulated. In the case the user leaves and forgets to pay their bill, once the user's mobile device leaves a pre-determined range of the business entity, an automatic payment from the user's account to the business may be initiated.

[0086] The software application can be generic or specific to the restaurant, the bar and/or business entity. The software application can be a mobile application. For example, the bar has a software application specific to its POS system. Thus, the user downloads and installs a specific software application for that POS system. In order to properly operate, the specific software application requires a creation of an account, which requires entry of the payment account data. The payment account data can be manually entered, imported from an NFC chip or the memory or accessed via the Internet. Upon creation of the account and visiting of the bar, irrespective of the placement of the order, the user runs the specific software application, which communicates with the POS and allows for display of information indicating the presence of the user.

[0087] In some implementations, a bill including the one or more orders to the first user may be transmitted. As a result, the user can view his/her individual bill, either in real-time or via a pre-programmed delay. The order data may include an itemized price list of the order, as described above, and a total amount due of the order, as described above. If the user subsequently modifies his/her order, then updated order data is sent to the server. The modification process and updated order data can be repeated multiple times and the bill is updated during or after each modification.

[0088] In an exemplary embodiment, the order is placed for a food item, such as bread, steak or chips, or a liquid item, such as water, soda, juice, spirits or beer. The order is placed by the user of the mobile device or a party, such as a friend, a child or a spouse, associated with the user of the device. For example, if a parent and a child visit a restaurant and the parent controls the mobile device, then either the parent or the child can place the order on behalf of the child and the parent. The order can be placed via an oral communication to a waiter, who enters the order into the POS system. The order can also be placed by orally speaking into a microphone, such as at a drive-in at a restaurant, and the waiter manually entering the order into the POS system. The order can be placed into a voice recognition system where the order is automatically entered into the POS system. [0089] In some implementations, at least partial payment of the bill using the payment account data may be received. At any point, the user can pay his/her entire bill or a portion of his/her bill by wirelessly sending a pay bill request from the client computing device to the server, which upon receipt of the pay bill request, charges an account associated with the payment account data. The pay bill request includes data corresponding to a specific amount the user desires to charge to the account. The payment account data can be verified after the receipt of the pay bill request. A bill pay confirmation request can be sent to client computing device after the account associated with the user payment account data has been charged. The user can also add a tip to the pay bill request so the payment would cover the bill and a tip to the waiter. After the user paid his/her bill, in order to prevent unauthorized charges, the user can wirelessly send a request to either halt access to his/her account stored in the system or have his/her account deleted from the system. A confirmation of halting access or account deletion can be sent to the client computing device.

[0090] In some implementations, the server and the mobile phone of the first user may transmit an identification of a second user in the establishment and the server may associate the second user with the bill of the first user. In some implementations, the server may receive a request from a mobile phone of the second user for at least partial payment of the bill using payment account data associated with the second user. In some implementations, the server may transmit the bill for display on a mobile phone of the second user.

[0091] The second user may control the mobile phone and, similarly to the first user, perform the check-in and the submission of the payment account data. If the first and second users jointly place one order and waiter enters that order as such, then the first and second users can each can pay a specified portion of the bill by wirelessly sending multiple pay bill requests from their client computing devices and/or mobile phones to the server. Upon receipt of the pay bill requests, the system charges multiple accounts associated with the payment account data submitted from client computing devices. The payment account data submitted via the client computing devices can be associated with one account. The first user can pay his/her share of the bill by wirelessly sending a pay bill request associated the payment account data submitted from their mobile device and have the second user pay his/her share of the bill by wirelessly sending a pay bill request associated the payment account data submitted from the second user's mobile device at different times. If the second user checks-in, but cannot submit payment account data or the submitted payment account data is invalid, then the first user can pay the second user's portion of the bill by wirelessly sending a pay bill request associated the payment account data submitted from the mobile device and server crediting the first user as paying the second user's portion of the bill. However, if desired, the second user can manually pay the remaining portion of the bill.

[0092] FIG. 3 illustrates method 300 of allowing the system to link an existing ticket to a mobile application ticket according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. The operations of method 300 presented below are intended to be illustrative. In some embodiments, method 300 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Some elements of this figure are described above. Thus, any repetitive detailed description thereof will hereinafter be omitted or simplified in order to avoid complication. Additionally, the order in which the operations of method 300 are illustrated in FIG. 3 and described below is not intended to be limiting.

[0093] In some embodiments, method 300 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 300 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 300.

[0094] At operation 302, check-in data regarding the presence of a user in a business establishment may be received by the host server. In some implementations, the wait staff may initiate a ticket on the point of sale system prior to the patron checking-in via the mobile device. The system described herein allows for the server to monitor tickets present on the point of sale system and link these tickets with a ticket opened on the patrons mobile device via the check-in information. This can be done through the server matching manually-opened ticket information with mobile device ticket information, or done by an employee by combining the tickets using functionality built into the point of sale system. This functionality may provide a seamless process for the end-user, regardless of who initiated the ticket (patron via mobile device, or wait staff via point of sale system).

[0095] At operation 304, the check-in data and payment account data associated with the first user may be transmitted by the host server. In some implementations, the server is further configured to receive check-in information in response to the first user selecting a check- in icon on a touchscreen of the personal mobile phone of the first user.

[0096] At operation 306, a record of first order placed by the first user may be received by the host server from a POS system prior to receiving check-in data regarding the presence of the mobile computing device of the first user in the business establishment. In some implementations, the user may place the order physically by ordering the wait staff. In some implementations, the user may order using their mobile device and/or any other client computing device. After the user has placed an order, a ticket linked to the user may be opened.

[0097] At operation 308, a generation of a ticket corresponding to the payment account data, and the record of the first order placed by the first user may be requested by the host server. The user may continue to order after the ticket has been opened. The user may physically order by ordering with the same wait staff or different wait staff, and/or the user may electronically order. At operation 310, a record of a second order placed by the first user may be received by the host server from a POS system. At operation 312, the record of the second order placed by the first user to the ticket corresponding to the payment account data, and the record of the first order placed by the first user may be linked by the host server.

[0098] At operation 314, a bill including the first and second order to the first user may be transmitted by the host server to the POS system. In some implementations the user may check-in at a venue via a mobile application on their mobile device, selecting that they already have a ticket open. The server passes the check-in information to the venue's POS system and creates a ticket. The server combines a previously opened ticket with the new mobile application created ticket. The user sees all previously ordered items, as well as future items reflected on the mobile application.

[0099] At operation 316, at least partial payment of the bill using the payment account data may be received by the host server from the POS system. In some implementations, the server and the mobile phone of the first user may transmit an identification of a second user in the establishment and the server may associate the second user with the bill of the first user. In some implementations, the server may receive a request from a mobile phone of the second user for at least partial payment of the bill using payment account data associated with the second user. In some implementations, the server may transmit the bill for display on a mobile phone of the second user. [00100] The second user may control the mobile phone and, similarly to the first user, perform the check-in and the submission of the payment account data. If the first and second users jointly place one order and waiter enters that order as such, then the first and second users can each can pay a specified portion of the bill by wirelessly sending multiple pay bill requests from their client computing devices and/or mobile phones to the server. Upon receipt of the pay bill requests, the system charges multiple accounts associated with the payment account data submitted from client computing devices. The payment account data submitted via the client computing devices can be associated with one account. The first user can pay his/her share of the bill by wirelessly sending a pay bill request associated the payment account data submitted from their mobile device and have the second user pay his/her share of the bill by wirelessly sending a pay bill request associated the payment account data submitted from the second user's mobile device at different times. If the second user checks-in, but cannot submit payment account data or the submitted payment account data is invalid, then the first user can pay the second user's portion of the bill by wirelessly sending a pay bill request associated the payment account data submitted from the mobile device and server crediting the first user as paying the second user's portion of the bill. However, if desired, the second user can manually pay the remaining portion of the bill (e.g., cash, physical credit, debit, gift and/or pre-paid cards, and/or check, etc.).

[00101] FIG. 4 illustrates method 400 of allowing the system to split the bill among multiple users according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. The operations of method 400 presented below are intended to be illustrative. In some embodiments, method 400 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Some elements of this figure are described above. Thus, any repetitive detailed description thereof will hereinafter be omitted or simplified in order to avoid complication. Additionally, the order in which the operations of method 400 are illustrated in FIG. 4 and described below is not intended to be limiting.

[00102] In some embodiments, method 400 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 400 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 400.

[00103] At an operation 402, check-in information and payment information via a personal mobile phone corresponding to a first user may be received by the host server. In some implementations, the payment information and/or any other information related to the user may be retrieved from the first user's profile information.

[00104] At an operation 404, user profile information corresponding to the first user, the user profile information containing payment information related to the first user may be queried by the host server. In an exemplary embodiment, the user can check-in into the restaurant or the bar by sending location information to the POS system. The check-in can be performed via the NFC chip coupled to the mobile device communicating with the NFC chip reader coupled to the POS system. The check-in can be automatically or manually wirelessly performed via a GPS protocol or a social networking service. The POS system can function as a network gateway/r outer by creating a WPAN or a WLAN and the mobile device automatically detects the presence of such network and thereby checks-in into the POS system. Regardless of the method, upon successful check-in, the mobile device appears to the POS system as physically present in the restaurant or the bar. For example, when the user walks into the bar, the software application, running either in the background or the foreground of the mobile device, automatically detects the presence of the WPAN and checks-in the user into the POS system.

[00105] At an operation 406, identification from the mobile computing device of the first user of a presences of a second user in the business establishment may be received. In some implementations, the identification is based on the first user tagging the second user. In some implementations, the second user accepts the tag from the first user. In some implementations, the tag is sent through a short messaging service (SMS) message, multimedia messaging service (MMS), and/or email. In some implementations, the identification may include validating the user information. Validation may involve determining whether the user of the mobile device is identical to the user authorized to incur the charge to the payment account associated with the payment account data.

[00106] At an operation 408, the host server may open a ticket on the POS system based on an order place by the first user and the second user. In some implementations, association may involve taking the order from the user, associating the order with the already validated and verified payment account data and allowing the user to view the bill associated with the order. Also, the processing may involve modifying the order if the user desires to modify the order.

[00107] At an operation 410, the host server may transmit a bill for display on the mobile computing device of the first user and a mobile computing device of the second user to the POS system. In some implementations an identification of a second user in the establishment may be received from the server and the computing device of the user. In some implementations, the second user may be associated with the bill of the first user. In some implementations, a request from a mobile phone of the second user for at least partial payment of the bill using payment account data associated with the second user may be received. In some implementations, the bill for display on a mobile phone of the second user may be transmitted.

[00108] At an operation 412, the bill among the first user and the second user based on input from the first user may be allocated by the host server. In some implementations, splitting and/or allocating the bill comprises: an even divide of the bill, an itemized split corresponding to items the first user ordered and items the second user ordered, randomly splitting between the first and second user, and randomly charges the first user or the second user for the bill. In an exemplary embodiment, the system allows for splitting the bill amongst two or more patrons directly through the mobile application. The system allows for a seamless bill splitting experience between multiple patrons.

[00109] At an operation 414, at least partial payment for the bill according to the validated payment information in response to the host server authorizing the at least partial payment from the mobile computing device of first user and the mobile computing device of the second user may be received by the host server. In some implementations, the method has various ways of adding friends to a shared tab. Because the application has access to the phones contact list, as well as third party social networks, it can display a list of contacts that can be added to the shared tab. When a user decides to invite friends to their tab, they are presented with this list, and can tap one or more contacts that should be granted access. We refer to this feature as tagging users on the tab.

[00110] In some implementations, if another user is tagged on the tab, and already has the mobile application installed, they will be able to view this tab anytime they open the application. The server automatically grants access to the shared tab to any user that has been tagged inside the application. In many cases, the user may be tagged on the tab, but has not yet installed the mobile application. The server may send an SMS message, MMS message and/or email to the tagged user, notifying them that they've been tagged on the shared tab, and includes a link to download the mobile application. The server can determine based on a user account list, who to add inside the application, and who to send an SMS message, MMS message and/or email notification. Once the notification is received and the mobile application is downloaded, the server recognizes that this new user has previously been added to a shared tab, and displays that tab to the new user.

[00111] In some implementations, for ease of splitting, all of the parties present on a tab decide they want to split a bill evenly. The mobile application allows for an even split of the bill through the application. Any user who has access to the shared tab can initiate an even bill split (User A). All of the other users who have access to the shared tab receive a notification that User A suggests the bill be split evenly. This notification may also include the total amount each user will be paying if they approve the even bill split. If all of the other parties approve the even bill split, the server carries out the transaction through communication with the point of sale system inside of the venue. The users are notified that the payment has been approved by the venue. This completes the transaction through the mobile application.

[00112] In an exemplary embodiment, when multiple parties are on one tab, they wish to split the bill on an itemized level. The mobile application facilitates this interaction by allowing a user to select only the items in which they've consumed. Any user on the shared tab can suggest an itemized split, which sends a notification to other users on the shared tab for approval. When the itemized split is initialized, each party can select his/her items, and post a payment through the server, on the point of sale system, for their specific items. Wait staff can print a physical remainder receipt so that other parties who do not have the mobile application can settle the transaction as well. [00113] In some implementations, users who have joined a shared tab would like to randomize the payment process. Traditionally, this has been done by providing wait staff with multiple credit cards, and asking that only one be used to close the entire total of the tab. The mobile application allows for a computerized randomization of this process. Any user on the shared tab can initiate a request for a randomized bill split, sending a notification to the other users tagged on the shared tab allowing them to opt-in or approve this splitting method. If all of the users have opted in to the randomized bill split, the server will make a random selection as to which payment method will be used, and will close the tab using this payment method, sending a notification to the point of sale system that the tab has been closed. A notification is sent back to all of the parties on the shared tab with the result of the randomized bill split.

[00114] The functionality described herein can be implemented by numerous modules or components that can perform one or multiple functions. Each module or component can be executed by a computer, such as a server, having a non-transitory computer-readable medium and processor. In one alternative, multiple computers may be necessary to implement the functionality of one module or component.

[00115] Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as "processing" or "computing" or "calculating" or "determining" or "measuring" or "selecting" or "displaying" or "identifying" or "detecting" or the like, can refer to the action and processes of a data processing system, or similar electronic device, that manipulates and transforms data represented as physical (electronic) quantities within the system's registers and memories into other data similarly represented as physical quantities within the system's memories or registers or other such information storage, transmission or display devices. [00116] The exemplary embodiments can relate to an apparatus for performing one or more of the functions described herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a machine (e.g. computer) readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs and magnetic-optical disks, read only memories (ROMs), random access memories (RAMs) erasable programmable ROMs (EPROMs), electrically erasable programmable ROMs (EEPROMs), magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a bus.

[00117] The exemplary embodiments described herein are described as software executed on at least one server, though it is understood that embodiments can be configured in other ways and retain functionality. The embodiments can be implemented on known devices such as a personal computer, a special purpose computer, cellular telephone, personal digital assistant ("PDA"), a digital camera, a digital tablet, an electronic gaming system, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), and ASIC or other integrated circuit, a digital signal processor, a hard-wired electronic or logic circuit such as a discrete element circuit, a programmable logic device such as a PLD, PLA, FPGA, PAL, or the like. In general, any device capable of implementing the processes described herein can be used to implement the systems and techniques according to this invention.

[00118] It is to be appreciated that the various components of the technology can be located at distant portions of a distributed network and/or the Internet, or within a dedicated secure, unsecured and/or encrypted system. Thus, it should be appreciated that the components of the system can be combined into one or more devices or co-located on a particular node of a distributed network, such as a telecommunications network. As will be appreciated from the description, and for reasons of computational efficiency, the components of the system can be arranged at any location within a distributed network without affecting the operation of the system. Moreover, the components could be embedded in a dedicated machine.

[00119] Furthermore, it should be appreciated that the various links connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements. The term module as used herein can refer to any known or later developed hardware, software, firmware, or combination thereof that is capable of performing the functionality associated with that element. The terms determine, calculate and compute, and variations thereof, as used herein are used interchangeably and include any type of methodology, process, mathematical operation or technique.

[00120] The embodiments described above are intended to be exemplary. One skilled in the art recognizes that there are numerous alternative components and embodiments that may be substituted for or included in the particular examples described herein and such additions or substitutions still fall within the scope of the invention.

[00121] FIG. 5A is a flowchart 500 of an example embodiment of a process for table selection according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In an exemplary embodiment, when a user opens a tab on their mobile device, a common issue is determining where the user is in the specific venue. Typically, the wait staff would manually select at the POS system which table the patron is seated. Because the mobile application allows the user to open a tab, this process can allow the patron to select the table for entry into the system. When a user checks- in on the mobile application, the server queries the point of sale system for a list of tables present in the restaurant's database. The tables are presented to the user, who can then select which table they are currently seated. In some implementations, the user may be provided a list of tabs to select. The user may select a table number and/or may select a from a list of tabs. The tabs may be shown by table number, last name, first name, check number, and/or items on the tab. This can be done through a visual queue, verbally asking wait staff, scanning a QR code, transmitting using an NFC device, etc. After the table and/or tab number is selected by the user, the server opens the ticket appropriately on the POS system by associating the ticket with the correct table and/or tab ID in the POS system, and labeling that ticket with the correct table and/or tab number.

[00122] In some implementations, the user selects a venue on the mobile application and checks-in as present at the venue. The server queries the POS system to see if the venue offers table service. If the venue offers table system, the server queries the venue system for the table layout of the venue, including table name, and table ID as referenced in the POS system. The server returns a list of table names to the users mobile device. The user selects the table they are currently seated at on the mobile device. The server opens a ticket on the POS system and associates this ticket on the POS system with the table ID selected by the user. The ticket is labeled on the POS system with the corresponding table name of the table ID on the POS system.

[00123] FIG. 5B is a user interface 502 of an example embodiment of displaying a list of nearby venues according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. Nearby venues may be determined based on the user's location and automatically determining the GPS coordinates. In some implementations, the user may input their location information.

[00124] FIG. 5C is a user interface 504 of an example embodiment of displaying a single venue with general information and allowing a user to open a tab according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, images of services offered by the venue may be displayed for the user to view and select.

[00125] FIG. 5D is a user interface 506 of an example embodiment of determining where the user is looking to open a tab inside of the venue according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In an exemplary embodiment, the user may have the option to open a tab at the bar of a restaurant, and/or a table of the restaurant.

[00126] FIG. 5E is a flowchart 508 of an example embodiment of a process for ticket/employee assignment according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. One of the challenges in opening a ticket on the point of sale system is assigning the ticket to the correct member of the wait staff (the member servicing the patron). Tickets opened via a mobile device can be assigned to one employee or unassigned. If the ticket is unassigned, then wait staff will need to navigate the menus of the user interface of the POS system to find the unassigned ticket and transfer the ownership of that ticket to the appropriate wait staff. The ticket will then be visible anytime the wait staff logs into the POS system.

[00127] In some implementations, the server uses opens a separate ticket for each employee clocked-in to the POS system, and assigns that ticket to that employee's ID. Every employee that walks up to the point of sale system can then see the ticket without navigating to another menu in the POS system. The server continues to monitor this group of tickets, waiting for an item to be added to one of the tickets. Once an item is added to a ticket, the ticket is deemed active, and the inactive tickets (assigned to other employees) are automatically closed. [00128] In an exemplary embodiment, three bartenders may be clocked-in for their shift at a bar. A patron enters the establishment and checks-in via the mobile application. Three separate tickets are opened, one assigned to each individual bartender that is clocked in. The patron orders with one of the bartenders, who adds an item to the ticket assigned to him/her. As soon as the item is added to that ticket, the remaining two inactive tickets are closed out and removed from the point of sale system.

[00129] In some implementations, the user selects a venue and checks-in on their mobile device using the mobile application. The server queries the POS system for a list of all clocked-in employees on the venue. The server opens a ticket on the POS system for each of the employees present at the venue, associating a new ticket with each of the employees at the venue. The server monitors all of the tickets, waiting for an item to be added to one of the tickets. An employee adds an item to a ticket, as ordered by the patron, on the POS system to the ticket associated with their employee ID. The server closes out all of the tickets associated with this user, with exception of the ticket that has an active order in place (step 5).

[00130] FIG. 5F is a flowchart 510 of an example embodiment of a process for linking the application to a ticket by an ID according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, patrons may not always check-in using the mobile application before they order their first items. The mobile application allows an individual to use a receipt number printed on a physical receipt to access a tab that was opened without using the mobile application. The server uses the number input from the patron to search the point of sale system for the appropriate ticket to display on the mobile application. Once a match is found, the ticket is presented to the user on the mobile application for payment.

[00131] In an exemplary embodiment, the employee prints a receipt for the user, which shows a ticket ID number. The user enters this ticket ID number on the mobile application. The server queries the POS system for any tickets matching the ID that the user has entered on their mobile device. The server links the POS system ticket to the mobile application based on a successful match of the ticket ID. The active ticket is displayed on the users mobile device.

[00132] FIG. 5G is a flowchart 512 of an example embodiment of a process for linking a ticket to a table from the reservation system according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, patrons make a reservation at a venue prior to entering the establishment. Patrons may make the reservation using a reservation system, a third party application, calling via a telephone, or using a reservation feature in the mobile application. The mobile application requests that the server to connect with a reservation system to link a reservation made by the patron prior to entering the venue with a table number entered on the reservation system. The server would then open the ticket on the point of sale system using the proper table number based on this information. The user would no longer be required to select their table number on the mobile application, as the server was able to source this information from the reservation system.

[00133] In an exemplary embodiment, the user makes a reservation at a venue through any reservation system, this could be built into the mobile application, a third party reservation system, or via any other computing system. The user checks-in as present at the venue on the mobile application. The server queries the reservation system for table number and table ID associated with the users reservation. The server opens a ticket and associates the ticket on the POS system with the table ID.

[00134] FIG. 5H is a user interface 514 of an example embodiment of displaying a list of tables, as queried from the system for the user to select where they are seated according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In an exemplary embodiment, the tables may be displayed to the user so they have the option to select and open table.

[00135] FIG. 51 is a user interface 516 of an example embodiment of showing a real time list of items that have been placed on the ticket according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, a user is interested in receiving notifications via their mobile device based on interactions happening inside of a venue. A server can monitor the interactions on the point of sale system, including but not limited to, items being added, total cost of tab, time the tab has been open, and other friends entering a venue. The server can then notify the user through mobile application notifications in real time. In some implementations, a user does not want to spend more than 100 dollars at a given venue. The server monitors their open point of sale ticket and sends notifications to the mobile application as they approach, and when they hit or exceed, their $ 100 threshold. In one embodiment, the server may send a notification as the user approaches the predetermined threshold. This notification system should not be limited to spending, as many other interactions inside of a venue are important for a user to know in real time.

[00136] In some implementations, a user can receive a notification through the app when: a table booked through a third party reservation system is ready; informs other members of a party know when each other have arrived; a certain threshold amount is hit. In an exemplary embodiment, a user sets a threshold at $100 dollars and received a notification when the tab goes above this threshold. The tab is closed outside of the system. In some implementations, the user forgets to close their tab and the wait staff closes the tab at the end of the night. The tab may be automatically closed by the server when detecting the user's mobile device is no longer located locally near the business entity. [00137] FIG. 5J is a user interface 518 of an example embodiment of allowing the user to set a tip by sliding an indicator across a bar and setting the percentage and tip amount according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, a list of items ordered and the optional tip amount may be displayed to the user.

[00138] FIG. 5K is a user interface 520 of an example embodiment of displaying a confirmation of charges before the payment is processed and allowing social sharing of interactions occurring within the mobile application according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure.

[00139] In some implementations, the system and process allows for automatic expensing through the mobile application for the means of accounting for transactions that take place inside the platform. The ability for the server to automatically send detailed expense reports to third party expensing software, email addresses, and expense accounts, allows for ease of reimbursement. Ability to receive an email receipt for all items settled through Dash. Ability to allocate expenses based on certain expense codes, (travel, hotel, dining) and account (personal, work). Ability to send bundled expenses / receipts to another person via email - or another means. (Send 20 different expenses to secretary for reimbursement)

[00140] FIG. 5L is a user interface 522 of an example embodiment of displaying a confirmation that the payment has processed, allowing a rating of the venue by the user, showing rewards earned by the user, and emailing a receipt confirmation of the charge according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. [00141] In some implementations, the system allows for the tracking of points and credits through the mobile application that can be used for promotional, discount, and marketing efforts. The points and/or credits may be stored in the user's profile. The server may keep track of points accrued through use of the application and apply these points to different interactions that can take place inside the application. In one example of a use of this system, a user may accrue points for each dollar spent through the application. The user can then redeem the points for a discount, which can be applied through the mobile application, towards a current or future bill/payment. These points can also be accrued through other interactions, like inviting friends to use the application and promoting on social media channels. In some implementations, the system provides: the ability to get points for using the system, and these points can be transferred or redeemed through the application.

[00142] In some implementations, the system provides a social layer between wait staff and patrons to communicate inside of the mobile application. Wait staff have found it difficult to connect with their clientele and establish a list of loyal patrons. The system allows for patrons to connect with their favorite bartenders, table servers, chefs, and other hospitality employees by following them inside of the mobile application. When a patron follows an employee, they have established a connection with them through the application. The employee can then provide certain interactions through the system. For example, a bartender could send a notification to all of their followers with offers, hours they're working at a venue, specials for users of the mobile application, and so on. The system also allows for wait staff to build a personal list of clientele through which they can find value in as they build their careers inside the hospitality vertical.

[00143] In some implementations, multiple patrons can follow their favorite local bartender through the mobile application. When the bartender clocks in on the point of sale system, these patrons would be able to view that their favorite bartender is on staff at the location. The bartender could send a notification through the system notifying his/her followers that he/she is running a special for half off drinks for the next two hours. This provides increased loyalty for both the venue as well as the employees working inside the venue.

[00144] In some implementations, a patron at an establishment may need assistance from a member of the staff but is unable to communicate this need with them. Sometimes the staff member may be serving other patrons or is unable to be located. The mobile application allows for the patron to request that a member of the staff attend to them through the application. The mobile application send a signal to the server, which in turn displays a message on the point of sale system, wait list system, and/or mobile device held by the employee indicating that the patron requires attention.

[00145] In some implementations, the system may allow for deep integration into third party social media services for ease of check-in to an establishment. Many users utilize social media services like Facebook, Foursquare, Path, Instagram, and others to check-in to venues or locations. Our server monitors these location based social networking features when the user connects these accounts inside of the mobile application. The server can associate a check-in on a third party network with a check-in to a venue accepting payment through our mobile application. These allows the user to check-in on only one social network, and subsequently have a ticket opened on the venues point of sale system automatically.

[00146] In an exemplary embodiment, a user opens mobile application and connects third party social media services to their account. The user may check-in on a third party social media account to a venue that participates in the mobile payment service. The server may monitor check-ins on third party services, and associates the check-in with the user's account. The server opens a ticket on the appropriate venues point of sale system based on check-in data from third party. The user opens the mobile payment application and sees that they have an active tab available for use.

[00147] In some implementations, the system allows for sharing of in-app interactions on third party social media services. The user has the ability to attach their social media accounts inside of the mobile application for ease of sharing these interactions. When the user chooses to share, a message is sent to the server, which can share seamlessly amongst one or more social media services by transmitting a request to the appropriate social media server. The user has the ability to share items including, but not limited to: which venue they're currently checked-in to, friends that they are checked-in with, items that they are ordering at the venue, amount they are spending at the venue (tip, tax, subtotal, total), awards and credits earned through the application, check-out status, time spent in venue, location inside the venue, reservation status and confirmation.

[00148] FIG. 5M is a flowchart 524 of an example embodiment of a process for linking an existing ticket to a mobile application ticket according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, the wait staff may initiate a ticket on the point of sale system prior to the patron checking-in via the mobile device. The system described herein allows for the server to monitor tickets present on the point of sale system and link these tickets with a ticket opened on the patrons mobile device via the check-in information. This can be done through the server matching manually-opened ticket information with mobile device ticket information, or done by an employee by combining the tickets using functionality built into the point of sale system. This functionality provides a seamless process for the end-user, regardless of who initiated the ticket (patron via mobile device, or wait staff via point of sale system). [00149] In an exemplary embodiment, the user checks-in at a venue via a mobile application on their mobile device, selecting that they already have a ticket open. The server passes the check-in information to the venue's POS system and creates a ticket. The server combines a previously opened ticket with the new mobile application created ticket. The user sees all previously ordered items, as well as future items reflected on the mobile application.

[00150] FIG. 6A is a flowchart 600 of an example embodiment of a process for identification verification according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, during the sign-up (or registration) process, the user enters basic information to complete the set-up. The entry of this information may be inputted on a mobile application or from a website of any computer device. The inputted information includes, but is not limited to, full name, date of birth, email, phone number, and payment information. The user will also be presented with the option to scan a photo ID using their smartphone's camera. Once they scan the ID, the server will verify that this is an authentic form of identification. Specific information will also be pulled from the ID, including date of birth. Because the server is able to validate the authenticity of the ID as well as verify the user's DOB, this information can be passed on to other entities, like venues (e.g., bars, restaurants, clubs, casinos, retail outlets), to ensure that patrons are of appropriate drinking age.

[00151] The system can display the patron's date of birth on the point-of-sale system directly visible to wait staff who will be serving the patrons. The system can also tie in to third party guest list applications to allow similar functionality and value at different entry points to the venue. The system's ability to identify a user's identification and utilize the information is not limited to verifying age, but could also be used to provide demographic information to third parties, combat credit card and payment fraud, expedite entry into ID required establishments, etc. [00152] In an exemplary embodiment, during the sign-up process in the mobile application, the user takes a photograph of their photo identification (drivers license, passport, etc.), by taking a picture using their mobile device. The photo ID is transmitted to a server for verification of authenticity. Information like name, date of birth, address, identification numbers and demographic information is stored from the ID. If the ID is deemed valid, it is associated in the data store with the user's other account information. The user checks-in on their mobile device using the mobile application at a venue, and a ticket is generated by the POS system for the user. If the user is over 21 years of age based on the information in their photo ID, the server labels the POS system ticket as "21+." If the user is under 21 years of age based on the information in their photo ID, the server labels the POS system ticket as "Under 21."

[00153] FIG. 6B is a user interface 602 of an example embodiment of allowing a user to snap a picture of the user's photo identification through a mobile application according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, the user may upload a photo to the mobile device and/or take a picture using the mobile device.

[00154] FIG. 6C is a user interface 604 of an example embodiment of allowing a user to implement a built in camera to photograph the user's photo identification according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure.

[00155] FIG. 6D is a user interface 606 of an example embodiment of showing age verification in the account information screen according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, this information may be stored in the user's profile information. [00156] FIG. 6E is a user interface 608 of an example embodiment of displaying age verification in the system according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, this information may be presented to the wait staff in a restaurant on a graphical user interface.

[00157] FIG. 7A is a flowchart 700 of an example embodiment of a process for checking in to a hotel system according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, the mobile payment infrastructure that is being used in the food and beverage space also allows for a seamless integration with hotel systems. A hotel guest can check-in via the mobile application to the hotel where they are currently located. This check- in information is transmitted via a server to the hotel's point of sale and reservation system. All charges that are added to the guest's tab, including but not limited to, room, room service, restaurant, bar, club, amenity, parking, salon, golf, and retail shops can be placed on the users tab and displayed on the mobile application. The mobile application would update in real time with all charges that are added to the guests account. When the guest is ready to leave the hotel, they can check-out via the mobile application, ending their stay, and closing the financial transaction using their stored payment data. This system is also applicable to events or banquets held in hotel or similar venues. Many times, a guest enters a hotel for a multi-day event and accrues many charges through their stay. The system allows event guests to monitor their charges and settle through the mobile application.

[00158] In an exemplary embodiment, the user checks-in at a hotel venue via a mobile application on their mobile device. The server passes the check-in information to the hotel system. The hotel system opens a ticket for the user and associates their payment information on the ticket. The server associates all hotel related charges (like room charges, room service, food and beverage service, spa, salon, parking, hotel gift shop, golf, etc.) to the users ticket. The user checks-out of the hotel via the mobile application. The hotel system closes payment for all charges associated with the user. The user received a confirmation of the check-out.

[00159] FIG. 7B is a flowchart 702 of an example embodiment of a process for checking in to a gas system according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, the system allows for other remote payments, such as gas stations. In many instances, a driver hands their payment information to an attendant to settle the transaction for both gasoline as well as other merchandise that they purchase at the station, such as beverages, retail items, service center items, car care products, etc. Instead, these transactions can be settled through the mobile application. The server connects to the point of sale terminal in the station to monitor the charges accrued while at the station and presents the charges to the driver in real time so they may settle the transaction electronically and efficiently.

[00160] In an exemplary embodiment, the user checks-in at a gas station via a mobile application on their mobile device. The server passes the check-in information to the station POS system. The server opens a ticket on the stations POS system and associates the users payment information with this ticket. The server associates all station related charges to the user's ticket. The station system closes payment for all charges associated with the user upon the transaction being completed. The user received a confirmation that the transaction has completed.

[00161] FIG. 7C is a flowchart 704 of an example embodiment of a process for checking in to a retail system according to the present disclosure. This embodiment may incorporate any aspects of other implementations as described in the disclosure. In some implementations, the process allows for functionality inside a retail environment. The shopper can check-in on the mobile application, validating their presence in a retail shop, and allow for transactions to process remotely from the traditional point of sale system. The server can monitor items that the shopper wishes to purchase through multiple interactions (scanning barcodes on the mobile application, transmitting using an NFC device, adding items on the point-of-sale system by a store employee, manually selecting the item on the mobile application, and other methods of entry.) When the shopper is ready to complete the transaction, they can select to close the transaction on the mobile device, sending a signal to the server, and completing the purchase.

[00162] In an exemplary embodiment, the user checks-in at a venue via a mobile application on their mobile device. The server passes the check-in information to the venue's POS system. The venue's POS system opens a ticket for the user and associates user payment information. Server associates all venue related charges to the user's ticket. User verifies the accuracy of charges and confirms payment on the mobile application. The venue system closes payment for all charges associated with the user. User receives confirmation of successful payment.

[00163] In some implementations, the system also allows for use inside of a casino environment. Many of the interactions inside of a casino revolve around remotely settled transactions, such as lodging, dining, nightlife, poolside food and beverage, gambling, and so on. When a casino guest checks-in via the mobile application, the server initiates a tab on the casino's central server and point of sale system. As the guest accrues charges inside of the casino, the guest is able to monitor and audit these charges in real-time. When they're ready to close out their transaction, check-out, or settle-up, they can perform the transaction via the mobile application. The server will communicate with the casino's point of sale system to settle the transaction and communicate the verification to the user.

[00164] The system may also allows for settling multi-party transactions for ease of auditing. One of these scenarios is common in event planning. A user frequently has to pay multiple parties for one event, creating a logistical challenge in account for expenses. In some implementations, the system may be integrated with expense software (e.g., Concur). The system allows for the user to settle transactions through the mobile device, communicating with the server, with many different parties. These expenses can all be tagged with expense codes (food/beverage, travel, etc.), account codes (personal, work, etc.) and expensed automatically through the platform. The server will aggregate all of the transactions and submit the expenses for reimbursement.

[00165] In some implementations, the system provides the ability to track expenses and make payments through the app in scenarios where you have many parties involved. For example, planning a wedding. Pay all of the different vendors through the app and organize an event based spending report automatically.

[00166] In some implementations, the system may be implemented in casinos. In an exemplary embodiment, sports book betting, actually making bets and keeping tabs of bets may be implemented using this system. A user can do a direct ACH from bank account for betting to the casino (all age verification, ID, etc. can accomplished using a system such as Experian). In some implementations, users of this system can use their mobile application at a gambling table rather than use chips or post actual cash.

[00167] In some implementations, the system may provide the ability to check-in to a previously booked flight though the mobile application, and have all of the charge information available, in addition to the expensing capabilities and other features present in the mobile application. The airport system also allows for viewing charges accrued at businesses located inside of the airport, including but not limited to food and beverage services, retail shops, and quick service restaurants.

[00168] As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or computer program product. Accordingly, aspects of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system." Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

[00169] Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus or device.

[00170] A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate or transport a program for use by or in connection with an instruction execution system, apparatus or device.

[00171] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[00172] Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. Other types of programming languages include HTML5, Flash and other similar languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[00173] Aspects of the present disclosure are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[00174] These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[00175] The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[00176] The flowchart and block diagrams in the Figures illustrate the architecture, functionality and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block might occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[00177] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

[00178] The flow diagrams depicted herein are just one example. There may be many variations to this diagram or the steps (or operations) described therein without departing from the spirit of the disclosure. For instance, the steps may be performed in a differing order or steps may be added, deleted or modified. All of these variations are considered a part of the claimed disclosure.

[00179] While the preferred embodiment to the disclosure had been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the disclosure first described.

[00180] Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.

Claims

CLAIMS What is claimed is:

1. A method comprising:

receiving, by a host server, check-in data regarding the presence of a mobile computing device of a first user in the business establishment;

querying, by the host server, the client server for a reservation associated with the first user;

receiving, by the host server, transmittal of a reservation for the first user in a business establishment from a client server of the business establishment, the reservation comprising a table selection indicating a table identification and a time and date of dining;

upon receiving the transmittal of the reservation, associating, by the host server, the mobile computing device of the first user with the reservation;

transmitting, by the host server, to the mobile computing device of the first user, the table identification based on the reservation associated with the first user;

transmitting, by the host server, to the point of sale (POS) system, the check-in data and payment account data associated with the first user;

requesting, by the host server, generation of a ticket on the POS system based on the reservation associated with the first user; and

associating, by the host server, in a database the ticket corresponding to the reservation, the payment account data, and an order placed by the first user.

2. The method according to claim 1, further comprising:

transmitting, by the host server, a bill including the one or more orders to the first user.

3. The method according to claim 2, further comprising:

receiving, by the host server, at least partial payment of the bill using the payment account data.

4. The method of claim 1, wherein table selection is based on displaying, by the host server on the POS system, a list of tables present in the business establishment to the business entity and allowing the business entity to select a particular table.

5. The method of claim 1, wherein table selection is based on displaying, by the host server on the POS system, a list of tables present in the business establishment to the first user and allowing the first user to select a particular table or tab.

6. The method according to claim 1, wherein the check-in data is based upon GPS on the mobile phone of the first user.

7. The method according to claim 1, further comprising:

transmitting, from the host server to the POS system, a location of the first user based upon check-in data received from the mobile phone of the first user.

8. The method according to claim 1, further comprising:

communicating, by the host server via a social networking service, a location of the first user based upon check-in data.

9. A method comprising: receiving, by a host server, check-in data regarding the presence of a mobile computing device of a first user in a business establishment;

transmitting, by the host server to a point of sale (POS) system, the check-in data and payment account data associated with the first user;

receiving, by the host server from the POS system, a record of a first order placed by the first user prior to receiving the check-in data regarding the presence of the mobile computing device of the first user in the business establishment;

requesting, by the host server, generation of a ticket corresponding to the payment account data and the record of the first order placed by the first user prior to receiving the check- in data of the first user;

receiving, by the host server from the POS system, a record of a second order placed by the first user;

linking, by the host server, the record of the second order placed by the first user to the ticket corresponding to the payment account data and the record of the first order placed by the first user;

transmitting, by the host server to the POS system, a bill including the first and second order of the first user; and

receiving, by the host server from the POS system, at least partial payment of the bill using the payment account data.

10. The method according to claim 9, further comprising:

receiving, by the host server and from the mobile computing device of the first user, an identification of a second user in the establishment; and

associating, by the host server, the second user with the bill of the first user.

11. The method according to claim 10, further comprising:

receiving, by the host server, a request from the mobile computing device of the second user for at least partial payment of the bill using payment account data associated with the second user.

12. The method according to claim 10, further comprising:

transmitting, by the host server, the bill for display on a mobile computing device of the second user.

13. A method comprising:

querying, by the host server, user profile information associated with the first user, the user profile information containing payment information related to the first user;

receiving, by the host server, an identification, from the mobile computing device of the first user, of a presence of a second user in the business establishment;

opening, by the host server, on a point of sale (POS) system a ticket based on an order placed by the first user and the second user;

transmitting, by the host server to the POS system, a bill for display on the mobile computing device of the first user and a mobile computing device of the second user;

allocating, by the host server, the bill among the first user and the second user based on input from the first user; and

receiving, by the host server, at least partial payment for the bill according to the validated payment information in response to the host server authorizing the at least partial payment from the mobile computing device of first user and the mobile computing device of the second user.

14. The method of claim 13, wherein the identification of the second user is based on the first user tagging the second user.

15. The method of claim 14, wherein the second user accepts the tag from the first user.

16. The method of claim 14, wherein the tag is sent through a short messaging service message, multimedia messaging service message, or email.

17. The method according to claim 13, wherein identification of the second user is based on check-in data regarding the presence of the mobile computing device of the second user in the business establishment.

18. The method according to claim 13, further comprising:

transmitting, by the host server, the bill for display on the mobile computing device of the second user.

19. The method of claim 13, wherein the allocating the bill comprises an itemized split corresponding to items the first user ordered and items the second user ordered.

20. The method of claim 13, wherein the allocating the bill comprises randomly charging the first user or the second user for the bill.