A method includes receiving a request to verify a dynamic security code included in a transaction authorization request message. The transaction authorization request message was generated in connection with a payment account transaction. The method further includes performing a verification process with respect to the dynamic security code to generate a verification result. In addition, the transaction authorization request message may be modified by adding the verification result to the transaction authorization request message. Also, the modified transaction authorization request message may be transmitted to an issuer of a payment account designated for use in the payment account transaction.

The present embodiments include a system and method for provisioning, storing, and deriving a cryptocurrency wallet. The system includes a card, a user device, an administrator processor, and a server. The method includes generating a private key and a public key over a user datum, encrypting the keys over a key-encryption-key (KEK), and transmitting the keys to a card. The keys can be optionally stored on a server in encrypted form. Alternatively, the keys can be derived from the user datum if the user has lost them.

Various embodiments are directed to applying, via contactless card authentication, one or more restrictions to a virtual card number and generating the card number for use by a recipient. The one or more restrictions may be specifically personalized to the recipient and may include, for example, a merchant restriction, an amount restriction, a time period restriction, or a location restriction. The generated virtual card number along with the applied one or more restrictions may be consumed in various ways, such as writing the number to a blank card, transmitting the number directly to the recipient's computing device, etc., all via near-field communication.

A method for tokenization of information associated with a payment card includes: transmitting a registration request including a primary account number (PAN) of the payment card to a server; sending, by the server, a request for a secure element (SE) package that includes a payment token and a payment-token-key to an issuer server, the payment token being a surrogate value of the PAN; and in response to receipt of the SE package from the issuer server, transmitting the SE package to an electronic card to be stored therein.

Systems, methods, and computer-readable media for providing accurate images of cards. An application executing on a mobile device may receive authentication credentials for an account, determine a card associated with the account, and determine a card manufacturer identifier (CMID) of the card. The application may receive, from a digital asset management system based on the CMID, a plurality of metadata attributes of the card and one or more images of the card. The application may determine, based on the metadata attributes and attributes of the mobile device, a first orientation of the card to enable near-field communication (NFC) data transfer between the card and the mobile device. The application may select a first image of the card. The application may generate a graphical user interface (GUI) including the first image and an indication specifying to tap the card to the mobile device according to the first orientation.

The present disclosure generally relates to the use of loyalty accounts, private label payment accounts, and general payment accounts using a wearable electronic device with an electronic wallet. In some examples, an electronic device displays a user interface for linking a payment account associated with the electronic device to a second electronic device.

A device receives, from a user device, a request to generate a verification code for a transaction associated with a user of the user device, and receives user profile information associated with a transaction card to be used for the transaction. The device generates a random verification code for the transaction based on the request and the user profile information, and authenticates the random verification code, based on the user profile information, to generate an authenticated random verification code. The device provides the authenticated random verification code to the user device, and receives transaction information, including the authenticated random verification code, from a merchant device associated with the transaction. The device validates the transaction based on the transaction information, and provides, to the merchant device associated with the transaction, information indicating that the transaction is validated.

A computerized system for activating, issuing and otherwise managing transactions and activities pertaining to stored-value cards over a communications network. A central information database is provided for storing stored-value cardholder and card purchaser information received directly from respective stored-value cardholders and card purchasers PCs through a universal central processor via respective communication gateways. The central processor is coupled for communication realtime to multiple unaffiliated stored-value card processing networks normally operated by respective hosts. Each network includes a stored-value card processor coupled to a stored-value card database and multiple respective merchant communication devices. The central processor is programmed for managing the activation and issuance of transactions and activities for the stored-value card through the respective unaffiliated networks. The universal central processor is programmed to issue the stored-value cards directly to the cardholder or card purchaser by download over respective communication gateways. The universal central processor is further programmed for reporting the card activations, issuances, transactions and activities to the cardholders and the merchants thereby providing a universal management system.

A cardholder enters (305) payment information and a freely-selected transaction CVV in a merchant system (20). A payment system (30) receives (400) a request from the merchant system including the transaction CVV and transaction information, and sends (405) a transaction authorization request to a cardholder device (13). The transaction information are displayed (310) on the cardholder device and invites the cardholder to enter the transaction CVV for confirmation purpose. In response, the cardholder enters (315) a confirmation CVV. The payment system approves (240, 415) the transaction when the transaction and confirmation CVVs are the same. As a result, the CVV can have a short life and be changed at each transaction, thereby increasing the security of the transactions. Also, PCI certification constraints on servers are reduced since no issuer master key is required for the CVVs. Lastly, the cardholder has more control on the transaction validation.

A hardware security module (HSM) includes a first HSM instance and a second HSM instance. The first HSM instance is configured to process a first type of service request. The second HSM instance is configured to process a second type of service request. The first HSM instance and the second HSM instance are physically on a same HSM. The first HSM instance is logically separated from the second HSM instance. The first type of service request is a service request that differs from the second type of service request.