Integration with the Native OTP Assist mobile SDK in 4 steps:

1. Include the SDK in your application.

2. Set up the payment hash and postdata

3. Initiate the payment.

4. Verify the transaction.

Watch the complete integration video of PayU OTP Assist.

Include the SDK in your app build.gradle

implementation 'in.payu:native-otp-assist:1.2.0' 

Compatibility

​

Generate Payment Hash

Refer this document: Generate Hash​

Payment Post Data

Initiate Payment

Initialize the Native OTP Assist SDK by providing the PayUOtpAssistConfig object having postdata and reference to the PayUOtpAssistCallback to listen to the SDK events.

PayUOtpAssistConfig payUOtpAssistConfig = PayUOtpAssistConfig();
payUOtpAssistConfig.setPostData("POST_DATA_FOR_TRANSACTION");
​
​
PayUOtpAssist.open(
    Context context, 
    PayUOtpAssistCallback payUOtpAssistCallback, 
    PayUOtpAssistConfig payUOtpAssistConfig)

val payUOtpAssistConfig = PayUOtpAssistConfig()
payUOtpAssistConfig.postData = "POST_DATA_FOR_TRANSACTION"
PayUOtpAssist.open(
    context: Context, 
    payUOtpAssistCallback: PayUOtpAssistCallback,  
    payUOtpAssistConfig: PayUOtpAssistConfig) 

Make sure to add internet permission in your manifest file.

​
<uses-permission android:name="android.permission.INTERNET" />

We fetch the OTP via RECEIVE_SMS if RECEIVE_SMS permission granted, otherwise, fetch the OTP using Google Consent API. To understand the flow, refer to this page.

Callbacks

List of the callback function provided by PayUOtpAssistCallback class:

1. fun onPaymentSuccess(merchantResponse: String?, payUResponse: String?)- Called when payment succeeds. merchantResponse:

2. fun onPaymentFailure(merchantResponse: String?, payUResponse: String?)- Called when payment fails.

3. fun onError(errorCode: String?, errorMessage: String?)- Called when we got some error where,

   • errorCode : Error Code

   • errorMessage : Error Description

4. fun shouldHandleFallback(payUAcsRequest: PayUAcsRequest) : Boolean - It's an optional callback, override when you want to handle the Bank page redirection flow. You just need to change the return value to false. You can also open CustomeBrowser in fallback scenarios. Below is the code snippet to open the CustomBrowser.

 boolean shouldHandleFallback(PayUAcsRequest payUAcsRequest){
 
 CustomBrowserConfig customBrowserConfig = new CustomBrowserConfig(merchantKey, txnId);
   
  //Set the issuerUrl and issuerPostData to open in WebView for otp assist redirection to bank page
  if (payUAcsRequest.getIssuerUrl()!=null && payUAcsRequest.getIssuerPostData()!=null) {
    customBrowserConfig.setPostURL(payUAcsRequest.getIssuerUrl());
    customBrowserConfig.setPayuPostData(payUAcsRequest.getIssuerPostData())
​
}else if (payUAcsRequest.getAcsTemplate()!=null){
    customBrowserConfig.setHtmlData(payUAcsRequest.getAcsTemplate());
}else {
    //Set the first url to open in WebView
    customBrowserConfig.setPostURL(url);
    customBrowserConfig.setPayuPostData(payuConfig.getData);
}
return false;
}
​

fun shouldHandleFallback(payUAcsRequest: PayUAcsRequest) : Boolean {
​
val customBrowserConfig = CustomBrowserConfig(merchantKey, txnId)
   
  //Set the issuerUrl and issuerPostData to open in WebView for otp assist redirection to bank page
  if (!payUAcsRequest?.issuerUrl.isNullOrEmpty() && !payUAcsRequest?.issuerPostData.isNullOrEmpty()) {
    customBrowserConfig.postURL = payUAcsRequest?.issuerUrl
    customBrowserConfig.payuPostData = payUAcsRequest?.issuerPostData
​
}else if (!payUAcsRequest?.acsTemplate.isNullOrEmpty()){
    customBrowserConfig.htmlData = payUAcsRequest?.acsTemplate
}else {
    //Set the first url to open in WebView
    customBrowserConfig.postURL = url
    customBrowserConfig.payuPostData = payuConfig.data
}
return false
}

You will get PayUAcsRequest on shouldHandleFallback() callback. whether you will get issuerUrl and issuerPostData or acsTemplate on PayUAcsRequest acsTemplate is the Html string that you need to load to the Webview.

Error codes and their description.

   - ErrorCode: Description
​
   - 1001     : No Internet
       
   - 1002     : Network timeout, please verify with your server.
   
   - 1003     : Gateway timeout, please verify with your server.
   
   - 1004     : User cancelled it, please verify with your server.
      
   - 1005     : Something went wrong , please verify with your server.
   
   - 1006     : Bank page timed out, please verify with your server.

Verify the transaction

Implementation of PayU verify API

Since you already have the txnID (Order ID generated at your end) value for such cases, you simply need to execute the verify_payment API with the necessary input parameters.

The output would return you the transaction status in "status" key and various other parameters also.

Url: https://info.payu.in/merchant/postservice.php?form=2

​

curl --location --request POST '{{Url}}' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'key={merchantKey}' \
--data-urlencode 'command=verify_payment' \
--data-urlencode 'hash=c6febddfaaf6986dd8bd982d3769f856ab149e4de92dbad995c8df808ffcfbcb2c227a3fae38b69eb39ad7b6ce4e06e6b12289f70cc500cea5a2cda449c7dcba' \
--data-urlencode 'var1=Txn1234'

var1:

​