Troubleshooting & FAQs

Overflow issue can occur if the viewport meta tag is not present in your code. Check if the meta tag is added. If not, add the following line.

<meta name="viewport" content="width=device-width, initial-scale=1.0"/>

Transaction timeout is applicable only when your customer attempts the payment. It times outs between 3 to 15 minutes.

The customer is redirected to the checkout if a payment fails due to timeout.

You need to enable the international payments feature on your Razorpay account. Refer to

Yes, language-based SDKs are available

Yes, it is possible to easily switch from one integration method to another. If you were earlier using Standard Integration, you can switch to using

• This is possible because the Standard Integration searches for the data-key field inside the <script> tag, that when found, switches to automatic mode.
• It also creates a button alongside the <script> tag and attaches its 'onclick event handler' (created internally) to the .open method of the Razorpay object.

Yes, you can track the status of the checkout modal. You can do this by passing a modal object with ondismiss: function(){} as options. The ondismiss function is called when the modal is closed by the user.

var options = {
    "key": "<YOUR_KEY_ID>", // Enter the Key ID generated from the Dashboard
    "amount": "29935",
    "name": "Acme Corp",
    "description": "A Wild Sheep Chase is the third novel by Japanese author Haruki Murakami",
    "image": "http://example.com/your_logo.jpg",
    "handler": function (response){
        alert(response.razorpay_payment_id);
    },
    /**
      * You can track the modal lifecycle by * adding the below code in your options
      */
    "modal": {
        "ondismiss": function(){
            console.log('Checkout form closed');
        }
    }
};
var rzp1 = new Razorpay(options);

You can utilize the handler function called on every successful transaction for tracking payment completion.

You can use Callback URL and webhook to get the status of the transaction for a payment source.

Payment methods like

Yes, you can enable UPI Intent in WebView on your:

• Android app

• iOS app

Multiple factors can cause a 500 internal server error. Ensure that the required features are enabled on your MID. Additionally, verify that you are calling the API correctly. If the issue is still not resolved, contact our

To resolve the error, request your customers to refresh the page and clear the browser cache.

If you want to accept payments on your Android or iOS apps without integrating with our native SDKs, you can reuse your Standard Integration code. This approach opens the checkout form in a WebView within your mobile app. Know more about