MetaMap enables biometric reauthentication

This turns MetaMap from a one time onboarding vendor into an always on identity checkpoint inside the customer journey. After a user completes KYC once, the business can call back to that stored identity record, ask for a fresh selfie, and confirm the same person is present with liveness checks, instead of forcing a full document upload again. That makes MetaMap useful not just for signup, but for login, password reset, payout release, and other moments where account takeover risk is highest.

• The product works off an existing identityId from the original verification. MetaMap documents show Customer Access Management runs a new face match event against the prior record, which keeps the workflow fast and lightweight compared with rerunning full KYC.
  1 metamap 2 sacra
• This changes the budget owner. Classic KYC is usually bought by compliance teams to satisfy onboarding rules. Re authentication for login and transaction approval is bought by security, fraud, and operations teams trying to stop account takeovers and bad payouts.
  2 sacra
• The competitive set also shifts. Entrust is combining Onfido identity verification with adaptive authentication for privileged actions and high value transactions, and Okta has highlighted Persona for self service account recovery. That shows returning user verification is becoming a core identity workflow, not an edge feature.
  3 entrust 4 okta

The next step is for biometric re authentication to become a standard layer across the full lifecycle, from signup to every risky action after signup. MetaMap is well positioned to sell more modules into the same account because each new authentication use case reuses the original KYC record, raises switching costs, and pushes the product deeper into security infrastructure.