|
swinkelmann
|
November 6, 2018 at 3:00 pm
I am having issues with a couple of users that are getting an error that states “error: Unable to tokenize the card”
I was able to process one of the users cards at my location, but at the users location they received this error.
Event Espresso – Version 4.9.68.p
QuickBooks Payments Gateway – Version 1.0.10.p
|
|
Josh
|
November 6, 2018 at 3:22 pm
Hi,
You can go to Event Espresso > Payment Methods > Logs, which will have several log entries for each transaction. If you know the transaction ID of the transaction that got the error, then you can look at each of the log entries for the transaction and one of them may have a more specific error message.
Since you mentioned they couldn’t complete the transaction at their location, you could also ask them to get & share their browser details from
https://supportdetails.com as this may be related to an incompatible browser.
|
|
swinkelmann
|
November 6, 2018 at 5:39 pm
Something I found along the way is I tried another transaction from from my location logged in as the user and I received the same error, but I did not receive the error when I was logged in as myself. I will look through the log and see what I can come up with.
|
|
Josh
|
November 6, 2018 at 7:38 pm
That’s a good find, and it may be the difference between the access levels of the accounts. Were you logged in with an administrator account when there were no errors? I wonder if there’s a security plugin/setting that’s not allowing the communication with Quickbooks unless the user is logged in as admin. Do you have any security plugins or security related code snippets activated on the website?
|
|
swinkelmann
|
November 7, 2018 at 6:57 am
Correct. No errors logged in as admin. This is just happening with a few users. There are a lot of users with the same role as this user and there is not an issue. Looking at the logs in the payment methods section the ones that are giving us the error look like this:
ID 105
Payment Method Unknown
Transaction 4700
Content
JS Error (Transaction: 4700) error : Unable to tokenize the card
For some reason it doesn’t even pick up the the fact that it using Quickbooks as the payment method.
as far as the plugins. Here is the active list:
AH Display Widgets by Andreas Hecht.
Akeeba Backup for WordPress by Akeeba Ltd.
Capability Manager Enhanced by Jordi Canals, Kevin Behrens.
Connections Business Directory by Steven A. Zahm.
Connections cMap – Template by Steven A. Zahm.
Connections CSV by Steven A. Zahm.
Connections Widgets by Steven A. Zahm.
Disable Comments by Samir Shah.
Document Gallery by Dan Rossiter.
Easy FancyBox by RavanH.
ee4-customizations by .
Event Espresso by Event Espresso.
Event Espresso – Calendar (EE 4.3+) by Event Espresso.
Event Espresso – MER – Multi Event Registration (EE 4.7.0+) by Event Espresso.
Event Espresso – QuickBooks Payments Gateway (EE 4.8.29+) by Event Espresso.
Event Espresso – WP Users (EE4.6+) by Event Espresso.
Gantry 5 Framework by RocketTheme, LLC.
Gravity Forms by rocketgenius.
Import users from CSV with meta by codection.
jQuery Updater by Ramoonus.
MetaSlider by Team Updraft.
Mobile Redirect by Ozette Plugins.
Pages In Widgets by Jayden Major.
RokCommon Library by RocketTheme, LLC.
RokSprocket by RocketTheme, LLC.
Role Includer by Justin Fletcher.
Rotating Tweets (Twitter widget & shortcode) by Martin Tod.
Sliding Widgets by codename065.
Team Members by WP Darko.
Ultimate FAQ by Etoile Web Design.
Ultimate Member by Ultimate Member.
WordPress Force HTTPS by A. Kai Armstrong.
WP Last Login by Konstantin Obenland.
There are a few that can be removed, but these are the current active plugnins.
|
|
Josh
|
November 7, 2018 at 7:09 am
I checked the site and I do see a JavaScript error in the console, and it points to a part of the page source where it appears some PHP code is mixed in with some JavaScript. Can you fix/remove the errant code? Here’s a screenshot that outlines the area of the errant code in the source:
https://slack-files.com/T02SY781D-FDX47MW80-69ecdca22a
|
|
swinkelmann
|
November 7, 2018 at 8:11 am
I removed the code. I will test and get back to you!
|
