Direct settlement for hands-free transactions

Abstract

The present disclosure relates to direct settlement of hands-free transactions. Hands-free transactions are processed by utilizing an account management system to authorize the transaction and provide payment account information to a payment processing system, while allowing transaction settlement to occur between the payment processing system and the merchant. After verifying the user's account, the POS device generates a payment authorization request based on the user verification and other transaction information. The POS device sends the payment authorization request to the account management system, and the account management system identifies the user's payment data. The account management system receives the authorization from the payment processing system and transmits the payment authorization to the merchant. The merchant salesperson completes the transaction with the user by providing the product or service being purchased. The payment processing system and the merchant system then settle the transaction without involving the account management system.

Description

[0001] Description of the case

[0002] This application is a divisional application of Chinese invention patent application No. 201780011540.1, filed on March 1, 2017. Technical Field

[0003] The present disclosure relates to improving user convenience and security, particularly in hands-free transactions, by utilizing an account management system to authorize transactions and provide payment account information to a payment processing system while allowing transaction settlement to occur between the payment processing system and a provider computing system. Background Art

[0004] When a customer conducts a transaction at a merchant location, many methods of conducting the transaction are available. The customer can use many different instruments to conduct the transaction, such as gift cards, debit cards, credit cards, stored-value cards, and other cards or accounts. The user account identifier and other data represented by the card can be communicated to the merchant system via a magnetic stripe, near-field communication technology involving the user's computing device, or other suitable mechanisms.

[0005] Current applications for conducting transactions do not provide customers with the opportunity to conduct hands-free transactions. In addition, current applications require customers to perform an action to identify themselves by providing a user account identifier or other data to the merchant system. Traditional systems do not allow third-party systems to protect the identity of user accounts from the merchant's computing system, employees of the merchant system, or anyone else who may gain access to transaction data.

[0006] Conventional systems do not allow payment processing systems to conduct settlement transactions with providers without participating in the settlement process of a third-party system, which would allow users to utilize the third-party system to maintain closed transaction records. Summary of the Invention

[0007] Technology provided herein is a computer-implemented method that utilizes an account management system to authorize transactions and provide payment account information to a payment processing system, while allowing transaction settlement to occur between the payment processing system and the merchant.

[0008] In an example, a merchant system registers with an account management system. The merchant system installs one or more merchant beacon devices and one or more merchant point-of-sale devices at the merchant system location. A user establishes an account with the account management system and downloads a payment application on a user computing device associated with the user. In an example, the user sends an image of themselves and / or an audio recording of themselves to the account management system to establish a facial template and / or audio template associated with the user account. The user enters the merchant system location and logs into the payment application via the user computing device. The user computing device receives the merchant beacon device identifier broadcast at the merchant location from the merchant beacon device and transmits the merchant beacon device identifier to the account management system. The account management system transmits the facial template, audio template, and / or challenge and response to the merchant point-of-sale device associated with the user whose user computing device is within the network range of the merchant beacon device and logged into the payment application. In addition, the account management system generates a payment token for each user whose user computing device is within the network range of the merchant beacon device and logged into the payment application. Example payment tokens include a series of alphanumeric and / or symbolic characters. Example payment tokens can be associated with the user's payment account and can be recognized by the issuer system associated with the user's payment account. For example, the account management system generates a payment token and communicates the payment token along with the user's payment account information to an issuer system associated with the user's payment account. In this example, if the issuer system later receives the payment token from a point-of-sale device in a payment transaction, the issuer system can extract the user's payment account information associated with the payment token.

[0009] A merchant camera device associated with a merchant point-of-sale device captures a facial image of the user, and the merchant point-of-sale device identifies the user based on comparing the captured facial image to a received facial template. Alternatively, the user submits an audio recording to the merchant point-of-sale device, which identifies the user based on comparing the received audio recording to the user's audio template. In yet another embodiment, the merchant point-of-sale device operator identifies the user based on the user's response to a challenge. After identifying the user, the merchant point-of-sale device processes the transaction using a payment token associated with the user received from an account management system. The merchant point-of-sale device generates a transaction authorization request including the payment token and transaction details and transmits the transaction authorization request to an issuer system associated with the user account selected for the transaction. The issuer system identifies the user's payment account based on the received payment token and processes the transaction using the transaction details and the user's payment account information. The merchant point-of-sale device receives approval of the transaction authorization request and transmits a receipt to the merchant point-of-sale device.

[0010] In an example, a hands-free transaction is processed by utilizing an account management system to authorize the transaction and provide payment account information to the payment processing system while allowing transaction settlement to occur between the payment processing system and the merchant. After verifying the user's account, the merchant's POS device generates a payment authorization request (also referred to herein as a transaction request) based on the user verification and other transaction information. The merchant's POS device transmits the payment authorization request to the account management system, and the account management system identifies the user's payment information. The account management system receives the authorization from the payment processing system and transmits the payment authorization to the merchant. The merchant's salesperson completes the transaction with the user by providing the product or service being purchased. The payment processing system and the merchant's system then settle the transaction without involving the account management system.

[0011] In certain other example aspects described herein, systems and computer program products are provided for conducting offline hands-free transactions through facial recognition of a user.

[0012] These and other aspects, objects, features and advantages of the examples will become apparent to those skilled in the art after considering the following detailed description of the illustrated examples. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a block diagram depicting a system for processing offline hands-free transactions using facial recognition of a user, according to certain examples.

[0014] Figure 2 is a block flow diagram describing a method for processing offline hands-free transactions using facial recognition of a user, according to certain examples.

[0015] Figure 3 is a block flow diagram describing a method for registering a merchant system with an account management system and installing hardware at a merchant system location, according to certain examples.

[0016] Figure 4 is a block flow diagram describing a method for registering an account with an account management system by a user according to certain examples.

[0017] Figure 5 is a block flow diagram describing a method for establishing a facial template associated with a user account according to certain examples.

[0018] Figure 6 is a block flow diagram describing a method for establishing an audio template associated with a user account according to certain examples.

[0019] Figure 7 is a block flow diagram describing a method for receiving, by a user computing device, a merchant beacon identifier broadcast by a merchant beacon device, according to certain examples.

[0020] Figure 8 is a block flow diagram describing a method for receiving, by a point-of-sale device, a facial template and a payment token for each user within range of a merchant beacon device, according to certain examples.

[0021] Figure 9 is a block flow diagram describing a method for updating a current customer log by a merchant point-of-sale device when a user enters or leaves network range of a merchant beacon device, according to certain examples.

[0022] Figure 10 is a block flow diagram describing a method for initiating a transaction by a user at a merchant point of sale device, according to certain examples.

[0023] Figure 11 is a block flow diagram describing a method for identifying a user via facial recognition by a merchant point-of-sale device, according to certain examples.

[0024] Figure 12 is a block flow diagram describing a method for identifying a user by a merchant point-of-sale device via voice recognition, according to certain examples.

[0025] Figure 13 is a block flow diagram describing a method for identifying a user by a merchant point-of-sale device operator via a challenge and response, according to certain examples.

[0026] Figure 14 is a block flow diagram describing a method for conducting a transaction according to certain examples.

[0027] Figure 15 is a block flow diagram describing a method for conducting a transaction according to certain examples.

[0028] Figure 16 is a block diagram depicting computing machines and modules according to certain examples. DETAILED DESCRIPTION

[0029] Overview

[0030] Examples described herein provide computer-implemented techniques for processing offline hands-free transactions using facial recognition of users.

[0031] In an example, a merchant system registers with an account management system. The merchant system installs one or more merchant beacon devices and one or more merchant point-of-sale devices at the merchant system location. A user establishes an account with the account management system and downloads a payment application on a user computing device associated with the user. In an example, the user sends an image of himself and / or an audio recording of himself to the account management system to establish a facial template and / or audio template associated with the user account. The user enters the merchant system location and logs into the payment application via the user computing device. The user computing device receives a merchant beacon device identifier broadcast at the merchant location from the merchant beacon device and sends the merchant beacon device identifier to the account management system. The account management system sends the facial template, audio template, and / or challenge and response to the merchant point-of-sale device associated with the user whose user computing device is within the network range of the merchant beacon device and logged into the payment application. In addition, the account management system generates a payment token for each user whose user computing device is within the network range of the merchant beacon device and logged into the payment application. Example payment tokens include a series of alphanumeric and / or symbolic characters. Example payment tokens can be associated with the user's payment account and can be recognized by the issuer system associated with the user's payment account. For example, the account management system generates a payment token and transmits the payment token along with the user's payment account information to an issuer system associated with the user's payment account. In this example, if the issuer system later receives the payment token from a point-of-sale device in a payment transaction, the issuer system can extract the user's payment account information associated with the payment token.

[0032] A merchant camera device associated with a merchant point-of-sale device captures a facial image of the user, and the merchant point-of-sale device identifies the user based on comparing the captured facial image to a received facial template. Alternatively, the user submits an audio recording to the merchant point-of-sale device, which identifies the user based on comparing the received audio recording to the user's audio template. In yet another embodiment, the merchant point-of-sale device operator identifies the user based on the user's response to a challenge. After identifying the user, the merchant point-of-sale device processes the transaction using a payment token associated with the user received from an account management system. The merchant point-of-sale device generates a transaction authorization request including the payment token and transaction details, and sends the transaction authorization request to an issuer system associated with the user account selected for use in the transaction. The issuer system identifies the user's payment account based on the received payment token and processes the transaction using the transaction details and the user's payment account information. The merchant point-of-sale device receives approval of the transaction authorization request and sends a receipt to the merchant point-of-sale device.

[0033] In an example, a merchant system is registered with an account management system. A merchant system operator installs a payment application on a merchant point-of-sale device. In another example, the merchant system operator installs the payment application on multiple merchant point-of-sale devices at a merchant system location. A merchant beacon device receives a beacon identifier code from the account management system. For example, the merchant system operator installs one or more merchant beacon devices at the merchant system location. The merchant beacon device broadcasts the merchant beacon identifier code via wireless communications at the merchant system location. The merchant system operator installs a merchant camera device at the merchant system location to correspond to a corresponding merchant point-of-sale device. In another example, multiple merchant camera devices are installed at the merchant system location, each merchant camera device corresponding to a specific merchant point-of-sale device. In yet another example, a specific merchant camera device may correspond to two or more specific merchant point-of-sale devices.

[0034] In one example, a user registers with an account management system. For example, the user accesses the account management system website via a user computing device associated with the user. The user registers with the account management system and downloads a payment application onto the user computing device. In one example, the account management system establishes a facial template associated with the user account. For example, the payment application displays a request for the user to capture a facial image via the user computing device. The user selects the option to capture a facial image. The payment application activates the camera module on the user computing device, and the user captures their own facial image. The account management system receives the facial image. Based on the received facial image, the account management system creates a facial template associated with the user account. The account management system deletes the received facial image. In another example, the account management system establishes an audio template associated with the user account. For example, the payment application requests and receives user audio via the user computing device. The payment application sends the received user audio to the account management system, and the account management system creates an audio template associated with the user account based on the received audio of the user's voice. The account management system deletes the received audio of the user's voice. In yet another example, the account management system establishes a challenge and response associated with the user account. For example, the payment application on the user computing device displays a challenge, such as "user initials," and requests a response from the user. In this example, user John Doe can enter "JD" as a response to the challenge. In this example, the payment application sends the entered response to the account management system, which associates the response with the challenge in the user's account.

[0035] A user logs into a payment application on a user computing device. The user brings the user computing device within a threshold distance of a merchant beacon device at a merchant system location. The user computing device receives a merchant beacon identifier broadcast by the merchant beacon device and transmits the received merchant beacon identifier and a user account identifier to an account management system. The account management system receives the merchant beacon identifier and the user account identifier. The account management system extracts a facial template associated with the user account identifier and identifies the merchant point-of-sale device associated with the merchant beacon device identifier. In another example, in addition to or in lieu of extracting the facial template associated with the user account identifier, the account management system extracts an audio template associated with the user account identifier and / or a challenge and response associated with the user account identifier.

[0036] The account management system sends the identified user's facial template to a merchant point-of-sale device associated with the merchant beacon device identifier. For example, the facial template associated with the identified user's account is sent to the merchant point-of-sale device. The merchant point-of-sale device receives the user's facial template, the user's audio template, and / or a challenge and response associated with the user.

[0037] In addition, the account management system generates a payment token for each user whose user computing device is within network range of the merchant beacon device and logged into the payment application. The example payment token includes a series of alphanumeric and / or symbolic characters. The example payment token can be associated with the user's payment account and can be recognized by an issuer system associated with the user's payment account. For example, the account management system generates a payment token and communicates the payment token along with the user's payment account information to the issuer system associated with the user's payment account. In this example, if the issuer system later receives the payment token from a point-of-sale device in a payment transaction, the issuer system is able to extract the user's payment account information associated with the payment token.

[0038] The merchant point-of-sale device associates the payment token, the user's facial template, the user's audio template, and the user's challenge and response in the current customer log. The merchant point-of-sale device periodically updates the current customer log based on updates received from the account management system. For example, the account management system transmits a subsequent facial template, audio template, challenge and response, and payment token for a subsequent user who brings a user computing device, logged into a payment application via their user account, within a threshold distance of the merchant beacon device required to establish a wireless network connection. In this example, the account management system receives the merchant beacon device identifier transmitted by the user computing device, generates a payment token, and transmits the subsequent user's facial template, the subsequent user's audio template, the subsequent user's challenge and response, and the generated payment token to the merchant point-of-sale device. In another example, in response to detecting that a user computing device associated with a particular user in the current customer log no longer maintains a network connection with the merchant beacon device, no longer retransmits the merchant beacon device identifier to the account management system, or is no longer logged into the payment application, the account management system transmits a notification to the merchant point-of-sale device that the user has left the merchant's location. In this example, the merchant point-of-sale device deletes the indicated user from the current customer log. For example, deleting the indicated user includes deleting the user account identifier, facial template, audio template, challenge and response, payment token, and / or any other data associated with the particular user on the merchant point of sale device.

[0039] A user approaches a merchant point-of-sale device. The merchant point-of-sale device operator adds up the items the user wishes to purchase. The merchant point-of-sale device operator asks the user to select a payment option. The user instructs the merchant point-of-sale device operator to initiate a transaction via a payment application. For example, as previously discussed, the payment application is installed on the merchant point-of-sale device and the user's computing device. The merchant point-of-sale device operator selects an option on the merchant point-of-sale device to initiate the transaction using the payment application.

[0040] A merchant camera device communicatively coupled to a merchant point-of-sale device captures video of a user. For example, the user is positioned in front of the point-of-sale device, and the merchant camera device is positioned to capture video of the user's face. In one example, the merchant camera device begins capturing video of the user only when the merchant point-of-sale device receives input from an operator of the merchant point-of-sale device identifying the user. In another example, the merchant camera device begins capturing video when the associated merchant point-of-sale device receives an instruction from an account management system to establish a network connection between a user computing device associated with the user and a merchant beacon device and / or to retransmit the merchant beacon device identifier to the account management system. In this example, the merchant camera device does not capture video when no user with an associated user computing device is within network range of the merchant beacon device. The merchant camera device extracts the user's facial image from the captured video and generates a facial template from the captured facial image. The merchant camera device deletes the captured video and the extracted facial image and transmits the facial template to the merchant point-of-sale device. In another example, the merchant camera device transmits the user's facial image to the merchant point-of-sale device, and the merchant point-of-sale device generates the facial template from the facial image.

