> 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/sdks-and-libraries.md).

# SDKs and Libraries

DOKU provides a full suite of SDKs and libraries to help you integrate payment capabilities quickly, securely, and reliably — across platforms and programming languages. This reduces the amount of work required to use DOKU's REST APIs. Whether you're building a mobile app, an online store, or a back-office finance system, we offer the tools to accelerate your integration and reduce time-to-market.

Our SDKs and libraries also ensure compliance with the new Bank Indonesia (BI) regulations. These regulations, known as SNAP BI, standardize the API between Payment Service Providers (PSPs) to ensure secure and consistent payment processing. Compliance with these regulations is crucial for maintaining secure operations and meeting industry standards.

## Server-side SDKs

DOKU provides server-side SDKs designed to streamline interactions with our REST APIs, significantly reducing development effort. Below is a list of the available libraries:

| Library | Version             | GitHub Repository                                                                                                                                                                                                                           |
| ------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Node.js | v18.0.0 or higher   | [https://github.com/PTNUSASATUINTIARTHA-DOKU/doku-nodejs-library&#xD;](<https://github.com/PTNUSASATUINTIARTHA-DOKU/doku-nodejs-library&#xD;&#xA;&#xD;&#xA;>)                                                                               |
| Java    | Java 11 or higher   | <https://github.com/PTNUSASATUINTIARTHA-DOKU/doku-java-library>                                                                                                                                                                             |
| PHP     | PHP 8 or higher     | <https://github.com/PTNUSASATUINTIARTHA-DOKU/doku-php-library>                                                                                                                                                                              |
| Python  | Python 38 or higher | <https://github.com/PTNUSASATUINTIARTHA-DOKU/doku-python-library>                                                                                                                                                                           |
| Golang  | Go 1.22.2 or higher | <p><a href="https://github.com/PTNUSASATUINTIARTHA-DOKU/doku-golang-library"><https://github.com/PTNUSASATUINTIARTHA-></a></p><p><a href="https://github.com/PTNUSASATUINTIARTHA-DOKU/doku-golang-library">DOKU/doku-golang-library</a></p> |

### Integration Guide (Server Side SDK)

For complete integration guide with SDKs and Libraries, visit [DOKU API Reference](https://developers.doku.com/developer-kit/libraries-and-sdk?utm_source=docs).

***

## Mobile Checkout SDKs

**DOKU Checkout SDK** enables merchants to integrate a secure, native checkout experience into iOS and Android applications. Featuring pre-built checkout components, support for multiple payment methods, and simplified payment workflows, the SDK reduces integration complexity while delivering a fast, consistent, and reliable payment experience across mobile platforms.

<figure><img src="/files/CkaAwtCrXLoUpOIVSMZU" alt="" width="563"><figcaption></figcaption></figure>

### Integration Guide&#x20;

* **DOKU Android SDK**

{% embed url="<https://github.com/PTNUSASATUINTIARTHA-DOKU/sdk-checkout-android-mobile>" %}

* **DOKU iOS SDK**

{% embed url="<https://github.com/PTNUSASATUINTIARTHA-DOKU/sdk-checkout-ios-mobile>" %}

***

## FAQ

<details>

<summary>What payment methods are supported?</summary>

We currently support the following payment methods:

1. Cards (Credit/Debit Card)
2. QRIS
3. Bank Transfer / Virtual Account
4. e-Wallets
   * DOKU e-Wallet
   * DANA
   * ShopeePay

</details>

<details>

<summary>Can I customize the checkout page?</summary>

Yes. You can customize the secondary color, which will be reflected in button colors and highlighted text.

</details>

<details>

<summary>Does Mobile Checkout SDK support Promo Engine features ?</summary>

Promo Engine features are not currently supported in Mobile Checkout SDK.

</details>

<details>

<summary>Does Mobile Checkout SDK work in Sandbox environment?</summary>

Yes. Mobile Checkout SDK supports the Sandbox environment for testing. Set `production = false` when initializing the SDK to use Sandbox.

</details>

<details>

<summary>What happens if the customer closes the checkout?</summary>

The payment session remains active until it expires. Customers can resume payment using the same session as long as it's still valid.

</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/accept-payments/integration-tools/sdks-and-libraries.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.