Abstract: Systems, methods, and computer program products for data security store, in memory, a plurality of ciphers in association with a plurality of public keys, the plurality of ciphers including a plurality of secret keys encrypted with a key encryption key, and the plurality of secret keys corresponding to the plurality of public keys; receive, a data chunk for encryption; generate, a data encryption key based on a hash function, a public key of the plurality of public keys, and a random number; encrypt, the data chunk with the data encryption key to generate an encrypted data chunk; generate, a header including a cipher of the plurality of ciphers corresponding to the public key of the plurality of public keys and key encapsulation data; and store, in a database, a cipher text including the header and the encrypted data chunk.

Abstract: Techniques are provided for fallback authorization routing. A merchant processor may receive authorization requests from one or more merchant systems. These authorization requests may be to authorize a transaction. The merchant processor may transmit these authorization requests over a first communication channel to an acquirer processor, which may then forward the requests to a payment network. If the merchant processor determines that the acquirer processor is not receiving the authorization requests, or is otherwise unavailable, the merchant processor may, as a fallback, transmit the authorization requests directly to the payment network through a second communication channel, thereby bypassing the acquirer processor. When the merchant processor receives some indication that the acquirer processor is available to process authorization requests, new authorization requests can be transmitted to the acquirer processor via the first communication channel.

Abstract: Techniques are provided for intelligent routing to a node in a network, such as a transport computer. A gateway server may receive authorization requests from a resource provider computer. There may be multiple potential transport computers to which to potentially route the authorization requests, depending on relationships established between the parties. A routing decision may be made automatically based on real-time network measurements and/or static rules. Real-time network measurements may be obtained by monitoring transport computers for failures, delays, or other undesirable activity. The routing decisions may further be based on expected volumes (e.g., based on analysis of historical spikes in volume). The routing decisions may further be based on user-configured rules and preferences, received via a routing administration interface.

Abstract: Systems, methods, and computer program products for data security store, in memory, a plurality of ciphers in association with a plurality of public keys, the plurality of ciphers including a plurality of secret keys encrypted with a key encryption key, and the plurality of secret keys corresponding to the plurality of public keys; receive, a data chunk for encryption; generate, a data encryption key based on a hash function, a public key of the plurality of public keys, and a random number; encrypt, the data chunk with the data encryption key to generate an encrypted data chunk; generate, a header including a cipher of the plurality of ciphers corresponding to the public key of the plurality of public keys and key encapsulation data; and store, in a database, a cipher text including the header and the encrypted data chunk.

Abstract: Systems, methods, and computer program products for data security store, in memory, a plurality of ciphers in association with a plurality of public keys, the plurality of ciphers including a plurality of secret keys encrypted with a key encryption key, and the plurality of secret keys corresponding to the plurality of public keys; receive, a data chunk for encryption; generate, a data encryption key based on a hash function, a public key of the plurality of public keys, and a random number; encrypt, the data chunk with the data encryption key to generate an encrypted data chunk; generate, a header including a cipher of the plurality of ciphers corresponding to the public key of the plurality of public keys and key encapsulation data; and store, in a database, a cipher text including the header and the encrypted data chunk.

Abstract: Systems, methods, and computer program products for data security store, in memory, a plurality of ciphers in association with a plurality of public keys, the plurality of ciphers including a plurality of secret keys encrypted with a key encryption key, and the plurality of secret keys corresponding to the plurality of public keys; receive, a data chunk for encryption; generate, a data encryption key based on a hash function, a public key of the plurality of public keys, and a random number; encrypt, the data chunk with the data encryption key to generate an encrypted data chunk; generate, a header including a cipher of the plurality of ciphers corresponding to the public key of the plurality of public keys and key encapsulation data; and store, in a database, a cipher text including the header and the encrypted data chunk.

Abstract: Techniques are provided for intelligent routing to a node in a network, such as a transport computer. A gateway server may receive authorization requests from a resource provider computer. There may be multiple potential transport computers to which to potentially route the authorization requests, depending on relationships established between the parties. A routing decision may be made automatically based on real-time network measurements and/or static rules. Real-time network measurements may be obtained by monitoring transport computers for failures, delays, or other undesirable activity. The routing decisions may further be based on expected volumes (e.g., based on analysis of historical spikes in volume). The routing decisions may further be based on user-configured rules and preferences, received via a routing administration interface.

Abstract: Techniques are provided for intelligent routing to a node in a network, such as a transport computer. A gateway server may receive authorization requests from a resource provider computer. There may be multiple potential transport computers to which to potentially route the authorization requests, depending on relationships established between the parties. A routing decision may be made automatically based on real-time network measurements and/or static rules. Real-time network measurements may be obtained by monitoring transport computers for failures, delays, or other undesirable activity. The routing decisions may further be based on expected volumes (e.g., based on analysis of historical spikes in volume). The routing decisions may further be based on user-configured rules and preferences, received via a routing administration interface.

Abstract: Techniques are provided for fallback authorization routing. A merchant processor may receive authorization requests from one or more merchant systems. These authorization requests may be to authorize a transaction. The merchant processor may transmit these authorization requests over a first communication channel to an acquirer processor, which may then forward the requests to a payment network. If the merchant processor determines that the acquirer processor is not receiving the authorization requests, or is otherwise unavailable, the merchant processor may, as a fallback, transmit the authorization requests directly to the payment network through a second communication channel, thereby bypassing the acquirer processor. When the merchant processor receives some indication that the acquirer processor is available to process authorization requests, new authorization requests can be transmitted to the acquirer processor via the first communication channel.

