Abstract: A method for providing a token code in conjunction with a value token is disclosed. The token code serves as a shared secret for authenticating the use of the value token. Multiple token holders can possess the same value token, but each token holder may have a different token code for use with the value token.

Abstract: A method for tokenizing credentials is disclosed. In addition to a token, a verification value can be provided for each interaction. The verification value can be generated based at least in part on a dynamic data element. The dynamic data element may be kept secret, while the verification value can be distributed for use during an interaction. When the verification value is used, it can be validated by re-creating the verification value based at least on the stored dynamic data element.

Abstract: A method for providing a token code in conjunction with a value token is disclosed. The token code serves as a shared secret for authenticating the use of the value token. Multiple token holders can possess the same value token, but each token holder may have a different token code for use with the value token.

Abstract: The UNIVERSAL ELECTRONIC PAYMENT APPARATUSES, METHODS AND SYSTEMS (“UEP”) transform touchscreen inputs into a virtual wallet mobile application interface via UEP components into purchase transaction triggers and receipt notices. In one implementation the UEP provides, via a user device, a product information search request; and obtains, in response to the product information search request, information on a first product for sale by a first merchant and a second product for sale by a second merchant. The UEP generates a single purchase transaction request, using the information on the first product for sale by the first merchant and the second product for sale by the second merchant. The UEP provides, via the user device, the single purchase transaction request for payment processing. Also, the UEP obtains an electronic purchase receipt for the first product for sale by the first merchant and the second product for sale by the second merchant.

Abstract: A method for tokenizing credentials is disclosed. In addition to a token, a verification value can be provided for each interaction. The verification value can be generated based at least in part on a dynamic data element. The dynamic data element may be kept secret, while the verification value can be distributed for use during an interaction. When the verification value is used, it can be validated by re-creating the verification value based at least on the stored dynamic data element.

Abstract: A method for tokenizing credentials is disclosed. In addition to a token, a verification value can be provided for each interaction. The verification value can be generated based at least in part on a dynamic data element. The dynamic data element may be kept secret, while the verification value can be distributed for use during an interaction. When the verification value is used, it can be validated by re-creating the verification value based at least on the stored dynamic data element.

Abstract: A method for tokenizing credentials is disclosed. In addition to a token, a verification value can be provided for each interaction. The verification value can be generated based at least in part on a dynamic data element. The dynamic data element may be kept secret, while the verification value can be distributed for use during an interaction. When the verification value is used, it can be validated by re-creating the verification value based at least on the stored dynamic data element.

Abstract: Techniques described herein relate to using tokenization with BIN table routing by configuring a computer system, such as an acquirer computer, to utilize a token BIN translation table to determine which payment processing network(s) are eligible to route a transaction based upon a utilized token. In an embodiment, each token BIN translation table entry associates a token BIN with one or more payment processing networks that are eligible to route transactions. An acquirer computer, upon receiving a token for a transaction, thus may flexibly route the transaction to an eligible network from the set of payment processing networks identified by the entry corresponding to the token's BIN value. The entry may further identify verification methods for the eligible payment processing networks, and may identify product type attributes of the account associated with the token, either of which may be used in determining which payment processing network to select.

Abstract: Techniques described herein relate to using tokenization with BIN table routing by configuring a computer system, such as an acquirer computer, to utilize a token BIN translation table to determine which payment processing network(s) are eligible to route a transaction based upon a utilized token. In an embodiment, each token BIN translation table entry associates a token BIN with one or more payment processing networks that are eligible to route transactions. An acquirer computer, upon receiving a token for a transaction, thus may flexibly route the transaction to an eligible network from the set of payment processing networks identified by the entry corresponding to the token's BIN value. The entry may further identify verification methods for the eligible payment processing networks, and may identify product type attributes of the account associated with the token, either of which may be used in determining which payment processing network to select.

Abstract: The UNIVERSAL ELECTRONIC PAYMENT APPARATUSES, METHODS AND SYSTEMS (“UEP”) transform touchscreen inputs into a virtual wallet mobile application interface via UEP components into purchase transaction triggers and receipt notices. In one implementation the UEP provides, via a user device, a product information search request; and obtains, in response to the product information search request, information on a first product for sale by a first merchant and a second product for sale by a second merchant. The UEP generates a single purchase transaction request, using the information on the first product for sale by the first merchant and the second product for sale by the second merchant. The UEP provides, via the user device, the single purchase transaction request for payment processing. Also, the UEP obtains an electronic purchase receipt for the first product for sale by the first merchant and the second product for sale by the second merchant.

Abstract: A method for utilizing a non-transactable account identifier with a payment token is disclosed. The non-transactable account identifier can have the same format as a primary account number (PAN) and the payment token, but is not used to conduct a payment transaction.

Abstract: A method for utilizing a non-transactable account identifier with a payment token is disclosed. The non-transactable account identifier can have the same format as a primary account number (PAN) and the payment token, but is not used to conduct a payment transaction.

Abstract: The UNIVERSAL ELECTRONIC PAYMENT APPARATUS, METHODS AND SYSTEMS (“UEP”) transform touchscreen inputs into a virtual wallet mobile application interface via UEP components into purchase transaction triggers and receipt notices. In one implementation the UEP provides, via a user device, a product information search request; and obtains, in response to the product information search request, information on a first product for sale by a first merchant and a second product for sale by a second merchant. The UEP generates a single purchase transaction request, using the information on the first product for sale by the first merchant and the second product for sale by the second merchant. The UEP provides, via the user device, the single purchase transaction request for payment processing. Also, the UEP obtains an electronic purchase receipt for the first product for sale by the first merchant and the second product for sale by the second merchant.

Abstract: A method for utilizing a non-transactable account identifier with a payment token is disclosed. The non-transactable account identifier can have the same format as a primary account number (PAN) and the payment token, but is not used to conduct a payment transaction.

Abstract: A method for utilizing a non-transactable account identifier with a payment token is disclosed. The non-transactable account identifier can have the same format as a primary account number (PAN) and the payment token, but is not used to conduct a payment transaction.

Abstract: A method for utilizing a non-transactable account identifier with a payment token is disclosed. The non-transactable account identifier can have the same format as a primary account number (PAN) and the payment token, but is not used to conduct a payment transaction.

Abstract: A method for providing a token code in conjunction with a value token is disclosed. The token code serves as a shared secret for authenticating the use of the value token. Multiple token holders can possess the same value token, but each token holder may have a different token code for use with the value token.

Abstract: Systems and methods related to a cryptocurrency system that enables transactions to be performed by transferring digital assets corresponding to amounts between appropriate entities are described. The cryptocurrency system includes a digital assets service provider computer that can host digital asset accounts associated with consumers and resource providers at which digital assets can be received. Consumers can be unbanked and use their digital asset account to perform cashless transactions. In one exemplary transaction, a consumer can receive change for the transaction as a digital asset that is assigned to their digital asset account. In another exemplary transaction, the consumer can use digital assets assigned to their digital asset account to pay for the transaction. Transfers of digital assets between accounts is managed by a ledger of transactions, which may be in the form of a block chain that cryptographically secures data that is stores.

Abstract: A method for utilizing a non-transactable account identifier with a payment token is disclosed. The non-transactable account identifier can have the same format as a primary account number (PAN) and the payment token, but is not used to conduct a payment transaction.

Abstract: A method for providing a token code in conjunction with a value token is disclosed. The token code serves as a shared secret for authenticating the use of the value token. Multiple token holders can possess the same value token, but each token holder may have a different token code for use with the value token.