How to add Razorpay Magic Checkout to your ecommerce website
What it needs beyond a normal Razorpay account, the callbacks your store has to answer, and whether 1-click actually pays for itself.
The short version: Magic Checkout is Razorpay's 1-click flow running on your own Razorpay account. Beyond a working Razorpay integration you need Magic enabled on your account, and your store has to answer a couple of callbacks while the checkout is open — chiefly to price shipping for whatever address the buyer picks.
TL;DR
- • You need a working Razorpay account with Magic Checkout enabled.
- • Your store must answer callbacks live while the modal is open — shipping being the important one.
- • Those callbacks are public endpoints, so they need their own authentication.
- • Money settles to your own Razorpay, on your normal schedule.
- • Always fall back to the native checkout if the modal cannot open.
Step 1 — Get Magic enabled
Magic Checkout is not on by default. You need a Razorpay account that has completed KYC and has Magic Checkout enabled on it — ask Razorpay if you do not see it.
If you have not connected Razorpay at all yet, start with the Razorpay setup guide; Magic sits on top of a working integration rather than replacing it.
Step 2 — Understand the callbacks
This is the part that makes Magic more work than a normal Razorpay integration, and it is worth knowing before you start.
The buyer picks a saved address inside Razorpay's modal, which your store has never seen. But shipping cost depends on that address — so Razorpay calls your store, live, while the modal is open, and your store has to answer with the shipping options and prices for that address, fast.
If you are building this yourself, that endpoint is on the critical path of every checkout. Slow or flaky, and the modal stalls in front of a buyer with their card out.
Those callbacks are public endpoints. Razorpay calls them from their servers, so they cannot sit behind your normal login. They need their own authentication — a per-store token in the URL path, or a signature check — or anyone who finds the URL can probe your shipping logic. Whatever you build, do not leave them open.
Step 3 — Decide whether 1-click is worth it
The case for Magic is recovered abandonment plus RTO reduction. The case against is that it is on a paid plan and adds a dependency to your checkout.
The number to look at first is where your buyers currently drop out. If your analytics show them reaching the address form and leaving, 1-click addresses exactly that and is likely worth it. If they are dropping out at the product page or the cart, a faster checkout fixes nothing — your problem is upstream, and you should spend the effort there instead.
Measure before you buy. This is a genuinely good feature for the right store and an expensive placebo for the wrong one.
Step 4 — Always keep the fallback
A hosted checkout is a dependency. Scripts fail to load, ad blockers block them, and plans lapse. If the modal cannot open, the buyer must land on your normal checkout form rather than an error.
On SitesPlaced both hosted checkouts fall back to the native form automatically, and the plan entitlement is re-checked per request — so a lapsed plan quietly reverts to the built-in checkout instead of breaking the store.
If you do not have the website yet
Everything above assumes you already have a store to put Magic Checkout on. If you are still taking orders in DMs, that is the part worth fixing first.
A SitesPlaced store is free to build and publish, with 0% commission on every sale, on every plan — and 21 integrations included rather than sold as add-ons. You can import your catalogue straight from Instagram instead of typing products in one at a time.
Magic Checkout and Sell with Shiprocket are both on the ₹499/month Ecommerce plan and can run at the same time. SitesPlaced takes 0% of every order either way.
Frequently asked questions
What do I need to use Razorpay Magic Checkout?
A Razorpay account through KYC with Magic Checkout enabled on it, plus a working Razorpay integration on your store. Magic sits on top of that rather than replacing it.
Why does my store need to answer callbacks?
The buyer picks a saved address inside Razorpay's modal, which your store never sees. Shipping cost depends on it, so Razorpay calls your store live while the modal is open and your store has to price shipping for that address quickly.
Are those callback endpoints a security risk?
They can be. They are called by Razorpay's servers, so they cannot sit behind a login and need their own authentication — a per-store token in the path or a signature check. Leaving them open lets anyone probe your shipping logic.
Is 1-click checkout worth paying for?
It depends entirely on where your buyers currently drop out. If they reach the address form and leave, yes. If they leave at the product page or cart, a faster checkout fixes nothing and you should spend the effort upstream. Measure first.
Add 1-click checkout, keep your settlement
Build the store free, then add Magic Checkout on the ₹499/month Ecommerce plan. Money settles to your own Razorpay.
