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 integrates with a payment service to fetch multiple payment records based on specified criteria. The "Fetch All" operation under the "Payment" resource allows users to retrieve a list of payments, optionally filtered by date range and paginated using count and skip parameters.

Common scenarios where this node is beneficial include:

Retrieving recent payment transactions for reconciliation or reporting.
Fetching payments within a specific timeframe for auditing purposes.
Paginating through large sets of payment data to process or analyze them in batches.

For example, a user might configure the node to fetch all payments made in the last month, retrieving 50 payments at a time, skipping the first 100 to paginate through results.

Properties

Name	Meaning
Additional Options	Collection of optional parameters to refine the fetch:
- From Date	Start date to fetch payments from (inclusive).
- To Date	End date to fetch payments until (inclusive).
- Count	Number of payments to fetch per request (1-100, default 10).
- Skip	Number of payments to skip for pagination (default 0).

Output

The node outputs an array of payment objects in the json field. Each object represents a payment record retrieved from the payment service API. The structure typically includes details such as payment ID, amount, currency, status, method, and timestamps.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to payments, but this operation focuses on JSON data only.

Dependencies

Requires an API key credential for authenticating with the payment service.
The node depends on the payment service's API endpoints to fetch payment data.
No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying invalid date ranges (e.g., 'From Date' after 'To Date') may result in empty responses or errors.
- Requesting a count outside the allowed range (less than 1 or greater than 100) will be rejected.
- Pagination parameters (skip) exceeding available data may return empty results.
Error Messages:
- "Unknown operation": Indicates the selected operation is not supported; ensure "Fetch All" is chosen under "Payment".
- API errors related to rate limits or invalid parameters will be surfaced; verify input values and API quota.
- Network or connectivity issues will cause request failures; check internet connection and API endpoint accessibility.