| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Invoicing (account) • Discuss (mail) • Website (website) |
| Lines of code | 849 |
| Technical Name |
doku_payment |
| License | LGPL-3 |
| Website | https://oentoro.blog |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Invoicing (account) • Discuss (mail) • Website (website) |
| Lines of code | 849 |
| Technical Name |
doku_payment |
| License | LGPL-3 |
| Website | https://oentoro.blog |
DOKU Payment Provider for Odoo 19
Sell with DOKU in Odoo 19 using a checkout flow built for delayed payments such as Virtual Account and QRIS, including webhook handling, retry-safe payment sessions, and customer portal continuation.
Key Features
DOKU Checkout Integration
Redirect customers from Odoo to the DOKU checkout page and track the payment lifecycle inside Odoo.
VA and QRIS Support
Optimized for delayed-payment methods where customers can pay later and return through webhook confirmation.
Safe Retry Flow
Expired payment links are not reused. Fresh DOKU sessions are generated with retry-safe references.
Customer Portal Continuation
Customers can continue payment from quotation or order detail pages while the DOKU link is still valid.
Business Flow
- Customer starts checkout and Odoo creates a DOKU session.
- The payment transaction becomes pending while the quotation remains unpaid.
- Customer pays through DOKU later using VA or QRIS.
- DOKU sends a notification to Odoo.
- On successful payment, the related quotation is confirmed.
Status Handling
Success
The transaction is marked as done and the related sales document can move forward.
Pending
The transaction stays pending and the customer can continue payment from the portal while the link is valid.
Expired or Canceled
The stale DOKU session is canceled and the customer can create a fresh payment session.
Failed
The transaction is marked as error and the sales team can review the case from Odoo.
Technical Notes
DOKU references are generated independently from final Odoo invoice numbers to support safe retries.
This keeps the DOKU side unique while preserving traceability back to the originating quotation or sales order.
Requirements
- Odoo 19
- Modules: payment, account_payment, sale, website_sale
- Python dependency: requests
- DOKU Client ID and Secret Key
- Public HTTPS base URL for callbacks
Why This Module
- Built specifically for Odoo 19.
- Pragmatic handling for Odoo Community deployments.
- Designed for real delayed-payment operations instead of instant-only card flows.
- Keeps payment retries manageable for customers and back-office users.
Please log in to comment on this module