Review the KYB requirements at docs.lithic.com/docs/account-holders-kyb; a business account holder requires business legal name, address, EIN, entity type, and beneficial owner information.
POST to https://api.lithic.com/v1/account_holders with workflow: KYB_BASIC or KYB_ADVANCED; include a business_entity object and a beneficial_owners array — each owner requires PII similar to individual KYC.
Parse the synchronous response status: ACCEPTED means all individuals and business data passed; PENDING_REVIEW or PENDING_DOCUMENT means further action is required.
If beneficial owners are flagged, use the account holder resubmit or document upload endpoints to submit the required identity documents for each flagged individual.
Poll or subscribe to events to detect when the business KYB status transitions to ACCEPTED before provisioning any cards or payment capabilities for the business.
In sandbox, use the test values from docs.lithic.com/docs/simulating-account-holder-creation to trigger ACCEPTED, PENDING_REVIEW, or REJECTED outcomes deterministically.
Known gotchas
Business account holders cannot be cardholders directly; you must create a user with the business as its parent account holder to issue cards for spending.
Beneficial owner threshold requirements are governed by your program configuration — consult your Lithic customer success contact for the ownership percentage thresholds applicable to your program.
A KYB_EXEMPT workflow exists for programs that manage their own business KYB externally; confirm with Lithic that this workflow is enabled for your program before using it.
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