SenseCrypt Docs
SDKs & apps

SDKs & apps

The SenseCrypt Authenticator mobile app for end users, the Mobile SDK for building your own, and how to integrate your own web application as a relying party.

There are two sides to a SenseCrypt integration: the end-user app that performs the biometric ceremony, and your application that speaks OIDC or SAML.

A live-face check proves the person in every ceremony; on the passkey method a real FIDO2/WebAuthn passkey (ES256) proves the device. See How SenseCrypt works for the three sign-in methods (Simple QR, passkeys, and the enterprise Simple Webcam).

For end users: the Authenticator app

The SenseCrypt Authenticator is the mobile app (iOS and Android) your users install to approve sign-ins with a face scan. It is the end-user app — you do not embed it in your product. Your users install it from the App Store or Google Play.

A tenant can instead run its own app: a rebuild of the Authenticator, or an app of your own built on the SDK, distributed under your own developer accounts. The server verifies that app once the tenant registers it on the console's Mobile App page. See Ship your own Authenticator app.

For your own app: the Mobile SDK

The Mobile SDK embeds the same device-bound keys, on-device face matching and authentication flows in your own iOS or Android app. It is provided on request, not published publicly. Most integrations do not need it.

For your application: relying party

Your web app integrates as a standard OIDC relying party (or a SAML SP). You do not need a SenseCrypt-specific SDK — any conformant OIDC/SAML client library works. See Relying party for how to think about it, then the Add Login quickstart for the concrete steps.

Pages

  • Mobile (Authenticator) — the end-user app, how enrollment works, and what users see when they approve a sign-in or a key request.
  • Mobile SDK — embedding the flows in your own app.
  • Relying party — integrating a web app over OIDC.

On this page