For business
Stop paying full price to verify people who have already been verified. OpenKYC lets your signup flow accept a credential the customer already holds, check it in seconds against a licensed issuer, and move on. No document upload, no manual review queue, no ID scans sitting in your storage.
Built on W3C Verifiable Credentials, OpenID4VP and SD-JWT, and aligned with the EUDI Wallet. The implementation will be open source at launch, so there is no vendor to be locked into.
Identity verification fails in two places at once. It is expensive, because you pay a provider for every check including the customer you verified last quarter under a different product. And it leaks, because the document upload and the review wait are the highest friction steps in any signup flow.
Reusable KYC attacks both from the same direction: verify once, then verify against that result instead of repeating it.
| Traditional KYC | OpenKYC | |
|---|---|---|
| Time to verified | Minutes at best, days when manual review is triggered | Seconds when the customer already holds a credential |
| Cost per check | Full price on every check, including repeat customers | Full price once, reuse fee after that |
| Documents you store | ID scans and selfies land in your systems and your breach radius | A cryptographic proof of the fact you needed, no raw documents |
| Credential portability | Locked to the vendor. Switching means re-verifying every customer | W3C Verifiable Credentials, readable by any compliant verifier |
| Coverage of AI agents | None. Agents get an API key and no accountable owner | Scoped, revocable agent credentials tied to a verified human |
The EU Digital Services Act and the UK Online Safety Act moved age checks from optional to mandatory across gambling, adult content and social platforms. A reusable credential proves 18+ in seconds with a selective disclosure proof, so you never hold a scan of a passport you did not want in the first place.
UK Online Safety Act and age verificationOpen banking flows already prove account ownership. They do not prove identity, so most fintechs run a full KYC check on top and lose applicants in the gap. Accepting an existing credential collapses that step for anyone who already holds one.
Open banking and KYCTwo-sided platforms verify sellers, drivers, hosts and renters, then verify them again at every tier change. A portable credential moves with the person across your own product surfaces and across the network.
Reusable KYC vs traditional KYCAgents now transact on their own, authenticated by API keys nobody stands behind. OpenKYC roots every agent identity in a KYC-verified human, encodes exactly what the agent may do, and lets the owner revoke it in one action. It ships as an MCP server your agents already know how to speak.
Know Your Agent explainedStep 01
Request a proof
Ask for the single attribute you actually need, over OpenID4VP. Age over 18, identity verified, address in a jurisdiction. Not the whole document.
Step 02
Verify the presentation
The SDK checks the signature against the issuer and the revocation status list. No call home about who asked, no shared secret.
Step 03
Onboard, or fall back
Holders are through in seconds. Anyone without a credential is routed into first-time issuance with a licensed provider, and comes out the other side holding one.
A reusable KYC platform turns a completed identity check into a portable credential the customer holds. The next business that needs to verify them asks for a proof from that credential instead of running the whole check again. The verification work happens once and every business after that verifies against it in seconds.
Most KYC drop-off happens at the document upload and the wait that follows. Removing both for customers who already hold a credential removes the two steps where funnels leak hardest. It does not help a customer who has never been verified anywhere, which is why OpenKYC supports first-time issuance as well as reuse.
No. Credentials are issued by licensed KYC providers who do the regulated work. OpenKYC is the layer that makes the result of that work portable and reusable, so you stop paying full price to re-verify people who were already verified. You keep your provider relationship and your compliance posture.
Open banking proves that someone controls a bank account. It does not by itself prove who they are, so most fintechs run identity verification alongside it. A reusable identity credential fills that second half without a second document upload, and the two signals together are stronger than either alone.
A verifier SDK call in your signup flow: request a proof of the specific attribute you need, receive a signed presentation, check it against the issuer and the revocation status list. It speaks OpenID4VP and SD-JWT, so if you already support the EUDI Wallet you support this.
That depends on your regulator, your jurisdiction and your risk profile, and it is a question for your compliance team rather than for us. What OpenKYC provides is a verifiable chain back to a licensed issuer, the attributes that issuer attested, and when. Reliance rules for third-party verification vary by regime and we are explicit about that rather than promising blanket compliance.
Yes. Know Your Agent issues an agent a scoped credential that traces back to the verified human who authorized it. The credential encodes what the agent is allowed to do and for how long, and the owner can revoke a single agent or an entire fleet immediately.
Join the waitlist for early access to the verifier SDK, or email us about your onboarding funnel.