Paypal, Inc.

Dinesh Gomes

Nitin Prabhu

Vyomesh Sharma

Ian Povey

Ashwini Vishwanath

Darshankumar Bhadrasinh Desai

Rachna Tibrewala

Methods and systems are provided to receive token context data from a token request, determine parameters of a custom token, and generate and communicate the custom token. Tokens may be generated that are compatible with one or more payment providers from a plurality of possible payment providers. Data related to current and future conditions of the payment providers, merchant preferences, customer preferences, locations of the merchant, customer, and/or the transaction, and regulatory rules may be used to select the payment provider.

Rule-based token service provider

There are provided systems and methods for a payment information autofill mechanism that links a browser application with a user account such that a payment page at the browser application can be automatically filled based on the link. Specifically, the autofill mechanism establishes a link between a browser application running on a user device and a user account associated with the user that is stored at the server. When the user engages with the browser application to conduct a transaction on a merchant website, an application programming interface (API) call can be made to retrieve user virtual card information for automatically populating the payment data fields at the transaction page.

Systems and methods for configuration information autofill at a browser linked with user accounts

In some embodiments, a method for binding a user's information to a user's account with a payment service provider includes receiving a request to pay for a transaction using the user's account with the payment service provider. The request to pay specifies a funding instrument. Additionally, the payment service provider is a source of the funding instrument, and the transaction is between the user and a merchant application. The method also includes generating a common identifier (ID) corresponding to the funding instrument, and generating a payment token corresponding to the common ID and the funding instrument. The common ID is a non-transactable token associated with the merchant application and the user, and the payment token is a non-transactable token that corresponds to the common ID. The method further includes binding the user's payment service provider account to the payment token and the common ID.

Processing a transaction using electronic tokens

In some embodiments, a verification system includes a memory storing a common identifier that identifies a user. The system may also include one or more hardware processors coupled to the memory and configured to read instructions from the memory to perform the steps of: receiving a token associated with a request to complete a transaction with an environment; determining the common identifier associated with the token, the common identifier being associated with an identifier of the merchant, an identifier of the user requesting the transaction, and a funding instrument associated with the user; and determining, based on information associated with the common identifier, whether to approve the transaction.

Token service provider for electronic/mobile commerce transactions

A method for verifying transactions is discussed. The method includes receiving a transaction request for performing a transaction between a user account and a merchant account. The method includes determining, based on authentication of the user account, a common identifier associated with the user account, the common identifier indicating the user account being authorized for use at a plurality of merchant accounts including the merchant account. The method includes determining a payment token for performing the transaction, the determining the payment token based on the common identifier and a user associated with the user account. The method also includes providing the payment token for completing the transaction.

Growing community of inventors

San Jose, CA, United States of America

Dinesh Gomes