Use the Stripe app for Adobe Commerce (Magento 2)

Install the module

php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy

Upgrade the module

Before you upgrade:

• Back up your files and database.
• Start with your sandbox environment.
• Keep a copy of any customization you made to the module’s original code.
• Check out the CHANGELOG.

Patch releases (x.x.Y) are backward compatible and require no extra development on your side after you upgrade. Minor and major releases might add new features or change code in a backwards incompatible way. If you customized the module’s code, you’ll need to port these customizations after upgrading and resolve any potential conflict.

composer remove stripe/stripe-payments
composer require stripe/stripe-payments
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento cache:clean

Uninstall the module

Before you uninstall:

• Backup your files and database.
• Keep a copy of any customization you made to the module’s original code in case you need to reinstall it later.

composer remove stripe/stripe-payments
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento cache:clean

Lifecycle policy

The latest version of the module supports the following versions of Adobe Commerce:

For stripe/stripe-payments:4.3.* and later, we provide new features, bug fixes, and security patches. Older versions are deprecated. Stripe recommends that you upgrade as soon as you can. All releases are available in the Adobe Marketplace and in the stripe-magento2-releases GitHub repository.

Version history

Learn about backward compatibility changes in Adobe Commerce app versions (Magento 2).

Version 4.1

Version 4.1.0 introduces changes to handle scenarios where orders could be placed and invoiced without collecting payment. These scenarios include:

• Purchases of trial subscriptions.
• Subscriptions with future start dates.
• Upgrades or downgrades of existing subscription plans.

Previously, the module automatically refunded and closed these orders with an offline credit memo. Now, to improve tax reporting:

• Automatic refunds are deprecated.
• Order items in these scenarios have a custom price of 0.
• These items are excluded from shipping amount calculations.

This results in orders with zero subtotal, shipping, and tax amounts. When regular products are purchased with subscriptions, the subtotal, shipping, and tax amounts only reflect the regular order items. These changes ensure the order grand total matches the collected payment amount on the order date.

Additionally, version 4.1 changes how partial captures and refunds are handled:

• Previously, partial captures or refunds from the Stripe dashboard automatically created invoices or credit memos in Magento.
• These documents didn’t include order items, using manual totals or adjustment fees or refunds instead.
• This approach caused issues with tax reporting.

In version 4.1:

• Only full captures and full refunds result in automatic invoices or credit memos.
• For partial captures or refunds, merchants should use the Magento admin panel.
• This ensures correct tax breakdown on documents and accurate reporting to the Stripe API.