Notification - API QRIS

about api qris 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 qris notification when your dbprocessurl received a {{notification}} , {{nicepay}} strongly recommend {{merchant}} to verify {{the}} {{notification}} using {{the}} status inquiry api qris docid\ i34g2mhsezzv2y4d1bj7y parameter type size description example / notes txidxample n 30 transaction id ionpaytest08202212141041407785 merchanttoken an 255 {{merchant}} token 69ba08191f47af25dd3ea089a99f89a6cb05295f9e641a78e8e44f5f75891cc7 referenceno ans 40 {{merchant}} order number ord54321 paymethod n 2 payment method code docid\ ek 0djw7nuhytcda4sa3p 08 paymenttrxsn an 32 {{paymentproduct}} transaction number 112160983971452364 userid an 128 {{qris}} user id hash 8bf254cdb4dfff447233a67e796556db7653c40234edb979614f007dfa8eb7c1 amt n 12 {{paymentproduct}} amount 5 mitracd n 4 mitra code docid 0upx1lyg1o2f4biu3ssp qshp transdt n 8 transaction date 20221214 transtm n 6 transaction time 104140 currency a 3 currency idr goodsnm an 100 goods n=name test+transaction+ {{nicepay}} billingnm a 100 billing name andi+pamungkas matchcl n 1 {{paymentproduct}} flag notification match amount indicator docid yqqe4ju5bjurdxkxdtho 1 status a 1 deposit status notification status code docid\ qahrf3q4g85njtqxmwfyk 0 deposit 1 reversal 0 shopid required for qris required for qris an 32 shop id {{nicepay}} additional parameter for qris notification parameter type size description paymenttrxsn an 32 {{paymentproduct}} transaction number userid an 128 {{qris}} user id hash shopid an 32 shop id 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 qris notification sample post for qris notification merchanttoken = 69ba08191f47af25dd3ea089a99f89a6cb05295f9e641a78e8e44f5f75891cc7 goodsnm = test+transaction+nicepay referenceno = ord54321 transtm = 104140 mitracd = qshp txid = ionpaytest08202212141041407785 amt = 5 paymenttrxsn = 112160983971452364 userid = 8bf254cdb4dfff447233a67e796556db7653c40234edb979614f007dfa8eb7c1 billingnm = andi+pamungkas matchcl = 1 paymethod = 08 currency = idr shopid = nicepay transdt = 20221214 status = 0