Notification - API Payloan

about api payloan 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 payloan notification when your dbprocessurl received a {{notification}} , {{nicepay}} strongly recommend {{merchant}} to verify {{the}} {{notification}} using {{the}} docid\ ikbnpmy56gww3hk0v3emu parameter type size description example / notes txid n 30 transaction id payloantes06202212141610281704 merchanttoken an 255 {{merchant}} token 0716e8cbb7bac584efa98df5021543e11fab1a520415f1382572eadcca81107f referenceno ans 40 {{merchant}} order number ord20221214161263 paymethod n 2 docid\ ek 0djw7nuhytcda4sa3p 06 amt n 12 {{paymentproduct}} amount 25145 goodsnm an 100 goods name testing matchcl n 1 {{paymentproduct}} flag docid yqqe4ju5bjurdxkxdtho null status a 1 deposit status docid\ qahrf3q4g85njtqxmwfyk 0 deposit 1 reversal 0 mitracd a 4 docid 0upx1lyg1o2f4biu3ssp kdvi transtm n 6 transaction time ( hh24miss ) 155852 clientuserkey mandatory if tokenize mandatory if tokenize an 100 user key, must be unique for each {{customer}} 1134431 billingnm a 100 buyer name john doe transdt n 8 transaction date 20221214 currency a 3 currency idr tokenizeuser n 1 transaction tokenize type 1 usertoken ans user token 12345eea9 6234 6789 12r3 123re3456tt5 additional parameter for others payment method notification parameter type size description mitracd a 4 docid 0upx1lyg1o2f4biu3ssp payno n 12 {{paymentproduct}} number payvaliddt n 8 expiry date ( yyyymmdd ) payvalidtm n 6 expiry time ( hh24miss ) receiptcode ans 20 authorization number mrefno an 18 reference number depositdt n 8 deposit date ( yyyymmdd ) deposittm n 6 deposit time ( hh24miss ) 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 payloan notification sample post for payloan notification merchanttoken=0716e8cbb7bac584efa98df5021543e11fab1a520415f1382572eadcca81107f goodsnm=testing referenceno=ord20221214161263 mitracd=kdvi transtm=155852 txid=payloantes06202212141610281704 amt=25145 clientuserkey=1134431 billingnm=john doe matchcl=null usertoken=12345eea9 6234 6789 12r3 123re3456tt5 paymethod=06 tokenizeuser=1 currency=idr transdt=20221214 status=0