Home response checksum or hash not matching in payumoney?

# response checksum or hash not matching in payumoney?

kofhearts
1#
kofhearts Published in 2018-01-12 14:28:17Z
 When notification is passed to the app after payumoney processing it sends response hash and we need to compute the hash and match it with the passed in response hash. I use the following code to compute the expected response hash. Digest::SHA512.hexdigest([ PAYU_SALT, notification.transaction_status, notification.user_defined, notification.customer_email, notification.customer_first_name, notification.product_info, notification.gross, notification.invoice, PAYU_KEY].join("|"))  The hash of the following string is computed "salt|success|||||||||||||Payment|100.0|1|key"  When I print the following hash it gives Digest::SHA512.hexdigest([ PAYU_SALT, notification.transaction_status, notification.user_defined, notification.customer_email, notification.customer_first_name, notification.product_info, notification.gross, notification.invoice, PAYU_KEY].join("|")) #⇒ e7b3c5ba00b98aad9186a5e6eea65028a[...]  whereas notification.checksum gives  #⇒ 546f5d23e0cadad2d4158911ef72f095d[...]  So the two hashes don’t match. I am using the following gem: https://github.com/payu-india/payuindia I appreciate any help as to why the response hash is not matching. Is there any error in my logic to compute the response hash? Thanks!
Stefan R
2#
Stefan R Reply to 2018-01-12 14:54:06Z
 Where did you come up with that order for the fields in the array? Looking at PayU's Developer FAQ it seems like the order is the following: key|txnid|amount|productinfo|firstname|email|||||||||||salt  Please make sure that the hash is calculated in the following format - hashSequence= key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3|udf4|udf5||||||salt Please make sure that in the above sequence please use the UDFs which have also been posted to our server. In case you haven't posted any UDFs, the hash sequence should look like this - hashSequence= key|txnid|amount|productinfo|firstname|email|||||||||||salt. Keep in mind that when computing the hash even a single character out of place will result in a completely different checksum.
kofhearts
3#