'No User Found' error occurs during first-factor authentication on the SDK. What could be causing this issue?

• Related Articles

• 'You are not authorized to take this action' error occurs when invoking the JS SDK. What could be causing this issue?

  Typically, this issue arises due to an incorrect user identifier passed in the digio.esign function. Kindly recheck the identifier(DID) with respect to the document you have generated.

• How does user authentication happen using Aadhar esign mandates?

  eSign Mandate authentication is triggered via Digio link sent over SMS/Email or SDK trigger using eNACH id and identifier provided by Digio. In both cases below screens open - The first step is first factor authentication of user Mobile/Email as per ...

• 'document not found' error occurs. Why is this happening?

  This error typically arises when there's a mismatch between the document's sandbox/production status and where it's being referenced.

• How does user authentication happen using API mandate?

  An authentication is triggered via Digio link sent over SMS/Email or SDK trigger using eNACH id and identifier provided by Digio. In both cases below screens open - NPCI then redirects the Customer to the Destination Bank’s NetBanking or to a Debit ...

• Why am I encountering the error "Provided document or docket_id is invalid"?

  This error occurs when an incorrect or incomplete Document ID (DID) is provided. The DID can be found in the URL bar with the DID prefix