Airwallex logo

Create cards

Copy for LLMView as Markdown

The information within this section is relevant only for API version 2024-03-31 and later. For older API versions, see Create a card.

The Issuing Cards API provides the flexibility for creating cards tailored to fit your use case. After determining your issuing solution (see Choose your issuing solution), you can start building your integration for your business requirements.

All Airwallex cards require an associated cardholder(s). See Create cardholders.

Before you begin

Build your card integration

List and retrieve card details

The List all CardsAPI endpoint returns a subset of card fields. Each item includes only additional_cardholder_ids, brand, card_id, card_number, card_status, cardholder_id, created_at, nick_name, and updated_at — it does not include authorization_controls or metadata. To read a card's spend limits, allowed merchant categories, or metadata (for example, card-to-agent attribution), fetch each card individually with Retrieve a CardAPI.

For a view that renders many cards, fetching each card individually creates an N+1 request pattern (one list call plus one request per card), which can make the first load slow. Cache the individual card objects locally with a short time to live (for example, 30 seconds) and invalidate on any card status change, so only the first load in each window pays the per-card fetch cost.

Was this page helpful?