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

# Sub Account

<figure><img src="/files/L5DbaJhkBy3sLVUCPNwz" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Availability: 🇮🇩 Indonesian Business Account only

This documentation covers Sub-Account V2 API only. For version differences, see FaQ
{% endhint %}

Sub Account is a powerful infrastructure layer that allows platforms to create sub-accounts, receive money, route, track, hold, and pay out funds across multiple account entities. It combines sub-account management, payment, and payout capabilities into one unified system.

***

## Why Sub-Account?

When you run a platform, marketplace, or multi-party business, all payments land in one merchant account and you're left figuring out whose money is whose.

```
Order #A-2013 · Siti    Rp 500,000   ─┐
Order #A-2014 · Andi    Rp 1,200,000 ─┤     YOUR MERCHANT ACCOUNT
Order #A-2015 · Budi    Rp 300,000   ─┤──▶  Rp 2.85M
Order #A-2016 · Dewi    Rp 850,000   ─┘     "Whose money is this, and
                                              how much goes where?"
```

Sub-Account eliminates this. Give every seller, agent, branch, or partner their own sub-account inside your platform with its own balance, history, split rules, and payout.

* **Sub Account, not bank accounts.** Created programmatically. One per party. Unlimited.
* **Route at the moment of payment.** Every inbound transaction distributed automatically, percentage or flat rule.
* **Real-time balances & ledger.** Every party sees what's theirs, what's held, and what's been paid out.
* **Payout, by API.** On demand disbursement to 100+ banks and e-wallets across Indonesia.

***

## Core Concepts

A sub-account is a digital balance container belonging to a party in your ecosystem, a seller, driver, branch, agent, etc. Each sub-account has a unique **Profile ID**, one or more **Account Numbers**, and can be organized in a **hierarchy** (parent-child, unlimited levels).

Each sub-account holds **three types of accounts**:

<table><thead><tr><th>Account Type</th><th width="196.0987548828125">Code</th><th width="236.5413818359375">Description</th><th>Withdrawable?</th></tr></thead><tbody><tr><td><strong>IDR Cash</strong></td><td><code>DOKU_MERCHANT_IDR</code></td><td>Main IDR balance, real money that can be spent or paid out</td><td>Yes</td></tr><tr><td><strong>Pending IDR</strong></td><td><code>DOKU_PENDING_IDR</code></td><td>Funds awaiting settlement from Checkout / Direct API payments</td><td>No</td></tr><tr><td><strong>Points</strong></td><td><code>DOKU_MERCHANT_POINT</code></td><td>Non cash value: loyalty points, credits, rewards</td><td>No (non-cash)</td></tr></tbody></table>

```
LEVEL 1 · MERCHANT
TokoMaju (BRN-TOKOMAJU)
│
├── L2 · SUB  Seller 001 (SAC-SELLER-001)
│   ├── 0000000001  DOKU_MERCHANT_IDR     IDR    Rp 1,000,000  ✓ withdrawable
│   ├── 0000000002  DOKU_PENDING_IDR          IDR    Rp 500,000    no
│   └── 0000000003  DOKU_MERCHANT_POINT   POINT  10,000 pts    non-cash
│
└── L2 · SUB  Seller 002 (SAC-SELLER-002)
    ├── 0000000004  DOKU_MERCHANT_IDR     IDR    Rp 2,500,000  ✓ withdrawable
    └── 0000000005  DOKU_PENDING_IDR          IDR    Rp 750,000    no
```

***

## Key Features

| Feature                       | Capability      | Description                                                                                                             |
| ----------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Payment Integration**       | Collect & Route | Collect payments through DOKU Checkout or Direct API and route them to sub-accounts automatically via `additionalInfo`. |
| **Automated Split Rules**     | Collect & Route | Configure percentage or flat-amount rules that automatically distribute every inbound payment.                          |
| **Payout to 100+ Banks**      | Collect & Route | Transfer funds from any sub-account to Indonesian banks via Transfer Inquiry → Transfer Payment API.                    |
| **Built-in BRI VA Top-Up**    | Shared          | Each sub-account gets a static BRI VA on registration. Funds land in real-time.                                         |
| **Debit API**                 | Deposit System  | Deduct from any sub-account per transaction — with double-entry ledger that credits the parent account.                 |
| **DOKU e-Wallet Integration** | Fund Oversight  | Link DOKU e-Wallet accounts to sub-accounts via Account Linking. Top-up petty cash and monitor from the Dashboard.      |
| **Points Ledger**             | Unified Ledger  | Track non-cash value — loyalty points, credits, cash-in-hand — via the PTS account.                                     |
| **Real-Time Monitoring**      | Shared          | Check balances, transaction status, and history per sub-account via API or dashboard.                                   |
| **Internal Transfer**         | Shared          | Move funds between sub-accounts on your platform.                                                                       |

