Posted: December 16, 2021 at 12:23 pm
Unable to connect to a client’s Stripe account. I’m added as developer to their Stripe account and have access when I login to Stripe. When I click the Connect with Stripe button and login with my developer account, it creates a new blank Stripe account instead of letting me select my client’s already existing account. I added the filter FHEE__EE_PMT_Stripe_Onsite__generate_new_settings_form__hide_key_fields to my functions.php then updated the keys using the ones from my client’s account. Then when I click the Connect with Stripe button it still doesn’t show me their account as an option, it just shows me the blank account it tried to create prior. How can I connect with Stripe? Their new site is live but we can’t process payments. |
|
Hi there,
I don’t think it will work for an account your added to as a developer, they would need to link the account whilst logged into the main account. However….
This part I’m confused about, if you are using the Secret and Publishable keys directly from the account then you don’t need to use Stripe connect to connect the account (the keys give the payment method access to the account). So if you’ve added the above, and added the keys to the payment method, do Stripe payments then not work? |
|
Yes, I added their keys but the Connect button was still there and didn’t show as connected. No caching plugin, all plugins up to date. They’re hosted on Godaddy managed WordPress if that makes a difference. Godaddy provides some sort of caching but that’s been cleared and has no configuration options. Also deleted and reinstalled the Stripe plugin. Getting this response in Firefox, Firefox private, Chrome and Safari. Any ideas? |
|
I believe it is working now but it is misleading to show the Connect button when entering the keys manually. It also doesn’t show a status of being properly connected when you do it that way. That’s why I didn’t think it was connected. I just went through the Stripe plugin setup again using the test keys and test mode and was able to successfully process a registration using Stripe. |
|
It will do, they are completely separate. You use Stripe connect OR the keys (they are now hidden as Connect is the preferred connection method), adding the keys will not change the connected buttons as they are totally separate authentication methods. If using the keys, leave the connect button alone, the keys alone give the payment method access to the account.
This doesn’t sound like a caching issue, although…
Indeed it does, GoDaddy Managed WordPress hosting forces caching on all pages of your site and either the caching will need to be completely disabled or (the better option) the EE critical pages excluded from the cache. You’ll need to contact GoDaddy on which option they have available as it’s their own caching system. For details on the pages which needs to be excluded follow the details in this guide: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
Which response? As mentioned I don’t think you can connect the account as a developer on that account. You need to be logged into the main Stripe account to connect to it if using Stripe connect, if using the keys then just make sure they are the correct keys for the main account. What is happening when you try to pay with Stripe whilst using the keys currently? |
|
You’ve posted your latest reply whilst I posted mine, but I’ll answer this:
It’s not misleading when you don’t see the key fields, you’ve added a function to force them to show which is why it doesn’t make sense. The key fields are the ‘old’ method of connecting to the Stripe account. The ‘Connect’ button is the ‘new’ OAuth method of connecting to Stripe. We left the key fields in the system so that it is still possible to connect via keys if needed but it’s not the norm so 99% of users don’t see both and again, as OAuth is the preferred method we don’t hide the connect button based on the key fields being shown.
Great. If you are eventually looking to switch to use Stripe connect you’ll need to log into the main account rather than the developer account linked to it so that you can ‘Connect’ the account. |
|
It’s working now with the keys. It would helpful to hide the connect button when enabling the keys via the filter and show a status on the Stripe settings page after saving the keys to show if the connection was successful. |
|
We crossed replies again 🙂 I understand using Connect is the preferred way but they didn’t want to give me access to their Stripe login which I completely understand. That’s why I had developer access. It’s too bad the Connect method doesn’t seem to work for Developer access. It would have saved me some hours today to realize that using the keys manually wouldn’t give any indication that it was connected or working. Adding this here so others can find this information later. |
|
Whilst I understand them not wanting to give you their login details, they’ve given you almost full access to their Stripe account with a developer account so there is very little difference there. And no, I’m not saying they should give you their login details here but not ‘giving you access to their Stripe login’ in terms of the account itself doesn’t make sense. You can do almost everything they can do as a developer account on their account so they’ve already handed over 99% of their Stripe account to you. If you actually wanted to be disruptive towards this client there is very little difference between your developer account and theirs but tbh most users don’t realize that either way. Again, I’m not saying they should give you their credentials. They can connect the Stripe account whilst logged into their account and because you have a developer account linked to them, you can view everything that happens on that account from there. I’ve created a ticket to see if we can add a step in the oAuth process for users with multiple businesses linked to their account (such as developers) to select the business they trying to connect with but IIRC we’ve discussed this previously and it wasn’t possible (that may have changed now).
I’ll open an internal discussion on this, generally, we wouldn’t add enhancements to a deprecated connection method. |
|
The support post ‘Stripe Integration: Creates new account instead of showing existing account’ 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.