topic Accpet.Authorize.Net Server response delay/errors in Integration and Testing

Accpet.Authorize.Net Server response delay/errors

micduncan — Fri, 04 May 2018 17:36:02 GMT

For years our software has allow our clients the ability to process payments using transact.dll end points. We are aware of the transition to TLS 1.2 exclusive support and have implemented measures to meet these requirements. We have also transitions over to using the Hosted payment forms using the api end points.

We can successfully retrieve tokens and direct end user to these hosted form, however our issue is the delay in response, server responses of intermittent 500/503 errors, or an operation timeout in general from the [controller.execute].

We are currently using the .net SDK 1.9.3

We have implemented the hosted payment form using the iframe/lightbox technique with the communicator.

Is there any performance measure we can take on our end to retrieve a faster, more reliable response from the accept.authorize.net api end points?
Are there more event listeners we can implement in the iframe communicator to get better tracking on payment processing?

How can we eliminate the 500/503 errors and the occasional operation timeouts?

Re: Accpet.Authorize.Net Server response delay/errors

Anurag — Fri, 04 May 2018 22:37:49 GMT

Hi @micduncan

You can use Webhooks for getting realtime notifications for payments done and double check .

http://developer.authorize.net/api/reference/features/webhooks.html

Also we are starting working on our Accept Hosted 2.0 soon where we will removing the iframe communicator and moving to post messages instead .

Thanks

Re: Accpet.Authorize.Net Server response delay/errors

micduncan — Mon, 14 May 2018 12:33:07 GMT

Anurag,

Thanks for the prompt response. Once we transition away from the transact.dll form submissions to the api methods, we implemented a proto-typing of the web notificaitons. Our concern with notificaitons were the entire transaction complete cycle was upwards to 20-30 seconds.
Our test form would submit the payment, see the reciept screen, then return to our outstanding balance page. Unfortunately when the user was return to the screen, the web hook notification had not been pushed to our servers to update the record on our side.

Is this the typical cycle time for Webhooks?

Re: Accpet.Authorize.Net Server response delay/errors

Anurag — Mon, 14 May 2018 17:24:17 GMT

Hi @micduncan

Yes we may see little delay in getting the notifications in some cases .

In your use case i will recoemmended using the transactionID receieved from the Accept Hosted and calling our getTransactionDetails API to retrieve the details

https://developer.authorize.net/api/reference/index.html#transaction-reporting-get-transaction-details

Thanks

Re: Accpet.Authorize.Net Server response delay/errors

micduncan — Tue, 15 May 2018 12:11:39 GMT

Anurag,

Thank you again for your prompt response. Based on the details provided with the transactionDetails api, our team is moving forward with a polling service. Right now our system already records audits of requested transaction with the hosted payment form. When we generate the paymentForm token requests, we are passing in the audit's unique id as the poNumber for the transaction. After which we retrieve a list of unsettled transactions and do a post comparison against poNumber, transaction Amount, and Order InvoiceNumbers.

Earlier you had mention your tam is moving towards Accept Hosted 2.0. How will this affect the current implementation of our current Accept Hosted? Would 2.0 relieve our necessity of polling?

Thank you,

Michael Duncan

Re: Accpet.Authorize.Net Server response delay/errors

Anurag — Wed, 16 May 2018 05:32:51 GMT

Hi @micduncan

Your current integration wont have any impact as Accept Hosted 2.0 changes will be under a new version number .

We will be removing the iframe communicator and using post messages for returning the responses from Accept Hosted .

Thanks

Re: Accpet.Authorize.Net Server response delay/errors

micduncan — Thu, 06 Sep 2018 13:35:34 GMT

Good Morning,

Our Authorize.Net module has just recently started experiencing more 500 server errors. This is happening on several end points such as, getUnsettledTransactions, getSettledTransactionByBatchId, getCustomerProfile, etc.

We are currently using 1.9.3 Sdk and ensuring all network communication is over a TLS 1.2 protocol.

The few lines in our business logic that is returning the 500 errors are shown below.
If controller IsNot Nothing Then
System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12
controller.Execute(If(_testMode, AuthorizeNet.Environment.SANDBOX, AuthorizeNet.Environment.PRODUCTION))
Return controller.GetApiResponse
End If

*the controller object is a reference to the various controllers defined within the sdk depending on the action we are trying to perform.
-getUnsettledTransactionListController

-createTransactionController

-createTransactionRequest

-getHostedPaymentPageController

Is there something we can do on our to further dianosis this issue?

Re: Accpet.Authorize.Net Server response delay/errors

DmitryEvmenov — Thu, 06 Sep 2018 15:05:12 GMT

Good morning! Looks like payments cannot be processed currently, the AuthNet service is returning 200 but the message says "An error occurred during processing. Please try again." when making the "AuthorizeOnly" call, and no other data is in there. Is anyone aware of the issue? It has critical impact on us currently.

