Abstract: Systems and methods for point-to-point encryption compliance are disclosed. In one embodiment, in a point of interaction device comprising at least one computer processor, a method for point-to-point encryption compliance may include: (1) receiving card data from a card reading device; (2) determining an error with the card data; (3) generating substitute data by replacing at least a portion of the card data with substitute data; and (4) communicating the substitute data to a payment server. The card data may be received from a magnetic stripe reader, from an EMV card reader, or from a contactless card reader. The error may include comprises the card data not being compliant with ISO-7813.

Abstract: Systems and methods for point-to-point encryption compliance are disclosed. In one embodiment, in a point of interaction device comprising at least one computer processor, a method for point-to-point encryption compliance may include: (1) receiving card data from a card reading device; (2) determining an error with the card data; (3) generating substitute data by replacing at least a portion of the card data with substitute data; and (4) communicating the substitute data to a payment server. The card data may be received from a magnetic stripe reader, from an EMV card reader, or from a contactless card reader. The error may include comprises the card data not being compliant with ISO-7813.

Abstract: An apparatus, method and program product for enabling biometric authentication that includes receiving a biometric submission (82) at a biometric device (60), and in response to an authentication of the submission (92), providing a cryptographic credential (68) from a computer (15, 30) to the biometric device (60) for use in a subsequent cryptographic purpose (100). In this manner, the biometric device (60) may subsequently mimic properties of a smart card.

Abstract: An apparatus, method and program product for enabling token authentication by generating a secret key using manufacturer controlled information (57) present on a token (34). A computer (30) typically reads the manufacturer controlled information and applies an cryptographic algorithm (41) to determine the secret key (47). The secret key (47) may comprise or be used to generate a one-time password (42) for use in authenticating the token (34). Typical manufacturer controlled information (57) present on the token (34) includes static, non-writeable/erasable information, such as a serial number (56) or manufacturer ID (54). Where desired, the token authentication is accomplished in the absence of memory or processors on the token that are dedicated to the authentication process, itself. This absence reduces token hardware requirements and associated expenses. The dynamic generation of the cryptographic key (47) also reduces risks conventionally associated with duplicating static keys stored within token memory.

Abstract: A signing interface is disclosed for facilitating digital signing of electronic messages by a buyer or other subscribing party in an e-commerce or other context. The signing interface provides a mechanism by which a seller's Web applications may invoke a buyer's smartcard subsystem or other signing module to execute a digital signature. The signing interface preferably comprises a signing interface library and a signing plug-in resident on the buyer's computer. The signing interface library is preferably implemented as a Java package and associated libraries that are installed locally on the buyer's computer and made accessible to signed Java applets provided by the seller's Web server. The signing plug-in is preferably implemented as a plug-in, ActiveX control, or similar code that is installed locally on the buyer's computer and made accessible through the buyer's Web browser using an embedded browser object on a seller's Web page.

Abstract: A signing interface is disclosed for facilitating digital signing of electronic messages by a buyer or other subscribing party in an e-commerce or other context. The signing interface provides a mechanism by which a seller's Web applications may invoke a buyer's smartcard subsystem or other signing module to execute a digital signature. The signing interface preferably comprises a signing interface library and a signing plug-in resident on the buyer's computer. The signing interface library is preferably implemented as a Java package and associated libraries that are installed locally on the buyer's computer and made accessible to signed Java applets provided by the seller's Web server. The signing plug-in is preferably implemented as a plug-in, ActiveX control, or similar code that is installed locally on the buyer's computer and made accessible through the buyer's Web browser using an embedded browser object on a seller's Web page.