Reply
Member
Posts: 7
Registered: ‎04-19-2016

transactions not working anymore with authorize.net USA (working only with authorize.net UK)

Hello,

 

we are receiving this error message below for all new transactions since yesterday evening.
this is happening on production account (developer account works fine).
this is happening for USA authorize.net account (UK authorize.net account works fine which is using the same scripts).
we have not changed anything on the server or on the authorize.net account settings.
any suggestions?

thank you

 


-----Original Message-----
From: Authorize.Net [mailto:noreply@mail.authorize.net]
Sent: Tuesday, February 28, 2017 8:53 PM
To: XXXXXXXXXXX
Subject: Transaction Error Notification

Authorize.Net Merchant,

Your script timed out while we were trying to post transaction results to
it.
Transaction ID: XXXXXXXXXXX
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.


------------------------------

Posts: 2,765
Topics: 57
Kudos: 248
Blog Posts: 67
Registered: ‎12-05-2011

Re: transactions not working anymore with authorize.net USA (working only with authorize.net UK)

Hello @ST1

 

This error suggests that Authorize.Net is unable to connect to your relay response URL after successfully processing your transaction request.  If it works properly in sandbox but has started failing in production, it would suggest a change with your server preventing us from connecting.

 

Richard

Member
Posts: 7
Registered: ‎04-19-2016

Re: transactions not working anymore with authorize.net USA (working only with authorize.net UK)

thanks for replying Richard,

 

we have not changed anything on the server.

 

the relay response URL seems to work fine when Authorize.net is sending unsuccessful transactions. but the successful transactions never reach our server.

 

the relay response URL is not blocked by our host.

 

furthermore, we are using the same scripts for another Authorize.net account (UK) which works fine. this makes me think that it may be a problem with the Authorize.net account USA only, versus something on our server.

 

the owner account is verifying with authorize.net support those specific transactions ID that are successful but not redirected to our server. I'm not sure what to check next on my side.

ST1

Member
Posts: 2
Registered: ‎03-01-2017

Re: transactions not working anymore with authorize.net USA (working only with authorize.net UK)

Any update on this? I don't have access to our customers' live Authorize.net accounts but we're seeing a similar behavior where there are a LOT of timeouts starting today.

 

My immediate concern is I hope people aren't making duplicate payments by trying again

Member
Posts: 2
Registered: ‎03-01-2017

Re: transactions not working anymore with authorize.net USA (working only with authorize.net UK)

Switching from secure2.authorize.net to secure.authorize.net in our AIM connection (https://secure.authorize.net/gateway/transact.dll) seems to have helped.

 

Something is wrong with the new URL?

Member
Posts: 7
Registered: ‎04-19-2016

Re: transactions not working anymore with authorize.net USA (working only with authorize.net UK)

Hi mgroger,

 

thanks for replying. we have open a ticket with authorize.net support and the problem has been solved. but they did not specify what they may have done.

 

for info and addressing your concern:
- we never used 'secure2.authorize.net', only 'secure.authorize.net'
- we prevent duplicate payment to be posted to authorize.net (preventing double-click)
- we never had any timeout issue, successful transactions were processed right away but not relayed back to us (unsuccessful transaction were properly relayed)

 

we have not changed anything on our side, but it works now.
ST1