Playbook, online course
The second of three payments declined and the course stopped opening
A plan on a course is a fixed price split into parts, so a decline does not cancel anything. The balance is still owed, the content closes until it is paid, and the learner is stuck in the middle of a module wondering whether they have lost the whole thing. What they need first is the date the next attempt happens.
Why this is not the general answer
The handling pattern for failed payments holds across every trade. What follows is the part that does not.
- Nothing lapses. A subscription that fails eventually ends and the customer walks away owing nothing, while an instalment plan is a total that is still due, so the honest wording is about a payment outstanding rather than about a cancellation.
- There is no degraded state to fall into. A course either opens or it does not, so the moment access is withdrawn the learner has lost the entire product rather than some of its features, and the language has to reflect that.
- The card that declines is usually the personal one used months earlier and expired since, and the warning went to the personal address the buyer stopped reading once the welcome message had been dealt with.
- On a cohort the timing bites: an instalment failing in a week with a live session costs an event that cannot be attended twice, so the retry window matters more here than the amount does.
How it arrives
- my second payment failed and the course will not open
- how many days do i have before you close my access
- can i pay the rest of the plan off in one go
- i changed my card where do i update it
- do i lose my progress if a payment bounces
- i missed a payment can i still join the live call this week
What has to be indexed for this to work
| The instalment schedule and the day access changes | How many payments, on which dates, how many attempts are made after a decline, and the day the content closes. Every one of those is a fixed rule, and publishing them turns a frightened message into a learner who knows they have until Friday. |
|---|---|
| What happens to progress and to anything already earned | Whether progress is kept while access is closed, whether a certificate already issued survives, and what is restored when the balance is paid. The anxiety underneath the question is almost never about the money. |
| Where the payment method is updated, and by whom | The exact screen or link, and what a learner does if they no longer have access to the account that holds it. Where the plan was set up at checkout rather than inside an account, say so, because the learner will look for a settings page that does not exist. |
| Whether the balance can be settled early or rescheduled | If a learner can clear the remainder in one payment, or move a date once, publish it. A meaningful share of declines are timing problems rather than affordability problems, and both are solved by a sentence you already know the answer to. |
The reply
A payment plan is the full fee split into instalments rather than a subscription, so a decline does not cancel anything: the remaining balance is still due and access closes on the day set out in the plan terms rather than immediately [1]. Progress is not deleted when that happens, and what comes back when the balance is paid is described on the same page [2]. The card is updated through the link on that page. I cannot see your payment, retry it, or hold your access open, so if a live session falls inside this, leave your name, the email you enrolled with and which cohort you are in, and somebody will pick it up today.
It corrects the model in the first sentence, because a learner who thinks they have been cancelled behaves very differently from one who knows they owe a balance. The progress sentence goes early since that is the actual fear. And the handover invites the cohort detail, which is the only thing that makes one of these urgent.
Where it stops
The trigger. The visitor asks for access to be reopened, a payment retried, a date moved, or says a live session falls before they can fix the card.
I cannot retry a payment, reopen access or move a date. Leave your name, the email you enrolled with and whether you are in a cohort with a session coming up, and it goes to the team as it stands.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never say a payment has gone through, been retried or that access has been restored, because nothing here touches a payment.
- Never waive an instalment, extend a deadline or hold access open, since only somebody on the team can agree to that.
- Never explain why a card was declined, as that sits with the card issuer and is not visible on your side.
- Never tell a learner their progress is safe, or lost, at a point your own published terms do not describe.
Questions
- Is publishing the day access closes a bad idea?
- It is the single most useful thing on the page. A learner who knows the date fixes the card before it. A learner who does not know assumes the worst has already happened, stops trying, and either disputes the earlier payments or disappears owing the balance.
- Can it take a payment to sort this out immediately?
- No. It cannot take a payment, hold card details or send anybody to a checkout on your behalf. It can point at the page where the method is updated, and it should never ask for a card number in the conversation, whatever the learner offers.
- People say they will just dispute the charge. What should it do?
- Stop answering and hand over. A dispute threat is a commercial conversation with a deadline attached to it, and the last thing it needs is a cited quotation from the plan terms, which reads as an argument rather than as help.
Keep reading
- Everything for a online courseWhat is included, how long access lasts, refund and cooling off rights, and the honest limit that it cannot see a learner's own progress.
- Handling failed payments in generalThe reason usually sits with the card issuer and is invisible to you. The useless reply, the useful one, and why card details never belong in a chat.
- The reset worked and the course was still not thereTwo addresses, one purchase. Why resetting the password rarely helps when a course was bought at one email and is read at another.
- Delete everything, except the thing that proves I did itErase me and keep my certificate do not sit together. What a provider holds afterwards, and why lifetime access ends with the record.
- The request is nearly always captions, and the answer is per moduleMost accessibility requests here are about captions on older modules. What to publish about what is captioned and what is machine generated.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.