> ## Documentation Index
> Fetch the complete documentation index at: https://razorpay-60c89f9a-mintlify-audit-missing-sections-1778528421.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting & FAQs

> 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 

#### 1. What is an order id, and how to generate it?

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](/api/orders).

#### 2. What is the process for raising a request for a new feature?

To raise a request for a new feature, go to **New Issue** → **Feature Request** on our [GitHub repository](https://github.com/razorpay/razorpay-cordova/issues/new/choose).

#### 3. How can I update the existing **'razorpay-pod'**?

* 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'**

#### 4. I have integrated with the Razorpay Payment Gateway to accept payments on my mobile app. However, it gets rejected when I publish my app on the Apple App Store. The following message is displayed, "We noticed that your app offers a subscription with a mechanism other than the in-app purchase API." How to resolve this?

* **Cause**: 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.
* **Resolution**: Use Apple's in-app purchase APIs.

#### 5. In the new M1 MacBook, why am I not able to compile the Flutter Razorpay plugin for release mode?

This is because of the new changes introduced in Xcode 12.

To resolve this:

1. Use [Rosetta 2](https://support.apple.com/en-us/HT211861) for launching the app on your Mac.
2. Add the following lines to Podfile within `post_install do |installer|` .

```js: podfile theme={null}
installer.pods_project.build_configurations.each do |config|
  config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end
```

Know more about [compilation errors](https://khushwanttanwar.medium.com/xcode-12-compilation-errors-while-running-with-ios-14-simulators-5731c91326e9).

#### 6. How can I check the Razorpay Flutter Custom SDK version?

To check the SDK version:

<Steps>
  <Step title="Step 1">
    Open your Flutter project in your preferred code editor.
  </Step>

  <Step title="Step 2">
    Open the `pubspec.yaml` file in the root directory of your project.
  </Step>

  <Step title="Step 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`.
  </Step>
</Steps>

#### 7. How can I update the Razorpay Flutter Custom SDK version?

To update the SDK version, follow these steps:

<Steps>
  <Step title="Step 1">
    Open the terminal or command prompt and navigate to your project directory where the `package.json` file resides.
  </Step>

  <Step title="Step 2">
    Use the following command to update the dependencies listed in your pubspec.yaml file to their latest compatible versions.

    ```java: Update SDK theme={null}
    dart pub upgrade 
    ```
  </Step>

  <Step title="Step 3">
    If you are using a Flutter 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.
  </Step>

  <Step title="Step 4">
    After running the update command, review the updates fetched by npm to ensure they do not introduce any breaking changes.
  </Step>

  <Step title="Step 5">
    Conduct thorough testing to ensure that the updated packages do not adversely affect the application functionality and commit the changes.
  </Step>
</Steps>