AU2017101311A4 - Frameworks and methodologies configured to enable mobile device payments via unique location-defining codes - Google Patents

Abstract

Abstract The present invention relates, in various embodiments, to fields including mobile device payments, wherein a user of a mobile device (such as a smartphone) is enabled to provide payment for goods and/or services by way of operating that device. 101 110 ,140 User Data Location Code Third Party Payment Display Screen Database Systems Payment Management Modules POS Interaction Modules o Payment Management Exemplary Mobile Device, Server / \ / \ 151 // \\ / \m'~ / age Capture Zone Human 131 130 Readable Identifier Region Mobile Payment Specific Standard POS Hardware Hardware/Software 0 and Software Components Components

Description

FRAMEWORKS AND METHODOLOGIES CONFIGURED TO ENABLE MOBILE DEVICE PAYMENTS VIA UNIQUE LOCATION-DEFINING CODES

FIELD OF THE INVENTION

[0001] The present invention relates to frameworks and methodologies configured to enable mobile device payments at point of sale.

BACKGROUND

[0002] Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field.

[0003] A range of payment techniques for POS payments are known. Over time, these have evolved from cash payments, to magnetic strip cards, to NFC cards, and more recently to mobile device payments. However, there remains scope for improvement in terms of facilitating an optimal consumer experience.

SUMMARY OF THE INVENTION

[0004] It is an object of the present invention to overcome or ameliorate at least one of the disadvantages of the prior art, or to provide a useful alternative.

[0005] One embodiment provides a system configured to enable mobile device payments, the system including: [0006] a user management module, wherein the user management module is configured to receive input representative of data transmitted from a user device thereby to update one or more records in a user records database, wherein for a given user the user records database contains data representative of: [0007] (i) a user token, which is configured to be transmitted by a mobile device associated with the user, wherein the user token allows unique identification of the user; and [0008] (ii) user payment data, wherein the user payment data is configured to enable automated processing of a payment transaction via a user-selected electronic payment system; [0009] a user check-in handling module, wherein the user check-in handling module is configured to: [0010] (i) receive, from a mobile device, data representative of a check-in event, wherein the data representative of the check-in event includes a user token and a vendor location tag; [0011] (ii) identify a Host POS environment associated with the vendor location tag; and [0012] (iii) perform a defined action based on data associated with a Host POS environment; [0013] a payment processing module, wherein the payment processing module is configured to, in response to a payment trigger, cause processing of a payment transaction, wherein causing processing of the payment transaction includes, in respect of a given check-in event: [0014] (i) identifying a payment amount associated with the check-in event, wherein the payment amount has a quantum defined by the Host POS environment associated with the vendor location tag; [0015] (ii) identifying a user based on the user token for the check-in event; and [0016] (iii) perform a payment process in respect of the payment amount by way of the user payment data for the identified user, wherein the payment process is executed based on a protocol defined for the user-selected electronic payment system for that user payment data.

[0017] One embodiment provides a mobile device configured to perform a method including: [0018] capturing, via an image capture device, data representative of a coded pattern; [0019] processing the coded pattern thereby to derive a vendor location tag; [0020] transmitting the vendor location tag to a defined server; [0021] receiving, from the server, data that enables viewing at the mobile device of data representative of a set of transaction items, the transaction items being derived from a POS environment remote of the mobile device and remote of the server, wherein the data representative of the transaction items is provided via a user interface of the mobile device that enables a user to select one or more of the transaction items for payment; and [0022] transmitting to the server data identifying the one or more of the transaction items selected for payment, thereby to trigger a payment process via the server.

[0023] One embodiment provides a computer program product for performing a method as described herein.

[0024] One embodiment provides a non-transitory carrier medium for carrying computer executable code that, when executed on a processor, causes the processor to perform a method as described herein.

[0025] One embodiment provides a system configured for performing a method as described herein.

[0026] Reference throughout this specification to “one embodiment”, “some embodiments” or “an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment”, “in some embodiments” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

[0027] As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0028] In the claims below and the description herein, any one of the terms comprising, comprised of or which comprises is an open term that means including at least the elements/features that follow, but not excluding others. Thus, the term comprising, when used in the claims, should not be interpreted as being limitative to the means or elements or steps listed thereafter. For example, the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B. Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.

