Razorpay subscription recovery, automated.

Razorpay auto-retries the charge on T+1, T+2, and T+3. After three consecutive failures, the subscription moves to a "halted" state. Recurflux picks up where Razorpay stops: a 6-step recovery email sequence, failure-type-specific retry logic, and a pause flow to capture intent before the customer churns.

Razorpay sends one notification to the customer when a payment fails. There is no multi-touch email sequence, no subject line testing, and no behavioral segmentation. Recurflux adds the full recovery email layer on top of Razorpay's native notification.

A halted subscription means Razorpay has exhausted its retry window and stopped charging. The subscription is technically still active but not billing. Recurflux treats halted subscriptions as a separate failure type — the moment Razorpay fires the halted event, a dedicated win-back sequence starts (2–3 emails over 30 days), with copy written specifically for a lapsed account rather than a payment in progress. This is distinct from the recovery email sequence that runs during active retries.

Yes — in two ways. First, Recurflux handles UPI mandate failures and bank-specific decline codes alongside card declines, mapping each to the right retry timing. Second, on Growth plan, when a card payment fails, Recurflux automatically creates a Razorpay payment link with UPI enabled and emails it to the customer. They can pay the outstanding amount via GPay, PhonePe, Paytm, or any UPI app — no card required. The link expires in 7 days.

No code changes. Connect with your Razorpay Key ID and Secret — Recurflux sets up the webhook listener and begins syncing immediately. The entire setup takes under 5 minutes.

Razorpay's native 3-day retry recovers roughly 15–25% of failed charges. Adding Recurflux's multi-touch recovery emails, failure-type-specific retry logic, and subscription pause typically brings total recovery to 60–75%, depending on your MRR mix and failure code distribution.