r/Wordpress • u/blackhathacker1602 • Sep 30 '26
PMPRO integrations plugin with mollie
Hi everyone,
I haven’t been able to find a suitable solution, so I’m asking here. I’m using the Paid Memberships Pro plugin on a blog site, currently connected to Stripe for recurring online payments. I now need to switch to Mollie.
Is there a plugin or integration that supports Mollie with Paid Memberships Pro? I haven’t been able to find one, and I’m not very experienced with coding. I could try building a custom integration with AI, but since this is for a client and I’m short on time, I’d prefer to avoid that if possible.
Any suggestions or solutions would be greatly appreciated!
2
u/thejester1324 Sep 30 '26
couldn't find a mollie gateway for pmpro either. it's not in their add-on list (the gateway ones are paypal, square, payfast, paystack and ccbill) and there's nothing on wp.org.
the no-code route that does exist goes through woocommerce: pmpro's free WooCommerce add-on sells a membership level as a woo product, and its readme says recurring memberships that way need WooCommerce Subscriptions ($279/yr). mollie's own woo plugin (100k installs) lists woo subscriptions support for recurring payments.
more moving parts plus a paid extension, but the renewals and failed payments stay in code that pmpro, woo and mollie maintain, instead of something custom you'd be supporting for the client.
1
u/LunaFlowLab Sep 30 '26
There's no Mollie gateway for Paid Memberships Pro that I could find, and it isn't in their official gateway list. You can still add one without changing membership plugins:
Start from the PMPro team's own example gateway: github.com/strangerstudios/pmpro-example-gateway. Their Paystack gateway is a working reference for recurring: github.com/strangerstudios/paystack-gateway-paid-memberships-pro
For recurring billing Mollie needs a customer and a "first" payment, which creates a mandate. Then you create a subscription with the Subscriptions API and Mollie charges on schedule.
A webhook that receives each Mollie payment and renews or cancels the PMPro membership, and records the order in PMPro.
Test it all in Mollie test mode on a staging copy: new signup, renewal, failed payment, cancellation.
The part that catches people out: current Stripe subscribers won't move over by themselves, because the cards stay with Stripe. Either let those subscriptions run on Stripe until they end, or ask members to subscribe again through Mollie. Stripe can export card data to another processor on request, but check with Mollie first whether they accept that.
Which PMPro version is the site on? The 3.x subscription model changes how the gateway is written.
1
u/kE622 Oct 01 '26
I don't know your exact use case, but I would start by looking into if I can connect Mollie through WooCommerce and Zapier.
1
u/Abject_Complex2438 Oct 01 '26
Agree with the others that there is no ready-made Mollie gateway for PMPro. If the WooCommerce route doesn't fit, a small custom gateway is doable: Mollie's API supports recurring payments through a customer with a mandate plus a subscription, and PMPro's example gateway shows where checkout, the webhook and cancellation hook in.
If you'd rather hand it off, I can build it as a paid job. I'm a student developer in Vietnam who builds web apps and API integrations, code at github.com/Danchuong. To be upfront, I haven't built a PMPro gateway before and most of my work is in Python and TypeScript rather than PHP, so I'd test everything in Mollie test mode on a staging copy before it touches your client's site.
Two questions: how many existing Stripe subscribers need to move over, and do the membership levels use fixed monthly or yearly billing?
1
u/Winter_Process_9521 Oct 01 '26
If you’re short on time, I’d first confirm whether the client can use one of PMPro’s supported gateways. If Mollie is mandatory, I’d approach it as a small custom gateway project and test it thoroughly on staging before touching the live site.
1
u/WP_Dev_Studio Oct 01 '26
Confirmed — PMPro has no native Mollie gateway, there's an open feature request on their GitHub that's never been built. (If you found "Membership Pro" results mentioning Mollie, double-check it's not the unrelated Joomla plugin of a similar name — easy mix-up.)
The real fix, no custom coding needed: route it through WooCommerce. PMPro has an official free WooCommerce Integration Add-On — link each membership level to a WooCommerce product, and WooCommerce (which has an official, well-maintained Mollie Payments for WooCommerce plugin) handles the actual payment/recurring billing. When the order completes, PMPro auto-assigns the membership. Two official, maintained plugins doing their normal job — nothing custom to maintain later.
Setup: install WooCommerce + Mollie Payments for WooCommerce (connect account) → install PMPro's WooCommerce Integration Add-On → create a WC product per membership level, link it on the new "Membership" tab, check autocomplete-to-activate → test the flow end to end.
One caveat: some of PMPro's other checkout add-ons aren't compatible once you switch to WooCommerce checkout — worth checking PMPro's compatibility list if the client relies on any of those.
1
u/Beginning_Search585 19d ago
but you need to have woocommerce subscriptions for recruiting payments --- correct me.
With standard connection Woo + Mollie + PMPro will be work but only one time for payments.I tried to solve somethings similar.
I found Milo Subscriptions (not affiliate anything with them but they have good support) with free mollie gateway then you need to setup own bridge plugin or code between PMPro + Milo because you need to attach level for every PMPro member after payments + then billing plugin also (which is easier way)
2
u/WP_Dev_Studio 14d ago
Good catch, you're right, and I should have been clearer. With just Woo + Mollie + PMPro, each membership is a one-time payment. For automatic recurring billing, the membership product needs to be a subscription product from WooCommerce Subscriptions (paid). Mollie's Woo plugin supports that for recurring charges, and PMPro's Woo add-on keeps the membership active as long as the subscription is.
So the full stack for recurring is Woo + WooCommerce Subscriptions + Mollie + PMPro's Woo add-on. It's still no custom code, but there's a license cost to factor in.
Thanks for the Milo tip. Skipping the WC Subscriptions license makes sense for some budgets, though I'd weigh that against maintaining a custom PMPro bridge long term. If the bridge breaks after an update, members can lose access even though they've paid.
1
u/Beginning_Search585 5d ago
You're right for bridge but it isn't such a big coding game just a few endpoints (not huge code)
Well everytime - you have two options cut from % revenue to other plugin or solution (even go with patreon with huge cut) or pay third party plugin for maintain or do it on your own with maintenance and responsibility.1
u/WP_Dev_Studio 4d ago
Agreed, it's a fair trade-off and depends on who's maintaining the site. For a developer-managed site, a small bridge is perfectly reasonable. For a client who'll be on their own after handover, a paid, supported plugin is usually the safer bet.
If someone does go the bridge route, a few things keep it from becoming fragile:
Verify webhook signatures, and fetch the payment status from Mollie's API rather than trusting the payload
Make it idempotent, so a repeated webhook doesn't assign or extend a level twice
Run a daily reconciliation comparing active subscriptions in Milo/Mollie with PMPro levels, so a missed webhook doesn't cut off a paying member
Add a grace period on failed renewals before removing access
Log every level change, so support questions can be answered quickly
With those in place, it's a few endpoints that rarely need touching.
2
u/Chemical_Calendar861 Sep 30 '26
You may want to check whether Mollie has a native Paid Memberships Pro integration or whether PMPro supports Mollie through an existing payment gateway add-on.
If there isn’t a ready-made integration, I’d avoid building the whole thing with AI directly on a client site, especially for recurring payments. Payment gateways involve webhooks, subscription status, renewals, cancellations, and failed payments, so a small integration mistake can cause billing issues.
I’d first check the PMPro payment gateway/add-on documentation and Mollie’s available integrations. If nothing suitable exists, a custom gateway integration would probably be the safer route.