The business
Identified by its registration: legal name, formation country and date, address, a tax identifier, and the number it is registered under. For a US company, that number is the Secretary of State filing number, sent as acompany_registration_number record. The EIN is the tax identifier and cannot stand in for it. Its trading profile is part of the check too — industry, purpose, expected volumes — because those are what the check is assessed against.
The value sets for each of those fields are in User values.
The people tied to it
Each person you list is checked in their own right, with their own identity details and documents. A business is not verified until they are. Who has to be listed is a rule about the business, not about any one person. When someone required is missing,missing_fields names them.
What the API gives you back
missing_fields is the one to build on. It is machine-readable, it names the field rather than describing it, and it is what you show to whoever can supply it — usually your own customer.
Tokens that do not always block
Most tokens inmissing_fields hold the user back. Verification does not start while one is outstanding. A few tokens only inform, either always or once the user is VERIFIED. Once the user is VERIFIED, read eligible on a product’s entry in eligible_products to know whether that product is open.
Never blocking. These are listed so you can complete the record. They never stop verification or a product.
Blocking until verified. Before the user is
VERIFIED, these hold verification back like any other gap. After that they can still be listed. A product can still count one, so read its eligible.
View the 20 tokens
View the 20 tokens
associated_persons:director_appointment_date, associated_persons:representing_start_date and associated_persons:tax_residence_country are listed only for the account product that asks for them. They never hold verification back, and once the user is VERIFIED they only inform.
Required documents
What has to be attached, and how.