Doku payment method is an Indonesia-based payments provider known for enabling local online payments through one merchant setup.
Merchants add it when Indonesia is a core market, and conversion depends on local payment habits, not only cards. In mixed checkouts, Doku usually sits next to cards and other local options, while Akurateco helps teams manage performance end-to-end, keep approval rates visible, and apply routing when more than one provider is in play.
What is Doku?
Doku is a PSP and payment gateway. It is used by Indonesian e-commerce brands, digital services, and regional platforms that need local payment acceptance for one-time purchases and sometimes recurring, depending on the rail.
Where Doku is used
Doku is primarily associated with Indonesia. Because availability can vary by product and agreement, confirm Doku supported countries during onboarding rather than assuming it is identical for every merchant setup. It’s common in e-commerce, digital goods, and services selling to Indonesian customers.
How Doku works
- The customer chooses Doku at checkout.
- Your backend creates a payment request through the Doku API and receives a reference.
- The customer completes the rail-specific step, such as wallet approval or bank transfer style confirmation.
- Doku processes the payment and returns an initial status.
- Final confirmation is delivered through callbacks or webhooks, so you can update the order even if the customer closes the page.
- Your system marks the order as paid, failed, or pending.
- If pending, you wait for confirmation before fulfillment.
- Finance reconciles using transaction references and provider reports.
Merchant requirements and setup basics
Common requirements for Doku integration:
- Merchant onboarding and account approval
- API keys and environment configuration
- Webhook endpoint for status updates
- Return URL handling if the flow uses redirects
- Test cases for success, failure, and pending outcomes
Fees, settlement, and refunds overview
The Doku payment gateway pricing is commercial. What you pay depends on the payment rail you enable, your business category, and the terms you agree to with Doku, so it’s not something you can immediately estimate from public information.
When it comes to Doku settlement, approval at checkout, and money landing in your account are two different moments. Payout timing depends on your agreed payout cadence and can vary by rail, so finance should confirm the actual timeline by reviewing settlement and payout reports once transactions start flowing.
Doku refunds are supported, but the experience is rail-dependent. Some refunds move quickly; others take longer. Customer support and finance should treat refunds as a tracked process and reconcile each refund to the original payment reference.
Pros and cons of Doku for merchants
Pros:
- Strong local fit when Indonesia is a priority market
- One provider setup can reduce the work of stitching local rails one by one
- Works well for mobile-first buyers who prefer local flows over cards
Cons:
- Outside Indonesia, you will likely need other providers for coverage
- Some rails confirm later, so fulfillment must respect pending states
- Refund timelines can vary by rail, which adds work for support and finance
Using Doku in a multi-method checkout
The Doku payment method is usually used to cover Indonesia, while cards are used for international buyers. Once multiple providers are live, the real benefit is operational simplicity. A payment monitoring system within orchestration lets you see which method is dragging approval rate down and where failures come from, without digging through separate dashboards.
Integration via Akurateco
Akurateco lets you centralise provider connections under one orchestration layer so monitoring, intelligent payment routing, and reporting stay consistent as you expand. If you need a specific payment option added to your checkout, we can scope it and deliver it upon request. Contact us to discuss details.
What is Doku?
Doku is an Indonesia-based payments provider that acts like a PSP and payment gateway. Merchants use it to accept local online payments through a single provider connection, rather than stitching together separate local rails.
Where is Doku available?
Doku is most strongly associated with Indonesia. In some cases, you may see wider regional positioning, but what matters is what your merchant account is actually enabled for, so confirm Doku supported countries during onboarding rather than relying on a generic list.
Does Doku support refunds?
Yes. Doku refunds are supported, but the timing is rail-dependent. Some refunds behave more like card refunds, others follow local rail rules, so support and finance should rely on status updates and clean reconciliation back to the original payment reference.
How long does the settlement take?
Doku settlement timing depends on two things: the rail used and your payout schedule. Approval can happen in seconds, but payouts follow an agreed cadence, so finance should validate the actual timeline in settlement and payout reports after you go live.
Is Doku good for subscriptions or recurring?
Sometimes. Many teams keep cards as the main option for renewals and use local rails mainly for one-time payments. If subscriptions are important, confirm whether your chosen Doku rails support recurring properly and what happens when a renewal fails before rolling it out widely.
Can I offer Doku alongside cards and other local methods?
Yes, and that is common in Indonesia-focused checkouts. Once you combine multiple methods and providers, orchestration helps you run it as one system, with consistent rules, clearer reporting, and one view of performance across the whole stack.
