Skip to main content
IRON ID
Request a demo

IRON ID Enterprise · Sign SDK

Coming soon

Trusted digital signing, inside your own applications.

An SDK and API to embed long term verifiable signatures into your own products and workflows, with signers as verified identities and an evidence bundle for every envelope.

Request a quoteTalk to an engineer

Sold through enterprise sales and technical discussion. Custom quotation. Not part of the Platform.

IRON ID EnterpriseThe Sign 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 Sign SDK?

Embed trusted digital signing into your own products.

The Sign SDK lets your applications send documents for signature, collect signatures in an embedded flow, and get back a sealed document: PAdES B-LTA, a timestamp per signature, and an evidence bundle.

Signers are IRON ID identities, verified through the KYC SDK where you require it. A partner, a client or a court can verify the result in any standard PDF reader, without IRON ID.

A signature, from your application

  1. Your appcreates an envelope
  2. Sign SDKembedded signing
  3. SealedPAdES B-LTA
  4. Your appwebhook + bundle

Signing happens inside your product. The sealed document and its evidence bundle come back to you, verifiable by anyone for years.

Integration

Embedded flow, API, webhooks.

  • Embedded signingA signing flow inside your web application, in your branding.Coming soon
  • REST APICreate envelopes, add signers and fields, read status and results.Coming soon
  • WebhooksSigned events on each signature and on completion.Coming soon
  • TemplatesReusable documents with fields and signer roles.Coming soon
  • Verified signersRequire a KYC verified identity before a signature.Coming soon
  • Evidence bundleSealed document, attestations and audit extract, in an open format.Coming soon

How it works

From your application to a sealed envelope.

  1. 1CreateYour back end creates an envelope: document, signers, fields, order.POST /v1/envelopes
  2. 2SignSigners sign in the embedded flow, with their IRON ID identity and MFA.embed_url · verified identity
  3. 3TimestampEach signature is applied with the signer's certificate and timestamped.RFC 3161 per signature
  4. 4SealThe completed document is sealed in PAdES B-LTA and written to the audit log.chain + revocation data embedded
  5. 5ReturnYou receive the sealed PDF and the evidence bundle by webhook.envelope.completed

Years later

Day 0, year 2, year 10.

A signature is only useful if it can still be checked when someone finally asks. That is where most signed PDFs quietly fail.

An ordinary signed PDF

Day 0ValidSignature and certificate check out.
Year 2 · certificate expiredCannot be validatedNo revocation data was kept; the reader cannot rebuild the chain.
Year 10 · vendor goneUnknownNobody can say what this file was, or when.

A Sign SDK signature

Day 0ValidSignature and certificate check out.
Year 2 · certificate expiredStill verifiesChain, revocation data and timestamp were embedded at signing (PAdES B-LTA).
Year 10 · vendor goneStill verifies, offlineEvidence bundle and any standard PDF reader; no IRON ID needed.

Levels

Precise about the level, on purpose.

Signature levels are legal categories. The SDK states exactly which one it provides, and what the next ones depend on.

Simple electronic signatureAny signature at the standard level.At launch
Advanced electronic signatureRequires the exclusive control model to be validated by a lawyer.Under legal review
Qualified electronic signatureRequires a qualified trust service provider and a qualified device; not planned for the first version.Not in V1

Legal value is not claimed beyond the level actually provided. When the advanced level is validated, this table changes, not the marketing.

How we work with you

Enterprise sales, technical discussion, quotation.

The Sign SDK is not a self service plan. Every integration starts with a conversation between your team and ours.

  1. 1Technical discussionYour use case, volumes, constraints, deployment model. With an engineer, not a sales deck.1 to 2 calls
  2. 2Pilot in the sandboxYour developers integrate the SDK against the sandbox with test data.API keys · sandbox
  3. 3QuotationPricing on volumes, scope and support. Contract, DPA and SLA where required.custom
  4. 4Integration and supportGo live with a named contact on our side; integration support included.named contact
Request a quoteTalk to an engineer

FAQ

Questions buyers ask first.

Is the Sign SDK part of the IRON ID Platform?

No. It is a separate enterprise product for embedding signing into your own applications, priced on quotation.

Which signature level does it provide?

The simple electronic signature level at launch. Advanced and qualified levels require legal validation and a qualified provider, and are not claimed until in place.

Can a partner without IRON ID verify a signed document?

Yes. PAdES B-LTA signatures verify in any standard PDF reader; the evidence bundle can be checked offline.

When is the Sign SDK available?

Coming soon. It is specified and follows the sharing milestone; enterprise prospects can start the technical discussion now.

How is it priced?

On quotation: envelope volumes, integration scope, signature levels required and support level.

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.

Request a demoRequest a quote

Reply within two business days · contact@iron-id.io