Razorpay

Razorpay customers, orders, payments, refunds, disputes, invoices, payment links, items, settlements and settlement reconciliation.

Bring Razorpay collections, invoices and settlements into accounting and CRM flows, and raise orders, draft invoices and payment links from upstream systems.

Build a flow with Razorpay Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

customers

Create customer
Destination
Not retried automatically
Approval 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.
customers.create
Get customer
Source
One customer by ID.
customers.get
List customers
Source
Customers, newest first, with count/skip paging.
customers.list
Update customer
Destination
Provider duplicate protection
Approval before production
Edits a customer's name, email and contact.
customers.update

disputes

Get dispute
Source
One dispute by ID.
disputes.get
List disputes
Source
Incremental
Disputes, newest first, with count/skip paging.
disputes.list

invoices

Create invoice
Destination
Not retried automatically
Approval 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.
invoices.create
Get invoice
Source
One invoice by ID.
invoices.get
List invoices
Source
Invoices, newest first, with count/skip paging.
invoices.list
Update invoice
Destination
Provider duplicate protection
Approval 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.
invoices.update

items

Create item
Destination
Not retried automatically
Approval before production
Creates a reusable invoice item.
items.create
Get item
Source
One item by ID.
items.get
List items
Source
Incremental
Items, newest first, with count/skip paging.
items.list
Update item
Destination
Provider duplicate protection
Approval before production
Updates an item's name, description, price, currency or active flag.
items.update

order payments

List order payments
Source
Payment attempts made against one order.
order_payments.list

orders

Create order
Destination
Not retried automatically
Approval before production
Creates an order that a checkout or payment link can collect against. No money moves until the customer pays.
orders.create
Get order
Source
One order by ID.
orders.get
List orders
Source
Incremental
Orders, newest first, with count/skip paging.
orders.list
Update order notes
Destination
Provider duplicate protection
Approval before production
Replaces an order's notes; Razorpay allows no other order changes.
orders.update

payment links

Create payment link
Destination
Not retried automatically
Approval before production
Creates a standard payment link. Razorpay SMS and email notifications and reminders are switched off; share the short URL yourself.
payment_links.create
Get payment link
Source
One payment link by ID.
payment_links.get
List payment links
Source
Standard payment links, optionally filtered by payment ID or reference ID.
payment_links.list
Update payment link
Destination
Provider duplicate protection
Approval before production
Updates reference, expiry, partial payment, reminders or notes on a link in created or partially_paid state.
payment_links.update

payments

Get payment
Source
One payment by ID.
payments.get
List payments
Source
Incremental
Payments, newest first, with count/skip paging.
payments.list

refunds

List refunds
Source
Incremental
Refunds already issued, for reconciliation. Nexra does not create refunds.
refunds.list

settlement recon

List settlement reconciliation
Source
Payments, refunds, transfers and adjustments settled in a month or day, with fees, tax and UTR.
settlement_recon.list

settlements

Get settlement
Source
One settlement by ID.
settlements.get
List settlements
Source
Incremental
Settlements, newest first, with count/skip paging.
settlements.list

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. Nexra event triggers are not yet available; flows run on demand or on a schedule.

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; payment 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 as drafts by default and always with sms_notify and email_notify set to false; payment links are created with notify.sms, notify.email and reminder_enable set to false.
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 for these writes; uncertain creates are not repeated automatically.
UPI-specific payment links, subscriptions, Route, Smart Collect 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

Razorpay docsAPI reference Razorpay docsAuthentication Razorpay docsRate limits Razorpay docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/razorpay and the Connections API.