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 perform operations related to payments. Specifically, the Payment - Get operation retrieves details of a specific payment made from a monetary account. This is useful for scenarios where you want to fetch and verify payment information such as amount, recipient, status, or description.
Practical examples include:
- Retrieving payment details after initiating a transfer to confirm it was processed correctly.
- Fetching historical payment data for reconciliation or reporting purposes.
- Integrating payment information into workflows that require validation or further processing based on payment status.
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 unique identifier of the payment to retrieve. (Required) |
Output
The output is a JSON object representing the detailed information about the specified payment. It typically includes fields such as:
- Payment amount and currency
- Counterparty details (recipient)
- Description or memo of the payment
- Status of the payment (e.g., pending, completed)
- Timestamps and identifiers related to the payment
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the bunq API via configured credentials (an API key or OAuth2 token).
- The node depends on helper functions to make HTTP requests to the bunq API and format the responses.
- Proper permissions on the bunq account are necessary to access payment details.
Troubleshooting
Common issues:
- Missing or incorrect
Account IDorPayment IDwill cause the API request to fail. - Using a
User IDthat does not match the authenticated user or lacks access rights may result in authorization errors. - Network connectivity problems can prevent successful API calls.
- Missing or incorrect
Error messages:
- Errors returned by the bunq API will be propagated, such as "Payment not found" if the
Payment IDis invalid. - Authentication errors if credentials are missing or invalid.
- Errors returned by the bunq API will be propagated, such as "Payment not found" if the
Resolutions:
- Verify that all required IDs (
Account ID,Payment ID) are correct and exist. - Ensure the API credentials have sufficient permissions.
- Check network connectivity and retry if transient errors occur.
- Verify that all required IDs (