Integrate with Turbo UPI
Steps to integrate Razorpay Turbo UPI with your app.
With Razorpay Turbo UPI, businesses experience faster and simpler payments. It condenses the payment process from 5 steps to just 1, eliminating app redirections. Enjoy a seamless in-app payment experience, reduce dependencies on third-party UPI apps, and gain complete visibility of the payment journey.
You can seamlessly integrate Turbo UPI with Razorpay iOS Standard SDK. Explore the full potential of
- Integrate with
- Import the following frameworks:
- Common library/NPCI framework
- Axis olive framework
- Razorpay Turbo UPI framework
The minimum supported iOS version for Turbo UPI is 11 and above.
Ensure your customers
Turbo UPI wrapper plugin is available as a cocoapod, which can be integrated with any iOS application with a minimum deployment target of iOS 11 later. Add the code given below in the project’s
podfile to get this cocoapod:
Follow these steps to integrate with Razorpay Turbo UPI:
Initialise the Checkout object to enable the Turbo UPI functionality.
Use the following code to link the newly created UPI account with your app. This function can be called from any application section, offering multiple entry points for customers to link their UPI account with your app. Linking it in advance allows customers to pay directly with the linked
UpiAccountwithout repeating the linking process.
Razorpay SDK will handle all the changes related to
UpiTurbo internally. To integrate with the payment flow,
Razorpay provides a single exposed function that allows you to manage linked UPI accounts and access all non-transactional flows seamlessly.
The SDK manages the linked
UpiAccounts on the application by triggering
manageUpiAccounts(), which follows the following internal non-transaction flows for
- Fetch balance: Check the customer's account balance.
- Change UPI pin: Provide the customer the ability to change their UPI PIN.
- Reset UPI pin: Let your customers reset the pin for their account.
- Delete the account from the application: Let your customers delink, that is, remove a selected UPI account from your application.
The SDKs given below provide access to exposed models for seamless integration.
|Types of error codes
|Brief description of the error.
|Specifies the specific reason for the error.
|Indicates the origin of the error. Possible values:
|Highlights the stage where the error occurred.
Is this integration guide useful?