US20190130408A1 - Hands-free transactions verified by location - Google Patents

Hands-free transactions verified by location Download PDF

Info

Publication number
US20190130408A1
US20190130408A1 US16/233,442 US201816233442A US2019130408A1 US 20190130408 A1 US20190130408 A1 US 20190130408A1 US 201816233442 A US201816233442 A US 201816233442A US 2019130408 A1 US2019130408 A1 US 2019130408A1
Authority
US
United States
Prior art keywords
computing
user
merchant
hands
location
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US16/233,442
Inventor
Varouj Chitilian
Sashikanth Chandrasekaran
Johnie Lee
Pramod Adiddam
Thai Ngoc Duong
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Google LLC
Original Assignee
Google LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201462023739P priority Critical
Priority to US14/540,009 priority patent/US10185960B2/en
Application filed by Google LLC filed Critical Google LLC
Priority to US16/233,442 priority patent/US20190130408A1/en
Assigned to GOOGLE INC. reassignment GOOGLE INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ADIDDAM, PRAMOD, CHANDRASEKARAN, SASHIKANTH, CHITILIAN, VAROUJ, DUONG, THAI NGOC, LEE, Johnie
Assigned to GOOGLE LLC reassignment GOOGLE LLC ENTITY CONVERSION Assignors: GOOGLE INC.
Publication of US20190130408A1 publication Critical patent/US20190130408A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3224Transactions dependent on location of M-devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3227Aspects of commerce using mobile devices [M-devices] using secure elements embedded in M-devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327Short range or proximity payments by means of M-devices
    • G06Q20/3278RFID or NFC payments by means of M-devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G06Q20/3674Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes involving authentication
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3821Electronic credentials
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3821Electronic credentials
    • G06Q20/38215Use of certificates or encrypted proofs of transaction rights
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4014Identity check for transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4016Transaction verification involving fraud or risk level assessment in transaction processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00Business processing using cryptography

Abstract

Conducting hands-free transactions comprises a server at a payment processing system, a user computing device, and a merchant computing device. The payment processing system registers a merchant system as a hands-free payment participant and provides a beacon identifier. The payment processing system receives a communication from a hands- free payment application on a user computing device, the communication comprising a transaction token, an identification of a user account, and the beacon identifier received by the user computing device via a wireless communication from a device associated with the merchant system and transmits the transaction token to the merchant system computing device. The payment processing system receives from the merchant system computing device, a transaction request, the transaction request comprising the token and transaction data associated with the transaction request and conducts the transaction between the user account and the merchant system based on the received token and transaction request.

