Help center

What "failed" actually means

A failed Razorpay payment usually falls in one of four buckets:

1. Bank-side decline. Insufficient balance, card limit hit, OTP timeout. The most common cause — and the one with the least guesswork.
2. Network drop. Your phone lost connection during the OTP screen. Razorpay marks the attempt as failed but no money moved.
3. Anti-fraud trigger. Your bank's fraud system flagged the merchant. A two-second call to the bank's customer support unblocks it.
4. App-side error. Rare, but happens. The retry path catches it.

The safe retry

1. Wait 60 seconds. If money was deducted by your bank but Razorpay didn't capture it, the bank auto-reverses within 5–7 working days — double-charge avoided.
2. Reopen the app.
3. Settings → Subscription → Retry payment.
4. Razorpay opens a fresh checkout. Use the same or a different payment method.

What not to do

• Don't open Razorpay's checkout twice in a row without waiting. Some banks treat back-to-back retries as fraud-suspicious and lock the card temporarily.
• Don't assume a deducted amount with a failed checkout means you've paid. Until Razorpay confirms the capture to us, you don't have access — and the deducted amount is genuinely on the way back.

If you're charged but the subscription doesn't activate

This is the messy case. Two possibilities:

• The capture is still in flight. Wait two hours; check the app again.
• The capture failed but your bank hasn't reversed yet. Email support@markov.in with the Razorpay reference ID from the checkout screen — we can look up the capture state directly.

UPI-specific gotcha

Some UPI apps (PhonePe, GPay) silently drop the second request if you launch a payment, close the app, and relaunch. The fix is to wait until the first request explicitly fails, then retry.