Cards

nuez can issue virtual debit cards. Cards don’t spend directly from the wallet balance — they draw from a separate card account balance that you fund explicitly.

Card account

Every user has at most one card account, provisioned separately from wallet onboarding. Check its status with get_card_account_status (MCP):

{ "onboard_status": "active", "balance_ars": 45000, "active_cards_count": 2 }

Funding and withdrawing

Move ARS between the wallet CVU and the card account balance — both directions go through the bank rail and require an idempotency_key:

fund_card_account — wallet → card account
withdraw_card_account — card account → wallet

Issuing a card

issue_card takes limit_ars (debited from the card account balance immediately), an optional label, and disable_after_first_use (defaults to true — cards are single-use unless you explicitly pass false for a reusable/multi-use card).

{ "card_id": "3f2a...", "last_four": "4242", "status": "active", "limit_ars": 5000 }

Cancelling

cancel_card disables the card and refunds limit_ars - spent_ars back to the card account balance.

Viewing sensitive data (PAN/CVV)

get_card_secure_token returns a short-lived, single-use iframe URL to a hosted widget that displays the card number, CVV, and expiry. Never try to extract or store PAN/CVV yourself — always render this URL in a browser or webview for the human to view.

Transactions

list_card_transactions returns settled, pending, and rejected authorizations, either for one card (card_id) or across all of a user’s cards.

MCP tools

See the full parameter reference at MCP tools → Cards. REST equivalents exist under /v1/cards/* for the same operations if you’re not using MCP.