Description

    RELATED APPLICATIONS
  • This patent application is a continuation of U.S. patent application Ser. No. 14/540,009, filed Nov. 12, 2014 and entitled “ Hands-Free Transactions Verified by Location,” which claims priority under 35 U.S.C. § 119 to U.S. Patent Application No. 62/023,739, filed Jul. 11, 2014 and entitled “Hands-Free Transactions.” The entire contents of the above-identified applications are hereby fully incorporated herein by reference.
  • TECHNICAL FIELD
  • The present disclosure relates generally to retail transactions, and more particularly to conducting hands-free transactions at a merchant location that allow a user to conduct transactions without engaging the user computing device. The disclosure additionally relates to making the transactions more secure and efficient.
  • BACKGROUND
  • When consumers make purchases at a merchant location, many methods of conducting a transaction are available. Consumers may use many different payment cards or accounts for purchases, such as gift cards, debit cards, credit cards, stored value cards, and other cards or accounts. The user account identifiers and other data represented by the cards may be communicated to the merchant system via magnetic stripes, near field communication technologies, manual input, and other suitable mechanisms.
  • Conventional payment systems require the consumer to perform actions to provide the user account identifiers and other data to the merchant system. For example, the user may be required to actuate a start button or initiate an application. In another example, the user may be required to tap or swipe a user computing device to initiate a transaction. Other user interactions may be required by conventional payment systems.
  • SUMMARY
  • Techniques herein provide computer-implemented methods to conduct hands-free transactions. In an example embodiment, conducting hands-free transactions comprises a server at a payment processing system, a user computing device, and a merchant computing device. The payment processing system registers a merchant system as a hands-free payment participant and provides a beacon identifier. The merchant system broadcasts the beacon, which is received by a user computing device at the merchant's location. The payment processing system receives a communication from a hands-free payment application on the user computing device. The communication comprises a transaction token, an identification of a user account, and the beacon identifier received by the user computing device and transmits the transaction token to the merchant system computing device. The payment processing system receives from the merchant system computing device, a transaction request. The transaction request comprises the token and transaction data associated with the transaction request. The payment processing system conducts the transaction between the user account and the merchant system based on the received token and transaction request.
  • In certain other example aspects described herein, systems and computer program products to conduct hands-free transactions are provided.
  • These and other aspects, objects, features, and advantages of the example embodiments will become apparent to those having ordinary skill in the art upon consideration of the following detailed description of illustrated example embodiments.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram depicting a system for conducting hands-free transactions, in accordance with certain example embodiments.
  • FIG. 2 is a block flow diagram depicting a method for conducting hands-free transactions, in accordance with certain example embodiments.
  • FIG. 3 is a block flow diagram depicting a method for a merchant computing device to broadcast a beacon via a wireless communication, in accordance with certain example embodiments.
  • FIG. 4 is a block flow diagram depicting a method for a user computing device to recognize a merchant computing device beacon, in accordance with certain example embodiments.
  • FIG. 5 is a block flow diagram depicting a method for a user computing device to provide a token authorization to a merchant, in accordance with certain example embodiments.
  • FIG. 6 is a block flow diagram depicting a method for a user computing device to recognize a beacon via wireless communication at a location of a merchant system and approve the merchant system, in accordance with certain example embodiments.
  • FIG. 7 is a block flow diagram depicting a method for a user computing device to recognize a beacon via wireless communication at a location of a merchant system and approve the merchant system using location data, in accordance with certain example embodiments.
  • FIG. 8 is a block diagram depicting a computing machine and module, in accordance with certain example embodiments.
  • DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview
  • The example embodiments described herein provide computer-implemented techniques to conduct hands-free payments. In an example embodiment, a user installs a hands-free application on a user computing device. The user maintains a user account on a payment processing system for conducting transactions. A merchant computing device at a merchant location provides a beacon identifier that is received by the user computing device.
  • The user computing device generates a token for conducting a transaction and transmits the token to the payment processing system. The payment processing system transmits the token to the merchant computing device. The merchant computing device stores the token for use in a transaction with the user computing device.
  • The user approaches the salesperson to conduct a transaction using the hands-free application. The salesperson initiates the transaction on the merchant computing device and identifies the user on a user interface of the merchant computing device. The merchant computing device transmits the transaction details and the token for the user to the payment processing system. The payment processing system verifies the details of the transaction and the token and conducts the transaction. The payment processing system communicates a notification to the user computing device with the transaction data.
  • In an example embodiment, the beacon identifier of the merchant system and other authorized beacon identifiers are stored on a database. The user computing device compares a received beacon identifier to the database and determines if the merchant beacon is authorized for hands-free transactions with the user.
  • In another example embodiment, a global positioning system (“GPS”) module of a user computing device is utilized to determine if the merchant beacon is authorized for hands-free transactions with the user. The user computing device, upon receiving a beacon identifier, determines the location of the user computing device, and thus, the location of the beacon. The location is compared to a database of beacon locations to determine if the beacon is broadcasting from the expected location. If the locations match, then the user computing device determines that a subsequent hands-free transaction with the merchant may proceed.
  • By using and relying on the methods and systems described herein, the hands- free application and payment processing system dynamically provide accurate and reliable transactions for a user without a needed action from the user. As such, the systems and methods described herein may be employed to allow the user to conduct a transaction using communications from the user computing device, the merchant computing device, and the payment processing system that are secure and efficient. The user is not troubled to provide any actuation or other initiating steps to conduct a transaction. The system may use the location of the user computing device to make the transaction more secure. The system may use communication between the user computing device and the payment processing system to reduce fraudulent activities by the merchant. The system may use beacon identifiers between the user computing device and the merchant computing device to reduce fraudulent activities. Hence, the methods and systems described herein decrease user frustration and permit accurate and reliable transactions for a user.
  • Example System Architectures
  • Turning now to the drawings, in which like numerals indicate like (but not necessarily identical) elements throughout the figures, example embodiments are described in detail.
  • FIG. 1 is a block diagram depicting a system 100 for conducting hands-free transactions, in accordance with certain example embodiments. As depicted in FIG. 1, the system 100 includes network computing devices 110, 130, 140, and 150 that are configured to communicate with one another via one or more networks 120. In some embodiments, a user 101 or a salesperson 102 associated with a device must install an application and/or make a feature selection to obtain the benefits of the techniques described herein.
  • In example embodiments, the network 120 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, storage area network (“SAN”), 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, near field communication (“NFC”), Wi-Fi, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages. Throughout the discussion of example embodiments, 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.
  • Each network computing system 110, 130, 140, and 150 includes a device having a communication module capable of transmitting and receiving data over the network 120. For example, each network computing device 110, 130, 140, and 150 can include a server, desktop computer, laptop computer, tablet computer, a television with one or more processors embedded therein and/or coupled thereto, smart phone, handheld computer, personal digital assistant (“PDA”), or any other wired or wireless, processor-driven device. In the example embodiment depicted in FIG. 1, the network computing devices 110, 130, 140, and 150 are operated by users 101, merchant system operators, payment processing system operators, and salespersons 102, respectively.
  • In the examples provided herein, actions performed by the user 101 may be performed by the salesperson 102 in other embodiments. Examples described as being performed by the user computing device 110 may be performed by the merchant computing device 150 or the payment processing system 140 in other embodiments.
  • An example user computing device 110 comprises a data storage unit 112, a communication application 113, a web browser 114, a user interface 115, a global positioning system (“GPS”) module 118, and a hands-free payment application 116.
  • In an example embodiment, the data storage unit 112 comprises a local or remote data storage structure accessible to the user computing device 110 suitable for storing information. In an example embodiment, the data storage unit 112 stores encrypted information, such as HTML5 local storage.
  • In an example embodiment, the user 101 uses a communication application 113, such as a web browser 114 application or a stand-alone hands-free payment application 116, to view, download, upload, or otherwise access documents or web pages via a distributed network 120.
  • In an example embodiment, the communication application 113 can interact with web servers or other computing devices connected to the network 120, including the user computing device 110, a point of sale (“POS”) terminal 134 associated with a merchant system 130 and/or a web server (not depicted) associated with a payment processing system 140.
  • In an example embodiment, the web browser 114 can enable the user 101 to interact with web pages using the user computing device 110.
  • In an example embodiment, the user interface 115 enables the user 101 to interact with the hands-free payment application 116 and/or web browser 114. For example, the user interface 115 may 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 embodiment, the user 101 interacts via the user interface 115 with the hands-free payment application 116 and/or web browser 114 to configure user accounts on a payment processing system hands-free module 141. In another example embodiment, the user 101 interacts via the user interface 115 with the hands-free payment application 116 and/or the web browser 114 to enable hands-free payments, if needed.
  • In an example embodiment, the GPS module 118 communicates with one or more satellites of the Global Positioning System (“GPS”) or other satellite-based location system to determine the location of the user computing device 110. In an example embodiment, the delivery system 140 periodically or continuously communicates with the GPS module 118 during applicable time periods to determine and log the location of the user computing device 110. In another embodiment, the location of the user computing device 110 is identified based on Wi-Fi signals, cellular location, or any suitable location identifying technology. Any location determining hardware, software, or combination of hardware and software is represented by the GPS module 118.
  • In an example embodiment, the hands-free payment application 116 is a program, function, routine, applet, or similar entity that exists on and performs its operations on the user computing device 110. In certain example embodiments, the user 101 must install the hands-free payment application 116 and/or make a feature selection on the user computing device 110 to obtain the benefits of the techniques described herein. In an example embodiment, the user 101 may access the hands-free payment application 116 on the user computing device 110 via the user interface 115. In an example embodiment, the hands-free payment application 116 may be associated with the payment processing system 140. In another example embodiment, the application may be associated with the merchant system 130. In yet another example embodiment, there are two hands-free payment applications 116, one associated with the merchant system 130 and another associated with the payment processing system 140.
  • In certain example embodiments, one or more functions herein described as performed by the hands-free payment application 116 may also be performed by a web browser 114 application, for example, a web browser 114 application associated with a merchant system website 134 or associated with the payment processing system 140. In certain example embodiments, one or more functions herein described as performed by the hands-free payment application 116 may also be performed by the user computing device operating system. In certain example embodiments, one or more functions herein described as performed via the web browser 114 may also be performed via the hands-free payment application 116.
  • In an example embodiment, the user computing device 110 communicates with the merchant system 130 and the payment processing system 140 via the network 120.
  • An example merchant system 130 comprises a server 133, POS terminal 134, and a data storage unit 132. In an example embodiment, the merchant system 130 communicates with a payment processing system 140 over the network 120. In example embodiments described herein, the merchant system 130 is a separate entity from the payment processing system 140. However, in certain other example embodiments, the merchant system 130 is associated with a payment processing system 140, is a component of another system along with a payment processing system 140, comprises a payment processing system 140, or is a component of a payment processing system 140.
  • In an example embodiment, the data storage unit 132 comprises a local or remote data storage structure accessible to the merchant system 130 suitable for storing information. In an example embodiment, the data storage unit 132 stores encrypted information, such as HTML5 local storage.
  • In an example embodiment, the web server 133 provides content accessible by the user 101 through the web browser 114 and/or hands-free payment application 116 on the user computing device 110, including but not limited to html documents, images, style sheets, and scripts. In an example embodiment, the server 133 supports the merchant system website 134.
  • In an example embodiment, the POS terminal 134 comprises a computing device that is configured to accept payments from users 101, from user computing devices 110, or other parties. The POS terminal 134 may communicate, via the network, with the user computing device 110, the merchant server 133, the merchant computing device 150, the payment processing system 140, or any suitable device or system. The POS terminal 134 may comprise a barcode scanner, a user interface, a customer display, or any suitable elements to enable the salesperson 102 to initiate and conduct a transaction. The POS terminal 134 in the example embodiments may comprise a function enabling the salesperson 102 to input an indication that the transaction was conducted with the hands-free application 156 on the merchant computing device 150, and that the POS terminal 134 should consider the transaction completed.
  • An example payment processing system 140 comprises a payment processing system hands-free module 141 and a data storage unit 142. In an example embodiment, the user 101 has a user account with the payment processing system 140. In an example embodiment, the payment processing system hands-free module 141 manages the user account. For example, the payment processing system hands-free module 141 may receive a user's username and password and allow the user 101 to access services provided by the payment processing system 140. In an example embodiment, the payment processing system hands-free module 141 communicates with the hands-free payment application 116 resident on the user computing device 110. In another example embodiment, the payment processing system hands-free module 141 communicates with the user 101 via the user computing device web browser 114. In an example embodiment, the payment processing system hands- free module 141 manages the user's digital wallet account.
  • In an example embodiment, the payment processing system hands-free module 141 communicates with the merchant system 130, account issuer systems (not depicted) and/or acquirers (not depicted), or other suitable financial systems (not depicted) to process payments. In an example embodiment, the payment processing system hands-free module 141 retrieves user financial account information and credit account information from other financial institutions, from the data storage unit 142, or by communicating with the hands-free payment application 116 over the network 120. In an example embodiment, the payment processing system hands-free module 141 requests a credit authorization from an issuer system through an acquirer system and receives the credit authorization. In an example embodiment, the payment processing system hands-free module 141 initiates a bank transfer with a financial institution system. In an example embodiment, the payment processing system hands-free module 141 receives the bank transfer or completes a credit card transaction associated with the credit card authorization.
  • In certain example embodiments, the payment processing system hands-free module 141 creates tokens, verifies tokens, verifies rescue codes, and performs other actions as described herein. In an example embodiment, the payment processing system hands-free module 141 generates a receipt of a transaction and transmits the receipt to the user computing device 110.
  • In an example embodiment, the data storage unit 142 comprises any local or remote data storage structure accessible to the payment processing system hands-free module 141 suitable for storing information. In an example embodiment, the data storage unit 142 stores encrypted information, such as HTML5 local storage. In an example embodiment, the data storage unit 142 stores user financial account information and/or user credit account information.
  • An example merchant computing device 150 comprises a data storage unit 152, a communication application 153, a web browser 154, a user interface 155, and a hands- free payment application 156.
  • In an example embodiment, the data storage unit 152 comprises a local or remote data storage structure accessible to the merchant computing device 150 suitable for storing information. In an example embodiment, the data storage unit 152 stores encrypted information, such as HTML5 local storage.
  • In an example embodiment, the salesperson 102 uses a communication application 153, such as a web browser 154 application or a stand-alone hands-free payment application 116, to view, download, upload, or otherwise access documents or web pages via a distributed network 120.
  • In an example embodiment, the communication application 153 can interact with web servers or other computing devices connected to the network 120, including the merchant POS terminal 134, a web server 133 associated with a merchant system 130 and/or a payment processing system hands-free module 141.
  • In an example embodiment, the web browser 154 can enable the salesperson 102 to interact with web pages using the merchant computing device 150. In an example embodiment, the salesperson 102 is able to access transaction information form the POS terminal 134, and access user account information from the user computing device 110 and/or the payment processing system hands-free module 141.
  • In an example embodiment, the user interface 155 enables the salesperson 102 to interact with the hands-free payment application 156 and/or web browser 154. For example, the user interface 155 may be a touch screen, a voice-based interface or any other interface that allows the salesperson 102 to provide input and receive output from an application or module on the merchant computing device 150. In an example embodiment, the salesperson 102 interacts via the user interface 155 with the hands-free payment application 156 and/or web browser 154 to access a user token to conduct a transaction via the payment processing system 140.
  • In an example embodiment, the hands-free payment application 156 is a program, function, routine, applet, or similar entity that exists on and performs operations on the merchant computing device 150. In certain example embodiments, the salesperson 102 must install the hands-free payment application 156 and/or make a feature selection on the merchant computing device 150 to obtain the benefits of the techniques described herein. In an example embodiment, the salesperson 102 may access the hands-free payment application 156 on the merchant computing device 150 via the user interface 155. In an example embodiment, the hands-free payment application 156 may be associated with the merchant system 130. In another example embodiment, the application may be associated with the payment processing system 140. In yet another example embodiment, there are two applications 156, one associated with the merchant system 130 and another associated with the payment processing system 140.
  • In certain example embodiments, one or more functions herein described as performed by the hands-free payment application 156 may also be performed by a web browser 154 application, for example, a web browser 154 application associated with a merchant system website 134 or associated with the payment processing system 140. In certain example embodiments, one or more functions herein described as performed by the hands-free payment application 156 may also be performed by the merchant computing device operating system. In certain example embodiments, one or more functions herein described as performed via the web browser 154 may also be performed via the hands-free payment application 156.
  • In certain example embodiments, the merchant computing device 150 may be part of the merchant system 130. The merchant computing device 150 functions described herein may be performed by the merchant server 133, POS terminal 134, or other merchant device.
  • It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers and devices can be used. Moreover, those having ordinary skill in the art having the benefit of the present disclosure will appreciate that the user computing device 110, the merchant system 130, the POS terminal 134, the payment processing system 140, and the merchant computing device 150 illustrated in FIG. 1 can have any of several other suitable computer system configurations. For example, a user computing device 110 embodied as a mobile phone or handheld computer may or may not include all the components described above.
  • In example embodiments, the network computing devices and any other computing machines associated with the technology presented herein may be any type of computing machine such as, but not limited to, those discussed in more detail with respect to FIG. 8. Furthermore, any modules associated with any of these computing machines, such as modules described herein or any other modules (scripts, web content, software, firmware, or hardware) associated with the technology presented herein may by any of the modules discussed in more detail with respect to FIG. 8. The computing machines discussed herein may communicate with one another as well as other computer machines or communication systems over one or more networks, such as network 105. The network 105 may include any type of data or communications network, including any of the network technology discussed with respect to FIG. 8.
  • Example Processes
  • The example methods illustrated in FIGS. 2-7 are described hereinafter with respect to the components of the example operating environment 100. The example methods of FIGS. 2-7 may also be performed with other systems and in other environments.
  • FIG. 2 is a block diagram depicting a method 200 for conducting a hands- free transaction, in accordance with certain example embodiments. The method 200 is described with reference to the components illustrated in FIG. 1.
  • In block 210, the merchant computing device 150 broadcasts a beacon via a wireless communication. Block 210 is described in greater detail hereinafter with reference to the method 210 described in FIG. 3.
  • FIG. 3 is a block diagram depicting a method 210 for a merchant computing device 150 to broadcast a beacon via a wireless communication, in accordance with certain example embodiments. The method 210 is described with reference to the components illustrated in FIG. 1.
  • In block 310, the merchant system 130 registers with the payment processing system 140. For example, the merchant system 130 may contact the payment processing system 140 to become associated with the hands-free transaction process. The merchant system 130 may obtain a merchant account, receive the appropriate applications and software, request authorization to participate, or perform any action required by the payment processing system 140.
  • The merchant system 130 may use the merchant computing device 150, the point of sale (“POS”) terminal 134, the merchant server 133, or any suitable computing device to request and configure a merchant account. The merchant account may allow the merchant system 130 to participate in some or all of the activities described in the methods herein.
  • In block 320, the merchant computing device 150 installs a hands-free payment application 156. In an example, the merchant computing device 150 is registered as an authorized agent of the merchant system 130. The merchant computing device 150 may be identified by an identifier, by a provided password, a serial number, or by any suitable manner.
  • In an example, the merchant computing device 150 downloads the hands-free payment application 156 from the payment processing system hands-free module 141 over the network 120. The merchant computing device 150 may download the hands-free payment application 156 from the merchant system server 133. The merchant computing device 150 may obtain the hands-free payment application 156 from any suitable location. The hands-free payment application 156 on the merchant computing device 150 may be integrated into an existing account that is shared with the merchant system server 133, the POS terminal 134, or any suitable computing device or system. A salesperson 102 or another merchant system operator may be required to make a feature selection to obtain the benefits of the techniques described herein.
  • In block 330, the merchant computing device 150 receives a beacon identifier. For example, the hands-free payment application 156, the merchant computing device 150, the merchant system server 133, or another computing device requests a beacon identifier from the payment processing system 140. The beacon may be a wireless signal emitted by the merchant computing device 150 comprising a beacon identifier, a merchant system 130 identifier, a merchant computing device 150 identifier, or other identifier.
  • In an example, the beacon identifier is a service set identifier (“SSID”), or other network name or identifier. The beacon identifier may be generated by the payment processing system hands-free module 141, the merchant computing device 150, the merchant server 133, or any suitable computing device. In certain embodiments, the beacon identifier is a unique, but fixed, identifier. That is, a particular beacon identifier may be utilized until changed by the payment processing system hands-free module 141, the merchant computing device 150, the merchant server 133, or any suitable computing device. In an alternate embodiment, the beacon identifier may be unique, but random. That is, the beacon identifier may be changed randomly, or upon any suitable schedule by the payment processing system hands-free module 141, the merchant computing device 150, the merchant server 133, or any suitable computing device.
  • The wireless signal emitted by the merchant computing device 150 may be any suitable technology, such as Wi-Fi direct, Bluetooth, low-energy Bluetooth, infrared, or any other suitable technology, and the merchant computing device 150 may include corresponding hardware and software components to emit the beacon via the associated technology.
  • In block 340, the merchant computing device 150 transmits the beacon via wireless communication at the location of the merchant system 150. The merchant computing device 150 may be configured to broadcast the wireless signal at only certain times or locations, or continuously. The merchant computing device 150 may limit or extend the strength of the broadcast beacon, if needed. The beacon is receivable and recognizable by other computing devices that are within range of the wireless signal. The beacon may be transmitted on one communication technology or on a plurality of communication technologies.
  • In a certain example embodiment, the beacon identifier is programmed on external communication access points. The merchant hands-free application 156 may be used to configure the external communication access point(s). For example, the merchant hands-free application 156 may utilize functions of the merchant computing device 150 to communicate instructions to the external communication access points. The instructions may include the beacon identifier, the requested communication technology, the time to broadcast, and/or any other suitable instructions. The instructions may be provided by any other suitable computing device.
  • The external communication access points may be employed to allow a variety of user computing devices 110 to receive the beacon despite differing wireless communication technology capabilities or in various locations in the merchant location. The external communication access points may allow the beacon to be broadcast over a wider area than the merchant computing device 150 alone is capable of broadcasting.
  • From block 340, the method 210 proceeds to block 220 of FIG. 2.
  • Returning to FIG. 2, in block 220, the user computing device 110 recognizes the merchant computing device beacon. Block 220 is described in more detail hereinafter with reference to the method 220 described in FIG. 4.
  • FIG. 4 is a block diagram depicting a method 220 for the user computing device 110 to recognize the merchant computing device beacon, in accordance with certain example embodiments. The method 220 is described with reference to the components illustrated in FIG. 1.
  • In block 410, the user 101 registers with the payment processing system 140. For example, the user 101 may contact the payment processing system 140 to register a user account. The user 101 may obtain a user account number, receive the appropriate applications and software to install on the user computing device 110, request authorization to participate in the hands-free payment processing, or perform any action required by the payment processing system 140. The user 101 may utilize the functions of the user computing device 110, such as the user interface 115 and the web browser 114, to register and configure a user account.
  • In block 420, the user computing device 140 installs a hands-free payment application 116. For example, the user computing device 110 downloads the hands-free payment application 116 from the payment processing system hands-free module 141 over the network 120. The user computing device 110 may obtain the hands-free payment application 116 from any other suitable location. The hands-free payment application 116 on the user computing device 110 may be configured with the user account information, user preferences, or other suitable information. A user 101 may be required to make a feature selection to obtain the benefits of the techniques described herein.
  • The hands-free payment application 116 may provide options, data, configurable alerts, and other suitable benefits to the user 101. For example, the hands-free payment application 116 may comprise a listing of participating merchant systems 130 and merchant locations. The listing may be updated periodically from the payment processing system 140. The hands-free payment application 116 may notify the user 101 when the user 101 is within a configured vicinity of a participating merchant system 130. The hands-free payment application 116 may provide the user 102 with options to update payment preferences. The hands-free payment application 116 may provide the user 101 with a listing of recent transactions. The hands-free payment application 116 may provide any other suitable information to the user 101.
  • In block 430, the user computing device 110 enters a location of the merchant system 130. The user 101 may enter the merchant location carrying the user computing device 101 in a pocket or a bag, in the hands of the user 101, or in any suitable manner. The location of the merchant system 130 may be a store location, a kiosk location, or any suitable physical location of a merchant system 130. In an alternate example, a salesperson 102 may be mobile and arrive at a location of the user 101. For example, the merchant system 130 may be a restaurant and the salesperson 102 may be a delivery person possessing a merchant computing device 150.
  • In certain example embodiments, the hands-free payment application 116 alerts the user 101 when the user 101 is in the vicinity of a merchant system 130 that accepts hands-free payments. The alert may be provided via a message on the user computing device 110, via an email or a text, or in any suitable manner.
  • The alert may be based on the location of the user 101 as determined by the GPS module 118. For example, the hands-free payment application 116 accesses the GPS data from the GPS module 118 and compare the GPS location to a list of locations of merchant systems 130 that accept hands-free payments. If a match results from the comparison, then an alert is generated and provided to the user. The match may result if the user 101 is within a configured distance of the merchant system 130.
  • The alerts may be configured to alert in any suitable manner. In an example, the alerts may be combined in commercially dense environment or the alerts may be presented individually. In another example, the alerts may be configured to only alert the user 101 a configured number of times. For example, the alert may be presented three times, but upon a fourth instance, the alert is not presented. The alerts may be presented as a notification with an audible alert, a vibration, a popup alert on the user interface 115 of the user computing device 110, or other suitable alert.
  • In block 440, the user computing device 110 recognizes a beacon via wireless communication at the location of the merchant system 130 and approves the merchant system 130. Block 440 is described in more detail hereinafter with reference to the methods 440 a and 440 b described in FIGS. 6 and 7.
  • FIG. 6 is a block flow diagram depicting a method 440 a for a user computing device 110 to recognize a beacon via wireless communication at a location of a merchant system and approve the merchant system, in accordance with certain example embodiments. The method 440 a is described with reference to the components illustrated in FIG. 1. In certain embodiments, some or all of the blocks of the method 440 a are performed by the payment processing system 140. For example, the beacon identifier and other suitable data are transmitted to the payment processing system 140 for analysis and verification.
  • In block 610, the user computing device 110 receives the beacon. The user computing device 110 may be configured to search for beacons or other wireless signals. Upon entering the range of the broadcast of the merchant computing device 150, the user computing device 110 receives the beacon. The user computing device 110 may search for a beacon continuously, when instructions to begin searching for the beacon are received from the user 101, when the location of the user computing device 110 dictates a beacon is near, or at any suitable time. In an example, the user computing device 110 may provide an alert that a merchant system 130 at the location of the user computing device 110 is listed on a database as a participant in the hands-free transaction program. Upon recognizing that the a merchant system 130 is listed on the database as a participant in the hands-free transaction program, the user computing device 110 may begin a search for beacons or provide a recommendation to the user 101 that a search should be conducted.
  • When the user computing device 110 receives the beacon, the user computing device 110 determines the communication technology being used and stores the data associated with the beacon. The data may be stored on the data storage unit 112 or in any suitable location. In certain embodiments, the user computing device 110 transmits the beacon data to the payment processing system 140 and, the payment processing system 140 conducts some or all of the remaining steps of the method 440 a.
  • In block 620, the user computing device 110 identifies the beacon identifier. The user computing device 110 interprets the data transmitted in the beacon and recognizes that the beacon is associated with the payment processing system 140 and/or the hands-free payment application 116 based on the data in the beacon. In an example, the hands-free payment application 116 extracts data from the beacon, such as a beacon identifier, a merchant system 130 name, communication technology requirements, or any other suitable information.
  • The user computing device 110 locates the beacon identifier in the beacon data via any suitable method. For example, the user computing device 110 may analyze the content and extract the beacon identifier based on the location of the identifier within the data, based on instructions from the merchant computing device 150, based on instructions within the data identifying the location, based on an industry standard, or based on any other suitable method.
  • In block 630, the user computing device 110 accesses a list of approved beacon identifiers. The list may comprise beacon identifiers that are approved by the payment processing system 140, by the user 101, by a financial institution that issued a payment account to the user 101, or by any other suitable party. Additionally, the list may be composed by one party and revised or limited by another party. The list may be stored on the data storage unit 112, on the payment processing system 140, cloud computing environment, or any suitable storage location. The user computing device 110 may access the list in any suitable manner, such as over the network 120.
  • In block 640, the user computing device 110 determines that the beacon identifier is represented on the list of approved beacon identifications. The user computing device 110 may compare the data from the beacon to the database of beacon data to determine an identity of the merchant system 130 associated with the beacon and to verify the authenticity of the beacon. If the beacon identifier is listed on the database as a verified beacon identifier associated with a verified merchant system 130, then the method 440 a may proceed. In certain embodiments, the user computing device 110 may use a prefix, a suffix or some regular expression to determine if the beacon identifier is potentially a valid identifier. The user computing device 110 device may communicate with the payment processing system 140 to further verify the authenticity of the beacon based on regular expression.
  • In certain example embodiments, the hands-free payment application 116 has received a list of one or more merchant systems 130 with which the user 101 does not wish to conduct hands-free transactions. If the hands-free payment application 116 identifies the merchant system 130 on the list, then the hands-free payment application 116 will not respond to the beacon identifier. In this case, hands-free payment application 116 may end any wireless communication with the payment processing system 140 and/or with the merchant computing device 150 and not provide any response or acknowledgement to the merchant computing device 150 while the user computing device 110 is at the location of the merchant system 130. Additionally or alternatively, the payment processing system 140 cease responding or acknowledging the merchant computing device 150.
  • The list may be populated by the user 101, the payment processing system 140, or any suitable party. In an example, a user 101 adds a merchant system 130 to the list based on a previous experience, because the merchant system 130 does not appear trustworthy, or for any suitable reason.
  • If the payment processing system 140, in an alternate embodiment, performed some or all of the blocks of method 440 a, then the payment processing system 140 transmits the determination that the beacon identifier is represented on the list of approved beacon identifications to the user computing device 110.
  • From block 640, the method 440 a proceeds to block 230 of FIG. 2.
  • An alternate embodiment of block 440 of FIG. 4 is explained in greater detail in the method 440 b of FIG. 7.
  • FIG. 7 is a block flow diagram depicting a method 440 b for a user computing device 110 to recognize a beacon via wireless communication at a location of a merchant system 130 and approve the merchant system 130 using location data, in accordance with certain example embodiments. The method 440 b is described with reference to the components illustrated in FIG. 1. In certain embodiments some or all of the blocks of the method 440 b are performed by the payment processing system 140. For example, the beacon identifier, the location data, and other suitable data are transmitted to the payment processing system 140 for analysis and verification.
  • Blocks 610 and 620 of FIG. 7 are substantially similar to Blocks 610 and 620 of FIG. 6 as described previously herein.
  • In block 730, the user computing device 110 accesses a list of approved beacon identifiers and merchant system locations. The list may comprise beacon identifiers and locations of merchant systems 130 that are approved by the payment processing system 140, by the user 101, by a financial institution that issued a payment account to the user 101, or by any other suitable party. Additionally, the list may be composed by one party and revised or limited by another party. The list may be stored on the data storage unit 112, on the payment processing system 140, cloud computing environment, or any suitable storage location. The user computing device 110 may access the list in any suitable manner, such as over the network 120. In certain embodiments, the payment processing system 140 will access the list upon receiving the beacon identifier and other data from the user computing device 110.
  • The locations of the merchant systems 130 are associated with the beacon identifiers that are associated with the merchant systems 130. For example, a particular merchant system 130 would be identified with a particular beacon identifier and a particular location in the database. The location may be stored as a longitude and latitude, a street address, or any suitable location identification. The locations may be provided by the merchant system 130, obtained from mapping programs, input by payment processing system 140 operators, or provided by any suitable source. In certain embodiments, the locations of the merchant systems 130 are in the same database with the beacon identifiers. In alternate embodiments, the locations of the merchant systems 130 are in a second database.
  • In block 740, the user computing device 110 determines the location of the user 101. For example, the user computing device 110 uses the GPS module 118 of the user computing device 110 to determine the location. In the example, the GPS module 118 communicates with one or more satellites of the Global Positioning System (“GPS”) or other satellite-based location system to determine the location of the user computing device 110. In an example embodiment, the delivery system 140 periodically or continuously communicates with the GPS module 118 during applicable time periods to determine and log the location of the user computing device 110. In another embodiment, the location of the user computing device 110 is identified based on Wi-Fi signals, cellular location, or any suitable location identifying technology. Any location determining hardware, software, or combination of hardware and software is represented by the GPS module 118.
  • After determining the location, the user computing device 110 stores the location for comparison with the merchant system database. In certain embodiments, the user computing device 110 transmits the determined location to the payment processing system 140 to compare to the database.
  • In block 750, the user computing device 110 determines if a location of the user computing device 110 matches an expected location of the merchant system 130 based on the location associated with the beacon identifier in the database. The user computing device 110 compares the stored location of the user computing device 110 to the location of the merchant system 130 associated with the beacon identifier. For example, the user computing device 110 locates the beacon identifier in the database and identifies the merchant system 130 associated with the beacon identifier. The user computing device 110 then identifies the location of the merchant system 130 from the database. The identified location is compared to the location received from the user computing device 110.
  • If the locations are identical or within a configured distance of each other, then a location match is identified. For example, if the locations are determined to be less than 100 feet apart, then a match is identified. If the locations are greater than 100 feet apart, then a match is not identified. Any suitable distance, such as 10 feet, 100 feet, or 500 feet, may be used.
  • In certain embodiments, the payment processing system 140 determines if a location of the user computing device 110 matches an expected location of the merchant system 130 based on the location associated with the beacon identifier in a similar manner.
  • In block 760, if the locations match, then the user computing device 110 determines that the beacon identifier is represented on the list of approved beacon identifications. If no match is identified, then the beacon is not verified as an approved beacon from an approved merchant system 130. If the beacon identifier is verified, then the method 440 b may proceed. In certain embodiments, the payment processing system 140 determines that the beacon identifier is represented on the list of approved beacon identifications in a similar manner.
  • If the payment processing system 140 identified the match, then the payment processing system 140 transmits the match to the user computing device 110 so that the user computing device 110 may proceed to create a token.
  • From block 760, the method 440 b returns to block 230 of FIG. 2.
  • Returning to FIG. 2, in block 230, the user computing device 110 provides token authorization to the merchant system 130. Block 230 is described in greater detail in the method 230 of FIG. 5.
  • FIG. 5 is a block flow diagram depicting a method 230 for a user computing device 110 to provide a token authorization to the merchant system 130, in accordance with certain example embodiments. The method 230 is described with reference to the components illustrated in FIG. 1.
  • In block 510, the user computing device 110 generates a token for a potential transaction. The token may be any data associated with the user account that is generated by the user computing device 110 for secure transmission to another computing device. The token may represent an authorization or acknowledgement by the user computing device 110 that the user computing device 110 is in communication with a merchant computing device 110 and that a transaction may be forthcoming. The token may comprise a user account identifier, the beacon identifier, a user computing device 110 identifier, or any suitable data. The token may be encrypted or otherwise configured to only be readable by one or more of the payment processing system hands-free module 141, the user computing device 110, a financial account server associated with the payment processing system 140, or any suitable computing system.
  • In certain example embodiments, the token, or certain portions of the token, is not readable by the merchant computing device 150. To generate the token, the user computing device 110 may compile all of the data needed for the token into a data file and insert identifiers, labels, or other items to prepare the token for transmission. The token may provide a time that the token will expire. For example, the token may only be usable for one hour after being generated. In the example, after the one hour has elapsed, the token is no longer valid for use and the payment processing system 140 will reject any transaction request including an expired token. In certain example embodiments, the token comprises the beacon identifier, the location of the user computing device 110, the user account identifier, or any other suitable data.
  • The token may be generated by the hands-free application 116, or another application module or component of the user computing device 110. For example, an application executing on a secure element or other secure memory of the user computing device 110 may generate the token. The token may be generated in response to receiving the beacon from the merchant computing device 150. That is, the token is not generated until the user computing device 110 recognizes the beacon and recognizes a need to transmit the token based on the identify of the merchant system 130, the location of the user computing device 110, or any other factors. In an alternate embodiment, the token is created in advance. The token, or a series of tokens, may be created and stored on the data storage unit 112 of the user computing device 110. The token may be accessed from the storage location and utilized when requested by the hands-free payment application 116.
  • In certain embodiments, a token is not generated by the user computing device 110. For example, the payment processing system 140 may generate the token. The payment processing system 140 may receive, from the user computing device 110, a set of authentication data for the user account and generate a token. The authentication data may comprise user 101 data, account data, passwords, user computing device 110 data, or any suitable data that may be used to authenticate the user account. The authentication data may be transmitted to the payment processing system 140 when the user computing device 110 receives the beacon from the merchant computing device 150. The user computing device 110 may access the authentication data from a database on the data storage unit 112, or from data stored in the hands-free payment application 116. The authentication data is transmitted in a similar fashion as the description of the transmission of the token from the user computing device 110 to the payment processing system 140. The token that is generated by the payment processing system 140 is transmitted back to the user computing device 110 or to the merchant computing device 150 on behalf of the user computing device 110.
  • In block 520, the user computing device 110 transmits the token to the payment processing system 140. The user computing device 110 may transmit a new token at the time that the user computing device 110 recognizes the beacon and the beacon identifier, at a time that a previous token has expired, or upon any suitable schedule. The user computing device 110 may transmit the token via an Internet communication over the Internet, Bluetooth communication, Wi-Fi communication, cellular connection, or via any suitable communication protocol.
  • In block 530, the payment processing system hands-free module 141 approves the token and transaction parameters. The payment processing system hands-free module 141 receives the token and any associated information from the user computing device 110 and determines if the beacon identifier can be verified.
  • The verification may be similar to the methods of the user computing device 110 to verify the beacon identifier in the method 440 a in FIG. 6 or method 440 b in FIG. 7. For example, the payment processing system hands-free module 141 may compare the beacon identifier to a database to determine if the beacon identifier is registered and approved. The payment processing system hands-free module 141 may compare a location of the user computing device 110, as determined by the global positioning system (“GPS”) module 118, to a database of locations associated with the beacon identifiers. If not provided already, the payment processing system hands-free module 141 may request the GPS location of the user computing device 110 in a communication over the network 120 and receive a response from the user computing device 110. If the location of the user computing device 110 matches the expected location of the merchant computing device 150, then the token is verified. Any other suitable criteria for verifying the token may be employed.
  • The payment processing system hands-free module 141 may verify the user account on the payment processing system 140 to determine if the user account is active and available for transactions. For example, the payment processing system may access the user account and determine if the account has funds available for use as stored value funds, or if the account has a valid credit or debit account associated with the account with which to conduct transaction.
  • In block 540, the payment processing system hands-free module 141 transmits the token to a merchant computing device 150. If the token is verified, the payment processing system hands-free module 141 communicates the token to the merchant computing device 150 to allow a hands-free transaction to be conducted. The token provides the merchant computing device 150 with the authorization to initiate a transaction on behalf of the user account. In an example embodiment, the token is transmitted to the merchant computing device 150 upon the detection by the user computing device of the beacon. Thus, he token is transmitted to the merchant computing device 150 before a transaction is initiated by the merchant computing device 150 or the user computing device 110.
  • In an alternate embodiment, the user computing device 110 provides the token directly to the merchant computing device 150. For example, the user computing device 110 generates the token as described in block 510 and transmits the token to the merchant computing device 150 instead of to the payment processing system 140. In a certain embodiment, the user computing device 110 may require approval from the payment processing device 140 before transmitting the token to the merchant computing device 150.
  • Alternatively, the user computing device may transmit authorization data to the payment processing system. The authentication data may comprise user 101 data, account data, passwords, user computing device 110 data, or any suitable data that may be used to authenticate the user account. The authentication data may be transmitted to the payment processing system 140 when the user computing device 110 receives the beacon from the merchant computing device 150. The user computing device 110 may access the authentication data from a database on the data storage unit 112, or from data stored in the hands-free payment application 116. The authentication data is transmitted in a similar fashion as the description of the transmission of the token from the user computing device 110 to the payment processing system 140. The token that is generated by the payment processing system 140 is transmitted back to the user computing device 110. The user computing device 110 then transmits the received token to the merchant computing device 150.
  • From block 540, the method 230 returns to block 240 of FIG. 2.
  • In block 240, the salesperson 102 enters transaction details into the merchant computing device 150. In an example, the user 101 selects a product for purchase at the location of the merchant system 130. The term “product” includes tangible and intangible products, as well as services. The salesperson 102 scans the product with a barcode scanner or in any suitable manner enters the product details into the merchant computing device 150. The transaction data may include the product identification, the product price, quantity of products, merchant location, merchant identification, or any other suitable information.
  • In block 250, the merchant computing device 150 transmits the transaction details and the token to the payment processing system hands-free module 141. The salesperson 102 selects the appropriate token. In an example, only one token is available for selection. In another example, the token is associated with the user 101 when the user 101 enters the merchant location and the token is received. In another example, the token is identifiable as being associated with the user 101 based on an identifier of the user 101, such as a picture.
  • In the example, the merchant computing device 150 has received and stored one or more tokens associated with one or more user accounts. The merchant computing device 150 identifies user account information associated with the tokens. The information may be provided by the token or by a communication with a database associated with the token. In another example, the user account information may have been provided to the merchant computing device 150 with a previous token or in a previous transaction. The user account information and/or the tokens are displayed to the salesperson 102 to allow the salesperson 102 to select the appropriate token or user account. The salesperson 102 identifies the user account or token and associates the user account with the product being purchased by the user 101. The user account may be represented to the salesperson 102 by a picture of the user 101, by a name of the user 101, by a configured alias, or by any suitable identifier of the user 101 or the user account.
  • The salesperson 102 provides an indication on the user interface 155 of the merchant computing device 150 that the user 101 has agreed to the purchase transaction. The user 101 may agree to the transaction by verbally informing the salesperson 102, or by any other suitable method. The salesperson 102 may select on the user interface the transaction details, the token, the user account, and other data and associate the data with the transaction request. The data is associated by the merchant computing device 150 and a transaction request is prepared, such as by entering the data on the appropriate entry blocks on a transaction request template.
  • The merchant computing device 150 transmits the transaction details and the token to the payment processing system 140 to conduct the transaction. The transaction details may be the identification of the product or products to be purchased, the total price, the merchant identification, or any other suitable details.
  • In block 260, the payment processing system 140 conducts the transaction and transmits a confirmation to merchant computing device 150. The payment processing system hands-free module 141 receives the transaction details and the token from the merchant computing device 150 and processes the transaction. The payment processing system hands- free module 141 verifies the token as the same token that was previously received from the user computing device 110 (or generated by the payment processing system hands-free module 141) and provided to the merchant system computing device 150. If the token is not verified as the same token, then the transaction does not proceed. If the token is not verified, the payment processing system hands-free module 141 may request the correct token from the merchant system computing device 150, decline the transaction, alert a payment processing system hands-free module 141 operator, or perform any suitable action to complete or cancel the transaction.
  • Upon a verification of the token, the payment processing system hands-free module 141 determines if the user account has the funds available for the transaction. In an example, the payment processing system hands-free module 141 may apply the transaction by deducting the amount of the transaction from a pool of funds stored in the user account. In another example, the payment processing system hands-free module 141 may provide an authorization request to a financial account issuer, such as a credit or debit card, associated with the account. Upon receiving an authorization from the financial account issuer, the payment processing system hands-free module 141 proceeds with the transaction. The user account may be funded by any other suitable source, such as a bank account, a stored value account, a debit card, or any suitable source. The payment processing system hands-free module 141 debits the appropriate account of the user 101 for the amount of the transaction and credits an account of the merchant for the amount of the transaction.
  • The payment processing system hands-free module 141 provides a notification to the merchant system computing device 150 that the transaction is authorized. The authorization may be presented to the salesperson 102 by the user interface 155 of the merchant computing device 150. Upon receiving the authorization, the salesperson 102 may provide the product and a receipt to the user 101 or the user computing device 110. Upon settlement of the transaction, the payment processing system hands-free module 141 provides the funds for the transaction to the merchant system 130.
  • In block 270, upon a successful conducting of the transaction, the payment processing system 140 transmits a notification of the successful completion of the transaction to the user computing device 110. The notification provides the details of the transaction, such as the transaction amount, the product purchased, and other suitable details. The notification allows the user 101 an opportunity to quickly dispute the charge. For example, the salesperson 102 or the merchant computing device 150 may have associated the wrong token with the transaction details. In another example, the transaction details were in error and an incorrect amount was deducted from the user account. The user 101 receives the notification on the user computing device 110 and views the transaction details on the user interface 115. In an alternate example, the user 101 receives the notification from the payment processing system 140 as an email, a text, as a notification on the hands-free payment application, or in any suitable manner. In an alternate embodiment, the notification may be provided by the merchant computing device 150. For example, the merchant computing device 150 provides a text to the user computing device with the transaction details.
  • The notifications, receipts, and other transaction data may be stored in a list on a database or other storage system on the user computing device 110, the hands-free payment application 116, or any suitable storage location. The notifications, receipts, and other transaction data may be stored in a list on a user account or other location on the payment processing system 140. The user 101 may access the list to review recent transactions, to seek refunds, or for any suitable reason. In certain examples, the list on the user computing device 110 may synchronize with the list on the payment processing system 140 either automatically or when prompted by the user 101.
  • All refunds for transactions may be conducted through the hands-free application 116. The user 101 initiates the hands-free application at the location of the merchant 130. The user 101 presents a transaction identification from a notification or a receipt to complete the refund. For example, the user 101 selects a notification from a recent transaction that has been transmitted to the user computing device 110. The user 101 may select a receipt for a recent transaction from the notification, from a text from the merchant computing device 150, or from any suitable provider. The user 101 may either present the receipt or notification via the hands-free application 116, an email receipt, or a print out of the email receipt.
  • To obtain a refund, a user 101 opens a list of completed transactions on the hands-free application 116 and selects the desired receipt. Additionally, the user 101 may manually enter the transaction identification, or scan a QR code on the receipt displayed on the hands- free application to obtain data from a particular transaction. The user 101 may access a list of recent transactions on the user computing device 110. The list may be displayed on the user interface 115 with control objects for selecting a transaction. The user computing device 110 may receive an input of a selection from the user 101 and transmit the details of the selected transaction to the merchant system computing device 150.
  • Once selected, a full or partial amount can be refunded to the user account. The merchant system 130 may transfer the refund amount to the payment processing system 140 for deposit into the user account. The funds may alternatively be transmitted by the merchant system 130 or the payment processing system 140 to a credit card account or other account associated with the user account. Any other refund method may be employed. The transaction history and receipt in the user account will reflect the full or partial refund.
  • If a user 101 desires to dispute a charge, the user 101 opens the hands-free application 116 and selects an option to dispute a transaction that has been conducted with the user account. The hands-free application 116 transmits a notification to the payment processing system hands-free module 141. An operator at the payment processing system 140 may contact the user 101 to resolve the issue. The hands-free application 116 may further transmit the transaction identification or other transaction details to the payment processing system hands-free module 141.
  • Other Example Embodiments
  • FIG. 8 depicts a computing machine 2000 and a module 2050 in accordance with certain example embodiments. 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 comprise 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 attached components such as a processor 2010, system bus 2020, system memory 2030, storage media 2040, input/output interface 2060, and a network interface 2070 for communicating with a network 2080.
  • The computing machine 2000 may be implemented as a conventional computer system, an embedded controller, a laptop, a server, a mobile device, a smartphone, a set-top box, a kiosk, a vehicular information system, one more processors associated with a television, a customized machine, any other hardware platform, or any combination or multiplicity thereof. The computing machine 2000 may be a distributed system configured to function using multiple computing machines interconnected via a data network or bus system.
  • The processor 2010 may be configured to execute code or instructions to perform the operations and functionality described herein, manage request flow and address mappings, and to perform calculations and generate commands. The processor 2010 may be configured to monitor and control the operation of the components in the computing machine 2000. The processor 2010 may 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, gated logic, discrete hardware components, any other processing unit, or any combination or multiplicity thereof. The processor 2010 may be a single processing unit, multiple processing units, a single processing core, multiple processing cores, special purpose processing cores, co-processors, or any combination thereof. According to certain example embodiments, the processor 2010 along with other components of the computing machine 2000 may be a virtualized computing machine executing within one or more other computing machines.
  • The system memory 2030 may include non-volatile memories 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. The system memory 2030 may also include volatile memories 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 also may be used to implement the system memory 2030. The system memory 2030 may be implemented using a single memory module or multiple memory modules. While the system memory 2030 is depicted as being part of the computing machine 2000, one skilled in the art will recognize that the system memory 2030 may be separate from the computing machine 2000 without departing from the scope of the subject technology. It should also be appreciated that the system memory 2030 may include, or operate in conjunction with, a non-volatile storage device such as the storage media 2040.
  • The storage media 2040 may include a hard disk, a floppy disk, a compact disc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), a Blu-ray disc, a magnetic tape, a flash memory, other non-volatile memory device, 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 multiplicity thereof. The storage media 2040 may store one or more operating systems, application programs and program modules such as module 2050, data, or any other information. The storage media 2040 may be part of, or connected to, the computing machine 2000. The storage media 2040 may also be part of one or more other computing machines that are in communication with the computing machine 2000 such as servers, database servers, cloud storage, network attached storage, and so forth.
  • The module 2050 may comprise one or more hardware or software elements configured to facilitate the computing machine 2000 with performing the various methods and processing functions presented herein. The module 2050 may include one or more sequences of instructions stored as software or firmware in association with the system memory 2030, the storage media 2040, or both. The storage media 2040 may therefore represent examples of machine or computer readable media on which instructions or code may be stored for execution by the processor 2010. Machine or computer readable media may generally refer to any medium or media used to provide instructions to the processor 2010. Such machine or computer readable media associated with the module 2050 may comprise a computer software product. It should be appreciated that a computer software product comprising the module 2050 may also be associated with one or more processes or methods for delivering the module 2050 to the computing machine 2000 via the network 2080, any signal-bearing medium, or any other communication or delivery technology. The module 2050 may also comprise hardware circuits or information for configuring hardware circuits such as microcode or configuration information for an FPGA or other PLD.
  • The input/output (“I/O”) interface 2060 may be configured to couple to one or more external devices, to receive data from the one or more external devices, and to send data to the one or more external devices. Such external devices along with the various internal devices may also be known as peripheral devices. The I/O interface 2060 may include both electrical and physical connections for operably coupling the 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 the 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 small computer system interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel, peripheral component interconnect (“PCI”), PCI express (PCIe), serial bus, parallel bus, advanced technology attached (“ATA”), serial ATA (“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, 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 as part of, all of, or to operate in conjunction with, the system bus 2020. The I/O interface 2060 may include one or more buffers for buffering transmissions between one or more external devices, internal devices, the computing machine 2000, or the processor 2010.
  • The I/O interface 2060 may couple the computing machine 2000 to various input devices including mice, touch-screens, scanners, electronic digitizers, sensors, receivers, touchpads, trackballs, cameras, microphones, keyboards, any other pointing devices, or any combinations thereof. The I/O interface 2060 may couple the computing machine 2000 to various output devices including video displays, speakers, printers, projectors, tactile feedback devices, automation control, robotic components, actuators, motors, fans, solenoids, valves, pumps, transmitters, signal emitters, lights, and so forth.
  • The computing machine 2000 may operate in a networked environment using logical connections through the network interface 2070 to one or more other systems or computing machines across the network 2080. The network 2080 may include wide area networks (WAN), local area networks (LAN), intranets, the Internet, wireless access networks, wired networks, mobile networks, telephone networks, optical networks, or combinations thereof. The network 2080 may be packet switched, circuit switched, of any topology, and may use any communication protocol. Communication links within the network 2080 may involve various digital or an analog communication media such as fiber optic cables, free-space optics, waveguides, electrical conductors, wireless links, antennas, radio-frequency communications, and so forth.
  • The processor 2010 may be connected to the other elements of the computing machine 2000 or the various peripherals discussed herein through the system bus 2020. It should be appreciated that the system bus 2020 may be within the processor 2010, outside the processor 2010, or both. According to some embodiments, any of the processor 2010, the other elements of the computing machine 2000, or the various peripherals discussed herein may be integrated into a single device such as a system on chip (“SOC”), system on package (“SOP”), or ASIC device.
  • In situations in which the systems discussed here collect personal information about users, or may make use of personal information, the users may be provided with an opportunity or option to control whether programs or features collect user information (e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current location), or to control whether and/or how to receive content from the content server that may be more relevant to the user. In addition, certain data may be treated in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be treated so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, ZIP code, or state level), so that a particular location of a user cannot be determined. Thus, the user may have control over how information is collected about the user and used by a content server.
  • Embodiments may comprise a computer program that embodies the functions described and illustrated herein, wherein the computer program is implemented in a computer system that comprises instructions stored in a machine-readable medium and a processor that executes the instructions. However, it should be apparent that there could be many different ways of implementing embodiments in computer programming, and the embodiments should not be construed as limited to any one set of computer program instructions. Further, a skilled programmer would be able to write such a computer program to implement an embodiment of the disclosed embodiments based on the appended flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use embodiments. Further, those skilled in the art will appreciate that one or more aspects of embodiments described herein may be performed by hardware, software, or a combination thereof, as may be embodied in one or more computing systems. Moreover, any reference to an act being performed by a computer should not be construed as being performed by a single computer as more than one computer may perform the act.
  • The example embodiments described herein can be used with computer hardware and software that perform the methods and processing functions described herein. The systems, methods, and procedures described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry. The software can be stored on computer-readable media. For example, computer-readable media can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc. Digital circuitry can include integrated circuits, gate arrays, building block logic, field programmable gate arrays (FPGA), etc.
  • The example systems, methods, and acts described in the embodiments presented previously are illustrative, and, in alternative embodiments, certain acts can be performed in a different order, in parallel with one another, omitted entirely, and/or combined between different example embodiments, and/or certain additional acts can be performed, without departing from the scope and spirit of various embodiments. Accordingly, such alternative embodiments are included in the scope of the following claims, which are to be accorded the broadest interpretation so as to encompass such alternate embodiments.
  • Although specific embodiments have been described above in detail, the description is merely for purposes of illustration. It should be appreciated, therefore, that many aspects described above are not intended as required or essential elements unless explicitly stated otherwise. Modifications of, and equivalent components or acts corresponding to, the disclosed aspects of the example embodiments, in addition to those described above, can be made by a person of ordinary skill in the art, having the benefit of the present disclosure, without departing from the spirit and scope of embodiments defined in the following claims, the scope of which is to be accorded the broadest interpretation so as to encompass such modifications and equivalent structures.

