Every rupee that leaks out of your revenue finds its way back.
Reclaim is an autonomous revenue recovery agent for Razorpay merchants. It diagnoses why payments fail, decides the right recovery move, executes through Razorpay’s own APIs, and proves every action in a tamper-evident audit ledger.
₹0.0Cr+
Simulated recovered
0
Recovery surfaces
NPCI
Compliant retries
Hash-chained
Audit ledger
At Risk
₹18.2L
Recovered
₹6.4L
The Revenue Leak
Money disappears in four places. You’re only watching one.
Card Declines
Card failures, bank timeouts, 3DS drop-offs. You see “payment failed.” Reclaim sees “bank technical error at authentication step — retry in 4 hours.”
Abandoned Carts
Customers start checkout, get distracted, never return. No error is fired. Reclaim detects silence and sends a timed nudge.
Failed Mandates
UPI Autopay debits fail for insufficient funds. NPCI allows 3 retries in specific windows. Reclaim sequences them compliantly.
Overdue Invoices
B2B receivables go overdue because someone forgot, not because they refused. Reclaim chases with an escalation ladder.
The Architecture
Signal → Diagnose → Decide → Act → Audit
Ingest
Pulls failed payments, mandate events, abandoned orders, and overdue invoices from Razorpay’s APIs in real time.
Diagnose
Maps every failure to Razorpay’s own error taxonomy (source, step, reason). No black boxes — every diagnosis is a named rule you can read.
Guardrail
Checks NPCI retry limits, DND flags, spend caps, and cooldown windows before any action. The agent stops as visibly as it starts.
Execute
Creates payment links, retries mandates, and sends recovery nudges through Razorpay’s own APIs — the same tools its dashboard uses.
Audit
Every decision is written to an append-only, hash-chained ledger. Prove compliance without asking your engineering team.
Bounded & Gated
The agent acts by default. You set the boundaries.
Max Attempts
3 nudges max, 4 hours apart, never the same channel twice.
Spend Caps
Invoices above ₹1,00,000 route to human approval before the first message is sent.
NPCI Compliance
Mandate retries respect the 1+3 attempt cap, non-peak windows, and pre-debit notice rules.
“Stopping rules are first-class UI events. A case that correctly stops is styled with the same weight as a case that recovers.”
See It Work