|
venvinoartstudios
|
September 12, 2017 at 10:52 pm
Hi, I carefully followed all instructions from your EE4 Doc: “QuickBooks Payment Gateway” (https://eventespresso.com/wiki/quickbooks-payment-gateway/) and I had the following problems:
1. The document describes labels and screens that have changed on the Intuit Developer website, so it was difficult to find a match to the steps described and I was unsure if I was doing it correctly.
2. No matter what I try to do I keep getting this error message on the EE payment method settings screen for QuickBooks: “NOT CONNECTED TO QUICKBOOKS ! This payment method requires an Authentication.” I have searched this forum and found two other recent instances, but no resolution publicly available. I never see the authentication pop-up described. Instead I only see a quick gear icon animation and the same error message appears when I click on the green connect button. I have tried whitelisting pop-ups in Chrome, removing all pop-up restrictions in Chrome, disabling and re-enabling the payment method among several troubleshooting steps. Help!
|
|
Tony
|
September 13, 2017 at 5:46 am
Hi there,
Can I take a quick look at this on the site?
I’ll need WP Admin credentials and FTP access to the site to do some debugging, if that’s ok you can send those details using this form:
https://eventespresso.com/send-login-details/
|
|
Josh
|
September 13, 2017 at 7:44 am
Hi,
In addition to the above, can you log into your Intuit account and check the Keys page to see which type of API keys your app has. If the app has oAuth 1.0 keys, your app will include an App Token and the page will look like this:
https://www.evernote.com/shard/s4/sh/d4d377a4-e0bd-4d74-b954-3c93616b5a10/7df6c854a02f6f21
If it’s a newer app that has oAuth2.0 keys then the App Token field will be omitted.
|
|
venvinoartstudios
|
September 13, 2017 at 11:42 am
Hi,
Tony, I submitted the login details. Josh, it’s a newer app (created yesterday) which has oAuth 2.0 and no app token field appears.
|
|
venvinoartstudios
|
September 13, 2017 at 11:48 am
More info: I have EE payment method set to debug mode and trying to connect to an Intuit-provided sandbox company account.
|
|
Josh
|
September 13, 2017 at 12:12 pm
OK the current version of the Quickbooks gateway can only connect with oAuth1.0. A developer is working on adding support for oAuth2 and we will let you know when that is ready.
|
|
venvinoartstudios
|
September 13, 2017 at 12:26 pm
Ok, can you confirm it is not possible to integrate EE with Quickbooks at this time? Is there any way to get the old method (oAuth1.0) set up with Intuit?
|
|
Josh
|
September 13, 2017 at 12:30 pm
It is possible but it currently only works with oAuth1.0. Apps that were created before August 2017 should have oAuth1.0. Later apps have oAuth2.
|
|
venvinoartstudios
|
September 13, 2017 at 12:44 pm
It seems like a long shot to petition Intuit to downgrade us, but I will try that. Do you have a timeline on your side for oAuth 2.0? Do you know of any similar challenges with Auth.net? We have to make some decisions on launching our website.
We purchased QuickBooks services with the assurance it would work with your plugin, so it’s a hardship now for us to switch to Auth.net. Do you plan to resolve this quickly or communicate this to your user base so they don’t wander into the same challenge we have?
|
|
Josh
|
September 13, 2017 at 1:44 pm
Do you know of any similar challenges with Auth.net?
No.
Do you plan to resolve this quickly or communicate this to your user base so they don’t wander into the same challenge we have?
I mentioned this before, there’s a developer that’s working on adding support for oAuth2.0. Part of the challenge is we cannot drop oAuth1.0 in the process because the current user base is using oAuth1.0 and they haven’t migrated to oAuth2.0 yet.
|
|
venvinoartstudios
|
September 13, 2017 at 2:50 pm
Josh, thanks for the responses as it helps us plan our next steps. I get all the complexities of keeping up with changes made by a larger 3rd party as I work in a similar industry, so I understand. It may be helpful for other users moving forward to get this info from an updated integration doc, so you may want to pass that along to the powers that be. Thanks again.
|
|
Josh
|
September 14, 2017 at 7:12 am
We’ll let you know when there’s an oAuth2.0 integration that’s ready for testing.
|
