systeme.io Payment Plans: When an Installment Fails

Selling a coaching package or a course in installments on systeme.io takes one setting: a price plan of the type Payment plan, with the number of payments filled in. The harder question comes later, on the morning the third installment doesn't go through. Does systeme.io try again? For how long? Does the buyer keep their access in the meantime? And who tells them?

systeme.io's help center answers most of that, but the answer isn't the one sellers tend to expect. For card payments, its article on failed subscription payments says "systeme.io does not control the retry schedule"; the retries follow the settings in your own Stripe account. Other gateways run on clocks you can't change at all. Flutterwave retries three times, 30 minutes apart. Paystack and Mollie don't retry. When the processor gives up, systeme.io cancels the subscription and access to the course stops.

So the grace period your buyer gets belongs to your payment processor, not to systeme.io. That's the order this guide follows: pick the processor and the access setting first, then build the failed-payment email around the clock you've ended up on.

Which clock you're on

If you sell installments by card, use Stripe unless your buyers can't pay that way. It's one of two rows where you set the clock yourself (GoCardless is the other, for direct debit), and the only one with a documented way to give a buyer a new card. If you're on Flutterwave, Paystack or Mollie, assume a failed installment has hours or no time at all before it's final, and write your follow-up as the recovery itself rather than a reminder that runs alongside one. Flutterwave's three tries fit inside 90 minutes.

The gateway list is also where sellers outside the big markets get stuck before any of this matters. Ibrahim A., an internet marketer who gave systeme.io five stars on Capterra in March 2026, named it as his main downside: "Since some of the available options are not supported in my country, it creates challenges when trying to sell and manage my courses smoothly." Even a supported route can run on a slow clock. A two-star Trustpilot reviewer selling in the Netherlands and Belgium wrote in November 2025, about payments that had switched to SEPA direct debit, that "It is impossible to issue a refund until the SEPA direct debit is validated (if it gets validated), which takes between one and two weeks." systeme.io's reply traced that problem to its Stripe integration. Check how your own buyers will pay before you pick the row you're on.

A Payment plan price, with the count filled in

Open the order form in your funnel and choose Digital product as the offer type. Add the product, then click the plus icon to set its price plan and pick Create a new one. Choose the type Payment plan. The price plan article describes it as a subscription with one difference: you enter the total number of payments, for example 5 for five monthly payments. An open-ended membership is a Subscription instead, set up the same way without the count.

Settle the price before buyers see it. A Trustpilot reviewer, Gianni Sbilli, listed among his complaints in a review last updated May 22, 2024 that "you have to create payment plans from scratch if you want to change the price." The price plan article only describes creating a plan, not editing one, so I'd treat a price change as a new plan on the order form.

Before you save, check that your currency is one your gateway takes for recurring payments. Each gateway's help page lists it: Stripe supports subscriptions "in all 46 currencies", Mollie needs an EU merchant account, and Flutterwave needs a merchant account "registered in an African country".

Access at purchase, or after the first payment

The help article on subscription access sets out the default plainly: a buyer gets access "immediately after purchasing a subscription offer, even if the payment has not yet been received." The reason given is that some methods, PayPal and GoCardless among them, can take up to seven days to process.

The alternative is Grant access only after receiving the first payment. That article places it under your profile picture, then Settings, then Payment settings. The failed-payment article describes the same option as something you select on the payment page. The two pages don't agree on where it lives, so look in both places.

For a course sold in installments, the first payment is the one that matters most. If it fails under the default, the buyer has the course before you have any money. The processing delay the access article gives as the reason is about PayPal and GoCardless, so if your buyers pay by card, waiting for the first payment shouldn't keep them waiting long.

Stripe's retry schedule, the one clock you control

If you take cards through Stripe, the retry schedule is yours to choose. The failed-payment article points to your Stripe dashboard, under Settings, then Subscriptions and emails. Stripe's own documentation now places it under Billing, then Revenue recovery, then Retries. You have two options there:

• Smart Retries. Stripe picks the timing. Its documentation calls "8 tries within 2 weeks" the recommended default.
• A custom schedule. The failed-payment article gives 3, 5 and 7 days as an example.

One thing the two companies' pages leave unresolved: systeme.io says a payment plan gets "up to four (4) total charges", while Stripe's default allows eight. Neither page says which limit wins for a systeme.io subscription. Setting a custom schedule with three retries keeps the two documents in line, and it tells you exactly how many days you have to reach the buyer.

On every other gateway in the table, you can't change the clock. You can only work inside it.

A workflow on Subscription payment failed

In the Automations tab, click Workflows, then Create, and give it a name. Click Add a trigger and pick Subscription payment failed from the Sales group. The workflows article has you choose the specific asset for each trigger before clicking Create, so point it at the payment-plan offer.

