Skip to content
Test Agent
Checking

Test Agent

Give the agent a failed payment and watch it work. The failure is synthetic; the recovery is real.

Test mode

Simulate a failed payment

The failure event is synthetic. Everything the agent does about it is real.

The failure

₹2,499 — this is the amount any payment link will ask for.

₹
The customer

Your own number. If you don't receive a message, send Hi to +91 99274 71836 on WhatsApp first, then try again.

Used if WhatsApp delivery is unavailable.

Payment history raises the recovery score, which affects what policy allows.

These start at placeholder values. Whatever you leave here is the history the agent scores against — change them to see the decision change.

More than two recent failures lowers the recovery score.

Consent
A real WhatsApp message or email will be sent to the details above, containing a real Razorpay test payment link. The backend refuses to run without this confirmation, and limits how many messages one contact can receive.

Takes about 5–15 seconds. You can watch each step as it happens.

How this works

Read this before you run it — a real message goes to a real number.

Submitting the form creates one synthetic failure event, carrying the same error code and reason Razorpay would send for the scenario you pick. From that point on nothing is simulated. The agent classifies the failure, scores how recoverable it is, checks the decision against your policy limits, creates a Razorpay payment link if it is allowed to, and sends the customer a message over WhatsApp — falling back to email if WhatsApp is unavailable.

Every step on the right is read back out of the case's audit trail. If the backend did not record a step, this page does not show it as done.

Guardrails in force

  • Outreach is capped at the configured number of messages per case, and retries at the configured number of attempts.
  • This page is separately rate limited, so one phone number or address cannot be used to send unlimited test messages.
  • Your consent is written to the audit trail before anything is sent, with the contact details masked.
  • Cases started here are tagged Test run everywhere they appear, so they are never mistaken for merchant traffic.