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
Cards → Issue Card
AI-generatedOverview
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 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.
- A fintech app creates virtual cards for online purchases with preset spending limits.
- An organization controls ATM access on issued cards by toggling the ATM permission.
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 receive 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 flag indicating if the card is physical (true) or virtual (false). |
| Is Atm Allowed | Boolean flag indicating if the card can be used at ATMs. |
| Name | Optional name for the card, useful for differentiating multiple cards. |
| Delivery Address | JSON object representing the delivery address for the physical card (if applicable). |
Output
The node outputs JSON data representing the newly issued card details as returned from 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 delivery information. The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the external card issuing service.
- The node uses a base URL configured in credentials/environment variables to connect to the card issuing API.
- The node depends on the external API described in the bundled OpenAPI specification (
payhawk.api.json).
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: The monthly limit should be a positive number; invalid values might be rejected by the API.
- Network or connectivity problems: Check network access to the API endpoint and correct base URL configuration.
Links and References
- OpenAPI Specification (referenced internally as
payhawk.api.json) - General concepts of card issuing and management APIs (varies by provider)
- n8n documentation on creating custom nodes and using credentials