Skip to main content
Order creation is the primary step of the Razorpay payment flow. An Order creates when a customer clicks the pay button on your app. A corresponding order_id generates in the response. Pass this order_id to the Razorpay Checkout options added in your Capacitor app. Know more about Orders.
To raise a request for a new feature, go to New IssueFeature Request on our GitHub repository.
  • Go to your project’s iOS folder and run ‘pod update’ to update all the pods.
  • If you do not want to update all pods, run ‘pod update razorpay-pod’.
As per Apple’s policy, if you use a subscription model in your iOS app, you must use Apple’s in-app purchase APIs. Apple does not redirect out of the app for digital product purchases.
This is because of the new changes introduced in Xcode 12.To resolve this:
  1. Use Rosetta 2 for launching the app on your Mac.
  2. Add the following lines to Podfile within post_install do |installer| .
podfile
Know more about compilation errors.
To check the SDK version:
  1. Open your Capacitor project in your preferred code editor.
  2. Open the package.json file in the root directory of your project.
  3. In the dependencies section, look for the Razorpay entry. The version number is specified next to the package name in the format x.y.z.
To update the SDK version using npm, follow these steps:
  1. Open the terminal or command prompt and navigate to your project directory where the package.json file resides.
  2. Use the npm update command followed by the package name to update a specific package to its latest version. For example, npm update <razorpay_package_name> (replace <razorpay_package_name> with the name of the package you want to update).
  3. If you are using a Capacitor iOS application, run cd ios && pod repo update && pod update to ensure the internal iOS dependencies are updated to the versions set by the Razorpay package. This is because cocoapods may not automatically update the internal trunk spec to fetch the latest versions.
  4. After running the update command, review the updates fetched by npm to ensure they do not introduce any breaking changes.
  5. Conduct thorough testing to ensure that the updated packages do not adversely affect the application functionality and commit the changes.