Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation issues a new card linked to a specified account and fund account for a particular user. It allows configuring key card attributes such as whether the card is physical or virtual, ATM usage permissions, spending limits, and delivery address details. This operation is useful in financial platforms or expense management systems where automated card issuance is required, for example, issuing employee cards with predefined monthly limits or creating virtual cards for online purchases.

Properties

Name Meaning
Account Id Identifier of the account to which the card will be issued.
User Id Unique identifier of the cardholder (user) who will own the card.
Fund Account Id Unique identifier of the fund account that the card is linked to.
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 JSON object representing the delivery address for the physical card.

Output

The node outputs JSON data representing the newly issued card's details as returned by the API. This typically includes identifiers, status, limits, and other metadata about the card. The output does not explicitly mention binary data, so it is assumed to be purely JSON structured information.

Dependencies

  • Requires an API key credential for authenticating requests to the external card issuing service.
  • The node uses HTTP requests configured with JSON content type and expects JSON responses.
  • The base URL for the API must be configured in the node credentials or environment settings.

Troubleshooting

  • Missing Required Fields: Errors may occur if mandatory fields like Account Id, User Id, Fund Account Id, Limit, Is Physical, or Is Atm Allowed are not provided. Ensure all required inputs are filled.
  • Invalid JSON in Delivery Address: If the delivery address JSON is malformed, the request will fail. Validate JSON syntax before input.
  • API Authentication Failures: Check that the API key or authentication token is correctly configured and has necessary permissions.
  • Limit Value Issues: Providing a non-numeric or negative value for the limit may cause errors; ensure the limit is a valid positive number.
  • Network or API Endpoint Errors: Verify network connectivity and that the API base URL is correct.

Links and References

  • No direct links available from the source code. For more information, consult the documentation of the external card issuing API integrated with this node.

Discussion