Issue a personalized consumer card via Airwallex Issuing using the v2024-03-31+ program object
domain: airwallex.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Onboard the recipient as an Individual (not Business) type customer via Airwallex's connected-accounts/BaaS onboarding before creating the cardholder
Create an INDIVIDUAL type cardholder (with address nested under the individual object, not top-level) and wait for cardholder status to reach READY
Call Create a card with program.purpose set to CONSUMER, program.type (e.g. CREDIT, DEBIT, or PREPAID), and is_personalized set to true
Pass cardholder_id from the Create a Cardholder response so the card is linked to that INDIVIDUAL cardholder
Set authorization_controls.allowed_transaction_count (SINGLE or MULTIPLE) and transaction_limits before activating the card for spend
Known gotchas
Do not send the legacy issue_to: ORGANISATION/INDIVIDUAL field or a top-level primary_contact_details object — both were replaced by the program object plus is_personalized/cardholder_id in API version 2024-03-31 and later
Consumer cards can only be issued to INDIVIDUAL-type cardholders and only as personalized cards (is_personalized: true) — a DELEGATE cardholder cannot be used with program.purpose: CONSUMER
The card and cardholder response shapes changed materially at 2024-03-31 (e.g. address moved under individual.address) — verify your SDK/client version matches, since older auto-generated clients may still model the pre-2024-03-31 shape
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?