Entity Roles

Roles govern which financial products an entity can use. Account Holders qualify for all Authorized Signer and Authorized User use cases. Authorized Signers qualify for all Authorized User use cases. Minor Account Holders qualify for all Authorized User use cases but are not eligible for the Authorized Signer role. To ensure that an entity meets role requirements during a Create or Update entity request, you must pass the intended_roles parameter. To check role eligibility for an entity, observe the role_details parameter of the GET entity request. Allowed roles:

Account Holder: Entity with full control and legal responsibility for the account.
Minor Account Holder: Individual aged 16–17 with full control of the account. Has the same requirements as the Account Holder role, except the minimum age. Only applies to individual entities.
Authorized Signer: Individual authorized to sign on behalf of the account holder, without legal responsibility. Common for business accounts.
Authorized User: Individual with restricted account access, without legal responsibility.

An entity may be eligible for more than one role. In this case, you can specify multiple roles in intended_roles (e.g., authorized signer, account holder) when creating an entity. However, all roles included in intended_roles must successfully pass validation before Lead creates the entity. See the next sections for more details on types of entities and how to use intended_roles and data requirements on intended roles.

Role Use Cases

Account Holder Role

Necessary for provisioning and using Account Numbers.
Necessary for designating an entity as an account_holder in the Account file.
Allows for provisioning Cards to an entity — if you also list the entity as an Account Holder for the Account under which you provision the card.

Minor Account Holder Role

Necessary for provisioning and using Account Numbers for individuals aged 16–17.
Applies to individual entities aged 16–17 who otherwise meet Account Holder eligibility requirements. Businesses and sole proprietorships cannot hold this role.
When the entity turns 18, role eligibility transitions automatically from minor_account_holder to account_holder. Lead computes role eligibility against the entity’s date of birth and the current date, so no action is required.
An account whose only account holders are Minor Account Holders cannot use the credit_with_underwriting capability. See Accounts API Validation Rules.
Supported through the API only. minor_account_holder is not supported in file integrations.

Program Availability. The minor_account_holder role is available only to programs approved for minor account holder support. Approving a program is subject to review and approval by Lead teams, including review of the program’s intended audience, monitoring, and product controls for minors. Contact your Lead Technical Account Manager to request enablement for your program.

Minor Account Holders can receive funds on all rails and originate ACH and instant payments, but cannot send wires or blockchain transfers. Programs are responsible for enforcing these restrictions in their product experience as a condition of enablement.

Authorized Signer Role

Necessary for listing an entity as a beneficial owner or control person for a business entity.
Necessary for designating an entity as an authorized_signer in the Account file.

Authorized User Role

Necessary for designating an entity as an authorized_user in the Account file.
Allows for provisioning Cards to an entity — if you also list the entity as an Authorized User for the Account under which you provision the card.

Data Requirements

	Individual	Business	Sole Proprietorship
Authorized User	- First name - Last name - Contact method (email or phone number)	N/A	N/A
Authorized Signer	- First name - Last name - Contact method (email or phone number) - Physical address³ - Date of birth (18 or older) - Government verified identification⁴ - OFAC passed & valid - KYC passed & valid	N/A	N/A
Account Holder	- First name - Last name - Contact method (email or phone number) - Physical address³ - Date of birth (18 or older) - Government verified identification⁴ - OFAC passed & valid - KYC passed & valid - Risk score	- Business name - Business type - Business industry - Contact method (email or phone number) - Government verified identification⁴ - Physical address³ - KYC passed & valid - OFAC passed & valid - Risk score - One or more control persons⁵ and their titles - One or more applicable beneficial owners⁵	- Business name - Business type - Business industry - Contact method (email or phone number) - Government verified identification⁴ - Physical address³ - KYC passed & valid - OFAC passed & valid - Risk score - One or more sole proprietors⁶
Minor Account Holder	- First name - Last name - Contact method (email or phone number) - Physical address³ - Date of birth (16 or 17) - Government verified identification⁴ - OFAC passed & valid - KYC passed & valid - Risk score	N/A	N/A

Minor Account Holder requirements are identical to the Account Holder requirements except for the date-of-birth window. Individuals 18 or older are not eligible for minor_account_holder — use account_holder instead. Individuals under 16 are not eligible for any account holder role.

^{1. An entity is a US entity if they have a US tax identification number.}
^{2. Full KYC means name, date of birth (applies to individual entity only), physical address, government verified id.}
^{3. Address must not be registered agent address, PO box or in prohibited countries.}
^{4. For a government verified identification, if the entity is a US entity, it must be a tax ID. Otherwise, for a non-US entity, other forms of government verified identification are required.}
^{5. Data requirements for beneficial owners/control persons match those of authorized_signer roles. You are expected to capture and submit accurate beneficial ownership data; however, in instances with no beneficial owners, an empty array is a valid submission.}
^{6. Data requirements for sole proprietors match those of authorized_signer roles.}

Banking Infrastructure

Funding & Settlement

Payment Rails

Customers & Accounts

Role Use Cases

Data Requirements

​Role Use Cases

​Data Requirements

Role Use Cases

Data Requirements