Entry is key

Verify humans. Not credentials.

Book a DemoView Documentation
entry-integration.js
import { EntrySDK, EntryApiEnvironment } from 'synapser/entry-web-sdk';

// Initialize once - authenticates the client and fetches config from the Entry API.
const sdk = EntrySDK.getInstance('your-app-name', EntryApiEnvironment.Live);

// Biometrically verify the user before authorizing payment
const container = document.getElementById('entry-container');
const user = await sdk.identifyUser(
  false, // identify only; do not auto-register unknown faces
  container
);

if (user) {
  // User biometrically verified; proceed with transaction
  authorisePayment({ userId: user.entryUserId, amount: 15000, currency: 'ZAR' });
} else {
  // Verification failed; do not proceed
  showVerificationFailed();
}
100K+Platform Users
MultilayerSecurity Architecture
iBeta L2Liveness Certified
AWS FTRTechnical Review
0Stored Credentials

Traditional authentication methods share a common weakness.

๐Ÿ”‘

Passwords get shared.

63% of employees reuse passwords across work and personal accounts. One breach exposes everything.

๐Ÿ“ฑ

OTPs get intercepted.

SIM swapping, SS7 exploits, and real-time phishing kits render SMS codes useless against motivated attackers.

๐Ÿ‘†

Biometrics get spoofed.

Device-level biometrics verify the finger or face โ€” not whether the right person is using them.

Entry doesn't patch these problems. It eliminates them entirely.

Entry

The credential that can't be handed over.

Entry generates a single-use cryptographic key for every verification โ€” bound to a live biometric check, tied to the specific transaction, and destroyed the moment it's used. There is no token to intercept, no password to phish, and no stored credential to steal.

Three steps. Zero stored credentials.

Step 01

Liveness verified.

iBeta Level 2 certified liveness detection confirms a real, present human โ€” not a photo, video, or mask.

Step 02

Single-use key generated.

A unique cryptographic key is created for this specific transaction, bound to the verified identity and device.

Step 03

Key destroyed after use.

The key expires the instant the transaction completes. Nothing is stored. Nothing can be reused or replayed.

How Entry compares.

Security factorEntryPasswordsOTP / SMSDevice Biometrics
Proves human presenceโœ“โœ—โœ—~
Resists phishingโœ“โœ—โœ—โœ“
Resists credential stuffingโœ“โœ—~โœ“
Resists SIM swappingโœ“N/Aโœ—โœ“
Nothing stored to stealโœ“โœ—โœ—โœ—
Transaction-specific bindingโœ“โœ—โœ—โœ—
Forensic audit trailโœ“~~โœ—

Built for high-stakes authentication.

๐Ÿข

Workforce authentication.

Eliminate buddy-clocking and credential sharing. Verify that the person clocking in is the person employed โ€” biometrically, every time.

Learn more โ†’
๐Ÿ”Œ

Platform integration.

Drop Entry into your authentication flow via SDK. Eliminate credential storage and reduce account takeover risk to near zero.

Learn more โ†’
๐Ÿ”’

Step-up verification.

Trigger biometric verification for high-value transactions โ€” payments, legal signatures, privileged access โ€” without routine friction.

Learn more โ†’

See Entry in your environment.

Book a Demo