> 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/wallet-as-a-service/sub-account/faq.md).

# FAQ

## API Versioning & Migration

<details>

<summary>What is the difference between V1 and V2?</summary>

V2 is the latest version of the Sub Account API with significant improvements over V1:

|                   | V1                                | V2                                        |
| ----------------- | --------------------------------- | ----------------------------------------- |
| **Status**        | Live, no longer receiving updates | Live, actively developed                  |
| **Split rules**   | -                                 | Automatic per-transaction splitting       |
| **Account types** | Single account type               | IDR + Pending IDR + Points                |
| **Built-in VA**   | -                                 | Auto-assigned DOKU BRI VA per sub-account |
| **API design**    | Legacy                            | Standardized headers, HMAC-SHA512 auth    |

</details>

<details>

<summary>I'm a new merchant. Which version should I use?</summary>

**Use V2.** All new integrations should use the V2 API for the latest capabilities and best experience. See the Sub Account V2 API documentation to get started.

</details>

<details>

<summary>I'm an existing merchant on V1. Do I need to do anything?</summary>

**No.** V1 is still live and fully supported. Your integration will continue to work as-is with no disruption.

However, V1 is **no longer receiving updates,** all new features and improvements are built on V2 only.

</details>

<details>

<summary>Can I migrate from V1 to V2?</summary>

Migration from V1 to V2 is **not yet available**. We are working on a migration path and will notify existing merchants when it's ready.

In the meantime, your V1 integration continues to work normally.

</details>

<details>

<summary>Will V1 be shut down?</summary>

There is **no planned shutdown date** for V1. Existing merchants can continue using V1. We will communicate well in advance if any changes are planned.

</details>

## General

<details>

<summary>How do I activate Sub-Account?</summary>

Sub-Account requires verification from the Sales team. [Contact Sales](https://www.doku.com/en-us/contact-sales) to get started.

</details>

<details>

<summary>Does DOKU need a financial institution license to offer Sub-Account?</summary>

No. Sub-Account operates as a **technology infrastructure layer**, not as a financial institution. It provides the tools to manage fund flows, but DOKU itself is not acting as a bank or e-money issuer.

</details>

<details>

<summary>How is Sub-Account accessed?</summary>

Two ways:

1. **API:** For developers to integrate programmatically into your platform
2. **Dashboard:** A web-based interface for operations and finance teams

Both show the same data in real time.

</details>

<details>

<summary>Is there a limit on how many sub-accounts I can create?</summary>

No. There is **no fixed limit** on the number of sub-accounts you can create. Scale as your business grows.

</details>

<details>

<summary>How is pricing structured?</summary>

[Contact Sales](https://www.doku.com/en-us/contact-sales) for pricing details.

</details>

<details>

<summary>What payout methods are supported?</summary>

* **Bank transfers:** To 100+ Indonesian and international banks
* **E-wallets:** To DOKU wallets

</details>

<details>

<summary>Can Sub-Account manage external accounts?</summary>

Yes. Sub-Account supports both **internal transfers** (between sub-accounts on your platform) and **external transfers** (to bank accounts and e-wallets outside the system).

</details>

<details>

<summary>What currencies are supported?</summary>

Sub-Account primarily supports **IDR** (Indonesian Rupiah). [Contact Sales](https://www.doku.com/en-us/contact-sales) for multi-currency availability.

</details>

## Developer

<details>

<summary>When can I payout funds after receiving a payment?</summary>

It depends on how the money came in:

| Money-In Source               | Payout availability                                                                   |
| ----------------------------- | ------------------------------------------------------------------------------------- |
| **BRI VA built-in top-up**    | Immediately, real-time settlement to `DOKU_MERCHANT_IDR`                              |
| **Checkout API / Direct API** | After settlement, unds must move from `DOKU_PENDING_IDR` to `DOKU_MERCHANT_IDR` first |

> Merchants **cannot** initiate transfers from `DOKU_PENDING_IDR`. It is system-managed.

</details>

<details>

<summary>What is the double-entry ledger and Level 1 profile?</summary>

When a Debit API is called on a sub-account, the system can automatically credit the `DOKU_MERCHANT_IDR` of a Level 1 (merchant/platform) profile. This enables platforms to aggregate funds from multiple sub-accounts before paying out.

</details>

<details>

<summary>How do I test my integration?</summary>

Use the **Sandbox environment** (`https://api-sandbox.doku.com`) with your sandbox credentials. No real money is moved in sandbox.

</details>

<details>

<summary>How do I know when a transaction completes?</summary>

Two ways:

1. **Notifications,** DOKU sends webhooks to your callback URL.
2. **Polling,** Call the SAC Transaction Status API with your reference number.

</details>

<details>

<summary>What happens if a transfer fails?</summary>

The funds remain in the source sub-account. Check the Transaction Status API for the failure reason, and refer to Error Codes for troubleshooting.

</details>

<details>

<summary>Where can I find Account Linking FAQ?</summary>

See the Fund Oversight guide for questions about Account Linking, referral codes, linking/unlinking flows, and data visibility.

</details>

<details>

<summary>Where can I find V1 and V2 API documentation?</summary>

* V1 API documentation is still available at the [Sub Account V1 API docs](https://developers.doku.com/wallet-as-a-service/sub-account).
* V2 API documentation available at the [Sub Account V2 API docs](https://developers.doku.com/wallet-as-a-service/sub-account/sub-account-v2).

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.doku.com/wallet-as-a-service/sub-account/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.