Skip to main content

Prerequisites

  1. Integrate with the Razorpay Android Custom SDK.
  2. Contact our Integrations team and provide the following details to get allowlisted:
    • Mobile numbers of your internal users.
    • App id of your debug, staging and production apps.
  3. Contact our Integrations team to get the access to the Sample App Repository https://github.com/upi-turbo/android-turbo-sample-app. Once you have access, please read the readme section of the repository to learn how to locate the library files and integrate them into your project.
  4. Add the following lines to your Android project’s gradle.properties file:
    • android.enableJetifier=true
    • android.useAndroidX=true
  5. The minSDKversion for using Turbo UPI is currently 23 and cannot be over written.
Add the following dependencies:
  • In the root settings.gradle file, use:
Kotlin
  • In the library module’s build.gradle, use:
Kotlin
Watch Out!
  • Use the rzp_test_0wFRWIZnH65uny API key id for testing on the UAT environment and the Razorpay live keys on the prod testing.
  • Replace the placeholders (CUSTOMUIVERSION,CUSTOMUI_VERSION, TURBO_VERSION and $CHECKOUT_VERSION) with the latest versions provided by Razorpay’s team or similar to app/build.gradle file in the Sample app.

1. Integration Steps

1.1 Create a Session Token

To enhance security, you must create a session token via a server-to-server (S2S) call between your backend and Razorpay’s backend. This session token ensures secure communication between the Turbo SDK and Razorpay’s systems.

How to Create a Session Token

  1. Trigger the S2S API from your Backend. Use the following API to generate a session token: Environment based URLs:
    • UAT: https://api-web-turbo-upi.ext.dev.razorpay.in
    • Production: https://api.razorpay.com
    Authorization Header Creation: Base64.encode(${public_key}:${secret})
    Curl

Request Parameters

customer_reference mandatory : string A unique identifier for the customer provided by the business. The recommended value is mobile number. For example, 9000090000.

Response Parameters

token : string A session token to be used in subsequent session-protected APIs. expire_at : long Expiry time (in seconds) for the session token, used to optimise session handling and reduce unnecessary reinitialisations. error : object The request failure due to business or technical failure.

1.2 Initialise Turbo SDK

Initialise the TurboSessionDelegate object anonymously and pass it through the initialize method. The SDK will call fetchToken function whenever required to get new token. In the fetchToken function, retrieve a new token from your server section, check 1.1 Create a Session Token. Once available, pass it to the completion object.
Kotlin

1.3 Getting Linked UPI Accounts

After initialising the Turbo SDK, proceed to securely link UPI accounts and complete the payment flow.
  1. Get already linked accounts. If your customer has already linked accounts, use the following code to fetch them. If there are no linked UPI accounts, an empty list is returned.
Handy Tips
  • When the user arrives at your checkout screen, use the getLinkedUpiAccounts function to fetch the updated list of UPI accounts.
  • For enhanced user experience mobile number is required in getLinkedUpiAccounts function, otherwise feel free to use either mobile number or customer id.
    Kotlin
Watch Out!If the device binding is not completed and the getLinkedUpiAccounts is triggered, it will return an OnError with a DEVICE_BINDING_INCOMPLETE error code.

Request Parameters

customerMobile mandatory : string The customer’s mobile number. listener : object The listener to be sent should be of type UpiTurboResultListener.

Response Parameters

onSuccess : This function is triggered if the list is fetched successfully. accList can be empty to indicate that no accounts have been linked yet. onError : This function is triggered in case an error is thrown during the retrieval process, either by the Razorpay SDK or the Bank SDK.

1.4 New user onboarding / Linking additional accounts

Invoke the below function for these use cases:
  1. To initiate new onboarding, in case you get a DEVICE_BINDING_INCOMPLETE error in the above section,
  2. To link additional bank accounts for already onboarded users.