[0029] As used herein, the term “exemplary” is used in the sense of providing examples, as opposed to indicating quality. That is, an “exemplary embodiment” is an embodiment provided as an example, as opposed to necessarily being an embodiment of exemplary quality.

BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which: [0031] FIG. 1A illustrates a framework according to one embodiment.

[0032] FIG. 1B illustrates a framework according to one embodiment.

[0033] FIG. 1C illustrates a framework according to one embodiment.

[0034] FIG. 2A to FIG. 2D illustrate methods according to embodiments.

[0035] FIG. 3 illustrates a client-server framework leveraged by some embodiments.

[0036] FIG. 4A and 4B illustrate examples of user interface displays according to embodiments.

[0037] FIG. 5 illustrates an example annular coded pattern according to one embodiment.

DETAILED DESCRIPTION

[0038] The present invention relates, in various embodiments, to fields including mobile device payments, wherein a user of a mobile device (such as a smartphone) is enabled to provide payment for goods and/or services by way of operating that device.

Overview [0039] Mobile device payments are becoming an increasingly popular means of performing transactions. Examples include the use of NFC technology to enable release of credit card information from a mobile device (in some cases subject to biometric authentication), and the implementation of various frameworks that deliver invoice details to mobile devices (for example technology whereby a unique QR code causes a mobile device to access a web-page uniquely defined for a particular payment transaction). Any given existing solution has its downsides, for example in terms of banking institution compatibility, hardware requirements, and/or user experience.

[0040] The present inventor has developed a technological framework that enables efficient and effective mobile device payments using coded patterns. At a very high level, a coded pattern is captured by a mobile device and data derived therefrom (referred to herein as a “vendor location tag”) communicated to a predefined server, thereby to provide a “check-in event” for that mobile device. In this manner, the server knows the current location of the mobile device. The server is also configured to receive transaction information from a plurality of Host POS environments. By performing a matching process between Host POS environment data and the vendor location tag, the server is able to associate a user account associated with the mobile device with a particular transaction, and trigger processing of a payment in respect of that transaction. The server is able to act as a payment intermediary, and cause the payment to be processed via third party servers (for example credit/debit card facilities, PayPal, and the like).

[0041] More advanced aspects of the technology are also discussed below, for example: (i) hardware at a Host POS environment is provided with data about users who have checked-in, thereby to enable manual association between users and payment amounts; and (ii) technology whereby transaction data from a Host POS environment is able to be displayed at a mobile device, thereby to enable advanced user-controlled payment selections (for instance to allow split bills in a restaurant).

Example System [0042] One embodiment provides a system configured to enable mobile device payments. The system is delivered via one or a plurality of networked computer terminals (server devices). These each include one or more microprocessors that are configured execute computer executable code (software instructions) stored on carrier media (for example memory modules). The execution of such software instructions enables the provision of functionality, for example by enabling performance of method steps described herein.

[0043] The system includes a user management module, which includes a set of software services that enable functionalities including user registration and user account management. The user management module is accessible to users via the Internet, for example via website interfaces and/or mobile device app interfaces. In this regard, the user management module is configured to receive input representative of data transmitted from a user device thereby to update one or more records in a user records database. In preferred embodiments, for a given user the user records database contains data representative of: (i) A user token. The user token is configured to be transmitted by a mobile device associated with the user, and allows unique identification of the user (i.e. a user account for the user defined by a set of user records). The user token is in some cases stored in an encrypted manner at the mobile device. In some embodiments the user token include attributes that are defined based upon unique hardware and/or software characteristics of the user device. (ii) User payment data. The user payment data is configured to enable automated processing of a payment transaction via a user-selected electronic payment system. That is, the user payment data is configured to enable automated processing of a payment transaction via a user-selected electronic payment system, wherein there is a plurality of available electronic payment systems, and wherein one or more of the available electronic payment systems are each associated with a respective online payment portal. For instance, the user-selected electronic payment system may include a third party service such as PayPal, in which case the user payment data provides user login/authentication information necessary to enable a server to trigger and automatically perform a payment transaction request on behalf of the user via PayPal. The user-selected electronic payment system may also include credit card details, stored value account details, and the like. Preferably, each user is able to designate a default payment system that will be used for transactions.

