The evidence areas
Legal Registration
The business is legally registered with the relevant national or sub-national registry. Establishes legal existence, registration number, and date of incorporation.Constitutive Documents
The instrument that brings the business into existence and governs how it operates: name, registered address, share capital, governance rules. Sometimes a single document (South African MOI, Ghanaian Constitution); sometimes a paired set (Memorandum + Articles in common-law jurisdictions; Escritura + Estatutos in Hispanophone Latin America).Tax Registration
The business is registered with the national tax authority. The local artifact is typically a tax-ID certificate (CNPJ in Brazil, RFC in Mexico, EIN letter in the US, UTR notice in the UK, etc.).Operating Permit
The business has the general municipal or national permit to do business at its registered location. This is the local-government permit (Alvará, Patente, Licencia de Funcionamiento, Trade License, Patente Municipal) — not a sector-specific regulatory license. Some jurisdictions (UK, Singapore) issue no general operating permit; only sector-specific licensing applies.Sector-Specific License
The business is authorized to operate in a regulated sector — financial services, insurance, healthcare, telecom, etc. Only collected when your customer operates in a regulated sector (banks, broker-dealers, insurers, healthcare providers, MSBs, payment institutions). The issuing authority varies by sector and country (BCB / CVM / SUSEP in Brazil; FCA / PRA in the UK; SEC / FinCEN / OCC / state regulators in the US; BaFin in Germany).Ownership Records
The current equity owners (shareholders, members, partners) and any beneficial owners above the local disclosure threshold. The local artifact varies widely: corporate share registers (Stock Ledger, Libro de Acciones), members’ lists (Quadro Societário, Companies House PSC Register), beneficial-owner declarations (post-AMLD5 / FinCEN BOI / RBE / Transparenzregister). The per-country page tells you what to collect.Governance Records
The current board of directors and equivalent governance figures (managers, officers). Sometimes embedded in commercial-registry extracts (CR 12 in Kenya, CoR 39 in South Africa, Extrait RCCM across OHADA states); sometimes filed separately (Annual Report, Statement of Information, Acta de Designación).Signing Authority
An instrument evidencing that the person executing your agreement is authorized to bind the company. Conduit accepts a board resolution, notarized power of attorney, personería certificate, or other equivalent (acta de directorio, PV de Conseil, Vigencia de Poder, Imza Sirküleri, written resolution under CA 2006 s.288).Operating Address
Evidence of the business’s operating address — a utility bill, bank statement or invoice dated within the last 90 days. A lease can be older when a recent document shows the same address.Entity documents that are not country documents
The nine areas above are satisfied by a local artifact, so each country page names the one to collect. Two further documents are the same everywhere, because no registry issues them. One the business draws up itself; the other comes from its auditor, and a self-prepared account summary does not stand in for it. They are requested for some onboardings and not others, andGET /v2/onboarding/requirements is what tells you which applies to your customer.
Organizational structure chart (ORG_STRUCTURE_CHART)
A diagram or document showing the ownership and control hierarchy: parent and subsidiary relationships, and the ultimate beneficial owners above the entity you are onboarding. Upload it as a PDF, JPEG or PNG, like every other document.
Financial evidence (AUDITED_FINANCIAL_STATEMENT or BANK_STATEMENT)
Either an audited financial statement for the most recent fiscal year — audited by an independent accountant, not prepared in-house — or three consecutive recent monthly statements for the entity’s operating bank account. The requirements response returns the two as one alternative group — satisfy one branch, not both.
Upload each document once. Submission takes one flat list of document IDs, and Conduit can recognise a single file as more than one kind of evidence: a bank statement that also shows the entity’s address satisfies both the financial-evidence group and the operating-address area, with no second upload.
Person-level evidence
The nine country-document areas above cover the business entity. Identity verification for a business’s control persons is handled separately, either through a Conduit-hosted identity flow or through a report you upload from your own provider. The same person-level evidence applies to an individual (natural-person) customer, where the account holder is the one person who verifies — see Onboarding an Individual.Identity verification (identity_verification)
A government-issued identity document — passport, national ID card, driver’s license. When Conduit runs per-person identity verification on your behalf, the hosted flow collects it. When your organization verifies identities with its own provider, upload the document the provider verified, together with the attestation below: the front, and the back as a second file if the document has one. Upload a scan or photo of the document itself: a page that only types out its details does not count as the ID. Attach it at ownership.persons[i].documentIds[].
Identity verification attestation (identity_verification_attestation)
A structured report exported from your own KYC/IDV provider confirming that a named individual has been verified. Required for the account holder of an individual, or each control person of a business, when your organization verifies identities with its own provider, as set up with your Conduit account manager.
This document type is distinct from a raw government ID (identity_verification). An attestation is a provider-issued verification report, not the identity document itself, so you upload the original ID as well. ID images embedded in the report do not count as the original ID. The report must contain: the provider’s name, the person’s full legal name, a verification result (verified / approved / clear / pass or equivalent), a verification reference or case ID, and a completion date printed with a label, for example Verification date: 2026-10-01. The person data must not carry test markers such as ZZZTEST. One file per person; the name and date of birth in the report must match what was submitted in the onboarding request. The completion date must be within the last 12 months at review; an older report is asked again. On an individual application, send the same date in identityVerificationDate so that the review does not depend on reading it from the report.
Attestations are attached at ownership.persons[i].documentIds[], not in the top-level documentIds[] array. See the KYC reliance integration guide for the full submission flow.
Enhanced due diligence evidence (EDD_EVIDENCE)
One document that shows where an individual’s funds or wealth come from: a payslip or employment letter, a tax return, documents for the sale of an asset or an inheritance, or a bank statement. Required of the account holder of an individual when the requirements response lists it, and when the application’s own answers make enhanced due diligence apply, which the requirements response does not show in advance. Upload it with type=EDD_EVIDENCE and an eddEvidenceKind, and attach it at ownership.persons[0].documentIds[]. See Enhanced due diligence for the kinds and how recent each must be.