Certain updates on Entity trigger KYC re-screening, requiring an updated kyc_details.result and kyc_details.screened_at.
For individual entities, KYC re-screening is triggered by changes to: first name, last name, date of birth, tax ID (for US entities), existing identification document (for non-US entities), existing physical address, and switching between US vs. non-US entities.
For business and sole proprietorship entities, KYC re-screening is triggered by changes to: business name, business type, tax ID (US entities), existing identification document (non-US entities), and existing physical address.
Note: Business and sole proprietors cannot switch between US and non-US entities. A new entity must be created in such case.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Idempotency key
255Entity ID
Type of entity = individual.
^individual$The entity's intended role. Lead highly recommends using this field to confirm data requirements for different roles to minimize errors later. In the event more than 1 role is passed in and at least 1 role doesn’t pass validation, the request will not succeed. It will be an all or nothing behavior. Lead currently supports:
authorized_user: Individual entity with restricted access to the account, without legal responsibility. Only applies to individual entity.authorized_signer: Individual entity allowed to sign on behalf of the account holder, without legal responsibility. Only applies to individual entity.account_holder: Entity with full control and legal responsibility for the account. Applies to all entity types.authorized_user, authorized_signer, account_holder "Possible values: authorized_user, authorized_signer, account_holder. In the event more than 1 role is passed in and at least 1 role doesn’t pass validation, the request will not succeed. It will be an all or nothing behavior. For type = business, sole_prop, only account_holder should be provided"
The entity's risk score, mapped to Lead by the client. Client should have provided risk score mapping to Lead.
low, medium, high Details for the individual entity
Details on OFAC on the entity.
Details on KYC on the entity.
A set of key-value pairs that can be used to store additional information related to this object.
Entity object updated.
Unique ID for the Entity object.
Timestamp at which the entity object is created.
Timestamp at which the entity object was last updated.
Type of entity = individual.
^individual$Client customer ID for the entity object. Limit of 64 characters.
64The entity's intended role. Lead highly recommends using this field to confirm data requirements for different roles to minimize errors later. In the event more than 1 role is passed in and at least 1 role doesn’t pass validation, the request will not succeed. It will be an all or nothing behavior. Lead currently supports:
authorized_user: Individual entity with restricted access to the account, without legal responsibility. Only applies to individual entity.authorized_signer: Individual entity allowed to sign on behalf of the account holder, without legal responsibility. Only applies to individual entity.account_holder: Entity with full control and legal responsibility for the account. Applies to all entity types.authorized_user, authorized_signer, account_holder "Possible values: authorized_user, authorized_signer, account_holder. In the event more than 1 role is passed in and at least 1 role doesn’t pass validation, the request will not succeed. It will be an all or nothing behavior. For type = business, sole_prop, only account_holder should be provided"
The entity's risk score, mapped to Lead by the client. Client should have provided risk score mapping to Lead.
low, medium, high Details for the individual entity
Details on OFAC on the entity.
Details on KYC on the entity.
A set of key-value pairs that can be used to store additional information related to this object.