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 operation allows you to create a payment request (called a "Request Inquiry") via the bunq banking API. It is useful when you want to request money from another party by specifying the amount, currency, and details about the debtor (the person who owes the money). The node supports requesting payments from different types of counterparty identifiers such as IBAN, email, or phone number.
Practical scenarios include:
- Requesting payment from a customer or client by email.
- Sending a payment request to a phone number for peer-to-peer transactions.
- Requesting funds from an IBAN account holder in a business context.
- Including a description or reference for the payment request.
- Allowing payment through bunq.me links for easier payer experience.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user on whose behalf the request is made. Leave empty to use the current user. |
| Account ID | The ID of the monetary account from which the request is issued. (Required) |
| Amount | The amount of money to request, e.g., "10.00". (Required) |
| Currency | The currency of the requested amount. Options: EUR, USD, GBP. (Required) |
| Counterparty Type | The type of identifier used for the debtor. Options: IBAN, Email, Phone. (Required) |
| IBAN | The IBAN of the debtor (required if Counterparty Type is IBAN). |
| The email address of the debtor (required if Counterparty Type is Email). | |
| Phone | The phone number of the debtor (required if Counterparty Type is Phone). |
| Debtor Name | The full name of the debtor. (Required) |
| Description | Optional description or reference for the payment request. |
| Allow Bunqme | Boolean flag indicating whether to allow payment via bunq.me link. Defaults to true. |
Output
The output JSON contains the response from the bunq API after creating the request inquiry. This typically includes details about the created payment request such as its unique ID, status, amount, currency, debtor information, description, and any URLs or tokens related to the request.
No binary data is output by this operation.
Dependencies
- Requires access to the bunq banking API.
- Requires proper authentication credentials configured in n8n for the bunq API.
- The node uses internal helper functions to format responses and handle API requests.
Troubleshooting
- Missing Required Fields: Ensure all required fields are provided, especially
accountId,amount,currency,counterpartyType,debtorName, and the corresponding contact detail based on the counterparty type. - Invalid Counterparty Details: Providing an invalid IBAN, email, or phone number will cause the API request to fail. Double-check these values.
- Authentication Errors: If the API key or OAuth token is missing or invalid, the request will be rejected. Verify your credentials setup.
- API Rate Limits or Network Issues: Temporary failures may occur due to network problems or API rate limits. Retrying might help.
- Error Messages: The node throws errors with messages returned from the bunq API. Review these messages carefully to identify issues like invalid parameters or permission problems.