topic Re: Default MD5 hash value if left unset in Settings in Integration and Testing

Default MD5 hash value if left unset in Settings

bodie — Fri, 24 Mar 2017 17:11:28 GMT

I am updating the DPM process for a legacy applicaiton where the MD5 hash value was an optional value on the merchant side.

I am curious, if the MD5 hash value is never set in Authorize.net settings, is there a default value that is used to generate the x_md5_hash value? Is it a blank string?

I ask because I need to know if I can validate the hash for existing customers who have not configured the MD5 hash value on both Authorize.Net and Merchant side.

Re: Default MD5 hash value if left unset in Settings

RichardH — Tue, 28 Mar 2017 21:31:23 GMT

Hello @bodie

The short answer is no, it's not optional.

For a more detailed answer, please refer to https://community.developer.authorize.net/t5/forums/replypage/board-id/Integration01/message-id/32110

I should also mention that DPM is now deprecated and we encourage merchants to begin migrating to use Accept.js instead of DPM.

Richard