Re: Accpet.Authorize.Net Server response delay/errors

RichardH — Thu, 06 Sep 2018 15:08:40 GMT

Hello @DmitryEvmenov

If you are experiencing issues with your live production account, please contact customer support by phone at 877-447-3938.

Richard

Re: Accpet.Authorize.Net Server response delay/errors

jmorrison — Thu, 06 Sep 2018 15:50:09 GMT

@DmitryEvmenov Did you find out any more information? We have been receiving errors as well over the past 48 -72 hours, but we also have successful transactions going through.

Re: Accpet.Authorize.Net Server response delay/errors

DmitryEvmenov — Thu, 06 Sep 2018 15:55:15 GMT

@jmorrison, unfortunately we couldn't sort this out yet. We have not enough info available to call for support just now. I'll post an update if we find out anything.

Re: Accpet.Authorize.Net Server response delay/errors

NickKrivetskiy — Thu, 06 Sep 2018 17:46:33 GMT

Hey

Looks like I was able to determine root of the issue.

For serialization we used classes from Authorize.NET library but for some fields we used inherited classes (e.g. orderExType instead of orderType ). So XML that was sent to Authorize had additional info about type ("xsi:type="orderExType") and server responded back with "E00045: The root node does not reference a valid XML namespace. E00001: An error occurred during processing. Please try again.". Fix was to use base class instead of extended versions and got rid of this additional type definitions in XML.

By the way previous implementation worked perfectly untill today/yesterday.

This endpoint can be usefull to determine the diff between valid and incorrect XML - https://developer.authorize.net/api/reference/index.html

I hope this will help someone else

Re: Accpet.Authorize.Net Server response delay/errors

CharlesDev — Thu, 06 Sep 2018 18:48:56 GMT

Nice work Nick!

This is the issue and changing the following fixed it for me.

transactionRequest.order = new orderExType();

Changed to:

transactionRequest.order = new orderType();

They seemed to have done some kind of change which broke our implementations. Unfortunate that this went without communication so I'm assuming it was a mistake, but for now this will allow us to process payments today.

Re: Accpet.Authorize.Net Server response delay/errors

micduncan — Thu, 06 Sep 2018 20:15:44 GMT

@RichardH - The services appear to be intermittent. The majority are returning proper responses however, we are still experiencing either 500 internal server errors or timeout. Our latest log file shows this failed request.

Stack: System.Net.WebException: The operation has timed out at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags) at Microsoft.VisualBasic.CompilerServices.NewLateBinding.CallMethod(Container BaseReference, String MethodName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, BindingFlags InvocationFlags, Boolean ReportErrors, ResolutionFailure& Failure) at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ObjectLateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn) at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn) at tppBusinessObjs.AuthorizeDotNet.ExecuteController(Object controller) in C:\tppGit\tppweb-gitflow\Projects\tppBusinessObjs\AuthorizeDotNet.vb:line 52 at tppBusinessObjs.AuthorizeDotNet.ValidateCredentials() in C:\tppGit\tppweb-gitflow\Projects\tppBusinessObjs\AuthorizeDotNet.vb:line 65

We can tell from this stack, we are requesting a response to test the validity of the credentials. This is a simple declaration of the authenticateTestRequest object and executed against the authenticateTestController.

Is there any insight you can provide for these occurances? This issue is not isolated to only one particular controller.

Re: Accpet.Authorize.Net Server response delay/errors

RichardH — Thu, 06 Sep 2018 20:20:15 GMT

Hello @micduncan

If you have not already, I would recommend calling support and opening a case with them at 877-447-3938. This insures your issues gets proper follow through. If you provide a case number, I can escalate your case to a support specialist.

If any others on this thread have opened a case, let me know and I can use those as well.

Re: Accpet.Authorize.Net Server response delay/errors

micduncan — Thu, 06 Sep 2018 20:21:27 GMT

Thanks @RichardH

Re: Accpet.Authorize.Net Server response delay/errors

RichardH — Thu, 06 Sep 2018 22:14:30 GMT

This issue now reported on https://status.authorize.net/

Our appologies for the issue, but greatly appreciate everyone's help in troubleshooting and providing information.

Richard

Re: Accpet.Authorize.Net Server response delay/errors

bveertu548356 — Fri, 29 Jan 2021 05:44:20 GMT

yes i also faced this issue and then i took guidabnce from data recovery here you shuold be able to find the best solution about every technical guidance to manage any software or website.

Re: Accpet.Authorize.Net Server response delay/errors

dorrymine678 — Thu, 18 Feb 2021 10:59:37 GMT

yes i also faced the same error in my replay page can someone guide me about it that how i will be able to solve this issue bcz i am suffering from it from many months plz guide if you know about it.