Google Inc.

Harry Lee Butler, Iv

Bobby Wieler

Justin Lee Brickell

Ignacio Carlos Blanco

Xiaohang Wang

Glenn Berntson

Jonathan Kingsley Blatter

Denis Lila

Glenn Thrope

Colin Fleming

Osama Bedier

Peter Hazlehurst

Michael Blandina

Swaminathan Mahadevan

In an example embodiment, the user initiates a digital wallet transaction at a point of sale ('POS') terminal of a merchant system. The POS terminal receives payment account information options associated with the user's digital wallet account from the account management system to display to the user. The user selects one or more payment account information options via a user interface of the POS terminal. The account management system receives an indication of the user's one or more selections, generates one or more payment tokens based on the corresponding selected payment account information options, and transmits the one or more payment tokens to the POS terminal for use in a transaction. The POS terminal communicates with one or more issuer systems associated with the selected payment account information options to process the transaction using corresponding payment tokens. The user receives a transaction receipt at the POS terminal.

Providing payment account information associated with a digital wallet account to a user at a merchant point of sale device

A bundle of public counters and a corresponding bundle of private counters are created and transmitted to a user device. The user device receives a request and processes the request without accessing a secure element processor on the user device. The user device calculates a security code using the private counter and a number. The user device transmits the calculated security code and one of the bundle of public counters in response to the request. A receiver of the response to the request determines the validity of the public counter and looks up the corresponding private counter using the public counter. The receiver determines the validity of the security code by recomputing it using the private counter and the number.

Secure interface using non-secure element processors

Identifying the geolocation of POS terminals using non-payment events to predict when the geolocation of a computing device at a time when the device detects events corresponds to the geolocation of the terminal. The device monitors for pre-selected events and transmit data to the account system. The account system determines a frequency of the events and it reaches a pre-defined threshold, the account system identifies the location of the terminal by identifying the common geolocation of the events. The identified geolocation is saved so that when a user then enters the location and transmits event data to the account system, the system can compare the geolocation of the event data to the saved geolocation to determine whether the computing device is located at the terminal. If the computing device is located at the terminal, the account system transmits offers or other content for display and use at the identified terminal.

Point of sale terminal geolocation

A method for maintaining a prepaid payment system comprises a user account that can be utilized to complete a purchase transaction with a merchant. A delayed processing window is introduced between a time when the merchant receives a payment approval notification from the payment system and a time when the payment system transmits a payment request to an issuer of a funding account associated with the user's payment system account. The payment system utilizes a user's stored value account maintained by the payment system to satisfy the requirements of a prepaid program, and therefore processes the payment request received from the merchant and transmits the payment approval notification without obtaining prior authorization from the issuer of the funding account. The payment system submits one or more payment requests for the funding transaction at a time after the completion of the purchase transaction between the user and the merchant.

Split tender in a prepaid architecture

Delayed processing window in a prepaid architecture

Inferring purchase intent using non-payment transaction signals predicts whether a payment transaction has been completed based on non-payment information. An account system that operates outside of the payment path does not take part in and the approval of a financial transaction between the user and the merchant system, distributes an offer to the user. The user completes a financial payment transaction with the merchant and the account system determines whether a trigger event has occurred. The user performs an action or enters information using the user computing device, and the user computing device transmits an indication of the action to the account system. In another example, the account system receives notification from another system or device. The account system determines whether the action is a trigger event and the predictive model determines whether the user completed a financial transaction and/or redeemed the distributed offer.

Inferring purchase intent using non-payment transaction events

Using discretionary data fields to secure transactions comprises a payment system employing a server configured to associate a payment account of a user with a user computing device, the payment account comprising a payment account identifier that identifies the payment account, and establish a authentication challenge and an corresponding challenge response. The payment system receives a first payment authorization request originating from a merchant computing system comprising the payment account identifier, data associated with the payment account identifier, and a request to fund a transaction using the payment account, wherein the data associated with the payment account identifier comprises a challenge response provided by the user computing device located in a discretionary data field. The payment system compares the provided challenge response with the corresponding challenge response, and approves the transaction based on whether the provided challenge response and the corresponding challenge response match.

Dynamic alteration of track data

An account management system creates a bundle of private application transaction counters (ATCs) and a bundle of corresponding public ATCs, and transmits them to a user device. The device receives a request for payment information from a merchant and processes the request without accessing a secure element processor on the device. The device calculates a security code using one of the bundle of private ATCs and a transaction number received from the merchant. The device transmits proxy account information, the calculated security code, and the corresponding public ATCs to the merchant. The merchant transmits a payment request to the account management system as the issuer of the proxy account information. The account management system retrieves the private ATC using the public ATC, and determines the validity of the security code by recomputing it. The account management system retrieves the financial account information and requests authorization from the issuer.

Growing community of inventors

New York, NY, United States of America

Harry Lee Butler, Iv