Posted: December 13, 2017 at 3:47 pm
|
Hello. I realized after testing 1.0a in sandbox, and it working and then going to production and it not working, that QB now only supports oauth 2.0. Maybe I’m completely missing it, but there is no client ID or client secret on the keys page of the Intuit developer site, just the usual consumer key and consumer secret. If I just switch to oauth 2.0, leaving the existing 1.0a info in the WP plugin, save and connect I get a, “We’re sorry! We’re experiencing some problems. Please try again later.” ANy help would be appreciated. Thanks |
Hi db2112, You might need to create a new app within your Intuit developer account. Apps that use oAuth 1.0 will have OAuth Consumer Key and OAuth Consumer Secret fields. Apps that use oAuth 2.0 will have Client ID and Client Secret fields. Also important: when you set up your oAuth 2.0 app, just a bit after the Client ID and Client Secret fields, you’ll see a section for setting Redirect URIs. There you’ll add a URL and copy and paste your website URL into the Redirect URI field. Production URIs must use https. |
|
|
Thanks for the info. That’s where I’m having the issue. I have created several new apps and none of them ask if this is a 1.0a or 2.0 app. The info bar on the developer site says “This app integrates with OAuth 1.0a and OpenID 2.0” but there is no 2.0 settings that I can find. Maybe intuit does not support at the moment? On the same info bar it states, “We are actively working on a migration path for you to implement OAuth 2.0 and OpenID Connect and will notify you when it is available.” Here is what I do under dev: |
You should be able to use oAuth 1.0 then, and if Quickbooks is no longer allowing production use of oAuth 1.0, then you can contact them to upgrade your account. |
|
|
I read this thread, and it looks like he was able to get it working with 2.0 |
Hi there, First, can I ask where you’ve seen this:
What makes you believe QuickBooks will only work with oAuth 2.0? As far as I am aware, they use oAuth 2.0 for new accounts but existing accounts can continue to use oAuth1.0 without a problem.
That user has an account that uses oAuth2.0 so he must use that setup. One problem with Quickbooks is they changed their integration and it depends on when you created your account which type you will have (annoying but that’s the way it goes) If this is a new account you’ll be using oAuth 2.0 and when looking within your intuit account and grabbing the key info it will look like this – http://take.ms/JvMLK If your keys section looks like that then you select oAuth 2.0 in the quickbooks payment method and input the keys in their relevant sections – http://take.ms/GaikJ — If you have an older account your keys in intuit look like this – http://take.ms/uaOxW If so you select oAuth 1.0a in the Quickbooks payment method and input the details were needed – http://take.ms/tEUIr So, which account type do you have? From this:
It sounds like your account is oAuth1.0 so you would use that in the payment method settings but can you confirm, please? Also, when ‘going to production’ as you switching out your keys for the ‘Production keys’ in your intuit account, or just disabling debug mode in the payment method? |
|
|
Hey Tony, To answer your first question, the payment failure message I received was after I added the oauth 1.0a production keys and turned off debug. I tried to process a 1.00 transaction event this morning againand received the following message. http://take.ms/EeUId After looking at the logs, it looks like there is a token issue. The one the system is using is not the one associated with the production key. http://take.ms/AiQt10 That token does not match the QB app token. Based on those screen shots above, I have the old account. http://take.ms/rFBVE I did swap out the dev keys for production keys as well. Thanks for the help. |
Did you disconnect the app from your website side before removing the sandbox keys? It sounds like the sandbox app is still connected to your website. |
|
|
I don’t recall exactly. It’s possible. Is there any way to update with the new/correct token assuming that is the issue? None of the QB apps have that specific app token, however. |
You can try reconnecting with the sandbox API keys, then disconnect, then after you disconnect switch the settings to use production keys + turn off debug mode. |
|
|
I created a new dev app and tried it again and now I am receiving the following message |
|
I tried what you mentioned by adding sandbox keys saving then disconnecting and adding dev keys + debug off and I am receiving the same issue but it’s a different token this time |
Can you open a support ticket with Intuit and include the error code from that screenshot? They’ve had that same error reported before and it was resolved, but the support topic did not explain how they resolved it: |
|
|
That is no longer an issue it seems. I’m back to the token issue per last screen shot. http://take.ms/Z59n5 |
PMT-6000 is a QuickBooks system error. Have you contacted Intuit about the error? |
|
|
Would this be a QB issue? |
|
Is this still a QB issue? |
|
This issue references sandbox mode but I’m using production |
|
They are no help so far and referenced this article: https://help.developer.intuit.com/s/question/0D5G000004Dk6sBKAR/i-am-receiving-a-400-bad-requestcodepmt6000typesystemerror-when-i-try-to-createfromtoken-could-someone-help |
|
test |
|
I contacted QB and they referenced their forums. |
|
I can’t seem to post urls. In any case, QG referenced me to their forum. However, the issues I’ve found related to PMT-6000 are sandbox issues. |
Those are Quickbooks systems errors. If their support techs can only give you links to unresolved support topics maybe it will help to escalate the ticket on their end. |
|
The support post ‘Quickbooks Payment Gateway and oAuth 2.0’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.