Accpet.Authorize.Net Server response delay/errors

[micduncan]

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?

[DmitryEvmenov]

@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.

[NickKrivetskiy]

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

[CharlesDev]

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.

[micduncan]

@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.

[RichardH]

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.

[micduncan]

Thanks @RichardH

[RichardH]

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

[bveertu548356]

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.

[dorrymine678]

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.