[CRITICAL][Launch] Complete Razorpay production readiness, website compliance, and live billing verification

Context

Razorpay has confirmed that the website must be complete and live before the integration can be approved/activated for production use.

Tracker is currently being tested with Razorpay Test Mode. Before requesting production approval, the public website and billing system must be production-ready.

Website readiness

Verify the live public site has:

• working HTTPS production URL;
• clear product/service description;
• pricing page matching the actual product;
• Terms & Conditions;
• Privacy Policy;
• Refund / Cancellation Policy with clear timelines/conditions;
• Contact / support information;
• accurate business/merchant identity details required for onboarding;
• no placeholder content;
• no broken links;
• no test-mode references visible to customers;
• checkout reachable from the live site.

Razorpay's current terms require merchants to display return/refund/cancellation information and customer terms on their website/app/customer interface, and require appropriate security/privacy measures.

Billing production readiness

Before switching to Live Mode:

• Test Mode and Live Mode credentials remain completely separated.
• Test plan IDs/offers/customer IDs/subscription IDs are never used in production.
• Live Razorpay plans are created and their IDs configured separately.
• Live webhook endpoint is configured.
• Live webhook secret is separate from Test Mode.
• Webhook signature verification is tested.
• Subscription activation/cancellation/failure/halting/expiry events reconcile correctly.
• Client checkout confirmation is supplemented by server-side webhook/provider verification.
• Production database does not contain test subscription/customer identifiers that can affect live entitlements.

Existing users / migration

Classify existing accounts:

1. Existing Free users remain Free; no migration grants Pro.
2. Existing users with legacy/local premium state are explicitly identified and migrated only under a documented rule.
3. Existing Test Mode billing records never become production entitlements; isolate/archive/mark them as Test Mode records.
4. Existing legacy 4-digit PIN users follow the password migration tracked in issue #49.

Production database safety

Verify:

• every active production subscription references a valid production provider subscription;
• no cust_mock_, sub_mock_, Test Mode plan IDs, Test Mode subscription IDs, or Test Mode offer IDs exist in production billing records;
• provider/environment is explicit;
• live/test configuration cannot be mixed accidentally;
• missing/invalid provider records fail closed rather than granting Pro.

End-to-end launch test

Free account
-> pricing
-> checkout
-> successful payment/authorization
-> webhook
-> ACTIVE subscription
-> Pro entitlement
-> actual Pro service
-> renewal/failure/cancellation handling
-> correct access after refresh/new login.

Do not switch public customers to Live Mode until this entire path is verified.

Acceptance criteria

• Razorpay can review a complete live website.
• Required customer-facing policy/contact information is present and accurate.
• Live and Test Mode billing data/configuration are isolated.
• Live webhook flow is verified.
• Existing users have an explicit migration policy.
• No test billing records can accidentally grant production access.
• A complete production-like paid-user journey passes before launch.

Start by auditing the live website, Razorpay Test Mode and Live Mode configuration, webhook flow, production billing records, and existing-user migration state described in this issue. Done means the required website policies are live, test and production data are isolated, webhook and entitlement handling pass the complete end-to-end journey, and the listed acceptance criteria are verified.