Update a user
Changes an existing user. Only the fields you send are written — everything else is left alone.
Use it to fill in what missing_fields still asks for.
A missing file works differently: sending other fields will not clear it. You have to send the file itself again in identifying_information[].documents[].
Touching a field the user’s category needs for verification starts the check again and the response says requires_reverification: true. A successful change emits a user.updated webhook (see Webhooks).
Authorizations
The data.access_token value from Get access token.
Headers
Version applied to this request. It wins over your account's pinned version — see Versioning.
"2026-04-14"
Body
address_country, formation_country, document_country, residential_address.country, and the address and document country fields in associated_persons[] take an ISO 3166-1 alpha-3 code.
How the user gets verified.
See User values for the accepted values.
automatic, verification_link The legal structure of the business.
See User values for the accepted values.
Accepted here, but not returned in the user object.
The industry the business works in, as a NAICS subsector slug — telecommunications, real_estate, construction_of_buildings.
See User values for the accepted values. Send one industry. A second is refused with a 400.
Accepted here, but not returned in the user object.
1Where the money comes from.
See User values for the accepted values.
Accepted here, but not returned in the user object.
What the account will be used for.
See User values for the accepted values.
Accepted here, but not returned in the user object.
How much is expected in payments in a month, as a bucket.
A business takes the business buckets in User values. Any other value for a business is refused with a 400.
How much is expected to move in a month.
See User values for the accepted values.
less_than_10000, 10000_to_49999, 50000_to_199999, 200000_to_999999, 1000000_or_more, less_than_50000, 50000_to_100000, 100000_to_500000, 500000_to_1000000, 1000000_to_5000000, 5000000_to_10000000, more_than_10000000 How many payments are expected in a month.
See User values for the accepted values.
1_to_10, 11_to_50, 51_to_200, more_than_200, less_than_10, 10_to_25, 26_to_50, 51_to_100, 101_to_500, more_than_500 What the person does for a living.
See User values for the accepted values.
employed, self_employed, unemployed, retired, student The person's occupation, as free text or a code. See User values for the accepted codes.
Response
The change was applied. updated_fields says what was written.
The user after the change, plus what the change did.
Whether the user is a company or a person.
Available options: business, individual.
See User values for what each one means.
Where the user sits in its lifecycle.
Available options: CREATED, VERIFYING, REVIEW, VERIFIED, REJECTED, plus the legacy ACTIVE, INACTIVE and SUSPENDED.
See User values for what each one means.
The result of the user's identity or business check.
Available options: unverified, started, in_review, verified, rejected, needs_action.
See User values for what each one means.
Whether the note in verification_link_error asks anything of you.
See User values for what each value means.
deferred, failed What this user can already use, product by product.
Each entry carries eligible, and when that is false, the reason why:
missing_fields— data is missing. Send it, and the product turns eligible once the user passes verification.unsupported_reason— nothing you send will change the answer.
A product stays eligible: false until the user reaches the status that product asks for. That status is VERIFIED.