Submit account holder KYC by POSTing to https://api.lithic.com/v1/account_holders with a workflow of KYC_BASIC or KYC_ADVANCED and providing PII fields including first_name, last_name, dob, address, and government_id.
The API returns synchronously with a status of ACCEPTED, PENDING_REVIEW, PENDING_DOCUMENT, or REJECTED; handle each status in your onboarding flow.
If status is PENDING_DOCUMENT, collect and upload the required documents via the account holder document upload endpoint referenced in docs.lithic.com/docs/account-holders-kyc.
Monitor status transitions by subscribing to account_holder event types via the Events API (docs.lithic.com/docs/events-api) or by polling GET /v1/account_holders/{account_holder_token}.
Only account holders with ACCEPTED status may have cards created and transactions processed; gate card issuance in your application on confirmed ACCEPTED status.
In sandbox, simulate specific KYC outcomes by using test values documented in the Simulating Account Holder Creation guide at docs.lithic.com/docs/simulating-account-holder-creation.
Known gotchas
Lithic offers both KYC_BASIC and KYC_ADVANCED workflows with different data requirements; KYC_EXEMPT is available for programs that handle their own KYC — choose the correct workflow for your program type.
The account_holder token returned at creation is permanent and is the primary key for all subsequent KYC status checks and card associations.
Editing account holder PII after KYC approval may trigger a re-verification flow; consult docs.lithic.com/docs/editing-account-holder-details before building update logic.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp