Notification - API Direct Debit
will send push s via the dbProcessUrl based on provided in Registration - API Direct Debit. The needs to reassure there is no Blacklist IP and should Whitelist IP to get push only from 's server.
Request Method | POST |
|---|---|
Merchant Token | SHA256 ( iMid+ tXid + amt+ merchantKey) |
IP | 103.20.51.0/24 103.117.8.0/24 |
User-Agent | User-Agent: Jakarta Commons-HttpClient/3.1 |
When your dbProcessUrl received a , strongly recommend to verify using Status Inquiry - API Direct Debit.
Parameter | Type | Length | Description | Example / Notes |
|---|---|---|---|---|
tXid Required | N | 30 | Transaction ID | TNICECP04100202210201205567417 |
merchantToken Required | AN | 255 | Token | ecd49958d29595d09cd7ccab6057e9db119dfeb83676c27fb7649d3393b911aa |
referenceNo Required | ANS | 40 | Order Number | ORD20250307130386 |
mitraCd Required | A | 4 | JENC | |
payMethod Required | N | 2 | 04 | |
payNo Optional | N | 20 | Number | 504100002539 |
payValidTm Optional | N | 6 | CVS Expiry Time (HH24MISS) | null |
payValidDt Optional | N | 8 | Expiry Date (YYYYMMDD) | null |
amt Required | N | 12 | Amount | 10000 |
clientUserKey Mandatory if tokenize | AN | 100 | User Key, Must be Unique for Each | 1134431 |
userToken Optional | ANS | 255 | User Token | 12345eea9-6234-6789-12r3-123re3456tt5 |
tokenizeUser Optional | N | 1 | Transaction Tokenize Type | 1 |
transDt Optional | N | 8 | Transaction Date | 20221020 |
transTm Optional | N | 6 | Transaction Time | 120803 |
currency Required | A | 3 | Currency | IDR |
goodsNm Required | AN | 100 | Goods Name | John Doe |
billingNm Required | A | 100 | Billing Name | John-Doe |
receiptCode Required | ANS | 20 | Authorization Number | 951523387713 |
instmntType Required | N | 2 | 2 | |
instmntMon Required | N | 2 | Installment Month 1: 1 Month/Full , if instmntType: null/1 3: 3 Months 6: 6 Months 12: 12 Months | 1 |
mRefNo Required | AN | 18 | Reference Number | 202503071335234 |
matchCl Required | N | 1 | Flag: Notification Match Amount Indicator | 1 |
status Required | A | 1 | 0 |
must compare again every Token received by Notification internally to prevent fake/invalid s.
💡Example Case:
For example, you have a merchantKey that is used to generate a token, which is 1234. When merchantToken generated by is known, it is abcd, while merchantToken obtained in is abdd. Then is considered fake/invalid.