RazorPay
RazorPay payments and refunds (India-first)
RazorPay is India's payments stack of record (UPI, cards, netbanking, wallets), and Tiny Command surfaces three webhook events that map to the merchant's revenue cycle: Payment Captured (the customer's auth-and-capture or auto-capture succeeded), Payment Failed (the customer dropped off or the bank declined), and Refund Processed (the refund cleared, which on UPI can take seconds and on cards can take days). Four actions cover the writes and reads: Create Payment Link (the no-checkout-code path — RazorPay hosts the page), Create Refund (full or partial against a payment ID), Get Payment, and List Payments. RazorPay webhooks are HMAC-SHA256 signed and Tiny Command verifies the X-Razorpay-Signature header against the configured secret before any handler runs — invalid signatures never reach the workflow. The test-mode versus live-mode distinction is per-API-key — a test connection only fires on test webhooks, which makes it safe to staging-test high-value refund workflows.
Workflows start when RazorPay does.
3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.
Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).
Fires when a refund clears (UPI is sub-minute, cards can take days). For "refund processed → revoke product access, update customer record, log to refund tracking" workflows.
Do anything RazorPay can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create RazorPay Payment Link | Generates a RazorPay-hosted payment page with amount, currency, customer, expiry. For "send invoice via WhatsApp with pay-now button" or "no-checkout-code collection" workflows. |
| RazorPay Create Refund | Refunds a payment — full or partial in paise. The speed parameter (normal vs optimum) controls whether the refund uses instant rails. |
| Get RazorPay Payment | Returns a payment by ID with method, amount, customer, captured status. The standard lookup for fulfilment workflows. |
| List RazorPay Payments | Paginated payments with filters by status, date, customer. For "daily revenue rollup" or backfill workflows. |
Pre-built RazorPay workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect RazorPay once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every RazorPay field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the RazorPay integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect RazorPay to Tiny Command?
What RazorPay triggers does Tiny Command support?
What RazorPay actions can I run from a workflow?
Is the RazorPay integration real-time?
Do I need to write code to use RazorPay with Tiny Command?
How much does the RazorPay integration cost?
More payments apps people connect.
Same category as RazorPay, ordered by how often teams pair them. Hover the carousel to pause.
Do more with RazorPay.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
