Re-verification

Re-checking an existing user's identity when a specific trigger calls for it, such as a high-value transaction, an account recovery, or a scheduled compliance refresh.

For example, a customer who loses their phone and asks to recover their account might take a fresh selfie, and the service compares it with the face captured when they first signed up.

A fresh biometric sample, or for higher-risk triggers a full proofing re-run, compared against the record captured at original enrollment. The comparison produces a new match score or assurance level; the one from signup doesn't carry over.

The usual triggers include:

• Account recovery, when a person has lost the login method they originally set up.
• High-value or unusual activity, such as a large transfer or a change to payout details.
• Account abandonment, when an account has sat inactive for a long time and then comes back to life.
• Regulatory refresh, when a rule requires periodic recertification of customer identity.

Re-verification sits next to terms that are easy to mix up:

• Identity verification (IDV) runs once, when the relationship starts, while re-verification repeats the check later.
• Authentication checks that a returning person holds the right login proof, while re-verification confirms the person is the one who enrolled.
• Perpetual KYC refreshes customer records continuously when risk changes, and re-verification is one way a program can carry out that refresh.