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 enables creating a payment through the bunq banking API. It allows users to transfer money from a specified monetary account to a recipient identified by IBAN, email, or phone number. This is useful for automating payments such as sending invoices, paying suppliers, or transferring funds between accounts.
Practical examples:
- Automatically pay a vendor by specifying their IBAN and amount.
- Send a payment to a user’s email address linked to their bank account.
- Transfer money to a contact’s phone number registered with bunq.
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 to make the payment from (required). |
| Amount | The amount to transfer, e.g., "10.00" (required). |
| Currency | The currency of the payment. Options: EUR, USD, GBP (required). |
| Counterparty Type | The type of recipient identifier. Options: IBAN, Email, Phone (required). |
| IBAN | The IBAN of the recipient (required if Counterparty Type is IBAN). |
| The email address of the recipient (required if Counterparty Type is Email). | |
| Phone | The phone number of the recipient (required if Counterparty Type is Phone). |
| Recipient Name | The name of the recipient (required). |
| Description | Payment description or reference (optional). |
Output
The output is a JSON array where each item represents the response from the bunq API after creating a payment. The structure includes details about the created payment such as its status, identifiers, and metadata returned by the API.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the bunq banking API.
- Requires appropriate API credentials configured in n8n (an API key or OAuth2 token).
- The node uses internal helper functions to format responses and handle API requests.
Troubleshooting
Common issues:
- Missing or incorrect
Account IDwill cause the API request to fail. - Providing an invalid IBAN, email, or phone number depending on the selected counterparty type will result in errors.
- Insufficient funds or account restrictions may cause payment creation to be rejected.
- Missing or incorrect
Error messages:
- Errors from the bunq API will be propagated, often indicating invalid parameters or authorization issues.
- If the node throws an error about missing required fields, verify that all mandatory properties are set correctly.
Resolution tips:
- Double-check the monetary account ID and ensure it belongs to the authenticated user.
- Validate the recipient information matches the selected counterparty type.
- Ensure the API credentials have sufficient permissions to create payments.