Now with confirmed copilot actions for live recovery ops

Undrop

An AI recovery cockpit for Razorpay merchants. Ask what is leaking, confirm the next action, resend recovery messages, update transaction status, and keep every decision traceable.

Launch cockpit See Ask Undrop

live recovery command center

Ask Undrop

Natural language, real payment actions.

Confirmation required

Resend WhatsApp recovery for txn_demo_7

I will resend a WhatsApp recovery message for Acme Store's INR 1,499 declined transaction. The recipient will come from the stored customer phone number. Confirm this action?

ConfirmCancel

Confirm

Resent WhatsApp recovery for txn_demo_7 via Twilio simulation. Audit entry written.

Built for payment teams that care about every failed checkout, every route, and every customer retry.

RazorpayUPICardsWhatsAppSupabase

Ask Undrop

A copilot that can act, with a human checkpoint.

The new tool-calling flow turns natural language into real recovery actions without letting a model send messages or mutate records unchecked.

Resend recovery messages

Ask Undrop can trigger email, SMS, WhatsApp, or Telegram recovery through the existing outreach providers.

Update transaction status

Mark a transaction recovered or escalated only after the merchant explicitly confirms the pending action.

Confirm before execution

Every tool call becomes a plain-language consequence summary with real transaction data before it runs.

Recovery loop

Every failed payment gets a better next move.

01

Capture

Razorpay failures and simulator events land in the Pulse Ledger with issuer, method, customer, and decline context.

02

Reason

GroqCloud or Cerebras summarizes the situation while deterministic rules keep the demo resilient.

03

Confirm

External actions pause as a pending confirmation with real amounts, channels, and transaction IDs.

04

Recover

The executor calls stored outreach configs, updates status, and writes an audit trace.

Route intelligence

Payment failures become route signals, not buried rows.

Undrop clusters failures by issuer, method, and error code so the team can see degraded corridors before they quietly drain GMV.

HDFC UPI Intent

critical
4.3x baseline

ICICI Card 3DS

high
2.1x baseline

SBI Netbanking

medium
1.6x baseline

Axis UPI Collect

watching
near normal

Product surfaces

Beautiful enough to demo. Concrete enough to operate.

Live GMV readout

Recovered GMV, recovery rate, and at-risk payments stay visible in the cockpit.

Real outreach paths

Email, SMS, WhatsApp, Telegram, and webhook integrations use stored merchant config.

Smart Router ready

Route clusters can become exportable route recommendations when router dependencies are enabled.

Retry timing

Recovery decisions can delay, retry, suggest alternatives, or escalate based on the failure signal.

Closed loop

Every payment outcome informs the next recovery decision and report view.

Credential care

Provider keys are stored encrypted and resolved server-side before dispatch.

Safe enough for live judging.

No tool executes on the same turn it is requested.
Unknown transaction IDs are refused before execution.
Recipients come from stored transaction data, not model text.
Executed tools are written to the agent action audit trail.

Buildathon ready

Recover the payment. Explain the decision. Prove the outcome.

Undrop turns failed Razorpay payments into an operator-grade recovery workflow with copilot actions, route intelligence, outreach, and auditability.

Open Undrop