TOPIC: [SOLVED] Relay Response returning a TImed-Out error message

We are pretty frustrated with this timed-out error message:

“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.”

Has anyone tested the Accept.js as a work-around that replaces DPM and the relay response through the Authorize.net API.

With correctly setup redirect URLs and such in your account, we know the currently available integration works just fine. However, we're about to release an update with a new Authorize.net plugin that incorporates the new Accept Hosted solution, which replaces the old SIM solution, which is what DT Register currently has integrated.

Will that function in the same way as the SIM payment method to avoid PCI requirements on our part?

Also, Authorize.net states that URLs with query strings are not permitted.

Please configure any scripts for your Relay URL so they do not depend on variables in the URL.

For example, testdomain.com/authorizenet/receipt.aspx is acceptable, but testdomain.com/authorizenet/receipt.aspx ?page=receipt would not be accepted.

Since the relay response URL contains a variable, /components/com_dtregister/success.php?task=restore, it is not accepted and therefore causes the errors.

See:
support.authorize.net/authkb/index?page=...archid=1501854031718

We are aware of the API changes within AUthorize.net. The relay response URL is no longer used with the new Accept Hosted integration. It instead uses a webhook. No variables are used.

The new solution does now require a SSL certificate on your website. Authorize.net has moved to this, even for the Accept Hosted (SIM) solution, as many other payment gateways have been doing.

We're wrapping this up (today hopefully). Get your SSL certificate ready if you don't have it already.

We ran into an issue in the meantime with records not being captured after payment was made and I checked the .htaccess file. It did not match the htaccess.txt file for some reason after the Joomla upgrades. In any event, I replaced the .htaccess file with a clone of the htaccess.txt file and ran another test. This time the records were being saved to the backend. So, it would be a good idea after upgrading Joomla, to make sure the .htaccess file (if being used) matches the text file. The .htaccess is only used if you are using Mod-Rewrite in Joomla Configuration settings.

I also noticed now that the error message still appears, however, it appears AFTER THE FULL 10 SECONDS has transpired. That is a good indication, since it was timing out earlier after only 2 seconds. Not sure still, why this is timing out unless it is that issue with the querry string as mentioned earlier regarding the relay response URL.

... and yes, we most assuredly use an SSL certificate.

The SIM URL has always used a variable with DT Register. With the update, it won't matter though as it's not used.