Notification - API Direct Debit

about api direct debit notification will send push s via the dbprocessurl based on provided in registration api direct debit docid 8j0pu1u2uvg7uzuknzzkf the needs to reassure there is no blacklist ip and should whitelist ip to get push only from 's server request method \<font color="#3b9f0f">post\</font> merchant token sha256 ( imid + txid + amt + merchantkey ) ip ip public environtment production 103 20 51 34 103 20 51 33 ip public environtment dev 103 20 51 39 103 20 51 40 user agent user agent jakarta commons httpclient/3 1 notification parameter direct debit notification when your dbprocessurl received a , strongly recommend to verify using status inquiry api direct debit docid\ b6ctfh0si5ntzuljbwtnd parameter type length description example / notes txid \<font color="#2166ae">required\</font> n 30 transaction id tnicecp04100202210201205567417 merchanttoken \<font color="#2166ae">required\</font> an 255 token ecd49958d29595d09cd7ccab6057e9db119dfeb83676c27fb7649d3393b911aa referenceno \<font color="#2166ae">required\</font> ans 40 order number ord20250307130386 mitracd \<font color="#2166ae">required\</font> a 4 mitra code docid\ tm257gq3dxgzf98uz0l33 jenc paymethod \<font color="#2166ae">required\</font> n 2 payment method code docid\ iifmsruuw7j9vmwefjz97 04 payno \<font color="#2166ae">optional\</font> n 20 number 504100002539 payvalidtm \<font color="#2166ae">optional\</font> n 6 cvs expiry time ( hh24miss ) null payvaliddt \<font color="#2166ae">optional\</font> n 8 expiry date ( yyyymmdd ) null amt \<font color="#2166ae">required\</font> n 12 amount 10000 clientuserkey \<font color="#2166ae">mandatory if tokenize \</font> an 100 user key, must be unique for each 1134431 usertoken \<font color="#2166ae">optional\</font> ans 255 user token 12345eea9 6234 6789 12r3 123re3456tt5 tokenizeuser \<font color="#2166ae">optional\</font> n 1 transaction tokenize type 1 transdt \<font color="#2166ae">optional\</font> n 8 transaction date 20221020 transtm \<font color="#2166ae">optional\</font> n 6 transaction time 120803 currency \<font color="#2166ae">required\</font> a 3 currency idr goodsnm \<font color="#2166ae">required\</font> an 100 goods name john doe billingnm \<font color="#2166ae">required\</font> a 100 billing name john doe receiptcode \<font color="#2166ae">required\</font> ans 20 authorization number 951523387713 instmnttype \<font color="#2166ae">required\</font> n 2 installment type code docid\ rt2c32s9hfl aohyoebv5 2 instmntmon \<font color="#2166ae">required\</font> n 2 installment month 1 1 month/full , if instmnttype null/1 3 3 months 6 6 months 12 12 months 1 mrefno \<font color="#2166ae">required\</font> an 18 reference number 202503071335234 matchcl \<font color="#2166ae">required\</font> n 1 flag notification match amount indicator docid wbzuzhpbdoycdehlbbx9 1 status \<font color="#2166ae">required\</font> a 1 deposit status notification status code docid\ ucni27ufonck8 zttm mv 0 deposit 1 reversal 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 sample for direct debit notification sample post for direct debit) notification merchanttoken=ecd49958d29595d09cd7ccab6057e9db119dfeb83676c27fb7649d3393b911aa goodsnm=john doe referenceno=ord20250307130386 transtm=133600 txid=tnicecp04104202503071335233256 amt=10000 receiptcode=951523387713 instmnttype=2 billingnm=john doe matchcl=1 mrefno=202503071335234 paymethod=04 currency=idr instmntmon=1 transdt=20250307 status=0