NAD Certificate Verification: Check Before Consent

Short answer: Before approving a NAD certificate verification request, confirm who is asking, why the check is needed and which academic award it concerns. Use the official consent flow after those details agree with your genuine application or enquiry. Keep the decision and reference, then ask the receiving organisation what happens next. Consent to a verification is not an admission decision, a job offer or permission to use your account credentials.

This guide helps students and graduates review an academic-award verification request through the DigiLocker National Academic Depository ecosystem. It is an evergreen decision checklist, not a report of a new October rule. No personal certificate or request has been accessed for this article, and no consent has been granted on anyone’s behalf.

What NAD certificate verification is asking you to do

The official NAD verifier guidance describes a process in which a verifier registers through API Setu, obtains individual consent, supplies relevant details and receives a verification response. This is a route for checking an academic award, rather than a request to give an organisation unrestricted control over your DigiLocker account.

Keep three roles separate. The academic institution issues the award. You are the person whose record is involved and whose consent is sought in the described process. The verifier is the organisation seeking the check. Identifying those roles helps you ask the right party a question without treating every message as an instruction from your university.

Also distinguish retrieval from verification. NAD’s student guidance explains how students obtain issued awards. Having a document available in your account does not mean that every later request to share or verify it has already been approved. Review each genuine request in its own context.

The decision in this guide is limited: whether the specific request is understood and should be authorised through its official route. It does not decide whether the qualification meets an employer’s criteria, whether an overseas institution recognises it, or whether a particular admission condition is satisfied.

Confirm who wants the verification

Start with the process you actually initiated. Are you applying to an institution, responding to an employer, or completing another stated requirement? Match the requesting organisation to that process. If a verification request arrives without an expected context, pause and ask for an explanation before approving it.

Check the name of the requester against an independently verified contact route. Use the organisation’s official website, a known application portal or a contact already established in the genuine process. Do not rely only on the phone number or reply address included in the unexpected message asking you to act.

A background-check provider may be involved on an organisation’s behalf. Ask the organisation to confirm that relationship and the relevant application reference. An unfamiliar vendor name does not automatically establish fraud, but neither does a claim to be a partner establish authority. Get the connection explained before sending personal records.

Write down the organisation and contact used for this check. If the response does not identify the request you received, explain the discrepancy. A vague reassurance that “all candidates get this message” does not answer whether this particular request concerns your application and the correct award.

For suspicious email links or sender details, use our Gmail phishing-email checks. The purpose is to establish a genuine route before interacting, not to decide legitimacy from a logo or the sender’s display name alone.

Check the purpose and the exact academic award

Identify what is to be verified. A final degree, provisional certificate and semester marksheet are separate records. Compare the issuer, course, examination or award year and document type with the requirement you are trying to satisfy. Do not approve a mismatched document merely because the institution’s name is familiar.

Ask what the verification will be used for and which application it supports. If the request is broader than the stated need, seek clarification. For example, a request concerning one qualification should be understandable in terms of that qualification; you should not have to infer why unrelated records are being requested.

The NAD FAQ describes verification as subject to student consent and says a student can approve or deny requests for particular certificates. It also describes online and offline consent routes. Read the actual request presented to you; do not assume that a generic description on a help page answers every question about a particular recipient’s use of information.

Before acting, prepare a short decision note with these fields:

• Requesting organisation and any confirmed service provider.
• Genuine application or case reference.
• Purpose the requester has stated.
• Issuer and exact award requested.
• Any mismatch or question awaiting an answer.

This note is a personal review tool, not an additional government form. Keep it privately. It helps prevent a hurried response to the wrong request and gives you a clear basis for a follow-up if two organisations later describe the same verification differently.

Read the consent screen before making a decision

Open the legitimate service route yourself where possible and check the request in that context. Read the names, document details and decision options shown. Do not let a message’s urgency replace the review. If the screen describes a different organisation or award from the one confirmed, stop and ask the requester to correct the discrepancy.

Follow the authentication instructions in the official flow. Do not send your password, login OTP or recovery information to a person who offers to complete consent for you. Authentication in the proper service and disclosing a code to another person are different actions, even when that person says they are assisting.

