cancel
Showing results for 
Search instead for 
Did you mean: 

sandbox wsdl oce-ex-cert-api nxdomain

I'm doing SOAP authorize.net things in the sandbox environment.

There's a document that tells me how to do that.

There is a (poorly indicated) WSDL specified in that document.

That WSDL specifies a service address: https://oce-ex-cert-api.authorize.net/soap/v1/Service.asmx

 

This has all worked flawlessly since December when I first integrated authorize.net. Yesterday I noticed that I couldn't transact in the sandbox any longer and a DNS error appears in my logs.

 

When I perform a DNS lookup on oce-ex-cert-api.authorize.net I receive an NXDOMAIN error message, which indicates that the domain requested does not exist.

 

I contacted Authorize.net support directly and was informed that this issue is "too detailed" and that I should use these forums to address the issue. I additionally emailed developer@authorize.net yesterday but haven't heard back yet.

 

Any assistance would be greatly appreciated.

kcartmell
Member
21 REPLIES 21

Our solution to this bug is to simply host our own corrected static WSDL file and to configure our tests to use that.  It should work with all libraries and is not hackey.  Once Auth.net gets around to fixing the issue you can just change the URL back to the real WSDL easily.

pegler
Member

The error in the WSDL is now corrected.  

 

Richard

RichardH
Administrator Administrator
Administrator