Claims (7)

What is claimed is:
1. A computer-implemented method to conduct automatic hands-free transactions based on determinations that user computing devices are located at merchant locations, comprising:
receiving, by a user computing device, a beacon identifier from a merchant computing device associated with a particular merchant computing system;
determining, by the user computing device, a location of the user computing device at a time when the user computing device received the beacon identifier from the merchant computing device;
receiving, by one or more computing devices, a communication from the user computing device, the communication comprising the received beacon identifier and the determined location of the user computing device;
identifying in a database, by the one or more computing devices, the particular merchant computing system associated with the beacon identifier and a location of the particular merchant;
determining, by the one or more computing devices, a location of the user computing device based on the location communicated by the user computing device;
determining, by the one or more computing devices, that the location of the user computing device matches the identified location of the particular merchant computing system; and
communicating, by the one or more computing devices, the determination that the location of the user computing device matches the identified location of the particular merchant computing system to the user computing device.
2. The computer-implemented method of claim 1, wherein the beacon identifier is a service set identifier.
3. The computer-implemented method of claim 1, wherein the location is determined based on data from a global positioning system module of the user computing device.
4. The computer-implemented method of claim 1, wherein the location of the merchant computing system is a street address.
5. The computer-implemented method of claim 1, wherein the location is determined based on data from a Wi-Fi communication received by the user computing device from a Wi-Fi transmitter.
6. The computer-implemented method of claim 1, wherein the beacon identifier is received, via a wireless communication, by the user computing device from the merchant computing device.
7. The computer-implemented method of claim 1, further comprising receiving, by the one or more computing devices, a token authorization from the user computing device.
US16/233,442 2014-07-11 2018-12-27 Hands-free transactions verified by location Pending US20190130408A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US201462023739P true 2014-07-11 2014-07-11
US14/540,009 US10185960B2 (en) 2014-07-11 2014-11-12 Hands-free transactions verified by location
US16/233,442 US20190130408A1 (en) 2014-07-11 2018-12-27 Hands-free transactions verified by location

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US16/233,442 US20190130408A1 (en) 2014-07-11 2018-12-27 Hands-free transactions verified by location

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/540,009 Continuation US10185960B2 (en) 2014-07-11 2014-11-12 Hands-free transactions verified by location

