|
corelearn
|
July 18, 2019 at 6:43 am
Hello! It appears that a shipping address is not being sent to Authorize.net. As a result, due to our Authorize.net settings, credit cards are being verified by held for manual approval. We do not want to change the Authorize.net setting to allow mismatch between shipping and billing addresses to be automatically approved. Is there a way to pass the address information that is collected in Event Espresso to Authorize.net? We are collecting two address fields — Address & Billing Address. Could the first Address field be passed to Authorize.net as the shipping address?
We read this support article but don’t think it completely addressed this issue. https://eventespresso.com/wiki/eea-authorizenet-accept/#setup
Thank you!
Emily
|
|
corelearn
|
July 18, 2019 at 6:58 am
One additional note… In the support article https://eventespresso.com/wiki/eea-authorizenet-accept/#setup, it mentions to fields that do not seem to appear in our payment settings within EE.
Billing address – Enable to collect a registrant’s billing address.
Shipping address – Enable to collect a registrant’s shipping address.
It seems if we had the ability to require those two fields as part of the credit card payment process, that would solve our issue.
Thanks!
|
|
Tony
|
July 18, 2019 at 7:33 am
Hi there,
The docs you are linking to are for the Auth.net Accept Payment method:
https://eventespresso.com/product/eea-authorizenet-accept/
Which you have access to as part of your license, but your site is not using that payment method, your using the Auth.net AIM payment method integration.
I’ll do some checking on this now, however, I recommend you switch away from Auth.net AIM and use Auth.net Accept as they Auth.net have deprecated the AIM integration method in favour of their new API (which the Accept payment method uses) which you can see here:
https://developer.authorize.net/api/upgrade_guide/
AIM is also an on-site payment method which mean you (the site admin) are fully responsible for all PCI compliance and it will require the highest level of compliance (SAQ-D).
Auth.net Accept is an offsite payment method using an iFrame which means Auth.net take care of most of the compliance for you.
You’ll also have the option to display both the billing and shipping address with the Auth.net Accept payment method.
|
|
corelearn
|
July 18, 2019 at 9:49 am
Thank you for the information! Is the switch to Auth.net Accept a change we make with our Authorize.net account? In Event Espresso, the only option I see available is AIM.
Emily
|
|
Josh
|
July 18, 2019 at 9:55 am
Hi Emily,
You’ll actually install the Authnet Accept add-on (it’s a separate plugin that you download from your account page). Here’s a link to its documentation:
https://eventespresso.com/wiki/eea-authorizenet-accept/
|
|
corelearn
|
July 18, 2019 at 12:45 pm
Thank you!!!!! This is such a big help.
Emily
|
|
Tony
|
July 19, 2019 at 9:55 am
Hi Emily,
I just wanted to check-in and confirm that Auth.net Accept worked better for you and everything now works?
|
