|
WebmasterPTC
|
December 18, 2018 at 1:07 am
For filling out the PCI DSS questionnaire, I would like to know how EE3’s Authorize.net AIM plugin works.
I am familiar with WooCommerce. WC lets me configure CC processing with ‘accept.js’ using an “public client key” for the Authorize.net AIM API. This avoids that my site gets exposed to the buyers’ card information. Does EE’s Authorize.net plugin do something like accept.js for Woo Commerce ? It would benefit me in the PCI DSS questionnaire.
Thanks,
Rainer.
|
|
Josh
|
December 18, 2018 at 7:05 am
Hi,
The EE3 Authorize.net AIM gateway does not have the Accept.js option. What you can do is upgrade to Event Espresso 4, which allows for using the Authorize.net Accept gateway.
|
|
Tony
|
December 18, 2018 at 7:08 am
Hi there,
I am familiar with WooCommerce. WC lets me configure CC processing with ‘accept.js’ using an “public client key” for the Authorize.net AIM API.
It’s actually not for the ‘AIM API’, it’s using the Authorize.net API integration using Accept.js, I’m not trying to be nit-picky, but point being SIM, AIM (and other Auth.net integration methods) have now be deprecated in favour of the Auth.net API.
Does EE’s Authorize.net plugin do something like accept.js for Woo Commerce ?
EE4 yes (using the Auth.net Accept payment method), EE3 no.
AIM has been deprecated by Auth.net but it currently still works, EE3 uses the AIM integration method (NVP method, see https://developer.authorize.net/api/upgrade_guide/#aim) and does not use the Auth.net API or Accept.js so you’ll need SAQ-D to be compliant when using AIM.
EE3 is no longer under active development other than security fixes, we focus all of our development time on EE4 (which has an Auth.net Accept integration) so as it stands we do not have plans to release Auth.net Accept integration for EE3.
|
