---
title: "Automating Recurring Orders and Subscriptions"
description: "A recurring payment looks like solved revenue. In reality it is a process that fails quietly — and you lose most customers to a failed payment, not to a cancellation."
canonical: "https://interfase.sk/en/news/automating-recurring-orders-and-subscriptions"
lang: "en"
last_updated: "2026-11-20"
---

# Automating Recurring Orders and Subscriptions

> A recurring payment looks like solved revenue. In reality it is a process that fails quietly — and you lose most customers to a failed payment, not to a cancellation.

Published: 2026-11-20

- Most subscription customers are lost to a failed payment rather than a decision to leave — and that can be addressed with process.
- A mid-period change (upgrade, downgrade, pause) is the hardest part; decide it before somebody needs it.
- Making cancellation difficult does not save subscriptions, it moves the problem into chargebacks and reviews.
- Prices on existing subscriptions do not change quietly — a change needs notice and a way out.

A subscription looks like the ideal model. The customer sets up payment once and the revenue arrives by itself.

Then you look into why two hundred customers left in the last six months, and find that a hundred and forty of them did not leave — their card simply stopped working and nobody got in touch.

## A failed payment is a process, not an error

This is the most important part of the whole subject. Cards expire, banks change, funds run short. If the system cancels the subscription on the first failure, the company is losing customers who never wanted to go.

What works:

- **Retries with spacing** — not five times an hour, but days apart. A share of payments go through with no intervention at all.
- **A comprehensible message to the customer** with a direct link to update their payment details. Not "payment failed", but what happened and what to do.
- **A grace period** during which the service keeps running. Cutting access before the problem can be fixed is the fastest way to lose the customer for good.
- **A warning before the card expires**, so the problem never happens.

**Before focusing on acquiring new customers, it is worth looking at how many you lose this way.** It tends to be cheaper work with a bigger effect.

## Mid-period changes

A customer adds five licences halfway through the month. Or removes some. Or moves to a higher plan. Or asks to pause for three months.

This is technically the hardest part of subscriptions and it almost always gets addressed only when somebody needs it. Decide in advance:

- **How the difference is calculated** — pro rata for the rest of the period, or only from the next one?
- **What happens on a downgrade** — a refund, or a credit?
- **Does a pause exist**, and what happens to access and data during it?
- **When the change takes effect** — immediately, or from the next period?

The answers have to match across the system, the price list and the terms of business. A contradiction between them will surface reliably at the first complaint.

## Cancelling should not be a fight

The temptation to bury cancellation behind three steps and a phone call is understandable and short-sighted. A customer who has decided to leave will leave either way — the only difference is whether they do it quietly or through a chargeback and a public review.

What works better: **clear cancellation in a few steps**, with an optional question about the reason and an alternative where one makes sense — a pause instead of cancelling, a lower plan instead of leaving. Offer once, not four times.

And an important detail: cancellation should **take effect at the end of the paid period**, not immediately. Withdrawing access the customer has paid for is grounds for a justified complaint.

## Changing the price for existing customers

A quietly raised price on an automatic payment is the fastest route to lost trust and disputes with a bank.

The rule is simple: **give notice in advance** with a specific date, **state both the old and the new amount**, and **allow the customer to leave** before it takes effect. Companies fear this, but the loss from departures tends to be smaller than the damage from a sense that something happened behind their back.

## Invoicing and communication

Every payment comes with a document sent automatically — not on request. And every change of state (successful payment, failure, upcoming renewal, plan change) comes with a notification in reasonable measure; we described the principles in [notifications in a business application](/blog/notifikacie-v-podnikovej-aplikacii-email-sms-a-push).

As for the price on the document, the same rule applies as to any document: **the amount is stored with the invoice**, not recalculated from the live price list. We explain why in [database design](/blog/navrh-databazy-rozhodnutia-ktore-sa-vypomstia-po-dvoch-rokoch).

## What to measure

- **Share of failed payments** and how many are recovered.
- **Churn split** into voluntary and technical — they are two different problems.
- **Share of customers who paused** instead of cancelling.
- **Number of disputes and chargebacks** — a rising figure signals that communication is not working.

## Where to start

Look at failed payments over the last six months and count how many customers were lost without ever deciding to leave. That number tends to be surprising, and it makes clear what to fix first.

If you are working on this, [get in touch](/kontakt). We handle it as part of [custom development](/riesenia/vyvoj) — examples in our [case studies](/referencie).


---

Web version: https://interfase.sk/en/news/automating-recurring-orders-and-subscriptions
llms.txt: https://interfase.sk/llms.txt
