By reducing implementation friction while maintaining the adaptability that makes Drupal Commerce powerful, we’re making it easier for organizations to choose and succeed with our platform.For years, merchants using Stripe with Drupal Commerce have faced a familiar dance: sign up for Stripe, create API keys in the Stripe dashboard, copy them over to Drupal, paste them into the right fields, and hope everything connects properly. Not complicated for a developer or experienced site builder who is familiar with the steps, but it’s one of those friction points that makes launching a new e-commerce site more complex than it needs to be.
What Changes With Stripe Connect
This dual approach ensures backward compatibility while providing a clear migration path. For most standard implementations, we expect the Stripe Connect option to become the preferred choice.
For merchants new to Stripe
The technical implementation introduces two distinct payment gateway plugins within the Commerce Stripe module:
For existing Stripe merchants
This OAuth method of authentication is now Stripe’s preferred method for merchant authentication. They are not removing shareable keys, but they will continue to push people towards Stripe Connect, and this is where most of the innovation will be happening.
Why This Matters Beyond Convenience
Try the latest release out. If you have any other ideas for improvements that might impact your specific use case, let us know!
Foundation for advanced features
Connect accounts unlock additional capabilities that weren’t easily accessible with the traditional API key approach. Future enhancements, such as deeper integration between Stripe data and Drupal Commerce, become possible.
Reduced support overhead
Important: merchants running specialized configurations, such as their own marketplace implementations, may need to continue using the traditional API key approach. Stripe Connect is primarily designed for standard merchant-to-Stripe relationships. This may change in the future.
Stripe’s preferred method of authentication
When setting up a payment gateway, merchants see a “Connect with Stripe” button. Clicking this button takes them to a Stripe-hosted page where they can create a new account. Once authenticated, they’re redirected back to Drupal with the connection automatically configured.
Implementation Details for Developers
By eliminating manual key configuration, we anticipate fewer setup-related support requests, allowing both merchants and developers to focus on building great commerce experiences rather than troubleshooting connection issues.
- Legacy Integration: The existing “Card Element” and new “Payment Element” implementation continues to work with manual API key configuration for merchants who need this approach.
- Stripe Connect Integration: The “Payment Element” plugin can also leverage Connect for simplified setup.
Stripe Connect changes this entire workflow by acting as a secure bridge between your Drupal Commerce site and your Stripe account. Instead of manually copying credentials, merchants can now authenticate directly through Stripe’s interface and automatically establish the connection.The same streamlined process applies. They just need to log into their existing Stripe account to connect without manual key management.
Moving Forward
That changes with the latest release of the Commerce Stripe module. It now integrates with Stripe Connect, which simplifies the payment gateway setup process.While the improved user experience is the most visible benefit, Stripe Connect brings several strategic advantages that we believe strengthen the entire Drupal Commerce ecosystem.
