Actions39
- Client Actions
- Loan Actions
Overview
This node integrates with the Fineract API to manage loan-related operations, specifically enabling users to process a "Merchant Issued Refund" on a loan. This operation records a refund transaction issued by a merchant against a specified loan.
Common scenarios include:
- Financial institutions or loan servicing platforms needing to record refunds issued by merchants directly related to loans.
- Reconciling merchant refunds in loan accounts for accurate financial tracking.
- Automating refund entries into loan management systems to maintain up-to-date loan balances.
Practical example:
A loan officer receives a refund from a merchant for a particular loan and wants to log this refund transaction automatically in the loan system via n8n. Using this node, they provide the loan ID, refund amount, date, and optional details like payment type and notes, and the node submits this information to the Fineract API.
Properties
| Name | Meaning |
|---|---|
| Loan ID | The unique identifier of the loan for which the merchant issued refund is being processed. |
| Transaction Date | The date when the refund transaction occurred, formatted as YYYY-MM-DD. |
| Transaction Amount | The monetary amount of the merchant issued refund. |
| Payment Type ID | (Optional) Identifier specifying the payment method used for the refund. |
| External ID | (Optional) An external reference ID for the refund transaction, useful for reconciliation. |
| Note | (Optional) Additional notes or comments about the refund transaction. |
Output
The node outputs JSON data representing the response from the Fineract API after processing the merchant issued refund. This typically includes confirmation details of the refund transaction such as IDs, status, timestamps, and any relevant metadata returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Fineract API endpoint.
- Needs credentials including base URL, tenant ID, and an API authentication token configured in n8n.
- The node sends requests with appropriate headers (
Content-Type: application/json,Accept: application/json, and tenant identification).
Troubleshooting
- Invalid Loan ID: If the provided loan ID does not exist or is incorrect, the API will likely return an error indicating the loan was not found. Verify the loan ID before retrying.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure that the API key/token and tenant ID are correctly set in the node credentials.
- Date Format Issues: The transaction date must be in
YYYY-MM-DDformat. Incorrect formats may lead to validation errors. - Missing Required Fields: Omitting required properties like Loan ID, Transaction Date, or Transaction Amount will result in errors. Make sure all mandatory fields are provided.
- API Rate Limits or Connectivity: Network issues or API rate limits can cause request failures. Check connectivity and API usage quotas.
Links and References
- Fineract API Documentation — Official API docs for detailed information on endpoints and parameters.
- n8n Documentation — For guidance on setting up credentials and using custom nodes.