Require Stripe module

Created on 11 October 2016, almost 9 years ago
Updated 18 August 2025, 18 days ago

For shops that use Commerce Stripe, and have been using it for a long time - such as ours - who then want to offer subscriptions to their customers, doing so is not very easy with the tools available. Commerce Stripe currently does not provide subscription functionality; if a user wants that, they need to download Stripe β†’ and Stripe Subscription β†’ modules. The alternative would be to add Subscription functionality to Commerce Stripe, which does not seem like the ideal route to take.

One problem is that the Stripe module's Library integration conflicts with Commerce Stripe's, and the module itself has a barebones (and by the looks of it, non-functioning) Commerce integration module as well; we'd be better off removing that code from the Stripe module altogether, and instead, allowing users to download Commerce Stripe on its own - but requiring Stripe in order to function.

The task would require ripping out any code from Commerce Stripe that does basic things around configuration and libraries, and potentially fields as well - but as per a discussion with @bojanz I think each payment method should still specify its own API keys. Perhaps we can leverage Stripe functionality to pre-populate those values but not require they all be the same.

I'm open to more discussion but, the benefits are many. Requiring Stripe would:
1. Cut down on code duplication;
2. Make both modules lighter;
3. Allow Commerce Stripe stores to leverage other functionality surround Stripe, including (eventually) ACH payments and Stripe Connect (systems which require users to authenticate, a process well outside of the scope of Commerce payment methods) and of course, Subscriptions - among other things.

🌱 Plan
Status

Closed: outdated

Version

3.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States torgosPizza Portland, OR

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024