Account Recovery After DigiLocker Verification
Design account recovery for users with an earlier document check. Separate recovery evidence, account binding, sensitive access, and re-verification decisions.
Treat recovery and earlier document verification as separate decisions. Recovery establishes control of an account under your recovery policy. The earlier check records evidence tied to a purpose, time, and account.
A copy of a licence can be shared or stolen. Use a recovery method appropriate to the account and the risk of granting access. For reference, NIST's authentication guidance describes recovery methods and notifications for authentication systems. NIST SP 800-63B-4.
Define a recovery decision record
| Situation | Question to answer | Example action |
|---|---|---|
| User replaces a device | Can the user prove account control through an approved route? | Complete recovery and record the event |
| User changes the account email | Does policy require additional checks for sensitive actions? | Hold the action for review |
| Two accounts appear to match | Can an authorised reviewer establish the correct binding? | Review before merging |
| Earlier evidence has expired | Does the next activity require current evidence? | Request a new verification |
| Support receives a document copy | Does the approved recovery process accept this evidence? | Follow the recovery policy and safe intake route |
These are design options. Choose the rules for your account risks and approved verification purposes.
Work through a disputed account
A synthetic user has a verified licence result tied to account A. Someone opens account B with a similar name and asks support to move the result. The name match gives support a reason to review the case.
Keep the evidence attached to A while the review runs. Establish control of the relevant account through the approved process. Record any decision to change the binding and who authorised it.
Recovery can restore access without changing a document's expiry or increasing its verification assurance. Recheck the evidence before the next action that depends on it.
Test the sensitive transitions
- Recover an account with a current result.
- Recover an account with an expired result.
- Attempt to attach the result to another account.
- Try a support override without the required approval.
- Confirm the owner receives the applicable recovery notice.
Review pending verification attempts when an account binding changes. Close an attempt if its original context can no longer be trusted. Callback and account binding.
Review recovery with NamoID
NamoID engineers can help map recovery, application sessions, and document evidence to separate decisions. Share a synthetic account transfer or recovery scenario and your current policy. Message the NamoID team in Slack