> 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/accept-payments/integration-tools/e-commerce-and-plugins/easystore.md).

# EasyStore

EasyStore is a unified commerce and e-commerce platform that helps businesses manage both their online web stores and physical retail operations from a single dashboard. It lets merchants sell across multiple channels such as their own branded website, social media, and major online marketplaces while synchronizing inventory, customer data, orders, and loyalty programs in real time.

***

## Requirements

Before you integrate your EasyStore website with DOKU, make sure that you have fulfilled the following requirements:

1. Create a website with [EasyStore](https://admin.easystore.co/login)
2. Create a [DOKU Business Account](https://docs.doku.com/get-started/create-account#create-your-first-business-account)

***

## Integration Guide

1. [🇲🇾 Easy Store Integration](/accept-payments/integration-tools/e-commerce-and-plugins/easystore/easy-store-integration.md)

***

## Activate Payment Methods

You can activate more payment methods for your Shopify store by following the steps below:

1. Log in to [DOKU Dashboard](https://dashboard.doku.com/bo/login?utm_source=docs), and then access the side navigation bar
2. Select **Settings** from the menu
3. **Settings** page will appear. Under **Account** section, select **Service**
4. On **Service** page, click **ADD SERVICE**
5. Select the payment method you would like to activate
6. Click **ACTIVATE**.

Notes:

* Some payment methods can be activated instantly.
* Others may require approval from our Risk Screening Team before they become active.
* Certain payment methods may also require credential registration before activation is complete.
* Certain payment methods may be seen as disabled, because it can only be activated with the assistance of our Sales team.

***

## FAQ <a href="#faqs" id="faqs"></a>

<details>

<summary>Which payment methods does DOKU support on EasyStore?</summary>

Debit and credit cards, e-wallets, FPX, BNPL, and IPP. Availability depends on your account package and approval status.

</details>

<details>

<summary>Is there an additional fee for using EasyStore with DOKU?</summary>

Fees are based on your subscribed package and the MDR (Merchant Discount Rate) tied to that package, there is no additional charge on top of this.

</details>

<details>

<summary>How do I check the status of a payment/transaction, and do I need to set up a webhook or notification URL?</summary>

No webhook or notification URL setup is needed for EasyStore, DOKU automatically updates the payment status directly on your EasyStore dashboard. If you don't see a status update as expected, please submit a ticket to our support team.

</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 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/accept-payments/integration-tools/e-commerce-and-plugins/easystore.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.