All ... I had this issue happen almost a year ago but the problem was on the Authorize side. I opened a ticket with Authorize and they said they would get back to me in 1-2 days. Nothing from them.
Background:
We use SIM ... moving away from that but not yet. We migrated our webserver from a co-location to Azure. Our relay responses immediately started to fail to post. Our TTL was set to 1 week and we believe that was what caused the fails. We setup a new relay URL, new DNS entry, and put it into Authorize. It worked for a day and then failed again. We can't get the new or the old relay URLs to work now. Help!
Users get this when the relay response failes:
The reporting of this transaction to the Merchant has timed out. 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.
Also I am not getting the error email that I should from Authorize. Again, support is no help.
In testing ... the time out on the relay response is supposed to be 10 seconds but it happens in some cases immediately.
Solved! Go to Solution.
โ07-31-2019 08:27 AM
OK ... I believe we found our error:
Authorize.net Relay URL: https://www.site.com/
Our SIM API call was sending https://www.site.com as the Relay URL ... missing trailing '/'
Ugh ...
Open Issues I still have with Authorize:
1. Why am I not receiving e-mail notifications when there are technical errors in credit card processing?
2. We have missed hundreds of relay responses from Authorize. Can we have those resent?
3. We believe we had an issue with DNS propagation initially ... how can we engage Authorize to update their DNS in the future?
โ07-31-2019 10:42 AM
My Support Ticket: 06209074
https://support.authorize.net/s/case/5002I00001sIurVQAS/not-getting-the-relayreceipt-response
โ07-31-2019 08:31 AM
OK ... I believe we found our error:
Authorize.net Relay URL: https://www.site.com/
Our SIM API call was sending https://www.site.com as the Relay URL ... missing trailing '/'
Ugh ...
Open Issues I still have with Authorize:
1. Why am I not receiving e-mail notifications when there are technical errors in credit card processing?
2. We have missed hundreds of relay responses from Authorize. Can we have those resent?
3. We believe we had an issue with DNS propagation initially ... how can we engage Authorize to update their DNS in the future?
โ07-31-2019 10:42 AM
โ07-31-2019 01:13 PM
Great idea for handling the missing responses. We can get a lot of the data from the on-line reporting also.
โ07-31-2019 01:16 PM