status
The user’s lifecycle status. It comes back on every user object, and you can filter a listing by it.
Compare status values case-insensitively. User statuses are uppercase everywhere — see State machines.
View the 5 status values
View the 5 status values
Legacy values
These three predate the current verification flow. They are still accepted as a filter and can still be returned by users created before it, so handle them if you read historical data — but no new user reaches them.type
Whether the user is a company or a person. It comes back on every user object, and you can filter a listing by it.
View the 2 type values
View the 2 type values
verification_status
The result of the user’s identity or business check. It comes back on every user object, and you can filter a listing by it.
View the 6 verification_status values
View the 6 verification_status values
verification_mode
How a business gets verified. You choose this when you create it, and it comes back on every read.
business_industry
The industries a business works in, as NAICS subsector slugs. A business takes an array of them.
View all 93 industry values
View all 93 industry values
business_type
The legal structure of a business.
View the 9 business types
View the 9 business types
Older spellings
These 10 are still accepted and mean the value beside them. Send the canonical value instead — these are kept for integrations written before it existed.language
The locale for the hosted verification form. It only matters when verification_mode is verification_link.
account_purpose
What the account will be used for.
View the 18 values
View the 18 values
A business accepts these.
A person accepts these.
source_of_funds
Where the money comes from.
View the 19 values
View the 19 values
A business accepts these.
A person accepts these.
expected_monthly_volume
How much is expected to move in a month, as a bucket.
View the 12 values
View the 12 values
A business accepts these.
A person accepts these.
expected_transaction_count
How many payments are expected in a month, as a bucket.
View the 10 values
View the 10 values
A business accepts these.
A person accepts these.
identifying_information types
What kind of record you are sending. The kind decides where its value goes: an identifier goes in number, a file goes in documents[].
View the 29 record types
View the 29 record types
Government photo IDs. Send the number in
number and the images in documents[]. Every one of these needs a front and a back, except passport and visa.Tax and identity numbers. Send the value in
number. No file needed. tax_id is accepted on the business itself, not on an associated person.Documents. Attach the file in
documents[].Business documents. Also attached in
documents[], and only valid on a business.documents types
What a file is within the record it belongs to. Three of these are the images of an identity document; the rest are supporting paperwork.
View the 12 supporting documents
View the 12 supporting documents
missing_fields instead of uploading the whole set.
liveness subject
Who a liveness link is for. A business gets one link per beneficial owner, so you need this to route them.
liveness code
Why a liveness link could not be minted. It comes back on the 422, and it is what to branch on.
View the 8 liveness codes
View the 8 liveness codes
verification_link_error_severity
Whether the note in verification_link_error asks anything of you. The two always arrive together.
unsupported_reason
Why a product is closed to a user when no data can change it. It replaces that product’s missing_fields — the two never appear together.
employment_status
What the person does for a living.
View the 5 employment_status values
View the 5 employment_status values