[0041] The merchant point-of-sale device retrieves a facial template from a current customer log. For example, the current customer log includes a user list and associated facial templates for users associated with a user computing device that has currently established a network connection with a merchant beacon device at the merchant system location and / or has retransmitted the merchant beacon device identifier to the account management system. In some examples, the current customer log includes volatile or temporary memory. For example, when a user computing device associated with a corresponding user enters or leaves the network range of the merchant beacon device, the current customer log is not saved, and user information is added or deleted from the current customer log. The merchant point-of-sale device compares the facial template generated from the extracted facial image with the facial template from the current customer log. If there is a match between the facial template from the current customer log and the generated facial template, the merchant point-of-sale device is able to identify the user. If there is no match between the facial template from the current customer log and the generated facial template, the merchant point-of-sale device cannot identify the user. If the merchant point-of-sale device is able to identify the user, the merchant point-of-sale device notifies the account management system of the user's identity, and the account management system processes the transaction between the user and the merchant system. In an example, if the merchant point of sale device is able to identify the user but is unable to inform the account management system of the user's identity, the merchant point of sale device processes the transaction using the received payment token associated with the user account of the identified user.

[0042] In one example, if the user cannot be identified based on facial recognition, the merchant point-of-sale device identifies the user based on audio recognition. In another example, the account management system does not identify the user based on audio recognition. In another example, if the payment processing identifies the user based on audio recognition, the account management system retrieves an audio template corresponding to the user from the current customer log. The merchant point-of-sale device displays a request to record the user's audio via the user interface of the merchant point-of-sale device. The merchant point-of-sale device records the user's voice input and compares the received voice input with the retrieved audio template corresponding to the user from the current customer log. If there is a match between the audio template from the current customer log and the received user's voice input, the merchant point-of-sale device is able to identify the user. If there is no match between the audio template from the current customer log and the received user's voice input, the merchant point-of-sale device is unable to identify the user. If the merchant point-of-sale device is able to identify the user, the merchant point-of-sale device notifies the account management system of the user's identity, and the account management system processes the transaction between the user and the merchant system. In another example, if the merchant point-of-sale device is able to identify the user but is unable to notify the account management system of the user's identity, the merchant point-of-sale device processes the transaction using a received payment token associated with the user account of the identified user.

[0043] If the merchant point-of-sale device cannot identify the user based on facial and / or voice recognition, the merchant point-of-sale device operator is notified via a display on the merchant point-of-sale device that a challenge has been issued to the user. The user provides a challenge response, and the merchant point-of-sale operator enters the response into the merchant point-of-sale device. The merchant point-of-sale device displays potential users from a current customer log based on the challenge response. For example, the merchant point-of-sale device accesses a current customer log that includes a list or table associating challenges with corresponding responses, user account identifiers, and payment tokens. In this example, the merchant point-of-sale device identifies the user by associating the challenges and responses to identify one or more users in the current customer log. In this example, the merchant point-of-sale device displays the one or more identified users to the merchant point-of-sale device operator. The merchant point-of-sale device operator selects a user. In this example, the merchant point-of-sale device operator may compare the user's visual image or name displayed on the user's computing device with the visual appearance of current customers at the merchant point-of-sale device and / or documents presented by the user to the merchant point-of-sale operator. In this example, the merchant point-of-sale device transmits the identity of the user identified by the merchant point-of-sale operator. If the merchant point-of-sale device operator is able to identify the user via the challenge and response, the merchant point-of-sale device notifies the account management system of the user's identity, and the account management system processes the transaction between the user and the merchant system. If the merchant point-of-sale device operator is unable to identify the user via the challenge and response, the merchant point-of-sale device operator cancels the transaction by actuating one or more objects on the user interface of the merchant point-of-sale device. In an example, if the merchant point-of-sale device is able to identify the user but is unable to notify the account management system of the user's identity, the merchant point-of-sale device processes the transaction using the received payment token associated with the user account of the identified user.

[0044] The merchant point-of-sale device operator confirms the transaction with the user's permission. In an example, the merchant point-of-sale device generates a transaction authorization request based on the transaction details and a received payment token associated with the user retrieved from the current customer log. For example, the transaction details may include the total amount of the transaction, the selected user account used in the transaction, the merchant's account used in the transaction, and other useful or relevant information. The merchant point-of-sale device transmits the transaction authorization request to the issuer system. For example, the issuer system is associated with the user's payment account selected for use by the user in all hands-free transactions involving the payment application. The issuer system approves or denies the transaction authorization request and transmits the transaction authorization approval or denial to the merchant point-of-sale device. The merchant point-of-sale device transmits a transaction receipt to the user's computing device and / or prints or displays a receipt for the user at the merchant point-of-sale device indicating the status of the transaction. For example, the merchant point-of-sale device displays an indication that the transaction was successfully processed or that the transaction was denied.

[0045] In another example, a merchant point-of-sale device transmits, along with the transaction details, an indication of the user's identity, identified via facial recognition, audio, and / or a challenge and response to an account management system. In this example, the account management system processes the transaction through an issuer system. For example, the account management system generates a transaction authorization request including a payment token, where the transaction authorization request is based on user account information and the transaction details. In this example, the merchant point-of-sale device transmits the transaction authorization request to the issuer system. In this example, the issuer system receives the transaction authorization request, approves or denies the transaction authorization request, and transmits the denial or approval of the transaction authorization request to the account management system. For example, the issuer system identifies the user's payment account associated with the payment token. In this example, the transaction authorization request includes a total transaction amount, and the issuer system determines whether the transaction will cause the user to exceed a user credit limit associated with the user's payment account. The issuer system may make a decision to approve the transaction authorization request based on factors other than the total transaction amount on the payment account or the user's credit limit.

[0046] In an example, the account management system transmits a notification approving or denying the transaction to the merchant point-of-sale device and / or the user computing device based on information received from the issuer system. In this example, the merchant point-of-sale device and / or the user computing device displays or otherwise indicates the status of the transaction to the user. For example, the user computing device may receive and display a text message from the account management system indicating to the user that the transaction was denied.

[0047] In an example, a hands-free transaction is processed by utilizing an account management system to authorize the transaction and provide payment account information to a payment processing system while allowing transaction settlement to occur between the payment processing system and the merchant. After verifying the user's account, the merchant POS device generates a payment authorization request based on the user verification and other transaction information. In an example, the payment authorization request does not include a payment token received from the account management system for the user. In an example, when the user account information is provided, the payment token is not provided to the merchant. In an example, only the information required to verify the user's account is provided to the merchant point of sale device 130. The merchant point of sale device 130 transmits the payment authorization request to the account management system, and the account management system identifies the user payment data. The account management system 160 receives the authorization from the payment processing system and transmits the payment authorization to the merchant. The merchant salesperson completes the transaction with the user by providing the product or service being purchased.

[0048] The payment processing system and the merchant's system then settle the transaction without involving the account management system. The payment processing system provides the appropriate funds to the merchant's account. Funds settlement occurs without the account management system. That is, while the account management system is part of the transaction authorization process, it is not part of the settlement process. The account management system is not named in the transaction details, such as the transaction statement provided by the card issuer to the user. The transaction is indicated as having been conducted with the merchant, not the account management system. In this example, the account management system does not receive or transmit any funds associated with the transaction settlement. Funds are provided directly to the merchant from the issuer or payment processing system. The account management system does not act as an intermediary in the settlement.

[0049] By using and relying on the methods and systems described herein, an account management system enables users to conduct transactions with merchant systems without requiring the user to interact with a user computing device or produce identification documents or physical payment cards, as required in some prior art techniques. Thus, the systems and methods described herein can reduce the input required by the user via the user computing device and the input required by the merchant's point-of-sale device operator to identify the user. Furthermore, the user can conduct transactions without the merchant having access to the user's account identifier, which protects the user's account from theft or fraud by the merchant or its employees. Furthermore, transactions occur without the account management system being named in the transaction, further protecting the user's account from fraud. For example, if a user employs an account management system to manage and protect the user's payment account, the transaction record will not list the name of the account management system, only the name of the payment account used and the merchant.

[0050] Example system architecture

[0051] Turning now to the drawings, in which like numerals indicate similar (but not necessarily identical) elements throughout the figures, examples are described in detail.

[0052] Figure 1 is a block diagram illustrating a system 100 for conducting hands-free transactions through facial recognition of a user 101, according to certain examples. Figure 1 As shown in , system 100 includes network computing devices 110, 130, 140, 150, 160, and 170 configured to communicate with each other via one or more networks 180. In some embodiments, a user associated with a device must install an application and / or make a feature selection to obtain the benefits of the techniques described herein.

[0053] In examples, network 180 may include a local area network ("LAN"), a wide area network ("WAN"), an intranet, the Internet, a storage area network ("SAN"), a personal area network ("PAN"), a metropolitan area network ("MAN"), a wireless local area network ("WLAN"), a virtual private network ("VPN"), a cellular or other mobile communication network, Bluetooth, Bluetooth low energy, NFC, or any combination thereof or any other suitable architecture or system that facilitates communication of signals, data and / or messages. Throughout the discussion of examples, it should be understood that the terms "data" and "information" are used interchangeably herein to refer to text, images, audio, video, or any other form of information that can exist in a computer-based environment.

[0054] Each network computing device 110, 130, 140, 150, 160, and 170 comprises a device having a communication module capable of transmitting and receiving data over the network 180. For example, each network computing device 110, 130, 140, 150, 160, and 170 can comprise a server, a desktop computer, a laptop computer, a tablet computer, a television having one or more processors embedded therein and / or coupled thereto, a smart phone, a handheld computer, a personal digital assistant ("PDA"), or any other wired or wireless, processor-driven device. Figure 1 In the example shown in , network computing devices 110, 130, 140, 150, 160, and 170 are operated by user 101, a merchant beacon device 120 operator, a merchant point of sale ("POS") device 130 operator, a payment processing system 140 operator, an issuer system 150 operator, an account management system 160, and a merchant system 170 operator.

[0055] The example user computing device 110 includes an antenna 111 , a Bluetooth Low Energy (“BLE”) controller 112 , a payment application 113 , a user interface 115 , a data storage unit 116 , a camera module 117 , a web browser 118 , and a communication application 119 .

[0056] In an example, antenna 111 is a means for communication between the user computing device 110 and the merchant beacon device 120. In an example, the BLE controller 112 outputs a radio signal through the antenna 111 or listens for a radio signal from the merchant beacon device 120. In another example, a Bluetooth controller, a Wi-Fi controller, or a near field communication ("NFC") controller is used. In an example, the BLE controller 112 outputs a radio signal through the antenna 111 or listens for a radio signal from the merchant beacon device 120.

[0057] In an example, the BLE controller 112 is capable of sending and receiving data, performing authentication and encryption functions, and instructing the user computing device 110 on how to listen for transmissions from the merchant beacon device 120 or configuring the user computing device 110 to enter various power saving modes according to BLE-specified procedures. In another example, the user computing device 110 includes a Bluetooth controller, a Wi-Fi controller, or an NFC controller capable of performing similar functions. The example BLE controller 112 communicates with the payment application 113 and is capable of transmitting and receiving data over a wireless BLE communication channel. In another example, the Bluetooth controller 112, the Wi-Fi controller 112, or the NFC controller 112 uses the Bluetooth, Wi-Fi, or NFC protocols to perform similar functions as the BLE controller 112. In an example, the BLE controller 112 activates the antenna 111 to create a wireless communication channel between the user computing device 110 and the merchant beacon device 120. The user computing device 110 communicates with the merchant beacon device 120 via the antenna 111. For example, when the user computing device 110 has been activated, the BLE controller 112 polls for radio signals through the antenna 111 or listens for radio signals from the merchant beacon device 120 .

[0058] In an example, the payment application 113 is a program, function, routine, applet, or similar entity that resides on the user computing device 110 and performs its operations thereon. In some examples, the user 101 must install the payment application 113 and / or perform feature selection on the user computing device 110 to obtain the benefits of the techniques described herein. In an example, the user 101 can access the payment application 113 on the user computing device 110 via the user interface 115. In an example, the payment application 113 can be associated with the account management system 160. In another example, the payment application 113 can be associated with a merchant system associated with the merchant beacon device 120 and / or the merchant point of sale device 130.

[0059] In an example, the user interface 115 enables the user 101 to interact with the payment application 113 and / or the web browser 118. For example, the user interface 115 can be a touch screen, a voice-based interface, or any other interface that allows the user 101 to provide input and receive output from an application or module on the user computing device 110. In an example, the user 101 interacts with the payment application 113 and / or the web browser 118 via the user interface 115. In another example, the user 101 interacts with the payment application 113 and / or the web browser 118 via the user interface 115 to implement hands-free payment if desired.

[0060] In an example, the data storage unit 116 includes a local or remote data storage structure suitable for storing information accessible by the user computing device 110. In an example, the data storage unit 116 stores encrypted information, such as HTML5 local storage.

[0061] In an example, the camera module 117 can be any module or functionality of the user computing device 110 that captures digital images. The camera module 117 can reside on the user computing device 110 or be logically connected to the user computing device 110 in any manner. For example, the camera module 117 can be connected to the user computing device 110 via the network 180. The camera module 117 can obtain individual images or video scans. Any other suitable image capture device can be represented by the camera module 117.

[0062] In an example, a user 101 can use a communication application 119 , such as a web browser 118 application or a standalone application, to view, download, upload, or otherwise access documents or web pages via the distributed network 180 .

[0063] In an example, the web browser 118 enables the user 101 to interact with web pages using the user computing device 110. In an example, the user 101 can access an account of the user 101 maintained by the account management system 160. In another example, the user 101 can access a merchant system website or an account management system website 169 via the web browser 118. In some examples described herein, one or more functions performed by the payment application 113 can also be performed by the web browser 118 application associated with the account management system 160.

[0064] In an example, the communication application 119 can interact with web servers or other computing devices connected to the network 180 , including the merchant system's web server and the account management system 160's web server 168 .

[0065] In some examples, one or more functions described herein as being performed by the payment application 113 may also be performed by a web browser 118 application (e.g., a web browser 118 application associated with a merchant system website or associated with the account management system 160). In some examples, one or more functions described herein as being performed by the payment application 113 may also be performed by the user computing device 110 operating system. In some examples, one or more functions described herein as being performed by the web browser 118 may also be performed via the payment application 113.

