Razorpay icon

Razorpay

Interact with Razorpay payment gateway API

Actions10

Overview

This node interacts with Razorpay's Settlements API to fetch settlement records. Specifically, the "Fetch All" operation retrieves multiple settlement entries based on optional filtering and pagination parameters. This is useful for financial reconciliation, auditing, or reporting purposes where you need to obtain a list of settlements processed within a certain timeframe or in batches.

Practical examples include:

  • Fetching all settlements from the last month to reconcile payments.
  • Paginating through large numbers of settlements by skipping and limiting the count per request.
  • Filtering settlements between two specific timestamps to analyze cash flow during a campaign.

Properties

Name Meaning
Additional Options A collection of optional parameters to filter and paginate the fetched settlements:
- From Timestamp Unix timestamp (in seconds) specifying the start time from which settlements should be fetched.
- To Timestamp Unix timestamp (in seconds) specifying the end time until which settlements should be fetched.
- Count Number of settlement records to fetch, ranging from 1 to 100.
- Skip Number of settlement records to skip, used for pagination.

Output

The node outputs an array of JSON objects representing settlement records retrieved from Razorpay. Each item corresponds to one settlement entry containing details such as settlement ID, amount, status, and timestamps (though exact fields depend on Razorpay's API response).

The output structure is:

[
  {
    "json": {
      /* Settlement record fields */
    },
    "pairedItem": {
      "item": <index_of_input_item>
    }
  }
]

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with Razorpay's API.
  • The node depends on Razorpay's REST API endpoints for settlements.
  • No additional environment variables are explicitly required beyond the API credentials configured in n8n.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing invalid timestamps (e.g., non-numeric or out-of-range values) may result in API errors.
    • Requesting more than 100 records in Count will be rejected due to API limits.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • "Unknown operation: ..." — indicates an unsupported operation was selected; ensure "Fetch All" is chosen under Settlements.
    • API error messages returned from Razorpay will be surfaced; check the error details for causes like rate limiting or invalid parameters.
    • If continueOnFail is disabled, the node execution will stop on the first error; enabling it allows processing subsequent items despite errors.

Links and References

Discussion