Razorpay
Keep Razorpay in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
29 ways to read, 14 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Razorpay, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create customerApproval by rule
- Create draft invoiceApproval by rule
- List customersRead
Example flow
- Razorpay · List customersDone
- Razorpay · Create customerNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Razorpay.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Razorpay
- Razorpay's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Razorpay test account before you go live.
For developers
Technical detail
Razorpay customers, orders, payments, refunds, disputes, draft invoices, payment links, items, plans, subscriptions, settlements and settlement reconciliation.
Razorpay API docs- Source actions
- 29
- Destination actions
- 14
- Data types
- 18
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Customers4
- Create customerDestinationNot retried automaticallyApproval before production
Creates a customer. fail_existing is 0, so an existing customer with the same email and contact is returned instead of an error.
- Get customerSource
One customer by ID.
- List customersSource
Customers, newest first, with count/skip paging.
- Update customerDestinationProvider duplicate protectionApproval before production
Edits a customer's name, email and contact.
Disputes2
- Get disputeSource
One dispute by ID.
- List disputesSourceIncremental
Disputes, newest first, with count/skip paging.
Instant settlements2
- Get instant settlementSource
One instant settlement by ID.
- List instant settlementsSourceIncremental
Instant (on-demand) settlements already requested, with amounts settled, pending and reversed. Read-only.
Invoice drafts1
- Create draft invoiceDestinationNot retried automaticallyApproval before production
Creates a draft invoice for an existing customer. It is never issued and Razorpay sends no SMS or email; issue it from the Razorpay Dashboard when ready.
Invoices4
- Create invoiceDestinationNot retried automaticallyApproval before production
Creates an invoice for an existing customer. It is saved as a draft unless Issue is true; SMS and email notifications are always off.
- Get invoiceSource
One invoice by ID.
- List invoicesSource
Invoices, newest first, with count/skip paging.
- Update invoiceDestinationProvider duplicate protectionApproval before production
Updates an invoice. Drafts accept every field; issued invoices accept partial payment, receipt, comment, terms, notes and expiry; other statuses accept notes only.
Items4
- Create itemDestinationNot retried automaticallyApproval before production
Creates a reusable invoice item.
- Get itemSource
One item by ID.
- List itemsSourceIncremental
Items, newest first, with count/skip paging.
- Update itemDestinationProvider duplicate protectionApproval before production
Updates an item's name, description, price, currency or active flag.
Order payments1
- List order paymentsSource
Payment attempts made against one order.
Orders4
- Create orderDestinationNot retried automaticallyApproval before production
Creates an order that a checkout or payment link can collect against. No money moves until the customer pays.
- Get orderSource
One order by ID.
- List ordersSourceIncremental
Orders, newest first, with count/skip paging.
- Update order notesDestinationProvider duplicate protectionApproval before production
Replaces an order's notes; Razorpay allows no other order changes.
Payment downtimes2
- Get payment downtimeSource
One payment downtime by ID.
- List payment downtimesSource
Current and scheduled downtimes of banks, card networks, UPI handles and wallets, so flows can warn customers or switch methods.
Payment links4
- Create payment linkDestinationNot retried automaticallyApproval before production
Creates a standard payment link. Razorpay SMS and email notifications and reminders are switched off; share the short URL yourself.
- Get payment linkSource
One payment link by ID.
- List payment linksSource
Standard payment links, optionally filtered by payment ID or reference ID.
- Update payment linkDestinationProvider duplicate protectionApproval before production
Updates reference, expiry, partial payment, reminders or notes on a link in created or partially_paid state.
Payment refunds1
- List payment refundsSourceIncremental
Refunds already issued against one payment. Nexra does not create refunds.
Payments3
- Get paymentSource
One payment by ID.
- List paymentsSourceIncremental
Payments, newest first, with count/skip paging.
- Update payment notesDestinationProvider duplicate protectionApproval before production
Replaces a payment's notes. Razorpay allows no other payment changes; nothing is captured or refunded.
Plans3
- Create planDestinationNot retried automaticallyApproval before production
Creates a subscription plan (price and billing frequency). No customer is charged until a subscription is created and authorised outside Nexra.
- Get planSource
One plan by ID.
- List plansSourceIncremental
Plans, newest first, with count/skip paging.
Receipt orders1
- Create order with receiptDestinationProvider duplicate protectionApproval before production
Creates an order keyed by your receipt. Razorpay rejects a second order with the same receipt, so a repeated request cannot create a duplicate. No money moves until the customer pays.
Refunds2
- Get refundSource
One refund by ID, for reconciliation.
- List refundsSourceIncremental
Refunds already issued, for reconciliation. Nexra does not create refunds.
Settlement recon1
- List settlement reconciliationSource
Payments, refunds, transfers and adjustments settled in a month or day, with fees, tax and UTR.
Settlements2
- Get settlementSource
One settlement by ID.
- List settlementsSourceIncremental
Settlements, newest first, with count/skip paging.
Subscriptions2
- Get subscriptionSource
One subscription by ID.
- List subscriptionsSourceIncremental
Subscriptions, newest first, optionally for one plan. Read-only.
Access and limits
- Authentication
- Razorpay API key ID and key secret (HTTP Basic)
- Plans and access
- Any activated Razorpay account; Test Mode keys work before activation. API keys act for the whole merchant account. Invoices, items and settlement reconciliation are documented for India, Malaysia and Singapore accounts.
- Test environment
- Test Mode uses separate rzp_test_ keys on the same host and never moves money; test mode allows at most 30 payment links.
- Rate limits
- Razorpay applies a request rate limiter without published fixed numbers and returns HTTP 429; Nexra backs off and retries reads.
- Pagination
- count (max 100) and skip with Unix from/to on creation time. Payment links return a single list.
- Provider events
- Razorpay webhooks for payment, order, invoice, payment link, refund, settlement and dispute events. Flows can start the moment something happens: when a payment succeeds; when a payment fails; when a refund is processed; when a dispute is opened.
Before you build a flow
- Refunds, payment capture, payouts, instant settlements, transfers, dispute accept or contest, invoice issue, cancel, delete and notification sends, and payment link cancel and resend are intentionally not automated.
- Payments are read-only except for notes (payments.update); refund notes updates are not exposed.
- Razorpay filters lists by creation time (from/to), not by modification time, so incremental reads only pick up new records.
- Invoices are created with sms_notify and email_notify set to false. Payment links are created with notify.sms, notify.email and reminder_enable set to false, but Razorpay has no draft state for payment links: a created link is live and payable through its short URL, although nothing is sent.
- Only orders accept notes updates after creation; Razorpay allows no other order changes.
- The payment link list endpoint documents only payment_id and reference_id filters and is read as one page.
- Razorpay documents no idempotency header. receipt_orders.create requires a receipt, which Razorpay rejects when reused, and is keyed by it.
- Subscriptions are read-only: creating, updating, pausing, resuming or cancelling subscriptions, subscription links and offers are not implemented because they charge or change charges to customers. Plans can be created (they move no money) but Razorpay offers no plan update.
- Instant settlements (settlements on demand) are read-only; creating one moves money and is not implemented.
- UPI-specific payment links, Route transfers, Smart Collect virtual accounts, QR codes, saved card tokens and RazorpayX are not covered.
Developer reference
- Create the Razorpay credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Razorpay, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/razorpay and the Connections API.