> ## Documentation Index
> Fetch the complete documentation index at: https://www.cashfree.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# DigiLocker FAQs

> Find answers to common questions about Cashfree DigiLocker integration, including consent flows, supported documents, KYC use cases, and error handling.

<AccordionGroup>
  <Accordion title="What is DigiLocker?">
    DigiLocker is a government-backed platform that allows users to securely store and share official documents, such as Aadhaar, PAN, and Driving License.
  </Accordion>

  <Accordion title="How does Cashfree use DigiLocker for KYC?">
    Cashfree integrates with DigiLocker to enable a consent-based KYC process. You redirect users to the DigiLocker portal, where they log in and approve document sharing. Cashfree retrieves the verified data securely after user consent.
  </Accordion>

  <Accordion title="Why should I use Cashfree’s DigiLocker integration?">
    Cashfree’s DigiLocker flow is compliant with UIDAI guidelines and the Digital Personal Data Protection (DPDP) Act. It supports multiple document types, uses a trusted government portal, and requires minimal changes to your existing integration.
  </Accordion>

  <Accordion title="Which documents can I verify using DigiLocker?">
    You can verify Aadhaar, PAN, Driving License, and other government-issued documents supported by DigiLocker.
  </Accordion>

  <Accordion title="Does the user need to provide consent?">
    Yes. The user must log in to DigiLocker and explicitly approve document sharing. Cashfree retrieves data only after receiving consent.
  </Accordion>

  <Accordion title="Which industries can use this integration?">
    You can use this solution in banking, lending, insurance, logistics, fintech, trading, and mobility services to meet KYC and compliance requirements.
  </Accordion>

  <Accordion title="How does the verification process work?">
    Use the **Verify Account API** to check if the user has a DigiLocker account (optional).<br /><br />
    Use the **Create URL API** to generate a consent link.<br /><br />
    Redirect the user to the DigiLocker portal for login and consent.<br /><br />
    Use the **Get Verification Status API** to check the user’s progress (optional).<br /><br />
    Use the **Get Document API** to retrieve the verified document.
  </Accordion>

  <Accordion title="What statuses can I receive?">
    You can receive the following status values:<br /><br />

    * `PENDING` – The user has not completed the verification.
    * `AUTHENTICATED` – The user has logged in and given consent.
    * `EXPIRED` – The link expired before completion.
    * `CONSENT_DENIED` – When user rejects or denies consent.
  </Accordion>

  <Accordion title="Do I need to change my existing integration?">
    No. The data format remains the same as the previous flow. You can enable DigiLocker verification with minimal or no code changes.
  </Accordion>

  <Accordion title="Why does the e-Aadhaar field in the API response return 'N'?">
    The e-Aadhaar field in the API response returns **N** if the user hasn’t provided consent. Verify that the user has given consent, and then retry fetching the status.
  </Accordion>
</AccordionGroup>