Wallet & CVU

What is a CVU?

A CVU (Clave Virtual Uniforme) is a 22-digit identifier for virtual accounts in Argentina’s financial system. It works exactly like a CBU — you can receive transfers from any Argentine bank, Mercado Pago, or Ualá using your CVU.

Every nuez user gets a CVU once onboarding (KYC) is complete. This is the address you fund your wallet from.

Funding your wallet

Transfer any amount to your CVU from any Argentine bank or wallet. Funds are detected via an incoming bank-rail webhook and fire a deposit.detected event on your configured webhook — see Webhooks.

Retrieve your CVU with:

• MCP: get_cvu
• REST: GET /v1/cvu

Balance

Your wallet has a single ARS balance, held on the bank rail and looked up live on every GET /v1/balance / get_balance call — nuez does not cache or extend credit. If the balance is insufficient when a payout is submitted, the rail rejects it and the payout attempt moves to failed.

{ "asset": "ARS", "available": "125430.50" }

Check balance via:

• MCP: get_balance
• REST API: GET /v1/balance
• Recent incoming transfers: GET /v1/deposits or list_recent_deposits

Onboarding gate

Both GET /v1/balance and GET /v1/cvu return 422 ONBOARDING_INCOMPLETE until the user has a linked bank-rail account (i.e. onboarding has been submitted). POST /v1/withdraws and request_payout additionally require user.CVU to be assigned, and the policy engine’s first rule denies any payout while onboarding != "done".

Multiple API keys, one wallet

Multiple API keys can belong to the same user and all draw from the same wallet balance — there’s no per-key sub-wallet. What differs per key is the audit trail: every payout attempt records the api_key_id and api_key_name that created it, and that same identifier is included in outgoing webhook payloads (buildPayoutEventData). Thresholds, however, are per user, not per key — see Policy engine.