INTEGRATIONS
Razorpay
How to connect Razorpay to NoChurn: what to paste, what NoChurn does in Razorpay and what it reads.
Connect
In NoChurn, test mode first, open Integrations, pick Razorpay and paste the fields below (or send them to POST /v1/billing_connections with provider: "razorpay"). Use the provider’s test or sandbox credentials in test mode. Secrets are stored encrypted and never returned by the API.
| Field | Where to find it |
|---|---|
key_id | Account & Settings › API keys (rzp_test_… in Test mode) |
key_secretSECRET | Shown once when the key is generated |
The connection returns a webhook_url. Create a webhook endpoint on that URL in Razorpay, then paste the signing secret Razorpay gives you in NoChurn (webhook_secret on PATCH /v1/billing_connections/{id}).
What NoChurn does
| Retries | Razorpay retries the payment (its own retry settings). NoChurn sends the recovery emails. |
|---|---|
| Card update | The recovery emails link to Razorpay’s own page where the customer updates the payment method. |
| Cancel flow offers | Applied in Razorpay: pause. An offer the provider cannot apply reaches your backend as a billing.*_requested webhook. |
| Cancellation | A cancellation requested in the cancel flow is carried out in Razorpay. |
| Disputes | NoChurn gathers the evidence and drafts the reply; a person reviews it before it is sent to the provider. |
| Events | NoChurn follows Razorpay’s webhooks. |
| Import | The last 12 months are imported when you connect (POST /v1/billing_connections/{id}/backfill imports again). |
Fixed by Razorpay, not by a setting: retries, offers. The rest can be changed per connection with PATCH /v1/billing_connections/{id}.
What NoChurn reads
- Customers and subscriptions
- Payments and failures
- Payment method type (card, UPI, netbanking…)
- Disputes
What stays with Razorpay: payment processing; card and bank details; your plans and prices. More on the Razorpay integration page.