new STRIPE workflow conflicts with plugins’

Is anyone experiencing conflicts and confusion lately, since STRIPE has changed their workflow?

For instance, my theme loads subscription plans automatically but now Stripe treats them as Products, i.e. a top category with no billing cycles. To create the billing cycle one must create Plans, which are therefore subcategories of Products.
Then I added a new membership plugin (hoping it would hook up with my theme) which treats a Subscription as something that requires a plan attached. It makes sense but when a user clicks on “buy now” the plugin creates a new Product inside Stripe instead of creating a new Plan. It does that even if the user then abandons his purchase.
By doing so I have both Stripe and the plugin inundated with Products and Plans that are not real.

Any comment or views about this?
I fear that any Stripe plugin would not work as intended.

• This topic was modified 4 years ago by Jan Dembowski. Reason: Moved to Fixing WordPress, this is not an Everything else WordPress topic