You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using WooNuxt with the WooCommerce Stripe Gateway and need to use an existing Stripe account for payments. Currently, each time I try to link my own Stripe account, WooPayments either creates a new affiliate account with the same details or forces affiliation to their platform.
Question
Is it possible to use an existing Stripe account without creating a new one or affiliating it with WooCommerce’s platform? If not, is there a plan to support this, or is there a recommended way to implement this?
Thanks!
The text was updated successfully, but these errors were encountered:
You don't have to use the WooPayments plugin. You can use the official Stripe plugin,Payment Plugins plugin,or one of the many other Stripe plugins out there. I have used the latter two before and you can easily use your existing Stripe account with them.
Do you mean in general or specifically with WooNuxt? I tried all the available options and couldn’t get them to work. From my experience, WooNuxt seems pretty tightly coupled with the WooCommerce Stripe Gateway.
That said, I ended up making my own Stripe integration, and it turned out to be a great learning experience. If anyone’s curious, I could share some of the peculiarities I noticed in the original WooNuxt + Woo Stripe setup.
Description
I am using WooNuxt with the WooCommerce Stripe Gateway and need to use an existing Stripe account for payments. Currently, each time I try to link my own Stripe account, WooPayments either creates a new affiliate account with the same details or forces affiliation to their platform.
Question
Is it possible to use an existing Stripe account without creating a new one or affiliating it with WooCommerce’s platform? If not, is there a plan to support this, or is there a recommended way to implement this?
Thanks!
The text was updated successfully, but these errors were encountered: