Abstract: A transaction is pre-staged by providing transaction preferences, such as a financial instrument, a transaction type, and a transaction amount, to a user device. The user device captures a visual code at a terminal, such as an ATM. The visual code includes terminal attributes, including a signed hash and call-back URI. The user device authenticates the visual code using the signed hash and requests the transaction through the issuer server. The issuer server creates and sends the card data to the call-back URI. The terminal uses the card data to create a transaction request it routes to through its acquirer server.

Abstract: Embodiments of the present invention provide systems and techniques for changing cryptographic keys in high-frequency transaction environments to mitigate service disruptions or loss of transactions associated with key maintenance. In various embodiments, a server device can employ a working key encrypted with a first master key to decrypt messages being communicated from a client device, whereby each message is encrypted with a first cryptogram that was generated based on the working key encrypted with the first master key. While the working key encrypted with the first master key is being employed, the server device can generate a notification including a second cryptogram generated based on the working key encrypted with a second master key for transmission to the client device. The transmitted notification can cause the client device to encrypt the messages being communicated with the second cryptogram.

Abstract: A transaction is pre-staged by providing transaction preferences, such as a financial instrument, a transaction type, and a transaction amount, to a user device. The user device captures a visual code at a terminal, such as an ATM. The visual code includes terminal attributes, including a signed hash and call-back URI. The user device authenticates the visual code using the signed hash and requests the transaction through the issuer server. The issuer server creates and sends the card data to the call-back URI. The terminal uses the card data to create a transaction request it routes to through its acquirer server.

Abstract: A transaction is pre-staged by providing transaction preferences, such as a financial instrument, a transaction type, and a transaction amount, to a user device. The user device captures a visual code at a terminal, such as an ATM. The visual code includes terminal attributes, including a signed hash and call-back URI. The user device authenticates the visual code using the signed hash and requests the transaction through the issuer server. The issuer server creates and sends the card data to the call-back URI. The terminal uses the card data to create a transaction request it routes to through its acquirer server.

Abstract: Embodiments of the present invention provide systems and techniques for changing cryptographic keys in high-frequency transaction environments to mitigate service disruptions or loss of transactions associated with key maintenance. In various embodiments, a server device can employ a working key encrypted with a first master key to decrypt messages being communicated from a client device, whereby each message is encrypted with a first cryptogram that was generated based on the working key encrypted with the first master key. While the working key encrypted with the first master key is being employed, the server device can generate a notification including a second cryptogram generated based on the working key encrypted with a second master key for transmission to the client device. The transmitted notification can cause the client device to encrypt the messages being communicated with the second cryptogram.

Abstract: Embodiments of the present invention provide systems and techniques for changing cryptographic keys in high-frequency transaction environments to mitigate service disruptions or loss of transactions associated with key maintenance. In various embodiments, a server device can employ a working key encrypted with a first master key to decrypt messages being communicated from a client device, whereby each message is encrypted with a first cryptogram that was generated based on the working key encrypted with the first master key. While the working key encrypted with the first master key is being employed, the server device can generate a notification including a second cryptogram generated based on the working key encrypted with a second master key for transmission to the client device. The transmitted notification can cause the client device to encrypt the messages being communicated with the second cryptogram.

Abstract: A transaction is pre-staged by providing transaction preferences, such as a financial instrument, a transaction type, and a transaction amount, to a user device. The user device captures a visual code at a terminal, such as an ATM. The visual code includes terminal attributes, including a signed hash and call-back URI. The user device authenticates the visual code using the signed hash and requests the transaction through the issuer server. The issuer server creates and sends the card data to the call-back URI. The terminal uses the card data to create a transaction request it routes to through its acquirer server.

Abstract: Embodiments of the present invention provide systems and techniques for changing cryptographic keys in high-frequency transaction environments to mitigate service disruptions or loss of transactions associated with key maintenance. In various embodiments, a server device can employ a working key encrypted with a first master key to decrypt messages being communicated from a client device, whereby each message is encrypted with a first cryptogram that was generated based on the working key encrypted with the first master key. While the working key encrypted with the first master key is being employed, the server device can generate a notification including a second cryptogram generated based on the working key encrypted with a second master key for transmission to the client device. The transmitted notification can cause the client device to encrypt the messages being communicated with the second cryptogram.

Abstract: Various embodiments automate an authorization for a partial amount in a pre-authorized transaction via a unique data element that uniquely identifies the pre-authorization and does not require multiple traversals over the network of a CAV (e.g., a four-digit pin). In this way, one type of network traversal for pre-authorization (e.g., of a total amount) is utilized via communicating an encrypted CAV, and another type of automated traversal is utilized to complete subsequent corresponding transaction requests (e.g., for partial amounts) via the unique data element (without the CAV). Thus, each portion of a pre-authorized transaction may be transferred individually without repetitively verifying the CAV. In other words, the CAV may be authenticated during the authorization/pre-authorization phase. Thereafter, the CAV need not traverse the network again.

Abstract: A system and method for processing payment transactions via payment devices are provided. Issuer application selection criteria associated with a payment device, merchant application selection criteria associated with an acceptance device, and/or payment network card program file(s) may be evaluated to determine the payment application to be used for processing a payment transaction.

Abstract: A system and method for processing funds transfers that may utilize a dual-message transaction with separate authorization and settlement messages for (consumer authentication value) CAV-based transactions. Initial authorization messages may be communicated to authorize and guarantee funds to a payee for goods and/or services before they are rendered. Thereafter, the payee may initiate one or more settlement advice request messages associated with the authorization/pre-authorization, as goods and/or services are rendered without authorization of CAV.