Publications (1)

Publication Number Publication Date
US20190130408A1 true US20190130408A1 (en) 2019-05-02

Family

ID=55067870

Family Applications (6)

Application Number Title Priority Date Filing Date
US14/540,001 Active 2036-01-13 US10460317B2 (en) 2014-07-11 2014-11-12 Hands-free transaction tokens via payment processor
US14/540,004 Abandoned US20160012421A1 (en) 2014-07-11 2014-11-12 Hands-free transactions using beacon identifiers
US14/540,009 Active 2036-02-22 US10185960B2 (en) 2014-07-11 2014-11-12 Hands-free transactions verified by location
US14/539,997 Active US9652759B2 (en) 2014-07-11 2014-11-12 Hands-free transactions
US15/492,718 Pending US20170221065A1 (en) 2014-07-11 2017-04-20 Hands-free transactions
US16/233,442 Pending US20190130408A1 (en) 2014-07-11 2018-12-27 Hands-free transactions verified by location

Family Applications Before (5)

Application Number Title Priority Date Filing Date
US14/540,001 Active 2036-01-13 US10460317B2 (en) 2014-07-11 2014-11-12 Hands-free transaction tokens via payment processor
US14/540,004 Abandoned US20160012421A1 (en) 2014-07-11 2014-11-12 Hands-free transactions using beacon identifiers
US14/540,009 Active 2036-02-22 US10185960B2 (en) 2014-07-11 2014-11-12 Hands-free transactions verified by location
US14/539,997 Active US9652759B2 (en) 2014-07-11 2014-11-12 Hands-free transactions
US15/492,718 Pending US20170221065A1 (en) 2014-07-11 2017-04-20 Hands-free transactions

