https://community.developer.cybersource.com/t5/Integration-and-Testing/Using-CIM-with-old-AIM-key-value-pairs-API/m-p/52024#M27323 <P>Hello&nbsp;<a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/18802">@unitedu</a></P> <P>&nbsp;</P> <P>Yes, you will need to add support for XML to take advantage of new Authorize.Net API features. &nbsp;NVP is now deprecated but still supported for existing functionality.</P> <P>&nbsp;</P> <P>Richard</P> Fri, 04 Sep 2015 00:19:45 GMT RichardH 2015-09-04T00:19:45Z https://community.developer.cybersource.com/t5/Integration-and-Testing/Using-CIM-with-old-AIM-key-value-pairs-API/m-p/52021#M27320 <P>We've been using the AIM key/value pairs API for several years, and we want to start using CIM. I see that profiles can be created automatically when an AIM transaction goes through, and that the payment profile ID can be used in place of payment information for AIM, but I only see that documented for the XML version of AIM. Can I also do these things with the old key/value pairs method, or am I going to have to convert all my code to XML?</P> Thu, 03 Sep 2015 21:53:01 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/Using-CIM-with-old-AIM-key-value-pairs-API/m-p/52021#M27320 unitedu 2015-09-03T21:53:01Z https://community.developer.cybersource.com/t5/Integration-and-Testing/Using-CIM-with-old-AIM-key-value-pairs-API/m-p/52024#M27323 <P>Hello&nbsp;<a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/18802">@unitedu</a></P> <P>&nbsp;</P> <P>Yes, you will need to add support for XML to take advantage of new Authorize.Net API features. &nbsp;NVP is now deprecated but still supported for existing functionality.</P> <P>&nbsp;</P> <P>Richard</P> Fri, 04 Sep 2015 00:19:45 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/Using-CIM-with-old-AIM-key-value-pairs-API/m-p/52024#M27323 RichardH 2015-09-04T00:19:45Z