https://community.developer.cybersource.com/t5/Integration-and-Testing/Problem-with-AIM-processing-after-moving-to-new-hosting-site/m-p/86986#M54739 <P>Thanks for the very helpful suggestions, Darrell.&nbsp; In our trouble-shooting, we performed the steps you listed.&nbsp; The thing that baffled me was that there were no entries for the declined transactions in Auth.net.&nbsp; I presented that information to the Auth.net support folks and was told that there will not be transaction entries for declined transactions.&nbsp; I knew from the response our new site was getting from Auth.net that it was indeed communicating with them.</P><P>As it turned out, even though all of the exposed configuration options were identical for the new and old website, the sites were handling encryption of the credit card differently.&nbsp; Once I determined that was happening, I was able to solve the problem by changing a setting in the new site.&nbsp; So things are working now, even though the new and old sites have this one different setting.</P><P>Bottom line, it was not a problem with Auth.net.</P><P>Again, many thanks for the reply.</P><P>Ben</P> Wed, 12 Jul 2023 14:22:03 GMT BenTriangle 2023-07-12T14:22:03Z https://community.developer.cybersource.com/t5/Integration-and-Testing/Problem-with-AIM-processing-after-moving-to-new-hosting-site/m-p/86908#M54698 <P>Our AIM processing has worked fine on our previous hosting site.&nbsp; This week we moved it to a new hosting site, and all of our transactions are coming back with the response pasted below:</P><P class="lia-align-center">3,1,6,The credit card number is invalid.,,[I removed the remaining info from the response]</P><P>The CC for this testing works correctly on the old site, but not the new host.&nbsp; And we switched back to the old site to verify that it still works correctly - it does.</P><P>Oddly, the rejected transactions do not appear in the Authorize.net Unsettled Transactions.</P><P>I'm aware that AIM is now "deprecated", and I asked auth net support if moving the site would trigger something at Auth.net to disable AIM support for our site.&nbsp; They were not helpful and suggested this community is where I should look for answers.&nbsp;</P><P>Any insight from you would be much appreciated.</P> Wed, 28 Jun 2023 18:21:05 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/Problem-with-AIM-processing-after-moving-to-new-hosting-site/m-p/86908#M54698 BenTriangle 2023-06-28T18:21:05Z https://community.developer.cybersource.com/t5/Integration-and-Testing/Problem-with-AIM-processing-after-moving-to-new-hosting-site/m-p/86986#M54739 <P>Thanks for the very helpful suggestions, Darrell.&nbsp; In our trouble-shooting, we performed the steps you listed.&nbsp; The thing that baffled me was that there were no entries for the declined transactions in Auth.net.&nbsp; I presented that information to the Auth.net support folks and was told that there will not be transaction entries for declined transactions.&nbsp; I knew from the response our new site was getting from Auth.net that it was indeed communicating with them.</P><P>As it turned out, even though all of the exposed configuration options were identical for the new and old website, the sites were handling encryption of the credit card differently.&nbsp; Once I determined that was happening, I was able to solve the problem by changing a setting in the new site.&nbsp; So things are working now, even though the new and old sites have this one different setting.</P><P>Bottom line, it was not a problem with Auth.net.</P><P>Again, many thanks for the reply.</P><P>Ben</P> Wed, 12 Jul 2023 14:22:03 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/Problem-with-AIM-processing-after-moving-to-new-hosting-site/m-p/86986#M54739 BenTriangle 2023-07-12T14:22:03Z