IRON ID Enterprise · KYC SDK
Early accessIdentity verification, inside your own applications.
An SDK and API to verify people and organizations in your onboarding flows, and to turn every verification into a fingerprinted, auditable record.
Sold through enterprise sales and technical discussion. Custom quotation. Not part of the Platform.
IRON ID EnterpriseThe KYC SDK is sold separately from the IRON ID Platform: integrated into your own applications, through enterprise sales, on quotation. It is not included in Workspace.
What is the IRON ID KYC SDK?
Verify people and organizations, in your own onboarding flows.
The KYC SDK lets your applications answer a question before trusting someone: is this person really who they claim to be, and may they act for this organization? You embed the SDK, or call the API, where your users sign up, apply or contract.
Every verification produces a record: fingerprinted, timestamped and auditable, on the IRON ID trust layer. It is built for banks, insurers, telecoms, fintechs and any business that onboards people or suppliers at scale.
A verification, from your application
- Your appopens a session
- KYC SDKdocuments · checks
- Decisionverified · refused
- Your appwebhook + record
The person never leaves your product. The decision, and a fingerprinted, timestamped record of the checks, come back to you.
Integration
SDK, API, webhooks.
Three ways in, one record out.
- Web SDKDrop in verification flow for your web applications, in your branding.Early access
- Mobile SDKNative components for iOS and Android apps.Coming soon
- REST APIOpen sessions, read decisions and records from your back end.Early access
- WebhooksSigned events when a decision is taken or a record changes.Early access
- SandboxTest data and test documents for your developers.Early access
- Reviewer consoleYour compliance team decides the cases the checks cannot.Early access
What gets checked
Three questions, one case.
Who is this person?
Identity documentauthentic, not expiredEarly access
Data consistencyname, birth date, document numberEarly access
Re-verification dateset per caseEarly access
Which organization?
Commercial register extractlegal form, registration, addressEarly access
Statusactive, suspended, struck offEarly access
Beneficial ownershipwho ultimately controls itPlanned
Who may act for it?
Mandate or corporate roledirector, CFO, delegateEarly access
Person to organization linkverified both waysEarly access
Scopesign, share, administerEarly access
How a verification runs
From your application to a decision.
- 1Open a sessionYour back end calls the API; the SDK opens in your app.POST /v1/verifications
- 2CollectThe person uploads documents in the SDK; each one is fingerprinted.id-card.jpg · sha256 7c1d…
- 3CheckAutomatic checks run; your reviewers decide where the result is not clear.document valid · data consistent
- 4DecideVerified, action needed, or refused, always with a reason.verification.completed
- 5RecordYou receive the decision and a timestamped, auditable record.sha256 9b1e…44aa · RFC 3161
Evidence
A verification is evidence.
Each verification produces a record that is fingerprinted, timestamped and written to a tamper evident log. You can show, later, what was checked, when, and by whom, even to a regulator.
- Subject
- Samir Benali · person
- Organization
- Numidia Group · finance
- Checks
- document valid · data consistent · link valid
- Fingerprint
- sha256 9b1e…44aa
- Timestamp
- RFC 3161 · 12 Mar 2026 09:01:44
- Audit
- entry #48 219 · checkpoint sealed
- Re-verify
- 12 Mar 2027
- Exportable in an open format
- Erasable content, durable proof
- Reviewer decisions recorded with their reason
Coverage
Designed for local documents first.
Document types and data sources are confirmed with early access members. Nothing here claims a regulatory approval.
- National identity card[COUNTRY LIST] · confirmed at early accessEarly access
- PassportMachine readable zone checksEarly access
- Commercial registerExtract, status, registration numberEarly access
- Compliance viewPolicies, deadlines, reporting across casesPlanned
- Other countriesAfrica first, adapted per legal frameworkPlanned
- Private deploymentThe SDK back end on your infrastructurePlanned
How we work with you
Enterprise sales, technical discussion, quotation.
The KYC SDK is not a self service plan. Every integration starts with a conversation between your team and ours.
- 1Technical discussionYour use case, volumes, constraints, deployment model. With an engineer, not a sales deck.1 to 2 calls
- 2Pilot in the sandboxYour developers integrate the SDK against the sandbox with test data.API keys · sandbox
- 3QuotationPricing on volumes, scope and support. Contract, DPA and SLA where required.custom
- 4Integration and supportGo live with a named contact on our side; integration support included.named contact
FAQ
Questions buyers ask first.
Is the KYC SDK part of the IRON ID Platform?
No. It is a separate enterprise product, integrated into your own applications and priced on quotation.
How is it priced?
On quotation, after a technical discussion: volumes, document types, integration scope and support level. There is no self service plan.
Which documents are supported?
National identity documents and commercial register data first; coverage is confirmed with early access members.
Is the verification legally recognised?
The SDK produces a verifiable record of the checks performed. It does not claim a regulatory approval; your compliance obligations remain yours.
Where is the data stored?
With the platform, under the deployment model agreed in your contract, including private deployment.
Get started
See IRON ID for your organization.
Request a demo of the Platform, join early access to be onboarded in the first cohorts, or request a quote for a KYC or Sign SDK integration.
Reply within two business days · contact@iron-id.io