Prerequisites
- Integrate with Razorpay iOS Standard SDK. Ensure that you integrate with SDK version 1.0.0 or higher.
- Import the following frameworks:
- Common library/NPCI framework
- Axis olive framework
- Razorpay Turbo UPI framework
Onboarding Flow
Ensure your customers onboard with Razorpay Turbo UPI to get started.Installation
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’spodfile to get this cocoapod:
Turbo UI SDK Integration
Follow these steps to integrate with Razorpay Turbo UPI:-
Initialise the Checkout object to enable the Turbo UPI functionality.
Swift
-
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.Swift
Payment Flow
UpiTurbo internally. To integrate with the payment flow, pass payment option and display the checkout form.
Non-Transactional Flow
Razorpay provides a single exposed function that allows you to manage linked UPI accounts and access all non-transactional flows seamlessly.Manage UPI Accounts
The SDK manages the linkedUpiAccounts on the application by triggering manageUpiAccounts(), which follows the following internal non-transaction flows for UpiAccounts:
- 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.
Swift
Models Exposed from the SDKs
The SDKs given below provide access to exposed models for seamless integration.TurboError
Error | Description
errorCode | Types of error codes - BAD_REQUEST_ERROR: Failure from the client’s end (SDK).
-
GATEWAY_ERROR: Failure either from the Secure Component or the Bank. -
SERVER_ERROR: Failure at PSP.
errorDescription| Brief description of the error.errorReason| Specifies the specific reason for the error.errorSource| Indicates the origin of the error. Possible values: -gateway -
issuer_bank -
beneficiary_bank -
customer_psp -
customer -
internal
errorStep| Highlights the stage where the error occurred. Refer to the list of possible error reasons.
Go-Live Checklist
For iOS users, outgoing device binding SMS is editable by default. To ensure these SMS messages are non-editable, you must complete the following steps:Requesting UPI Device Validation Entitlement
1. Submit a Request on the Apple Developer Portal
- Log in to the Apple Developer Portal.
- Fill out the necessary details to request permission for the
setUPIVerificationCodeSendCompletionAPI, which allows secure, non-editable content for device registration SMS. - Await approval from Apple.
2. Submit Details to NPCI
Once Apple approves the entitlement, share the request details with NPCI for their approval. Use the format given below for submitting the details:- Name of the App:
- Functionality (UPI or CBDC App): UPI
- App ID:
- Team ID:
- Request ID:
- Bundle ID:
3. Follow the Guidelines for Implementation
- Ensure your app supports iOS 17 and above.
- Use the
setUPIVerificationCodeSendCompletionAPI to comply with NPCI requirements.