NICEPAY API
...
Payment API - SNAP
API QRIS SNAP
Notification - API QRIS SNAP
9 min
about notification api qris snap this api with snap standards uses to send payment transaction notifications on the qris payment method x signature guidance validation the following is guidance to proceed x signature validation on request header notify sha256withrsa (public key, stringtosign) stringtosign = client id + “|” + x timestamp information specific to {{the}} {{snap}} notification {{api}} regarding {{the}} public key will be provided by {{the}} {{nicepay}} team to {{the}} {{merchant}} via email, because {{the}} public key credential used in {{the}} {{snap}} notification {{api}} is different from {{the}} {{snap}} transaction {{api}} (registration, inquiry & {{paymentproduct}} ) {{please}} contact {{the}} integration team through email ( integration\@nicepay co id ) for further {{information}} or assistance the following is the example of x signature result from the above guidance validation" myyscwbs00bm0tjq/xy7uu1goh8qxjyyslo88rfrhq+mlyqkmtq nkmlzdps+ merchant notification api qris snap service code 52 api endpoint \[merchant domain]/api/v1 0/qr/qr mpm notify http method post content type application/json description transaction result notification (when success) if your system use firewall, add allow policy for nicepay ip 103 20 51 0/24 103 117 8 0/24 request notification header parameter parameter type required description content type string mandatory application / json x timestamp string mandatory using iso 8601 as timestamp format transaction date time, in format yyyymmddthh\ mm\ ss+07 00 time must be in gmt+7 (jakarta time) 2022 03 21t10 11 40+07 00 x client key string mandatory unique partner id, partner id = client id x signature string mandatory signature will be generated by merchant snap api testing request notification body parameter parameter type length required description originalreferenceno string 40 mandatory original transaction identifier on service provider system originalpartnerreferenceno string 40 mandatory original transaction identifier on consumer system amount object variable mandatory amount of transaction value string 12 mandatory value currency string 3 mandatory currency latesttransactionstatus string 2 mandatory category code for the status of the transaction example 00 success 05 cancelled transactionstatusdesc string 50 optional description status transaction externalstoreid string 32 mandatory unique identifier of shop id in client system additionalinfo object variable mandatory additional information transactiondatetime string 25 optional transaction date using iso 8601 format yyyy mm ddthh\ mm\ ss paymenttrxsn object 32 mandatory payment transaction number from acquiring side userid string 128 optional qris user id response notification header parameter parameter type required description content type string mandatory application / json x timestamp string mandatory using iso 8601 as timestamp format transaction date time, in format yyyymmddthh\ mm\ ss+07 00 time must be in gmt+7 (jakarta time) 2022 03 21t10 11 40+07 00 response notification body parameter parameter type length required description responsecode string 7 mandatory general response code and message api snap docid\ bjr4kjamzcknln 5zrnvw responsemessage string 150 mandatory response message sample post for notification sample request notification //header section content type application/json x timestamp 2023 11 23t07 44 11+07 00 x signature 85be817c55b2c135157c7e89f52499bf0c25ad6eeebe04a986e8c862561b19a5 x client key 82150823919040624621823174737537 { "originalreferenceno" "tniceqr08108202210141451109841", "originalpartnerreferenceno" "2020102900000000000001", "latesttransactionstatus" "00", "transactionstatusdesc" "success", "amount" { "value" "12345678 00", "currency" "idr" }, "externalstoreid" "124928924949487", "additionalinfo" { "transactiondatetime" "2019 07 03t12 08 56 07 00", "paymenttrxsn" "07202210051341224326", "userid" "13nauasiqbih341bdjashf1204gkjbcas" } } sample response notification //header section content type application/json x timestamp 2023 11 23t07 44 16+07 00 { "responsecode" "2005200", "responsemessage" "success" }