Authorize.net CIM Gateway?
Posted: Wed May 07, 2014 12:09 pm
I just downloaded the Gold R7 demo because one of the features was Authorize.net CIM payments. This feature is important to us in order to reduce PCI compliance scope. If the payment data never touches our server and we can get an attestation of compliance from Authorize.net, it greatly reduces the burden of PCI self-assessments.
However, when I look at the source for the Payment form, it appears that the form is a] hosted on our server (as opposed to an iframe), and b] does a javascript postback to our server. I thought the whole point of CIM was that the data never touches your server. How is it any different than AIM with the way it is currently implemented?
However, when I look at the source for the Payment form, it appears that the form is a] hosted on our server (as opposed to an iframe), and b] does a javascript postback to our server. I thought the whole point of CIM was that the data never touches your server. How is it any different than AIM with the way it is currently implemented?