Hey
@wenabar16,
I regret that you’re having trouble with the hash verification on DPM. I didn’t expect to see you back or I would have given you a heads up that my sample code for DPM erroneously had an extra ^ at the beginning. I did that as a favor for some here. I use a different integration and had no DPM app to test on. The other person’s code I referenced has the correct string.
In regards to that extension, it uses the accept.js integration, which is a modern integration method. It will be around for a good while. DPM is deprecated and won’t be around forever. And I am just quoting docs from this website. I looked at the pdf you attached, and it is for magento 2.2. So the question is if an extension is good for 2.2, is it also good for 2.2.x.
If I were in your shoes I would be getting the accept.js extension or some other extension for a modern integration method. With that said, out of curiousity, what was the issue you ran into with the sha512 validation? Is it the the extension is preconfigured in a way that you can’t really make changes to the underlying code? And to your other question- accept.js doesn’t use md5 and you don’t have to submit a sha512 or md5 hash to complete a transaction. The pdf you linked says that the extension uses webhooks to capture responses for you. The md5 issue will not affect you at all, if you are able to use that extension in your app.
