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