Posted: December 4, 2017 at 6:54 pm
|
Hello – I’m looking for any EventEspresso client who has successfully connected their Quickbooks Payments to EventEspresso. I’m at a complete loss. I follow the instructions, triple check all settings, and then Intuit tells me my app won’t work in the OAuth2 setting that EventEspresso recommends… I could really use some help. I’m even willing to pay someone to set this up for me. Any help out there? |
Hi there, We can help you set up the Quickbooks payment method. First a quick question for clarification on this:
In your last thread you mentioned you were contacting Intuit for further details, so have support told you the app won’t work or do you mean the error message from your other thread continues to show? We would normally require a support token to troubleshoot directly on your server, however as you’ve been battling with this for a little while now, I’d like to take a quick look over your settings first and confirm they look correct. If that’s ok you can send temporary login details using this form: |
|
Event Espresso doesn’t actually recommend oAuth2 over oAuth1, the gateway makes both options available. So if Intuit tells you that your app won’t work in the oAuth2 setting, then you use the oAuth1 setting. |
|
|
Hi Tony and Josh – I sent Tony my login details via the link above. Thank you for your help with this. Intuit just sent me another piece of advice: “Make sure you are using the Production section in Keys tab to update the redirect_uri for your app. Also make sure you’re using a valid https redirect_uri for production, note that localhost is not allowed as a redirect_uri for production tokens.” Maybe the issue is my redirect uri? The one in production populated after my SSL certificate was activated, so I didn’t want to mess with it. |
That’s good advice, do you have any questions about how to follow that advice? |
|
|
I have ALL of the questions! Tony suggested that he would take a peek at my settings to see if I had set something up incorrectly. So I haven’t touched anything at this point. But I have no idea how to change my redirect uri so some resources would be useful. Thanks |
There’s an add URI button in the Quickbooks Production section Keys tab where you get the API key information from. You add your website’s URL there, and it needs to start with https. |
|
|
Right. I’ve done that but it keeps asking me to use a ‘valid’ redirect. |
|
Here’s a screenshot http://www.treasurevalleychildrenstheater.com/wp-content/uploads/2017/12/Screen-Shot-2017-12-05-at-4.27.59-PM.png |
Hi there, I just checked and we’ve not received any credentials from you, can you resend, please? If you don’t have a redirect_uri setup for your live site then that will be why it is not working and, as you’ve found, Quickbooks have some issues with their URL validation on the redirect_uri page. The EE Quickbooks help section provides the URL you need to use for your site. That’s in the help section at the top right of the Payment Methods page, then click the Quickbooks payment method section – http://take.ms/6Fva5 For the URL you are entering right now in the screenshots, you just need a trailing slash |
|
Hi TVCT, You login credentials were flagged as spam so I have those now. However, WordFence has locked me out as soon as I logged into the site due to my location. I’m based in the UK so can you temporarily remove the restriction for UK visitors? |
|
|
Hi Tony – sorry about that. I’ve removed the UK from my Wordfence block so you should be good to go. I really appreciate your help! |
|
So, I located the redirect URI in Quickbook Settings but it isn’t an https? See screenshot attached. |
Please use |
|
|
I added it and it accepted it this time… but still not connecting. I continue to the get the ‘We’re Sorry Something went wrong, please try again later” message. I’m at a loss. Maybe Tony can figure it out when he gets a chance to look at it. Thanks Josh. |
You’re site isn’t loading over https, do you have an SSL certificate? In your previous thread you said you had issues with SSL but they had been resolved, however your site isn’t using HTTPS (which is required by Quickbooks), so can I ask what happened with SSL previously? |
|
|
Yes, I DO have an SSL certificate. My webhost, iPage, installed it but I don’t know if I’m suppose to do anything else to “add” it to my site? They have given me what looks like html codes for a certificate and a private key (pasted below) but no instruction as to what, if anything, I am suppose to do with this… they told me once they installed it, I would be all set. |
A simple Yes or No to answer Tony’s question would have been sufficient. I’ve removed your RSA keys from your reply. Under no circumstances should that information be shared in a support forum or an email. Your site isn’t fully using SSL. If you go to your website right now, you’ll see that this URL does not redirect to https: http://www.treasurevalleychildrenstheater.com You can add and install the Really Simple SSL plugin to enforce https across your site (both front end and admin side). |
|
|
Josh – thanks so much for the help. I didn’t intend my previous response to be snarky. Sorry about that. I’ll see about getting this plugin uploaded as you recommend. Maybe that will solve all my problems. I’ve said it before and I’ll say it again, the EventEspresson customer service is beyond awesome! |
I didn’t take your previous reply to be snarky, the reason I bring this up is it’s a security issue. Your server’s private RSA key needs to be just that, private. Please take care to not post that information anywhere and keep it in a safe place. |
|
|
TONY! JOSH! I did it! It worked! Tested and processed and it worked! Thank you for your patience with my non-computer-programming mind. You guys are awesome. |
Nice job 🙂 I’m glad you got it working, any further question just let us know. |
|
The support post ‘Has anyone successfully initiated the Quickbooks Payment app?’ 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.