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. A tax identifier is keyed to nationality — a US national submits an SSN, for instance — and, because it depends on nationality rather than the residential country the discovery call carries, it is enforced at submit rather than listed in the discovery response. 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.

​
Verifying the person’s identity

The account holder proves their identity the same two ways a business’s control person does:
  • Conduit-hosted identity check (default) — the person completes a short hosted flow (a government-ID capture, plus a live selfie where enhanced due diligence applies). Conduit issues the link; you deliver it or let Conduit email it. Nothing to upload.
  • Uploaded verification attestation (under KYC reliance) — when your organization is enrolled in KYC reliance, you instead upload one identity verification attestation for the account holder, exported from your own identity-verification provider. Attach its id to ownership.persons[0].documentIds[]. See What You’re Verifying → Person-level evidence for what the report must contain, and the KYC reliance guide for the flow.
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

Submit an individual application step by step in Onboard a Customer → Onboarding an individual. The full response shape is the requirements reference.