Actions42
- Attachment Actions
- Payment Actions
- Transaction Actions
- Request Inquiry Actions
- Card Actions
- bunq.me Actions
- Webhook Actions
- Scheduled Payment Actions
- Export/Statement Actions
- User Actions
- Monetary Account Actions
Overview
This node interacts with the bunq banking API to update payment information. Specifically, the Payment - Update operation allows users to change the status of an existing payment, such as revoking (canceling) it.
Common scenarios where this node is beneficial include:
- Canceling a payment that was made in error or needs to be stopped.
- Managing payment workflows by programmatically updating payment statuses based on business logic or external triggers.
Practical example:
- A user wants to automatically cancel payments that have not been confirmed within a certain timeframe. This node can be used to update the payment status to "REVOKED" to reflect the cancellation.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user. Leave empty to use the current authenticated user. |
| Account ID | The ID of the monetary account from which the payment was made. (Required) |
| Payment ID | The ID of the payment to update. (Required) |
| Status | New status for the payment. Options: REVOKED (Cancel the payment). |
Output
The output is a JSON object representing the updated payment resource returned by the bunq API after the update operation. It contains details about the payment including its new status and other relevant metadata.
No binary data output is produced by this operation.
Dependencies
- Requires access to the bunq banking API.
- Requires proper authentication credentials configured in n8n (an API key or OAuth2 token).
- The node uses internal helper functions to format API responses and handle requests.
Troubleshooting
- Missing Required Parameters: Ensure that
Account IDandPayment IDare provided; otherwise, the API call will fail. - Invalid Payment ID: If the payment ID does not exist or belongs to another account/user, the API will return an error.
- Permission Issues: The API credentials must have permission to update payments on the specified account.
- API Errors: Network issues or API downtime may cause request failures. Check connectivity and bunq service status.
- Status Value: Currently, only the
REVOKEDstatus is supported for updates. Using unsupported statuses will result in errors.
To resolve errors, verify input parameters, check API credentials, and consult bunq API documentation for valid status values and permissions.