Will FluentCart continue to support Mollie Subscriptions API long-term?
Hi FluentCart team and community,
We’re seriously considering migrating our entire subscription infrastructure to FluentCart because we rely on provider-native recurring via Mollie — specifically the Mollie Subscriptions API, not the older “Mollie Recurring/RCUR” method that some plugins use. In our current setup (Pronamic Pay + Gravity Forms) much of the logic lives in WordPress, and we’ve had ongoing challenges with status syncing, webhook handling and reliability.
Before we invest significant time and resources into migrating:
1. Does FluentCart plan to continue long-term support for the Mollie Subscriptions API (the API that schedules recurring charges, mandates, retries, etc.), and not fall back to a WordPress-based subscription model?
2. Is the Mollie subscription integration considered a core part of FluentCart’s roadmap, especially for handling recurring via provider-side webhooks and schedules?
3. Are there planned changes to how subscription billing is handled that we should be aware of (for example changes in webhook requirements, API versions, or a shift in architecture)?
We want to ensure that FluentCart will remain a stable foundation for managing Mollie-driven recurring payments over the next few years before committing to a migration and building workflows around it.
Thanks in advance for clarifying!
Shahjahan Jewel Can you respond to this? It is important to know before we migrate a lot of subscriptions over to Fluentcart.
Why do you think we will not support the Mollie API for a long time? Each and every integration we are building will get updates for all the API changes by them.
Hi Jewel,
Thanks for your answer. I don’t mean that you will stop supporting Mollie. My question is specifically about how it is integrated and whether that architecture will change in the future.
From what I understand, FluentCart currently uses the Mollie Subscriptions API, where Mollie is the source of truth. That means subscriptions continue running even if something happens on the WordPress side. We really like this approach.
However, many other plugins we currently use rely on the Mollie Recurring API, where the subscription logic (intervals, amounts, scheduling) is handled inside WordPress and stored in the database. That puts much more pressure on WordPress to keep subscriptions running correctly.
In our experience, this has caused issues such as:
Subscriptions stopping because cron jobs failed
Webhook or sync problems
In some cases even duplicate charges
That’s why we strongly prefer the provider-side subscription model.
So my question is:
Are you planning to stick with the Mollie Subscriptions API architecture, or is there any intention to move toward a WordPress-driven recurring model in the future?
We just want to be sure before investing heavily in migrating our full subscription setup.
Thanks again for clarifying.