bunq icon

bunq

Interact with bunq banking API
Join our community

Actions42

Overview

The node interacts with the bunq banking API to manage card limits for a specified card. Specifically, the "Set Limits" operation allows users to set various spending or withdrawal limits on a card, such as daily or monthly ATM withdrawals, POS spending, or purchase limits. This is useful for controlling and monitoring card usage, preventing overspending, or enforcing budget constraints.

Practical examples:

  • A user wants to limit their card's daily ATM withdrawal to 200 EUR.
  • A business sets a monthly POS spending limit on employee cards to control expenses.
  • Parents set purchase limits on a child's card to manage allowance spending.

Properties

Name Meaning
User ID The ID of the user owning the card. Leave empty to use the current authenticated user.
Card ID The unique identifier of the card on which to set the limit. (Required)
Limit Type The type of limit to set. Options include:
- ATM Daily: Daily ATM withdrawal limit
- ATM Monthly: Monthly ATM withdrawal limit
- POS Daily: Daily point-of-sale spending limit
- POS Monthly: Monthly point-of-sale spending limit
- Purchase Daily: Daily purchase limit
- Purchase Monthly: Monthly purchase limit
Limit Amount The amount to set for the limit, e.g., "500.00". (Required)
Currency The currency for the limit amount. Options: EUR, USD, GBP. (Required)

Output

The output JSON contains the response from the bunq API after setting the card limit. It typically includes confirmation details about the newly set limit, such as the limit type, amount, currency, and status.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the bunq banking API.
  • Requires appropriate API credentials configured in n8n for authentication.
  • The node uses internal helper functions to format API responses.

Troubleshooting

  • Common issues:

    • Invalid or missing Card ID will cause the request to fail.
    • Incorrect limit amount format (non-numeric or missing decimal places) may result in API errors.
    • Unsupported currency or limit type values will be rejected by the API.
    • Insufficient permissions or invalid API credentials can cause authorization errors.

  • Error messages:

    • Errors returned from the bunq API are passed through; typical messages might indicate invalid parameters or authentication failures.
    • If the node throws an error about missing required parameters, verify that all required fields (Card ID, Limit Type, Limit Amount, Currency) are correctly set.
    • Network or connectivity issues will cause request failures; ensure stable internet access and valid API endpoint configuration.

Links and References

Discussion