A payment device including a medium is disclosed. A first programmable chip and a first magnetic stripe are disposed on the medium. The first programmable chip and the first magnetic stripe are associated with a first payment account. A second programmable chip and a second magnetic stripe are disposed on the medium. The second programmable chip and the second magnetic stripe are associated with a second payment account. The first and second programmable chips are programmed separately for each of the first and second payment accounts.

The present disclosure involves systems, software, and computer implemented methods for automatically modifying a payment instrument type of a user. One example method comprises receiving, via a communications module, a first signal including an indication of acceptance associated with a particular product selected from a set of potential products for replacing a current product associated with a first customer. At least one term or condition associated with the selected product is identified that is different than the terms or conditions associated with the at least one current product. The terms and conditions associated with the at least one current product associated with the first customer are automatically modified to correspond with the at least one different identified term or condition associated with the selected product, wherein modifying the terms or conditions does not change a unique identifier associated with the at least one current product being modified.

An identity management device and system. The device comprises a processor operably coupled to a memory, a display, and a communication interface. The device can have stored thereupon instructions that, when executed by processor, cause the processor to implement a user device interface configured to receive, from user device through the communication interface and store in the memory, at least one identification record comprising visually depictable identification data and a user interface configured to update the display to depict the visually depictable identification data. The identification record can comprise authentication data. Authentication data can be displayed on the device or securely transmitted.

This disclosure describes a card-scan system that can update a card-scan machine learning model to improve card-character predictions for payment cards, driver licenses, or other character-bearing cards by using an active-learning technique that learns from card-scan representations indicating corrections by users to predicted card characters. In particular, the disclosed systems can use a client device to capture and analyze a set of card images of a character-bearing card to predict card characters using a card-scan machine learning model. The disclosed systems can further receive card-scan gradients representing one or more corrections to incorrectly predicted card characters. Based on the card-scan gradients, the disclosed systems can generate active-learning metrics and retrain or update the card-scan machine learning model based on such active-learning metrics. By utilizing and updating the card-scan machine learning model, the disclosed systems can improve the accuracy with which card-character-detection systems predict card characters while preserving data security and verifying the presence of a physical character-bearing card.

Systems and methods for managing a user-selected card verification code (CVC2) value for a payment card are disclosed. A sever is coupled to a payment card database and a hardware security module. The server is programmed to receive a request from a user to change the CVC2 value of the payment card to the user-selected CVC2 value. Based upon the request, the server retrieves from a payment card table stored on the database a payment card record associated with the payment card. The server transmits the user-selected CVC2 value, and, from the payment card record, a primary account number, a payment card expiry date, and a first service code to a hardware security module. The server subsequently receives from the hardware security module a second service code associated with the user-selected CVC2 value. The server updates the first service code in the payment card record to the second service code.

A transaction card may power on the transaction card using electric current induced from an interaction of the transaction card with an electromagnetic field. The transaction card may establish a communication with a device. The communication may indicate that the transaction card has powered. The transaction card may receive, from the device, a set of instructions to configure a set of applets on the transaction card after notifying the device that the transaction card has powered on. The set of applets to be configured may be related to completing one or more different transactions. The set of applets to be configured may be different than another set of applets already configured on the transaction card. The transaction card may configure the set of applets on the transaction card according to the set of instructions after receiving the set of instructions.

A transaction card may power on the transaction card using electric current induced from an interaction of the transaction card with an electromagnetic field. The transaction card may establish a communication with a device. The communication may indicate that the transaction card has powered. The transaction card may receive, from the device, a set of instructions to configure a set of applets on the transaction card after notifying the device that the transaction card has powered on. The set of applets to be configured may be related to completing one or more different transactions. The set of applets to be configured may be different than another set of applets already configured on the transaction card. The transaction card may configure the set of applets on the transaction card according to the set of instructions after receiving the set of instructions.

Account registration using a contactless card. A payment application executing on a device may receive a request to generate a payment account using a contactless card. The payment application may receive encrypted data from the contactless card and transmit the encrypted data to a server associated with the contactless card. The device may receive a push notification from the server and open an account application associated with the contactless card responsive to selection of the push notification. The account application may receive confirmation to generate the payment account using the contactless card and transmit the confirmation to the server. The device may open the payment application responsive to receiving verification of the encrypted data from the server. The payment application may fill form fields with account data received from the server and generate the payment account using the account data received from the server filled into the form fields.

A Digital Transaction Processing Unit (DTPU) operable to host one or more transaction applications, each transaction application for digitally transacting with a Digital Transaction Device (DTD), the DTPU further operable to be reversibly placed into a disabled state such that the DTPU is inoperable for a digital transaction with a DTD.

An apparatus for a Digital Payment Device (DPD) operable for a digital transaction with a Digital Transaction Device (DTD), the apparatus being operable to provide transaction application identifier information for communication from the DPD to the DTD in a digital transaction, the apparatus including: an application selection module; on the DPD, a Digital Transaction Processing Unit (DTPU) operable to host one or more Personalized Digital Transaction Packages (PDTPs), each PDTP associated with at least one transaction application having a transaction application identifier; the DPD being operable to select at least one hosted PDTP to be operable for a digital transaction with the DTD; wherein the apparatus is operable to receive one or more commands to cause the application selection module to be set with a transaction application identifier for each transaction application associated with the selected at least one PDTP, such that the application selection module is operable to include, in the transaction application identifier information, the transaction application identifier for each transaction application associated with the selected at least one PDTP.