topic Re: CIM SOAP API returning a 550 error on sandbox and production in Integration and Testing

CIM SOAP API returning a 550 error on sandbox and production

jaearess — Wed, 18 Apr 2018 23:15:14 GMT

We're currently experiencing a complete failure of the SOAP API, which we use to create CIM profiles using the authorizesauce Python library.

It was working as of 10:45 a.m. central time this morning (April 18th.) It suddenly started failing at some point afterwards. Both our production and sandbox accounts simply return a 550 error with no other information when we attempt to create a CIM profile. We are able to, e.g., charge existing profiles, however.

Is there an issue with the SOAP API currently?

Re: CIM SOAP API returning a 550 error on sandbox and production

RichardH — Thu, 19 Apr 2018 01:40:37 GMT

Hello @jaearess

I've escalated your report. You should also contact customer support and open a case with them as well.

Richard

Re: CIM SOAP API returning a 550 error on sandbox and production

jaearess — Thu, 19 Apr 2018 01:42:57 GMT

Thank you. We have contacted support already.

Re: CIM SOAP API returning a 550 error on sandbox and production

Kent — Thu, 19 Apr 2018 02:40:54 GMT

We're experiencing the same with both AuthorizeSauce and our ERP system which also uses the SOAP API.

Re: CIM SOAP API returning a 550 error on sandbox and production

bilderbach — Thu, 19 Apr 2018 05:34:42 GMT

same for us using soap!

Thanks for this post, been chasing this down all day!

Re: CIM SOAP API returning a 550 error on sandbox and production

Anurag — Thu, 19 Apr 2018 05:43:08 GMT

Hi All,

Can you provide more details on the errors being receieved ?

If you have any error logs or error messages please provide in the post along with if you are using any SDKs or direct integration with SOAP .

Thanks

Re: CIM SOAP API returning a 550 error on sandbox and production

jaearess — Thu, 19 Apr 2018 05:54:47 GMT

The only error message we receive is "Unknown" when using the sandbox. In production, there's no error message at all. In both cases, the error code is 550.

We're using the authorizesauce Python library, which uses the Suds SOAP client Python library internally.

Re: CIM SOAP API returning a 550 error on sandbox and production

jaearess — Thu, 19 Apr 2018 05:57:39 GMT

As additional information, there's been an issue opened on the authorizesauce Github: https://github.com/drewisme/authorizesauce/issues/48

That includes code that reproduces the error.

Re: CIM SOAP API returning a 550 error on sandbox and production

Anurag — Thu, 19 Apr 2018 06:04:49 GMT

Is this issue only reported via the authorizesauce integration ? or have we seen this through other integrations also ?

Also I am seeing this repo hasnt been updated from May , 2016 .

Our internal tests with SOAP dont seem to be showing any issues .

I will suggest to use our Authorize.Net SDKs if possible going forward .

https://github.com/AuthorizeNet/sdk-python

https://github.com/AuthorizeNet/sample-code-python

Re: CIM SOAP API returning a 550 error on sandbox and production

bilderbach — Thu, 19 Apr 2018 06:06:18 GMT

Only using in production.

Can see 2 payments went through this morning around 6am pst and nothing since, all are failing as soon as it tries to manage profile.

PaymentProcessingProfileMaintenence Failed [Exception Occured, The request failed with HTTP status 550; .]

Talked to support twice today and said no issues reported...just submitted case and referenced this thread.

Case Number: 05001634

Thanks!

-R

Re: CIM SOAP API returning a 550 error on sandbox and production

Anurag — Thu, 19 Apr 2018 06:14:00 GMT

Hi @bilderbach

Are you also using authorizesauce for integration ?

Thanks

Re: CIM SOAP API returning a 550 error on sandbox and production

matto3 — Thu, 19 Apr 2018 06:16:08 GMT

We are also seeing this problem, and we are also using the authorizesauce library.

Interestingly enough not seeing this on our staging environment pointing to the Authorize.net sandbox - only seems to happen in the production environment.

Re: CIM SOAP API returning a 550 error on sandbox and production

jaearess — Thu, 19 Apr 2018 06:33:07 GMT

authorizesauce was working as late as 10:45 a.m. central on April 18th. Whatever the issue is, it is not with the library, but with a change made on your side.

Re: CIM SOAP API returning a 550 error on sandbox and production

drewisme — Thu, 19 Apr 2018 06:55:26 GMT

Here is the request and response for calling 'CreateCustomerProfile' in sanbox at 'https://api.authorize.net/soap/v1/CreateCustomerProfile'.

