These settings determine the transaction receipting options.
Receipt Page Settings
- Select a Return Link Method:
- AUTO POST
- AUTO GET
- Receipt Link text. This is the hyper-linked text that will display to the customer as the link to return them to the merchant's site. For example, "Return to Mystore".
- Receipt Link URL: this is the URL the customer will click to return to the merchant's website.
- Reference Number Title: if you are using the x_invoice_num value this setting will determine how it is labeled on the Payment Page. For example, "Invoice Number", or "Order ID", etc.
- Customer Reference Title: see Reference Number Title above.
Authorize.Net Protocol - Relay Response Settings
- Allow Relay Response: check this box if Relay Response is the receipting method chosen.
- Relay Response URL: if Relay Response is allowed, this is URL that Hosted Checkout will relay transaction results to AND receive HTML back from.
- Allow HTTP Redirect to the Merchant Website: when this option is selected, any HTTP redirect requests Hosted Checkout receives in the relay response back from the merchant will pass the customer back to the merchant's website - instead of displaying the receipt page on the Hosted Checkout domain.
- Validate Relay Response HTML: this option will allow Hosted Checkout to validate the HTML the merchant's servers relay back for the receipt page.
Authorize.Net Protocol - Silent Post Settings
- Silent Post URL: if Silent Post is desired, this is URL that Hosted Checkout will relay transaction results to. Hosted Checkout will not "listen" for a response back from this URL.
Hit "Next" to proceed to the next step, "Previous" to return to the preceding screen, "Save Changes" to return at a later time or "Cancel" if editing an existing page.
Hi Geoff, what's the difference between Auto-post and REDI? Thanks
AUTO-POST will send the transaction result parameters as an HTTP POST request, while the REDI method will send them as GET parameters. GET parameters will be visible to the user in their browser's URL bar, while POST parameters will not. The REDI method is somewhat deprecated; AUTO-GET actually performs the same task as REDI.
It seems when we redirect back the unsecured website using AUTOPOST that we get a security warning. Is there a way to avoid this. I don't recall seeing this while connecting to PayPal systems so I assume there is something we can do to prevent this security warning. Please help.
Are you seeing this on our live or demo system? Could you let us know what browser is being used when this warning appears?
I implemented this hosted checkout for a client and they are having a problem, were the user closes the browser before the E-xact system sends the user back to the website, so we can't track the sale.
Does the Silent Post option solve this problem?
Yes, the Silent POST feature should address this issue. Since the response gets sent regardless of any action taken by the cardholder, it provides redundancy to ensure that the transaction information is sent back to the merchant's server.
What method should be used when integrating with X-Cart? And what should the Receipt Link URL be for use with X-Cart?
I'm having the same problem described above where I get a security warning (in Firefox and Safari) when I use AUTO-POST to link back to our site. Does your system require SSL to be installed on our server? If not, how do I avoid the security warning?
Hello! I'm new here - what are the differences between these six options?