Basic Capital requires identity verification (IDV) for companies, trustees, and employees. Users must go through IDV as a first step before meaningfully interacting with the platform, including via a white-labeled experience.
Basic Capital integrates with Footprint as our default Identity Provider (IdP). However, if partners perform their own IDV and are able to provide us with the requisite data, we can instead pull this data directly during onboarding.
If you support IDV for only some of these entities (e.g., for businesses, but not persons), we support using a mix of providers. This provides as seamless an experience as possible for the user when onboarding onto Basic Capital.
The administrator setting up the account should go through KYB as a first step. This administrator does not need to be the plan trustee, who will carry individual fiduciary responsibility and must go through IDV separately.
We require the following data (field names can vary by provider):
| Field | Type | Required |
|---|---|---|
business_name | string | yes |
business_phone | string | yes |
company_address | Address | yes |
entity_type | C_CORPS_CORPLLCSOLE_PROPRIETORSHIPLLPNON_PROFITPARTNERSHIPELECTING_CHURCHOTHER | yes |
ein | string | yes |
state_of_organization | string; US state of operation for the company | optional |
Note: If
entity_type = OTHER, we require companies to contact our operations team to proceed with plan configuration, as we will need to confirm that this company is eligible to provide a 401(k).
Both trustees and employees must go through KYC before making elections or signing documents.
Note: Employees who are auto-enrolled into a 401(k) or carry a balance from a previous record keeper do not have to go through KYC in order for Basic Capital to receive their funds; however, it is required in order to set contributions, including if an employee wants to set their contribution rate to 0%. Employees who never set up their account will have their funds invested into the employer-selected QDIA for their age group.
We require the following data for KYC, for both trustees and employees:
| Field | Type | Required |
|---|---|---|
given_name | string | yes |
surname | string | yes |
full_name | string | yes |
email | string | yes |
date_of_birth | Date | yes |
ssn | string | yes |
document | IdentificationDocument | yes |
marital_status | SINGLEMARRIEDSEPARATEDDIVORCEWIDOWED | optional; defaults to SINGLE where a vendor requires it |
IdentificationDocument
| Field | Type | Required |
|---|---|---|
document | PassportStateIssuedDocument | yes |
document_number | string | yes |
citizenship | string | optional; recommended for non-US citizens |
Passport
| Field | Type | Required |
|---|---|---|
document | Blob | yes |
StateIssuedDocument
| Field | Type | Required |
|---|---|---|
type | DRIVERS_LICENSEGOVERNMENT_ID | yes |
document_front | Blob | yes |
document_back | Blob | yes |
state | string | yes |
If you do not fully support the required IDV, you can embed Footprint directly as part of the onboarding flow. This can then be connected directly to our API:
We require persons in our platform to have unique SSNs. If an employee has an existing account at Basic Capital associated with an IRA or a previous 401(k), they will need to link their new 401(k) to their existing account in order to complete KYC.
Note that this is a requirement for users in our member app, not for admins. Trustees and auto-enrolled employees who have never claimed their account will not be affected.
See Employee account linking for complete documentation.