Handy Tips
A mobile number is required in the linkNewUpiAccount function for an enhanced user experience. Otherwise, feel free to use either your mobile number or customer id.
Kotlin
  1. Invoke the below function in your Activity’s onRequestPermissionsResult function.
    Kotlin
  2. Additionally razorpay.onBackPressed() has to be invoked when a user tries to exit the app or return to the previous page. The razorpay.upiTurbo.releaseActivityReference() function releases the allocated memory.
    Kotlin
  3. To process the payment, first create a payload, which will be a JSONObject as shown in the code below.
    Kotlin
  4. Pass the upiAccount and payload objects as shown in the code below.
    Kotlin
Handy Tips
In case of an error response, you will get a nested reason JSON object, which will contain the original error code and description from the bank/NPCI.

Non-Transactional Flow

You can directly interact with the exposed methods of the Turbo Framework to perform the non-transactional flows listed below.

Fetch Balance

Fetch the customer’s account balance. Call getBalance() and pass the UpiAccount instance you have received from Turbo SDK before.
Kotlin

Change UPI PIN

Provide the customer the ability to change their UPI PIN. Call changeUpiPin() and pass the upiAccount instance you have received from Turbo SDK before.
Kotlin

Reset UPI

Let your customers reset the PIN for their account. You will need to collect the below mentioned details for the account:
  • Bank accounts: last 6 digits, expiry month & year of the Debit Card.
  • Credit cards: last 6 digits, expiry month & year of the Credit Card.
Pass these details in the Card data class provided by Turbo SDK and the upiAccount object you received from Turbo SDK.
Kotlin
Let your customers delink, that is, remove a selected UPI account from your application.
Kotlin
Watch Out!The same mobile number and customer id combination must be consistently passed across all sessions when calling linkNewUpiAccount and getLinkedUpiAccounts for a given user.

Additional Features

  1. To get the device binding status, please use the method isDeviceOnboarded() which returns a boolean. It indicates whether the device binding, which is a prerequisite for adding UPI accounts, is done with the user’s mobile number.
    Kotlin
  2. Users can now link their credit cards alongside bank accounts during onboarding. You can seamlessly retrieve both credit and bank accounts for transactions, thereby simplifying payments, expanding options, and ensuring security.
  3. Changes have been made to the AccountBalance and UpiAccount models regarding credit card support on UPI.
  4. Charges will be levied for payments made using CC on UPI. Contact the support team for further information.
  5. Turbo SDK will auto-select the SIM card in few cases and the SELECT_SIM action will not be triggered in such cases:
    • Device has only one SIM card.
    • Device has multiple SIM cards and the mobile number provided by you matches the number on one of the SIM cards.

Action Parameter Values

Following are the constants passed in the action.code parameter in onResponse.

Name | Description | Next Function

ASK_FOR_PERMISSION | Runtime permissions have not been granted yet, or were revoked by the user later. | action.requestPermission()

SHOW_PERMISSION_ERROR | You can use this to show a dialogue directing customers to navigate and enable permissions from app settings. | NA (You should show Go To Settings UI to enable permissions for the customers)

SELECT_SIM | SIM details are fetched from the device to show the customer to begin the registration process. This will be skipped if the customer only has one SIM on the device. | action.selectedSim(sim)

SELECT_BANK | Object AllBanks returned by SDK for customer selection with: - popularBanks
  • allBanks | action.selectedBank(bank)

    SET_UPI_PIN | Triggered if the UPI Pin is not set for the selected bank account. | action.setUpiPin(Card)

    LOADER_DATA | Returns messages that can be used for the loader, informing the customer of the steps happening during the onboarding process. | NA

    STATUS | The onboarding process’s final status returns the onboarded UpiAccount or error after a bank account was selected or SET_UPI_PIN was triggered. | NA

Models Exposed from the SDKs

The SDKs given below provide access to exposed models for seamless integration.

BankAccount

Method | Return Type | Description

getAccountNumber() | String | Masked account number.

getBeneficiaryName() | String | Name of the account holder.

getBank() | String | The bank code.

state() | BankAccountState | The current state of account.

