Cybersource Developer Community Cybersource Developer Community

npiasecki · 03-19-2017

CIM is sporadically returning this error since at least 3/18: The content type text/html of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSuppor...

npiasecki · 06-29-2016

We got a bunch of these around 5:30 a.m. Eastern this morning. I missed the maintenance schedule, where was this posted? It's not on the status page.

npiasecki · 01-06-2016

CIM API endpoint down since 8:50 a.m. Eastern ... http://stats.pingdom.com/awg3t4nsnd7a/1283656 ... seems to be taking several minutes to reply to any request ... status update?

npiasecki · 11-05-2015

Hi @RichardH Please escalate ticket 1-216949971. When attempting a linked refund through CIM, either through the API or the Merchant Interface, it fails with E00051 - The original transaction was not issued for this payment profile. I can do it for t...

npiasecki · 11-03-2015

Recently (may have been last night, from what I can tell), Authorize.Net inserted a "customerProfileId" field in the WSDL for the CIM CreateCustomerPaymentProfileResponseType. For older clients using the standard svcutil tool provided by the .NET Fra...

npiasecki · 01-30-2016

For example, in .NET 4.5, TLS 1.2 is enabled by default. Upgrading to .NET 4.5 should provide your solution with support for TLS 1.2. That enables it in the platform, but you still need to interact with System.Net.ServicePointManager.SecurityProtocol...

npiasecki · 01-29-2016

Since we're now on the second outage this week, and one of many since the CyberSource acquisition, is there any actual plan in place at Authorize.Net to improve uptime? The outages happen so often that we added a feature for it. Our e-commerce platfo...

npiasecki · 01-24-2016

I can confirm this as well, appears to be happening sporadically. Happened again just 5 minutes ago as I was running through orders

npiasecki · 01-06-2016

I see the status page updated to say a fix was implemented, but CIM is still replying with (E00104) Server in maintenance

npiasecki · 11-10-2015

Update: Authorize.Net confirmed the issue and that they will deploy a fix on 11/12. However, I would recommend using the workaround posted above in the general case, as this issue has popped up time and again, and this seems to be a permanent fix.

Cybersource Developer Community Cybersource Developer Community

Your latest statistics

User Activity

CIM is sporadically up and down

(E00104) Server in maintenance

Authorize.Net Down

CIM E00051

CIM WSDL Breaking Change on 11/3?

Re: Request for Comments: API Best Practices

Re: CIM down again

Re: CIM down again

Re: Authorize.Net Down

Re: CIM E00051

Re: CIM: Void Captured/Pending Settlement stopped...

Re: CIM E00051

Re: CIM is still down

Re: CIM Outages

Re: CIM Refund E00051