PBIC identity assurance

Last update:
Aug 21, 2026
This section explains how Phone‑Based Identity Confirmation (PBIC) fits within the broader identity assurance approach used by the Aikyam Identity Platform, while maintaining PBIC’s recovery‑only scope.
PBIC provides phone‑based verification during account recovery to help confirm access to a phone number and evaluate its association with a user’s identity. This verification contributes to the overall assessment of identity during recovery but does not represent full identity proofing and does not independently grant access.

How PBIC contributes to identity assurance

  • PBIC is used during account recovery when additional confirmation is needed to verify access to a phone number and its association with the user’s identity.
  • PBIC evaluates:
    • Access to a phone number, and
    • Risk based association between the phone number and the user’s identity.
  • PBIC outcomes are considered alongside other recovery signals to determine whether the recovery flow can proceed.

Scope and limitations

  • PBIC is designed only for account recovery and does not apply to normal sign‑in or primary authentication flows.
  • PBIC provides moderate assurance appropriate for recovery use cases and may be combined with other controls depending on application or tenant requirements.
  • PBIC does not replace stronger verification methods that may be required in other identity assurance contexts.

Outcome handling

  • PBIC produces a verification outcome that indicates whether phone‑based identity confirmation was successful.
  • Final access and recovery decisions are made by the consuming application or platform based on the overall recovery context.
  • PBIC outcomes are logged and auditable to support compliance and operational review.

On this page

Powered by Aikyam @2025 All rights reserved