NICEPAY API
...
Payout API (Disbursement) - SN...
Notification - API Payout (Disbursement) SNAP
9 min
about notification api payout (disbursement) snap this api with snap standards uses to send the notification from payout or disbursement proses result 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 ( mailto\ 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 payout (disbursement) snap api endpoint \[merchant domain]/api/v1 0/transfer/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 docid\ uzex33relyenkogbjjnyp request notification body parameter parameter type length required description originalpartnerreferenc eno string 40 mandatory original transaction identifier on consumer system originalreferenceno string 40 mandatory original transaction identifier on service provider system latesttransactionstatus string 2 mandatory category code for the status of the transaction docid\ nvclmbygxr5uc 5qmyu7 example 00 success 03 pending 09 failed transactionstatusdesc object 50 optional description status transaction beneficiarybankcode string 4 mandatory beneficiary docid 5pxu cbdxvy2biili8 cv beneficiaryaccountno string 25 mandatory beneficiary account number beneficiaryname string 100 mandatory beneficiary name amount object variable mandatory amount of transaction value string 12 mandatory value currency string 3 mandatory currency transactiondatetime string 25 optional transaction date using iso 8601 format yyyy mm ddthh\ mm\ ss 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 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 { "originalpartnerreferenceno" "2020102900000000000001", "originalreferenceno" "tnicepo07105202210141451109841", "latesttransactionstatus" "00", "transactionstatusdesc" "success", "beneficiarybankcode" "bbba", "beneficiaryaccountno" "888801000003301", "beneficiaryname" "yories yolanda", "amount" { "value" "12345678 00", "currency" "idr" }, "transactiondatetime" "2019 07 03t12 08 56 07 00" } sample response notification //header section content type application/json x timestamp 2023 11 23t07 44 16+07 00 { "responsecode" "2000000", "responsemessage" "success" }