Razorpay cookies3 of 5 need consent
Razorpay sets 5 cookies we know of. 3 cookies may only be set after the visitor opts in; 2 are strictly necessary and exempt.
Reviewed · Provider: Razorpay Software Private Limited
List of Razorpay cookies
rzp_unified_session_idNecessaryNo consent neededSessionStores a unified session identifier that ties a visitor's activity together across Razorpay's payment products during a single checkout session.
x-session-dataNecessaryNo consent neededSessionHolds session and account state for Razorpay's authenticated areas (accounts.razorpay.com), keeping a signed-in session valid.
ra_clientIdAnalyticsConsent required12 monthsAssigns a persistent client identifier used by Razorpay Analytics (the 'ra_' family of cookies) to recognise a returning browser and measure product usage.
ab_user_idAnalyticsConsent required12 monthsStores an identifier used to assign the visitor to A/B test variants so Razorpay can measure experiment performance.
rzp_utmMarketingConsent required12 monthsStores UTM campaign parameters (source, medium, campaign) so Razorpay can attribute sign-ups and conversions to marketing campaigns.
How to handle Razorpay cookies
- 1Load it only after consent
Hold the Razorpay script until the visitor accepts analytics / marketing cookies. Blocking the script is what stops the cookies; hiding them in a banner does not.
- 2Make Reject work
After a visitor rejects, none of the 3 consent-requiring cookies below may be set or kept.
- 3Name every cookie in your policy
List each cookie by name with its purpose, provider (Razorpay Software Private Limited) and lifetime.
- 4Check the result, not the settings
Open your site in a private window, reject cookies, and look at what was stored. Or run a scan and compare the three stages.
Tools that help: tracking script blocker · Consent Mode v2 generator
Other vendorsAnd the cookies they set
Does Razorpay wait for consent on your site?Scan it in 2 minutes
Free scan · every cookie before consent, after Reject and after Accept