topic Re: DPM – PHP (response_code 3) in Integration and Testing

DPM – PHP (response_code 3)

mark0ne — Mon, 04 Jun 2012 13:13:42 GMT

Hi,

I receive an error (response_code) # 3 regardless if the credit card info is legitimate or test data. This occurs for both a test (sandbox) account or a real account. Either way, the connection to Authorize.net seems successful because if the account is switched to test mode, the response_reason_text includes “(TESTMODE)”. This leads me to believe my site and Authorize.net are successfully communicating with each other.

The response page only gets back the following GET values from the Authorize.net site (printing all GET values):

Array ( [response_code] => 3 [response_reason_text] => This transaction cannot be accepted. )

Adding a Relay Response URL value (the same passed in AuthorizeNetDPM::getCreditCardForm) in the Authorize.net merchant website does change the results, but not in a very helpful way. I receive an email message with the text below (the transaction ID is always zero), and the browser stays at

https://secure.authorize.net/gateway/transact.dll:

Your script timed out while we were trying to post transaction results to it.

Transaction ID: 0

Transaction Result: The referrer, relay response or receipt link URL is invalid.

Re: DPM – PHP (response_code 3)

RaynorC1emen7 — Mon, 04 Jun 2012 13:22:28 GMT

Array ( [response_code] => 3 [response_reason_text] => This transaction cannot be accepted. )

That Response_reason_Text point to x_fp_hash or x_fp_timestamp being wrong.

Try

http://developer.authorize.net/tools/responsecode97/

and

https://developer.authorize.net/tools/responsecode99/

And for

The referrer, relay response or receipt link URL is invalid

Read Relay Response Basics and Troubleshooting

Re: DPM – PHP (response_code 3)

mark0ne — Mon, 04 Jun 2012 15:43:25 GMT

Thanks - the problem turned out to be a leading space in the amount value.