DOKU has partnered with various partners and one of them is Alfa Group (Alfamart, Alfaexpress, Alfamidi, Lawson, Dan+Dan) to provide O2O Payment. Learn more about how DOKU can help you integrate with Alfa Group here.
Integration methods
There are two methods to integrate with Alfa Group:
Register: The payment code will be registered to DOKU and Alfa will inquiry to our side when the customer make payment at the Alfa Store
DOKU Generated Payment Code (DGPC): The payment code is generated by DOKU. Suitable for e-commerce business model.
Merchant Generated Payment Code (MGPC): The payment code is generated by Merchant. Suitable for top up business model.
Direct Inquiry (DIPC): The payment code is registered on merchant side and DOKU will forward Alfa inquiry request to merchant side when the customer make payment at the Alfa store
Integration steps
Here is the overview of how to integrate with Online to Offline:
Generate payment code
Display payment code
Acknowledge payment result
1. Generate payment code
To generate payment code, you will need to hit this API through your Backend:
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 generate payment code:
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
Generated by DOKU that will be used by customer for doing a payment through Alfa store
online_to_offline_info.how_to_pay_page
string
Optional
Page URL that merchant can use to display how customer can complete the payment process through Alfa store
online_to_offline_info.how_to_pay_api
string
Optional
URL that merchant can parse to display customized how customer can complete the payment process through Alfa store
online_to_offline_info.created_date
string
Conditional
Date time of payment code generated with the format of yyyyMMddHHmmss. The created date uses UTC+7 time
online_to_offline_info.expired_date
string
Conditional
Date time of payment code will be expired with the format of yyyyMMddHHmmss. The expired date uses UTC+7 time. Use this to set the expiry order on merchant side
online_to_offline_info.created_date_utc
string
Conditional
Date time of payment code generated in UTC format
online_to_offline_info.expired_date_utc
string
Conditional
Date time of payment code will be expired in UTC. Use this to set the expiry order on merchant side
PRO TIPS
You can also show payment instruction link to your customer by using online_to_offline_info.how_to_pay_page. If you wish to customize the UI for the payment instruction, you can use the online_to_offline_info.how_to_pay_api.
2. Display payment code
You can display the payment code to your customer by using online_to_offline_info.payment_code that you retrieved from the API response.
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:
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 generate payment code:
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
Generated by DOKU that will be used by customer for doing a payment through Alfa store
online_to_offline_info.how_to_pay_page
string
Optional
Page URL that merchant can use to display how customer can complete the payment process through Alfa store
online_to_offline_info.how_to_pay_api
string
Optional
URL that merchant can parse to display customized how customer can complete the payment process through Alfa store
online_to_offline_info.created_date
string
Conditional
Date time of payment code generated with the format of yyyyMMddHHmmss. The created date uses UTC+7 time
online_to_offline_info.expired_date
string
Conditional
Date time of payment code will be expired with the format of yyyyMMddHHmmss. The expired date uses UTC+7 time. Use this to set the expiry order on merchant side
online_to_offline_info.created_date_utc
string
Conditional
Date time of payment code generated in UTC format
online_to_offline_info.expired_date_utc
string
Conditional
Date time of payment code will be expired in UTC. Use this to set the expiry order on merchant side
PRO TIPS
You can also show payment instruction link to your customer by using online_to_offline_info.how_to_pay_page. If you wish to customize the UI for the payment instruction, you can use the online_to_offline_info.how_to_pay_api.
2. Display payment code
You can display the payment code to your customer by using online_to_offline_info.payment_code that you retrieved from the API response.
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:
Unique random string (max 128 characters) generated from DOKU 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 verified on merchant Backend to ensure that the request is coming from DOKU. Please refer to this section to generate the signature
Here is the sample of request body that DOKU will send to defined Inquiry URL:
Generated by merchant to identify the order and must unique per request
Allowed chars: alphabetic, numeric, special chars
Max length: 64
order.amount
number
Mandatory
In IDR currency and without decimal. Alfa only supports Close Amount
Allowed chars: numeric
Max length: 12
online_to_offline_info.payment_code
string
Mandatory
Same as the request
online_to_offline_info.info
string
Optional
Additional info that will be display on the Alfa POS when customer do inquiry
Allowed chars: alphabetic, numeric, special chars
Max length: 30
online_to_offline_inquiry.status
string
Mandatory
Possible value: success, decline, billing_already_paid, billing_was_expired, billing_not_found
customer.name
string
Mandatory
Customer name that will be displayed on Alfa POS when do inquiry
Allowed chars: alphabetic, numeric, special chars
Max length: 64
customer.email
string
Optional
Customer email
Allowed chars: alphabetic, numeric, special chars
Max length: 128
additional_info
object
Optional
Merchant can send additional data through this parameter and will be get the data in the HTTP Notification
4. 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:
We provide various additional features to suited your needs. Learn more here.
Insurance Data
For insurance merchant, DOKU can show insurance data to Alfa POS and Alfa receipt by give object additional_info.insurance_info and also DOKU can show footer message on Alfa receipt by give alfa_info.receipt.footer_message to DOKU. Here is the sample:
{ ..."alfa_info": {"receipt": {"footer_message":"Call Center 021 555-0525" } },"additional_info": {"insurance_info": {"policy_type":"Dana Pendidikan","policy_number":"9090901234","policy_account_name":"Taufik Ismail","policy_status":"aktif","bill_due_date":"21 May 2021" } }, ...}
Update and Cancel Payment Code Data
If you wish to update your payment code data such as, update the amount, update the expiry time, customer details, and etc. You can do that by hitting the API with PATCH method:
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 update payment code data:
Cancel payment code data
To cancel a payment code, simply set online_to_offline_info.status to DELETE
{"order": {"invoice_number":"INV-20210124-0001","amount":150000 },"online_to_offline_info": {"payment_code":"6059000000000205","status":"ACTIVE","expired_time":60,"reusable_status":false,"info":"Thank you for shopping" },"customer": {"name":"Anton Budiman","email":"anton@example.com" }}
Request Body Explanation
Parameter
Type
Mandatory
Description
order.invoice_number
string
Same as the generate payment code request
order.amount
number
Conditional
Set this with updated value if wished. Set this parameter to more than (>) 0for Close Amount
Allowed chars: numeric
Max length: 12
online_to_offline_info.payment_code
string
Mandatory
The payment code that wish to be updated
online_to_offline_info.status
string
Mandatory
Set ACTIVE to update the payment code and set DELETE to cancel the payment code
Possible value: ACTIVE, DELETE
online_to_offline_info.expired_time
number
Optional
Set this with updated value if wished
Allowed chars: numeric
Maximum length: 5
Default value: 60
online_to_offline_info.reusable_status
number
Mandatory
Set this with updated value if wished
Possible value: truefalse
online_to_offline_info.info
string
Optional
Additional info that will be display on the Alfa POS when customer do inquiry
Allowed chars: alphabetic, numeric, special chars
Max length: 30
customer.name
string
Mandatory
Set this with updated value if wished
Allowed chars: alphabetic, numeric, special chars
Max length: 40
customer.email
string
Optional
Set this with updated value if wished
Allowed chars: alphabetic, numeric, special chars
Max length: 128
API Response
After hitting the above API request, DOKU will give the response.
Generated by DOKU that will be used by customer for doing a payment through Alfa store
online_to_offline_info.created_date
string
Conditional
Date time of payment code generated with the format of yyyyMMddHHmmss. The created date uses UTC+7 time
online_to_offline_info.expired_date
string
Conditional
Date time of payment code will be expired with the format of yyyyMMddHHmmss. The expired date uses UTC+7 time. Use this to set the expiry order on merchant side
online_to_offline_info.created_date_utc
string
Conditional
Date time of payment code generated in UTC format
online_to_offline_info.expired_date_utc
string
Conditional
Date time of payment code will be expired in UTC. Use this to set the expiry order on merchant side
Split Settlement
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.