• Resolved midmich

    (@midmich)


    Good day. We have two websites that we use the stripe checkout on and they are all managed under one corporation using one stripe account. When we try to connect the second site we get an error that the connection is already established. It is for the first site but not the second. With this new update will this plugin still work for two sites using one stripe account to connect to?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support WebToffee Support

    (@webtoffeesupport)

    HI @midmich,

    Greetings from Webtoffee!

    We acknowledge that you are utilizing a single Stripe account to integrate with two websites. Upon connecting your first website to Stripe, the status will reflect as “connected” in Stripe. Consequently, when you proceed to connect to the second site, Stripe will display the message “Already installed”. Verify whether this is the message you are receiving. If so, you may proceed by selecting the previously established connection and then clicking “Continue” to complete the connection for the second site.

    If you are encountering a different issue, please share a screen recording with us to facilitate a more comprehensive understanding of the matter.

    Thread Starter midmich

    (@midmich)

    That is what we are seeing and then when we click continue and we are redirected back to the site we are still shown the message saying “Urgent: Switch to OAuth…….” and we are assuming the connection failed. I will post a recording shortly.

    Thread Starter midmich

    (@midmich)

    Here is the link to a quick screen view of what is happening. Thank you.

    Plugin Support WebToffee Support

    (@webtoffeesupport)

    HI @midmich,

    We have recently released an updated version of the plugin. Could you kindly test the latest iteration? Our team has been unable to reproduce the issue within our multisite test environment.

    Furthermore, if your firewall is blocking IP requests, we recommend whitelisting the following IP address 128.199.13.9 in your security plugin or at the hosting provider’s end.

    Thread Starter midmich

    (@midmich)

    Awesome it does seem it was CloudFlare blocking the request. Whitelisting the above IP fixed the issue.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.