@handle) is a memorable, permanent identifier for a Veil account. The use case is simple: someone wants to send you fiat by offramping from their crypto, but they don’t have your bank details — and you don’t want to share them. With a username, they pick @yourhandle as the recipient and Veil routes their offramp into your primary bank account.
How it shows up in Veil
You claim a handle in the dashboard under Settings. It’s bound to your account permanently. Handles are made of letters, numbers, and underscores; some brand and generic names are reserved.Per-mode handles
Handles are scoped per environment mode. The same handle can exist in both sandbox and production, owned by different users. Sandbox claims don’t carry over to production. See Sandbox vs. production.Rename cooldown
In production, you can rename your handle after a short waiting period. In sandbox, there is no cooldown — rename takes effect immediately so you can iterate freely.Beneficiary preview
When someone wants to offramp to your handle, their client (the dashboard, the MCP server, the CLI) looks up your handle first. The preview returns just enough to confirm the right recipient — your display name and a readiness flag. Your bank details never leave Veil. If you rename your handle or change your primary bank between the preview and the actual offramp, the sender’s transaction is rejected — what they confirmed isn’t what would have been routed. If a handle recently changed owners, Veil shows an advisory to the sender at confirmation time.See also
- Bank accounts — handle-routed offramps land in the recipient’s primary
- Offramp lifecycle — where handle routing fits
- Sandbox vs. production — why handles are per-mode