Recurring payments mean one of two things: an invoice that sends itself each month, or a saved card that is charged on a schedule. Pick the invoice for new or variable clients, the saved card for stable ones, and plan for the month a card fails.
A retainer you bill by hand is a recurring chore
The point of a retainer is predictable income. In practice many owners get a predictable monthly task: remember to invoice, send it, wait, follow up, wait again. The money is recurring only if the billing is too.
It also costs time in a way people underestimate. In a 2026 survey of 397 freelancers reported by ContentGrip, admin and paperwork took about 204 hours a year, and 54% waited more than a week to be paid after sending an invoice. Every month you create and chase a retainer invoice by hand adds to both numbers.
Two different things people call recurring
Recurring invoicing means the system creates and sends an invoice on a schedule. The client still pays each one. It removes "remember to invoice" and leaves "client forgets to pay" in place.
Automatic charging means the client authorizes a payment method once, and the system charges it on schedule. This is the hands-off version.
Stripe draws the same line. In its subscriptions documentation, a subscription can use charge_automatically, where Stripe charges the payment method on file, or send_invoice, where it emails the customer a link to an invoice with a due date. The first is automatic charging. The second is recurring invoicing.
A person working at a laptop in a calm workspace, setting up scheduled billing
Which one to use for which client
Written by
Delivvo Team
Delivvo runs the client cycle for service businesses: inquiry, quote, contract, deposit and delivery. Payments go straight to your own account.
The first invoice feels bigger than it is. This post lists what every invoice needs, how to set the due date and payment terms, why a signed agreement should sit behind it, and how to turn the first one into a template you reuse.
Wave, Zoho Invoice and Invoice Ninja all send invoices for $0, but each charges you somewhere else. This post compares the caps, the card fees and the branding limits using each vendor's own pricing page, then shows where an all-in-one client tool fits.
Taking a card in person no longer needs a terminal. This post compares Square, Stripe and SumUp on in-person rates, hardware and payouts, says which suits an occasional seller or a full point of sale, and covers what to use for work that is paid by invoice.
8 min read
Your inquiry link is free.
Free plan. No card needed.
Blog
Guides for service businesses, from the first inquiry to the final payment. Written by the team behind Delivvo.
Use automatic charging when the engagement is stable, the amount is predictable and the client is happy to set it and forget it. Monthly maintenance, ongoing support and subscription-style services fit well. The client authorizes once and each cycle runs.
Use recurring invoicing when the amount changes month to month, when the client's finance team has to approve every payment against an invoice, or when the relationship is new and the client is not ready to leave a card on file.
A rule that works: start new retainers on recurring invoices to build trust, then offer automatic charging to clients who have paid on time for several months. Our guide to recurring invoices for retainers covers the invoice side in more detail.
What to check before you promise automatic billing
You do not need billing software built for large subscription companies. You need three things.
First, a gateway that supports saved payment methods. Stripe's page on saving a payment method to charge it later is the reference for how that works on Stripe. Other gateways differ, and some do not allow charging a saved card without the client present, so confirm before you offer it.
Second, a clear moment of authorization. The client must knowingly agree to be charged on a schedule. Put the amount, the interval and how to cancel in plain words, and keep the record. A client who understood and agreed rarely disputes a charge later.
Third, a schedule and an end. Decide the interval (weekly, monthly, quarterly) and whether it stops after a fixed number of cycles, on an end date, or when someone cancels. Set it once and write it into the agreement.
If the work has a defined end, a payment schedule may suit better than open-ended billing. Splitting a fixed fee into milestones is covered in how to structure milestone payments.
Plan for the failed card
Cards fail. They expire, get replaced after fraud, hit a limit or get declined for reasons nobody explains. If you set up automatic charging and ignore failure, you will eventually do a month of work and not be paid for it.
Stripe's documentation on automatic payment retries gives a useful baseline. Smart Retries chooses retry times for failed subscription and invoice payments, and the recommended default is 8 tries within 2 weeks. Retries stop in some cases: when the issuer returns a hard decline such as a lost or stolen card, a retry only runs after a new payment method is added. Stripe also notes that the invoice.payment_failed event fires on each failure, so you can notify the client.
Stripe's page on how cards work adds one more piece. Stripe tries to update saved card details automatically when a bank issues a replacement card, which reduces the number of failures, but support varies by country and you cannot tell in advance which cards will update.
From that, build a failure plan with three parts:
A retry rule, so one decline does not mean a lost month.
A polite message to the client with a link to update the card, sent after the first failure and not after the third.
A manual path. If the saved card keeps failing, the client can pay that cycle by invoice, so work does not stop over a payment problem.
Keep the client relationship intact
Automation should make the client's life easier, not make them feel trapped.
Make cancellation easy and visible. A client who knows they can stop at any time is more likely to stay.
Send a reminder before larger charges. A retainer at a few hundred a month does not need one every cycle. A charge of a few thousand does.
Show what the client got that month. A short summary in the portal or an update email keeps recurring billing from looking like a charge for nothing. The fastest way to a cancellation is an automatic payment in a month when the client cannot remember what you did.
Invoices or payment links for recurring work
A payment link is not the same thing as a recurring invoice. Stripe's page on Payment Links compares the two. Invoices go to a specific customer, can be duplicated but not reused, support partial payments and payment plans, and can charge a payment method on file. Payment links are reusable by anyone who has the link and suit selling a product or a subscription to many people.
For a retainer with one named client, an invoice is the better tool. For a standard monthly plan you sell to many buyers, a payment link for a subscription can fit.
A plan to start this month
Confirm what your gateway supports for saved cards and recurring charges.
For a stable, trusted retainer, set up automatic charging with a written authorization and a defined schedule.
For newer or variable work, set up recurring invoices so the invoice builds itself.
Write down your failed-payment steps now, before the first decline.
Check how much the gateway costs per charge. Our post on the true cost of payment processing fees shows how small percentages add up on monthly charges.
How Delivvo handles recurring billing for retainers
Delivvo creates and sends the retainer invoice on schedule and chases it for you, so the monthly task disappears even if your gateway does not charge cards automatically.
Set up a recurring invoice for the client: the amount, the interval and the start date. The invoice is created and sent on the schedule, with a sequential number in your format.
The client opens the invoice from a link and pays through your own gateway. Delivvo supports Stripe, PayPal, Tap, MyFatoorah, Moyasar, Telr, PayTabs, N-Genius and Checkout.com. Delivvo takes 0% and is never the merchant.
If the invoice goes unpaid, a late-payment rule sends reminders at 7, 14 and 30 days and stops as soon as the invoice is paid.
For a fixed fee, use a payment schedule instead. A schedule can split one fee into up to 12 payments with their own due dates.
The client sees the money line, the invoice history and the work files in the same portal, so each charge arrives next to the proof of what was delivered.
The result is that a retainer client gets the same clean invoice on the same day each cycle, with the same payment link, and you spend no time rebuilding it. When the retainer ends, you stop the schedule in one place and the invoice history stays on the project for your records. Whether a saved card is charged without the client present depends on your gateway, so check that with the gateway before you promise it. See how it works on the recurring invoices page.
FAQ
What is the difference between recurring invoices and automatic payments?
A recurring invoice is created and sent on a schedule, and the client pays each one. Automatic payment charges a saved card on a schedule without the client acting. The first keeps the client in control. The second is hands-off.
Do I need a special gateway for recurring card payments?
You need one that supports saving a payment method and charging it later. Stripe does. Check your own gateway's documentation before you offer automatic billing to a client.
What happens when a recurring card payment fails?
It depends on your settings. On Stripe, Smart Retries retries on its own schedule, with a recommended default of 8 tries in 2 weeks, but a hard decline needs a new card. Notify the client with a link to update their details.
Should I get written permission to charge a client automatically?
Yes. Write down the amount, the interval and the cancellation steps, and keep the client's agreement. It protects both of you.
Can I use a payment link for a monthly retainer?
You can, but an invoice usually suits a single named client better, because invoices support partial payments and payment plans and are tied to one customer.
Delivvo runs the whole client cycle for service businesses, from the first inquiry to the quote, contract, deposit, invoice and delivery, so retainer billing sends itself and late payments get chased without you. Clients pay you directly through your own gateway, and Delivvo takes 0%. Start free