Bank

Method | Return Type | Description

getIfsc() | String | IFSC code of bank.

getName() | String | Name of bank.

getBankPlaceholderUrl() | String | Image URL for bank logo placeholder.

AccountBalance

Method | Return Type | Description

getBalance() | long | Balance amount in paise.

getCurrency() | String | Currency Type in INR.

getId() | String | Bank Account id.

getOutstanding() | Long | Outstanding balance for Credit accounts.

Error

Error | Description

getErrorCode() | Types of error codes - BAD_REQUEST_ERROR: Failure from client’s end (SDK).
  • GATEWAY_ERROR: Failure either from the NPCI or the Bank.
  • SERVER_ERROR: Failure at PSP.
    getErrorDescription() | Brief description of the error.

UpiAccount

Method | Return Type | Description

getAccountNumber() | String | Returns masked bank account number.

getType() | String | The account type. Possible values are bank_account and credit_card.

getIfsc() | String | Returns IFSC for Bank.

getBankName() | String | Returns name of bank.

getBankLogoUrl() | String | Returns URL to the logo of the PNG image.

getBankPlaceholderUrl() | String | Image URL for bank logo placeholder.

SIM

Method | Return Type | Description

getId() | String | SIM id used to target SIM card for binding.

getProvider() | String | Network provider name.

getSlotNumber() | Integer | SIM slot number. Possible values are 0 and 1.

getNumber() | String | Mobile number stored in SIM card.

Card

Method | Return Type | Description

getLastSixDigits() | String | Last six digits of the debit card number.

getExpiryYear() | String | Expiry year. Format: YY.

getExpiryMonth() | String | Expiry month.

AllBanks

Method | Return Type | Description

getPopularBanks() | List | Returns the list of the top 8 banks.

getAllBanks() | List | Returns a list of all banks.

UpiTurbo.LinkAction

Method | Return Type | Description

additionalDetails() | NA | Send additional required parameters.

requestPermissions() | NA | Request for required permissions and get SIM details.

selectedSim() | NA | Send selected SIM object to SDK.

selectedBank() | NA | Send selected bank object to SDK.

selectedBankAccount() | NA | Send selected bankAccount object to SDK.

setUpiPin() | NA | Send card object to SDK to create UPI PIN.

selectBankAccount() | NA | Send bank account and card details to set the pin.

BankAccountState

Enum Instances | Description

UPI_PIN_NOT_SET | This is the state of the bank account when the UPI pin is not set.

UPI_PIN_SET | This is the state of the bank account when the UPI pin is set.

LINKING_IN_PROGRESS | This is the state of the bank account when account linking is in progress.

LINKING_SUCCESS | This is the state of the bank account when the account is linked successfully.

LINKING_FAILED | This is the state of the bank account when the account linking is failed.

2. Test Integration

We recommend the following:
  • Complete the integration on UAT before using the prod builds.
  • Perform the UAT using the Razorpay-provided API keys.

3. Go-live Checklist

Complete these steps to take your integration live:
  • You should get your app id whitelisted by Razorpay to test on prod.
  • As a compliance requirement, you need to get approval from Google for READ_SMS permission. Refer to the Google article for more details.
  • Add Proguard rules:
    • keepclassmembers,allowobfuscation class * { @com.google.gson.annotations.SerializedName ; }
    • keepclassmembers enum * { *; }
    • keepclassmembers class * { @android.webkit.JavascriptInterface ; }
    • dontwarn com.razorpay.**
    • keep class com.razorpay.** {*;}
    • keep class com.olivelib.** {*;}
    • keep class com.olive.** {*;}
    • keep class org.apache.xml.security.** {*;}
    • keep interface org.apache.xml.security.** {*;}
    • keep class org.npci.** {*;}
    • keep interface org.npci.** {*;}
    • keep class retrofit2.** { *; }
    • keep class okhttp3.** { *; }
  • Replace the UAT credential with the Razorpay live keys for prod testing.