> 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/direct-api.md).

# Direct API

If you wish to implement your own payment page, DOKU provides REST API that you can use to directly integrate with us. We provide code library in various programming languages to help you integrate.&#x20;

With Direct API, you are enabled to create customized payment flows and integrate them directly into your website while still adhering to security and compliance standards. The following are some benefits of integrating with Direct API:

| Benefits                      | Description                                                                                                                                                                                                                                                                                                            |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Brand Consistency             | Merchants can maintain a consistent brand experience throughout the entire customer journey, including the checkout process. Customization allows for the i**ncorporation of brand colors, logos, and styles**, reinforcing brand identity.                                                                            |
| Seamless User Experience      | Integration directly into the website ensures a seamless user experience. Customers **stay on the merchant's site** from product selection to payment confirmation, reducing friction and potential drop-offs in the conversion funnel.                                                                                |
| Flexibility and Customization | Developers have the flexibility to design and implement payment flows that align with the specific requirements of the business. Customization **extends to the layout, user interface elements, and user interactions** during the payment process.                                                                   |
| Control Over User Interface   | Merchants and developers have complete control over the look and feel of the payment interface. This control is valuable for creating **user-friendly and intuitive payment forms**, optimizing the checkout process for increased conversions.                                                                        |
| Security Compliance           | DOKU handles the complexities of security compliance, especially compliance with the Payment Card Industry Data Security Standard (PCI DSS). By using DOKUs APIs, merchants can ensure that **sensitive payment information is handled securely** without having to manage intricate security requirements themselves. |
| Scalability                   | DOKU's infrastructure is designed for scalability. Merchants can handle growing transaction volumes **without worrying about the technical challenges** associated with scaling payment processing capabilities.                                                                                                       |

{% hint style="info" %}
You can try Direct API by using our demo [here](https://sandbox.doku.com/demo/direct-api), or immediately integrate with our API by following the guide [here](https://developers.doku.com/accept-payment/direct-api).
{% endhint %}


---

# 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/accept-payments/integration-tools/direct-api.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.
