Skip to main content
Conduit onboards two kinds of customer. The default is a business — a legal entity, with the people behind it. The other is an individual — a natural person opening an account in their own name, not on behalf of a company. The rest of this section (the country pages, the coverage map, the matrix) is the business reference; this page is the individual counterpart. You never learn these areas to integrate. The requirements endpoint returns the exact fields and documents to collect. This page is the background: what a person owes, and where an individual application differs from a business one.

​
Telling Conduit the subject is a person

Both the requirements endpoint and the submit endpoint take an optional subjectType. Send individual to onboard a natural person:
Omitting subjectType means a business — permanently. It is not a temporary default: an application that never sends the parameter is a business onboarding, and always will be. A business integration that predates individual support needs no change.

​
What an individual owes

An individual application names exactly one person — the account holder — under ownership.persons[], with the role ACCOUNT_HOLDER. That person carries the same identity fields a business’s control person does: legal name, date of birth, nationality, and residential address. The account holder also sends the expiry date of the identity document your provider verified, and that date must not be in the past. A tax identifier is owed by a US national wherever they live (an SSN) and by anyone who lives in the United States (an SSN or an ITIN). The discovery response lists it as required when the residential country is the US, and as a requirement conditional on nationality otherwise. Each time, it lists the tax id types it accepts. Alongside those identity fields, an individual sends two things a business collects at the entity level:
  • Activity and due-diligence descriptors — an activity object: the account holder’s occupation, the purpose of the account, source of funds, expected monthly volume and transaction count, and the countries they transact with. The requirements response lists which apply. The purpose, source of funds, volume, transaction count and countries carry closed sets of accepted values; occupation and the optional employer name are free text.
  • Consent — a certification.termsAndConditions acknowledgement.
An individual application carries no business envelopes — no businessInfo, registeredAddress, operatingAddress, companyClassification, businessActivity, compliance, or relatedCompany. The subject is a person, not a company, so sending any of them is rejected, and the requirements response for an individual never lists them.

​
Phone number

Send the account holder’s phoneNumber in E.164 format, for example +14155551234. A national number is also accepted when the person’s address.country can complete it, for example (408) 555-0166 for a person who lives in the US. The customer reads the number back as you sent it. A number that cannot be read for that country returns 422 ONBOARDING_NOT_READY with errors[].pointer /ownership/persons/0/phoneNumber and the detail “Phone Number is not a valid phone number for USA. Send it in international format, for example +14155551234.”

​
Verifying the person’s identity

Individual onboarding must be enabled for your organization. Contact your Conduit account manager. You verify the account holder with your own identity-verification provider and upload one identity verification attestation for them; attach its id to ownership.persons[0].documentIds[]. See What You’re Verifying → Person-level evidence for what the report must contain, and Upload each person’s attestation for the upload call. There is no Conduit-hosted identity check for an individual: Conduit issues the person no verification link. If individual onboarding is not enabled for your organization, both the requirements call and the submit call return 422 SUBJECT_REQUIREMENTS_NOT_AVAILABLE. Do not retry. Contact your Conduit account manager. Where enhanced due diligence applies, two more requirements appear, at different levels. A proof-of-address document is listed on the account holder’s individualRequirements[] row — attach it to ownership.persons[0].documentIds[]. Enhanced financial evidence is a customer-level requirement: the top-level documents[] checklist carries a bank-statement row with its own minCount — three months of statements where individual enhanced due diligence applies — so attach that many document ids to the top-level documentIds[], not to the person. (The top-level minDocuments is only the floor of one document; the row’s own minCount is the count that matters here.)

​
Next

Run the whole individual path in sandbox, with real requests and responses, in the Individual quickstart. Submit an individual application step by step in Onboard a Customer → Onboarding an individual. The full response shape is the requirements reference.