CIMB Direct Debit
CIMB direct debit offers tokenization scheme that requires customer to input OTP and/or PIN to verify every payment.
Last updated
CIMB direct debit offers tokenization scheme that requires customer to input OTP and/or PIN to verify every payment.
Last updated
DOKU API
Legacy DocumentationOverview of integration process with CIMB Direct Debit.
Account Binding process should be done before payment can be made and processed. Merchant will send account binding request from customer to DOKU. The request includes customer's phone number that is registered to customer's CIMB account.
Each CIMB account can only be bind to one customer on one merchant. Customer needs to do verification for account binding process by inputting OTP and PIN.
Account Binding Flow
| Environment | Endpoint |
|---|---|
HTTP Method | POST |
API Sandbox | |
API Production | |
Path |
|
Sample of Request Header, Request Body and Response Body
Notes:
Parameter with (*) is mandatory
Paramater without (*) is optional/conditional
After customer's account is bind/linked and customer has enough balance for payment, merchant can send payment request from customer to DOKU by bringing customer's token.
Payment Flow
| Environment | Endpoint |
|---|---|
HTTP Method | POST |
API Sandbox | |
API Production | |
Path |
|
Sample of Request Header, Request Body and Response Body
Notes:
Parameter with (*) is mandatory
Paramater without (*) is optional/conditional
Once customer has submitted their payment request along with the OTP, merchant needs to verify the payment. Merchant can hit this API to verify the OTP.
OTP Verification Flow
| Environment | Endpoint |
|---|---|
HTTP Method | POST |
API Sandbox | |
API Production | |
Path |
|
Sample of Request Header, Request Body and Response Body
Notes:
Parameter with (*) is mandatory
Paramater without (*) is optional/conditional
After payment is completed, DOKU will send HTTP Notification to merchant's defined Notification URL. Learn how to handle the notification from DOKU.
This endpoint is used to create refund request for previous successful payment. Merchant can request a transaction refund to DOKU. Full refund and partial refund are available to be requested.
Online Refund Flow
| Environment | Endpoint |
|---|---|
HTTP Method | POST |
API Sandbox | |
API Production | |
Path |
|
Sample of Request Header, Request Body and Response Body
Notes:
Parameter with (*) is mandatory
Paramater without (*) is optional/conditional
If a registered customer no longer wants their account/card to be bind/linked and wish to remove themself from DOKU's and merchant’s system, merchant can send account unbinding request that is initiated by customer.
| Environment | Endpoint |
|---|---|
HTTP Method | POST |
API Sandbox | |
API Production | |
Path |
|
Sample of Request Header, Request Body and Response Body
Notes:
Parameter with (*) is mandatory
Paramater without (*) is optional/conditional
