DOKU e-Wallet
Doku e-Wallet API Guide Explanation
Integration steps
Here is the overview of how to integrate with DOKU e-Wallet:
Obtain
payment.url
by generating orderDisplay DOKU Wallet payment page to customer
Acknowledge payment result
Direct API - DOKU e-Wallet Sequence Diagram
1. Obtain payment.url
by generating order
payment.url
by generating orderTo generate order, you will need to hit this API through your Backend:
API Request
Type | Value |
---|---|
HTTP Method | POST |
API endpoint (Sandbox) |
|
API endpoint (Production) |
|
Here is the sample of request header to generate order:
Request Header Explanation
Parameter | Description |
---|---|
Client-Id | Client ID retrieved from DOKU Back Office |
Request-Id | Unique random string (max 128 characters) generated from merchant side to protect duplicate request |
Request-Timestamp | Timestamp request on UTC time in ISO8601 UTC+0 format. It means to proceed transaction on UTC+7 (WIB), merchant need to subtract time with 7. Ex: to proceed transaction on September 22th 2020 at 08:51:00 WIB, the timestamp should be 2020-09-22T01:51:00Z |
Signature | Security parameter that needs to be generated on merchant Backend and placed to the header request to ensure that the request is coming from valid merchant. Please refer to this section to generate the signature |
Here is the sample request body to generate order:
Request Body Explanation
Parameter | Type | Mandatory | Description |
---|---|---|---|
| string | Mandatory | Generated by merchant to identify the order and must unique per request
Allowed chars: |
| number | Mandatory | In IDR currency and without decimal
Allowed chars: |
| string | Conditional | Optional if request doesnt pass line items. But if request passes, then it becomes Mandatory.
Allowed chars: |
| number | Conditional | Price of the product item. Total price and quantity must match with the |
| number | Conditional | Quantity of the product item<. Optional if request doesnt pass line items. But if request passes, then it becomes Mandatory.
Allowed chars: |
| string | Optional | Merchant URL that will redirected to after the order success. If merchant set |
| string | Optional | Merchant URL that will redirected to after the order failed. If not set, then will redirect to |
| string | Mandatory | Merchant URL that will be notify from DOKU. If its not define, status in merchant will not update.
Allowed chars: |
| string | Mandatory | Redirection to defined |
API Response
After hitting the above API request, DOKU will give the response.
Type | Value |
---|---|
HTTP Status | 200 |
Result | SUCCESS |
Response Header Explanation
Parameter | Description |
---|---|
Client-Id | Same as the request |
Request-Id | Same as the request |
Request-Timestamp | Timestamp Response on UTC with format ISO8601 UTC+0 from DOKU |
Signature | Signature generated by DOKU based on the response body |
Here is the sample of response body:
Response Body Explanation
Parameter | Type | Mandatory | Description |
---|---|---|---|
| string | Mandatory | Same as the request |
| number | Mandatory | Same as the request |
| number | Mandatory | Same as the request |
| number | Mandatory | Same as the request |
| string | Mandatory | DOKU Wallet Payment Page URL generated by DOKU that merchant displays to the customer |
2. Display DOKU Wallet payment page to customer
Once you have the payment.url
, you can now display the payment page by redirecting your customer to the DOKU Wallet payment page.
After the customer completed the payment, they will be redirected to the defined success_url
that you set on the API request.
3. Acknowledge payment result
After the payment is being made by your customer, DOKU will send HTTP Notification to your defined Notification URL
. Learn how to handle the notification from DOKU:
Last updated