DOKU MCP Server

DOKU Model Context Protocol capabilities and use cases

QRIS Payment with DOKU MCP

Overview

DOKU MCP Server is a gateway that connects DOKU’s payment APIs with AI-powered applications. Built using the Model Context Protocol (MCP), this server allows AI agents to communicate with DOKU to build conversational commerce, automated payment assistants, and other AI-driven experiences. Instead of manually handling API calls, developers can let their AI agents communicate with DOKU through the MCP Server in a predictable and secure way.

If your business uses AI-powered apps, chatbots, or automated workflows, DOKU MCP makes it easy for your AI agents to perform operations such as:

• Generating a payment link

• Issuing a Virtual Account number

• Generating a QRIS code

• Checking the status of a transaction

• Handling post-payment workflows

Benefit	Description
AI-Powered Payment Automation	Any AI system that supports MCP can immediately discover your tools and invoke them (no per-integration adapters).
Quick Setup	No custom wrappers needed; tools are discoverable and ready to use, cutting integration time.
Safer / Predictable Interaction	The schema defines valid parameters, types, and error responses, reducing the chance an agent miscalls your API.

---

Key Features

DOKU MCP allows your system (or an AI assistant you use) to create payments on demand. Whether your customer is checking out on a website, speaking to a virtual assistant, or interacting through a chat application, you can provide seamless payment options instantly.

You can choose between two payment experiences:

1. Checkout Payment (Checkout Payment)

   • Generates a DOKU-hosted payment page or payment link

   • Displays all payment methods available for your merchant account

   • Reduces development effort because DOKU handles the UI and instructions

   • Ideal for customer-facing chatbots or quick link-based payments

2. Direct Payment (Direct Payment)

   • Creates a payment instruction for a specific method (QRIS, VA, e-Wallet, PayLater)

   • No hosted page; you provide the instructions directly to the customer

   • Gives you full control over the customer experience

   • Suitable for conversational flows (WhatsApp or mesagging apps), kiosks, and POS systems

Checkout Payment

A Checkout Payment refers to creating a link or embedded payment page hosted by DOKU. Your customer sees all payment methods available on your merchant account and can choose how they want to pay.

Checkout Payment Example

What you get:

• A checkout link you can send to your customer

• A ready-to-use payment page with all supported methods

• DOKU handles the user interface and instructions

When to use Checkout Payment:

• You want a simple, all-in-one payment page

• You don’t want to build your own payment UI

• Your customers are interacting through chat, AI assistants, or messaging apps

• You want to show multiple payment methods (QRIS, VA, e-Wallet, PayLater)

This is the easiest way for merchants to collect payments through MCP.

Direct Payment

Direct Payment creates a payment instruction for one specific payment method. This option does not use a hosted payment page. Instead, your AI agent gives the customer the information they need to complete the payment. Direct Payment is ideal when you already know the customer’s preferred payment method or when you want full control of the payment flow.

Direct Payment Example

What you get:

When you create a Direct Payment, DOKU returns the payment information needed for the customer to complete the transaction, such as:

• A Virtual Account number

• A QRIS dynamic QR code or QR string

• An e-Wallet redirect link or deeplink

• A PayLater authorization URL or instructions

• A Convenience Store payment code

When to use Direct Payment:

• You already know the customer’s preferred payment method

• Your product uses chat or AI-driven flows (e.g., WhatsApp/AI agents)

• You want to display the payment method directly in your interface

• You only accept one or a few specific payment methods

• You want full control of the user experience

---

Payment Methods

DOKU MCP supports a wide range of payment methods for both Checkout Payment and Direct Payment. The table below shows which payment methods are available for type:

Payment Method	Checkout Payment	Direct Payment
QRIS	✅	✅
Cards	✅	✅
Virtual Account (Bank Transfer)	✅	✅
OVO	✅	✅
ShopeePay	✅	✅
DANA	✅	✅
LinkAja	✅	❌
i.saku	✅	❌
DOKU e-Wallet	✅	✅
Alfa Group	✅	✅
Indomaret	✅	✅
Akulaku	✅	✅
Kredivo	✅	✅
Indodana	✅	❌
BRI Ceria	✅	❌
Kartu Kredit Indonesia	✅	❌
Direct Debit BRI	✅	❌
Direct Debit CIMB	✅	❌
Direct Debit Allobank	✅	❌
Direct Debit Mandiri	✅	❌
Jenius Pay	✅	❌
Internet Banking	✅	❌

---

Get Started

Please visit our API Reference to learn how to integrate with DOKU MCP Server, including authentication steps, available tool schemas, request/response formats, webhook event structures, error codes, and best practices. The API Reference also covers sandbox environments for testing, migration guidelines from traditional REST APIs, and code samples in multiple languages so your team can get started quickly.

Get Started Now

---

FAQ

Is using DOKU MCP Server free of charge?

Yes, there is no fee in using DOKU MCP.

Do I need AI to use DOKU MCP?

Not necessarily. While MCP is designed to make it easier for AI agents and assistants to interact with payments, you don’t need AI to use it. You can call MCP tools directly from your backend systems, apps, or automation scripts just like a normal API. AI simply adds another layer of flexibility for conversational or autonomous payment flows.

How do I manage permissions / quotas on who can call MCP tools?

We support role-based access control (RBAC) at the tool level. You can designate which agents / users / applications can call which MCP methods. You can also enforce rate limits, quotas, and logging per API key.

Are there tools available for refunds, voids, or transaction reversals in DOKU MCP?

Yes. DOKU MCP provides tools that support refunds, voids, and transaction cancellations. For more details, please refer to the complete list of available DOKU MCP tools here.

Can I migrate existing payment flows to DOKU MCP without disruption?

Yes. Because your agents / systems will detect both MCP and REST interfaces, you can phase in MCP gradually, test it, and fall back to your existing flow until full cutover.

If I don’t have a technical team, can I still use DOKU MCP?

Yes. We will guide you through the setup, from creating checkout or payment links to enabling QRIS and Virtual Account payments. We can handle the technical configuration for you and make sure everything is working smoothly. Please contact our Sales team by filling the following form to get started.