> 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/changelog/march-2024/new-payment-method-dana.md).

# New Payment Method: DANA

Welcome DANA as a New Payment Channel!

We're excited to announce that DANA is now available as a new payment channel on DOKU! This integration allows your customers to pay for your products and services using their preferred DANA e-wallet, providing them with a convenient and secure checkout experience.

**Benefits for Your Business:**

* **Expand Your Reach:** Offer DANA as a payment option to attract a wider customer base who use DANA e-wallet.
* **Simplify Transactions:** Facilitate seamless and secure payments for your customers through DANA integration.
* **Enhance Customer Experience:** Provide more flexibility and convenience for your customers at checkout.

**Stay tuned for further updates as we continue to integrate with more payment channels!**


---

# 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/changelog/march-2024/new-payment-method-dana.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.