Hosted Link Flow
Create a
Link identification and receive a URL. Your customer completes KYB verification in Iron’s hosted interface. Iron handles the entire collection, review, and approval process.Programmatic Business API
Submit all KYB data directly via the API with a
Business identification. You collect and provide company info, beneficiaries, documents, and the compliance questionnaire programmatically.Hosted Link Flow
The simplest way to onboard a business customer. You create aLink identification and Iron returns a URL where your customer completes the full KYB process through Iron’s hosted interface.
Iron is fully responsible for collecting all required information, performing verification, and deciding on approval.
Create a Link identification
POST /customers/{id}/identifications/v2url field. Pass this URL to your customer to begin the hosted KYB flow.Customer completes hosted KYB
The customer opens the link and completes the flow in Iron’s hosted interface, which collects company information, documents, beneficial ownership details, and the business questionnaire.Once the submission is complete, Iron reviews the data, performs verification, and decides on approval. Track progress via webhooks or by polling the identification status.
Handle signings and activation
Once KYB is approved, the customer status transitions to
SigningsRequired. Retrieve required signings and present them to the customer, then mark them as signed. See the onboarding lifecycle for details.Programmatic Business API
For partners who collect KYB data within their own application, you can submit all business verification data directly via the API. This requires an outsourcing agreement with Iron. You collect the company information, beneficial ownership details, identity documents, and the compliance questionnaire, then submit everything in a single API call.Create a Business identification
POST /customers/{id}/identifications/v2Submit the full KYB payload with type: "Business". The example below shows a minimal request with one beneficial owner:Example Scenarios
The following examples show thebeneficiaries array for common ownership structures. All other fields (company info, documents, questionnaire) remain the same as the full example above.
Multiple beneficiaries with separate roles
Multiple beneficiaries with separate roles
A company with a majority shareholder/director and a minority UBO:
Corporate shareholder in the ownership chain
Corporate shareholder in the ownership chain
Using an existing Iron customer as a beneficiary
Using an existing Iron customer as a beneficiary
If a beneficiary has already been onboarded as an Iron customer, pass their
customer_id instead of providing beneficiary_info:Business API Field Reference
Company Information
Company Information
| Field | Type | Description |
|---|---|---|
company_name | string | Legal name of the company |
alternative_names | string[] | Optional list of trading or alternative names |
registration_number | string | Number assigned at legal registration |
country | string | ISO 3166-1 alpha-2 country code of registration |
incorporation_date | string | Date of incorporation (YYYY-MM-DD) |
legal_address | string | Address used during legal registration |
postal_address | string | Postal address of the company |
address | object | Structured address (street_1, street_2, city, state, zip_code, country) |
email | string | Company email address |
phone | string | Company phone number (international format) |
tax_identification_number | string | Tax ID of the company |
website | string | Company website URL |
company_type | enum | LimitedLiabilityCompany, PubliclyListedCompany, SoleProprietorship, Partnership, Corporation, Trust, PrivateFoundation, Charity, NonprofitCorporation, NonprofitOrganization, PublicAgenciesOrAuthorities, GeneralCorporation |
Beneficiaries
Beneficiaries
The
The
Used when the beneficial owner is a natural person.
Used when the beneficial owner is a legal entity (corporate shareholder).
beneficiaries array contains one or more CompanyBeneficiary objects representing UBOs, directors, or representatives. At least one beneficiary is required.CompanyBeneficiary
| Field | Type | Required | Description |
|---|---|---|---|
customer_id | uuid | Conditional | ID of an already-onboarded Iron customer. Provide this or beneficiary_info. |
roles | enum[] | Yes | One or more of: UltimateBeneficialOwner, Director, Representative |
share_percentage | decimal | Conditional | Ownership percentage. Required when role includes UltimateBeneficialOwner. |
beneficiary_info | object | Conditional | Person or Business info. Required when customer_id is not provided. |
beneficiary_info field is a discriminated union — set "type": "Person" for an individual or "type": "Business" for a corporate shareholder.PersonBeneficiaryInfo
Used when the beneficial owner is a natural person.| Field | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Must be "Person" |
first_name | string | Yes | First name |
last_name | string | Yes | Last name |
middle_name | string | No | Middle name |
date_of_birth | string | Yes | Date of birth in YYYY-MM-DD format |
tax_identification_number | string | Conditional | SSN or TIN. Required for US residents. |
email_address | string | Yes | Email address |
phone_number | string | Yes | Phone number in international format (e.g. +4915112345678) |
identity_country_code | string | Yes | ISO 3166-1 alpha-2 country code of the identity document |
nationality_country_code | string | Yes | ISO 3166-1 alpha-2 country code of nationality |
tax_jurisdiction_country_code | string | Yes | ISO 3166-1 alpha-2 country code of tax jurisdiction |
birth_place | object | Yes | Place of birth (see BirthPlace below) |
address | object | Yes | Residential address (see Address below) |
BusinessBeneficiaryInfo
Used when the beneficial owner is a legal entity (corporate shareholder).| Field | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Must be "Business" |
company_name | string | Yes | Legal name of the company |
registration_number | string | Yes | Company registration number |
registration_location | string | Yes | City, town, or location where the company is registered |
company_type | enum | Yes | Company type (same values as the top-level company_type field) |
incorporation_date | string | Yes | Date of incorporation in YYYY-MM-DD format |
legal_address | string | Yes | Legal address of the company |
postal_address | string | Yes | Postal address of the company |
email | string | Yes | Company email address |
phone | string | Yes | Company phone number |
tax_identification_number | string | Yes | Tax ID of the company |
control_scheme | string | Yes | Description of the control scheme |
website | string | Yes | Company website URL |
When a corporate shareholder is identified, Iron will require the same KYB documentation for that entity. The natural person(s) who ultimately own 25%+ through the chain must also be identified as UBOs.
BirthPlace
| Field | Type | Required | Description |
|---|---|---|---|
place | string | Yes | City or town of birth |
state | string | Yes | State or region of birth |
country | string | Yes | ISO 3166-1 alpha-2 country code |
Address
| Field | Type | Required | Description |
|---|---|---|---|
street_1 | string | Yes | Street address |
street_2 | string | No | Additional street address |
city | string | Yes | City |
state | string | Yes | State, province, or region |
zip_code | string | Yes | Postal / ZIP code |
country | string | Yes | ISO 3166-1 alpha-2 country code |
Documents
Documents
The
documents array contains one or more CompanyDocParams objects. Each document is uploaded as a base64-encoded file.CompanyDocParams
| Field | Type | Required | Description |
|---|---|---|---|
type | enum | Yes | Document type (see table below) |
country | string | Yes | ISO 3166-1 alpha-2 country code of the issuing country |
file | string | Yes | Base64-encoded document content without the data: URI prefix |
Upload requirements
- Maximum file size: 5 MB per document (after base64 decoding)
- Encoding: standard base64 (no
data:application/pdf;base64,prefix) - Supported formats: PDF, JPEG, PNG
Document types
| Value | Description |
|---|---|
PowerOfAttorney | Power of attorney |
TransparencyRegistryExtract | Recent excerpt from a transparency company registry |
DirectorsRegistry | Directors registry |
GoodStandingCert | Certificate of good standing |
IncorporationArticles | Memorandum, articles of incorporation, association, or registration |
IncorporationCert | Certificate of incorporation or registration |
IncumbencyCert | Certificate of incumbency |
InformationStatement | Statement of information |
PartnershipAgreement | Partnership agreement |
ProofOfAddress | Proof of address (e.g. utility bill, rent contract) |
ProofOfNatureOfBusiness | Proof of nature of business |
RegulatoryLicense | Regulatory or operating license |
SelfDeclarationForm | Self-declaration form |
ShareholderRegistry | Shareholder registry |
StateRegistry | Recent excerpt from a state company registry |
TradeLicense | Commercial or trading license |
TrustAgreement | Trust agreement |
Other | Other document not covered by the types above |
Questionnaire
Questionnaire
The
Industry classification and operational information about the company.
Information about the company’s intended account use and expected transaction patterns.
Information about where the company’s funds originate.
BusinessQuestionnaire object is a required compliance questionnaire structured into three sections. Each section collects specific regulatory information about the business.business_details
Industry classification and operational information about the company.| Field | Type | Required | Description |
|---|---|---|---|
industry_type | enum | Yes | Industry sector classification (see values below) |
business_model_description | string | Yes | Description of the business model and target clients |
main_business_countries | string[] | Yes | ISO 3166-1 alpha-2 country codes where the company primarily operates |
has_licenses_or_registrations | boolean | Yes | Whether the company currently holds any licenses or registrations |
requires_licenses_or_registrations | boolean | Yes | Whether licenses or registrations are required in the company’s jurisdiction |
estimated_annual_revenue | enum | No | Estimated annual revenue bracket in EUR |
aml_cft_policy_document_ids | string[] | No | Sumsub document IDs for uploaded AML/CFT policy documents |
industry_type values: Agriculture, Automotive, BankingAndFinancialServices, ConstructionAndRealEstate, CryptocurrencyAndBlockchain, CryptocurrencyMining, DecentralisedFinance, NftPlatforms, CryptoPaymentProcessors, CryptoWalletProviders, CryptoExchanges, CryptoCustodyServices, EcommerceAndOnlineMarketplaces, EducationAndTraining, EnergyAndUtilities, EntertainmentAndMedia, GamingAndEsports, HealthcareAndPharmaceuticals, HospitalityAndTourism, InformationTechnologyAndSoftware, Insurance, LegalAndProfessionalServices, LogisticsAndTransportation, ManufacturingAndIndustrial, MetaversePlatforms, MiningAndNaturalResources, NonProfitAndCharitable, RetailAndWholesaleTrade, Telecommunications, VentureCapitalAndPrivateEquity, CasinosAndGambling, MoneyServiceBusinesses, SocialMediaAndNetworking, CrowdfundingPlatforms, RegTech, Otherestimated_annual_revenue values:| Value | Range |
|---|---|
Under100K | 0 – 99,999 EUR |
From100KTo1M | 100,000 – 999,999 EUR |
From1MTo10M | 1,000,000 – 9,999,999 EUR |
From10MTo50M | 10,000,000 – 49,999,999 EUR |
From50MTo250M | 50,000,000 – 249,999,999 EUR |
Over250M | 250,000,000+ EUR |
planned_activities
Information about the company’s intended account use and expected transaction patterns.| Field | Type | Required | Description |
|---|---|---|---|
purpose_and_intended_use | enum | Yes | Primary purpose of the business account |
estimated_monthly_volume | enum | Yes | Expected monthly transaction volume in EUR |
estimated_monthly_transactions | enum | Yes | Expected number of transactions per month |
sends_funds_on_customer_behalf | boolean | Yes | Whether the company sends funds on behalf of customers or third parties |
sends_funds_on_customer_behalf_description | string | Conditional | Required if sends_funds_on_customer_behalf is true. Describe how funds are sent. |
flow_of_funds_document_ids | string[] | No | Sumsub document IDs for uploaded flow of funds documents |
purpose_and_intended_use values: ReceivingBusinessIncome, BusinessPurchasesAndExpenses, EmployeeAndContractorPayouts, EcommerceSales, TreasuryManagement, PaymentIntermediary, Investments, TaxPlanning, AssetProtection, Otherestimated_monthly_volume values:| Value | Range |
|---|---|
TenToTwentyFiveThousand | 10,000 – 25,000 EUR |
TwentyFiveToFiftyThousand | 25,000 – 50,000 EUR |
FiftyToOneHundredThousand | 50,000 – 100,000 EUR |
OneHundredToTwoHundredFiftyThousand | 100,000 – 250,000 EUR |
TwoHundredFiftyToFiveHundredThousand | 250,000 – 500,000 EUR |
MoreThanFiveHundredThousand | 500,000+ EUR |
estimated_monthly_transactions values:| Value | Range |
|---|---|
LessThanTen | Fewer than 10 |
TenToTwentyFive | 10 – 25 |
TwentyFiveToFifty | 25 – 50 |
FiftyToOneHundred | 50 – 100 |
MoreThanOneHundred | More than 100 |
source_of_funds
Information about where the company’s funds originate.| Field | Type | Required | Description |
|---|---|---|---|
source_of_funds | enum | Yes | Primary source of the company’s funds |
source_of_funds_description | string | No | Detailed description of the source of funds |
customer_funds_handling_details | string | No | How customer funds are handled (relevant for payment intermediaries) |
source_of_funds values: BusinessRevenue, ShareholderFunds, VcPrivateEquity, AssetSale, IcoProceeds, CryptoActivityProceeds, LoanProceeds, OtherStandard KYB Requirements
Company Information
- Country
- Company name
- Registration number
- Company registration address
- Company operations address
- Type of entity
- Date of registration
- Website
- Company email
- Tax ID
Documents
Company Details
Company Details
Accepted document types:
- Statement of information
- Excerpt from a state company registry
- Articles and memorandum of association
- Incorporation certificate
- Certificate of incumbency
- Certificate of good standing
Ownership Structure
Ownership Structure
Accepted document types:
- Shareholder registry
- Statement of information
- Trust agreement
- Excerpt from a state company registry
Control and Management Structure
Control and Management Structure
Accepted document types (any that contains information about appointed directors):
- Director registry
- Trust agreement
- Statement of information
- Excerpt from a state company registry
Business Questionnaire
| Section | Question | Answers |
|---|---|---|
| Business information | Industry type | Agriculture, Automotive, Banking and Financial Services, Construction and Real Estate, Cryptocurrency and Blockchain, Cryptocurrency Mining, DeFi, NFT Platforms, Crypto Payment Processors, Crypto Wallet Providers, Crypto Exchanges, Crypto Custody Services, E-commerce and Online Marketplaces, Education and Training, Energy and Utilities, Entertainment and Media, Gaming and Esports, Healthcare and Pharmaceuticals, Hospitality and Tourism, Information Technology and Software Development, Insurance, Legal and Professional Services, Logistics and Transportation, Manufacturing and Industrial, Metaverse Platforms, Mining and Natural Resources, Non-Profit and Charitable Organizations, Retail and Wholesale Trade, Telecommunications, Venture Capital and Private Equity, Casinos and Gambling, Money Service Businesses, Social Media and Networking Platforms, Crowdfunding Platforms, RegTech, Other |
| Business information | Business description | Free text |
| Business information | Main countries of operation | Dropdown country selection |
| Business information | Licensed or registered | Yes / No |
| Business information | AML program required | Yes / No |
| Business information | Estimated annual revenue | Up to 99,999 EUR, 100,000–999,999 EUR, 1,000,000–9,999,999 EUR, 10,000,000–49,999,999 EUR, 50,000,000–249,000,000 EUR, More than 250,000,000 EUR |
| Source of funds | Source of funds | Business revenue, Shareholder funds, VC or private equity, Sale of assets, ICO proceeds, Crypto related income, Loan proceeds, Other |
| Source of funds | Customer funds details | Free text |
| Planned activities | Purpose and intended use | Receiving income, Expenses, Payouts, E-commerce sales, Treasury management, Payment intermediary, Investments, Tax planning, Asset protection, Other |
| Planned activities | Estimated monthly volume | 10,000–25,000 EUR, 25,000–50,000 EUR, 50,000–100,000 EUR, 100,000–250,000 EUR, 250,000–500,000 EUR, More than 500,000 EUR |
| Planned activities | Monthly transaction count | Less than 10, 10–25, 25–50, 50–100, More than 100 |
| Planned activities | Send funds on behalf of customers | Yes / No |
Upload Source of Funds document is only required for Euro 3rd party payout.
Associated Parties
| Party Type | Description |
|---|---|
| UBO (Ultimate Beneficial Owner) | Always a natural person. Direct or indirect ownership above 25% (or 10% in high-risk cases). |
| Director | Individual(s) formally appointed as director(s). |
| Representative | Authorized individual acting on behalf of the company. |
| Shareholder | Direct ownership above 25%; always a legal entity. |
Example: Business Customer → owned by Company A → John Smith owns Company A → Company A is Shareholder, John Smith is UBO.
Required Information by Party Type
- UBO (Individual)
- Director / Representative
- First name
- Last name
- Middle name
- Date of birth
- Contact number
- Nationality
- Percentage of ownership
- SSN (Social Security Number) for US citizens and US residents
- Address details
- Proof of Address (not older than 90 days)
Identity Verification / Liveness Check
For business customers, there are typically 2–3 types of people to identify, depending on whether an authorized representative is appointed:| Party | Requirements |
|---|---|
| Director(s) | ID collection + liveness check |
| UBO(s) | ID collection (liveness check may be required in high-risk cases, or if also a director) |
| Authorized Representative | ID collection + liveness check + power of attorney signed by the company’s director |
Enhanced KYB Due Diligence
Business customer risk is defined through a customer risk rating process, calculating the risk score based on different factors: geography, industry, use of product, expected activities, legal form, etc.| Requirement | Details |
|---|---|
| KYB Information | Standard KYB |
| UBO Information | Individuals holding 10%+ ownership |
| Source of Wealth | Financial document outlining the corporate entity’s ability to continue business |
Appendix
Prohibited Industries
- Adult entertainment and dating services (dating apps, matchmaking sites, coaching/advice providers)
- Sexual services (anything which implies sex as a service)
- Marijuana/Cannabis/CBD industry (including cannabis paraphernalia)
- Production or trade in tobacco (cigarettes, cigars, e-cigarettes, vapes, vape liquids) - vape hardware not included
- Production or trade in weapons and munitions, including explosives and nuclear weapons
- Arms/Defense/Military
- Private military/Security contractors
- Car dealers
- Antique brokers
- Jewellery or watch dealers
- Precious metal and/or gem dealers
- Pre-paid cards
- Religious organizations
- Multi-Level Marketing (MLM) structures
- Financial pyramid or Ponzi schemes, matrix programs, and other similar schemes
- Unlicensed Forex/Binary Options
- Donations/Charities/Societies/Non-profit organizations
- Drugs, as well as chemicals used to manufacture synthetic drugs
- Commercial activity which infringes on copyrighted material
- Alternative medicines (e.g. homeopathy)
- Financial services (loan lenders, payday loans companies, debt/credit consolidation companies, debt collection agencies)
Business Ownership and Constitutional Documents
To comply with Iron’s KYB requirements, all businesses must provide clear, official documentation that reliably verifies their complete ownership structure, ultimate beneficial owners (UBOs), controlling individuals, and confirms the existence and ongoing operations of the legal entity. If the entity does not have individual beneficial shareholders, we will need to confirm the individuals who significantly control the entity instead, such as its directors and officers. Supported entity types:- Sole Proprietorships
- Partnerships
- LLCs & Corporations
- Trusts
- Nonprofits
- DAOs
- Cooperatives
Required Documentation per Entity Type
Sole Proprietorships
Sole Proprietorships
- Official sole proprietorship license or registration document clearly naming the sole proprietor and confirming active operation
- Recent tax filings or official government-issued documents linking the proprietor to business operations
Partnerships (General, Limited, LLP)
Partnerships (General, Limited, LLP)
- Partnership agreements officially certified or notarized, detailing partners and ownership shares
- Officially issued partnership registration certificates clearly listing partners and their shares
LLCs and Corporations
LLCs and Corporations
- Articles of Incorporation or Articles of Organization issued by the official business registry, clearly listing shareholders/members
- Official shareholder/membership register or certified extracts from commercial registries clearly indicating owners and ownership percentages
- Share certificates officially verified or notarized
- Recent audited financial statements (for publicly traded or regulated entities), confirming the company’s operations and ownership
Trusts
Trusts
- Official trust deed or certificate clearly identifying trustees, settlors, protectors (if applicable), and beneficiaries
- Notarized trustee affidavit clearly verifying trustee identity, roles, and authorities
Nonprofit Organizations
Nonprofit Organizations
- Official formation documents (e.g., Articles of Incorporation) clearly listing controlling individuals (e.g., directors or board members)
- Government-issued or officially filed annual reports or governance documents confirming ongoing operations and key individuals
DAOs (Decentralized Autonomous Organizations)
DAOs (Decentralized Autonomous Organizations)
- Official governance documents or independently audited membership agreements clearly outlining membership, control mechanisms, and operational status
Cooperatives
Cooperatives
- Official formation documents clearly identifying cooperative members
- Independently certified membership ledgers or agreements clearly indicating members and voting rights
Document Verification Standards
All provided documents must be issued by an official governmental authority and, where applicable, certified by a notary public, lawyer, auditor, or similar independent professional, with Apostille certification where applicable.- General Standards
- Required Confirmations
- Unacceptable Documents
- Must be officially issued by governmental authorities
- Must be verifiable online through an official registry or database (if not possible, must be independently certified)
- Apostille certification or equivalent legalization required where applicable
- Self-generated or internally-produced documents are NOT acceptable
- Must clearly display the full legal name and registration code of the business entity
- If ownership structure involves more than two layers, a clear organizational chart with ownership percentages is required
- Must be recent (issued within the past three months)
- Documents not in English must include certified translations
Requirements for Regulated Entities
Entities that operate under regulatory supervision must provide additional documentation to confirm their licensing status and compliance with AML/CFT regulations.Regulatory Licenses and Authorizations
A valid license or authorization issued by the relevant financial regulator or supervisory authority permitting the entity to conduct its business activities. If the license or authorization is not publicly accessible online, it must be certified by the issuing authority or a notary public.AML/CFT Policy and Procedures
A copy of the entity’s internal AML/CFT policy, outlining its approach to:- Customer due diligence (CDD) and enhanced due diligence (EDD)
- Transaction monitoring processes
- Suspicious activity reporting procedures
- Sanctions screening and PEP checks
- The policy must be approved by senior management and aligned with the applicable jurisdiction’s AML laws and regulations
- Licenses and authorizations must be verifiable online (if not, must be certified by the issuing authority, a notary public, or a licensed legal/audit professional)
- The submitted AML/CFT policy must be an officially approved internal document (not a draft or template)

