For IDV Issuers

Become an Issuer
in the lemma.id network.

Lemma is to your IDV product what Plaid is to bank APIs — a consumer-web distribution layer for the reusable-credential model. You issue once; we distribute across sites your enterprise sales motion can't economically reach.

Didit is the production issuer. Persona, Veriff, Yoti, and Sumsub integrations on roadmap.

Talk to us about issuance How it works

A new category of IDV demand,
structurally non-competing

Most websites — waitlists, free-trial SaaS, ticketing, comments, dating, AI agent gating — never buy IDV because $1–2 per user can't be justified per signup. Lemma pools demand across many sites so a single issuance funds verification across the network. The net-new IDV volume comes from a population that today generates zero revenue.

Four reasons

Why this is good for the issuer specifically

Net-new verification volume

Long-tail sites won't pay $1–2 per user for full IDV. Pooled across the network, they will pay a few cents per check. They adopt precisely because Lemma lets them act on a verified-human signal without storing ID documents or running their own KYC stack — so the issuer sees verification volume from a population that today generates zero.

You keep the upsell

Lemma never participates in expansion revenue. The relying-site relationship belongs to the issuer; full IDV, age, KYB, AML, monitoring, manual review — all sold direct, full margin. Contractually carveable.

Recurring revenue via revocation

Sites can challenge a credential at any time. Refresh and step-up checks generate a long tail of issuance events from a single onboarding — converting one-shot KYC into a continuously-priced trust signal.

Designed not to disintermediate issuers

lemma.id's local-first design is built so it does not need cross-site behavioral data to deliver value. Issuers keep the verification relationship, pricing power, and upsell path for higher-assurance checks.

Issuer's role

You sign once. The credential lives in the user's wallet.

Verification happens in-context on whichever site the user is on, then the credential is stored locally. Sites verify it offline. You see the issuance event, then nothing — no cross-site behavior data to store, secure, or be subpoenaed for.

1

Site triggers verify

Relying site embeds the SDK; user has no credential yet.

2

Issuer flow runs in-flow

SDK launches the issuer's verification flow on the relying site. No detour to lemma.id.

3

Issuer signs credential

Issuer's TTL, issuer metadata, and Ed25519 signature on the master credential.

4

Wallet stores it locally

Master credential lives in the user's browser wallet, not on Lemma servers.

5

Sites verify locally

Future sites validate signature + freshness in-browser, no round-trip to issuer or to Lemma.

Like a physical driver's license. The DMV signs once. The bar verifies locally. The DMV doesn't get notified at the moment of use. Lemma works the same way — issuers sign, sites verify, users carry the credential.

Architecture moat

Designed not to disintermediate issuers

Every issuer evaluating a partnership of this shape asks the same question: what stops the aggregator from eventually routing to other issuers and replacing us?

lemma.id does not need to observe cross-site usage to deliver value. Credentials live in the user's browser, verification happens in-browser, and routine access decisions do not require a live callback to the issuer. Issuers keep the verification relationship, pricing power, and upsell path for higher-assurance checks.

The architecture is designed to complement issuer distribution — not replace it.

Issuer roadmap

Multi-issuer is the long-term moat

A reusable credential issued by Issuer X is only valuable to relying sites that also accept Issuer X. Lemma's value is the multi-issuer aggregation — same logic as Plaid winning despite every bank having APIs.

Live

Didit

Production IDV rail. Hosted liveness and document verification in the lemma.id wallet flow.

Targeted

Persona

Mapped to Persona Connect. Strongest end-to-end fit for the consumer-web distribution layer.

Targeted

Veriff

Strong PLG fit; net-new anti-bot tier as a product line for their roadmap.

Open

Yoti, Sumsub, iProov

Adjacent issuers with reusable-credential strategies. Open to conversation.

Issue once. Distribute everywhere.
Keep the customer.

If you're an IDV issuer and the consumer-web distribution thesis is interesting, send a note. We'll send a one-pager and schedule a 20-minute exploratory call.

Email [email protected] Back to home