Ask us anything. We probably already did.

No. Install is one OAuth approval — the checkout script attaches to your store automatically, no theme edits, no code. Uninstalling restores Shopify's native checkout instantly.

About a day, mostly your own pace: connect the store (2 minutes), add gateway keys, style the checkout in Widget Studio, place a test order on a private preview link, flip Go live.

No. Everything — install, branding, rules, offers, going live — is dashboard settings with a live preview. The only technical-ish step is pasting gateway API keys, and the fields tell you exactly where to find them.

Yes — that's the default. New stores start in testing mode: shoppers keep seeing Shopify's checkout while you test the real thing via a private preview link (visible only to people who have it) or on a draft theme.

Shopify's native checkout takes over immediately. Your orders, customers and reports stay in Shopify — they were always real Shopify orders.

For shoppers, yes — Checkout and Buy-now buttons open the IndiSell flow. Behind the scenes every order is created as a normal Shopify order, so fulfilment, apps, taxes and reports keep working untouched.

Phone number + OTP — no passwords, no accounts to create. The OTP arrives on SMS, or WhatsApp-first with automatic SMS fallback if you enable it. Merchants can choose 6-digit (default) or 4-digit codes.

The code falls back to SMS automatically when WhatsApp can't deliver synchronously, and the checkout always shows a 'Send by SMS instead' link so nobody gets stranded.

A shopper who has checked out on any IndiSell store gets their saved addresses offered on yours — but only after verifying the same phone number by OTP. No verification, no data.

The +91 OTP flow is India-only, so international visitors get a link to Shopify's native checkout, which handles worldwide addresses.

Fully — Widget Studio controls colors, corner radius, banner, copy, fonts (match your store's font or pick a Google Font) and every conversion element, with a live preview. Publishing is a settings change, not a deploy.

Every COD attempt gets a 0–100 risk score from network order history (RTOs, deliveries, paid orders), address quality, device and velocity signals — combined with your own rules: value caps, pincode/state gates, product gates, per-customer overrides.

The shopper pays a small advance online (you choose fixed ₹ or %) and the rest at the door. It keeps COD's comfort while making the buyer committed enough to accept delivery — the standard treatment for medium-risk orders.

No — decisions run server-side at payment time. The browser can request COD; the risk engine decides what's offered.

An optional WhatsApp/SMS/email sent after a COD order asking the buyer to Confirm or Cancel before dispatch. Cancellations at this stage cost you nothing — and feed the risk engine.

Yes — the COD simulator takes a phone, pincode and cart and shows the exact verdict with every signal behind it, before any shopper is affected.

No — it's the checkout layer on top. Payments run through your own Razorpay, PayU, Cashfree, PhonePe or Bulkpe accounts; money settles directly with you. IndiSell never holds funds.

No. You pay your gateway's MDR to them, exactly as today.

Only orders placed through the IndiSell checkout. Native-checkout, POS and draft orders are never billed; cancelled and refunded orders are excluded automatically.

One click from the dashboard — the refund is executed by your gateway and synced back. Refunds are idempotent, so a double-click can't pay out twice.

Effectively yes: install, test on a preview link and go live when ready — billing starts with real orders, so trying it costs nothing.

Never. Card entry happens on your gateway's PCI-compliant surfaces — full card numbers and CVVs never reach IndiSell.

Encrypted at rest, decrypted only to execute your own requests, never displayed back in full. Revoking an admin-granted capability wipes the related credentials.

You do. We process it to run your checkout, act on your export/deletion requests, and never sell it. Full details in the privacy policy.

No — server events and your pixels share order ids and the ad platforms deduplicate on them. Keep the tags you have.

Yes — real cart, real payment, real Shopify order. Cancel or refund them afterwards. That's what makes the test trustworthy.

No — analytics pixels stay off during preview and draft-theme testing, so ad platforms never see test traffic.

Team testing without sharing a link: anyone previewing a draft theme in Shopify gets the new checkout there, while the published theme stays untouched.

Instantly — one toggle returns every shopper to Shopify's checkout. Nothing is lost; flip forward again whenever.