KYC (“Know Your Customer”) is the identity verification step every Veil user completes before they can offramp. Veil delegates the verification itself to a regulated banking partner via a hosted form — Veil never sees your government ID directly.Documentation Index
Fetch the complete documentation index at: https://docs.useveil.co/llms.txt
Use this file to discover all available pages before exploring further.
How it shows up in Veil
When you start KYC, Veil opens the partner’s hosted form in a new browser tab. You upload a government ID and a selfie; verification runs in the background and updates your status in Veil when complete. You can check your status at any time from Veil or via the API. Most approvals are quick, but some take longer when a document needs a second look or the name on the ID doesn’t match the account — in those cases you’ll be asked to re-submit.Two identities per user
Veil verifies you separately in each environment. Individuals only run KYC once — they live in production. Developers typically do it twice: once in sandbox during signup (synthetic data is accepted), and again against real documents when graduating to live. See Sandbox vs. production.Why it matters
KYC is the gate for moving money in Veil. You cannot offramp until your KYC is approved in the mode you’re operating in. Individuals complete KYC during onboarding before reaching the dashboard; developers complete sandbox KYC during signup and production KYC later via the Go-Live flow.See also
- Sandbox vs. production — why developers KYC twice
- Bank accounts — adding payout details after KYC