Integration and Testing

Authorize.Net API questions and help with your payment integration.

Posts: 1
Registered: ‎03-24-2017

Default MD5 hash value if left unset in Settings

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 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.

Posts: 2,765
Topics: 57
Kudos: 272
Blog Posts: 67
Registered: ‎12-05-2011

Re: Default MD5 hash value if left unset in Settings

Hello @bodie


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


For a more detailed answer, please refer to


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