Short answer: Drop the "RazorPay → RazorPay Create Refund" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Payment ID payment_id | string | Required | The ID of the payment to refund |
Amount (in paise) amount | string | Optional | Amount to refund in paise. Leave empty for a full refund. |
{"payment_id": "pay_abc123def456","amount": "25000"}
{"id": "rfnd_abc123def456","amount": 50000,"entity": "refund","status": "processed","currency": "INR","created_at": 1714010000,"payment_id": "pay_abc123def456","speed_processed": "normal"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.