# RuPay Payer Authentication
source: https://developer.mastercard.com/mastercard-gateway/documentation/security-and-fraud/authentication/rupay-payer-auth/index.md

RuPay payer authentication allows you to authenticate RuPay cardholders before initiating a RuPay payment. The payer will be redirected through the RuPay PaySecure network to a site hosted by the issuer to enter a One-Time Password (OTP). You receive the authentication result that enables you to decide whether you want to proceed with the payment or not.
Alert: RuPay payment authentication is only available in India.

## Prerequisites {#prerequisites}

Your National Payments Corporation of India (NPCI) merchant-acquirer link on the gateway must be enabled to process RuPay authentication.

## Integrating to use RuPay payer authentication {#integrating-to-use-rupay-payer-authentication}

The gateway supports the following integration options for RuPay authentication.

* [Authentication API](https://developer.mastercard.com/mastercard-gateway/documentation/security-and-fraud/authentication/rupay-payer-auth/rupay-auth-auth-api/index.md): This is a server-side integration option that gives you total control over your integration but requires the highest integration effort. Use this option if you are required to customize API interactions between the payer's browser and the gateway. Perform operations needed for managing the integration flows directly from your merchant server to the gateway server.

## FAQs {#faqs}

If you wish to retrieve the authentication results at any stage, use the Retrieve Transaction operation. Fields that are only used during the authentication. For example, `authentication.redirectHtml`, are not persisted in the gateway hence not returned.
**Retrieve Transaction API Reference** [\[REST\]](https://developer.mastercard.com/mastercard-gateway/documentation/api-reference/v100/rest/api-ops/index.md#transaction.md) [\[NVP\]](https://developer.mastercard.com/mastercard-gateway/documentation/api-reference/v100/nvp/api-ops/index.md#transaction.md)
The gateway provides the authentication status in the `transaction.authenticationStatus` field. This field may return one of the following values depending on the authentication stage:

* **AUTHENTICATION_ATTEMPTED**: Payer authentication was attempted, and a proof of authentication attempt was obtained.
* **AUTHENTICATION_AVAILABLE**: Payer authentication is available for the payment method provided.
* **AUTHENTICATION_FAILED**: The payer was not authenticated. Do not proceed with this transaction.
* **AUTHENTICATION_NOT_SUPPORTED**: The requested authentication method is not supported for this payment method.
* **AUTHENTICATION_PENDING**: Payer authentication is pending completion of a challenge process.
* **AUTHENTICATION_REJECTED**: The issuer rejected the authentication request and requested that you do not attempt authorization of a payment.
* **AUTHENTICATION_REQUIRED**: Payer authentication is required for this payment, but payment was not provided.
* **AUTHENTICATION_SUCCESSFUL**: The payer was successfully authenticated.
* **AUTHENTICATION_UNAVAILABLE**: The payer could not be authenticated due to a technical or other issue.
You can view authentication details for both individual RuPay authentications and authentications that proceeded with the payment in Merchant Administration. Search for the order or transaction in the search page and view the authentication details.