> For the complete documentation index, see [llms.txt](https://docs.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doku.com/mobile-apps/doku-e-wallet/account-verification.md).

# Account Verification

DOKU e-Wallet Account Verification

## FAQ

<details>

<summary>Can I use the same identity card for more than 1 DOKU e-Wallet account?</summary>

Your identity card can only be used for one account. If you have used your ID card (SIM, KTP, or Passport) to upgrade your account, you cannot use the same ID card again for another account.

</details>

<details>

<summary>Why hasn't my DOKU e-Wallet account upgrade request been processed?</summary>

DOKU e-Wallet account upgrade process typically takes up to 2×24 hours. If you have not received a verification result after this period, please contact us at <care@doku.com> by providing your DOKU ID and details of the issue.

</details>

{% hint style="info" %}
If your questions cannot be found here, please visit [DOKU Help Center](https://help.doku.com) for further information.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.doku.com/mobile-apps/doku-e-wallet/account-verification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.