Request

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://api.authorize.net/soap/v1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Header/>
   <ns0:Body>
      <ns1:CreateCustomerProfile>
         <ns1:merchantAuthentication>
            <ns1:name>XXX</ns1:name>
            <ns1:transactionKey>XXX</ns1:transactionKey>
         </ns1:merchantAuthentication>
         <ns1:profile>
            <ns1:merchantCustomerId>ddbdeee855d948398353</ns1:merchantCustomerId>
            <ns1:email>joe@test.com</ns1:email>
            <ns1:paymentProfiles>
               <ns1:CustomerPaymentProfileType>
                  <ns1:customerType>individual</ns1:customerType>
                  <ns1:billTo>
                     <ns1:firstName>Joe</ns1:firstName>
                     <ns1:lastName>Blow</ns1:lastName>
                     <ns1:address>1234 Street</ns1:address>
                     <ns1:city>Irvine</ns1:city>
                     <ns1:state>CA</ns1:state>
                     <ns1:country>US</ns1:country>
                  </ns1:billTo>
                  <ns1:payment>
                     <ns1:creditCard>
                        <ns1:cardNumber>4111111111111111</ns1:cardNumber>
                        <ns1:expirationDate>2018-11</ns1:expirationDate>
                        <ns1:cardCode>911</ns1:cardCode>
                     </ns1:creditCard>
                  </ns1:payment>
               </ns1:CustomerPaymentProfileType>
            </ns1:paymentProfiles>
            <ns1:profileType/>
         </ns1:profile>
         <ns1:validationMode>none</ns1:validationMode>
      </ns1:CreateCustomerProfile>
   </ns0:Body>
</SOAP-ENV:Envelope>

Response

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://api.authorize.net/soap/v1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><ns0:Body><ns1:CreateCustomerProfile><ns1:merchantAuthentication><ns1:name>6V46Shu5J</ns1:name><ns1:transactionKey>682G5yFJyc485uJF</ns1:transactionKey></ns1:merchantAuthentication><ns1:profile><ns1:merchantCustomerId>ddbdeee855d948398353</ns1:merchantCustomerId><ns1:email>drewisme@gmail.com</ns1:email><ns1:paymentProfiles><ns1:CustomerPaymentProfileType><ns1:customerType>individual</ns1:customerType><ns1:billTo><ns1:firstName>Joe</ns1:firstName><ns1:lastName>Blow</ns1:lastName><ns1:address>1234 Street</ns1:address><ns1:city>Irvine</ns1:city><ns1:state>CA</ns1:state><ns1:country>US</ns1:country></ns1:billTo><ns1:payment><ns1:creditCard><ns1:cardNumber>4111111111111111</ns1:cardNumber><ns1:expirationDate>2018-11</ns1:expirationDate><ns1:cardCode>911</ns1:cardCode></ns1:creditCard></ns1:payment></ns1:CustomerPaymentProfileType></ns1:paymentProfiles><ns1:profileType/></ns1:profile><ns1:validationMode>none</ns1:validationMode></ns1:CreateCustomerProfile></ns0:Body></SOAP-ENV:Envelope>
HTTP failed - 550 - Unknown:

Re: CIM SOAP API returning a 550 error on sandbox and production

raviteja333 — Thu, 19 Apr 2018 12:02:01 GMT

Hi,

Is this issue resolved completely? We are facing the same problem when tried to use the function UpdateCustomerProfile.

https://api.authorize.net/soap/v1/UpdateCustomerProfile

Thank you.

Re: CIM SOAP API returning a 550 error on sandbox and production

caleb — Thu, 19 Apr 2018 13:39:02 GMT

@drewisme You forgot to redact your credentials in the response. The whole request XML structure is on the first line.

Re: CIM SOAP API returning a 550 error on sandbox and production

qilucas — Thu, 19 Apr 2018 15:37:25 GMT

The issues are still present. The SOAP API is returning a HTTP 550 Unknown response for valid and previously working requests.

The issue is not library dependent. You can make the request and see the response using the information posted by drewisme.

This has happened before and is likely the same IIS misconfiguration that was eventually resolved by authorize.net (https://community.developer.authorize.net/t5/Integration-and-Testing/Sandbox-Accept-js-seems-to-be-down/td-p/55935).

This is a critical issue that needs more attention. While the SOAP API is depracted this is effectively a sudden end of life of a mission critical service.

Re: CIM SOAP API returning a 550 error on sandbox and production

bilderbach — Thu, 19 Apr 2018 15:54:32 GMT

same here, call center is down behind this!

Re: CIM SOAP API returning a 550 error on sandbox and production

matto3 — Thu, 19 Apr 2018 16:13:42 GMT

Other departments in our organization are also having this issue, they use the SOAP API as well but do not use AuthorizeSauce (or even Python for that matter) so second the notion that this is more widespread than the original response of "don't use that library". There was clearly a breaking change introduced on the Authorize.NET SOAP API side.

It would be nice (at the very least) to get an official acknowledgement of an issue from Authorize.NET. My direct support ticket has been sent to "development" but has been generally unhelpful, especially considering our production system is down due to this.

Re: CIM SOAP API returning a 550 error on sandbox and production

Kent — Thu, 19 Apr 2018 17:40:17 GMT

Would everyone please share their case numbers? Our case has yet to be reviewed by an enginner (since 10PM EST last evening) and I'm attempting to compel support to further escalate the matter.

05001577