Razorpay

Interact with Razorpay payment gateway API

Actions10

Order Actions
- Fetch All
Payment Link Actions
- Create
- Fetch
Payment Actions
- Fetch Payment
- Fetch All
Refund Actions
- Fetch All
Settlement Actions
- Fetch Settlement
- Fetch All
Invoice Actions
- Fetch Invoices for Subscription
Dispute Actions
- Fetch All

Overview

This node interacts with Razorpay's Order resource to fetch multiple orders based on various filtering and pagination options. It is useful for scenarios where you need to retrieve a list of orders from your Razorpay account, such as generating reports, syncing order data with other systems, or analyzing payment authorization statuses.

For example, you can use this node to:

Fetch all authorized orders within a specific date range.
Retrieve a paginated list of recent orders including detailed payment information.
Filter orders by receipt number to find specific transactions.

Properties

Name	Meaning
Authorization Status	Filter orders by payment authorization status. Options: All Orders, Authorized Only, Not Authorized Only
Count	Number of orders to fetch (1-100). Default is 10.
Expand Details	Additional information to include in the response. Options: Payments (include payment details), Payment Card Details (include card details for each payment)
From Date	Start date to fetch orders from (ISO 8601 datetime).
Receipt	Filter orders by receipt number (string).
Skip	Number of orders to skip for pagination (default: 0).
To Date	End date to fetch orders until (ISO 8601 datetime).

Output

The node outputs an array of JSON objects representing Razorpay orders matching the specified filters. Each object contains order details such as order ID, amount, currency, status, and optionally expanded payment and card details if requested.

The output structure corresponds directly to the Razorpay API response for orders, including nested fields when expansions are enabled.

No binary data is output by this node.

Dependencies

Requires a valid Razorpay API authentication token configured in the node credentials.
The node depends on the Razorpay API service being accessible.
No additional environment variables are required beyond standard n8n credential setup.

Troubleshooting

Common Issues:
- Invalid or missing API credentials will cause authentication errors.
- Requesting more than 100 orders in one call will be rejected due to API limits.
- Incorrect date formats for "From Date" or "To Date" may result in request failures.
- Using unsupported filter combinations might return empty results.
Error Messages:
- "Unknown operation": Indicates the selected operation is not implemented; ensure "Fetch All" is chosen under the Order resource.
- API errors related to authorization or rate limiting should be resolved by verifying credentials and respecting API usage limits.
- Pagination errors can occur if "Skip" exceeds the total number of available orders.