Razorpay

Overview

This node integrates with a payment service to manage various payment-related resources, including Payment Links. Specifically, the Fetch Payment Link operation retrieves detailed information about a single payment link using its unique identifier. This is useful when you want to verify the status, details, or metadata of a previously created payment link.

Common scenarios include:

• Checking the current status of a payment link (e.g., whether it is active, expired, or paid).
• Retrieving payment link details for record-keeping or reporting.
• Validating payment link data before proceeding with further business logic.

Example: After creating a payment link and sending it to a customer, you can use this operation to fetch the link’s details later to confirm if the payment was completed.

Properties

Output

The output is a JSON object containing all the details of the requested payment link as returned by the payment service API. This typically includes fields such as:

• Payment link ID
• Status (e.g., created, paid, cancelled)
• Amount and currency
• Description or purpose of the payment link
• Customer details (if available)
• Creation and expiry timestamps
• Any metadata associated with the payment link

If the node supports binary data output, it would generally relate to downloadable invoices or receipts linked to the payment, 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 being accessible and the provided payment link ID being valid.
• No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

• Invalid Payment Link ID: If the provided ID does not exist or is malformed, the node will throw an error indicating the resource could not be found. Verify the ID format and ensure the payment link exists.
• Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly configured in n8n.
• Network Issues: Connectivity problems with the payment service API may result in timeouts or errors. Check network access and service status.
• Unknown Operation Error: If the operation parameter is incorrect or unsupported, the node throws an "Unknown operation" error. Confirm that the operation is set to "fetchPaymentLink" for this use case.

Links and References

• Payment Service API Documentation - Payment Links
• n8n Documentation - Creating Custom Nodes
• Handling API Credentials in n8n