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

Recovery case RC-TM-LjCtaAvqeR

Explain the failure.
Show every decision.

Recovered

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

RAZORPAY TEST MODELast updated 2 Sept 2026, 5:12 pm
Amount at risk₹1pay_TXFGLjCtaAvqeR
Recoverability78/100High confidence band
Proposed actionCreate Payment LinkPolicy-controlled proposal
Recovered value₹1Closed 2 Sept 2026, 5:12 pm

Diagnosis and evidence

The normalized cause behind this failed payment.

Customer Auth

Customer authentication failed. A fresh, contextual payment attempt is more useful than repeated automatic retries.

Evidence used

Customer Contact Allowed
  • Error SourceCustomerRazorpay failure origin
  • Error StepPayment AuthenticationPayment-flow step
  • Error ReasonPayment CancelledNormalized failure reason
  • Error CodeBad Request ErrorProvider error code
  • Payment MethodCardNormalized payment method
  • Attempt Count1Failed attempts observed for this order
  • Classification RuleCustomer AuthDeterministic category selected from the observed signals
Payment ID
pay_TXFGLjCtaAvqeR
Order ID
order_TXFGAgGKAqY59Z
Payment method
Card
Payment status
Failed
Failure source
Customer
Failure step
Payment Authentication
Failure reason
Payment Cancelled
Occurred
2 Sept 2026, 5:08 pm

Recovery actions

Recommendations remain separate from policy approval and execution.

Attempt 1: Create Payment LinkSucceeded
AI proposal · gpt-5.6-terra

This is a contact-safe customer-authentication failure with no prior recovery actions. A payment link avoids another automatic attempt and lets the customer retry when ready within the recovery window.

  • ERROR_SOURCE: customer — Razorpay failure origin
  • ERROR_STEP: payment_authentication — Payment-flow step
  • ERROR_REASON: payment_cancelled — Normalized failure reason
  • PAYMENT_METHOD: CARD — Normalized payment method
  • ATTEMPT_COUNT: 1 — Failed attempts observed for this order
  • fallbackAction: CREATE_PAYMENT_LINK
Approved
The proposal passed payment-state, merchant, consent, limit, cooldown, recovery-window, and duplicate-action checks.
92% confidence2 Sept 2026, 5:08 pmEligible 2 Sept 2026, 5:11 pm
✓Test Mode payment recoveredThe ₹1 Payment Link has been paid and needs no retry.

Customer context

The minimum identity and consent context used by policy.

Customer
demo.customer
External reference
+919000000099
Contact preference
Contact allowed

Decision trail

A chronological, inspectable audit of this recovery case.

  1. 01
    Payment.failed.received2 Sept 2026, 5:08 pm · Webhook

    A signed Razorpay Test Mode webhook created this recovery case.

  2. 02
    Diagnosis.completed2 Sept 2026, 5:08 pm · Diagnosis Engine

    Customer authentication failed. A fresh, contextual payment attempt is more useful than repeated automatic retries.

    Decision: Customer Auth
  3. 03
    Agent.proposal.created2 Sept 2026, 5:08 pm · Recovery Agent

    This is a contact-safe customer-authentication failure with no prior recovery actions. A payment link avoids another automatic attempt and lets the customer retry when ready within the recovery window.

Decision: Create Payment Link
  • 04
    Policy.approved2 Sept 2026, 5:08 pm · Policy Engine

    The proposal passed payment-state, merchant, consent, limit, cooldown, recovery-window, and duplicate-action checks.

    Decision: Approved
  • 05
    Recovery.executed2 Sept 2026, 5:11 pm · Execution Layer

    BullMQ executed CREATE_PAYMENT_LINK for attempt 1.

    Decision: Succeeded
  • 06
    Recovery.verified.api2 Sept 2026, 5:11 pm · Execution Layer

    The Payment Link API state was checked and is not paid.

    Decision: Created
  • 07
    Payment Link.paid.received2 Sept 2026, 5:12 pm · Webhook

    A paid Razorpay Payment Link verified recovered revenue.