Abstract: Described are a system, method, and computer program product for processing a transaction as a push payment transaction. The method may include receiving, with a payment gateway processor, a transaction request from a merchant system. The transaction request may include transaction data associated with a payment device of a user, the payment device being associated with an issuer system. The method may also include generating, with the payment gateway processor, an authentication request based on the transaction data. The method may further include communicating, with the payment gateway processor, the authentication request to the issuer system. The method may further include, in response to the issuer system authenticating the authentication request, generating a push payment request including an account identifier associated with the merchant system, and communicating the push payment request to the issuer system.

Abstract: Methods for authenticating digital transactions include receiving a device registration request, a device attestation response including a first token, and a selection of an authentication mode from a device. In response to receiving the device registration request and determining that the selected authentication mode is a static personal identification number (PIN) authentication mode, a device registration response is provided to the device. A first payment transaction request and an enrolment request to authenticate a second payment transaction request using the static PIN authentication mode are subsequently received from the device. The device is communicated with to receive the static PIN from the device. The device is enrolled based on the static PIN. Systems and computer program products are also provided.

Abstract: Embodiments of the present disclosure relate to methods and systems for authenticating and authorizing mobile-One Time Password (m-OTP) based transactions. A cardholder (101) can generate the m-OTP in an issuer mobile application (301) and enter in a checkout page for completing the transaction. Once the m-OTP is entered, a merchant system (104) generates a transaction message comprising the m-OTP and a unique identifier indicating that the transaction message comprises the m-OTP. Is submitted to a directory server (106) which sends the transaction message to an issuer system (107) for authentication and authorization. The issuer system (107) generates a response message comprising a result of authentication and authorization of the transaction message. The directory server (106) routes the response message to the merchant system (104) via the acquirer system (105).

Abstract: In some embodiments, a computer-implemented method includes receiving, at an acquirer, a trust-verification-use-case-specific root certificate from a certificate authority of a payment processing network, the trust-verification-use-case-specific root certificate being associated with a trust verification use case; receiving an intermediate certificate from the certificate authority, the intermediate certificate being associated with the trust-verification-use-case-specific root certificate; generating, at the acquirer, a key pair for identity associated with an end-entity; signing the key pair for identity associated with the end-entity using the intermediate certificate; generating a digital certificate based upon the signing of the key pair for identity; generating a secure QR code utilizing the digital certificate, identify information associated with the end-entity, and an associated certificate chain; and providing the secure QR code to the end-entity for scanning by a user of a communication device to a

Abstract: Described are a system, method, and computer program product for processing a transaction as a push payment transaction. The method may include receiving, with a payment gateway processor, a transaction request from a merchant system. The transaction request may include transaction data associated with a payment device of a user, the payment device being associated with an issuer system. The method may also include generating, with the payment gateway processor, an authentication request based on the transaction data. The method may further include communicating, with the payment gateway processor, the authentication request to the issuer system. The method may further include, in response to the issuer system authenticating the authentication request, generating a push payment request including an account identifier associated with the merchant system, and communicating the push payment request to the issuer system.

Abstract: Described are a system, method, and computer program product for processing a transaction as a push payment transaction. The method may include receiving, with a payment gateway processor, a transaction request from a merchant system. The transaction request may include transaction data associated with a payment device of a user, the payment device being associated with an issuer system. The method may also include generating, with the payment gateway processor, an authentication request based on the transaction data. The method may further include communicating, with the payment gateway processor, the authentication request to the issuer system. The method may further include, in response to the issuer system authenticating the authentication request, generating a push payment request including an account identifier associated with the merchant system, and communicating the push payment request to the issuer system.

Abstract: Described are a system, method, and computer program product for processing a transaction as a push payment transaction. The method may include receiving, with a payment gateway processor, a transaction request from a merchant system. The transaction request may include transaction data associated with a payment device of a user, the payment device being associated with an issuer system. The method may also include generating, with the payment gateway processor, an authentication request based on the transaction data. The method may further include communicating, with the payment gateway processor, the authentication request to the issuer system. The method may further include, in response to the issuer system authenticating the authentication request, generating a push payment request including an account identifier associated with the merchant system, and communicating the push payment request to the issuer system.

Abstract: Embodiments of the present disclosure relate to methods and systems for authenticating and authorizing mobile-One Time Password (m-OTP) based transactions. A cardholder (101) can generate the m-OTP in an issuer mobile application (301) and enter in a checkout page for completing the transaction. Once the m-OTP is entered, a merchant system (104) generates a transaction message comprising the m-OTP and a unique identifier indicating that the transaction message comprises the m-OTP. Is submitted to a directory server (106) which sends the transaction message to an issuer system (107) for authentication and authorization. The issuer system (107) generates a response message comprising a result of authentication and authorization of the transaction message. The directory server (106) routes the response message to the merchant system (104) via the acquirer system (105).