[0066] An example merchant beacon device 120 includes an antenna 121 and a Bluetooth Low Energy (“BLE”) controller 122. In an example, a merchant system location includes one or more merchant beacon devices 120 installed at the merchant system location. In an example, each installed merchant beacon device 120 is associated with a specific merchant point of sale device 130 installed at the merchant location via an account management system 160. For example, the account management system 160 may include a database that associates merchant beacon device 120 identifiers with merchant point of sale device 130 identifiers for the associated merchant point of sale devices 130. For example, the merchant point of sale device 130 identifier may include a device-specific hardware identifier, such as a serial number or a media access control (“MAC”) identifier. In another example, the merchant beacon device 120 identifier may include a beacon device-specific hardware identifier or an identifier generated by the account management system 160 and stored in the merchant beacon device 120. The example merchant beacon device 120 is programmed to broadcast, transmit, or otherwise communicate a specific merchant beacon device 120 identifier via a local wireless network, such as a BLE network, to any user computing device 110 within a threshold distance required to maintain a wireless network 180. For example, the wireless network may include a BLE network 180, a Wi-Fi network 180, a Bluetooth network 180, an NFC network 180, or any other suitable wireless network 180.

[0067] In an example, the antenna 121 is a communication device between the user computing device 110 and the merchant beacon device 120. In an example, the BLE controller 122 outputs a radio signal through the antenna 121 or listens for a radio signal from the user computing device 110. In another example, a Bluetooth controller, a Wi-Fi controller, or a near field communication ("NFC") controller is used. In an example, the BLE controller 122 outputs a radio signal through the antenna 121 or listens for a radio signal from the user computing device 110.

[0068] In an example, the BLE controller 122 is capable of transmitting and receiving data, performing authentication and encryption functions, and instructing the merchant beacon device 120 on how to listen for transmissions from the user computing device 110 or configuring the merchant beacon device 120 into various power saving modes according to BLE-specified procedures. In another example, the merchant beacon device 120 includes a Bluetooth controller, a Wi-Fi controller, or an NFC controller capable of performing similar functions. The example BLE controller 122 communicates with the payment application 113 and is capable of sending and receiving data over a wireless BLE communication channel. In another example, the Bluetooth controller 122, the Wi-Fi controller 122, or the NFC controller 122 performs similar functions as the Wi-Fi controller 122 using Bluetooth, Wi-Fi, or NFC protocols. In an example, the BLE controller 122 activates the antenna 121 to create a wireless communication channel between the user computing device 110 and the merchant beacon device 120. The merchant beacon device 120 communicates with the user computing device 110 via the antenna 121. For example, when the merchant beacon device 120 has been activated, the BLE controller 122 polls for radio signals through the antenna 121 , or listens for radio signals from the user computing device 110 .

[0069] The example merchant point of sale device 130 includes an audio module 131 , a camera module 132 , a payment application 133 , a user interface 135 , a data storage unit 136 , and a communication application 139 .

[0070] In an example, audio module 131 can be any module or functionality of merchant point of sale device 130 that captures audio input from the environment external to merchant point of sale device 130. Audio module 131 can reside on merchant point of sale device 130 or be logically connected to merchant point of sale device 130 in any manner. For example, audio module 131 can be connected to merchant point of sale device 130 via network 180. Audio module 131 is capable of obtaining audio recordings. Any suitable audio recording device can be represented by audio module 131.

[0071] In an example, camera module 132 can be any module or functionality of merchant point of sale device 130 that captures images or video feeds of the external environment of merchant point of sale device 130. The camera module can reside on merchant point of sale device 130 or be logically connected to merchant point of sale device 130 in any manner. For example, audio module 131 can be connected to merchant point of sale device 130 via network 180. Camera module 132 can capture one or more images or record video recordings. Any suitable image capture and / or video recording device can be represented by camera module 132.

[0072] In an example, the payment application 133 is a program, function, routine, applet, or similar entity that resides on the merchant point of sale device 130 and performs its operations on the merchant point of sale device 130. In some examples, the merchant point of sale ("POS") device operator 102 or other merchant system operator must install the payment application 133 and / or perform feature selection on the merchant point of sale device 130 to obtain the benefits of the techniques described herein. In an example, the merchant POS device operator 102 can access the payment application 133 on the merchant point of sale device 130 via the user interface 135 of the merchant point of sale device 130. In an example, the payment application 133 can be associated with the account management system 160. In another example, the payment application 133 can be associated with a merchant system associated with the merchant beacon device 120 and the camera module 132 of the merchant point of sale device 130.

[0073] In the example, user interface 135 enables merchant POS device operator 102 to interact with merchant point of sale device 130. For example, user interface 135 may be a touch screen, a voice-based interface, or any other interface that allows merchant POS device operator 102 to provide input and receive output from an application or module on merchant point of sale device 130. In the example, merchant POS device operator 102 interacts with payment application 133 via user interface 135.

[0074] In an example, data storage unit 136 includes a local or remote data storage structure suitable for storing information accessible to merchant point of sale device 130. In an example, data storage unit 136 stores encrypted information, such as HTML5 local storage.

[0075] In an example, a communication application 139, such as a web browser application or a standalone application, enables an operator of a merchant point of sale device 130 to view, download, upload, or otherwise access documents or web pages via the distribution network 180. For example, the communication application 139 may enable communication with the account management system 160, the payment processing system 140, and / or the issuer system 150 over the network 180.

[0076] Merchant point-of-sale device 130 may be associated with merchant system 170. Merchant system 170 may represent a merchant's system for managing merchant functions. Merchant system 170 may represent a merchant server, a third-party financial system provider, or any other person, server, or system that performs merchant functions. For example, merchant system 170 may communicate transaction data, authorization requests, settlement requests, or any other data necessary to conduct a transaction. Merchant system 170 may perform these functions using or in conjunction with merchant point-of-sale device 130. That is, any functions described herein as being performed by merchant point-of-sale device 130 or merchant system 170 may be performed by either or both parties, as appropriate.

[0077] The example payment processing system 140 communicates with the account management system 160 and the merchant point-of-sale device 130. In this example, when the account management system 160 processes a payment transaction, the account management system 160 transmits the user 101 payment account data to the payment processing system 140, which communicates a transaction authorization request to the issuer system 150 associated with the payment account data on behalf of the merchant system. In this example, the payment processing system 140 receives an approval or denial of the payment authorization request from the issuer system 150. In this example, the payment processing system 140 communicates a notification to the account management system 160 and / or the merchant point-of-sale device 130 of the approval or denial of the transaction. In this example, the account management system 160 and / or the merchant point-of-sale device 130, upon receiving the notification of the approval or denial of the transaction, may transmit receipt data to the user computing device 110.

[0078] The example issuer system 150 approves or denies a payment authorization request received from a merchant point-of-sale device 130. In the example, the issuer system 150 communicates with the merchant point-of-sale device 130 via a network 180. In the example, the issuer system 150 communicates with an acquirer system to approve the credit authorization for user 101 and make payment to the merchant system. For example, the acquirer system is a third-party payment processing system 140. In other examples, the issuer system 150 receives the payment authorization request from a payment processing system 140 or an account management system 160 via the network 180.

[0079] The example account management system 160 includes an account management module 161 , a facial recognition module, an audio recognition module, a data storage unit 166 , a transaction processing module 167 , a server 168 , and a website 169 .

[0080] In the example, account management module 161 manages one or more user 101 accounts. In the example, user 101 accounts may include digital wallet accounts, email accounts, social network accounts, or any other suitable accounts associated with account management system 160. In the example, account management module 161 communicates with payment application 113 operating on user computing device 110 associated with user 101, who has a user 101 account with account management system 160. In the example, user 101 enters payment account information into the user 101 account via payment application 113, and account management module 161 receives the payment account information via network 180 and associates the received payment account information with the user 101 account.

[0081] In an example, the data storage unit 166 includes a local or remote data storage structure suitable for storing information accessible by the account management system 160. In an example, the data storage unit 166 stores encrypted information, such as HTML 5 local storage.

[0082] In some examples, transaction processing module 167 receives transaction details and a request to initiate a transaction from a merchant point-of-sale device 130. Example transaction details include merchant system account information, a transaction total, and user 101's selection of a payment account associated with user 101's account in account management system 160. For example, user 101's account may be a digital wallet account that includes one or more payment account information corresponding to one or more corresponding payment accounts of user 101. In an example, transaction processing module 167 extracts payment account information from user 101's account corresponding to the user 101 payment account selected by user 101 from the merchant point-of-sale device 130 in the transaction details. In an example, transaction processing module 167 transmits a payment authorization request to issuer system 150 or another appropriate financial institution associated with the payment account selected by user 101 for use in the transaction. The example payment authorization request may include merchant system payment account information, user 101 payment account information, and the transaction total. In an example, after issuer system 150 processes the payment authorization request, transaction processing module 167 receives an approval or rejection of the payment authorization request from issuer system 150 via network 180. In an example, the transaction processing module 167 transmits a receipt including a transaction summary to the merchant point of sale device 130 and / or the user computing device 110 .

[0083] It will be understood that the network connections shown are examples and that other means of establishing a communications link between the computer and the device can be used. Furthermore, those of ordinary skill in the art having the benefit of this disclosure will appreciate that Figure 1The user computing device 110, merchant beacon device 120, merchant point of sale device 130, payment processing system 140, issuer system 150, and account management system 160 shown in FIG can have any of several other suitable computer system configurations. For example, the user computing device 110 embodied as a mobile phone or handheld computer may or may not include all of the above components.

[0084] In an example, the network computing device and any other computing machines associated with the techniques presented herein may be any type of computing machine, such as, but not limited to, a computer system. Figure 16 Furthermore, modules associated with any of these computing machines, such as the modules described herein or any other modules (scripts, web content, software, firmware, or hardware) associated with the techniques presented herein, may be implemented by reference to Figure 16 Any module discussed in more detail. The computing machines discussed herein can communicate with each other and with other computing machines or communication systems via one or more networks, such as network 180. Network 180 can include any type of data or communication network, including Figure 16 Any network technology discussed.

[0085] Example Process

[0086] The following is a description of the components of the example operating environment Figure 2-14 The example method illustrated in FIG. can also be performed by other systems and in other environments Figure 2-14 Example method.

[0087] Figure 2 is a block diagram illustrating a method 200 for conducting a hands-free transaction using facial recognition of a user 101, according to certain examples. Figure 1 The components illustrated in FIG. 2 describe method 200 .

[0088] In block 210, the merchant system registers with the account management system 160 and installs the hardware in the merchant location. Figure 3 The method described in more detail describes the method for registering with the account management system 160 by the merchant system and installing the hardware at the merchant system location.

[0089] Figure 3 is a block diagram illustrating a method 210 for registering a merchant system with the account management system 160 and installing hardware at a merchant system location, according to certain examples. Figure 1 Method 210 is described with reference to the components illustrated in FIG.

[0090] In the examples described herein, the merchant system does not need to install the hardware at the example merchant system location in any particular order. Method 210 describes one example method for installing hardware at a merchant location. However, the merchant system or other system that installs the merchant hardware does not need to install the merchant point of sale device 130, the camera module 132 of the merchant point of sale device 130, or the merchant beacon device 120 in the order described herein.

[0091] In block 310, the merchant system registers with the account management system 160. In an example, an agent of the merchant system accesses the account management system 160 website and registers a merchant account with the account management system 160 via the website. In an example, the merchant system adds payment account information associated with the merchant account to the merchant account managed by the account management system 160. In an example, the merchant system includes one or more merchant system locations. For example, the merchant system can include one or more physical store locations. An example merchant location includes one or more merchant point of sale ("POS") devices 130. In an example, one or more merchant POS device operators 102 operate one or more merchant point of sale devices 130 at the merchant system location.

[0092] In block 320, the merchant system operator installs the payment application 133 on the merchant point of sale device 130. In another example, the merchant system operator purchases the merchant point of sale device 130 from the account management system 160 with the payment application 133 pre-installed on the merchant point of sale device 130. In an example, the merchant point of sale device 130 is capable of communicating with the account management system 160 via the network 180. In an example, the merchant point of sale device 130 communicates with the account management system 160 via the payment application 133. For example, the merchant point of sale device 130 is capable of transmitting transaction details to the account management system 160 via the payment application 133 via the network 180 so that the account management system 160 can process the transaction. In another example, the merchant point of sale device 130 is capable of receiving a receipt from the account management system 160 that notifies the merchant POS device operator 102 whether the transaction was successful.

[0093] In block 330, the merchant beacon device 120 receives a beacon identifier from the account management system 160. In an example, the merchant system receives the beacon identifier from the account management system 160 and installs or otherwise stores the beacon identifier on the account management system 160. In an example, the merchant system operator installs the merchant beacon device 120 in proximity to the merchant point-of-sale device 130. In an example, the merchant system operator installs multiple merchant beacon devices 120, each merchant beacon device 120 in proximity to one or more associated merchant point-of-sale devices 130. In an example, the merchant beacon device 120 can broadcast the merchant beacon identifier over a wireless medium, wherein one or more user computing devices 110 within a threshold proximity range to the merchant beacon device 120 can receive the merchant beacon identifier over the wireless medium. In another example, the merchant beacon device 120 can establish a local network 180 connection to one or more user computing devices 110 that are located within a threshold proximity to the merchant beacon device 120, and the merchant beacon device 120 transmits the merchant beacon identifier to the one or more user computing devices 110 over the established local network 180 connection. For example, the threshold proximity depends on the network 180 communication protocol used by the merchant beacon device 120.

[0094] In block 340, the merchant beacon device 120 broadcasts the beacon identifier code via wireless communication at the location of the merchant system. For example, the merchant beacon device 120 can broadcast, transmit, or otherwise communicate data including the beacon identifier via Wi-Fi, Bluetooth, Bluetooth Low Energy (“BLE”), near field communication (“NFC”), or other suitable communication protocol to one or more user computing devices 110 at a merchant system located within a threshold proximity to the merchant beacon device 120. In some examples, the merchant beacon device 120 is operable to establish a network 180 connection between the one or more user computing devices 110 at the merchant system located within the threshold proximity to the merchant beacon device 120 and the merchant beacon device 120 at a time prior to transmitting the merchant beacon identifier.

[0095] In block 350, the merchant system operator installs the camera module 132 of the merchant point of sale device 130 at the merchant system location to correspond to the merchant beacon device 120. In an example, the camera module 132 of the merchant point of sale device 130 and the merchant beacon device 120 are both installed proximate to a particular merchant point of sale device 130. In another example, the camera module 132 of the merchant point of sale device 130 and the merchant beacon device 120 are installed proximate to two or more particular merchant point of sale devices 130. In an example, the camera module 132 of the merchant point of sale device 130 is oriented to be able to capture video and / or images of the face of the user 101 standing in front of one or more merchant point of sale devices 130 during the checkout process. In an example, the merchant system installs the camera module 132 of the merchant point of sale device 130 oriented to capture video and / or images of the face of the user 101 standing in front of the particular merchant point of sale device 130. In another example, the merchant system installs the camera module 132 of the merchant point of sale device 130 oriented to capture video and / or images of the faces of one or more users 101 standing proximate to a particular plurality of merchant point of sale devices 130 within the field of view of the camera module 132 of the merchant point of sale device 130 .