***

## Who is it for?

| Segment                       | Description                                                                                      |
| ----------------------------- | ------------------------------------------------------------------------------------------------ |
| **Marketplaces & Platforms**  | Many sellers, one checkout. Each seller needs their own balance, payout, and ledger.             |
| **SaaS with Payouts**         | Creators, hosts, merchants earning through your product. You owe them money you're holding.      |
| **Logistics & COD**           | Cash collected on delivery, routed through couriers, owed to hundreds of shippers daily.         |
| **Multi-Branch & Franchise**  | One brand, many outlets. Revenue, royalties, and pool funds distributed by rule and region.      |
| **Agent & Reseller Networks** | Distributors, insurance agents, field sales — each with a deposit balance and commission ledger. |

***

## Two Services

Sub Account offers two services in the DOKU Dashboard. [Contact Sales](https://www.doku.com/en-us/contact-sales) to activate.

{% tabs %}
{% tab title="Collect and Route / Deposit System / Fund Oversight" %}
One service activation, three capabilities covering all money-flow use cases:

| Capability          | What it does                                                                                                        | Guide                                                                              |
| ------------------- | ------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **Collect & Route** | Accept payments → Route → Payout. Money in via Checkout/Direct API, split rules, payout to 100+ banks.              | [Guide →](https://docs.doku.com/wallet-as-a-service/sub-account/collect-and-route) |
| **Deposit System**  | Top-up → Debit → Monitor. Money in via built-in BRI VA (real-time), debit per transaction with double-entry ledger. | [Guide →](https://docs.doku.com/wallet-as-a-service/sub-account/deposit-system)    |
| **Fund Oversight**  | DOKU e-Wallet integration. Top-up staff wallets, monitor balances, no API required.                                 | [Guide →](https://docs.doku.com/wallet-as-a-service/sub-account/fund-oversight)    |
| {% endtab %}        |                                                                                                                     |                                                                                    |

{% tab title="Unified Ledger" %}
Non-cash ledgering — no money flow through DOKU. Track points, credits, and internal balances via the `DOKU_MERCHANT_POINT` (PTS) account.

* PTS credit via Transfer API
* PTS debit via Debit API
* PTS debit cancel via Debit Cancel API
* Balance inquiry and transaction history
  {% endtab %}
  {% endtabs %}

***

## Payment Method Compatibility

| No | Payment Method              | Checkout API | Direct API SNAP |
| -- | --------------------------- | ------------ | --------------- |
| 1  | Virtual Account (All Banks) | Yes          | Yes             |
| 2  | Credit Card                 | Yes          | -               |
| 3  | QRIS                        | Yes          | Yes             |
| 4  | OVO                         | Yes          | No              |
| 5  | DANA                        | Yes          | No              |
| 6  | ShopeePay                   | Yes          | No              |
| 7  | LinkAja                     | Yes          | No              |
| 8  | DOKU e-Wallet               | Yes          | Yes             |
| 9  | Alfa Group                  | Yes          | -               |
| 10 | Indomaret                   | Yes          | -               |

> **Note:** Payment method compatibility is updated regularly. Check back for the latest supported channels.

***

## How Sub-Account Compares

| Dimension          | Split Settlement                      | Domestic Payouts                    | **Sub Account**                              |
| ------------------ | ------------------------------------- | ----------------------------------- | -------------------------------------------- |
| Whose money moves? | Yours, to your own banks              | Yours, out to anyone                | **Many parties money, on your platform**     |
| Per-party balance  | None                                  | None                                | **Real-time, per sub-account**               |
| Fund routing       | Batched at settlement                 | Not applicable                      | **Automatic, per payment**                   |
| Recipient count    | Up to 10 bank accounts\*              | Many, one-shot or batch             | **Many Bank Account**                        |
| Ideal job          | Route settlement to your own accounts | Mass disbursement, payroll, vendors | **Infrastructure for multi party platforms** |

***

## Access Channels

{% tabs %}
{% tab title="API" %}
REST endpoints for every action — register sub-accounts, configure routing rules, inquire balances, process payouts.

Available endpoints:

* Register Sub Account
* Transfer Inquiry / Payment
* Debit / Debit Cancel
* Balance Inquiry
* Transaction Status / History
* Split Rules

[Explore Sub Account V2 API Docs Here!](https://developers.doku.com/wallet-as-a-service/sub-account/sub-account-v2/integration-guide)
{% endtab %}

{% tab title="Dashboard" %}
A full console with two main menus:

* **Sub Account V2:** create and manage sub-accounts, check balances and transactions history
* **Fund Oversight:** manage DOKU e-Wallet integration, link/unlink e-Wallet accounts to sub-accounts
  {% endtab %}
  {% endtabs %}


---

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