If you do not understand the request, ask a focused question before choosing. State the field or scope that is unclear. If you decide not to authorise it, inform the genuine receiving organisation through its verified channel and ask what alternative process, if any, it permits. Do not assume there is always an alternative or that declining has no consequence for the application.

NAD’s FAQ says an unaddressed request can become ineffective and may need to be initiated again. It does not give you a universal deadline for every admission or employment case. Check the actual request and the receiver’s written requirements promptly rather than assuming an unanswered notification will wait indefinitely.

Keep evidence of the decision and the next step

After an action, retain the reference, date, requester, award and result displayed. If the service provides a confirmation or acknowledgement, save it in your private application folder. Avoid placing a full certificate or a consent screenshot containing identifiers in a public group simply to ask whether you completed the task.

Then confirm what remains with the receiving organisation. A record that you authorised verification does not prove that the receiver has reviewed the response or made its final decision. Ask whether it has the verification it needs and whether another document or step is outstanding.

Keep a distinction between a consent problem, a verification response and an application outcome in your notes. “I approved the request” and “my admission is confirmed” are not equivalent statements. This separation makes a status enquiry more precise and avoids repeating a step that may already be complete.

If there are several applications, maintain separate references. A verification for one organisation should not be assumed to complete a different organisation’s process. Use each receiver’s stated instructions and preserve the relevant acknowledgement with that application’s records.

Handle a wrong award, an unfamiliar request or an error

For a wrong award or incorrect personal detail, identify the precise discrepancy. Ask the requester to correct a mistaken request; ask the issuing institution about an error in its academic record. Do not edit a certificate file yourself to make it match what a verifier expects.

For a technical error, record the stage and exact message. Did the service fail before the request appeared, during authentication or after you selected a decision? Describe only what you observed. A page error does not establish that the award is invalid or that the requester has completed its check.

For an unexpected request, contact the organisation independently and ask whether it initiated that exact verification. Until that is established, do not provide more information merely to help the unknown sender “locate” your account. If the organisation disowns the request, preserve the evidence and use the service’s official support route.

For broader document questions, our DigiLocker issued-document and validity explainer discusses issued records and personal uploads. This guide does not repeat the general legal-validity question or provide a missing-record retrieval procedure; its purpose is reviewing a consent request before authorisation.

A worked request-review pattern

Consider a request received during an application where a third-party verification company is named. First ask the receiving institution or employer to confirm the provider through its known contact. Next match the reference and award. If the message asks for a final degree but your application concerns a different certificate, ask which record is required before deciding.

Once the request is explained and the official flow shows the correct details, you can make the consent decision yourself and retain the result. You then check with the receiver whether anything remains. This example describes a review method; it does not claim that any named organisation has used that process or promise a favourable application outcome.

Read privacy information without making blanket assumptions

NAD’s published privacy policy describes handling of personal information and contains permitted-disclosure provisions. Its displayed last-modified date is 26 June 2020. That page should not be portrayed as a new October privacy rule or a promise about every outside verifier’s practices.

For a particular organisation, ask about its own stated purpose, contact and data-handling policy where unclear. Do not infer that approving one verification gives you an automatic way to erase every copy already held elsewhere. If you later want to change or withdraw an instruction, ask the relevant service and recipient what can be changed and what has already happened.

Frequently asked questions

Must I give my DigiLocker password to the verifier?

No assistance should be treated as a reason to disclose login credentials. Complete the relevant official authentication and consent steps yourself.

Does consent guarantee a job or admission?

No. Verification and the receiving organisation’s decision are separate. Confirm its requirements and outcome through the genuine application channel.

Can I assume every verification request is genuine?

No. Establish the requester, relationship, purpose and award. An unexpected request needs an independent check before you decide.

Final NAD certificate verification checklist

Confirm the requester, match the purpose and exact award, resolve discrepancies, read the official consent flow and record your decision. Follow up with the genuine receiver about its next step. Keep academic-record access under your control without assuming that a verification authorisation settles the entire application.

---