Get RazorPay Payment: RazorPay action

Inputs

The fields this action accepts.

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 retrieve

Sample request

{
  "payment_id": "pay_abc123def456"
}

Returns

{
  "id": "pay_abc123def456",
  "fee": 1180,
  "tax": 180,
  "vpa": "customer@upi",
  "email": "customer@example.com",
  "amount": 50000,
  "entity": "payment",
  "method": "upi",
  "status": "captured",
  "contact": "+919876543210",
  "currency": "INR",
  "order_id": "order_xyz789",
  "created_at": 1714000000,
  "description": "Payment for Order #123"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get RazorPay Payment.

What does the Get RazorPay Payment action do in RazorPay?

Returns a payment by ID with method, amount, customer, captured status. The standard lookup for fulfilment workflows.

What inputs does Get RazorPay Payment require?

Required: Payment ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if RazorPay returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get RazorPay Payment support batch operations?

Yes. Run Get RazorPay Payment inside a Loop node to process arrays. Tiny Command handles RazorPay's rate limits automatically so you don't have to throttle manually.

More actions