Abstract: A system and method for transaction processing with conditional authorization are disclosed. The method includes receiving an authorization request message from a resource provider and sending the authorization request message to an authorizing entity. When an error response is received from the authorizing entity, the method includes determining a conditional authorization response and sending the conditional authorization response to the resource provider. Then a final authorization response is sent to the resource provider.

Abstract: Techniques are provided for intelligent routing to a node in a network, such as a transport computer. A gateway server may receive authorization requests from a resource provider computer. There may be multiple potential transport computers to which to potentially route the authorization requests, depending on relationships established between the parties. A routing decision may be made automatically based on real-time network measurements and/or static rules. Real-time network measurements may be obtained by monitoring transport computers for failures, delays, or other undesirable activity. The routing decisions may further be based on expected volumes (e.g., based on analysis of historical spikes in volume). The routing decisions may further be based on user-configured rules and preferences, received via a routing administration interface.

Abstract: Techniques are provided for fallback authorization routing. A merchant processor may receive authorization requests from one or more merchant systems. These authorization requests may be to authorize a transaction. The merchant processor may transmit these authorization requests over a first communication channel to an acquirer processor, which may then forward the requests to a payment network. If the merchant processor determines that the acquirer processor is not receiving the authorization requests, or is otherwise unavailable, the merchant processor may, as a fallback, transmit the authorization requests directly to the payment network through a second communication channel, thereby bypassing the acquirer processor. When the merchant processor receives some indication that the acquirer processor is available to process authorization requests, new authorization requests can be transmitted to the acquirer processor via the first communication channel.

Abstract: Provided are computer-implemented methods for guaranteeing a payment authorization response. Computer-implemented methods may include determining that a payment authorization response message for a payment transaction was not received from a transaction service provider system within a predetermined period of time after a payment authorization request message for the payment transaction was transmitted to the transaction service provider system; generating a supplemental payment authorization request message for the payment transaction based on the payment authorization request message; determining that the payment transaction is authorized based on a quantitative risk score associated with the supplemental payment authorization request message and an insurer rate associated with the supplemental payment authorization request message; and transmitting a supplemental payment authorization response message to a merchant system based on determining that the payment transaction is authorized.

Abstract: Provided are computer-implemented methods for guaranteeing a payment authorization response. Computer-implemented methods may include determining that a payment authorization response message for a payment transaction was not received from a transaction service provider system within a predetermined period of time after a payment authorization request message for the payment transaction was transmitted to the transaction service provider system; generating a supplemental payment authorization request message for the payment transaction based on the payment authorization request message; determining that the payment transaction is authorized based on a quantitative risk score associated with the supplemental payment authorization request message and an insurer rate associated with the supplemental payment authorization request message; and transmitting a supplemental payment authorization response message to a merchant system based on determining that the payment transaction is authorized.

Abstract: Embodiments of the invention are directed to techniques for redirecting data streams from a production environment to validate non-production software code. In some embodiments, a front-end computer executing a first version of software can receive a request message from a requesting computer, generate a request payload using the request message, transmit the request payload to a processor computer, receive a response payload from the processor computer, generate a reply message using the response payload, and provide, to a validation computer that is executing a second version of the software, the request message, the request payload, and the response payload. The validation computer can generate a modified request payload using the request message and a modified reply message using the response payload. To detect potential errors in the second version, the modified request payload is compared with the request payload and the modified reply message is compare with the reply message.

Abstract: Techniques are provided for fallback authorization routing. A merchant processor may receive authorization requests from one or more merchant systems. These authorization requests may be to authorize a transaction. The merchant processor may transmit these authorization requests over a first communication channel to an acquirer processor, which may then forward the requests to a payment network. If the merchant processor determines that the acquirer processor is not receiving the authorization requests, or is otherwise unavailable, the merchant processor may, as a fallback, transmit the authorization requests directly to the payment network through a second communication channel, thereby bypassing the acquirer processor. When the merchant processor receives some indication that the acquirer processor is available to process authorization requests, new authorization requests can be transmitted to the acquirer processor via the first communication channel.

Abstract: Embodiments of the invention are directed to techniques for redirecting data streams from a production environment to validate non-production software code. In some embodiments, a front-end computer executing a first version of software can receive a request message from a requesting computer, generate a request payload using the request message, transmit the request payload to a processor computer, receive a response payload from the processor computer, generate a reply message using the response payload, and provide, to a validation computer that is executing a second version of the software, the request message, the request payload, and the response payload. The validation computer can generate a modified request payload using the request message and a modified reply message using the response payload. To detect potential errors in the second version, the modified request payload is compared with the request payload and the modified reply message is compare with the reply message.

Abstract: Embodiments of the invention are directed to techniques for redirecting data streams from a production environment to validate non-production software code. In some embodiments, a front-end computer executing a first version of software can receive a request message from a requesting computer, generate a request payload using the request message, transmit the request payload to a processor computer, receive a response payload from the processor computer, generate a reply message using the response payload, and provide, to a validation computer that is executing a second version of the software, the request message, the request payload, and the response payload. The validation computer can generate a modified request payload using the request message and a modified reply message using the response payload. To detect potential errors in the second version, the modified request payload is compared with the request payload and the modified reply message is compare with the reply message.

Abstract: A new approach is proposed that contemplates systems and methods to support a secure machine environment on a HSM adapter, which enables an end user of the HSM adapter to run its own security sensitive applications securely via a secure machine within the HSM adapter and to gain access to its security measures. During operation, the secure machine receives commands from an application running on a host outside of the HSM adapter and executes a security sensitive application within the secure machine environment. The secure machine is configured to process all sensitive information of the security sensitive application via one or more secure machine processes/threads, while the applications running on the host only deal with non-sensitive information. The secure machine then sends a response back to the application running on the host following execution of the security sensitive application within the secure machine environment.