Country Status (1)

Country Link
US (6) US10460317B2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10460317B2 (en) 2014-07-11 2019-10-29 Google Llc Hands-free transaction tokens via payment processor
US10474879B2 (en) 2016-07-31 2019-11-12 Google Llc Automatic hands free service requests
US10482463B2 (en) 2016-03-01 2019-11-19 Google Llc Facial profile modification for hands free transactions

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160342979A1 (en) * 2014-04-08 2016-11-24 Capital One Services, Llc Systems and methods for transaction authentication using dynamic wireless beacon devices
KR20160131572A (en) * 2015-05-08 2016-11-16 삼성전자주식회사 Method and apparatus for certificating information related payment in a mobile communication system
US20170039568A1 (en) * 2015-07-14 2017-02-09 NXT-ID, Inc. Personalized and Dynamic Tokenization Method and System
US10332096B2 (en) * 2015-07-27 2019-06-25 Paypal, Inc. Wireless communication beacon and gesture detection system
US10594689B1 (en) 2015-12-04 2020-03-17 Digimarc Corporation Robust encoding of machine readable information in host objects and biometrics, and associated decoding and authentication
KR20170093419A (en) * 2016-02-05 2017-08-16 삼성전자주식회사 Method and apparatus for providing crowdsourcing services
WO2017151820A1 (en) * 2016-03-01 2017-09-08 Google Inc. Network security based on proximity with ip whitelisting
US20170316417A1 (en) * 2016-04-28 2017-11-02 Yu-Hsuan Wang Systems and methods for incentivizing transactions
US20180101834A1 (en) * 2016-10-06 2018-04-12 Paypal, Inc. Wireless communication beacon offer and transaction system
US20180247283A1 (en) * 2017-02-24 2018-08-30 MPD Spark LLC System and method for processing beacon-initiated mobile transactions
US10755281B1 (en) 2017-03-31 2020-08-25 Square, Inc. Payment transaction authentication system and method
US10448313B2 (en) * 2017-04-11 2019-10-15 Google Llc Identifying users via mobile hotspots
US20180315038A1 (en) * 2017-04-28 2018-11-01 Square, Inc. Multi-source transaction processing
US20200275267A1 (en) * 2017-09-20 2020-08-27 Visa International Service Association Hands free interaction system and method
WO2019067944A1 (en) * 2017-09-29 2019-04-04 Visa International Service Association Federated closed-loop system

