API Overview

Recent Revisions to This Document

About This Guide

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Overview of RuPay Payer Authentication
- Authentication Modes

Redirection Mode Payer Authentication
- Check Enrollment Service
  - Check Enrollment Request
  - pa-rupay-int-redir-enroll-overview-resp
  - REST Example: Enrollment Service
- Authenticating Cards Using Redirection
  - HTML Frame Requirements
  - HTTP Post Form
  - PARes Message from the RuPay Card-Issuing Bank
- Authorization Service
  - REST Example: Authorization
- Validating Authentication
  - Validation Service Request
  - Pass or Fail Message Page
  - REST Example: Validate Authentication Service

Seamless Flow Payer Authentication
- Possible Authentication Results
- One-Time Password Generation
  - Required Fields for Generating a One-Time Password in RuPay
  - REST Example: One-Time Password Generation
  - REST Example: One-Time Password Generation (with Token)
- One-Time Password Resend
  - Required Field for Resending a One-Time Password in RuPay
  - Response Field for Checking Enrollment in Payer Authentication
  - REST Example: One-Time Password Resend
  - REST Example: One-Time Password Resend (with Token)
- One-Time Password Validation
  - Required Fields for Validating a One-Time Password in RuPay
  - Response Fields for Payer Authentication Validation in RuPay
  - Example: One-Time Password Validation (No Token)

Standing Instructions
- Standing Instruction Registration
  - Required Fields for Standing Instruction Registration
  - Optional Fields for Standing Instruction Registration
  - REST Example: Registering a Standing Instruction
  - REST Example: Registering a Standing Instruction (with Token)
- Standing Instruction Modification
  - Required Fields for Standing Instruction Modification
  - Optional Fields for Standing Instruction Modification
  - REST Example: Modifying a Standing Instruction
  - REST Example: Modifying a Standing Instruction (with Token)
- Standing Instruction Deregistration (Cancellation)
  - Required Fields for Deregistering a Standing Instruction
  - REST Example: Deregistering a Standing Instruction
  - REST Example: Deregistering a Standing Instruction (with Token)
- Completion of Standing Instructions
  - Required Fields for Standing Instruction Completion
  - REST Example: Completing a Standing Instruction
- Standing Instructions Intimation
  - Required Fields
  - REST Example: Intimating a Standing Instruction
- One-Time Password Generation
  - Required Fields for Generating a One-Time Password in RuPay
  - Optional Fields for Generating a One-Time Password
  - REST Example: One-Time Password Generation
  - REST Example: One-Time Password Generation (with Token)
- One-Time Password Resend
  - REST Example: One-Time Password Resend
  - REST Example: One-Time Password Resend (with Token)
- One-Time Password Validation
  - Required Fields for Validating a One-Time Password in RuPay
  - Response Fields for Payer Authentication Validation in RuPay
  - Example: One-Time Password Validation (No Token)
- Standing Instruction Authorization
  - Required Fields for SI Authorizations
  - Optional Fields for Standing Instruction Authorization
  - REST Example: Authorizing a Standing Instruction
  - REST Example: Authorization of a Standing Instruction Transaction (with Token)

On This Page

Required Fields for Validating a One-Time Password in RuPay

These fields are required for RuPay when validating the one-time password the customer sends:

consumerAuthenticationInformation.authenticationTransactionContext: This value must be the same value received in the Payer Authentication Enrollment response.
consumerAuthenticationInformation.authenticationTransactionId: The same value returned in the Payer Authentication Enrollment response must be used as the
consumerAuthenticationInformation.authenticationTransactionId
in the Payer Authentication Validate request.
consumerAuthenticationInformation.otpToken: Merchant must send the OTP entered by the cardholder as part of this request field in Payer Authentication Validate request.
deviceInformation.ipAddress: Merchant must pass the customer IP address as part of this field.

Back to top