The Authorize.Net Developer Blog

Posts from Authorize.Net employees, community members and experts about integrating with the Authorize.Net Payment Gateway: sample code, tutorials, and problem-solving techniques, just to name a few.

SOAP API Deprecation and EOL Date for Hosted CIM

by Administrator Administrator ‎11-04-2016 09:00 AM - edited ‎11-08-2016 10:33 AM (39,057 Views)

Today we are announcing the deprecation of our SOAP API and providing an end-of-life notice for Hosted CIM (Customer Information Manager). Our SOAP API offered support primarily for Customer Information Manager.


The Authorize.Net API includes all of the SOAP API functionality plus additional features such as Authorize.Net Accept, creating one-time transactions and enhanced Customer Profile methods. This will allow us to continue providing you with the most up-to-date features and to support a single, consistent platform. We strongly recommend moving to the Authorize.Net API using XML or JSON. An end of life date for SOAP will be announced later.


Hosted CIM, which has been replaced by Accept Customer, will reach end-of-life on March 1, 2018. Requests sent for Hosted CIM after that date will return an HTTP Error 410.





by dtobey
on ‎11-10-2017 07:03 AM

Is the EOL date for Hosted CIM of March 1, 2018 still accurate?


And, has an EOL date for SOAP been set yet?



by cemllyrios
on ‎01-07-2019 01:38 AM

The EMV chip automatically detects the user which transmits a customer’s chip information from the EMV chip card reader to Authorize.Net. DNS Server Not Responding