[0096] In block 360, the account management system 160 receives the camera module 132 identifier of the merchant point-of-sale device 130 and associates it with the corresponding beacon identifier code of the merchant beacon device 120. In an example, the merchant system and / or account management system 160 configures the camera module 132 of the merchant point-of-sale device 130 so that the camera module 132 of the merchant point-of-sale device 130 can communicate with the account management system 160 via the network 180. Example camera device 140 identifiers include hardware identifiers, MAC addresses, or other useful or relevant identifiers of the camera module 132 of the associated merchant point-of-sale device 130. In an example, the account management system 160 includes a database that includes the camera module 132 identifiers of the merchant point-of-sale device 130 and the associated beacon identifiers of the merchant beacon device 120 identifiers for a particular merchant system location. In an example, the merchant camera device transmits the merchant beacon device 120 identifier to the account management system 160 in addition to the camera module 132 identifier of the merchant point-of-sale device 130. In an example, the camera module 132 of the merchant point of sale device 130 can receive the merchant beacon device 120 identifier from the merchant beacon device 120 via an appropriate wireless communication channel during the setup and installation process. In another example, the camera module 132 of the merchant point of sale device 130 can establish a network 180 connection with the merchant beacon device 120 during the setup and installation process and receive the merchant beacon device 120 identifier via the network 180. In another example, the account management system 160 receives the camera module 132 identifier of the merchant point of sale device 130, extracts one or more merchant beacon device 120 identifiers from a database, and associates the camera module 132 identifier of the merchant point of sale device 130 with one or more of the one or more extracted merchant beacon device 120 identifiers. In yet another example, the merchant system operator installs the one or more merchant beacon devices 120 after installing the camera module 132 of the one or more merchant point of sale devices 130. In this example, the account management system 160 generates a merchant beacon device identifier to associate with the camera module 132 identifier of the merchant point of sale device 130 and transmits the generated merchant beacon device identifier to the merchant system. In this example, the merchant system operator manually configures the merchant beacon device 120 to broadcast, transmit, or otherwise transmit the merchant beacon device identifier assigned by the account management system 160 over the network 180.

[0097] In some examples, one or both of the camera module 132 of the merchant point of sale device 130 and the merchant beacon device 120 are components of the merchant point of sale device 130, or are wirelessly or physically connected to the merchant point of sale device 130 and controlled by one or more processors of the merchant point of sale device 130. In some examples, certain functions described herein as being performed by the camera module 132 of the merchant point of sale device 130 and / or the merchant beacon device 120 may also be performed by the merchant point of sale device 130.

[0098] From block 360, method 210 proceeds to Figure 2 Frame 220.

[0099] return Figure 2 , in block 220, user 101 registers with account management system 160. Figure 4 The method 220 described in

[0044] is described in more detail below as a method for registering an account with the account management system 160 by the user 101.

[0100] Figure 4 is a block diagram illustrating a method 220 for registering an account with the account management system 160 by a user 101 according to certain examples. Figure 1 Method 220 is described with reference to the components illustrated in FIG.

[0101] In block 410, user 101 accesses account management system website 169. For example, user 101 accesses account management system 160 via web browser 118 of user computing device 110. In another example, user 101 may contact account management system 160 in other ways to register user 101 account.

[0102] In block 420, user 101 registers with account management system 160. User 101 may obtain a user account, receive appropriate applications and software to install on user computing device 110, request authorization to participate in hands-free payment processing, or perform any other actions required by account management system 160. User 101 may utilize functionality of user computing device 110, such as user interface 115 and web browser 118, to register and configure user 101 account. In an example, user 101 may enter payment account information associated with one or more user 101 accounts, such as one or more credit accounts, one or more bank accounts, one or more stored value accounts, and / or other appropriate accounts, into user 101 accounts maintained by account management system 160.

[0103] In block 430, user 101 downloads payment application 113 onto user computing device 110. In an example, payment application 113 operating on user computing device 110 is capable of communicating with account management system 160 via network 180. In an example, user 101 can configure user 101 account settings or add, delete, or edit payment account information via payment application 113. In an example, user 101 can select an option to enable or disable permission from account management system 160 to process hands-free transactions. For example, hands-free transactions include transactions in which user 101 does not require interaction with user computing device 110 or requires minimal user 101 interaction with user computing device 110 to initiate a transaction with a merchant system.

[0104] In block 440, the account management system 160 creates a facial template associated with the user 101 account. Figure 5 Method 440 described in more detail describes a method for establishing a facial template associated with user 101's account.

[0105] Figure 5 is a block diagram illustrating a method 440 for establishing a facial template associated with a user 101 account according to certain examples. Figure 1 Method 440 is described with reference to the components illustrated in FIG.

[0106] In block 510, payment application 113 displays a request for user 101 to capture a facial image via user computing device 110. In the example, payment application 113 displays the request via user interface 115. In the example, user interface 115 may display a request that reads, "To enable hands-free transactions, we need an image of your face. Would you like to submit a facial image now?" In this example, user 101 may select an option to take a current picture, or may otherwise select a picture stored on user computing device 110.

[0107] In block 520, the user 101 selects an option to capture a facial image. For example, the user 101 activates an object on the user interface 115 that reads "yes, I would like to take a picture now."

[0108] In block 530, the payment application 113 activates the camera module 117 on the user computing device 110, and the user 101 captures an image of their own face. In an example, the user computing device user interface 115 may display a live camera feed of the user 101 to help the user 101 align their face to capture the facial image. In an example, the payment application 113 may display a frame or other perimeter on the user interface 115 on the user computing device 110 within which the user 101 should align their face to capture a picture of the desired size predetermined by the account management system 160. In an example, the user 101 may actuate an object on the user interface 115 to capture the image. In this example, in response to the user actuating the object on the user interface 115, the camera module 117 receives a command from the payment application 113 to capture an image of the user 101. In another example, the camera module 117 receives a command from the payment application 113 to capture multiple images of the user 101 as the user 101 moves the camera around the user 101's face. For example, each of the multiple images of user 101 may correspond to a particular pose of user 101's face. The example facial image may include a digital image of user 101's face. In an example, account management system 160 may establish guidelines for user 101 in submitting facial images. For example, payment application 113 may instruct user 101 to remove any hat, head covering, glasses, or other objects or accessories that may obscure user 101's facial area so that payment application 160 can receive a complete depiction of user 101's face.

[0109] In the example, user computing device 110 determines whether the captured facial image is a valid facial image or an invalid facial image. For example, a valid facial image meets criteria predetermined by account management system 160, and an invalid facial image does not meet one or more of the criteria. For example, if user computing device 110 captures a facial image that includes incorrect dimensions, if part or all of user 101's face is obscured, or if the image is too dark or too light, user computing device 110 rejects the invalid facial image and displays a request directing user 101 to capture a subsequent facial image. In this example, user 101 captures the subsequent facial image via user computing device 110, and user computing device 110 transmits the subsequent facial image to account management system 160 via network 180.

[0110] In block 540, account management system 160 receives facial images. In another example, account management system 160 receives multiple facial images of user 101. For example, payment application 113 transmits one or more facial images of user 101 to account management system 160 via network 180. For example, account management system 160 associates the received one or more facial images with an account of user 101. For example, account management system 160 can identify user 101's account to associate with the received one or more images because user 101 was currently logged into payment application 113 on user computing device 110 when the one or more facial images were transmitted to account management system 160. In some examples, account management system 160 determines whether the received facial images are valid or invalid. For example, a valid facial image meets all criteria predetermined by account management system 160, while an invalid facial image does not meet one or more criteria. For example, if user 101 submits a facial image that includes incorrect dimensions, if part or all of user 101's face is obscured, or if the image is too dark or too light, account management system 160 rejects the invalid facial image and transmits a request to user computing device 110 directing user 101 to capture a subsequent facial image for transmission to account management system 160. In this example, user computing device 110 receives and displays the request, user 101 captures the subsequent facial image via user computing device 110, and user computing device 110 transmits the subsequent facial image to account management system 160 via network 180.

[0111] In block 550, account management system 160 creates a facial template associated with user 101's account based on the received facial image. In another example, account management system 160 generates a corresponding facial template for each of a plurality of received facial images associated with user 101's account. In an example, the facial template has a predetermined size, for example, a 128-byte facial template. In an example, account management system 160 generates a facial template comprising a computer code representation of a digital facial image. For example, the facial template may describe key features of user 101's facial image, such as shape, color, line, value, space, form, texture, or other useful or relevant features of the image or other useful or relevant features of a characteristic region of a particular image. In an example, the facial template is generated by processing the facial image via a convolutional neural network. In an example, account management system 160 stores the generated facial template associated with user 101 in data storage unit 166 associated with account management system 160. For example, the account management system 160 database may include a table or other means by which each user 101 account identifier is associated with a corresponding facial template of user 101.

[0112] In another example, after the user computing device 110 captures one or more facial images of the user 101, the user computing device 110 generates one or more facial templates corresponding to one or more of the one or more captured facial images of the user 101. In this example, the user computing device 110 transmits the one or more generated facial templates to the account management system 160 via the network 180.

[0113] At block 560 , account management system 160 deletes the received facial image. For example, account management system 160 uses only the facial template that includes the computer code representation of user 101's facial image. In another example, account management system 160 saves the received facial image for future processing. For example, account management system 160 later updates the facial template generation algorithm and generates an updated facial template corresponding to the saved facial image.

[0114] From block 560, method 440 proceeds to Figure 4 450 in the box.

[0115] Returning to block 450, Figure 4 In the example, the account management system 160 creates an audio template associated with the user 101 account. Figure 6 The method 450 described in more detail describes a method for establishing an audio template associated with the user 101 account.

[0116] Figure 6 is a block diagram illustrating a method 450 for establishing an audio template associated with a user 101 account according to certain examples. Figure 1 The components illustrated in FIG. 4 describe method 450 .

[0117] In block 610, payment application 113 displays a request to user 101 via user computing device 110 to capture an audio recording of user 101's voice. In the example, payment application 113 displays the request via user interface 115. In the example, user interface 115 may display a request that reads, "To enable hands-free transactions, we need recording of your voice. Would you like to submit a audio recording now?" In this example, user 101 may select an option to submit a live audio recording, or may otherwise select a pre-recorded audio recording of user 101 stored on user computing device 110.

[0118] In block 620, the user 101 selects an option to capture an audio recording. For example, the user 101 activates an object on the user interface 115 that reads "yes, I would like to submit a audio recording now."

[0119] In block 630, payment application 113 activates an audio module (not depicted) on user computing device 110, and user 101 captures audio of user 101's voice. In an example, user computing device user interface 115 may display guidelines received from account management system 160 to assist user 101 in submitting the audio recording. For example, payment application 113 may display instructions for user 101 to record user 101's voice speaking user 101's name. In another example, payment application 113 instructs user 101 to capture the audio recording to establish a voice password that can be used in user 101's hands-free transactions. In an example, user 101 may actuate an object on user interface 115 to capture or record a live audio recording. In this example, in response to the user actuating an object on user interface 115, the audio module receives a command from payment application 113 to capture the audio recording of user 101. In an example, account management system 160 may establish guidelines for the user in submitting the audio recording. For example, payment application 113 may instruct user 101 to submit an audio recording that is no longer than a predefined maximum duration. For example, the audio recording must not exceed five seconds. In another example, the payment application 113 may instruct the user 101 to submit an audio recording that lasts for a predetermined length of time, for example, five seconds. In this example, after the user 101 initiates the audio recording by actuating an object in the user interface 115, after the predefined length of time or the predefined maximum length has expired, the payment application 113 transmits a command to the audio module to stop recording the user's 101 voice.

[0120] In block 640, the account management system 160 receives the audio recording of the user 101's voice. For example, the payment application 113 or the audio module transmits the audio recording to the account management system 160 via the network 180. In another example, the payment application 113 retrieves the audio recording selected by the user 101 and saved in the data storage unit 116, and transmits the retrieved audio recording to the account management system 160 via the network 180.

[0121] In block 650, account management system 160 creates an audio template associated with user 101's voice based on the received audio of the user's voice. In this example, the audio template has a predetermined size. In this example, account management system 160 generates the audio template including a computer code representation of the audio recording of user 101. For example, the audio template may describe key features of the audio recording of user 101, such as the intonation of user 101's voice or other characteristics of user 101's voice. In this example, account management system 160 stores the generated audio template associated with user 101 in data storage unit 166 associated with account management system 160. For example, the account management system 160 database may include a table or other means by which each user 101 account identifier is associated with a corresponding audio template for user 101.

[0122] At block 660, account management system 160 deletes the received audio of user 101's voice. In an example, account management system 160 deletes the received audio recording of user 101 to protect the privacy of user 101. For example, account management system 160 uses only the audio template that includes the computer code representation of the audio recording of user 101.

[0123] From block 660, method 440 proceeds to Figure 2 230 in the FIG.

[0124] Returning to block 230, Figure 2 In one embodiment, user 101 enters a merchant system location and logs into payment application 113 on user computing device 110. In another example, user 101 logs into payment application 113 before entering the merchant system location and enters the merchant location with user computing device 110 logged into payment application 113.

[0125] In block 240, the user device receives the merchant beacon device 120 identifier. Figure 7 The method 240 described in more detail describes a method for receiving, by a user computing device 110, a merchant beacon identifier broadcast by a merchant beacon device 120 .

[0126] Figure 7 is a block diagram illustrating a method 240 for receiving, by a user computing device 110, a merchant beacon identifier broadcast by a merchant beacon device 120, according to certain examples. Figure 1 The components illustrated in FIG. 240 describe the method.

[0127] In block 710, user 101 logs into payment application 113 on user computing device 110. In an example, user 101 may have a username and password associated with user 101's account maintained by account management system 160. In an example, user 101 opens payment application 113 on user computing device 110 and enters the username and / or password via user interface 115 to log into payment application 113. In an example, when user 101 is logged into payment application 113, payment application 113 is able to communicate with account management system 160 via network 180. In this example, when user 101 is not logged into payment application 113, payment application 113 does not communicate with account management system 160, even if network 180 connectivity is available. In an example, user 101 can log out of payment application 113 at any time by actuating one or more objects on user interface 115 of user computing device 110. In an example, after logging into the payment application 113, the user 101 configures one or more user 101 account settings, adds, edits, or deletes user 101 payment account information, and / or changes user 101 preferences. In some examples, the user 101 may be required to perform feature selections to benefit from the techniques described herein. For example, the user 101 may have to enable one or more user 101 account settings to enable hands-free transactions according to the methods described herein.

[0128] In an example, payment application 113 may provide user 101 with options, data, configurable alerts, and other suitable features. For example, payment application 113 may include a list of merchant systems and merchant locations that participate in hands-free payment transactions according to one or more of the methods described herein. The list may be periodically updated by account management system 160. Payment application 113 may notify user 101 when user 101 is within a configured proximity of a participating merchant system. Payment application 113 may provide user 101 with the option to update payment preferences. Payment application 113 may provide user 101 with a list of recent transactions. Payment application 113 may provide user 101 with any other suitable information.

