Support

June 30, 2016 at 10:52 am

That’s a ‘Relay Response Error’ which means Auth.net did not reseieve a response from your site in a timely fashion (10 seconds) when they sent the payment details back to your site.

Is this happening for every transaction made on the site using auth.net?

June 30, 2016 at 11:08 am

Is ‘several a week’ every auth.net transaction made on the site or some of them?

July 1, 2016 at 8:00 am

Theres a few possible reasons for the above error:

1. The x_relay_url value being passed to auth.net is wrong.

EE generates this dynamically for each registration, the way it generates the url is the same for any transaction, so if this was the problem it would prevent all Auth.net payments.

2. The relay response URL is inaccessible.

Again this would cause all of the payments to fail, not some.

3. The SSL certificate you are using is invalid. (Auth.net will drop the connection if i can not validate your certificate)

Again this would cause all payments to fail and we would see this when browsing your site.

4. An error is being thrown on the relay page.

This would prevent the page from loading and responding to Auth.net this could happen intermittently depending on the cause of the error.

5. Server load causing longer page load times.

The page loads fine for some transactions, but not not quick enough for Auth.net on others. This would then trigger the notice for the transactions that take longer but not for the others.

From the above it seems most likely to be #5 which is why I recommended the simplified transactions template above, can you install that template, set the transactions page to use it and see if the problem persists?

Take a look within the servers error log around the time of one of the transactions that failed, any errors from event espresso?

How much memory is available to the site? You can check this within Event Espresso -> Maintenance -> System information.

Search for ‘wp_memory’ and post what that is set to.

Then search for ‘memory_limit’ and post what that is set to.

July 1, 2016 at 8:01 am

Where exactly do I put the template? Just in the theme folder?

Yes, it’s a standard WordPress theme template file.

Place it directly within your theme/child theme.

July 1, 2016 at 8:49 am

That page already had that short code there.

Its nothing to do with the shortcode 🙂

Notice in this screenshot – http://take.ms/Asie3

On the right in the sidebar you can set the ‘Template’ used for the page. Set that to ‘txn page’ as shown.

Then update the page.

The /transactions/ page now uses the ‘txn page’ template.

July 1, 2016 at 8:54 am

Great.

Now https://www.masterpiecemixerslouisville.com/transactions/

Loads nothing but a blank page with the content of the [ESPRESSO_TXN_PAGE] shortcode, meaning it now loads as quickly as it can on your site.

Its fine that the page is bare, your visitor will never be directed to that page by EE and if you are linking users directly to that page you should not be, it is only used for processing IPN’s.

So wait for a little and confirm if auth.net payments now work as expected.

July 5, 2016 at 1:34 pm

Where do I send login? Also see below:

We just got two registrations and only one got this error.

——————————

July 5, 2016 at 8:09 pm

Did you get the login info?

she got another one: Its weird its only her site:

Another one. We’re not getting them every time anymore. But still a lot more than the past.

Sent from my iPhone

On Jul 5, 2016, at 8:45 PM, Authorize.Net <noreply@mail.authorize.net> wrote:
Authorize.Net Merchant,
Your script timed out while we were trying to post transaction results to it.
Transaction ID: 20031207398
Transaction Result: This transaction has been approved.
The following message was displayed to the customer:
——————————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.

July 6, 2016 at 1:57 pm

This is from Auth.net:

had a chat with them. It only took them greater than 14 minutes to pick up the chat…yikes! See below.

Jeff: 15:00
Thank you for holding, Kim. This is a simple Relay Response error. The transactions are still processing and are being approved, it is just taking more than 10 seconds for us to get a response to the credit card.
KimR: 15:01
Is there any way to increase the seconds allowed so that the customer isn’t confused if they are registered or not?
Jeff: 15:01I would have your developer review the following URL:
Jeff: 15:01https://support.authorize.net/authkb/index?page=content&id=A583&actp=search&viewlocale=en_US&searchid=1467831650867
Jeff: 15:02
There isn’t a way through the default settings.
KimR: 15:02
So he will be able to change it by going through this link?
Jeff: 15:03
This link will advise him what he can review in the integration he set up to resolve the error that he is seeing.

July 6, 2016 at 2:34 pm

How do you force it to use the Akamai service? And again it only happens on this site. We have 11 other sites with the same set up, just different Auth.net accounts.

July 7, 2016 at 1:57 pm

AIM is onsite where the credit card form displays on your site. SIM takes the buyer to Authorize.net’s site and captures the credit card information there.

July 7, 2016 at 2:04 pm

AIM tends to work better because the buyer isn’t sent over to another site. They stay right on your site.

AIM is best suited for sites that have SSL and where the site is secured (loads as https instead of http). You’ll only see the SIM option if the SIM add-on is installed. AIM is included in EE4 core.

July 7, 2016 at 2:53 pm

Authorize.net has information about PCI Compliance:

https://www.authorize.net/resources/pcicompliance/