Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation, Issue Card, allows users to create and issue a new card linked to a specific account and fund account. It supports both physical and virtual cards, with configurable monthly spending limits and ATM usage permissions. This is useful in financial platforms or expense management systems where issuing controlled payment cards to users (cardholders) is required.
Practical examples:
- A company issues physical debit cards to employees for business expenses, setting monthly limits and enabling ATM withdrawals.
- A fintech app issues virtual cards instantly for online purchases, disabling ATM use.
- Managing multiple cards per user with distinct names and delivery addresses.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the card will be linked. |
| User Id | Unique identifier of the cardholder who will own the card. |
| Fund Account Id | Unique identifier of the fund account that backs the card's funds. |
| Limit | Recurring monthly spending limit set on the card. |
| Is Physical | Boolean indicating if the card is physical (true) or virtual (false). |
| Is Atm Allowed | Boolean indicating if the card can be used at ATMs. |
| Name | Optional name for the card to help differentiate it from others. |
| Delivery Address | Optional JSON object representing the address where the physical card should be delivered. |
Output
The node outputs JSON data representing the newly issued card details as returned by the API. This typically includes card identifiers, status, limits, type (physical/virtual), and other metadata related to the issued card.
If the card is physical, the delivery address information may also be part of the output.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating requests to the external card issuing service.
- The node uses a base URL configured in credentials to send HTTP requests.
- The node depends on the external card issuing API to create and manage cards.
Troubleshooting
- Missing required fields: Ensure all required properties (Account Id, User Id, Fund Account Id, Limit, Is Physical, Is Atm Allowed) are provided; otherwise, the API call will fail.
- Invalid JSON in Delivery Address: If providing a delivery address, ensure it is valid JSON; parsing errors will cause failures.
- API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Limit value issues: Setting a zero or negative limit might be rejected by the API; confirm acceptable values.
- Network or API errors: Check connectivity and API endpoint availability if requests time out or return errors.
Links and References
- Refer to your card issuing service’s official API documentation for detailed field descriptions and constraints.
- n8n documentation on creating custom nodes and handling API credentials.