Razorpay Refund Reconciliation
Refund exceptions surfaced before escalation.
Helps finance and support spot Razorpay refund problems before customers escalate or books drift.
Compares refund status, timing, value, and related payments to detect aging items, exceptions, and customer-impacting cases.
How it runs
Multi-agent orchestration — here's the flow, step by step.
Call verslay_recall to retrieve prior Razorpay refund rate baselines, average processing times, and refund policy thresholds from memory. Connect to Razorpay to pull all refund records for the specified date range: refund IDs, original payment IDs, refund amounts, speeds (instant/normal), statuses (processed/pending/failed), and initiation vs settlement dates. Produce a refund transaction dataset as Phase 1 output.
payment scannerConsume Phase 1 refund dataset. Cross-reference each refund against its original payment to verify amount accuracy (partial vs full refund, no over-refund). Calculate refund processing lag (initiation to settlement) segmented by speed tier (instant vs normal). Identify failed or stuck refunds. Flag anomalies: over-refund cases, duplicate refund attempts, and refunds on disputed payments. Produce a refund discrepancy ledger for Phase 3.
razorpay payment operations analystIn parallel with razorpay-payment-operations-analyst, call verslay_web_search for 'Razorpay refund processing SLA 2026' and 'Indian e-commerce refund rate benchmarks' to surface platform SLA standards and industry refund norms. Call verslay_news_search for any RBI or NPCI regulation updates affecting refund timelines in India. Call verslay_rss_fetch on Razorpay developer blog RSS to catch any refund-related API changes. Produce an industry refund standards package for Phase 4.
web researcherConsume Phase 2 refund discrepancy ledger and Phase 2 industry standards. Apply reconciliation logic: match each refund to original payment amount, verify no over-refund, confirm status is 'processed' within Razorpay's SLA window. Calculate total refunded amount vs expected, cumulative SLA breach count, and percentage of refunds processed on time. Produce a reconciliation summary for Phase 4.
reconciliation checkerConsume Phase 3 reconciliation summary, Phase 2 discrepancy ledger, and Phase 2 industry benchmarks. Aggregate refunds by type (full/partial), speed tier, and anomaly class. Compare refund rate and lag to industry benchmarks from Phase 2. Call verslay_chart_create to generate a refund-status breakdown pie chart and a processing-lag distribution histogram. Compute total refund cost as percentage of gross revenue. Produce a synthesis package for Phase 5.
data analystConsume Phase 4 charts and synthesis, Phase 3 reconciliation summary, and Phase 2 standards. Write a refund reconciliation brief: total refund volume and rate, SLA compliance rate vs Razorpay standard, anomaly list (over-refunds, duplicates, failed refunds), benchmark comparison (industry refund rate vs company rate), and recommended remediation actions. Call verslay_memorize to store the current period's refund rate, SLA compliance rate, and anomaly counts as baseline. Pass to distributor.
executive briefing writerReceive the refund reconciliation brief from executive-briefing-writer. Distribute to the configured finance team email or Slack channel. Confirm delivery and log the send timestamp.
distributorRequired Agents
7- payment-scanner
- razorpay-payment-operations-analyst
- web-researcher
- reconciliation-checker
- data-analyst
- executive-briefing-writer
- distributor
Connections
Required
What it does
- Refund aging scan
- Payment-refund matching
- Exception detection
- High-value flags
- Finance review summary
Example prompt
Reconcile open Razorpay refunds. Flag aging refunds, mismatches, high-value cases, and what finance should review today.
Ready to deploy Razorpay Refund Reconciliation?
Start free. One click, full agent orchestration.
Get Started Free →