During a notification-based verification, what might the customer be asked to do?

During a notification-based verification, what might the customer be asked to do?

• A. Enter password
• B. Provide SSN
• C. Upload their ID
• D. Answer a security question

Answer: (C)

The idea behind notification-based verification is to confirm who the customer is using something verifiable, without needing in-person access. Uploading a government-issued ID provides concrete, verifiable details (name, photo, document number) that the agent can compare to account records, making it a reliable way to prove identity remotely before allowing sensitive actions. Other options aren’t as well suited to this flow: a password is something the user already knows and isn’t typically requested through a notification; answering a security question is less reliable and can be guessed or reused; providing an SSN is highly sensitive and not a standard step in this notification process. Uploading the ID aligns with the goal of securely verifying identity in this scenario.

The idea behind notification-based verification is to confirm who the customer is using something verifiable, without needing in-person access. Uploading a government-issued ID provides concrete, verifiable details (name, photo, document number) that the agent can compare to account records, making it a reliable way to prove identity remotely before allowing sensitive actions. Other options aren’t as well suited to this flow: a password is something the user already knows and isn’t typically requested through a notification; answering a security question is less reliable and can be guessed or reused; providing an SSN is highly sensitive and not a standard step in this notification process. Uploading the ID aligns with the goal of securely verifying identity in this scenario.