> 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/subscription-and-billing/flexibill/account-billing/account-billing-activation.md).

# Account Billing Activation

{% hint style="info" %}
This page is a tutorial for activating **Account Billing**. For a full feature overview → [Account Billing](/subscription-and-billing/flexibill/account-billing.md)
{% endhint %}

Learn how to activate Account Billing on your DOKU Dashboard. Before the feature can be used, at least one compatible payment channel must be enabled and configured on your account — and this requires coordination with your DOKU Account Manager.

## Prerequisites

Account Billing activation has two tiers of prerequisites with different owners and lead times.

#### Tier 1 — Platform (Self-Serve)

* [ ] **FlexiBill is activated** — [Activate FlexiBill](/subscription-and-billing/flexibill/activation.md)

This step is self-serve and takes effect immediately.

#### Tier 2 — Payment Channel (Requires Account Manager)

* [ ] At least one of the following payment channels is active on your DOKU account:
  * **Credit Card** — with the correct payment type combination for your acquirer
  * **Direct Debit** — for the specific bank issuer(s) available on your account

{% hint style="warning" %}
Payment channel activation is **not self-serve**. It requires coordination with your DOKU Account Manager and may involve acquirer review. Allow several business days before the channel is active. Complete Tier 2 before starting the activation steps below.
{% endhint %}

## Payment Channel Requirements

#### Credit Card

Account Billing requires **two Credit Card payment types working together**: one for the initial card tokenization (SALE) and one for all subsequent recurring charges (RECURRING or MOTO). Both must be active on your account.

**Payment Types**

<table><thead><tr><th width="133.85546875">Payment Type</th><th width="419.22265625">Role</th><th>Required</th></tr></thead><tbody><tr><td><strong>SALE</strong></td><td>Handles the initial card tokenization — the registration transaction that securely vaults the customer's card as a token. This is the void charge executed when a customer first registers.</td><td>✅ Always required</td></tr><tr><td><strong>RECURRING</strong></td><td>Processes all subsequent auto-debit charges against the stored token, using a RECURRING transaction flag.</td><td>✅ If your acquirer supports RECURRING</td></tr><tr><td><strong>MOTO</strong></td><td>Processes all subsequent auto-debit charges against the stored token, using a MOTO (Mail Order Telephone Order) transaction flag. Alternative to RECURRING for acquirers that use MOTO for card-not-present recurring charges.</td><td>✅ If your acquirer supports MOTO</td></tr></tbody></table>

**Valid Combinations**

The combination you need is **determined by your acquirer** — not a merchant preference. Both combinations always include SALE:

<table><thead><tr><th width="191.8828125">Combination</th><th>When It Applies</th></tr></thead><tbody><tr><td><strong>SALE + RECURRING</strong></td><td>Your acquirer processes recurring auto-debit charges using the RECURRING transaction flag</td></tr><tr><td><strong>SALE + MOTO</strong></td><td>Your acquirer processes recurring auto-debit charges using the MOTO transaction flag</td></tr></tbody></table>

{% hint style="info" %}
**Not sure which combination applies to you?** Ask your DOKU Account Manager: *"For my Credit Card acquirer, should I request SALE + RECURRING or SALE + MOTO for Account Billing?"* They will confirm the correct combination based on your acquirer's configuration.
{% endhint %}

**Why SALE Is Always Required**

SALE is the tokenization transaction. When a customer registers their card, Account Billing executes a SALE charge that is immediately voided — no money is collected. This step creates the secure token that all future RECURRING or MOTO charges are billed against. Without SALE, there is no token, and no subsequent charge can be processed.

