> 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/september-2026/mobile-checkout-sdk.md). # Mobile Checkout SDK Effective Date: 1 September 2026 DOKU Checkout SDK enables merchants to integrate a **secure, native checkout experience directly into iOS and Android applications**. With pre-built checkout components, support for multiple payment methods, and simplified payment workflows, the SDK helps reduce integration complexity and development effort while delivering a fast, consistent, and reliable payment experience across mobile platforms. [Read more in DOKU Documentation...](https://docs.doku.com/accept-payments/integration-tools/sdks-and-libraries)
*** ### πŸ” What’s New? DOKU Mobile Checkout SDK provides pre-built components that allow merchants to add checkout capabilities directly into their mobile applications. The SDK currently supports: * **Cards (Credit / Debit Card)** * **QRIS** * **Bank Transfer / Virtual Account** * **E-Wallets** * **DOKU e-Wallet** * **DANA** * **ShopeePay** For complete integration instructions and SDK documentation, visit the [**DOKU Documentation**.](https://docs.doku.com/accept-payments/integration-tools/sdks-and-libraries) #### The SDK is available for both **Android and iOS** applications. **DOKU Android SDK**\ [\[GitHub Repository\]](https://github.com/PTNUSASATUINTIARTHA-DOKU/sdk-checkout-android-mobile) **DOKU iOS SDK**\ [\[GitHub Repository](https://github.com/PTNUSASATUINTIARTHA-DOKU/sdk-checkout-ios-mobile) *** ### πŸ’‘ Why It Matters Building a payment experience inside a mobile application can require significant development effort. DOKU Checkout SDK provides pre-built checkout components and simplified payment workflows to help streamline the integration process. #### **For Merchants** * Reduce development effort when integrating payments * Add multiple payment methods through a single checkout experience * Provide a consistent checkout experience across mobile platforms * Customize selected checkout elements to match your brand * Test the integration in the **Sandbox environment** before going live #### **For Customers** * Complete payments directly within the merchant's mobile application * Access multiple payment methods in one checkout experience * Enjoy a consistent and streamlined payment flow *** ### πŸš€ How It Works #### πŸ”„ Before Without a mobile checkout SDK, merchants need to build and manage the payment integration and checkout experience within their mobile application using DOKU APIs. This can require additional development effort to handle payment workflows and supported payment methods. #### πŸ†• After With **DOKU Checkout SDK**, merchants can use pre-built checkout components and simplified payment workflows to integrate payments into their iOS or Android application. The SDK handles the checkout experience while connecting to DOKU's supported payment capabilities. *** ### βš™οΈ How to Get Started Getting started with Mobile Checkout SDK: 1. Choose the platform you want to integrate: **Android or iOS**. 2. Access the relevant DOKU Checkout SDK. 3. Follow the integration guide in the DOKU API Reference. 4. Configure the SDK for the **Sandbox environment** for testing. 5. Test your payment flow. 6. Set the appropriate production configuration when you're ready to go live. For Sandbox testing, set **`production = false`** when initializing the SDK. *** ### 🎨 Customize Your Checkout The Mobile Checkout SDK supports customization of the **secondary color**. The selected color is reflected in elements such as: * Button colors * Highlighted text This allows merchants to align selected parts of the checkout experience with their brand. *** ### 🎯 **Potential Use Cases** Mobile Checkout SDK is suitable for businesses that provide payment experiences through their own mobile applications, such as: * **E-commerce & Retail** let customers complete purchases directly within the mobile app. * **Travel & Hospitality** support in-app payments for bookings and reservations. * **Food & Delivery** enable customers to complete payments as part of the ordering journey. * **Subscription Services** support payment flows within mobile-based subscription experiences. * **Digital Platforms** integrate DOKU payment capabilities into mobile products and services. *** ### ⚠️ Important Notes * Mobile Checkout SDK is currently available for **Android and iOS**. * **Promo Engine features are not currently supported** in Mobile Checkout SDK. * The SDK supports the **Sandbox environment** for testing. * The payment session remains active until it expires. Customers can resume payment using the same session as long as the session is still valid. * Only the **secondary color** can currently be customized. *** For assistance, contact our Care Team at or (021) 1500963. *** Thank you and best regards,\ **DOKU Product Team** --- # 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/september-2026/mobile-checkout-sdk.md?ask=&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.