@biotone/sdk · Apache-2.0
Hosted API + public SDK
Use typed API clients and capture components to integrate verification into your product. Matching runs on the BioTone API; review upload, storage, and retention requirements for your tenant.
Start with your runtime and where biometric data can be processed.
@biotone/sdk · Apache-2.0
Use typed API clients and capture components to integrate verification into your product. Matching runs on the BioTone API; review upload, storage, and retention requirements for your tenant.
@biotone/edge · Approved partners
Evaluate local biometric processing, encrypted templates, and distributed-key workflows with the private Edge SDK. Access and supported platforms are agreed for your pilot.
QR code or deep link
Hand a browser or kiosk session to the mobile verifier. Your backend validates the result and connects it to your identity provider and application authorization rules.
From sandbox to pilot
Use the SDK package and documentation supplied for your tenant. Complete one enrollment-to-verification flow on the devices you plan to support.
Confirm API access, package entitlement, processing location, consent, and retention before capturing biometric data.
Test your chosen signals with real devices. Exercise rejected captures, failed matches, expired sessions, and user cancellation.
Validate the verification result and its session context. Apply your own access policy, audit the decision, and test revocation and recovery.
Evaluate distributed operations using separate keystore participants and the person’s key share. Test a complete approval, unavailable nodes, and recovery before rollout.
If the person will use a hardware token, include that token and host device in the acceptance test.
Bring your identity provider and target sign-in flow. We will confirm configuration and complete an end-to-end test before rollout.
Tell us where capture happens, where matching may run, and which action needs verification.