RecoveryOS
DashboardReported issuesCheckout drop-offsRecovery workbenchTest paymentAbout
RecoveryOSAPI liveAPI readyWorker
Back to reported issues

Recovery case RC-1003

Explain the failure.
Show every decision.

Recovered

A normalized payment record, the proposed recovery path, and the complete audit trail behind it.

SIMULATED DATALast updated 20 Aug 2026, 10:12 am
Amount at risk₹1,896pay_sim_rc1003
Recoverability79/100High confidence band
Proposed actionWaitPolicy-controlled proposal
Recovered value₹1,896Closed 20 Aug 2026, 10:12 am

Diagnosis and evidence

The normalized cause behind this failed payment.

Customer Auth

Incorrect OTP. Customer retry recovered the payment without extra reminders.

Evidence used

  • Error SourceCustomerRazorpay failure origin
  • Error StepPayment AuthenticationPayment-flow step
  • Error ReasonIncorrect OtpNormalized failure reason
  • Error CodeBad Request ErrorProvider error code
  • Payment MethodCardNormalized payment method
Payment ID
pay_sim_rc1003
Order ID
order_sim_rc1003
Payment method
Card
Payment status
Failed
Failure source
Customer
Failure step
Payment Authentication
Failure reason
Incorrect Otp
Occurred
20 Aug 2026, 10:05 am

Recovery actions

Recommendations remain separate from policy approval and execution.

Attempt 1: WaitSucceeded
Proposed by Recovery Agent

Allow another immediate attempt after an incorrect OTP.

Approved
Customer-action failures should not generate delayed reminder spam.
79% confidence20 Aug 2026, 10:06 amEligible 20 Aug 2026, 10:06 am

Customer context

The minimum identity and consent context used by policy.

Customer
Kabir Shah
External reference
cust_kabir_shah
Contact preference
Contact allowed

Decision trail

A chronological, inspectable audit of this recovery case.

  1. 01
    Payment.captured.received20 Aug 2026, 10:12 am · Webhook

    The customer retried successfully after the OTP failure.

    Decision: Recovered