Notification - API Convenience Store

about api convenience store notification {{nicepay}} provides push {{notification}} s via dbprocessurl {{merchant}} the {{merchant}} needs to reassure there is no blacklist {{nicepay}} ip and should whitelist {{nicepay}} ip to get {{the}} push {{notification}} only from {{nicepay}} 's server request method post 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 notification parameter convenience store when your dbprocessurl received a {{notification}} , {{nicepay}} strongly recommend {{merchant}} to verify {{the}} {{notification}} using {{the}} docid 79r7v9ynenetfidqqvmkk parameter type size description example / notes txid n 30 transaction id tnicecv03103202212141459041632 merchanttoken an 255 {{merchant}} token 8b5565e793731a1a1c8817c9e42bcbbdc3f5fb6a2785a6e0b19a2d5e3a41a51b referenceno ans 40 {{merchant}} order number ord0123456 mitracd a 4 docid 0upx1lyg1o2f4biu3ssp alma paymethod n 2 docid\ ek 0djw7nuhytcda4sa3p 04 payno n 20 {{paymentproduct}} number 504100002539 payvalidtm n 6 cvs expiry time ( hh24miss ) null payvaliddt n 8 cvs expiry date ( yyyymmdd ) (cvs) null amt n 12 {{paymentproduct}} amount 5000 clientuserkey mandatory if tokenize mandatory if tokenize an 100 user key, must be unique for each {{customer}} 1134431 usertoken ans user token 12345eea9 6234 6789 12r3 123re3456tt5 tokenizeuser n 1 transaction tokenize type 1 transdt n 8 transaction date 20221214 transtm n 6 transaction time 150229 currency a 3 currency idr goodsnm an 100 goods name testing billingnm a 100 billing name john doe matchcl n 1 {{paymentproduct}} flag docid yqqe4ju5bjurdxkxdtho 1 status a 1 deposit status docid\ qahrf3q4g85njtqxmwfyk 0 deposit 1 reversal 0 instmnttype n 2 docid\ wfsinjxqc2s9yubbybpep 1 instmntmon n 2 installment month 1 the {{merchant}} token received by {{the}} notification endpoint must compare internally to prevent fake/invalid {{notification}} s 💡example case for example, you have a merchantkey that is used to generate a token, which is 1234 when {{the}} merchanttoken generated by {{the}} {{merchant}} is known, it is abcd , while {{the}} merchanttoken obtained in {{the}} {{notification}} is abdd then {{the}} {{notification}} is considered fake/invalid sample for convenience store notification sample post for convenience store notification merchanttoken=8b5565e793731a1a1c8817c9e42bcbbdc3f5fb6a2785a6e0b19a2d5e3a41a51b goodsnm=testing referenceno=ord0123456 mitracd=alma transtm=150229 txid=tnicecv03103202212141459041632 amt=5000 instmnttype=1 billingnm=john doe matchcl=1 payno=504100002539 payvalidtm=null paymethod=03 currency=idr instmntmon=1 payvaliddt=null transdt=20221214 status=0