[0129] In block 720, user 101 brings user computing device 110 within a threshold distance of merchant beacon device 120 at a merchant system location. In an example, user 101 enters the location of the merchant system. User 101 can enter the merchant location with user computing device 110 in a pocket or bag, in the hand of user 101, or in any suitable manner. The location of the merchant system can be a store location, a self-service terminal location, or any suitable physical location of the merchant system. In another example, merchant POS operator 102 can be mobile and arrive at the location of user 101. For example, the merchant system can be a restaurant and merchant POS device operator 102 can be a delivery person with a portable merchant point of sale device 130.

[0130] In some examples, payment application 113 may alert user 101 when user 101 is near a merchant system that accepts hands-free payments. The alert may be provided via a message on user computing device 110, via email, text, or in any other suitable manner. In one example, the alert may be based on user 101's location, as determined by a GPS module (not shown) residing on user computing device 110. For example, payment application 113 accesses GPS data from the GPS module and compares the GPS location to a list of locations of merchant systems that accept hands-free payments. For example, payment application 113 includes a list or accesses a list maintained by account management system 160 of merchant system locations that accept hands-free payments. If a match is generated from the comparison, an alert is generated and provided to user 101. A match may be generated if user 101 is within a configured distance of a qualifying merchant system location. In one example, the alert may be configured to alert in any suitable manner. In one example, the alert may be combined in a commercially dense environment, or the alert may be presented individually. In another example, the alert may be configured to alert only a number of times configured by user 101. For example, the alert may be presented three times, but not the fourth time. The alert may be presented as a notification with an audible alert, a vibration, a pop-up alert on the user interface 115 of the user computing device 110, or other suitable alert.

[0131] In block 730, the user computing device 110 receives a merchant beacon identifier broadcast by the merchant beacon device 120. The user computing device 110 identifies the merchant beacon device 120 via wireless communication at the location of the merchant system. The user computing device 110 can be configured to search for beacons or other wireless signals. In an example, the user computing device 110 and the merchant beacon device 120 establish a BLE wireless network 180 connection. In other examples, the user computing device 110 and the merchant beacon device 120 establish a Bluetooth, Wi-Fi, NFC, or other suitable network 180 connection. After entering the signal range of the merchant beacon device 120, the user computing device 110 receives the merchant beacon identifier.

[0132] In block 740, user computing device 110 transmits the received merchant beacon identifier and user 101 account identifier to account management system 160. In an example, user computing device 110 transmits the data received in the merchant beacon identifier along with the user 101 account identifier to account management system 160 over network 180.

[0133] In block 750, the account management system 160 receives the merchant beacon identifier and the user 101 account identifier. For example, the account management system 160 receives the merchant beacon identifier and the user 101 account identifier via the network 180. The user computing device 110 may compare data from the merchant beacon identifier to a database of merchant beacon identifier data and merchant camera device identifier data to determine the identity of the merchant system and the camera module 132 of the merchant point of sale device 130 associated with the merchant beacon identifier and / or verify the authenticity of the beacon.

[0134] From block 750, method 240 proceeds to Figure 2 250 in the box.

[0135] Return to Figure 2 In block 250, the merchant point-of-sale device 130 receives a facial template of each user 101 within range of the merchant beacon device 120. Figure 8 The method 250 described in greater detail describes a method for receiving, by the camera module 132 of the merchant point of sale device 130, facial templates for various users 101 within range of the merchant beacon device 120. In other examples, in addition to or in lieu of receiving facial templates, the merchant point of sale device 130 receives audio templates and / or challenges and responses associated with the user 101 account.

[0136] Figure 8 is a block diagram describing a method 250 for receiving a facial template for each user 101 within range of a merchant beacon device 120 by a camera module 132 of a merchant point of sale device 130, according to certain examples. Figure 1 In other examples, in addition to or instead of receiving a facial template, the merchant point of sale device 130 receives an audio template and / or a challenge and response associated with the user 101 account according to similar methods.

[0137] In block 810, the account management system 160 retrieves a facial template, an audio template, and / or a challenge and response associated with the user 101 account identifier. In an example, the account management system 160 accesses a database containing stored facial templates for a plurality of users 101, each with a corresponding user 101 account identifier for each user 101. This database is stored, for example, in the data storage unit 166. In another example, the account management system 160 retrieves an audio template and / or a challenge and response from the database instead of or in addition to the facial template.

[0138] In block 820, account management system 160 generates a payment token for the user's payment account and notifies the issuer system of the association of the payment token with the user's payment account. In this example, account management system 160 generates a payment token for each user 101 whose user computing device 110 is within network range of a merchant beacon device 120 and logged into a payment application 113. The example payment token includes a series of alphanumeric and / or symbolic characters. The example payment token can be associated with user 101's payment account and can be recognized by issuer system 150 associated with user 101's payment account. For example, account management system 160 generates the payment token and communicates the payment token and user 101's payment account information to issuer system 150 associated with the user's payment account. In this example, if issuer system 150 later receives the payment token from a merchant point-of-sale device 130 in a payment transaction after receiving the payment token from account management system 160, issuer system 150 can retrieve user 101's payment account information associated with the payment token.

[0139] In some examples, account management system 160 may impose restrictions on the payment token for security reasons or based on one or more configurations of user 101's account desired by user 101. For example, a payment token may only be valid for a preconfigured length of time (e.g., one hour). In another example, a payment token may only be valid for transactions between user 101 and a specific merchant system. In yet another example, a payment token is only valid within specific geographic boundaries or within a threshold distance from a geographic point. In an example, account management system 160 communicates one or more of these exemplary restrictions along with the payment token to issuer system 150, and issuer system 150 associates these one or more restrictions with the payment token and payment account data of user 101 in a database of issuer system 150. In an example, account management system 160 may communicate a current timestamp representing the time when the payment token was generated to associate the payment token along with the payment token and user 101 account data to issuer system 150. In another example, the account management system 160 may communicate location data describing a geographic boundary and / or a threshold distance from a geographic point at which the payment token may be used in a transaction, along with the payment token and the user 101 account data, to the issuer system 150. In yet another example, the account management system 160 may communicate a merchant system identifier and an indication that only payment authorization requests originating from merchant systems that include the merchant system identifier may be approved, along with the payment token and the user 101 account data, to the issuer system 150. In an example, the issuer system 150 associates the payment token, the user 101 payment account data associated with the payment token, one or more restrictions imposed on the payment token by the account management system 160, and / or one or more location data, timestamp data, merchant system identifier data, or other data that the issuer system 150 may use to determine whether one or more restrictions on the payment token are satisfied to enable use of the payment token.

[0140] In block 830, the account management system 160 identifies the merchant point-of-sale device 130 associated with the merchant beacon device 120 identifier. In an example, the account management system 160 identifies that the merchant beacon identifier is associated with the account management system 160 and a particular merchant point-of-sale device 130 at the merchant system location. In an example, the account management system 160 identifies that the merchant beacon identifier is associated with multiple merchant point-of-sale devices 130 installed at the particular merchant location.

[0141] In block 840, the account management system 160 transmits the identified facial template of user 101, the identified audio template of user 101, and / or the challenge and response associated with the identified user 101, along with the generated payment token, to a merchant point-of-sale device 130 associated with the merchant beacon device 120 identifier. In another example, the account management system 160 transmits the identified facial template of user 101 and the generated payment token to multiple merchant point-of-sale devices 130 associated with the merchant beacon device 120 identifier. In some examples, the account management system 160 receives, in real time, multiple transmissions from user computing devices 101 corresponding to multiple users 101 present at a merchant system location, each transmission including a user 101 account identifier and a retransmitted merchant beacon identifier. In these examples, in response to receiving each such transmission, the account management system 160 retrieves the facial template associated with the received user 101 account identifier and transmits the facial template to one or more merchant point-of-sale devices 130 at the merchant location associated with the merchant beacon identifier. In other examples, in addition to or instead of transmitting the facial template, the account management system 160 transmits the audio template and / or the challenge and response associated with the user 101 account to one or more merchant point of sale devices 130 .

[0142] In block 850, the merchant point-of-sale device 130 receives a facial template for user 101. In another example, in addition to or in lieu of receiving the facial template, the merchant point-of-sale device 130 receives an audio template and / or a challenge and response associated with the account of user 101. In another example, multiple merchant point-of-sale devices 130 receive the facial template for user 101. In yet another example, according to methods previously described herein, the merchant point-of-sale device and / or multiple merchant point-of-sale devices 130 receive one or more additional facial templates, audio templates, and / or challenges and responses from an account management system 160 corresponding to one or more users 101 other than the instant user 101 connected to the user computing device 110 and the merchant beacon device 120 in the network 180. For example, when additional users 101 other than the instant user 101 receive a merchant beacon device 120 identifier via the wireless communication network 180 or otherwise establish a network 180 connection between their user computing device 110 and one or more merchant beacon devices 120, one or more additional facial templates, audio templates, and / or challenges and associated responses are received in real time from the account management system 160. For example, one or more merchant point of sale devices 130 may receive the one or more additional facial templates, audio templates, and / or challenges and responses corresponding to the one or more additional users 101 at a time before, simultaneously with, or after the merchant point of sale device 130 receives the facial template of the instant user 101.

[0143] In block 860, the merchant point-of-sale device 130 adds the facial template of user 101 to the current customer log. In an example, the merchant point-of-sale device 130 adds the audio template and / or the challenge and response associated with user 101 in addition to or in lieu of the facial template of user 101. In an example, the current customer log is accessible to the merchant point-of-sale device 130 and the account management system 160. In an example, the merchant point-of-sale device 130 maintains the current customers logged in on the merchant point-of-sale device 130 or on a computing device logically connected to the merchant point-of-sale device 130.

[0144] In block 870, the merchant point of sale device 130 periodically updates the current customer log. Figure 9 The method 860 described in more detail describes a method for updating the current customer log via the merchant point of sale device 130 when the user 101 enters or leaves the network range of the merchant beacon device 120.

[0145] Figure 9 is a block diagram illustrating a method 870 for receiving notifications from an account management system 160 via a camera module 132 of a merchant point of sale device 130 when a user 101 enters or leaves the network range of a merchant beacon device 120, according to certain examples. Figure 1 The components illustrated in FIG. 8 describe method 860 .

[0146] In block 910, when user 101, who is logged into a payment account, enters or leaves the network range of a merchant beacon device 120, the account management system 160 notifies the merchant point-of-sale device 130. For example, as previously described, when user 101, carrying user computing device 110, enters a threshold distance from a merchant beacon device 120, the merchant beacon device 120 or user 101's user computing device 110 can detect the other device and establish a wireless network 180 connection between the two devices at the merchant system's location. In this example, the merchant beacon device 120 transmits a merchant beacon identifier corresponding to the merchant beacon device 120 to the user computing device 110 via the wireless network 180. For example, the merchant beacon device 120 transmits the merchant beacon identifier to the user computing device 110 via a BLE, Bluetooth, Wi-Fi, or NFC wireless communication network 180. In this example, the user computing device 110 retransmits the received merchant beacon identifier to the account management system 160 along with the user 101 account identifier identifying the user.

[0147] In block 920, account management system 160 determines whether new user 101 is within range of merchant beacon device 120. For example, if account management system 160 receives a new user 101 account identifier in addition to the same merchant beacon identifier, account management system 160 may determine that new user 101 is within range of merchant beacon device 120. In this example, account management system 160 may infer that new user 101 has entered the merchant location based on receipt of the new user 101 account identifier. In another example, if account management system 160 does not receive any new user 101 account identifiers with the same merchant beacon identifier within a threshold length of time, account management system 160 may determine that no new user 101 has entered range of network 180 of merchant beacon device 120.

[0148] If the new user 101 is within range of the merchant beacon device 120, the method 860 proceeds to Figure 8 830 in the example. For example, in addition to the same merchant beacon identifier, the account management system 160 receives the new user 101 account identifier. In this example, the account management system 160 infers that the new user 101 has entered the merchant location based on the receipt of the new user 101 account identifier and the same merchant beacon identifier previously received from the first user 101.

[0149] return Figure 8 In block 810, the account management system 160 extracts a facial template associated with the new user 101 account identifier. In another example, in addition to or in lieu of the facial template associated with the new user 101, the account management system 160 extracts an audio template and / or a challenge and response associated with the new user 101. For example, the account management system 160 transmits the facial template, audio template, and / or challenge and response to the appropriate one or more merchant point of sale devices 130, and the one or more merchant point of sale devices 130 process the facial template, audio template, and / or challenge and response based on the previously generated facial template. Figure 8 The example method described in method 250 in adds a new user 101 facial template, audio template and / or challenges and responses to the current customer log.

[0150] return Figure 9 At block 920, if there is no new user 101 within range of the merchant beacon device 120, the method 860 proceeds to block 930. For example, the account management system 160 does not receive any new user 101 account identifier and the same merchant beacon identifier within the threshold time length and determines that no new user 101 has entered the network 180 range of the merchant beacon device 120.

[0151] In block 930, the camera module 132 of the merchant point-of-sale device 130 determines whether the current user 101 has moved out of range of the merchant beacon device 120. In an example, the user computing device 110 continues to receive the merchant beacon identifier from the merchant beacon device 120 and retransmits the merchant beacon identifier along with the user 101 account identifier to the account management system 160. In this example, the user computing device 110 may periodically transmit information including the merchant beacon identifier and the user 101 account identifier to the account management system 160 as long as the user computing device 110 continues to detect the merchant beacon device 120 and receive the merchant beacon device 120 identifier via periodic scanning. For example, the user computing device may scan the merchant beacon device 120 every five seconds. In another example, the user computing device 110 may periodically transmit information including the merchant beacon identifier and the user 101 account identifier to the account management system 160 as long as the user computing device 110 maintains a wireless network 180 connection to the merchant beacon device 120. For example, the user computing device 110 may transmit this information to the account management system 160 every five seconds. In this example, if the account management system 160 stops receiving information from the user computing device at a predefined number of intervals, the account management system 160 may determine that the corresponding user 101 has moved out of range of the merchant beacon device. In this example, if the account management system 160 continues to receive information transmitted by the user computing device 110 at the expected intervals, the account management system 160 determines that the user 101 is still within the range of the merchant beacon device 120 network 180.

[0152] If the current user 101 has not moved out of the range of the merchant beacon device 120, the method 860 proceeds to Figure 2 For example, the account management system 160 continues to receive the merchant beacon identifier and the user 101 account identifier transmitted by the user computing device 110 at expected intervals and determines that the user 101 is still within the network 180 range of the merchant beacon device 120.

[0153] Returning to block 260, Figure 2 In FIG, user 101 initiates a transaction at a merchant point-of-sale device 130 .

[0154] return Figure 9 , in block 930 , if the current user 101 has moved out of range of the merchant beacon device 120 , the method 860 proceeds to box 940 .