[0044] The system also includes a user check-in handling module, wherein the user check-in handling module is configured to: (i) Receive, from a mobile device, data representative of a check-in event. The data representative of the check-in event includes both a user token and a vendor location tag. The user token is discussed above. The vendor location tag is data derived from reading of location-specific coded information via the mobile device. In embodiments considered herein, the coded information is provided via an optically readable patterned code. A preferred form of patterned code is a patterned code that is configured to graphically surround (in whole or in part) a human recognisable artefact (such as a logo, table number, image, or the like). A preferred embodiment makes use of an annular coded pattern. The patterned code is read by a mobile app, which when launched accesses an imaging device (e.g. camera) provided by the mobile device, and executes optical recognition algorithms that are configured to recognise and read a predetermined form of coded patter in the mobile device imaging device’s field of view. (ii) Identify a Host POS environment associated with the vendor location tag. Each vendor location tag is associated with a unique Host POS environment, for example having been custom generated for that purpose. For instance, in some cases a vendor tag is associated with a particular POS terminal. In some embodiments there are multiple vendor locations associated with unique sublocations, for example individual tables in a restaurant, which are each in practice related to a particular Host POS environment. (iii) Perform a defined action based on data associated with a Host POS environment. The nature of this action varies between embodiments, and/or between individual instances, and examples are discussed below. In general terms, the action results, directly or indirectly, with a payment trigger for a payment of a particular payment amount via the payment details of a particular user account. The various defined actions relate to different processes leading to that point.

[0045] The term “Host POS environment” is used herein to define a collection of hardware and software components that provide both point-of-sale functions and functionality to interact with the system. There are a number of ways in which this is implemented, depending primarily on the nature of existing POS equipment. For example, in some cases an additional hardware device (such as a tablet device) is provided to operate in conjunction with existing POS equipment, thereby to provide integration between the existing POS equipment and the mobile device payment system. Alternatively, in some cases POS hardware is modified to execute modified software to provide such integration. In further cases POS hardware is configured from the outset with software adapted for mobile device payment system integration. Furthermore, a Host POS environment may include a single POS terminal, a single POS terminal in a vendor location with multiple POS terminals, or a networked system of multiple POS terminals.

[0046] The system also includes a payment processing module. The payment processing module is configured to, in response to a payment trigger, cause processing of a payment transaction. The processing of the payment transaction includes, in respect of a given check-in event: (i) Identifying a payment amount associated with the check-in event. This payment amount has a quantum defined by the Host POS environment associated with the vendor location tag. In some cases this is a transaction total, in other cases it is a total for a subset of transaction items selected by the mobile device user, as discussed further below. (ii) Identifying a user based on the user token for the check-in event. Each payment amount defined by a given Host POS environment is tied to a user account via a received user token for a check in event based on a vendor location tag associated with the Host POS environment. (iii) Perform a payment process in respect of the payment amount by way of the user payment data for the identified user. The payment process is executed based on a protocol defined for the user-selected electronic payment system for that user payment data. This may be a payment to a party associated with the POS host system, or a payment to a payment intermediary associated with the system (with a subsequent funds transfer being made to the party associated with the POS host system, optionally with a service fee/margin extracted).

[0047] In the case that the triggered payment process completes successfully (i.e. the payment processing module receives confirmation from the payment system that the payment has completed), a notification is provided representative of successful payment to the Host POS environment. This allows, for example, the Host POS environment to confirm that payment was successful, and close an associated transaction.

[0048] Optionally, in the case that the triggered payment process completes successfully, a notification is provided to the mobile device. In some embodiments delivery of such notifications is controlled via user settings made available in the mobile device app.

[0049] Examples of the “defined action” performed by the user check-in handling module are described below.