→ See [How Billing Dates Work](/subscription-and-billing/flexibill/account-billing.md#how-billing-dates-work) for the full registration flow including the void charge behavior.

#### Direct Debit

Direct Debit enables automated balance deductions directly from a customer's linked bank account. There are no payment type variants — activation is straightforward. However, Direct Debit availability is **issuer-specific**: the bank issuers available to your account depend on your acquirer configuration.

* Customer authorizes the debit mandate once during registration
* Subsequent charges are pulled automatically from their bank account on each billing date
* No card credential re-entry required for future billing cycles

{% hint style="info" %}
Contact your **DOKU Account Manager** to confirm which bank issuers are available for Direct Debit on your account before requesting activation. Currently support MANDIRI and BRI.
{% endhint %}

## Step-by-Step Guide

{% stepper %}
{% step %}

#### Open Account Billing

Log in to [DOKU Dashboard](https://dashboard.doku.com/), then navigate to **FlexiBill → Account Billing** from the left sidebar.

If Account Billing has never been activated, you will land on the activation page.

<figure><img src="/files/9iTnK75LQJkw8tGL2wA3" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Review and Agree to Terms & Conditions

Read the Account Billing Terms & Conditions and click **Agree** to proceed.
{% endstep %}

{% step %}

#### Verify Payment Channel Status

The dashboard displays the current activation status of your payment channels under the **Cards**, **Direct Debit**, and **e-Wallet** tabs.

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

**Channel status states:**

<table><thead><tr><th width="169.48828125">Status</th><th>Description</th></tr></thead><tbody><tr><td><strong>Active</strong></td><td>The channel is live and ready to use for Account Billing. Proceed to Step 4.</td></tr><tr><td><strong>Pending</strong></td><td>A channel activation request has been submitted and is awaiting acquirer review. No action needed — wait for approval confirmation from your Account Manager.</td></tr><tr><td><strong>No Data / Inactive</strong></td><td>No compatible channel is active. An <strong>"Account Billing Cannot Be Used Yet"</strong> banner will appear.</td></tr></tbody></table>

If no compatible channel is active, click **Request Activation** to submit a channel activation request to DOKU.

{% hint style="warning" %}
If you are requesting Credit Card activation, specify the correct payment type combination for your acquirer (SALE + RECURRING or SALE + MOTO) when submitting the request. An incorrect combination will require a resubmission and extend the activation timeline.
{% endhint %}
{% endstep %}

{% step %}

#### Configure Bill Execution Preferences

<img src="/files/xMqGnidQ0wOn716YYabh" alt="Bill execution Preferences" height="307" width="624">

Once at least one compatible payment channel shows **Active** status, click **Next** to configure your billing execution settings:

<table><thead><tr><th width="225.99609375">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Time Execution</strong></td><td>The daily time window (HH:MM WIB) when the scheduler attempts to process charges on each billing date. Default: 00:00 WIB.</td></tr><tr><td><strong>Send One Bill/Month</strong></td><td>When enabled, ensures a customer is only successfully charged once per calendar month — even if multiple billing dates or retry dates are configured. All subsequent attempts in the same month after a successful charge are automatically set to <code>ALREADY_PAID</code>.</td></tr><tr><td><strong>Freeze the Card</strong></td><td>When enabled, automatically bypasses cards previously flagged by the processor as Stolen, Frozen, or Restricted — avoids unnecessary transaction fees on cards that will not succeed.</td></tr><tr><td><strong>URL Amount</strong></td><td>(Optional) For dynamic billing amounts — provide an endpoint URL that the system queries just before each scheduled charge to retrieve the exact <code>billing_amount</code> for that cycle.</td></tr><tr><td><strong>URL Notification</strong></td><td>(Optional) Default fallback endpoint for receiving payment execution results for every automated charge attempt.</td></tr><tr><td><strong>New Recurring Alert URL</strong></td><td>(Optional) Default endpoint for receiving success callbacks when a customer's card is registered and tokenized.</td></tr></tbody></table>

{% hint style="info" %}
**Time Execution** and **Send One Bill/Month** work together with calendar-based billing dates. If you configure retry dates (e.g., 5th, 6th, 7th) for a customer, Time Execution controls what time charges are attempted on each of those dates, and Send One Bill/Month ensures the customer is not charged again once a retry succeeds. → [How Billing Dates Work](broken://pages/5151f0d346add81e168768d4331dc6deac895a9a#how-billing-dates-work)
{% endhint %}

Click **Save** to apply the configuration.
{% endstep %}

{% step %}

#### Complete Activation

Once at preference configured, click **Next** to complete the activation process.

Account Billing is now ready to use.

<figure><img src="/files/CgMSZNWpnDDqskdpn8IA" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## What's Next

Once Account Billing is activated and configured, choose your integration model:

* 👉 [DOKU Hosted Scheduler](broken://pages/3ce41dce1fe775c299e446263889b1d436839282) — Let DOKU fully manage the billing schedule and charge execution
* 👉 [Merchant Hosted Scheduler](broken://pages/6a64ce07cd943d1376872313cc430f4169464bff) — Control your own billing schedule and trigger charges on demand
* 👉 [Connectivity & File Security (SFTP)](broken://pages/9b7dbec1aadfd9548c89eb6bc5c2645118f726eb) — Set up secure SFTP access for bulk file-based billing operations

## FAQ

<details>

<summary>Why is SALE always required even though Account Billing charges customers automatically?</summary>

SALE is the tokenization step — it creates the secure card token that all future auto-debit charges are billed against. Without an initial SALE transaction, no token exists and no RECURRING or MOTO charge can be processed. The SALE on registration day is immediately voided, so no money is collected — it is purely a technical prerequisite for tokenization.

</details>

<details>

<summary>What is the difference between RECURRING and MOTO for subsequent charges?</summary>

Both process auto-debit charges against a stored card token — the difference is in the transaction flag sent to the acquirer. RECURRING uses a recurring transaction flag; MOTO uses a Mail Order Telephone Order flag. The behavior for Account Billing is the same from the merchant's perspective. Which one you use is determined by your acquirer, not your preference — confirm with your DOKU Account Manager.

</details>

<details>

<summary>How do I know which Credit Card combination — SALE + RECURRING or SALE + MOTO — applies to my account?</summary>

Ask your DOKU Account Manager. The correct combination depends on which acquirer processes your Credit Card transactions and which transaction flags that acquirer supports for recurring billing. Your Account Manager will confirm the exact combination to request.

</details>

<details>

<summary>How long does payment channel activation take?</summary>

Payment channel activation requires acquirer review and is not instant. Allow several business days from the time you submit the request. Your DOKU Account Manager will notify you once the channel is active. You can check the current request status under the **Cards** or **Direct Debit** tabs on the Payment Method screen in the dashboard.

</details>

<details>

<summary>Can I use both Credit Card and Direct Debit at the same time?</summary>

Yes. Both channels can be active simultaneously. Each individual customer registration specifies which payment method to use for their recurring charges — the two channels operate independently.

</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/subscription-and-billing/flexibill/account-billing/account-billing-activation.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.