[0155] In block 940, camera module 132 of merchant point of sale device 130 receives a notification from account management system 160 that current user 101 is out of network range of merchant beacon device 120. In another example, merchant point of sale device 130 receives a notification from account management system 160 that user computing device 110 associated with current user 101 has stopped transmitting notifications including an identifier of merchant beacon device 120 to account management system 160. For example, merchant point of sale device 130 receives a user 101 account identifier associated with current user 101, user 101 associated with user computing device 110 that is out of network range or has stopped transmitting notifications including an identifier of merchant beacon device 120 to account management system 160, accesses a current customer log, and locates an entry corresponding to current user 101. For example, the current customer log is maintained by account management system 160, and merchant point of sale device 130 accesses the current customer log via network 180 by communicating with account management system 160. In another example, account management system 160 does not transmit a notification that current user 101 is out of network range to merchant point of sale device 130. In this example, account management system 160 accesses the current customer log and deletes the facial template of current user 101 from the current customer log. In another example, in addition to deleting the facial template of current user 101 from the current customer log, merchant point of sale device 130 also deletes the challenge and response and / or audio template associated with current user 101 from the current customer log.

[0156] In block 950, the merchant point-of-sale device 130 deletes the facial template of the current user 101 from the current customer log. For example, the current customer log includes a table, and the merchant point-of-sale device 130 deletes or requests deletion of an entry or row corresponding to data associated with the current user 101 of which the merchant point-of-sale device 130 received notification. In another example, in addition to the facial template of the current user 101, the merchant point-of-sale device 130 deletes the associated audio template and / or associated challenges and responses of the current user 101 from the current customer log. In another example, the account management system 160 accesses the current customer log and deletes the facial template, audio template, and / or challenges and responses of the current user 101 from the current customer log.

[0157] From block 950, method 860 proceeds to Figure 2 260 in the box.

[0158] return Figure 2 In block 260, user 101 initiates a transaction at the merchant point of sale device 130. Figure 10The method 260 described in greater detail in the accompanying drawings describes a method for initiating a transaction by user 101 at a merchant point of sale device 130. In the example described herein, user 101 initiates a "hands-free transaction" at a merchant point of sale device 130. The example hands-free transaction does not require any interaction on the part of user 101 with user computing device 110. In another example, the hands-free transaction requires only minimal interaction on the part of user 101 with user computing device 110.

[0159] Figure 10 is a block diagram depicting a method 260 for initiating a transaction at a merchant point of sale device 130 by a user 101, according to certain examples. Figure 1 Method 260 is described with reference to the components illustrated in FIG.

[0160] In block 1010, user 101 approaches merchant point of sale device 130. In an example, user 101 browses the merchant system location and selects one or more items to purchase prior to approaching merchant point of sale device 130. In this example, user 101 may collect the one or more items and carry or otherwise transport the one or more items to merchant point of sale device 130 via a physical basket or shopping cart.

[0161] In block 1020, the merchant point of sale device 130 operator 102 totals the items to be purchased by the user 101. In the example, the merchant POS device operator 102 scans a barcode attached to one or more items or otherwise enters a description and price associated with the one or more items into the merchant point of sale device 130. In the example, after scanning or manually entering the items into the merchant point of sale device 130, the merchant POS device operator 102 activates an object on the user interface 135 of the merchant point of sale device 130 to instruct the merchant point of sale device 130 to total the items. In the example, the merchant point of sale device 130 displays the total to the user 101 via the user interface 135.

[0162] At block 1030, the operator of the merchant point of sale device 130 requests that the user 101 select a payment option. In the example, the merchant point of sale device 130 displays one or more payment options that the user 101 can select to use in the transaction. Example payment options may include payment via a payment application 113 associated with the account management system 160, cash payment, check payment, credit card payment, debit card payment, and / or any other payment method that the merchant system is able or willing to accept from the user 101. In the example, the one or more payment options are displayed as objects on the user interface 135 and are selectable by the merchant POS device operator 102 in response to the user 101 directing the operator of the merchant POS device 102 to make a selection.

[0163] In block 1040, user 101 directs merchant point of sale device operator 102 to initiate a transaction via payment application 113. In the example, in response to receiving a verbal request from user 101 to select payment application 113 as a payment option, merchant POS device operator 102 actuates an object on user interface 135 of merchant point of sale device 130 that corresponds to the payment application 113 payment option.

[0164] In block 1050, the merchant point of sale device operator 102 selects an option on the merchant point of sale device 130 to initiate a transaction using the payment application 113. In the example, the merchant point of sale device 130 displays a confirmation screen after the merchant POS device operator 102 selects the option to initiate the transaction using the payment application 113. The example confirmation screen may display information summarizing the potential transaction and including one or more of the transaction total, a description of the one or more items that the user 101 is purchasing, and an indication that the user 101 has selected the payment application 113 as the payment method for the transaction. The example confirmation screen may also display an option to confirm the transaction or cancel the transaction. In the example, the user 101 reviews the confirmation screen, determines that the information displayed on the confirmation screen is correct, determines to proceed with the transaction, and directs the merchant POS device operator 102 to select the option to confirm the transaction via the user interface 135.

[0165] From block 1050, method 260 proceeds to Figure 2 270 in the box.

[0166] return Figure 2 In block 270, the merchant point of sale device 130 identifies the user 101 via facial recognition. Figure 11 The method 270 described in more detail describes a method for identifying the user 101 via facial recognition by the merchant point of sale device 130. In other examples, the merchant point of sale device 130 identifies the user 101 via audio recognition and / or via a challenge and response.

[0167] Figure 11 is a block diagram illustrating a method 270 for identifying a user 101 via facial recognition by a merchant point of sale device 130, according to certain examples. Figure 1 The components illustrated in FIG. 270 describe the method.

[0168] In block 1110, camera module 132 of merchant point-of-sale device 130 captures video of user 101. In an example, in response to receiving a request to identify user 101, merchant point-of-sale device 130 activates camera module 132 to begin capturing video of the surroundings of merchant point-of-sale device 130. In an example, merchant point-of-sale device 130 captures a video feed of user 101's face. In another example, camera module 132 continuously captures but does not record a video feed of its surroundings. In this example, when merchant point-of-sale device 130 receives input from merchant point-of-sale device 130 operator 102 and a request to identify user 101 from account management system 160, camera module 132 begins recording the video feed for a threshold amount of time. In an example, user 101 may be mobile during the period in which camera module 132 records the video feed. In an example, camera module 132 extracts a facial image by determining a particular frame of the video feed and an area within the instance of the video feed that corresponds to the user's face.

[0169] In block 1120, the camera module 132 extracts a facial image of the user 101 from the captured video. In an example, the camera module 132 determines a frame of the captured video to provide an image of the face of the user 101, and extracts a frame of the captured video including the facial image of the user 101.

[0170] In some other examples, camera module 132 identifies frames of captured video to provide images of the faces of multiple users 101. For example, the frames include facial images of a first user 101, a second user 101, and a third user 101 at different locations in the image. In this example, one camera module 132 associated with a particular merchant point-of-sale device 130 may capture video of an environment corresponding to an area proximate to the multiple merchant point-of-sale devices 130. In this example, camera module 132 may identify the specific merchant point-of-sale device 130 corresponding to each of the multiple faces of the multiple users 101 in the captured image.

[0171] In block 1130, camera module 132 generates a facial template from the captured facial image. In another example, merchant point-of-sale device 130 generates the facial template. In one example, the facial template has a predetermined size, for example, a 128-byte facial template. In one example, account management system 160 generates the facial template including a computer code representation of the digital facial image. For example, the facial template may describe key features of user 101's facial image, such as shape, color, line, value, space, form, texture, or other useful or relevant features of the image or other useful or relevant features of a characteristic region of the image. In another example, the facial template is generated by processing the facial image via a convolutional neural network. In one example, camera module 132 stores the generated facial template in data storage unit 136 associated with merchant point-of-sale device 130. For example, a camera module 132 database may include a log of facial templates of current customers, where merchant point-of-sale device 130 stores the generated facial templates.

[0172] In certain other examples, camera module 132 continuously captures a video feed of user 101's surroundings as user 101 enters and exits the vicinity of one or more merchant point-of-sale devices 130 within a specific time period. In this example, merchant point-of-sale device 130 and / or camera module 132 are capable of continuously monitoring the incoming video feed to detect faces from extracted frames of the video feed. In this example, each time camera module 132 detects the presence of one or more faces in the video feed, camera module 132 extracts a frame of the video feed that includes one or more facial images of the corresponding detected faces and creates a facial template based on the extracted facial images. In this example, merchant point-of-sale device 130 stores the facial templates in a log of facial templates for the current customer as they are generated. In this example, when camera module 132 or merchant point-of-sale device 130 generates a subsequent facial template, merchant point-of-sale device 130 determines whether the generated subsequent facial template is similar to within a threshold value compared to any facial templates already stored in the log of facial templates for the current customer. If the generated subsequent facial template is similar to any facial template already stored in the log within a threshold, then, after associating the facial template with one or two specific merchant point-of-sale devices 130 based on the location of the associated facial image in the extracted frame of the captured video, the merchant point-of-sale device adds the facial template to the log of facial templates for the current customer. If the generated subsequent facial template is not similar to any facial template already stored in the log of facial templates for the current customer within a threshold, the merchant point-of-sale device 130 deletes or otherwise ignores and / or performs no action on the generated facial template. In this example, if the merchant point-of-sale device 130 determines that a facial image is no longer in the video feed, the corresponding facial template is deleted from the log of facial templates for the current customer.

[0173] At block 1140, camera module 132 deletes the captured video and extracted facial image. For example, camera module 132 does not store the captured image or video. In this example, the facial template generated by camera module 132 includes a computer code representation of the facial image of user 101. In this example, camera module 132 of merchant point of sale device 130 deletes any captured or extracted video or image after the facial template is generated or after a threshold time has elapsed after capturing or extracting a video or image.

[0174] In block 1150 , the merchant point of sale device 130 retrieves a facial template from the current customer log. For example, the current customer log includes facial templates received from the account management system 160 corresponding to all current users 101 whose associated user computing devices 110 are within network distance of the merchant beacon device 120 .

[0175] In block 1160 , the merchant point of sale device 130 compares the generated facial template from the captured facial image with facial templates from the current customer log.

[0176] In block 1170 , the merchant point of sale device 130 determines whether there is a match between the generated facial template and one of the facial templates from the current customer log.

[0177] If the facial template from the current client log matches the generated facial template, the method 270 proceeds to Figure 2 295. For example, the merchant point of sale device 130 processes the transaction.

[0178] Returning to block 1170, if none of the facial templates from the current client log matches the generated facial template, the method 270 proceeds to Figure 2 In another example, if no face template log from the current customer's log matches any face template from the current customer's log of face templates, the method 270 proceeds to Figure 2 280 in the box.

[0179] Returning to block 280, Figure 2 In another example, the merchant point of sale device 130 recognizes the user 101 via voice recognition. In another example, the account management system 160 does not recognize the user 101 via voice recognition and continues to recognize the user 101 via challenge and response. For example, the camera module 132 of the merchant point of sale device 130 and / or the account management system 160 cannot recognize the user via facial recognition and / or whether the camera module 132 of the merchant point of sale device 130 and / or the account management system 160 recognizes two or more users 101 via facial recognition. Figure 12 The method 280 described in more detail describes a method for identifying the user 101 by the account management system 160 via voice recognition.

[0180] Figure 12 is a block diagram illustrating a method 280 for identifying a user 101 via voice recognition by the account management system 160 according to certain examples. Figure 1 The components illustrated in FIG. 280 describe the method.

[0181] In some examples, it may be necessary to identify user 101 via voice recognition because merchant point-of-sale device 130 is unable to identify user 101 based on facial recognition. For example, merchant camera module 132 may be unable to extract an appropriate facial image of user 101 from a video feed to generate a facial template. In another example, merchant point-of-sale device 130 cannot find a match for user 101's facial template in the current customer log. In yet another example, merchant point-of-sale device 130 identifies a matching user 101 facial template in the current customer log, however, the identified user 101 facial template is assigned to two adjacent merchant point-of-sale devices 130. In this example, user 101 may have to identify himself via voice recognition at the merchant point-of-sale device 130 where user 101 initiates the transaction.

[0182] In block 1210 , the merchant point of sale device 130 transmits a notification to the account management system 160 that the user 101 cannot be identified.

[0183] In block 1220, merchant point-of-sale device 130 retrieves an audio template corresponding to user 101 from the current customer log. As previously described, when user 101 establishes an account with merchant point-of-sale device 130, user 101 may submit an audio recording of user 101's voice to merchant point-of-sale device 130. In this example, merchant point-of-sale device 130 establishes an audio template corresponding to user 101 based on the received audio recording. In another example, user 101 does not submit an audio recording to merchant point-of-sale device 130 when user 101 establishes user 101's account. In this other example, merchant point-of-sale device 130 does not have an audio template associated with user 101's account and cannot authenticate user 101 through voice recognition.

[0184] In block 1230, the merchant point of sale device 130 transmits a request to the merchant system point of sale device to record the audio of the user 101. For example, the merchant point of sale device 130 transmits the request over the network 180.

[0185] In block 1240, the merchant system point of sale device displays a request for user 101 to record audio. For example, the merchant system POS device may display instructions for recording the audio recording to user 101. For example, user 101 may be instructed to speak the same words in the same intonation that user 101 spoke when the audio template was established with account management system 160 when setting up user 101's account.

[0186] In block 1250 , the merchant system point of sale device records the voice input of the user 101 . For example, the merchant POS device operator 102 may actuate an object on the user interface 135 to activate the audio module 131 to receive the audio input of the user 101 .

[0187] In block 1260, the merchant point of sale device 130 compares the received voice input to the audio template corresponding to the user 101 retrieved from the current customer log. For example, the merchant point of sale device 130 receives the audio input of the user 101.

[0188] In block 1270, the merchant point-of-sale device 130 determines whether a match exists between the received voice input and one of the audio templates retrieved from the current customer log. In an example, the merchant point-of-sale device 130 compares one or more features between the received voice input and each retrieved audio template from the current customer log. In an example, if the similarity between the received voice input and the particular audio template exceeds a predefined threshold, the merchant point-of-sale device 130 determines that the received voice input matches the particular audio template. In another example, if the similarity between the received voice input and the particular audio template is less than a predefined threshold, the merchant point-of-sale device 130 determines that the received voice input does not match the particular audio template.

[0189] If the audio template from the current customer log matches the received voice input, method 270 proceeds to block 1280. For example, the similarity between a particular audio template from the current customer log and the received audio recording of user 101 exceeds a predefined threshold and merchant point of sale device 130 determines that there is a match.

[0190] Returning to block 1270, if none of the audio templates from the current client log matches the received speech input, the method 280 proceeds to Figure 2 In another example, the merchant point of sale device 130 cannot receive the audio recording of the user 101 or the received audio recording of the user 101 is insufficient and cannot be used to identify the user 101.

[0191] return Figure 2 , in block 295, the merchant system POS operator 102 identifies the user 101 via the challenge and response. Figure 13 The method 290 described in more detail describes a method for a merchant point of sale device operator 102 to identify a user 101 via a challenge and response.

