- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Authorize.net not posting back to response URL -Timed Out
Can somebody give me an idea what could be the problem?
We are using Opencart3.0 and Authorize.net SIM. Everything was working fine including response URL back to our site till March 24, 2018. Suddenly all the transactions went into "Missing Orders" starting March 25, 2018.
We get the following error:
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.
We were able to make successful transactions through following method:
1. Setting "x_relay_response" to "false" in opencart redirected to default receipt URL of authorize.net and by clicking on a button it redirects successfully to the merchant site.
2. Forcing the site to run under "http" and setting the "x_relay_repose" to "true" and configuring "http" callback url in authorize.net works fine. The response reaches the merchant site.
Problem:
We were not able to get the response from authorize.net and it times out when we use "x_relay_response" to "true" and when running under "https" and configuring "https" callback url in authorize.net "response url".
Please help!
โ04-09-2018 01:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You need to implement TLS 1.2 and disable older types of SSL. That will fix your problem
โ04-10-2018 08:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. I will try and get back.
โ04-12-2018 03:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you got this working by updating TLS? Because it was working fine at our end till March 24,2018.
Did authorize.net make some changes?
โ04-12-2018 05:21 AM - edited โ04-12-2018 05:23 AM

