DOKU Wallet
Last updated
Was this helpful?
Last updated
Was this helpful?
Overview of integration process with DOKU Wallet SNAP.
Before partners can access SNAP API DOKU, a partner must request a B2B / B2B2C token. Token B2B / B2B2C session expired 900s (access token will continue to be used as long as there is activity request API from a partners to DOKU), but when partners request access token B2B / B2B2C more than one element before time limit expired, the latest access token B2B / B2B2C will be processed.
Token B2B used all SNAP API DOKU.
Token B2B2C is used for all SNAP API DOKU that involve customers for transaction activity.
At this stage is the process for registering a new account, where after a successful registration process the customer will get a DOKU ID that is unique among customers to one another.
Partners use API Verify OTP when user input OTP on partner side, this activity is required when we need to validate the account, example on flow journey Account Creation and Account Unbinding.
Account Binding is flow to bind DOKU Wallet accounts to partner for get authCode (B2BB2C / Authorization-Customer for payment purposes)
This is the process when customers want to unbinding their DOKU account from merchants. To complete the unbinding account process OTP must send to API Verify OTP.
With this API, partners can check for customer balance that has been verified by DOKU, so that partners can equate customer data, between partners and DOKU.
This API allows partners to get BANK beneficiary information, so customers can see and confirm the transfer activity
This API allows partners to trigger transfer balance from account balance to BANK Account
This API allows partners to trigger transfer balance from their corporate account balance to DOKU customer Account.
This API allows partners to check status top up.
Partners can provide an online payment facility using PIN authentication that can facilitate customers in making the transaction at any merchant that has been integrated. DOKU will provide a webview payment page to input the PIN and proceed with the payment
Partners can cancel the transaction or reverse immediately after successful transaction processing in the DOKU system, it can be used in case of time-out or other problems that occur on the merchant side
Partners can request a refund when the transaction has already settled.
This API allows partners to get history from an account with 1 month range time and the oldest transaction is 1 year behind.
This API allows partners to get transaction details from an account.
Credential partner from DOKU
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Algorithm symmetric signature SHA256withRSA(PrivateKey, StringToSign) SHA256withRSA is used to generate the signature with your Private Key. Generate StringToSign : StringToSign = client_ID+"|"+X-TIMESTAMP
client_credentials
OK
Credential partner from DOKU
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Algorithm symmetric signature SHA256withRSA(PrivateKey, StringToSign) SHA256withRSA is used to generate the signature with your Private Key. Generate StringToSign : StringToSign = client_ID+"|"+X-TIMESTAMP
authorization_code
cfb5de1a-6a40-40e0-8549-0634bcaed8ed
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
f1a69bce-41bc-4abd-8c5c-01910574e404
SNAPaccount11230010
81212340010
SNAPaccount11230010@doku.com
https://doku.com
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Activity ID partners from request AccountCreation
Activity ID DOKU from respond AccountCreation
OTP that user input
Additional Information
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Activity ID from partners
Partner URL when user finish binding
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Identifier activity ID from partners
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Identifier activity ID from partners
Identifier provided from Account Binding
Credential client ID from DOKU
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
Activity ID from partners
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
partnerReferenceNo
customerNumber
beneficiaryAccountNumber
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
partnerReferenceNo
customerNumber
accountType
beneficiaryAccountNumber
beneficiaryBankCode
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
partnerReferenceNo
customerNumber
sessionId
notes
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
originalPartnerReferenceNo
originalReferenceNo
originalExternalId
serviceCode
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
Transaction ID from partners
Default “DOKU”
Detail amount
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
Transaction ID from partners
Unique service API “17”
Transaction date
Detail amount
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
Original Transaction ID from partners
Reason cancelation
Additional Information
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
Original Transaction ID from partners
Reason cancelation
Transaction ID on service consumer system, when for refund payment.
Additional Information
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
Activity ID from partners
Starting time range ISO-8601
Ending time range ISO-8601
Maximum number of transaction returned in one pagination Default 10
Current page number Default 0
Additional Information
OK
Client's current local time in yyyyMMddTHH:mm:ss.SSST ZD format
Credential client ID from DOKU
Reference number that should be unique in the same day
SHA-512 HMAC is used to generate the signature with your Client Secret. Generate stringToSign : HTTPMethod + ”:“+ EndpointUrl +":"+ B2BAccessToken + ":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody)))) + ":“ + X-TimeStamp
Represents access_token of a request, string starts with keyword “Bearer ” followed by Token B2B
Represents access_token of a request belong customer; string starts with keyword “Bearer ” followed by Token B2B2C
Transaction ID from partners
OK