This requires an outsourcing agreement with Iron.Documentation Index
Fetch the complete documentation index at: https://docs.iron.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Outsourcing Agreement
To use the Outsourcing API Endpoint, a signed KYC/KYB Data Sharing Agreement must be in place between your organization and Iron. This agreement is a prerequisite for submitting customer identification data directly via the API.Why is the agreement required?
Iron operates under strict anti-money laundering (AML) and counter-terrorist financing (CTF) regulations across multiple jurisdictions. The Outsourcing Agreement establishes a formal legal framework that:- Defines data collection standards — Specifies the identity documents, customer information, and verification methods your organization must use when collecting KYC/KYB data on Iron’s behalf.
- Ensures regulatory compliance — Confirms that both parties maintain the necessary licenses, authorizations, and internal controls required by applicable laws.
- Sets data quality and security requirements — Establishes obligations around accuracy, completeness, authenticity, and secure transmission of customer data via the API Endpoint.
- Governs data protection — Ensures customer data is handled in compliance with applicable data protection laws, with each party acting as an independent data controller.
- Enables independent verification — Clarifies that Iron conducts its own verification and risk assessment on all received data. The agreement does not exempt Iron from its own compliance obligations.
Key considerations
- Timing matters: Only customer data collected after the agreement is executed is fully compliant for Iron’s onboarding process. Data collected before the agreement may require supplementary verification. See the Data Collection Timeline below for details.
- Approved identity verification providers: Your identity verification provider(s) must be proposed to and approved by Iron before data sharing begins.
- Data Completion Loop: If Iron identifies missing or insufficient information during its review, you will be notified to collect and resubmit the required data via the API.
Onboarding Lifecycle
Optimizing Customer Identification
Leverage existing customer identity data to streamline onboarding. In optimal scenarios, this eliminates the need for redirects or third-party verification flows.Regulatory Framework and Data Usage
The outsourcing agreement establishes a framework for sharing customer identification data with Iron for KYC/KYB purposes. However, data collected prior to the agreement falls outside its scope. Regulatory requirements mandate that we independently verify critical identification elements through our authorized KYC providers.Data Collection Timeline
Example: Outsourcing agreement executed at 13:00 (UTC) on January 1, 2026:| Data Type | Collection Time | Status |
|---|---|---|
| Post-Agreement | After 13:00, Jan 1, 2025 | Fully compliant for Iron’s approval process |
| Pre-Agreement | Before 13:00, Jan 1, 2025 | Requires supplementary verification |
Technical Details
Onboarding via API
The process mirrors the standard onboarding flow, with one exception: when creating an Identification, a body must be provided. The request body uses atype discriminator at the top level — set it to "Person" for KYC or "Business" for KYB. All other fields are siblings of type in the same object.
KYC
KYB
Sole proprietor variants
For sole proprietorships, setcompany_type to "SoleProprietorship" and questionnaire.type to "SoleProp". The proprietor is submitted as a single beneficiary with the UltimateBeneficialOwner role at 100% share. See Sole Proprietor Onboarding for the full data breakdown.
US sole proprietor
US sole proprietor
Non-US sole proprietor (UK)
Non-US sole proprietor (UK)
Triggering EDD
To proactively trigger Enhanced Due Diligence for a customer (e.g. high-volume or high-risk jurisdiction), include theedd_questionnaire object in your Person params. This initializes the identification with the full EDD flow, including Source of Funds collection.
| Field | Values |
|---|---|
occupation | Agriculture, ArtsAndEntertainment, Construction, Education, FinancialServices, InformationAndTechnology, Retail, RealEstate, Other |
approximate_net_worth | UpTo25000, Between25001And50000, Between50001And100000, Between100001And300000, Between300001And500000, Between500001And1000000, Over1000001 |
source_of_funds_proof | Base64-encoded document (jpg, png, pdf, doc, docx, xls, xlsx, odt, ods, txt). Max 10 MB. |
edd_questionnaire is provided, with_edd is set to true on the identification response. See Tracking EDD Status for how to interpret the identification status with EDD.
EDD is only available for individual customers (KYC). Business customers (KYB) are not supported.