Then add three actions. Send an email to the buyer saying what happened, that you'll send a link to update their card, and how long they have; that last part comes from your row in the table, not from systeme.io. Send email to specific address, with your own address, is the action that makes the recovery work, for the reason in the next section. And Add a tag, named something like installment-failed, so you can find these buyers later.

Workflows are inactive when you create them. Open the three-dot menu in the list and click Activate. The workflows article also notes that workflows don't act on past events, so a payment that failed before activation won't start it.

The card-update link goes out by hand

For Stripe payments, the card-update article sets out a manual route. Go to Sales, then Transactions, filter by the buyer's email, open their record, and scroll to Subscriptions. Click the three dots, then Change credit card details. Copy the address of the page that opens and send it to the buyer.

That's why the workflow emails you. The update link is made one buyer at a time, by hand, so no automated email can carry it. The workflow's real job is to tell you within minutes, so that you can send the link while the retries are still running.

The failed-payment article doesn't say whether saving a new card immediately settles the installment that already failed, or only changes what the next retry uses. Stripe's documentation says a retry tries the subscription's default payment method first. Write your email so that it doesn't promise the charge will go through the moment the card is updated.

PayPal buyers can't swap their payment method on an existing subscription. The card-update article says they "must cancel their current plan and start a new subscription". For a payment plan, that means sending them back to the order form. Decide in advance what a restarted plan should cost someone who has already paid two installments, because systeme.io's pages don't cover this case.

When the retries run out

If every retry fails, systeme.io says the subscription is canceled and access to the course is suspended. You don't have to build that part.

What you can add is the message. A second workflow with the trigger Sale canceled can send an email explaining what happened and how to come back. The workflows article says that trigger fires "When a subscription is canceled or a one-time payment is refunded", so point it at the payment-plan offer and nothing else. I've used a workflow here because the workflows article lists both triggers; the rules article doesn't print its full trigger list.

If you'd rather stop a plan yourself, go to Sales, then Subscriptions. Unsubscribe when the subscription period ends keeps access until the next payment date. Cancel now removes it the same day.

The alert fits Free; the goodbye email needs Startup

The failed-payment workflow fits Free on its own, using Free's one workflow and one tag. The cancellation message is a second workflow, and Free stops at one. The tag can run out too: if a lead magnet already uses Free's single tag, the installment-failed tag is a second.

Think about what the cancellation email is worth to you. A buyer three installments into a five-payment course who loses access with no word from you is the buyer who files a dispute or writes a review. A short note saying what happened and how to come back is the cheapest recovery you'll send, and it's the one Free can't hold next to the alert. If you sell installments at all, that's the case for Startup: 5 workflows and 10 tags, at $17 a month or $170 for a year paid up front, about $14.17 a month. Switch to Startup when you add the cancellation workflow.

If you only run one small payment plan and know every buyer by name, the alert on Free is enough, and you can write the goodbye yourself. Startup also leaves room if the plan sits next to a lead magnet or a tripwire.

When to skip this setup

If your installments are small and your buyers are people you speak to every week, as in a coaching program, a direct message may recover a failed payment faster than any workflow. In that case the alert to yourself is the only part of the workflow you need. And if you sell through a creator store rather than a funnel order form, check before you rely on the trigger. systeme.io's public roadmap carries a request titled "Enable Creator stores automation/workflow triggers" for New Sale, Sale Canceled and Subscription Payment Failed, which suggests store sales don't fire them yet.

FAQ

How many times does systeme.io retry a failed installment? systeme.io's help center says up to four charges in total for a payment plan. For cards, the timing follows your Stripe settings, and Stripe's own default allows more tries. Setting a custom schedule in Stripe makes the number yours.

Does the buyer keep access while the retries run? Access is granted at purchase by default, so the buyer keeps it while the retries run. If every retry fails, the subscription is canceled and access is suspended. How long that takes depends on the gateway, from Flutterwave's three retries inside 90 minutes to whatever schedule you set in Stripe or GoCardless. That window is all the time your recovery email has to work.

Can systeme.io email the card-update link automatically? No such route is documented. The card-update article has you copy the link from the buyer's record and send it yourself, and PayPal buyers have to start a new subscription instead.

Can I change the price of a payment plan after launch? The help center doesn't describe editing one. Its price plan article only covers creating a plan, so I'd plan on adding a new price plan to the order form for new buyers.

Which gateway gives a buyer the most time after a failed installment? Stripe or GoCardless, because you set the schedule there. Flutterwave's three retries fit inside 90 minutes, and Mollie and Paystack don't retry.

Can a PayPal buyer switch to a card mid-plan? Not on the existing subscription. systeme.io says PayPal buyers must cancel and start a new subscription, so decide what a restarted plan costs before it happens.