> 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/august-2024/new-payment-method-allo-bank.md).

# New Payment Method: Allo Bank

Introducing Allo Bank as Your New Payment Option!

<figure><img src="https://2961485474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5XrPPWlRNNTQG72DaVGd%2Fuploads%2FbxndTJoxBhjEYYGBebE8%2FNEW%20Payment%20Method%20Allo%20Bank.png?alt=media&amp;token=7d6fc25d-3881-4d9d-86cb-24a10f9ddfd5" alt="" width="375"><figcaption></figcaption></figure>

We're thrilled to let you know that **Allo Bank** is now live as a payment method on DOKU! Your customers can now enjoy the flexibility of paying through Allo Bank, ensuring a smoother, more secure checkout experience tailored to their needs.

***

#### What This Means for Your Business:

* **Broaden Your Customer Base:** Attract more customers by offering Allo Bank as a preferred payment method, reaching those who prefer to use Allo Bank for their transactions.
* **Streamline Payment Processes:** With Allo Bank integration, you can offer fast, seamless, and secure payments that benefit both you and your customers.
* **Enhance Convenience:** Elevate your customer’s checkout experience by offering a wider range of payment options, improving satisfaction and making purchases easier.

***

Stay tuned for more exciting updates as we expand our payment options to better serve your business needs!


---

# 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/august-2024/new-payment-method-allo-bank.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.
