Debit Card EMI - Native OTP Flow

The steps involved in debit card integration with native OTP flow:

Check Pre-EMI Eligibility
Initiate the payment request
Submit the 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 transaction information to PayU through a server-to-server curl request to initiate the transaction. As a result of this API call, the customer will receive the OTP. For more information, refer to Collect Payment API - Server-to-Server.

Parameter	Description	Example
s2s_device_info `mandatory`	`String` This parameter must have the customer agent’s device. Note: This information is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information.	Mozilla
s2s_client_ip `mandatory`	`String` This parameter must have the source IP of the customer. Note: This information is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information.	10.11.101.11'
txn_s2s_flow `mandatory`	`String` This parameter must be passed with the value as 4.	4

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.