|
asisnyc
|
July 28, 2018 at 3:08 pm
We just are completing the migration from EE3 to EE4 with one prominent reason being the need to move to Authorize.net Accept as SIM was no longer supported. We purchased the “Everything” license to get Accept as well as other needed features. We configured Accept correctly and were able to take ticket sale payments successfully. The other day Accept is no longer in our payment options, it diapered magically causing us to halt ticket sales.
What happened to Accept?
Rich
|
|
Josh
|
July 28, 2018 at 3:11 pm
Hi Rich,
If you go to your site’s WP > Plugins page, is the EE4 Accept add-on installed & activated there? It may have been deactivated, in which case you’ll need to reactivated. If you cannot find it there, you can download a fresh copy from your account page.
|
|
asisnyc
|
July 28, 2018 at 4:12 pm
Hi Josh,
Thanks I previously decided to look in the plugins and found Accept to be deactivated. I am not sure why but I did activate it again and found the original transaction key in the configuration so I went ahead to testing payments. Now Authorize.net is a payment option and I do get to the Accept insert to enter payment information. I have reached a new problem now where I get an error “Finger print value is not valid” I checked the payment information and all is correct. Mu merchant account indicates that the payment was declined. Any idea on how to resolve this?
|
|
asisnyc
|
July 28, 2018 at 4:24 pm
Hi Josh,
I did further testing and updated the Authorize.net transaction ID which corrected the problem.
Rich
|
|
Tony
|
July 30, 2018 at 3:03 am
Hi Rich,
Just for future readers ‘Finger print value is not valid’ is usually either incorrect credentials, or trying to use sandbox credentials in live mode (or vise versa) so double check the credentials and if using a sandbox account the payment method should be in debug mode, if a live account it should not be in debug mode.
Anyway, I’m glad you found the cause, if you run into any further problems please let us know.
|