[0192] Figure 13 is a block diagram depicting a method 290 for identifying a user 101 via a challenge and response by a merchant point of sale device operator 102, according to certain examples. Figure 1 The components illustrated in FIG. 290 describe the method.

[0193] In block 1310, point-of-sale device operator 102 issues a challenge to user 101. In one example, merchant POS device operator 102 asks user 101 for user 101's initials. In another example, merchant POS device operator 102 asks user 101 for the last four digits of user 101's phone number. In another example, merchant POS device operator 102 asks user 101 for a configured password. Merchant POS device operator 102 may issue any suitable challenge. In this example, the response to the challenge does not provide any secure or private information.

[0194] In block 1320, user 101 provides a challenge response. As described in the example challenge, the response can be user 101's initials, the last four digits of user 101's phone number, or a configured password. Any configured challenge response can be utilized. In some embodiments, the response can be a verbal response, a gesture, a keypad entry, the display of an identification card, or any suitable response.

[0195] In block 1330, point of sale device operator 102 enters a response into merchant point of sale device 130. Merchant POS device operator 102 enters a challenge response for user 101. In the example, if user 101 indicates that user 101's initials are "AC," merchant POS device operator 102 enters "AC" into payment application 133 of merchant point of sale device 130. In the example, user interface 135 of merchant point of sale device 130 displays a request to enter user 101's response. Merchant POS device operator 102 enters the response via a virtual or physical keyboard, voice dictation, or in any suitable manner. In an alternative example, user 101 enters the response into user interface 135 of merchant point of sale device 130.

[0196] In block 1340, the merchant point of sale device 130 displays the potential users 101 based on the challenge responses. The merchant point of sale device 130 displays the potential users 101 based on the challenge responses. A list of users 101 associated with the challenge responses is displayed on the merchant point of sale device 130 to the merchant POS device operator 102. For example, if ten customers are near the merchant beacon device 120, the merchant point of sale device 130 may receive a challenge response associated with each of the ten customers from the account management system 160. When the merchant point of sale device 130 receives a challenge response input, only the potential users 101 associated with the challenge responses are displayed to the merchant POS device operator 102.

[0197] In another embodiment, the merchant point of sale device 130 or account management system 160 processing the challenge presents additional challenges until there is a single matching user 101 remaining.

[0198] In the example, if merchant POS device operator 102 enters "AC" as the initials of user 101 associated with the transaction, only potential users 101 with those initials will be displayed to merchant POS device operator 102 via payment application 133. Payment application 133 accesses an account management system 160 or a database on another computing device and identifies the initials of the potential users 101 who have provided a token. Payment application 133 identifies one or more potential users 101 with the initials "AC" and displays the identified user 101 accounts to merchant POS device operator 102. In the example, two of ten customers located near merchant beacon device 120 have the initials "AC." The user 101 accounts of both customers are displayed to merchant POS device operator 102.

[0199] In some examples, all nearby customers who have had tokens transferred to merchant point of sale device 130 are presented to merchant POS device operator 102, and merchant POS device operator 102 selects the appropriate user 101 account.

[0200] The payment application 133 can display pictures of potential user 101 accounts presented to the merchant POS device operator 102. For example, each user 101 can associate a picture with a user 101 account. When the merchant point of sale device 130 presents one or more potential user 101 accounts to the merchant POS device operator 102, the merchant POS device operator 102 can select the appropriate user 101 account based on the picture that matches the user 101 conducting the transaction. Other identifying information can be presented instead of or in addition to the picture. For example, the user 101's name can be displayed, and the merchant POS device operator 102 can identify the potential user 101 by that name. Any other suitable identifying information can be presented.

[0201] In block 1350, merchant point of sale device operator 102 selects user 101 account to use in the transaction. After identifying the displayed picture of user 101, merchant POS device operator 102 may input user 101's selection by actuating a user interface 135 control associated with the picture, or by inputting the selection in any suitable manner. If the picture does not match any potential user, merchant POS device operator 102 may cancel the transaction, notify user 101 of the discrepancy, or perform any other suitable action.

[0202] In this example, only a single user 101 account is presented in the list of potential users 101. If only a single user 101 account is identified, the method can continue after merchant POS device operator 102 verifies that the displayed picture matches the user. If the picture does not match, merchant POS device operator 102 can cancel the transaction, notify user 101 of the discrepancy, or perform any other suitable action.

[0203] From block 1350, method 290 proceeds to Figure 2 Box 295 in.

[0204] return Figure 2 , in block 295, the transaction is processed. Figure 14 Method 295a and Figure 15 Method 295b described in more detail describes the method for processing transactions.

[0205] Figure 14 is a block diagram illustrating a method 295a for processing a transaction according to certain examples. Figure 1 The components shown in describe method 295a.

[0206] At block 1410, the merchant point of sale device 130 generates a payment authorization request based on the payment token and other transaction information. In an example, the payment authorization request includes the payment token received from the account management system 160 for the user 101 and transaction details including the transaction amount, a description of the one or more items being purchased, a merchant identifier, a merchant payment account identifier, and / or other relevant transaction details.

[0207] In block 1420, the merchant point of sale device 130 transmits the payment authorization request to the issuer system 150. For example, the merchant point of sale device 130 communicates the payment authorization request to the issuer system 150 via the network 180.

[0208] In block 1430, the issuer system 150 approves the payment authorization request. In an example, the issuer system 150 identifies the user's payment account based on the received payment token. For example, the issuer system 150 accesses a database that associates the payment token with the user 101 payment account identifier. In an example, the database may also associate the payment token with one or more conditions, such as the length of time the payment token is valid. For example, the payment token may only be valid for a threshold length of time, such as one hour, after being generated by the account management system 160. In this example, a current timestamp is received from the merchant point-of-sale device 130 as part of the transaction details in the payment authorization request, and the issuer system 150 compares the received timestamp from the transaction details with one or more time conditions described in the database associated with the payment token and / or one or more data received from the account management system 160 upon receipt of the payment token. In another example, the payment token is only valid for use at a specific merchant system. In this example, the transaction details received in the payment authorization request from the merchant point-of-sale device 130 identifier include the merchant system identifier. In this example, the issuer system 150 determines that the payment token is valid if the merchant identifier received in the transaction details of the payment authorization request matches the merchant identifier in one or more conditions associated with the payment token in the database. In certain other examples, other conditions related to time, location, merchant identifier, or a combination of these conditions and / or other conditions may be specified in the database as associated with one or more specific payment tokens. In the example, the issuer system 150 verifies that the payment token received as part of the payment authorization request is valid based at least in part on data received from the merchant point of sale device 130 and / or data currently available to the issuer system 150. In the example, to process the transaction, the issuer system 150 uses the transaction details and the user payment account information to identify the user payment account associated with the payment token received in the database to process the transaction.

[0209] In block 1440, the merchant point-of-sale device 130 receives approval of the payment authorization request from the issuer system 150. In an example, the issuer system 150 either approves or denies the payment authorization request. In this example, the issuer system 150 may determine whether to approve or deny the payment authorization request based on the transaction total amount of user 101 against the currently available credit on user 101's payment account. In an example, if the issuer system 150 approves the payment authorization request, the merchant point-of-sale device 130 receives approval of the payment authorization request from the issuer system 150 via network 180. In another example, if the issuer system 150 denies the payment authorization request, the merchant point-of-sale device 130 receives notification of the denial of the payment authorization request from the issuer system 150 via network 180.

[0210] In block 1450, the merchant point-of-sale device 130 displays a confirmation of the approved transaction to the user 101. An example confirmation of the approved transaction may include the total amount charged to the user 101 payment account, identification of the user 101 payment account, the merchant system name, and / or other relevant or useful information. In another example, the merchant point-of-sale device 130 displays a notification of the declined transaction in response to receiving a notification from the issuer system 150 that the payment authorization request was declined. For example, the merchant point-of-sale device 130 displays a message reading "This transaction has been declined" via the user interface 135 of the merchant point-of-sale device 130. In another example, the merchant point-of-sale device 130 prints a receipt for the user 101.

[0211] Figure 15 is a block diagram illustrating an alternative method 295b for processing a transaction according to certain examples. Figure 1 295b. In this alternative embodiment, account management system 160 does not provide user payment account information to merchant point of sale device 130 in the form of a token or any other means. Account management system 160 receives transaction data from merchant point of sale device 130, requests authorization from payment processing system 140, provides authorization to merchant point of sale device 130, and allows merchant system 170 and payment processing system 140 to settle the transaction without account management system 160.

[0212] In addition to the hands-free environment described herein, method 295b may be practiced in any other suitable transaction environment. For example, the transaction may be a traditional transaction in which user 101 provides a user account identifier to a merchant point-of-sale device 130 to initiate a transaction via a magnetic stripe card, smart card, RFID device, or any other suitable device or card. In another example, user 101 provides a user account identifier to an online merchant on a website to initiate an online transaction. In another example, the transaction is initiated by a "tap" of user computing device 110 against a wireless reader on merchant point-of-sale device 130. In any of these environments, account management system 160 may execute a transaction in Figure 15 Some or all of the steps described herein to conduct a transaction.

[0213] For example, the method of block 1510 may be practiced by obtaining user authentication via methods other than those described herein. For example, user authentication may be a process in which user 101 swipes a card to submit a user account identification number. Any other suitable method may be utilized to authenticate user 101. In this example, the remaining blocks of method 295b are substantially similar to those described herein.

[0214] In block 1510, the merchant point of sale device 130 generates a transaction request in the form of a payment authorization request based on the user authentication and other transaction information. Figure 11 、 12 As described in and 13, user 101 can be verified as the owner of the account with which the transaction will be conducted. Verification can be performed as described in the example or in any other suitable manner. In the example, the payment authorization request does not include a payment token previously received from account management system 160 for user 101. In the example, when the user account information is provided, the payment token is not provided to merchant point of sale device 130. In the example, only the information required to verify the user account is provided to merchant point of sale device 130. Therefore, when merchant point of sale device 130 transmits the payment authorization request to account management system 160, merchant point of sale device 130 can only include user verification, for example, in the form of a user identifier, and transaction data such as transaction details, including the transaction amount, a description of the one or more items being purchased, a merchant identifier, a merchant payment account identifier, and / or other suitable transaction details.

[0215] In block 1520 , merchant point of sale device 130 transmits the payment authorization request to account management system 160 . For example, merchant point of sale device 130 transmits the payment authorization request to account management system 160 via network 180 .

[0216] At block 1530, account management system 160 identifies the user payment data. For example, when merchant point-of-sale device 130 transmits a payment authorization request with user authentication, account management system 160 extracts the user authentication and maps the user authentication to a user account stored in account management system 160, thereby identifying a payment account identifier to be transmitted to the payment processing system. In this context, account management system 160 also accesses the user account and identifies the payment device to be used for the transaction.

[0217] If multiple payment instruments are available, account management system 160 selects the appropriate payment instrument. In one example, one of the payment instruments may be configured as the default payment instrument. In another example, user 101 may select one of the payment instruments as the current payment instrument until changed. In another example, account management system 160 may select one of the payment instruments based on one or more configured rules, such as the merchant's identity, the product being purchased, the location, or any other suitable characteristics of the transaction. The payment instrument may be a credit card, debit card, prepaid card, bank account, loyalty card, or any other suitable payment instrument.

[0218] In block 1540, the account management system 160 requests authorization from the payment processing system 140. For example, the account management system 160 communicates to the payment processing system 140 an authorization request for the transaction, which includes a payment account identifier and transaction data, at least one of which includes the transaction amount, the product being purchased, payment instrument information, user identification, or any other suitable information. The account management system 160 also transmits to the payment processing system 140 an identification of the merchant system 170 and any other data required to allow the transaction to proceed between the payment processing system 140 and the merchant system 170. The identification of the merchant system 170 may include any information required for the payment processing system 140 to settle the transaction with the merchant system 170, such as a merchant account identifier, a bank account identifier, contact information, or any other suitable information.

[0219] At block 1550, account management system 160 receives approval of the payment authorization request from payment processing system 140. In this example, payment processing system 140 approves the transaction using user 101's payment account. For example, account management system 160 may contact issuer system 150 of user 101's account to obtain authorization. In another example, payment processing system 140 may utilize existing credit card network paths to obtain authorization for the transaction. In another example, payment processing system 140 is the issuer of user 101's payment instrument. In this case, payment processing system 140 may analyze user 101's account and approve the transaction if sufficient credit is available.

[0220] After receiving or granting authorization for the transaction, payment processing system 140 transmits the authorization to account management system 160. The transmission may be sent via any suitable technique, such as via the Internet over network 180.

[0221] In block 1560, the account management system 160 transmits the payment authorization to the merchant point-of-sale device 130. The merchant point-of-sale device 130 receives approval of the payment authorization request from the account management system 160 and displays to the clerk that the transaction is approved. The transmission from the account management system 160 can be sent via any suitable technology, such as via the Internet on the network 180. The account management system 160 can provide an authorization number or other authorization token to reference the approval of the transaction. In an alternative embodiment, the merchant point-of-sale device 130 receives approval of the payment authorization request directly from the payment processing system 140.

[0222] POS operator 102 may receive an indication of authorization from merchant point of sale device 130 via user interface 135 and provide the purchased product to the user. For example, POS operator 102 may read the authorization message, provide the product or service to user 101, provide user 101 with a printed or electronic receipt, and perform any other functions necessary to conduct the transaction.

[0223] Merchant point-of-sale device 130 displays a confirmation of the approved transaction to user 101. An example confirmation of the approved transaction may include the total amount charged to user 101's payment account, the identifier of user 101's payment account, the name of merchant system 170, and / or other relevant or useful information. In another example, if the authorization is not approved, merchant point-of-sale device 130 displays a notification of the transaction decline in response to receiving a notification from issuer system 150 that the payment authorization request was declined. For example, merchant point-of-sale device 130 displays a message to user 101 via user interface 135 of merchant point-of-sale device 130 that reads "This transaction has been declined." In another example, merchant point-of-sale device 130 prints a receipt for user 101.

[0224] In block 1570, the payment processing system 140 and the merchant system 170 settle the transaction without involving the account management system 160. In the example, the merchant point of sale device 130, a server at the merchant system 170, a third-party system associated with the merchant system 170, or any suitable party that manages the financial processing system of the merchant system 170 initiates settlement with the payment processing system 140. For example, the merchant system 170 may communicate one or more completed transactions to the payment processing system 140 and request the transfer of the associated funds. Settlement requests may be transmitted at the end of each day's business, after each transaction is completed, every two days, or at any other suitable interval.

[0225] In this example, merchant system 170 transmits the request directly to payment processing system 140. Account management system 160 does not participate in the settlement of transactions. In an alternative embodiment, account management system 160 transmits settlement requests to payment processing system 140 on behalf of merchant system 170. For example, merchant system 170 transmits notification to account management system 160 of which transactions have been completed and are awaiting settlement. Account management system 160 compiles a list of these transactions and transmits the list to payment processing system 140. In another example, merchant system 170 transmits a notification to account management system 160 each time a transaction is completed. Account management system 160 records the transactions and transmits settlement requests to payment processing system 140 on a configured schedule.