Family Cites Families (175)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5280527A (en) 1992-04-14 1994-01-18 Kamahira Safe Co., Inc. Biometric token for authorizing access to a host system
US6230148B1 (en) 1994-11-28 2001-05-08 Veristar Corporation Tokenless biometric electric check transaction
US6783459B2 (en) 1997-08-22 2004-08-31 Blake Cumbers Passive biometric customer identification and tracking system
US6941274B1 (en) 1997-11-28 2005-09-06 Diebold, Incorporated Automated transaction machine
US6636833B1 (en) 1998-03-25 2003-10-21 Obis Patents Ltd. Credit card system and method
US6315193B1 (en) 1998-08-31 2001-11-13 Mastercard International Incorporated Financial transaction card with installment loan feature
JP2000113085A (en) 1998-10-08 2000-04-21 Sony Corp Electronic cash system
US7047416B2 (en) 1998-11-09 2006-05-16 First Data Corporation Account-based digital signature (ABDS) system
EP1131761A4 (en) 1998-11-17 2005-07-06 Prenet Corp Electronic payment system utilizing intermediary account
CA2373208A1 (en) 1999-05-19 2000-11-23 Digimarc Corporation Methods and systems for processing audio
US6934381B1 (en) 1999-08-16 2005-08-23 Avaya Technology Corp. Contact routing system and method
AU782832C (en) 2000-01-05 2006-04-27 Electronic Finger Print Technologies Limited Method and apparatus for authenticating financial transactions
WO2001054038A1 (en) 2000-01-20 2001-07-26 David Thieme System and method for facilitating secure payment with privacy over a computer network including the internet
US6847953B2 (en) * 2000-02-04 2005-01-25 Kuo James Shaw-Han Process and method for secure online transactions with calculated risk and against fraud
CA2319919A1 (en) 2000-09-15 2002-03-15 Twin Lion Systems Inc. On-line payment system
US6934389B2 (en) 2001-03-02 2005-08-23 Ati International Srl Method and apparatus for providing bus-encrypted copy protection key to an unsecured bus
EP1246144A3 (en) 2001-03-29 2003-11-12 Telefonaktiebolaget Lm Ericsson Wireless point of sale transaction
GB0113630D0 (en) 2001-06-05 2001-07-25 Koninkl Philips Electronics Nv Payment authorisation through beacons
US6601762B2 (en) 2001-06-15 2003-08-05 Koninklijke Philips Electronics N.V. Point-of-sale (POS) voice authentication transaction system
AUPS087602A0 (en) 2002-03-04 2002-03-28 Ong, Yong Kin (Michael) Electronic fund transfer system
US8396809B1 (en) * 2002-05-14 2013-03-12 Hewlett-Packard Development Company, L.P. Method for reducing purchase time
AU2003262746A1 (en) 2002-08-20 2004-03-11 Fusionarc, Inc. Method of multiple algorithm processing of biometric data
US7318235B2 (en) 2002-12-16 2008-01-08 Intel Corporation Attestation using both fixed token and portable token
US8694352B1 (en) 2003-04-22 2014-04-08 Reflexis Systems, Inc. System and method for providing handheld field force data gathering automation in a big box retail environment
WO2005031663A2 (en) 2003-09-26 2005-04-07 Mastercard International Incorporated Method and system for biometrically enabling a proximity payment device
US20050129286A1 (en) 2003-12-16 2005-06-16 Hekimian Christopher D. Technique using eye position and state of closure for increasing the effectiveness of iris recognition authentication systems
KR100439437B1 (en) 2003-12-18 2004-07-09 주식회사 교원나라 Bank transaction system for linked accounts via common account
US9530132B2 (en) 2004-01-27 2016-12-27 George Chester Cox System and method for customer video authentication to prevent identity theft
JP2006139476A (en) 2004-11-11 2006-06-01 Glory Ltd Debit settlement system and debit settlement method
US8768838B1 (en) 2005-02-02 2014-07-01 Nexus Payments, LLC Financial transactions using a rule-module nexus and a user account registry
RU2007135925A (en) 2005-02-28 2009-04-10 Нокиа Сименс Нетуоркс Ой (FI) Solution of the problem of transmission of service for connecting cellular communications networks based on multiprotocol marking
US7849020B2 (en) 2005-04-19 2010-12-07 Microsoft Corporation Method and apparatus for network transactions
US20070084913A1 (en) 2005-10-18 2007-04-19 Capital One Financial Corporation Systems and methods for authorizing a transaction for a financial account
US20070183634A1 (en) 2006-01-27 2007-08-09 Dussich Jeffrey A Auto Individualization process based on a facial biometric anonymous ID Assignment
US8234220B2 (en) 2007-02-21 2012-07-31 Weiss Kenneth P Universal secure registry
US7853708B2 (en) 2006-02-24 2010-12-14 Cisco Technology, Inc. Techniques for replacing point to point protocol with dynamic host configuration protocol
WO2008018052A2 (en) 2006-08-10 2008-02-14 Seergate Ltd. Secure mechanism and system for processing financial transactions
US8566242B2 (en) 2006-11-22 2013-10-22 Ebay Inc. Network-based consumer transactions with credit accounts
US8384516B2 (en) 2007-01-12 2013-02-26 Voorhuis Plc, Limited Liability Company System and method for radio frequency identifier voice signature
US8694792B2 (en) 2007-02-16 2014-04-08 Honeywell International Inc. Biometric based repeat visitor recognition system and method
JP2008205861A (en) 2007-02-20 2008-09-04 Matsushita Electric Ind Co Ltd Viewing and listening quality determining apparatus, viewing and listening quality determining method, viewing and listening quality determining program, and storage medium
WO2008134595A1 (en) 2007-04-27 2008-11-06 Pelago, Inc. Determining locations of interest based on user visits
US7930249B2 (en) 2007-07-11 2011-04-19 Qualcomm Incorporated Mobile wireless financial instrument for automatically selecting a payment instrument
US7761381B1 (en) 2007-10-31 2010-07-20 Intuit Inc. Method and system for approving of financial transactions
US8558663B2 (en) 2007-11-30 2013-10-15 Bank Of America Corporation Integration of facial recognition into cross channel authentication
US8793509B1 (en) 2008-02-12 2014-07-29 Google Inc. Web authorization with reduced user interaction
US20090313129A1 (en) 2008-06-11 2009-12-17 Lmr Inventions, Llc System and method for verifying user identity information in financial transactions
US8897808B2 (en) 2008-06-27 2014-11-25 Verizon Patent And Licensing Inc. Systems and methods for facilitating a third-party service based on location of a mobile device
EP2465082A4 (en) 2009-08-14 2015-04-01 Payfone Inc System and method for paying a merchant using a cellular telephone account
US20100084462A1 (en) 2008-10-02 2010-04-08 German Scipioni Systems and methods for secure photo identification at point of sale
WO2010040206A1 (en) 2008-10-07 2010-04-15 Codapay Reverse payment transaction system and method
WO2010053899A2 (en) 2008-11-06 2010-05-14 Visa International Service Association Online challenge-response
CN101800639A (en) 2009-02-09 2010-08-11 华为终端有限公司 Method, system and device for realizing ebanking services
US8473352B2 (en) 2009-03-24 2013-06-25 The Western Union Company Consumer due diligence for money transfer systems and methods
US8788429B2 (en) 2009-12-30 2014-07-22 First Data Corporation Secure transaction management
US8645213B2 (en) 2010-01-15 2014-02-04 Ebay, Inc. Transactions associated with a mobile device
US8864581B2 (en) 2010-01-29 2014-10-21 Microsoft Corporation Visual based identitiy tracking
US20110238476A1 (en) 2010-03-23 2011-09-29 Michael Carr Location-based Coupons and Mobile Devices
US10304051B2 (en) 2010-04-09 2019-05-28 Paypal, Inc. NFC mobile wallet processing systems and methods
US20110257985A1 (en) 2010-04-14 2011-10-20 Boris Goldstein Method and System for Facial Recognition Applications including Avatar Support
WO2011137082A1 (en) 2010-04-26 2011-11-03 Ebay, Inc. Reverse payment flow
US20110307403A1 (en) 2010-06-11 2011-12-15 Arad Rostampour Systems and method for providing monitoring of social networks
US9760905B2 (en) 2010-08-02 2017-09-12 Visa International Service Association Systems and methods to optimize media presentations using a camera
JP2011014174A (en) 2010-10-22 2011-01-20 Japan Research Institute Ltd Electronic settlement system, personal terminal, terminal for member store, authentication-settlement device, electronic settlement method, and electronic settlement program
US8396485B2 (en) 2010-11-09 2013-03-12 Apple Inc. Beacon-based geofencing
US8706559B2 (en) 2010-12-23 2014-04-22 Mastercard International Incorporated Methods and systems for activating a contactless transaction card
US20120313761A1 (en) 2011-01-06 2012-12-13 John Rolin Power Management for an Active RFID Tag in Credit Card Form Factor
WO2012112992A2 (en) 2011-02-18 2012-08-23 Google Inc. Facial recognition
US8824749B2 (en) 2011-04-05 2014-09-02 Microsoft Corporation Biometric recognition
US9285944B1 (en) 2011-04-22 2016-03-15 Angel A. Penilla Methods and systems for defining custom vehicle user interface configurations and cloud services for managing applications for the user interface and learned setting functions
US10380570B2 (en) 2011-05-02 2019-08-13 Ondot System, Inc. System and method for secure communication for cashless transactions
KR101754852B1 (en) 2011-05-30 2017-07-06 김재형 Method for Settling Reverse-Order
US9621350B2 (en) 2011-06-30 2017-04-11 Cable Television Laboratories, Inc. Personal authentication
US20130006810A1 (en) 2011-06-30 2013-01-03 Aurelio Elias Method and system for the execution of non-bank Third Party Services Transactions over Financial Networks through Electronic Terminals utilizing a Non-Depository Virtual Account Management System
US20130024308A1 (en) 2011-07-18 2013-01-24 Tata Consultancy Services Limited Self check out using a portable device
US9444547B2 (en) 2011-07-26 2016-09-13 Abl Ip Holding Llc Self-identifying one-way authentication method using optical signals
WO2013019567A2 (en) 2011-07-29 2013-02-07 Visa International Service Association Passing payment tokens through an hop/sop
US20130035979A1 (en) 2011-08-01 2013-02-07 Arbitron, Inc. Cross-platform audience measurement with privacy protection
FR2978891B1 (en) 2011-08-05 2013-08-09 Banque Accord METHOD, SERVER AND SYSTEM FOR AUTHENTICATING A PERSON
DE202012100620U1 (en) 2011-11-22 2012-06-13 Square, Inc. System for processing cardless payment transactions
US20140006123A1 (en) 2011-12-09 2014-01-02 Weyenot, Inc. Microgift System and Method of Operation
US20140040139A1 (en) 2011-12-19 2014-02-06 Sequent Software, Inc. System and method for dynamic temporary payment authorization in a portable communication device
KR101242390B1 (en) 2011-12-29 2013-03-12 인텔 코오퍼레이션 Method, apparatus and computer-readable recording medium for identifying user
GB2492614B (en) 2012-02-28 2014-01-29 Barclays Bank Plc System and method for authenticating a payment transaction
US8898088B2 (en) 2012-02-29 2014-11-25 Google Inc. In-card access control and monotonic counters for offline payment processing system
KR101409754B1 (en) 2012-03-12 2014-06-19 에스케이플래닛 주식회사 System for payment of off-line transaction, method thereof and apparatus thereof
US9741045B1 (en) 2012-03-16 2017-08-22 Square, Inc. Ranking of merchants for cardless payment transactions
US8615439B2 (en) 2012-04-16 2013-12-24 Wal-Mart Stores, Inc. Processing online transactions
US8254647B1 (en) 2012-04-16 2012-08-28 Google Inc. Facial image quality assessment
AU2013204110B2 (en) 2012-04-18 2014-08-21 Google Llc Processing payment transactions without a secure element
EP2828814A4 (en) 2012-04-18 2015-12-16 Ebp Tecnologia Desenvolvimento De Sist S Ltda System and method for data and identity verification and authentication
CN106879047B (en) 2012-05-02 2020-06-09 阿里巴巴集团控股有限公司 Method for near-field information transfer, information transmission and receiving client and information system
US20130346201A1 (en) 2012-06-22 2013-12-26 QUALCOMM Labs Incorporated Method for in-store competition with internet sales pricing
US8676709B2 (en) 2012-07-31 2014-03-18 Google Inc. Merchant category codes in a proxy card transaction
US9626678B2 (en) 2012-08-01 2017-04-18 Visa International Service Association Systems and methods to enhance security in transactions
US20140040135A1 (en) 2012-08-03 2014-02-06 Visa International Service Association Systems and methods to digitally sign transactions
US9124574B2 (en) 2012-08-20 2015-09-01 Saife, Inc. Secure non-geospatially derived device presence information
CA2825635A1 (en) 2012-08-28 2014-02-28 Solink Corporation Transaction verification system
US9519903B2 (en) 2012-08-29 2016-12-13 24/7 Customer, Inc. Method and apparatus for proactive notifications based on the location of a user
US10026119B2 (en) 2012-09-10 2018-07-17 Google Llc Efficient transfer of funds between accounts
US9665858B1 (en) 2012-10-11 2017-05-30 Square, Inc. Cardless payment transactions with multiple users
US9264850B1 (en) 2012-11-20 2016-02-16 Square, Inc. Multiple merchants in cardless payment transactions and multiple customers in cardless payment transactions
KR101330943B1 (en) 2012-12-10 2013-11-26 신한카드 주식회사 Transaction method using one time card information
WO2014093390A1 (en) 2012-12-10 2014-06-19 Visa International Service Association Authenticating remote transactions using a mobile device
US9374369B2 (en) 2012-12-28 2016-06-21 Lookout, Inc. Multi-factor authentication and comprehensive login system for client-server networks
US9940620B2 (en) 2013-01-14 2018-04-10 Capital One Services, Llc Systems and methods for processing customer purchase transactions using biometric data
CA2898205A1 (en) 2013-01-30 2014-08-28 Paypal, Inc. Transaction token issuing authorities
US20140222596A1 (en) 2013-02-05 2014-08-07 Nithin Vidya Prakash S System and method for cardless financial transaction using facial biomertics
US9652791B1 (en) 2013-02-08 2017-05-16 Square, Inc. Updating merchant location for cardless payment transactions
US8924735B2 (en) 2013-02-15 2014-12-30 Microsoft Corporation Managed biometric identity
US20140279458A1 (en) 2013-03-15 2014-09-18 Elwha Llc Devices, methods, and systems for assisting multiple discrete devices
US20160078430A1 (en) 2013-03-15 2016-03-17 Capital One Financial Corporation System and method for digital authentication
JP2014191416A (en) 2013-03-26 2014-10-06 Hitachi Kokusai Electric Inc Service user confirmation apparatus
US9710800B2 (en) 2013-05-03 2017-07-18 Oracle International Corporation Using voice input at a mobile point of sale
WO2014182787A2 (en) 2013-05-08 2014-11-13 Jpmorgan Chase Bank, N.A. Systems and methods for high fidelity multi-modal out-of-band biometric authentication
US20140351132A1 (en) 2013-05-22 2014-11-27 Google Inc. Returns handling in a prepaid architecture
US9870556B2 (en) 2013-05-22 2018-01-16 Google Llc Split tender in a prepaid architecture
US9754258B2 (en) 2013-06-17 2017-09-05 Visa International Service Association Speech transaction processing
US10192231B2 (en) 2013-07-01 2019-01-29 United Airlines, Inc. Mobile payment system with rewards points
DK2821931T3 (en) 2013-07-02 2019-08-26 Precise Biometrics Ab Verification application, method, electronic device and computer application.
KR102166041B1 (en) 2013-07-18 2020-10-16 삼성전자 주식회사 Method And Apparatus For Performing Authentication Based On Biometrics
US9053310B2 (en) 2013-08-08 2015-06-09 Duo Security, Inc. System and method for verifying status of an authentication device through a biometric profile
JP2014099156A (en) 2013-08-19 2014-05-29 Nomura Research Institute Ltd Information processing system
WO2015026862A1 (en) 2013-08-19 2015-02-26 Estimote, Inc. Wireless beacon and methods
US9633345B2 (en) 2013-08-28 2017-04-25 Paypal, Inc. Merchant point of sale security system
US20150081550A1 (en) 2013-09-10 2015-03-19 Scvngr, Inc. Remote transaction processing using biometrics
US9805366B1 (en) 2013-09-16 2017-10-31 Square, Inc. Associating payment information from a payment transaction with a user account
US20150269583A1 (en) 2014-03-24 2015-09-24 Thomas Jason Taylor Device for face-key purchasing
US9727866B2 (en) 2013-10-15 2017-08-08 Intuit Inc. Methods systems and computer program products for verifying consumer identity during transaction
US20150120473A1 (en) 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Vendor-facilitated guaranty provisioning
US8930274B1 (en) 2013-10-30 2015-01-06 Google Inc. Securing payment transactions with rotating application transaction counters
WO2015072191A1 (en) 2013-11-14 2015-05-21 日本電気株式会社 Customer information management device, storefront terminal, customer information management method, and program
US9189659B2 (en) 2013-12-06 2015-11-17 Fish Six RC Secure code generation for customer tracking
US20150170136A1 (en) 2013-12-18 2015-06-18 PayRange Inc. Method and System for Performing Mobile Device-To-Machine Payments
US9820093B2 (en) 2013-12-20 2017-11-14 Apple Inc. Programmable beacon payloads
US20150178652A1 (en) * 2013-12-23 2015-06-25 Egan Schulz Systems and methods for targeted assistance on user check-in
US9770206B2 (en) 2014-01-17 2017-09-26 Rajeev Ashokan Touch input biometric apparatuses and methods of using the same
US20150371234A1 (en) 2014-02-21 2015-12-24 Looppay, Inc. Methods, devices, and systems for secure provisioning, transmission, and authentication of payment data
US9268793B2 (en) 2014-03-12 2016-02-23 Google Inc. Adjustment of facial image search results
US20150302412A1 (en) 2014-04-17 2015-10-22 Google Inc. Online bank transfer transactions
WO2015164584A1 (en) 2014-04-23 2015-10-29 Google Inc. User interface control using gaze tracking
US9881303B2 (en) 2014-06-05 2018-01-30 Paypal, Inc. Systems and methods for implementing automatic payer authentication
US9717108B2 (en) 2014-06-20 2017-07-25 Visa International Service Association Midrange contactless transactions
US9589263B2 (en) 2014-06-27 2017-03-07 Paypal, Inc. Automatic payment code display system
US9639907B2 (en) * 2014-06-27 2017-05-02 Paypal, Inc. Communication of orders and payments in a drive through using wireless beacons
WO2016007801A1 (en) 2014-07-11 2016-01-14 Google Inc. Hands-free transactions with a challenge request
US10671996B2 (en) 2014-07-11 2020-06-02 The Toronto-Dominion Bank Systems and methods for providing pre-paid multicards
US20160012422A1 (en) 2014-07-11 2016-01-14 Google Inc. Hands-free transactions with a transaction confirmation request
WO2016007445A1 (en) 2014-07-11 2016-01-14 Google Inc. Hands-free transactions
US10460317B2 (en) 2014-07-11 2019-10-29 Google Llc Hands-free transaction tokens via payment processor
CN107077664A (en) 2014-07-11 2017-08-18 谷歌公司 Exempt to hit offline communications
US9384486B2 (en) 2014-07-15 2016-07-05 Verizon Patent And Licensing Inc. Secure financial payment
JP2016024758A (en) 2014-07-24 2016-02-08 陽介 西田 Point information management program and method
US9818114B2 (en) 2014-08-11 2017-11-14 Mastercard International Incorporated Systems and methods for performing payment card transactions using a wearable computing device
US10152698B2 (en) 2014-08-26 2018-12-11 Samsung Electronics Co., Ltd. System and method for mobile payments in a vehicle
WO2016029319A1 (en) 2014-08-27 2016-03-03 Samer Ziade Systems and methods for facilitating secure ordering, payment and delivery of goods or services
US9684826B2 (en) 2014-08-28 2017-06-20 Retailmenot, Inc. Reducing the search space for recognition of objects in an image based on wireless signals
US9972004B1 (en) 2014-09-29 2018-05-15 Amazon Technologies, Inc. Proximity-based mobile device payments
US10397220B2 (en) 2015-04-30 2019-08-27 Google Llc Facial profile password to modify user account data for hands-free transactions
US9619803B2 (en) 2015-04-30 2017-04-11 Google Inc. Identifying consumers in a transaction via facial recognition
US10733587B2 (en) 2015-04-30 2020-08-04 Google Llc Identifying consumers via facial recognition to provide services
US20160342967A1 (en) 2015-05-21 2016-11-24 Green Dot Corporation Systems and Methods for Banking Platform Isolation
CN106211122B (en) 2015-05-27 2020-01-24 意法半导体股份有限公司 Method for managing multiple profiles in a SIM module, SIM module and computer readable medium
US10438177B2 (en) 2015-06-15 2019-10-08 Worldpay, Llc System and method for third party payment at point of sale terminals
US20170024731A1 (en) 2015-07-22 2017-01-26 Green Dot Corporation Systems and Methods for Dynamic Account Routing
US20170053276A1 (en) 2015-08-21 2017-02-23 Green Dot Corporation Systems and Methods for Transaction Routing
US9519901B1 (en) 2015-09-16 2016-12-13 Square, Inc. Biometric payment technology
US20170091765A1 (en) 2015-09-30 2017-03-30 Bank Of America Corporation Non-intrusive geo-location determination associated with transaction authorization
US20170116589A1 (en) 2015-10-23 2017-04-27 Paypal, Inc. Portable point-of-sale devices
EP3374915A1 (en) 2016-03-01 2018-09-19 Google LLC Facial template and token pre-fetching in hands free service requests
KR102195222B1 (en) 2016-03-01 2020-12-24 구글 엘엘씨 Direct settlement of hands-free transactions
KR102084174B1 (en) 2016-03-01 2020-04-23 구글 엘엘씨 Modify face profile for hands-free trading
US10510077B2 (en) 2016-05-03 2019-12-17 Facebook, Inc. Facial recognition identification for in-store payment transactions
US20170364901A1 (en) 2016-06-19 2017-12-21 Google Inc. Identifying user computing device specific locations
JP2019532441A (en) 2016-07-31 2019-11-07 グーグル エルエルシー Automatic hands-free service request

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10460317B2 (en) 2014-07-11 2019-10-29 Google Llc Hands-free transaction tokens via payment processor
US10482463B2 (en) 2016-03-01 2019-11-19 Google Llc Facial profile modification for hands free transactions
US10839393B2 (en) 2016-03-01 2020-11-17 Google Llc Facial profile modification for hands free transactions
US10474879B2 (en) 2016-07-31 2019-11-12 Google Llc Automatic hands free service requests

