Relayed response - no receipt page shown or url redirect

[mho]

We are using Server Integration Method (SIM) in asp.net c#

We succeed to pass payment info, and after submitting it, the relayed response is working, but the receipt page is never showen - the following error occurred:

 An error occurred while trying to report this transaction to the merchant.
An e-mail has been sent to the merchant informing them of the error. The
following is the result of the attempt to charge your credit card. 

This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will
receive the product or service.

The transaction seems to be done, but we never gets redirected to receipt page or our own server. When we set relayed response to false, we do get the receipt page, but neither a redirect back.

The relayed response url is working properly when we executes it locally.

Have set both: x_relay_response, x_relay_url, x_receipt_link_url, but none in the merchant account settings.

Any one knows what the problem is? 

[mho]

All right..

Seems difficult to achieve what I want then.

I want a hosted payment form(like SIM), with a relay(server to server)(like DPM). Want the SIM relay_response like DPM, but in SIM it is a user redirect/post, not a server to server.

Is there a method to achieve this?

[RaynorC1emen7]

Not sure about when you said server to server mean?Both SIM and DPM relay work the same way.

The customer post cc info to https://????.authorize.net/gateway/transact.dll. Authorize.net process it, relay the response from the bank processor to the url on the x_relay_url. Then you do what ever you need to do to the result post info.

[mho]

Okay. We are experiencing that when we redirect the relayed response to a page at our server, what happens is that the Authorize.net server our page but the browser show it under the Authorize.net url: https://test.authorize.net/gateway/transact.dll. Can you confirm this behavior?

You said before that the x_relay_url should be matched in the merchant account, but we are now experiencing that it works if the merchant account urls is cleared and we pass a url with x_relay_url. Just to let you know..

Our other possibility is to use the set the x_relay_response to false and use the receipt page, but if this option should be useful for us, it require that link to redirect from the receipt page can be dynamic made. Is that possibly? (Setting x_receipt_link_url and x_receipt_link_method ? how?)

The problem with this method is, as I understand it, that when the receipt page is shown, the transaction is completed but if the user closes the browser without clicking the link, our site won't know that the transaction is completed.

How do the "Link", "Get" and "Post" options differ in behavior? There don't seems to happen anything when we set it to "Get" or "Post"..

[mho]

And a bit more..

While testing we tried to see if successful orders were registered at https://sandbox.authorize.net/. But while in testmode the transactions were not registered, even though I got a relay with a successful transaction. Is that possibly to get them registered in testmode?

But then when we disabled testmode, orders was registered at https://sandbox.authorize.net/, but the relay gave the same error as in the first post. I find it a bit strange that the same code work so differently of testmode?

I have then tested the "csharp_sim" example to see if it works there, with relay response.

I have added the following lines(code behind):

x_relay_response.Value = "true";

x_relay_url.Value = "http://uc01.getaccess.dk/umbraco/Relay.html";

//"https://developer.authorize.net/tools/paramdump/index.php";

(view):

<inputtype='hidden'runat="server"name='x_relay_response'id='x_relay_response'/>

<inputtype='hidden'runat="server"name='x_relay_url'id='x_relay_url'/>

When I set relay_url to https://developer.authorize.net/tools/paramdump/index.php it shows the page as expected, but when I set relay_url to http://uc01.getaccess.dk/umbraco/Relay.html the error shows.

Please test for you self... I don't really have a clue anymore how to solve this..

[RaynorC1emen7]

Okay. We are experiencing that when we redirect the relayed response to a page at our server, what happens is that the Authorize.net server our page but the browser show it under the Authorize.net url: https://test.authorize.net/gateway/transact.dll. Can you confirm this behavior?

Yes, this is correct. That why they suggest to do a javascript redirect on your page after it process the post data Authorize.net.

Our other possibility is to use the set the x_relay_response to false and use the receipt page, but if this option should be useful for us, it require that link to redirect from the receipt page can be dynamic made. Is that possibly? (Setting x_receipt_link_url and x_receipt_link_method ? how?)

The problem with this method is, as I understand it, that when the receipt page is shown, the transaction is completed but if the user closes the browser without clicking the link, our site won't know that the transaction is completed.

How do the "Link", "Get" and "Post" options differ in behavior? There don't seems to happen anything when we set it to "Get" or "Post"..

x_receipt_link_url is the url location on your server.

x_receipt_link_method is just how they will send you the data. Use Request.Form for "POST" and Request.QueryString for "GET".

There is something call "slient post" that will post the result separately, if you want to receipt page. As far as I know it work the same way as relay response. Read more by searching "silent" on https://support.authorize.net/

While testing we tried to see if successful orders were registered at https://sandbox.authorize.net/. But while in testmode the transactions were not registered, even though I got a relay with a successful transaction. Is that possibly to get them registered in testmode?

But then when we disabled testmode, orders was registered at https://sandbox.authorize.net/, but the relay gave the same error as in the first post. I find it a bit strange that the same code work so differently of testmode?

Since livemode is what you will use on the production account, there is really no good reason to run testmode on the sandbox account.

I have then tested the "csharp_sim" example to see if it works there, with relay response.

I have added the following lines(code behind):

x_relay_response.Value = "true";

x_relay_url.Value = "http://uc01.getaccess.dk/umbraco/Relay.html";

//"https://developer.authorize.net/tools/paramdump/index.php";

(view):

<inputtype='hidden'runat="server"name='x_relay_response'id='x_relay_response'/>

<inputtype='hidden'runat="server"name='x_relay_url'id='x_relay_url'/>

When I set relay_url to https://developer.authorize.net/tools/paramdump/index.php it shows the page as expected, but when I set relay_url to http://uc01.getaccess.dk/umbraco/Relay.html the error shows.

Please test for you self... I don't really have a clue anymore how to solve this..

.html have the same issue as aspx when it is serve from IIS. You might just as well use a .aspx page. and set it on the account urls and set the enableviewstatemac="false"

[mho]

Okay. We are experiencing that when we redirect the relayed response to a page at our server, what happens is that the Authorize.net server our page but the browser show it under the Authorize.net url: https://test.authorize.net/gateway/transact.dll. Can you confirm this behavior?

Yes, this is correct. That why they suggest to do a javascript redirect on your page after it process the post data Authorize.net.

While testing we tried to see if successful orders were registered at https://sandbox.authorize.net/. But while in testmode the transactions were not registered, even though I got a relay with a successful transaction. Is that possibly to get them registered in testmode?

But then when we disabled testmode, orders was registered at https://sandbox.authorize.net/, but the relay gave the same error as in the first post. I find it a bit strange that the same code work so differently of testmode?

Since livemode is what you will use on the production account, there is really no good reason to run testmode on the sandbox account.

In response to those to: Yes but our code works in test mode but not off testmode - but I don't understand that there is a difference in code execution, other than it post to another url.. Which things could be different in this switch?

[RaynorC1emen7]

http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Test-Accounts-vs-Live-A...

From that post. Test Mode basically allows you to validate that the transaction information was submitted correctly, but the info is not passed on for processing.