[0226] Upon receiving the settlement request, the payment processing system 140 provides the appropriate funds to the merchant system 170. For example, the payment processing system 140 may identify the funds required to cover the transaction requested by the merchant system 170 and transfer the funds to the merchant system 170's bank account. In an example, the merchant system 170 may have an account with the payment processing system 140. If so, the payment processing system 140 transfers the funds to the merchant system 170 by simply debiting the merchant system 170's account with the appropriate funds. If the merchant system 170 maintains a bank account with a third-party bank, the payment processing system 140 may transfer the funds via bank wire or any other suitable means of transferring funds.

[0227] In an example, funds are transferred directly from issuer system 150 to merchant system 170. Payment processing system 140 transmits a settlement request to issuer system 150, and issuer system 150 transfers the funds to merchant system 170, either directly or via payment processing system 140.

[0228] In the example, the settlement of funds occurs without account management system 160. That is, while account management system 160 is in the process flow of the transaction authorization process, account management system 160 is not in the process flow of the settlement process. Account management system 160 is not mentioned in the transaction details (such as in the transaction statement provided by the card issuer to user 101). The transaction is indicated as having been conducted with merchant system 170 rather than account management system 160. In the example, account management system 160 does not receive or transmit any funds associated with the transaction settlement. Funds are provided directly from issuer system 150 or payment processing system 140 to merchant system 170. Account management system 160 does not act as an intermediary for the settlement.

[0229] Other examples

[0230] Figure 16A computing machine 2000 and a module 2050 are described according to certain examples. The computing machine 2000 may correspond to any of the various computers, servers, mobile devices, embedded systems, or computing systems presented herein. The module 2050 may include one or more hardware or software elements configured to facilitate the computing machine 2000 in performing the various methods and processing functions presented herein. The computing machine 2000 may include various internal or additional components, such as a processor 2010, a system bus 2020, a system memory 2030, a storage medium 2040, an input / output interface 2060, and a network interface 2070 for communicating with a network 2080.

[0231] The computing machine 2000 may be implemented as a conventional computer system, an embedded controller, a laptop computer, a server, a mobile device, a smart phone, a set-top box, a self-service terminal, an in-vehicle information system, one or more processors associated with a television, a custom machine, any other hardware platform, or any combination or diversity thereof. The computing machine 2000 may be a distributed system configured to operate using multiple computing machines interconnected via a data network or bus system.

[0232] The processor 2010 can be configured to execute code or instructions to perform the operations and functions described herein, manage request flows and address mappings, and perform calculations and generate commands. The processor 2010 can be configured to monitor and control the operations of the components in the computing machine 2000. The processor 2010 can be a general-purpose processor, a processor core, a multiprocessor, a reconfigurable processor, a microcontroller, a digital signal processor ("DSP"), an application-specific integrated circuit ("ASIC"), a graphics processing unit ("GPU"), a field programmable gate array ("FPGA"), a programmable logic device ("PLD"), a controller, a state machine, a gated logic, a discrete hardware component, any other processing unit, or any combination or diversity thereof. The processor 2010 can be a single processing unit, multiple processing units, a single processing core, multiple processing cores, a dedicated processing core, a coprocessor, or any combination thereof. According to certain embodiments, the processor 2010, together with other components of the computing machine 2000, can be a virtualized computing machine executed within one or more other computing machines.

[0233] System memory 2030 may include non-volatile memory, such as read-only memory ("ROM"), programmable read-only memory ("PROM"), erasable programmable read-only memory ("EPROM"), flash memory, or any other device capable of storing program instructions or data with or without applied power. System memory 2030 may also include volatile memory, such as random access memory ("RAM"), static random access memory ("SRAM"), dynamic random access memory ("DRAM"), and synchronous dynamic random access memory ("SDRAM"). Other types of RAM may also be used to implement system memory 2030. System memory 2030 may be implemented using a single memory module or multiple memory modules. Although system memory 2030 is described as being part of computing machine 2000, those skilled in the art will recognize that system memory 2030 may be separate from computing machine 2000 without departing from the scope of the subject technology. It should also be understood that system memory 2030 may include, or operate in conjunction with, non-volatile storage devices, such as storage medium 2040.

[0234] The storage medium 2040 may include a hard disk, a floppy disk, a compact disk read-only memory ("CD-ROM"), a digital versatile disk ("DVD"), a Blu-ray disk, a magnetic tape, a flash memory, other non-volatile memory devices, a solid-state drive ("SSD"), any magnetic storage device, any optical storage device, any electrical storage device, any semiconductor storage device, any physical-based storage device, any other data storage device, or any combination or diversity thereof. The storage medium 2040 may store one or more operating systems, applications and program modules, such as module 2050, data, or any other information. The storage medium 2040 may be part of or connected to the computing machine 2000. The storage medium 2040 may also be part of one or more other computing machines that communicate with the computing machine 2000, such as a server, a database server, cloud storage, network-attached storage, etc.

[0235] Module 2050 may include one or more hardware or software elements configured to facilitate the computing machine 2000 in performing the various methods and processing functions presented herein. Module 2050 may include one or more instruction sequences stored as software or firmware associated with system memory 2030, storage medium 2040, or both. Thus, storage medium 2040 may represent an example of a machine- or computer-readable medium on which instructions or code may be stored for execution by processor 2010. A machine- or computer-readable medium may generally refer to any medium or media for providing instructions to processor 2010. Such machine- or computer-readable media associated with module 2050 may include a computer software product. It should be understood that a computer software product including module 2050 may also be associated with one or more processes or methods for delivering module 2050 to computing machine 2000 via network 2080, any signal-bearing medium, or any other communication or delivery technology. Module 2050 may also include hardware circuitry or information for configuring the hardware circuitry, such as microcode or configuration information for an FPGA or other PLD.

[0236] The input / output ("I / O") interface 2060 may be configured to couple to one or more external devices to receive data from one or more external devices and to send data to one or more external devices. These external devices, along with various internal devices, may also be referred to as peripheral devices. The I / O interface 2060 may include electrical and physical connections for operably coupling various peripheral devices to the computing machine 2000 or the processor 2010. The I / O interface 2060 may be configured to communicate data, addresses, and control signals between peripheral devices, the computing machine 2000, or the processor 2010. The I / O interface 2060 may be configured to implement any standard interface, such as a small computer system interface ("SCSI"), serial attached SCSI ("SAS"), fiber channel, peripheral component interconnect ("PCI"), PCI Express (PCIe), a serial bus, a parallel bus, advanced technology attached ("ATA"), serial ATA ("SATA"), a universal serial bus ("USB"), Thunderbolt, Fire Wire, various video buses, and the like. The I / O interface 2060 may be configured to implement only one interface or bus technology. Alternatively, the I / O interface 2060 may be configured to implement multiple interfaces or bus technologies. The I / O interface 2060 may be configured to operate as part of, in whole, or in conjunction with the system bus 2020. The I / O interface 2060 may include one or more buffers, internal devices, computing machines 2000, or processors 2010 for buffering transmissions between one or more external devices.

[0237] The I / O interface 2060 can couple the computing machine 2000 to various input devices, including a mouse, a touch screen, a scanner, an electronic digitizer, a sensor, a receiver, a touch pad, a trackball, a camera, a microphone, a keyboard, any other pointing device, or any combination thereof. The I / O interface 2060 can couple the computing machine 2000 to various output devices, including a video display, a speaker, a printer, a projector, a tactile feedback device, an automation control, a robotic component, an actuator, a motor, a fan, a solenoid, a valve, a pump, a transmitter, a signal transmitter, a light, and the like.

[0238] The computing machine 2000 can operate in a networked environment using logical connections to one or more other systems or computing machines on the network 2080 via the network interface 2070. The network 2080 can include a wide area network (WAN), a local area network (LAN), an intranet, the Internet, a wireless access network, a wired network, a mobile network, a telephone network, an optical network, or a combination thereof. The network 2080 can be packet-switched or circuit-switched in any topology and can use any communication protocol. The communication links within the network 2080 can involve various digital or analog communication media, such as fiber optic cables, free space optics, waveguides, electrical conductors, wireless links, antennas, radio frequency communications, and the like.

[0239] The processor 2010 may be connected to other elements of the computer 2000 or the various peripheral devices discussed herein via a system bus 2020. It should be understood that the system bus 2020 may be internal to the processor 2010, external to the processor 2010, or both. According to some embodiments, any of the processors 2010, other elements of the computer 2000, or the various peripheral devices discussed herein may be integrated into a single device such as a system on a chip (“SOC”), a system in a package (“SOP”), or an ASIC device.

[0240] Where the systems discussed herein collect personal information about a user or may utilize personal information, the user may be provided with an opportunity or option to control whether a program or feature collects user information (e.g., information about the user's social network, social actions or activities, profession, the user's preferences, or the user's current location) or to control whether and / or how content that may be more relevant to the user is received from a content server. Additionally, certain data may be processed in one or more ways prior to storage or use so that personally identifiable information is removed. For example, the user's identity may be processed so that personally identifiable information cannot be determined for the user, or the user's geographic location for which location information is obtained may be generalized (e.g., to the city, zip code, or state level) so that the user's specific location cannot be determined. Thus, the user may have control over how information about the user is collected and used by the content server.

[0241] Embodiments may include computer programs that embody the functions described and illustrated herein, wherein the computer programs are implemented in a computer system comprising instructions stored in a machine-readable medium and a processor that executes the instructions. However, it should be apparent that there may be many different ways of implementing embodiments in computer programming, and the embodiments should not be construed as being limited to any one set of computer program instructions. In addition, a skilled programmer will be able to write such a computer program based on the associated descriptions in the attached flowcharts and application text to implement embodiments of the disclosed embodiments. Therefore, it is not considered necessary to disclose a specific set of program code instructions to fully understand how to make and use the embodiments. In addition, those skilled in the art will understand that one or more aspects of the embodiments described herein may be performed by hardware, software, or a combination thereof, as they may be embodied in one or more computing systems. In addition, any reference to an action performed by a computer should not be construed as being performed by a single computer, as more than one computer may perform the action.

[0242] The examples described herein can be used with computer hardware and software that perform the methods and processing functions described herein. The systems, methods, and processes described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry. The software can be stored on a computer-readable medium. For example, the computer-readable medium can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc. The digital circuitry can include an integrated circuit, a gate array, building block logic, a field programmable gate array (FPGA), etc.

[0243] The example systems, methods, and actions described in the previously presented embodiments are illustrative, and in alternative embodiments, certain actions can be performed in a different order, in parallel with each other, omitted entirely, and / or combined in different examples, and / or certain additional actions can be performed without departing from the scope and spirit of the various embodiments. Accordingly, these alternative embodiments are intended to be included within the scope of the following claims, which are to be given the broadest interpretation so as to encompass these alternative embodiments.

[0244] Although specific embodiments have been described in detail above, the description is for illustrative purposes only. Therefore, it should be understood that many of the aspects described above are not intended to be required or essential elements unless otherwise expressly stated. In addition to those described above, those skilled in the art who have the benefit of this disclosure will be able to modify the aspects of the disclosed examples and make equivalent components or actions corresponding to the aspects of the disclosed examples without departing from the spirit and scope of the embodiments defined in the following claims, and the scope of the following claims is to be given the broadest interpretation so as to include such modifications and equivalent structures.

Claims

1. A computer-implemented method for providing secure transactions by identifying a user account using one or more computing devices of an account management system, comprising: receiving, by the one or more computing devices from a user computing device, a merchant beacon identifier of a merchant beacon device and a user account identifier of a user account; extracting, by the one or more computing devices, user identification data associated with the user account identifier; identifying, by the one or more computing devices, a merchant point of sale device of a merchant system associated with the merchant beacon identifier; transmitting said user identification data to said merchant point-of-sale device before a user initiates a transaction at said merchant system; After transmitting the user identification data to the merchant system, receiving, by the one or more computing devices, a transaction request from the merchant system, the transaction request including the user identification data and transaction data for a transaction; identifying, by the one or more computing devices, the user account stored in the account management system with which the transaction is to be conducted, and thereby identifying a user payment account identifier associated with the user payment account; transmitting, by the one or more computing devices, the payment account identifier and the transaction data to a payment processing system; receiving, by the one or more computing devices, approval of the transaction from the payment processing system; as well as The approval of the transaction is communicated by the one or more computing devices to the merchant system. 2 . The method of claim 1 , further comprising mapping, by the one or more computing devices, the user account identifier to a payment account identifier, the payment account identifier being stored in a database associated with the user. 3 . The method of claim 1 , further comprising requesting, by the one or more computing devices, the approval of the transaction from the payment processing system. 4 . The method of claim 1 , wherein a device of the merchant system generates the transaction request including the user account identifier based on user authentication.

5. The method of claim 4, wherein the user authentication is performed via facial recognition, via voice recognition and / or via challenge and response.

6. The method of claim 1, wherein the user account identifier is determined by the merchant system via hands-free identification of the user.

7. The method of claim 3, wherein identification of the one or more computing devices does not appear on a record of the transaction at the merchant system or the payment processing system.

8. The method of claim 1, further comprising mapping, by the one or more computing devices, the user account identifier to a payment instrument to be used for the transaction.

9. A non-transitory computer-readable storage device having computer-executable program instructions embedded thereon, the computer-executable program instructions, when executed by one or more computing devices of an account management system, causing the one or more computing devices to perform the method of any one of claims 1-8.

10. The non-transitory computer-readable storage device of claim 9, wherein the identification of the account management system does not appear on the record of the transaction.

11. A system for providing secure transactions by identifying user accounts using an account management system, comprising: a merchant system comprising a merchant point-of-sale device and a merchant beacon device; as well as One or more computing devices of the account management system, the one or more computing devices being arranged to: receiving, from a user computing device, a merchant beacon identifier of the merchant beacon device and a user account identifier of a user account; extracting user identification data associated with the user account identifier; identifying the merchant point-of-sale device associated with the merchant beacon identifier; transmitting said user identification data to said merchant point-of-sale device before a user initiates a transaction at said merchant system; After transmitting the user identification data to the merchant system, receiving a transaction request from the merchant system, the transaction request including the user identification data and transaction data for a transaction; identifying the user account stored in the account management system with which the transaction is to be conducted, and thereby identifying a user payment account identifier associated with the user payment account; transmitting the user payment account identifier and the transaction data to a payment processing system; receiving approval of the transaction from the payment processing system; as well as The approval of the transaction is communicated to the merchant system.

12. The system according to claim 11, wherein The merchant system is further arranged to receive funds to settle the transaction with the payment processing system or issuer system, or is further arranged to determine the user account identifier via hands-free identification of the user.

13. The system of claim 11, wherein identification of one or more computing devices of the account management system does not appear on the record of the transaction, or wherein identification of the account management system does not appear on the record of the transaction.

14. The system of claim 11, wherein the account management system identifies the user payment account identifier based on the user account identifier.

Images