> 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-and-security.md).

# Account & Security

Explore account types and security settings.

## Account Types: Basic & Premium

Your account starts as **Basic** after registration. Upgrade to **Premium** to unlock all features and higher limits.

| Type                                 | Basic        | Premium      |
| ------------------------------------ | ------------ | ------------ |
| Maximum balance                      | Rp2,000,000  | Rp20,000,000 |
| Monthly transaction limit            | Rp20,000,000 | Rp40,000,000 |
| Transfer to banks & other DOKU users | ❌            | ✅            |
| Cash withdrawal                      | ❌            | ✅            |
| Transfer to other e-wallets          | ❌            | ✅            |
| Premium themes                       | ❌            | ✅            |

### Upgrade to Premium

Have a valid identity document ready: **KTP, driver's license (SIM), or passport**.

1. On the Home screen, tap the **Verify Your Data** banner.
2. Select **Upgrade Account**, then choose your document type.
3. Fill in the details as shown on your document.
4. Take a photo of your document, then a selfie while holding it. Make sure both are clear and not blurry.
5. If you're using a KTP, complete face verification.
6. Review your details, then submit.

Verification takes up to **2 business days**. We'll send the result by email and in-app notification.

{% hint style="info" %}
One identity document can only be used for one DOKU e-Wallet account.
{% endhint %}

***

## Account Security

Security is the foundation of DOKU e-Wallet. We use international-standard security infrastructure and layered protection on your account.

### Account Protection

* **Two-step login:** Sign in with your PIN and an OTP code sent to WhatsApp.
* **PIN for every transaction:** Payments and transfers are always confirmed with your PIN.
* **Automatic account lock:** If you enter the wrong PIN 3 times in a row, your account is locked for your protection.
* **PIN history:** Your new PIN can't be the same as any of your last 3 PINs.
* **Multi-step verification:** Changing your mobile number or email goes through several verification steps.

### PIN and Account Management

* **Change PIN:** **Account** > **Security** > **Change PIN**, then verify with the WhatsApp OTP.
* **Forgot PIN:** Tap **Forgot PIN** on the PIN screen or in the **Security** menu, then verify with an OTP.
* **Locked account:** Tap **Send Verification Code**, enter the OTP from your email, then the OTP from WhatsApp.

### Tips

{% hint style="danger" %}
**Never share your PIN or OTP code with anyone**, including anyone claiming to be from DOKU.
{% endhint %}

* Make sure you can always access your registered mobile number and email.
* Check the recipient and amount before confirming a transaction.
* Notice changes you didn't make, or suspect your account has been taken over? Report it right away to **<care@doku.com>** with your registered mobile number and what happened.


---

# 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-and-security.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.