Actions10
- Order Actions
- Payment Link Actions
- Payment Actions
- Refund Actions
- Settlement Actions
- Invoice Actions
- Dispute Actions
Overview
The node integrates with a payment service to fetch detailed information about a specific payment using its unique identifier. This operation is useful when you need to retrieve the status, amount, method, and other metadata related to a particular payment transaction.
Common scenarios include:
- Verifying payment details after a customer completes a purchase.
- Auditing or reconciling payments in your system.
- Fetching expanded payment information such as card, EMI, offer, or UPI details for enhanced reporting or processing.
For example, after receiving a payment ID from a webhook or database, you can use this node to fetch comprehensive payment data to update your records or trigger further workflows.
Properties
| Name | Meaning |
|---|---|
| Payment ID | Unique identifier of the payment to be retrieved (e.g., pay_DG4ZdRK8ZnXC3k). |
| Additional Options | Optional flags to expand specific parts of the payment details in the response: |
| - Expand Card Details | Whether to include detailed card information in the response (boolean). |
| - Expand EMI Details | Whether to include detailed EMI (Equated Monthly Installment) information (boolean). |
| - Expand Offer Details | Whether to include detailed offer-related information (boolean). |
| - Expand UPI Details | Whether to include detailed UPI (Unified Payments Interface) information (boolean). |
Output
The node outputs a JSON object representing the fetched payment details. The structure typically includes:
- Basic payment information such as payment ID, amount, currency, status, and timestamps.
- Depending on the selected expansion options, additional nested objects may appear:
- Card details (if expanded)
- EMI details (if expanded)
- Offer details (if expanded)
- UPI details (if expanded)
This output allows downstream nodes or processes to access comprehensive payment data for further automation or analysis.
If binary data were involved (e.g., receipts or documents), it would be included in a separate binary field, but this node focuses on JSON payment data only.
Dependencies
- Requires an API key credential for authenticating with the payment service.
- The node depends on the external payment provider's API to fetch payment information.
- Proper network connectivity and valid credentials are necessary.
- No additional environment variables beyond standard API authentication are indicated.
Troubleshooting
Common Issues:
- Invalid or missing Payment ID: The node requires a valid payment identifier; ensure it is correctly provided.
- Authentication failures: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network errors: Check internet connectivity and firewall settings that might block API requests.
- Unsupported expansions: If expansion options are set incorrectly or not supported by the API, the response may omit those details or return errors.
Error Messages:
"Unknown operation": Indicates the operation parameter is incorrect; ensure "fetchPayment" is selected.- API error messages returned from the payment service will be passed through; review them for specifics like invalid IDs or permission issues.
- Node operation errors will include the item index to help identify which input caused the failure.
To resolve errors, verify input parameters, credentials, and network conditions. Use the node's "Continue On Fail" option to handle errors gracefully in batch operations.