Adobe's merchant documentation for Adobe Commerce and Magento Open Source does not describe a built-in subscription billing engine, so subscription based ecommerce on Magento runs through one of three routes: a subscription extension that stores schedules in Magento, a payment provider's billing product (such as Stripe Billing through Stripe's Adobe Commerce module), or an external subscription platform integrated with the store. Whichever you choose, it must charge saved cards without the customer present, retry failed payments, create a proper Magento order for each renewal and give customers a self-service way to skip, change or cancel.
Below are the subscription models, the billing and dunning requirements to put in your specification, and how the three routes compare.
Subscription models and what each needs
| Model | Example | What the system must handle |
|---|---|---|
| Replenishment | Coffee, pet food, contact lenses every 4 or 6 weeks | Customer-chosen intervals, skip and delay, stock checks before each renewal, shipping recalculation |
| Curated box | Monthly box with changing contents | Fixed billing date, cut-off dates, product assignment per cycle, prepaid terms (3, 6, 12 months) |
| Access or membership | Free shipping club, members-only prices | Linking subscription status to a customer group, renewal without shipping, prorated upgrades |
| Digital or service | Software licences, maintenance plans, content | Virtual products, entitlements, renewals that trigger provisioning |
| B2B standing order | Scheduled consumables for a business account | Purchase orders or payment on account instead of cards, approval rules, invoicing |
The model decides more than the product setup. A replenishment program lives or dies on how easy it is to skip a delivery; a curated box needs cut-off logic; a membership needs clean group switching when a payment fails.
Billing and dunning requirements
This is the part most subscription projects underestimate. Use it as a checklist for your specification.
Payment tokens and stored cards
- Tokenized payments: renewals must charge a stored payment token held by the payment provider, never card data stored in Magento. Magento's Vault framework stores gateway tokens for this purpose, and payment provider modules implement it. Check that your provider's module supports vaulting and merchant-initiated charges.
- Strong Customer Authentication: in the EU and UK, the first payment usually needs authentication, and later merchant-initiated renewals can then be processed without the customer present. Your provider's integration must flag these transactions correctly.
- Card updates: cards expire and get reissued. Ask whether your provider supports automatic card updates or network tokens, which reduce failures without customer action.
- Payment method changes: customers need to replace a card from their account without cancelling the subscription.
Dunning and failed payments
- A retry schedule (for example, several attempts over a set number of days), configurable per model
- Emails at each failure with a link to update the payment method
- A defined end state: pause, cancel, or downgrade the customer group
- Rules for whether the order ships before payment succeeds
- Reporting on failed, recovered and lost renewals
Orders, stock, tax and shipping
- Each renewal creates a real Magento order so fulfillment, ERP export and reporting keep working
- Stock is checked before charging, with a policy for out-of-stock renewals
- Tax and shipping are recalculated per renewal, because rates and addresses change
- Price changes: decide whether existing subscribers keep their price, and how you notify them
Customer self-service and cancellation
Customers should be able to view, skip, reschedule, change quantities, update addresses and cancel online. Cancellation rules are a legal matter, not just UX. In the US, the FTC's 2024 "click-to-cancel" amendments to its Negative Option Rule were vacated by a federal appeals court, the FTC revised the rule in February 2026 to conform to that decision, and in March 2026 it opened a new advance notice of proposed rulemaking, so check the FTC's Negative Option Rule page for the current position. The Restore Online Shoppers' Confidence Act and state automatic-renewal laws still apply, and EU and UK consumer rules have their own requirements. Get advice for your markets; this is general information, not legal advice.
Payment provider choice affects most of the list above. Our guide to payment gateways for Adobe Commerce compares the options.
Three ways to run subscriptions on Adobe Commerce
1. A subscription extension
Several extension vendors sell subscription modules on the Adobe Commerce Marketplace (Aheadworks' Advanced Subscription Products is one example) that add subscription products, schedules and a customer subscription area to Magento. Depending on the extension, schedules are kept in your database or on the payment gateway side, and renewals charge a supported payment method's stored tokens. Check each listing for compatibility with your exact Magento version and for the payment methods it supports for renewals, because that list is usually shorter than the list of methods the store accepts.
2. A payment provider's billing product
Stripe documents a subscription option in its Adobe Commerce module. According to Stripe's documentation, you can turn simple or virtual products into subscriptions with a frequency, trial days, an initial fee and an optional fixed start date. Stripe Billing collects recurring payments and handles failed-payment notifications, and the module creates a new Adobe Commerce order for each successful renewal after a webhook, recalculating shipping and tax. Customers can change quantities, options, address and payment method from their account. The trade-off is that billing logic sits with one provider, so switching providers later means migrating subscriptions.
3. An external subscription platform
Dedicated subscription and billing platforms manage plans, invoices and dunning outside Magento and push orders into it through the API. This suits businesses where subscriptions are the main revenue line, or where subscriptions are also sold through other channels. It is the most integration work: customer accounts, orders, stock and refunds must stay in sync in both directions.
Comparison: extension vs billing product vs platform
| Factor | Magento extension | Payment provider billing | External platform |
|---|---|---|---|
| Where schedules live | Magento database | Payment provider | External platform |
| Dunning | Extension features, varies by vendor | Provider's retry and email tools | Usually the most complete |
| Payment flexibility | Limited to methods the extension supports | Tied to one provider | Depends on the platform's gateways |
| Integration effort | Lowest; install, configure, theme | Low to moderate | Highest; two-way sync |
| Upgrade risk | Extension must keep pace with Magento releases | Provider module must keep pace | Connector must keep pace |
| Best for | Replenishment and simple boxes | Stores already on that provider | Subscription-first businesses and multichannel |
When none of these fit, for example B2B standing orders paid on account, a custom module is reasonable. Our guide to build vs buy for Magento extensions helps you decide.
Retention: the other half of subscriptions
Subscription revenue depends on keeping subscribers. Practical levers include letting customers skip instead of cancel, offering a pause, reminding customers before a renewal ships, and rewarding milestones rather than every renewal. If you run a points program, decide whether renewals earn points; our guide to ecommerce loyalty programs explains how to model that cost.
Testing before launch
- Run a full renewal cycle in the payment provider's test mode, including a successful charge and a failed one.
- Expire a test card and check the update flow and retries.
- Test a renewal when the product is out of stock or disabled.
- Change tax rates and shipping prices and confirm renewals recalculate.
- Refund a renewal order and confirm stock, ERP and reporting update.
- Cancel from the customer account and confirm no further charges are scheduled.
Frequently asked questions
Does Adobe Commerce have built-in subscriptions?
Not as a documented core feature. Adobe's merchant guides do not describe a built-in subscription billing engine, so subscriptions come from extensions, payment provider modules (such as Stripe's Adobe Commerce module) or integrated platforms.
Can I store card details in Magento for renewals?
You should not. Use your payment provider's tokens through the Vault framework or the provider's billing product, so card data stays with the provider.
Can subscriptions work with PayPal or wallets?
It depends on the provider and the extension. Confirm that the method supports stored, merchant-initiated payments before offering it on subscription products.
Next step
Start by writing down your subscription model and the dunning rules you need, then check each option against that list. Mistri's Adobe Commerce development team can help you choose and integrate the right route, and our Magento extension development service covers custom subscription logic when off-the-shelf options fall short.
Sources
Use Stripe Billing to enable subscriptions for Adobe Commerce (Stripe Docs); Adding vault integration (Adobe Developer); Restore Online Shoppers’ Confidence Act (FTC); Negative Option Rule (FTC); Aheadworks Advanced Subscription Products (Adobe Commerce Marketplace).


