Skip to main content

Advantages

Using the Native OTP feature, you can:
  • Increase success rates by up to 4%.
  • Reduce payment failures due to low internet speeds.
  • Avoid failures due to redirects to bank pages.
  • Offer a consistent experience on mobile and web checkout.

Prerequisites

Before implementing the Native OTP feature, check the following prerequisites:
  1. Log in to the Dashboard and generate the API Keys.
  2. Integrate with the Razorpay Android Custom SDK.

Integration Steps

1.1 Update Razorpay Android Custom SDK version. 1.2 Implement CardsFlowCallback interface in the getCardsFlow function. 1.3 Call razorpay.getCardOtpData(CardsFlowCallback) Function. 1.4 Handle Success and Error Events. 1.5 Store Field in Server. 1.6 Verify Payment Signature.

1.1 Update Razorpay Android Custom SDK version

Update the Android Custom SDK version. This feature is available from version 3.9.3 and above.

1.2 Implement CardsFlowCallback Interface in getCardsFlow Function

Implement the CardsFlowCallback interface in the getCardsFlow function in the payment activity. The SDK fires the isNativeOtpEnabled function and determines whether the native OTP flow is enabled for the BIN.

Sample Code

Java

1.3 Call razorpay.getCardOtpData(CardsFlowCallback) Function

If Native OTP is enabled for BIN, you should call the razorpay.getCardOtpData(CardsFlowCallback) function. The SDK then fires the otpGenerateResponse(boolean otpGenerated) function and confirms if the OTP was successfully sent to the customer. Based on this information, you can display the generated OTP UI to the customer. After entering the OTP, the customer can either:
  • Submit OTP The customer needs to submit the OTP for authenticating the payment. The customer receives the OTP through your application frontend. For card payments, the customer receives the OTP via their preferred notification medium, SMS or email.
Handy TipsDo not perform any validation on the length of the OTP since this can vary across banks. However, the OTP should not be blank.
  • Request for OTP to be resent There could be situations when customers have to re-enter the OTP sent to them. The bank determines the number of retries that the user is allowed.
  • Cancel OTP Cancel the payment by cancelling the OTP.

Sample Code

Java

1.4 Handle Success and Error Events

You must handle the payment success and error events as shown in the code sample below:
Java
Handy TipsTo reuse the Razorpay Checkout web integration inside a web view on Android or iOS, pass a callback_url along with other checkout options to process the desired payment.

Use PaymentResultWithDataListener

You have the option to implement PaymentResultListener or PaymentResultWithDataListener to receive callbacks for the payment result.
  • PaymentResultListener provides only payment_id as the payment result.
  • PaymentResultWithDataListener provides additional payment data such as email and contact of the customer, along with the order_id, payment_id, signature and more.
Java

1.5 Store Fields in Your Server

A successful payment returns the following fields to the Checkout form.

Success Callback

  • You need to store these fields in your server.
  • You can confirm the authenticity of these details by verifying the signature in the next step.
Success Callback
razorpay_payment_id : string Unique identifier for the payment returned by Checkout only for successful payments. razorpay_order_id : string Unique identifier for the order returned by Checkout. razorpay_signature : string Signature returned by the Checkout. This is used to verify the payment.

1.6 Verify Payment Signature

This is a mandatory step to confirm the authenticity of the details returned to the Checkout form for successful payments.

To verify the razorpay_signature returned to you by the Checkout form:

  1. Create a signature in your server using the following attributes:
    • order_id: Retrieve the order_id from your server. Do not use the razorpay_order_id returned by Checkout.
    • razorpay_payment_id: Returned by Checkout.
    • key_secret: Available in your server. The key_secret that was generated from the Dashboard.
  2. Use the SHA256 algorithm, the razorpay_payment_id and the order_id to construct a HMAC hex digest as shown below:
    HMAC Hex Digest
  3. If the signature you generate on your server matches the razorpay_signature returned to you by the Checkout form, the payment received is from an authentic source.

Generate Signature on Your Server

Given below is the sample code for payment signature verification:
Java

Post Signature Verification

After you have completed the integration, you can set up webhooks, make test payments, replace the test key with the live key and integrate with other APIs.

Next Steps

Step 2: Test Integration