Relay Response url is not invoked

hasykes — Sat, 29 Dec 2012 22:23:33 GMT

Thank you in advance for any help. I have been banging my head for several weeks trying to isolate why the following problem arises, but am tapped out of ideas. Of all the relay response posts in the forum, this one has unique attributes, so I am starting a new thread.

Configuration:

Authorize.net interface: SIM

A.net environment: test.authorize.net

Language: Classic ASP

Have read manuals, Michelle's "Relay Response Basics and Troubleshooting", used sample code, read all relevant forum posts, and have run successful direct test calls to the relay response url using valid transaction data.

Numerous tests appear to work successfully. Emails to customer and merchant all indicate successful transactions. However, at the point when the relay response module should be invoked matters grind to a halt.

A.net return codes and messages indicate transactions process successfully (see test case post-transaction data below displayed by ...tools/paramdump/index.php).

The merchant is sent an email indicating a successful transaction (see test case text below).

The relay response url passed to the payment gateway, and listed in the A.net settings is:

https://1780805.sites.myregisteredsite.com/store2/AUTHORIZENET_callback.asp

Despite the apparent success of transactions, once the payment form has been submitted, the next message displayed by a url,

https://test.authorize.net/gateway/AUTHORIZENET_callback.asp?cookiecheck=yes& is:

The following errors have occurred.

(13) The merchant login ID or password is invalid or the account is inactive.

The html for the page is:

<HTML><BODY><H3>The following errors have occurred.</H3>(13) The merchant login ID or password is invalid or the account is inactive.<BR></BODY></HTML>

This html is not generated by the relay response module. Further, I cannot determine why the "13" error code happens because the post to the A.net payment form is working just fine.

It also is very curious that the message is appears to come from a url that is a combination of A.net (test.authorize.net/gateway), and the intended relay response module (AUTHORIZENET_callback.asp)

The parameter, cookiecheck=yes&, indicate that AUTHORIZENET_callback.asp may have been called, but any errors passed by A.net would be trapped and displayed by the relay response module.

_________________

Start of post-transaction data

https://test.authorize.net/gateway/transact.dll displayed the following information, all of which appears fine:

REMOTE_ADDR:	10.1.186.51
REQUEST_METHOD:	POST
HTTP_REFERER:	none

This is a test mode transaction.

Field Name	Field Value
x_response_code	1
x_response_reason_code	1
x_response_reason_text	(TESTMODE) This transaction has been approved.
x_avs_code	P
x_auth_code	000000
x_trans_id	0
x_method	CC
x_card_type	Visa
x_account_number	XXXX8888
x_first_name	Hxxx
x_last_name	Sxxx
x_company
x_address	76 Mxxx
x_city	Nxxx
x_state	CT
x_zip	06xxx
x_country	USA - Connecticut
x_phone	203-xxx-xxxx
x_fax
x_email	ha---
x_invoice_num	3561
x_description	2 x Lines/Outhaul line - 1/4X 15white for standard 2:1 rig (Trophy) (150890) 1 x Forestay/Forestay extension heavy duty - 1/8(660039)
x_type	auth_capture
x_cust_id	10
x_ship_to_first_name	Hxxx
x_ship_to_last_name	Sxxx
x_ship_to_company
x_ship_to_address	76 Mxxx
x_ship_to_city	Nxxx
x_ship_to_state	CT
x_ship_to_zip	06xxx
x_ship_to_country	USA - Connecticut
x_amount	54.21
x_tax	0.00
x_duty	0.00
x_freight	0.00
x_tax_exempt	FALSE
x_po_num
x_MD5_Hash	75FAFEFE465DFF7DA11FA6E3E66A9F1B
x_cvv2_resp_code
x_cavv_response
x_test_request	true
x_method_available	true

End of post-transaction data

_____________________________________

Start of test case text emailed to Merchant:

************* TEST MODE *************

**Please DO NOT REPLY to this message. E-mail developer@authorize.net if you have any questions.

========= SECURITY STATEMENT ==========

It is not recommended that you ship product(s) or otherwise grant services relying solely upon this e-mail receipt.

========= GENERAL INFORMATION =========

Merchant : Henry Sykes (3xxxxx)

Date/Time : 29-Dec-2012 15:30:40 EST

========= ORDER INFORMATION =========

Invoice : 3566

Description : 1 x Anchor, paddles, bailing scoop/Anchor bracket with screws (690974)

1 x Anchor, paddles, bailing scoop/Anchor and line - 8 lb. traditional and 100'X 5/16 nylon (690970) Amount : 99.64 (USD) Payment Method : Visa Type : Authorization and Capture

============== RESULTS ==============

Response : This transaction has been approved.

Authorization Code : 000000

Transaction ID : 0

Address Verification : AVS Not Applicable

==== CUSTOMER BILLING INFORMATION ===

Customer ID : 10

First Name : Hxxx

Last Name : Sxxx

Company :

Address : 76Mxxx

City : Nxxx

State/Province : CT

Zip/Postal Code : 06xxx

Country : USA - Connecticut

Phone : 203-xxx-xxxx

Fax :

E-Mail : hasyk1@comcast.net

==== CUSTOMER SHIPPING INFORMATION ===

First Name : Hxxx

Last Name : Sxxx

Company :

Address : 76Mxxx

City : Nxxx

State/Province : CT

Zip/Postal Code : 06xxx

Country : USA - Connecticut

======= ADDITIONAL INFORMATION ======

Tax :

Duty :

Freight :

Tax Exempt :

PO Number :

========== MERCHANT DEFINED =========

x_method_available : true

End of Test case text emailed to merchant

Re: Relay Response url is not invoked

RaynorC1emen7 — Sun, 30 Dec 2012 00:22:27 GMT

Look to me that the

https://1780805.sites.myregisteredsite.com/store2/AUTHORIZENET_callback.asp

is trying to redirect but didn't use absolute path, but using a relative path with ?cookiecheck=yes&

When I go to the link https://1780805.sites.myregisteredsite.com/store2/AUTHORIZENET_callback.asp

It turn to https://1780805.sites.myregisteredsite.com/store2/AUTHORIZENET_callback.asp?cookiecheck=yes&

Re: Relay Response url is not invoked

hasykes — Sun, 30 Dec 2012 01:22:14 GMT

...is trying to redirect but didn't use absolute path, but using a relative path with ?cookiecheck=yes&...

Thank you. I will check whether the path is relative or absolute.

Re: Relay Response url appears not to be invoked

hasykes — Sun, 30 Dec 2012 22:47:46 GMT

Thank you RaynorC1emen7. Some redirect logic was the cause. Working around that logic enables the transaction to complete successfully.

topic Re: Relay Response url appears not to be invoked in Integration and Testing

Relay Response url is not invoked

Re: Relay Response url is not invoked

Re: Relay Response url is not invoked

Re: Relay Response url appears not to be invoked