You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-- In the documentation, it was written that "postData" should be a string of concatenated values of the request-body object, which should be created by sorting keys in "descending" order, excluding the "signature" key and encryption type should be set to "base64".
-- But in function, it is treating the body as an "object" and converting it using "toString()" then encrypting it in "hex" rather than "base64".
-- code has been fixed and PR has been raised.
The text was updated successfully, but these errors were encountered:
oshinpojta
changed the title
"verifySignature" function not working for Payouts.
"verifySignature" function not working in lib/payouts/services.
Jul 29, 2023
-- In the documentation, it was written that "postData" should be a string of concatenated values of the request-body object, which should be created by sorting keys in "descending" order, excluding the "signature" key and encryption type should be set to "base64".
-- But in function, it is treating the body as an "object" and converting it using "toString()" then encrypting it in "hex" rather than "base64".
-- code has been fixed and PR has been raised.
The text was updated successfully, but these errors were encountered: