New: Hypersign is now eIDAS 2.0 ready verifiable credentials and EUDI Wallet compliance built in. See case studies →
Developers

Ship identity verification your way.

A shareable link, a drop-in widget, or a fully custom flow on our REST API, all backed by the same KYC, KYB, AML, consent, and identity vault infrastructure. Pick the integration depth your team needs today, and change your mind later without switching platforms.

✓ REST API & Webhooks✓ W3C DIDs & Verifiable Credentials✓ Session-Based, HMAC-Signed Callbacks✓ White-Label by Default

Integration Paths

Three ways to go live, no rewrite required to move between them.

Start with a hosted link while you validate the flow, move to an embedded widget once you need branding, and drop to raw API calls when your product demands full control. Every path talks to the same sessions, decisions, and credentials underneath.

Go Live in Minutes
Early-stage teams, DAOs, ops-led onboarding

No SDK, no code. Share a branded, hosted verification link and your users verify in minutes.

  • Hosted verification page
  • Zero engineering lift
  • Fully branded, ready today
Follow the quickstart →
Integrate the Widget
Product teams moving fast

Embed a configurable, white-labeled verification widget directly into your web or mobile app.

  • Plug-and-play SDK
  • Full brand control
  • Session-based security
Read the widget guide →
Build a Custom Flow
Scaling & enterprise teams

Call the REST API directly and compose your own onboarding flow, with webhooks for every state change.

  • Full UI ownership
  • Real-time webhook events
  • Complete control over UX
Read the API guide →

See It In Code

The widget path, end to end.

Plain TypeScript, no SDK install
const url = new URL("https://verify.hypersign.id");
url.searchParams.set("sessionId", sessionId);
url.searchParams.set("kycUserAccessToken", userBearerToken);
window.open(url.toString(), "hypersignKyc", "width=440,height=900");
window.addEventListener("message", (e: MessageEvent) =>
  e.data.code === "VERIFICATION_SUCCESS" && onVerified(e.data));

sessionId and kycUserAccessToken come from one backend call to Hypersign's KYC API. Full integration guide →

How We Build It

Core design principles behind the API.

These aren't marketing bullets, they're the constraints every endpoint and widget in the platform is designed against.

Standards First

Every identity issued is a W3C DID (did:hid) and Verifiable Credential, so proofs are portable to any standards-compliant verifier, not locked to Hypersign's own network.

Learn more →
Privacy by Design

Selective disclosure and zero-knowledge proofs mean a verifier gets exactly the attribute it needs, an over-18 flag instead of a birthdate, never the full document.

Learn more →
Composable, Not Monolithic

ID verification, KYB, AML, consent, and the identity vault are independent modules. Call one, or wire them into a single decision, your flow either way.

Learn more →
Session-Based Security

Every check runs behind a short-lived session token, and every webhook callback is HMAC-SHA256 signed. No long-lived credentials sitting around to leak.

White-Label by Default

Hosted pages and embedded widgets ship brandable out of the box, your logo, your colors, your domain, not an enterprise-tier upsell.

Learn more →
Built for Regulation

Native support for GDPR, India's DPDP Act, and eIDAS 2.0 / EUDI Wallet requirements from day one, not retrofitted after a compliance review.

Learn more →

Talk to the team building this.

Book a call with an engineer for a walkthrough of the API, or start in the sandbox and read as you go.