Stripe has officially joined the Sylius ecosystem as our Preferred Payment Partner, marking another important step in the development of our payments ecosystem. Stripe is a financial infrastructure platform for businesses, used by millions of companies to accept payments and grow revenue.
This partnership also represents something broader. Stripe has an established presence in the PrestaShop ecosystem, and extending this relationship to Sylius is another concrete example of the growing connection between the two open-source eCommerce ecosystems. For merchants, the partnership means access to a Stripe integration maintained alongside Sylius, while their everyday technology choices help support the continued development of our open-source framework.
It starts with the official Stripe Plugin. The plugin integrates Stripe as a payment gateway for Sylius and gives projects a ready-to-use connection to Stripe’s payment infrastructure, reducing the need for development teams to build and support a custom solution. The plugin is developed and maintained by our internal team alongside the platform, helping keep it aligned with supported Sylius versions. Rather than managing the core payment setup independently, merchants and development teams can rely on an official solution with a clearly defined owner.
Through Stripe, merchants gain access to global card processing, digital wallets such as Apple Pay and Google Pay, and local payment methods across key markets, including BLIK and Przelewy24 in Poland, iDEAL in the Netherlands, and Bancontact in Belgium, alongside broader multi-currency and fraud-prevention capabilities. The plugin offers two payment gateway types. Stripe Checkout redirects customers to a Stripe-hosted checkout page, while Stripe Web Elements embeds the form directly into the Sylius storefront using Stripe Payment Intents. Both options give Sylius projects the flexibility to choose the checkout experience that best matches their architecture, markets, and customer journey.
Already using Stripe with Sylius? If your project currently uses an earlier community-maintained Stripe package, an older custom setup, or a self-built integration, now is the best time to review the official migration guidance – including the move toward Restricted API Keys and the available paths for existing implementations.
Stripe itself is not new to the Sylius ecosystem. Before the current partnership was established, the integration had already been evolving through the work of the Sylius community. Francis Hilaire, together with other contributors, played an important role in building the foundation of the Stripe Plugin and bringing modern Stripe payment flows into Sylius. The official integration available today did not start from scratch. It builds on years of open-source contributions, practical implementation experience, and feedback from developers using Stripe with Sylius in projects.
With the new partnership, Sylius has taken responsibility for the continued development and maintenance of the integration. The repositories are now under our organization, while the plugin remains open-source. What started as a community plugin is now officially part of Sylius.
To our coding heroes – Francis and everyone else involved – you rock ♥️
Have questions? Contact us or connect with the Sylius Community in the #payments channel on our Slack. Click the banner above to join!
For merchants already using Stripe, this shift is particularly relevant. A custom payment integration gives development teams full control, but it also means taking responsibility for keeping that integration compatible with changes across Stripe APIs, Sylius versions, dependencies, and the surrounding application. An officially maintained integration can reduce that workload. With Sylius responsible for the plugin, merchants gain a defined owner for the core integration and a solution that is maintained as the platform evolves.
That can mean less integration-specific maintenance for internal teams and a clearer path when upgrading Sylius. For projects using the earlier community-maintained Stripe packages, the transition is also straightforward at the project level: the repositories have moved under our organization while the existing Composer package names remain in place. The official migration guide also introduces Stripe Restricted API Keys and explains how they can replace unrestricted secret keys. Projects that use additional Stripe resources outside the standard plugin scope should verify the required permissions before making the switch.
And, as with this official Sylius payment integration, there’s a second benefit worth keeping in mind: choosing it also helps support the continued development of open-source. More on that below.
Ready to switch? Follow the official Migration Guide to move your existing Stripe setup to the supported integration.
There is another benefit to choosing the official integration. Choosing an official Sylius payment extension helps support the continued development of open-source. Keeping Sylius moving forward means ongoing work behind the scenes: maintaining compatibility and dependency versions, improving security, fixing bugs, testing releases, and addressing issues reported by the community. As the platform grows, so does the effort required to keep it stable, secure, and ready for what comes next.
Official payment partnerships create a way for the ecosystem itself to help fund that work. We reinvest 100% of the revenue generated through PSP affiliate and revenue-share partnerships into the development of Sylius Community Edition.
Choosing an official integration is not only a technology decision. It is also a way to contribute to the long-term sustainability of open-source.
The Stripe partnership is also a good example of how the Sylius ecosystem is evolving. Working more closely with established global technology providers gives merchants access to integrations with clearer ownership and long-term maintenance, while creating more opportunities for technical collaboration, ecosystem development, and joint market activity. It also strengthens the surrounding partner ecosystem. Agencies and development teams can build on a common official integration rather than repeatedly solving the same payment infrastructure problems independently for each project.
The closer connection between Sylius and PrestaShop is already creating new opportunities, and Stripe is a good example of that in practice. Stripe has long been present in the PrestaShop ecosystem, and its role as Sylius’ Preferred Payment Partner brings that relationship into Sylius as well. For merchants and developers, the result is simple: easier access to Stripe through an official integration maintained with us.
This partnership is more than just a new payment plugin. It brings together three things that matter for the whole Sylius ecosystem:
The official Stripe Plugin is an open-source extension maintained by Sylius for Sylius 2.x projects. This plugin enables Stripe Checkout and Stripe Web Elements payment gateways, integrating Sylius stores with Stripe through two distinct payment flows.
The current official Stripe Plugin targets Sylius 2.x. Projects still running Sylius 1.x use the separate Payum Stripe Plugin, which is now deprecated. The official Migration Guide covers both setups and explains the available upgrade paths.
The plugin provides access to card payments, Apple Pay, Google Pay, Stripe Link, and local payment methods such as BLIK, Przelewy24, iDEAL, and Bancontact. The exact methods displayed at checkout depend on the merchant’s Stripe Dashboard configuration, market, currency, and customer eligibility.
Stripe Checkout redirects customers to a checkout page hosted by Stripe and uses the Checkout Sessions API. Stripe Web Elements embeds the form directly into the Sylius storefront and uses Stripe Payment Intents, giving projects more control over the on-site checkout experience.
Yes. The official Stripe Plugin is compatible with Sylius API Platform endpoints and can be used in headless and API-driven storefronts. Projects can select the gateway type that best fits their frontend architecture and customer journey.
The official Migration Guide outlines separate paths for three setups: Sylius 2.x with an earlier Stripe Plugin release, Sylius 1.x with the Payum Stripe Plugin, and a custom Stripe implementation. Existing Composer package names and namespaces remain unchanged following the repositories’ move to the Sylius organization.
Restricted API Keys provide access only to selected Stripe resources and actions, unlike unrestricted secret keys that have broad account permissions. The official Sylius Stripe Plugin uses Restricted API Keys to limit unnecessary access. Projects using additional Stripe resources should verify that their key includes all required permissions before switching.
Sylius reinvests 100% of the revenue generated through PSP affiliate and revenue-share partnerships into the development of Sylius Community Edition. Choosing the official Stripe integration therefore also helps fund ongoing maintenance, security improvements, testing, and development of the open-source platform.
Sylius Plus 
