Razorpay modal close never detected: the checkout is a sandboxed iframe

TL;DR

Use the modal lifecycle callbacks in the Razorpay checkout options to detect dismissal, and run your cancel-order logic there. Razorpay exposes the modal lifecycle through its own checkout options instead.

Steps

1. Do not try to watch the Razorpay modal's close button with your own click handlers: it lives in a sandboxed iframe your page cannot touch. Use the modal lifecycle callbacks in the Razorpay checkout options to detect dismissal, and run your cancel-order logic there. If your close detection silently never fires, the iframe boundary is the reason.

When to use

You are seeing this: Do not try to watch the Razorpay modal's close button with your own click handlers: it lives in a sandboxed iframe your page cannot touch. Use this skill when you run into "Razorpay modal close never detected: the checkout is a sandboxed iframe".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #45049438 (accepted answer): A developer trying to detect when a user closes the Razorpay checkout modal attached a jQuery click handler to the close button and it never fired. The accepted answer explains why: the checkout page runs in a sandboxed iframe, so no page-side JS can reach the close button. Razorpay exposes the modal lifecycle through its own checkout options instead.

Verified resolution: Do not try to watch the Razorpay modal's close button with your own click handlers: it lives in a sandboxed iframe your page cannot touch. Use the modal lifecycle callbacks in the Razorpay checkout options to detect dismissal, and run your cancel-order logic there. If your close detection silently never fires, the iframe boundary is the reason.

Source URL: https://stackoverflow.com/questions/45049438