Cardless EMI - Native OTP Flow
The steps involved in cardless EMI with Native OTP:
Step 1: Check pre-EMI eligibility
Before initiating a payment request for a customer, it is necessary to check their eligibility using the Get Checkout Details API. For more information, refer to Get Checkout Details API.
Step 2: Initiate the payment request
Send the following additional parameters to PayU through a server-to-server curl request to initiate the payment. As a result of this API call, the customer will receive the OTP. For sample request and response, refer to Collect Payment API - Server-to-Server.
Parameter | Description | Example |
---|---|---|
panNumbermandatory | String PAN number of the customer. | ABCDE1234A |
s2s_device_infomandatory | String This parameter must have the customer agentβs device. | Mozilla |
s2s_client_ipmandatory | String This parameter must have the source IP of the customer. | 10.11.101.11 |
txn_s2s_flowmandatory | StringString This parameter must be passed with the value as 4. | 4 |
Notes for panNumber:
- Only 4-digit number of the PAN: Pass the 4-digit numeral in a sequential order as in the PAN.
- This parameter is mandatory for ICICI Bank and HDFC Bank Cardless EMI. Not mandatory for other banks
- The data validation performed is either the whole PAN card number or 4-dig-t number of the PAN.
- Whole PAN card Number: For validating the whole PAN Card number:
- It should be ten characters long.
- The first five characters should be any upper case alphabets.
- The next four-characters should be any number from 0 to 9.
- The last(tenth) character should be any upper case alphabet. It should not contain any white spaces.
Step 3: Submit the OTP
Once your customer enters the OTP on the payment page (postUrl/acsTemplate), pass the OTP using the Submit OTP API. For more information, refer to Submit OTP API.
Resend OTP
If the customer enters the incorrect OTP or an expired OTP, use Resend OTP API to handle the Resend OTP request made by a customer.
Updated about 2 months ago