Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses 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 payment 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 scenarios where businesses or individuals want to programmatically manage card issuance for employees, customers, or themselves, enabling control over spending and card type.
Practical examples:
- A company issuing physical cards to employees with predefined monthly limits.
- Creating virtual cards for online purchases with restricted ATM access.
- Automating card issuance workflows integrated into financial platforms or CRMs.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the card will be issued. |
| User Id | Unique identifier of the cardholder (the user who will own the card). |
| Fund Account Id | Unique identifier of the fund account that backs the card's spending. |
| 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 (true) or not (false). |
| Name | Optional name for the card, useful for differentiating multiple cards. |
| Delivery Address | Optional JSON object representing the delivery address for the physical card. |
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 output may also include shipping or delivery information. The node does not explicitly handle binary data output.
Dependencies
- Requires an API key credential for authenticating requests to the external card issuing service.
- The base URL for the API must be configured in the node credentials.
- The node depends on the external card issuing platform’s API to perform the card creation.
Troubleshooting
- Missing required fields: Ensure all required properties such as Account Id, User Id, Fund Account Id, Limit, Is Physical, and 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 or authentication token is correctly configured and has sufficient permissions.
- Limit value issues: Setting a zero or negative limit might be rejected by the API; use appropriate positive numbers.
- Network or connectivity problems: Check network access to the API endpoint and correct base URL configuration.
Links and References
- Refer to your card issuing service’s official API documentation for detailed information on card issuance parameters and responses.
- n8n documentation on creating custom nodes and handling API credentials.