Akulaku
Last updated
Last updated
DOKU API
Legacy DocumentationDOKU has partnered with various Paylater Providers and one of them is Akulaku to provide Buy Now Pay Later. Learn more about how DOKU can help you integrate with Akulaku here.
Here is the overview of how to integrate with Akulaku:
Obtain payment.url
by generating order
Display Akulaku payment page to customer
Acknowledge payment result
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 |
---|---|---|---|
|
| Mandatory | Generated by merchant to identify the order and must unique per request
Allowed chars: |
|
| Mandatory | In IDR currency and without decimal
Allowed chars: |
|
| Mandatory | Name of the product item
Allowed chars: |
|
| Mandatory | Price of the product item. Total price and quantity must match with the |
|
| Mandatory | Quantity of the product item
Allowed chars: |
|
| Mandatory | SKU of the item in this transaction |
|
| Mandatory | Category of the item in this transaction |
|
| Mandatory | Merchant URL that will redirected to after the order completed
Allowed chars: |
|
| Mandatory | Unique reference number generated by merchant, can be same value as |
|
| Mandatory | Unique customer identifier generated by merchant
Allowed chars: |
|
| Mandatory | Customer name that will be displayed on acquirer channel when do inquiry
Allowed chars: |
|
| Mandatory | Customer phone number. Format: |
|
| Optional | Customer address
Allowed chars: |
|
| Optional | Customer city, (Please send the following object, even if the value is empty.)
Allowed chars: |
|
| Optional | Customer province, (Please send the following object, even if the value is empty.)
Allowed chars: |
|
| Optional | Customer postcode, (Please send the following object, even if the value is empty.)
Allowed chars: |
|
| Optional | This parameter is intended to override the configured |
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 |
Response-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 |
---|---|---|---|
|
| Mandatory | Same as the request |
|
| Mandatory | Same as the request |
|
| Mandatory | Same as the request |
|
| Mandatory | Akulaku payment page URL to display for the customer |
|
| Mandatory | The current payment status
Possible value:
|
|
| Optional | List of transaction identifier that coming from the acquiring. Merchant can save these data for reference |
|
| Optional | Same as the request |
Once you have the payment.url
, you can now display the payment page by redirecting your customer to the Akulaku payment page.
After the customer completed the payment, they will be redirected to the defined order.callback_url
that you set on the API request.
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:
We provide various additional features to suited your needs. Learn more here.
If you wish to cancel your order request, you can do that by hitting the API with POST
method:
API Request
Type | Value |
---|---|
HTTP Method | POST |
API endpoint (Sandbox) |
|
API endpoint (Production) |
|
Here is the sample of request header to Cancel 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 of request body to Cancel Order:
Request Body Explanation
Parameter | Type | Mandatory | Description |
---|---|---|---|
|
| Same as the generate VA request | |
|
| Mandatory | Unique reference number of merchant's order. generated by merchant. Please note, this reference is |
|
| Optional | Key Value pairing data |
|
| Optional | Get from generate order response body |
|
| Optional | Get from generate order response body |
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 |
Response-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 |
---|---|---|---|
|
| Mandatory | Same as the request |
`order.amount |
| Mandatory | Same as the request |
|
| Mandatory | Status of the payment.
Possible Value:
1. |
|
| Mandatory | Date time of Akulaku will be expired with the format of |
|
| Mandatory | Unique reference number of merchant's order. generated by merchant. Please note, this reference is |
|
| Mandatory | Status of Cancel.
Possible Value:
1. |
|
| Mandatory | Date time of Order Akulaku already cancel. |
You can request refund using this API.
To request a refund, 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 payment URL:
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 request a refund:
Request Body Explanation
Parameter | Type | Mandatory | Description |
---|---|---|---|
|
| Mandatory | Invoice number of the transaction that being refunded, same as the invoice when payment |
|
| Mandatory | Same as the request |
|
| Mandatory | Key Value pairing data |
|
| Mandatory | unique reference no of merchant’s order refund, generated by merchant (new) |
API Response
After hitting the above API request, DOKU will give the response.
Type | Value |
---|---|
HTTP Status | 200 |
Result | SUCCESS |
Here is the sample response header:
Response Header Explanation
Parameter | Description |
---|---|
Client-Id | Same as the request |
Request-Id | Same as the request |
Response-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 |
---|---|---|---|
|
| Mandatory | Same as the request |
|
| Mandatory | Same as the request |
|
| Mandatory | Time Stamp response on UTC time in ISO8601 format |
|
| Mandatory | Status of the payment
a. |
|
| Mandatory | Same as the request payment |
|
| Optional | Key Value pairing data |
|
| Mandatory | Time Stamp response on UTC time in ISO8601 format |
|
| Mandatory | Refund status
Possible value: |
|
| Optional | Same as the request refund |
|
| Optional | Key Value Pairing Data |
Refund Type
Currently, Akulaku only accepts refund requests with Full Amount type.
If you are a platform or a marketplace, you can use this feature to settle the funds to your sellers or partners programmatically, save many operational efforts.