Roles

Account Holders qualify for all Authorized Signer and Authorized User use-cases. Authorized Signers qualify for all Authorized User use-cases. 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, you may observe the role_details parameter of the GET entity request. Allowed roles:

Account Holder: Entity with full control and legal responsibility for the account.
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 1 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 for the entity to be created. 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 the entity is also listed as an Account Holder for the Account under which the card is provisioned.

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 the entity is also listed as an Authorized User for the Account under which the card is provisioned.

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 - Control person(s)⁵ and title of control person(s) - Applicable beneficial owner(s)⁵	- 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 - Sole proprietor(s)⁶

^{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 is 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.}

Foundations

API Guides

Role Use Cases

Data Requirements

​Role Use Cases

​Data Requirements

Role Use Cases

Data Requirements