Actions10
- Order Actions
- Payment Link Actions
- Payment Actions
- Refund Actions
- Settlement Actions
- Invoice Actions
- Dispute Actions
Overview
This node interacts with a payment service to fetch refund data. Specifically, the "Fetch All" operation under the "Refund" resource retrieves multiple refund records based on optional filtering and pagination parameters.
Typical use cases include:
- Retrieving a list of all refunds issued within a specific time range.
- Paginating through refunds for reporting or reconciliation purposes.
- Automating refund data extraction for accounting or customer service workflows.
For example, you might use this node to fetch all refunds created between two Unix timestamps or to retrieve the first 50 refunds while skipping the initial 10, enabling batch processing of refund data.
Properties
| Name | Meaning |
|---|---|
| Additional Options | A collection of optional parameters to filter and paginate the refunds fetched: |
| - From Timestamp | Unix timestamp indicating the start time from which refunds were created (inclusive). |
| - To Timestamp | Unix timestamp indicating the end time until which refunds were created (inclusive). |
| - Count | Number of refunds to fetch in one call; maximum allowed is 100. Default is 10. |
| - Skip | Number of refunds to skip for pagination purposes; default is 0. |
Output
The node outputs an array of JSON objects representing refund records. Each item corresponds to a single refund with its associated details as returned by the payment service API.
The output structure includes fields such as refund ID, amount, status, creation timestamp, and other relevant refund metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the payment service.
- The node depends on the payment provider's API endpoints for fetching refund data.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Providing invalid or expired API credentials will result in authentication errors.
- Specifying timestamps in incorrect formats (non-Unix timestamps) may cause the API to reject the request.
- Requesting more than 100 refunds in a single call will be rejected due to API limits.
- Network connectivity issues can prevent successful API calls.
Error Messages:
"Unknown operation": Indicates that the selected operation is not supported; ensure "Fetch All" is chosen under the Refund resource.- API error messages related to authentication or rate limiting should be resolved by verifying credentials and respecting API usage limits.
- Pagination errors may occur if
skiporcountvalues are out of valid ranges; adjust these parameters accordingly.
Links and References
- Razorpay Refunds API Documentation (example link to official refund API docs)
- Unix Timestamp Converter – useful for converting human-readable dates to Unix timestamps for input parameters.