Also Published As

Publication number Publication date
US20160012420A1 (en) 2016-01-14
US10460317B2 (en) 2019-10-29
US20160012413A1 (en) 2016-01-14
US20170221065A1 (en) 2017-08-03
US20160012421A1 (en) 2016-01-14
US20160012414A1 (en) 2016-01-14
US10185960B2 (en) 2019-01-22
US9652759B2 (en) 2017-05-16

Similar Documents

Publication Publication Date Title
US10628817B2 (en) Processing payment transactions without a secure element
US10268999B2 (en) Determining languages for a multilingual interface
AU2019200260B2 (en) Methods and systems for wallet enrollment
US20190213673A1 (en) Systems and methods for transferring funds using a wireless device
US20190057364A1 (en) Managing devices associated with a digital wallet account
US10664833B2 (en) Transactions utilizing multiple digital wallets
US20210035147A1 (en) Loyalty Account Identification
JP2019215909A (en) Securing payment transaction using circulating application transaction counter
US10579981B2 (en) Selecting a preferred payment instrument
US8924259B2 (en) Mobile device payments
US9123038B2 (en) Methods for discovering and paying debts owed by a group
US10423959B2 (en) Voice recognition to authenticate a mobile payment
US9264850B1 (en) Multiple merchants in cardless payment transactions and multiple customers in cardless payment transactions
KR20160105297A (en) Method for providing payment service and electronic device thereof
US10826898B2 (en) Facial profile password to modify user account data for hands free transactions
AU2012368266B2 (en) Systems and methods to provide check-in based payment processes
US20170109745A1 (en) Instant token issuance system
US10733587B2 (en) Identifying consumers via facial recognition to provide services
US10726407B2 (en) Identifying consumers in a transaction via facial recognition
US20140244506A1 (en) Dynamic payment authorization system and method
US20140052532A1 (en) Portable device wireless reader and payment transaction terminal functionality with other portable devices
CA2955197A1 (en) Mobile communication device with proximity based communication circuitry
US10592884B2 (en) Split tender in a prepaid architecture
US20170085563A1 (en) System for validating a biometric input
US10134041B2 (en) Method, medium, and system for online fraud prevention

Legal Events

Date Code Title Description
AS Assignment

Owner name: GOOGLE INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHITILIAN, VAROUJ;CHANDRASEKARAN, SASHIKANTH;LEE, JOHNIE;AND OTHERS;REEL/FRAME:047872/0424

Effective date: 20141112

Owner name: GOOGLE LLC, CALIFORNIA

Free format text: ENTITY CONVERSION;ASSIGNOR:GOOGLE INC.;REEL/FRAME:047992/0705

Effective date: 20170929

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION