How to Tell If a Website Uses Razorpay

Razorpay is India's leading payment gateway, the way a huge share of Indian online businesses accept payments — cards, UPI, netbanking and wallets. Because it loads a distinctive checkout script and exposes a clear global, detecting it is straightforward: look for checkout.razorpay.com/v1/checkout.js and the global Razorpay constructor. This guide covers every reliable signal, the checkout model behind them, the other gateways to distinguish it from, and what Razorpay usage tells you about the business and its market. Because Razorpay is India's dominant gateway, recognising it is one of the most reliable ways to confirm a business serves the Indian market.

What is Razorpay?

Razorpay is a full-stack payments platform founded in India, and the dominant payment gateway in the Indian market. It lets businesses accept payments through every method Indian customers use — domestic and international cards, UPI (India's ubiquitous instant-payment system), netbanking, and wallets — and has expanded into banking, payroll and lending for businesses (RazorpayX). For online merchants, its appeal is a developer-friendly, India-optimised checkout that handles the country's diverse payment landscape in one integration. It is to Indian ecommerce and SaaS what Stripe is to much of the West.

For detection, the key context is that Razorpay is a strong India signal. Because it is India-focused and supports India-specific methods, finding it almost always means an India-based or India-focused business — ecommerce, SaaS, services, education, or a startup. Finding it tells you the business serves the Indian market and accepts local payment methods. Because Razorpay loads from checkout.razorpay.com with a key that reveals live/test mode and calls api.razorpay.com, it is easy to confirm. Its presence marks an Indian online business and its market focus.

How Razorpay loads and processes payments

A Razorpay integration loads the standard checkout from checkout.razorpay.com/v1/checkout.js, which exposes the global Razorpay constructor. The merchant initialises it with options including the key (the key_id, prefixed rzp_live_ for live mode or rzp_test_ for test mode), the amount, currency (typically INR) and order details: var rzp = new Razorpay(options); rzp.open();. The checkout opens as a modal/iframe overlay where the customer selects a method — UPI, cards, netbanking, wallets — and payment is processed via api.razorpay.com.

Some merchants use Razorpay's hosted Payment Pages/Links or a custom server-side integration, but the checkout.razorpay.com script and api.razorpay.com calls are consistent signals. The key_id prefix tells you whether real payments are being processed. So a Razorpay site shows the checkout.razorpay.com/v1/checkout.js script, the Razorpay global, the rzp_live_/rzp_test_ key, and api.razorpay.com traffic. Knowing these makes detection quick and reveals live/test mode.

How to tell if a website uses Razorpay

Confirm at least one strong signal.

1. Check the Network tab. On a checkout, filter for razorpay. The script from checkout.razorpay.com/v1/checkout.js and calls to api.razorpay.com confirm Razorpay.

2. Use the console. Type Razorpay and press Enter. A returned constructor confirms the checkout library.

3. View the source. Search for razorpay. The checkout.razorpay.com script and the new Razorpay(...) configuration with a key are usually visible.

4. Read the key_id. A rzp_live_... or rzp_test_... key confirms Razorpay and reveals live vs test mode.

5. Trigger the checkout. The Razorpay payment modal (with UPI, cards, netbanking, wallets) opening on checkout is a clear confirmation.

What the Razorpay signals look like

<script src="https://checkout.razorpay.com/v1/checkout.js"></script>
var rzp = new Razorpay({ key: "rzp_live_AbC123", amount: 50000, currency: "INR", order_id: "order_…" });
window.Razorpay = ƒ Razorpay()
POST https://api.razorpay.com/v1/...   (payment processing)

The checkout.razorpay.com/v1/checkout.js script, the Razorpay global, the rzp_live_/rzp_test_ key, and api.razorpay.com traffic are conclusive.

Razorpay versus other gateways — avoiding false positives

Match the domain and global to keep payment gateways distinct. Razorpay uses checkout.razorpay.com/api.razorpay.com and the Razorpay global; Stripe uses js.stripe.com and the Stripe constructor; PayU (another India gateway) uses its own domains; Cashfree, Instamojo and CCAvenue are other Indian gateways with distinct hosts; Paytm uses its own checkout. The razorpay.com domains and the Razorpay global are unique to Razorpay. Its India focus distinguishes it regionally — finding Razorpay rather than Stripe is itself a market signal. A business may use Razorpay for India and another processor for other markets, so check for multiple gateways on cross-border sites.

How reliable is each Razorpay signal?

The checkout.razorpay.com/v1/checkout.js script and the Razorpay global are definitive, as is api.razorpay.com traffic. The rzp_live_/rzp_test_ key is unambiguous and reveals the mode. The weakest situation is a homepage that loads Razorpay only at checkout, so test the payment step. As a rule, the checkout.razorpay.com script or the Razorpay global settles it, and the key prefix reveals whether real payments are processed.

What Razorpay usage reveals about a business

Finding Razorpay signals an Indian online business accepting payments via the dominant local gateway. Its India focus and support for UPI, netbanking and Indian cards mean its presence almost certainly indicates an India-based or India-serving business — ecommerce, SaaS, edtech, services or a startup. Finding it tells you the business serves Indian customers and has integrated local payment methods, and the live key confirms it is transacting. If you sell to Indian businesses, or to companies expanding into India, a Razorpay site marks an Indian-market operation. The broader Razorpay product footprint (RazorpayX banking, payroll, lending) may indicate a deeper Razorpay relationship. Because Razorpay is the default for Indian online businesses, its presence is also a strong "this is an Indian company" signal for market research and segmentation.

What finding Razorpay means for sales, agencies and competitive research

For sales and prospecting, Razorpay marks an Indian online business — a precise market signal for anyone targeting or expanding into India, and a fit for ecommerce, SaaS and fintech tools serving Indian merchants.

For agencies and consultants, finding Razorpay tells you the client serves the Indian market with local payment methods, so engagements can address India-specific conversion (UPI optimisation), checkout, or expansion.

For competitive and market research, Razorpay (versus Stripe or other gateways) reveals a business's market focus; mapping Razorpay across a sector identifies the India-focused players, useful for market sizing and competitive segmentation.

Razorpay in the wider stack

Razorpay sits in the payments layer of an India-focused stack. It accompanies an ecommerce platform (Shopify, WooCommerce, or Indian platforms) or a custom app, analytics (GA4), and often India-specific marketing and logistics tools. On cross-border businesses, Razorpay (for India) may sit alongside Stripe or another processor (for other markets). For an auditor, the valuable details are the key (live/test mode), whether other gateways serve other markets, the ecommerce platform, and any RazorpayX/banking signals; together these reveal an India-focused business and its payment and market strategy. Razorpay's value as a market signal is hard to overstate: payment-gateway choice is one of the most reliable proxies for which market a business actually serves, because gateways are chosen to support local methods and settlement. So mapping Razorpay across a list effectively isolates the India-focused companies in it — a segmentation that is otherwise surprisingly hard to derive from a website alone, since language, currency and TLD are all imperfect signals. For anyone selling into India, partnering with Indian businesses, or sizing the Indian segment of a market, a Razorpay scan is among the most efficient and accurate filters available, and the live-versus-test key even tells you which of those businesses are actively transacting.

A quick Razorpay confirmation walkthrough

Open a checkout or payment page with developer tools on the Network panel and filter for razorpay. The script from checkout.razorpay.com/v1/checkout.js and calls to api.razorpay.com confirm Razorpay. In the console, type Razorpay to confirm the constructor. View the source for the new Razorpay({ key: "rzp_live_..." }) configuration and read the key to determine live vs test mode. Triggering the checkout opens the Razorpay modal with UPI, cards and netbanking. The checkout.razorpay.com script or the Razorpay global confirms Razorpay.

A quick Razorpay detection checklist

• On a checkout, filter the Network tab for razorpay; the checkout.razorpay.com/v1/checkout.js script is conclusive.
• Type Razorpay in the console to confirm the constructor.
• Read the key (rzp_live_/rzp_test_) for live vs test mode.
• Look for api.razorpay.com payment traffic and the UPI/cards/netbanking modal.
• Treat Razorpay as a strong India-market signal.
• Distinguish Razorpay (razorpay.com) from Stripe, PayU, Cashfree and Paytm.

Detecting Razorpay at scale

Checking one site is quick, but mapping gateway adoption across many domains — to find India-focused businesses — calls for automation. StackOptic detects Razorpay and thousands of other technologies from a real browser, reading the script, global and API traffic. For related reading, see our guide to finding out what payment processor a website uses and the full Razorpay technology profile.