Reply
Highlighted
Member
Posts: 6
Registered: ‎09-17-2009

DPM Clarifications

Integrating DPM for the first time.  I've read many of the DPM posts as well as the docs.  Still need some clarification though:

 

1. The sample PHP code has $md5_setting = $api_login_id .  What should the MD5 value really be?  DPM docs don't seem to explain this anywhere.

 

2. Is there really a need for relay_response.php AND order_receipt.php, or can these be combined into a single script that: A. handles error processing, or B. processes a successful transaction and displays a receipt?  Having a redirect just seems like one extra place where something could go wrong.

 

Thank you!

Highlighted
Member
Posts: 6
Registered: ‎09-17-2009

Re: DPM Clarifications

Just to clarify 2 above, the DPM docs indicate that the relay should provide a code snippet back to AN, which is then sent back to the browser for a redirect to take place.  However, looking at samples/your_store/process_sale.php, getRelayResponseSnippet($return_url) is called, which simply redirects to a local URL on the server, and not back to AN.

Highlighted
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: DPM Clarifications

1)It should be same as in the merchant account settings.

 

2)see if this help http://developer.authorize.net/api/howitworks/dpm/

Highlighted
Member
Posts: 6
Registered: ‎09-17-2009

Re: DPM Clarifications

I heard back from AN support.  Apparently the documentation is a bit lacking.  Where it says YOUR_API_LOGIN_ID for the $md5_setting, it should indeed be the MD5 Hash from the account settings; this is being reported to get fixed.  It also appears that for DPM, the relay "simply redirect[s] the customer back to the merchant's site," so combining the scripts should be fine.

Highlighted
Posts: 1,609
Topics: 15
Kudos: 201
Solutions: 121
Registered: ‎06-23-2011

Re: DPM Clarifications

MD5 can be left blank if you haven't generated a value for it.