Notification - API Paylater

about api paylater notification provides push s via dbprocessurl 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 18 98 96 50 ip public environtment dev 103 20 51 39 103 20 51 40 18 98 96 54 user agent user agent jakarta commons httpclient/3 1 notification parameter paylater notification when your dbprocessurl received a , strongly recommend to verify using status inquiry api paylater docid\ c7by1comgvlnauoqjixnx parameter type size description example / notes txid n 30 transaction id payloantes06202212141610281704 merchanttoken an 255 token 0716e8cbb7bac584efa98df5021543e11fab1a520415f1382572eadcca81107f referenceno ans 40 order number ord20221214161263 paymethod n 2 payment method code docid\ nq1y7vma25ztvqhn5he6w 06 amt n 12 amount 25145 goodsnm an 100 goods name testing matchcl n 1 flag notification match amount indicator docid\ hhezyw5ikliptkqyya5bi null status a 1 deposit status notification status code docid\ qumt9fmvjdh5gjhd2pwy8 0 deposit 1 reversal 0 mitracd a 4 mitra code docid 0lup35kfowksisrzkx6yz kdvi transtm n 6 transaction time ( hh24miss ) 155852 clientuserkey \<font color="#2166ae">mandatory if tokenize\</font> an 100 user key, must be unique for each 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 mitra code docid 0lup35kfowksisrzkx6yz payno n 12 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 token received by notification endpoint must compare 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 paylater notification sample post for paylater 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