[0050] In some cases the defined action based on data associated with a Host POS environment includes: • Identifying payment request data including a payment amount received from the Host POS environment, where the payment request occurs proximal the receiving of data representative of the check-in event. For example, in a practical implementation, a POS terminal user selects a “mobile payment” option, which triggers communication of the payment amount to the mobile device payment server. The user then scans the coded pattern (which is provided on or adjacent the physical payment location), and the mobile payment system server automatically identifies that the resulting check-in relates to the communicated payment amount. The system then associates the payment amount with the check-in event, and causes a payment trigger for the payment processing module. • Providing, to the Host POS environment, user identifying data associated with the user token, and in doing so causing a user interface provided by the Host POS environment is configured to enable user association of the user identifying data with a payment amount (for example a user interface on a tablet deviceprovided for the purpose of mobile device payments). This allows a POS operator to associated the user with a payment amount (for example the user’s name is shown on an icon, and the POS operator selects that icon). The system then receives, from the Host POS environment, data representative of the payment amount and the association of the user identifying data with a payment amount, associates the payment amount with the check-in event, and causes a payment trigger for the payment processing module. This process is particularly useful where a user (“Tony", for this example) scans the code and triggers a check-in prior to a POS operator entering a transaction into a POS terminal. For example, a user verbally places an order for a coffee and scans the code. The coffee is then made, and the transaction entered into a POS terminal (potentially by different workers). The POS operator sees Tony’s name on the tablet, and associates Tony with the payment amount, thereby to allow the payment to proceed. • In the case of a payment in a restaurant, bar, or other environment where multiple items are associated with a particular table or location, defining a new “multi item transaction record” at the server side. The multi action transaction record is associated with a sub-location known to the Host POS environment, and the vendor location tag is unique to the sub-location (for example a physical sub location such as a particular table, a virtual sub location such as a tab name, and so on). The method then includes providing, to the Host POS environment, data representative of the multi item transaction record, and via software executing at the Host POS environment, the Host POS environment is configured to upload to the multi item transaction record data representative of transaction items. This data representative of transaction items includes respective payment amounts for each of the transaction items. Then, data is provided to the mobile device to enable viewing at the mobile device of data representative of the transaction items. The data representative of the transaction items is provided via a user interface that enables a user to select one or more of the transaction items for payment. The mobile payment system then receives, from the mobile device, data representative of the one or more of the transaction items selected for payment, associates the payment amounts for the one or more of the transaction items selected for payment with the check-in event; and causes a payment trigger for the payment processing module. As illustrated further below, this approach is especially useful for split bills, as multiple users can check-in via the same vendor location tab, view the same items, and select which they will pay.

[0051] In some cases two or all of the above are available as options for defined actions.

[0052] As noted, the data representative of the vendor location tag received from the mobile device is generated by the mobile device based on identification and analysis of a coded pattern captured by an image capture device of the mobile device. In embodiments described below, the coded pattern includes a coded pattern contained in an annular space, and the annular space surrounds a human-recognizable identifier (such as a vendor business logo and/or table number and/or other graphical/textual information). In other embodiments alternate coded patterns are used, including other coded patterns that surround a human-recognizable identifier (partially or wholly). This is helpful from a human user perspective, as a user is able to visually recognise and understand the relevance of a coded pattern that is being scanned by way of the human recognisable identifier. In practice, the user “feels” like that is what they are scanning, whilst from a technological perspective it is the surrounding code that is used.

Example Frameworks [0053] FIG. 1A to 1C illustrate example frameworks according to embodiments. Corresponding features are designated by corresponding reference numerals, and described initially by reference to FIG. 1 A.

[0054] As shown in FIG. 1A, an example mobile device 100 includes a display screen 101. This display screen 101 allows for graphical rendering of mobile app data for a mobile app executing via one or more microprocessors of the mobile device. The mobile app of note is a mobile payments app. The mobile payments app is configured to, following launch, configured an image capture device (preferably a rear-facing camera) of the mobile device to scan for a predefined form of patterned code, in this case being a code sharing attributes with code 150. The app is configured to read code 150, and communicate a vendor location tag derived therefrom to a payment management server 110, along with a “user token” which uniquely identifies a user associated with the mobile device (in the context of a repository of user data managed by server 110).

[0055] Server 110 maintains user data, which for a plurality of registered users includes user tokens, and payment information as described above. Server 110 also maintains a location code database, which enables association of vendor location tags with Host POS environments (and optionally sub-locations thereof), payment management modules, which are configured to associate POS environment defined payment amounts with particular users (and trigger payment processes via third party payment systems 140) and POS interaction modules which are configured to enable exchange of data between the server and a plurality of Host POS environments.

[0056] In the example of FIG. 1A, a Host POS environment includes standard POS hardware and software components 130, and mobile payment specific hardware/software 131. For example, item 131 may include a tablet device which is coupled to POS hardware 130, receives a request for payment from POS hardware 130, and processes that payment via server 110. In the example of FIG. 1B, items 130 and 131 are combined, for example via the application of a software patch and/or additional software to a given instance of existing POS hardware/software, thereby to provide functionality to handle mobile device payments via server 110. In the example of FIG. 1C, POS hardware/software is inherency adapted for interaction with server 110 (yet may still provide various other conventional payment options).

Example Methods [0057] FIG. 2A illustrates a method according to one embodiment, including a registration phase and a payment phase.

[0058] Blocks 201 and 202 of the registration phase represent a user providing registration data, and the installation of a mobile payments mobile app and user token at the user’s mobile device. It should be appreciated that the steps may be varied in order (for example a user first installs the mobile app, then provides registration data, and then downloads a user token). In any case, the registration phase configures a mobile device payment server to recognise a user based on a user token uploaded by a mobile device, and know how to automatically process electronic payments for that user (for example via a third party electronic payment system having an online portal).

[0059] In relation to the payment phase, the user launches the mobile payments smartphone app at 203, and reads an annular code such as code 150 of FIG. 1A at 204. The annular code ID (vendor location tag) is transmitted to a defined server device at 205. The server then is able to identify a unique Host POS environment at 206. The server then provides user data (for example a user name or nickname) to the Host POS environment at 207, enabling a user interface at the Host POS environment to be operated thereby to associate a payment amount with the user at 208. Data representative of that association (e.g. the user data and payment amount) is transmitted to the server at 209, and the server processes the payment at 210 based on the user’s selected payment system. Confirmation signals are provided to the Host POS environment and mobile device at 211.

[0060] In the example of FIG. 2B, a POS terminal in a POS environment is operated to define a payment amount for a transaction at 221, and a “mobile payment” checkout option is selected at 222. The POS environment transmits the payment amount to a server at 223, along with data identifying the POS environment (for example a terminal ID). At 224 the server correlates a time-proximal check in event for a vendor tag associated with the POS environment with the payment amount, and triggers payment processing at 225. Confirmation signals are provided at 226.

[0061] In the example of FIG. 2C, a mobile device payment server receives an annular code ID (vendor location tag) and user token from a mobile device at 231. The server then, based on the vendor location tag, identifies a host POS environment at 232, and transmits user data to that host POS environment at 233. The user data is then displayed at the host post environment at 234. For example, this may occur via a user interface such as that shown in FIG. 4A, which shows details of current checked-in customers and details of current transactions, and allows association of customers and transactions (as per block 235). That association results in transmission of the payment amount and user data to the server at 236, triggering payment processing at 237, and conformation signals at 238 (of course, assuming payment processing is successful).

[0062] In the example of FIG. 2D, the server receives an annular code ID (vendor location tag) and user token from a mobile device at 241. The server then, based on the vendor location tag, identifies a host POS environment at 242, and transmits user data to that host POS environment at 243. User data is made available for display at the host POS environment at 244. In this case, the POS environment transmits transaction information for a sub-location associated with a unique vendor location tag to the server at 245 (for example individual items applied to a bill associated with the sub-location, which may be for instance a table in a restaurant). The server transmits those to the mobile device at 246, allowing a user of the mobile device to view those in a user interface and select one or more individual items for payment at 247. The server then processes payments for those items at 248, and provides confirmation signals at 249. Then the host POS environment shows updated information verifying which individual items have been paid, and which remain outstanding.

[0063] FIG. 4B illustrates example user interface displays related to the method of FIG. 2D. In this example, we assume that multiple user devices have scanned a common coded patterns representative of a vendor location tag at Table X in a venue. Items added to the Table X account via POS hardware appear in two forms places: in a user interface of a POS mobile device payment display device, and on user interfaces of the relevant mobile devices (with the device of “Person A” being shown). Via the device of Person A, a user (presumably Person A) is able to review the individual items, see for which items they have paid, select items for which they wish to pay, and see which items have already been paid for by others (for example “Person C”). The POS mobile device payment display device shows which persons have paid for which items, and which remain outstanding. It will be appreciated that this presents a particularly advantageous technological arrangement for bill splitting via mobile device payments.

Comments Regarding Implementation [0064] Although examples provided above focus on retail environments, the concept of a host POS system should be read more broadly. For example, the technology described above (using reading of local coded patterns thereby to cause a location-known check-in event, but which to cause automated payments) is applicable in situations including (but not limited to) the following: • Physical retail, where there is a physical POS terminal. • Online retail, where a coded pattern is rendered on a computer screen and the POS environment is a remote networked server device. • Transport environments, where a code is used for tap-on/tap-off identification, thereby to trigger payment for transportation charges. In some embodiments the payment management server interacts with a host POS environment in the form of a transportation payment management server, and the payment amount is based upon a pair of check-in events for the user, which collectively define a trip having an associated payment amount. Determination of that cost may be performed by the payment management server (e.g. that server has access to rules which enable determination of a trip cost based on check-in events) or the transportation payment management server. In some embodiments upon successful payment a signal is provided to cause predefined operation of a local access control device, such as a turnstile or approval light. • Transactions in the form of validating entry into a venue based on a pre-existing ticket (e.g. a code is scanned, and valid ticket ownership is determined based on a resulting check-in event). • Providing ID details (e.g. government or other personal details are communicated form a secure location to a local terminal in response to a code-triggered mobile device check-in event).

[0065] These are examples only, and persons skilled in the art will appreciate how technology disclosed by reference to examples further above is applied in these and other situations.

Example Client-Server Framework [0066] In overview, a web server 302 provides a web interface 303. This web interface is accessed by the parties by way of client terminals 304. In overview, users access interface 303 over the Internet by way of client terminals 304, which in various embodiments include the likes of personal computers, PDAs, cellular telephones, gaming consoles, and other Internet enabled devices.

[0067] Server 303 includes a processor 305 coupled to a memory module 306 and a communications interface 307, such as an Internet connection, modem, Ethernet port, wireless network card, serial port, or the like. In other embodiments distributed resources are used. For example, in one embodiment server 302 includes a plurality of distributed servers having respective storage, processing and communications resources. Memory module 306 includes software instructions 308, which are executable on processor 305.

[0068] Server 302 is coupled to a database 310. In further embodiments the database leverages memory module 306.

[0069] In some embodiments web interface 303 includes a website. The term “website” should be read broadly to cover substantially any source of information accessible over the Internet or another communications network (such as WAN, LAN or WLAN) via a browser application running on a client terminal. In some embodiments, a website is a source of information made available by a server and accessible over the Internet by a web-browser application running on a client terminal. The web-browser application downloads code, such as HTML code, from the server. This code is executable through the web-browser on the client terminal for providing a graphical and often interactive representation of the website on the client terminal. By way of the web-browser application, a user of the client terminal is able to navigate between and throughout various web pages provided by the website, and access various functionalities that are provided.

[0070] Although some embodiments make use of a website/browser-based implementation, in other embodiments proprietary software methods are implemented as an alternative. For example, in such embodiments client terminals 304 maintain software instructions for a computer program product that essentially provides access to a portal via which framework 100 is accessed (for instance via an iPhone app or the like).

[0071] In general terms, each terminal 304 includes a processor 311 coupled to a memory module 313 and a communications interface 312, such as an internet connection, modem, Ethernet port, serial port, or the like. Memory module 313 includes software instructions 314, which are executable on processor 311. These software instructions allow terminal 304 to execute a software application, such as a proprietary application or web browser application and thereby render on-screen a user interface and allow communication with server 302. This user interface allows for the creation, viewing and administration of profiles, access to the internal communications interface, and various other functionalities.

[0072] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as "processing," "computing," "calculating," “determining”, analyzing” or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.

[0073] In a similar manner, the term "processor" may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A “computer” or a “computing machine” or a "computing platform" may include one or more processors.

[0074] The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM. A bus subsystem may be included for communicating between the components. The processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth. Input devices may also include audio/video input devices, and/or devices configured to derive information relating to characteristics/attributes of a human user. The term memory unit as used herein, if clear from the context and unless explicitly stated otherwise, also encompasses a storage system such as a disk drive unit. The processing system in some configurations may include a sound output device, and a network interface device. The memory subsystem thus includes a computer-readable carrier medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein. Note that when the method includes several elements, e.g., several steps, no ordering of such elements is implied, unless specifically stated. The software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system. Thus, the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code.

[0075] Furthermore, a computer-readable carrier medium may form, or be included in a computer program product.

[0076] In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a user machine in server-user network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

[0077] Note that while diagrams only show a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

[0078] Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that is for execution on one or more processors, e.g., one or more processors that are part of web server arrangement. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium, e.g., a computer program product. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.

[0079] The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an exemplary embodiment to be a single medium, the term "carrier medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "carrier medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks. Volatile media includes dynamic memory, such as main memory. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media also may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. For example, the term "carrier medium" shall accordingly be taken to include, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media; a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that, when executed, implement a method; and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.

[0080] It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.

[0081] It should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, FIG., or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

[0082] Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[0083] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a computer system or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

[0084] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

[0085] Similarly, it is to be noticed that the term coupled, when used in the claims, should not be interpreted as being limited to direct connections only. The terms "coupled" and "connected," along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Thus, the scope of the expression a device A coupled to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. "Coupled" may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.

[0086] Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as falling within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

Claims (5)

1. CLAIMS:

   1. A system configured to enable mobile device payments, the system including: a user management module, wherein the user management module is configured to receive input representative of data transmitted from a user device thereby to update one or more records in a user records database, wherein for a given user the user records database contains data representative of: (i) a user token, which is configured to be transmitted by a mobile device associated with the user, wherein the user token allows unique identification of the user; and (ii) user payment data, wherein the user payment data is configured to enable automated processing of a payment transaction via a user-selected electronic payment system; a user check-in handling module, wherein the user check-in handling module is configured to: (i) receive, from a mobile device, data representative of a check-in event, wherein the data representative of the check-in event includes a user token and a vendor location tag; (ii) identify a Host POS environment associated with the vendor location tag; and (iii) perform a defined action based on data associated with a Host POS environment; a payment processing module, wherein the payment processing module is configured to, in response to a payment trigger, cause processing of a payment transaction, wherein causing processing of the payment transaction includes, in respect of a given check-in event: (i) identifying a payment amount associated with the check-in event, wherein the payment amount has a quantum defined by the Host POS environment associated with the vendor location tag; (ii) identifying a user based on the user token for the check-in event; and (iii) perform a payment process in respect of the payment amount by way of the user payment data for the identified user, wherein the payment process is executed based on a protocol defined for the user-selected electronic payment system for that user payment data.
2. 2. A system according to claim 1 wherein performing a defined action based on data associated with a Host POS environment includes: identifying payment request data including a payment amount received from the Host POS environment, wherein receipt of the payment request occurs proximal the receiving of data representative of the check-in event; associating the payment amount with the check-in event; and causing a payment trigger for the payment processing module.
3. 3. A system according to any preceding claim wherein performing a defined action based on data associated with a Host POS environment includes: providing, to the Host POS environment, user identifying data associated with the user token, wherein a user interface provided by the Host POS environment is configured to enable user association of the user identifying data with a payment amount; receiving, from the Host POS environment, data representative of the payment amount and the association of the user identifying data with a payment amount; associating the payment amount with the check-in event; and causing a payment trigger for the payment processing module.
4. 4. A system according to any preceding claim wherein performing a defined action based on data associated with a Host POS environment includes, based on a set of rules, selecting a defined action from the following set of available defined actions: identifying payment request data including a payment amount received from the Host POS environment, wherein receipt of the payment request occurs proximal the receiving of data representative of the check-in event; associating the payment amount with the check-in event; and causing a payment trigger for the payment processing module; providing, to the Host POS environment, user identifying data associated with the user token, wherein a user interface provided by the Host POS environment is configured to enable user association of the user identifying data with a payment amount; receiving, from the Host POS environment, data representative of the payment amount and the association of the user identifying data with a payment amount; associating the payment amount with the check-in event; and causing a payment trigger for the payment processing module; and defining a new multi item transaction record; providing, to the Host POS environment, data representative of the multi item transaction record, wherein the Host POS environment is configured to upload to the multi item transaction record data representative of transaction items, wherein the data representative of transaction items includes respective payment amounts for each of the transaction items; providing, to the mobile device, data that enables viewing at the mobile device of data representative of the transaction items, wherein the data representative of the transaction items is provided via a user interface that enables a user to select one or more of the transaction items for payment; receiving, from the mobile device, data representative of the one or more of the transaction items selected for payment; associating the payment amounts for the one or more of the transaction items selected for payment with the check-in event; and causing a payment trigger for the payment processing module.
5. 5. A mobile device configured to perform a method including: capturing, via an image capture device, data representative of a coded pattern; processing the coded pattern thereby to derive a vendor location tag; transmitting the vendor location tag to a defined server; receiving, from the server, data that enables viewing at the mobile device of data representative of a set of transaction items, the transaction items being derived from a POS environment remote of the mobile device and remote of the server, wherein the data representative of the transaction items is provided via a user interface of the mobile device that enables a user to select one or more of the transaction items for payment; and transmitting to the server data identifying the one or more of the transaction items selected for payment, thereby to trigger a payment process via the server.