Abstract: The method comprises receiving an onboarding request for a first onboarding process of a first representation of a first user at a token issuance and transaction system, the request received from a transaction system, the request indicating a second onboarding process of a second representation of the first user at the transaction system. The method includes generating, based on performing the first onboarding process and receiving an indication of success of the second onboarding process, a link between the first and second representations at the token issuance and transaction system and the transaction system. The method includes receiving a pre-transaction request from the transaction system, the pre-transaction request indicating a transaction type and the link between the first and second representations. The method also includes determining, based on the link, whether to generate a payment token for completing a requested transaction corresponding to the pre-transaction request.

Abstract: 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.

Abstract: A system or method may be provided to implement dynamic hybrid wallet tokens. The method can includes determining to generate a hybrid wallet token based on a user request for a transaction at a user device. The method includes determining, based on a transaction type of the transaction, non-payment information of a user associated with the user device. The method includes generating a hybrid wallet token for use with a payment account associated with the user, where the generating is based on the authorization token and on the transaction type, the hybrid wallet token comprising information indicating a funding instrument associated with the user, the hybrid wallet token further comprising the non-payment information. The method also includes providing the wallet token to the user device for implementing the transaction.

Abstract: The method comprises receiving a transaction request, including a token, from a first system for using the token for a transaction, the token associated with a user account at a second system. The method includes accessing preferences for the token, the preferences indicating association between the token and an initial resource for transactions, the preferences including transaction rules for altering transaction processing, the preferences created during generation of the token. The method includes determining, based on the preferences and the transaction request, whether to revise use of the initial resource to another resource during transaction processing. The method includes processing the first using the token and based on the user account and the preferences, the processing the transaction including using the another resource.

Abstract: In some embodiments, a method of processing a multiple-use token includes receiving a first request to pay for an online transaction using a digital wallet. The online transaction is between the user and a merchant application. The method also includes generating a multiple-use token corresponding to the online transaction and the digital wallet and sending the multiple-use token to the merchant application. The method further includes receiving a transaction authorization request to pay for a second transaction between the user and a merchant associated with the merchant application, and validating the multiple-use token in accordance with the transaction authorization request and a set of policies defined for the multiple-use token. If the multiple-use token is valid, the digital wallet is charged in accordance with the transaction authorization request.

Abstract: 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.

Abstract: 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.

Abstract: A system or method may be provided to implement dynamic hybrid wallet tokens. A payment network architecture may be established to allow a payment service provider to implement seamless flow of payment transactions. Hybrid dynamic wallet tokens may be morphed with additional information based on the types of transactions to be performed and may be communicated over industry payment networks. In particular, the payment service provider may use Industry Standard BINs as tokens to transmit information in lieu of actual funding source information to all interacting parties with the provision of securely allowing each party to de-tokenize via secure connection from the backend to identify the true funding instrument only when needed.

Abstract: Systems and methods for transferring funds to an user account include a payment service provider device receiving a request for fund transfer information for an user account from a payer device that is associated with a payer. The payment service provider device then provides a routing number that is associated with the payment service provider and a virtual account number that is associated with the user account to the payer device. The payment service provider device then receives information from a financial institution about a funds transfer to a payment service provider account that is provided to a payment service provider by the financial institution. The information about the funds transfer includes a funding amount and the virtual account number, and the payment service provider device allocates the funding amount to the user account using the virtual account number.