Verification Status
Verification state for the request's active account: whether a valid payment method is on file, and the account's identity-verification (KYC) status. The platform's verification gates (UDP tunnels, dedicated IPs, custom domains, dedicated ports) read these flags to decide whether to allow an action.
Verification is account-scoped — we bill accounts and gate account-scoped resources, so both payment method and KYC live on the account, not the individual user. Use this on app load to know which gates the account has cleared and surface "add a payment method" or "verify your identity" prompts before hitting a 403 from a gated endpoint.
Response (200 OK)
true if at least one un-expired card or other payment instrument is on file for the account's Stripe customer. Required for paid-tier upgrades and certain feature gates.none (default — no KYC submitted), pending (submitted / under review), verified, rejected. KYC is required only for high-trust gates (e.g. dedicated IPs in restricted regions).kyc_status is verified.KYC documents
Identity verification is document-driven: an admin defines which documents the account must submit, and the account uploads each. This lists the account's documents — { documents: [{ uuid, doc_type, label, status, file_name, submitted_at, reviewed_at, review_notes }] }. doc_type is one of government_id, proof_of_address, business_registration, other; status is requested → submitted → approved/rejected. The file bytes are never returned. Uploading a document is done from the dashboard verification page (multipart), not via the public API.
Errors
billing:update on the active account.