Disclosed are a system and methods enabling updating of a card number of a payment card and thereby reissuing the payment card utilizing a reissue application associated with the payment card. The reissue application, when executed communicates with a service provider that manages the payment card. The payment card includes processing circuity and a rewriteable visual display. Using cryptographic techniques, the reissue application and payment card are authenticated to the service provider. Upon verification, an updated card number is obtained and provided via near-field communication to the payment card. In response to the update payment card number received from the reissue application, the rewriteable visual display on the payment card is updated with the updated card number. Other information may also be presented on the rewriteable visual display of the payment card based on user preferences.

Example embodiments of systems, methods, and computer-accessible mediums for transaction authorization are provided. An exemplary system can comprise a card including an input device and a display device in data communication with a server. The server can generate an authorization passcode upon an initiation of a transaction session, and the card can receive an entered passcode through the input device, display the entered passcode on the display device, and transmit the entered passcode to the server for comparison to the authorization passcode. Upon a determination that the entered passcode is a match for the authorization passcode, the server can transmit a match notification indicating the transaction session is valid, and upon a determination that the entered passcode is a mismatch for the authorization passcode, the server can transmit a mismatch notification terminating the transaction session.

Systems, methods, articles of manufacture for authentication of payment cards. A server may assign, in a database, an expected card identifier to a contactless card, the contactless card associated with an account. The server may receive, from a client device, a request comprising a uniform resource locator (URL), a parameter of the URL comprising a card identifier, wherein the URL is transmitted by the contactless card to the client device. The server may extract the card identifier from the URL and compare the extracted card identifier to the expected card identifier in the database. The server may determine, based on the comparison, that the extracted card identifier matches the expected card identifier. The server may authenticate the request based on the extracted card identifier matching the expected card identifier, and transmit, to the client device, an indication specifying that the request was authenticated.

Example embodiments of systems and methods for data transmission between a contactless card, a client device, and one or more servers are provided. The memory of the contactless card may include one or more applets and a counter. The client device may be in data communication with the contactless card and one or more servers, and the one or more servers may include an expected counter value. The client device may be configured to read the counter from the contactless card and transmit it to the one or more servers. The one or more servers may compare the counter to the expected counter value for synchronization. The contactless card and the one or more servers may resynchronize the counter, via one or more processes, based on one or more reads of the one or more applets. The one or more servers may authenticate the contactless card based on the resynchronization.

Example embodiments of systems and methods for data transmission between a contactless card, a client device, and one or more servers are provided. The memory of the contactless card may include one or more applets and a counter. The client device may be in data communication with the contactless card and one or more servers, and the one or more servers may include an expected counter value. The client device may be configured to read the counter from the contactless card and transmit it to the one or more servers. The one or more servers may compare the counter to the expected counter value for synchronization. The contactless card and the one or more servers may resynchronize the counter, via one or more processes, based on one or more reads of the one or more applets. The one or more servers may authenticate the contactless card based on the resynchronization.

Disclosed are a system and methods enabling updating of a card number of a payment card and thereby reissuing the payment card utilizing a reissue application associated with the payment card. The reissue application, when executed communicates with a service provider that manages the payment card. The payment card includes processing circuity and a rewriteable visual display. Using cryptographic techniques, the reissue application and payment card are authenticated to the service provider. Upon verification, an updated card number is obtained and provided via near-field communication to the payment card. In response to the update payment card number received from the reissue application, the rewriteable visual display on the payment card is updated with the updated card number. Other information may also be presented on the rewriteable visual display of the payment card based on user preferences.

Systems and methods for conducting transactions using cards with keys are disclosed. In one embodiment, a method may include: receiving, at a backend for a financial institution in a transaction, a unique identifier for a card, a key read from the card by a card reading device, and additional data received by the card reading device, the card reading device associated with a merchant; retrieving, by the backend, stored additional data associated with the unique identifier; retrieving, by the backend, a stored key associated with the unique identifier in response to the received additional data matching the stored additional data; confirming, by the backend, that the received key and the stored key are related; retrieving, by the backend, a payment mechanism for the transaction; conducting, by the backend, the transaction with the retrieved payment mechanism; and settling, by the backend, the transaction with the merchant.

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.

A Digital Transaction Processing Unit (DTPU) including one or more transaction applications operable for a digital transaction with a Digital Transaction Device (DTD), each of the one or more transaction applications being associated with identifying information, the identifying information being capable of identifying a subset of at least one transaction application within the one or more transaction applications, wherein the DTPU is operable, when conducting a transaction with the DTD, to communicate to the DTD the identifying information associated with one of the one or more transaction applications involved in the transaction.