You can run subscriptions with Mollie without writing code, but not in Mollie's Web app alone. Mollie's documentation says recurring payments are API-only, either directly or indirectly through a partner. A billing layer such as PayRequest supplies the no-code plan, consent, invoices, reminders and customer portal while Mollie processes the payment.
This guide is for European service businesses, creators and membership operators. Its original asset is the launch ledger below: every state must work before a subscription is shared.
The No-Code Mollie Subscription Stack
| Layer | Job | What to verify |
|---|---|---|
| PayRequest | Plan, checkout, schedule, invoices and communication | Price, interval, start date and cancellation policy |
| Mollie | First payment, mandate and recurring charges | Live profile, eligible method and valid mandate |
| Customer | Gives consent once | Amount, frequency, merchant and next charge are clear |
| Operations | Handles paid, pending, failed and canceled states | Access follows confirmed status |
Mollie's recurring-payments documentation explains that the customer completes a first payment to give consent. Later eligible recurring charges happen in the background.
Set Up the Subscription
- Verify the Mollie business account and live website profile.
- Enable an eligible recurring method for that profile.
- Connect Mollie from PayRequest.
- Create the plan name, price, currency, interval and start date.
- Publish renewal, cancellation, access and refund terms.
- Complete a real low-value buyer-view signup.
- Confirm the first payment, mandate, invoice and next charge.
- Cancel the test through the customer route and confirm collection stops.
Do not call the plan live after seeing only a checkout redirect. The first payment, mandate and subscription are separate records.
Build the Failure Policy First
- Temporary failure: keep a short grace period while an eligible retry runs.
- Customer action required: send one secure payment-update route.
- Invalid or revoked mandate: stop blind retries and request fresh consent.
- Dispute: pause collection and investigate the transaction and service evidence.
Mollie says a subscription payment may be retried up to five times, once daily, depending on method and failure reason. Some reasons cancel a subscription immediately or after repetition. Respond to the actual status rather than assuming every failure gets five retries.
When Direct Development Fits Better
Build directly on Mollie's API for bespoke usage events, unusual intervals or a custom state machine. Use a no-code layer for a standard fixed membership, retainer or recurring service where the goal is to operate billing without maintaining payment code.
PayRequest's subscription billing and Mollie billing pages show the layer added above the processor. Launch only when a buyer can consent, pay, see the next date, manage the plan and cancel without staff editing Mollie records by hand.