How to set up a payment plan for customers, step by step
A plan is three decisions and one page: what is due today, when the rest lands, and what the customer sees before they agree.
Before you set anything up, write one sentence
A payment plan only makes sense when there is a gap between the sale and the day the customer uses what they bought: a date held eighteen months out, a place on a programme that runs in the spring, a pass for a weekend that has not happened yet. That gap is the whole reason a schedule exists. If the customer walks away with the thing today, there is nothing to spread.
So the first step is a sentence rather than a tool. What am I selling, when is it used, and how many weeks sit in between. Every number that follows is arithmetic on that sentence, and the setup goes quickly once it is written down somewhere other than your head.
Step one: set the amount due today
The first payment does two jobs at once. It covers what you actually lose if the booking goes away: the date you stopped selling, the supplier you have already paid, the hours spent on a quote. And it tells you the person opposite you is serious, which is the part no reminder can do for you later.
Price it against those costs rather than a round percentage somebody quoted at you. Most operators land between a tenth and a third of the total. Much below that and a cancellation is yours to absorb; much above and you have not really spread anything, you have asked for most of the money with extra steps.
Decide in the same sitting whether that first payment is refundable and under what conditions. You will be asked, usually at the worst possible moment, and the answer should exist before the question does.
Step two: work the dates backwards from the day
Start at the day the customer uses what they bought and walk backwards. The last payment should clear before you commit money on their behalf, which means before final numbers go to the caterer, before the coach is booked, before the badges are printed. For events a week or two is the usual gap. A single day is not enough, because a card that fails needs somewhere to fail.
Then fill the middle. Take what is left after the first payment and divide it across however many dates fit comfortably in the gap: monthly for a long booking, every two weeks for a short one. Even amounts on predictable days are easier to honour than a clever schedule nobody can hold in their head.
A short gap needs fewer payments, not smaller ones. A booking taken six weeks before the date is a deposit and a balance. Fitting four payments into those six weeks is work for you and noise for them.
Step three: the page they agree to, and the weeks after
Before the customer agrees, one screen should carry the whole thing: every amount, every date, the card that will be charged on those dates, what happens if one of them does not go through, and who to write to. The point is that nothing in the plan gets discovered later. They agree once, at the point of booking, to a schedule they were able to read.
Keep the wording plain enough to check against a bank balance. Four hundred today, then three hundred on the first of each month until the fourteenth of June, is a sentence a customer can verify in ten seconds. A table of terms is not.
Then take the first payment and keep the card on file for the rest, through your own Stripe account, so the later charges run from the same place the deposit did. Nobody is advancing anybody money. The customer's own card is charged on the dates they agreed, and the funds land with you when the schedule says they do.
After that the setup is finished and the job turns into a weekly glance: what is due, what cleared, what needs a short note to a customer. That is a smaller job than the one it replaces, which was remembering. Set the plan up carefully on the day of the booking and most of what follows is waiting.