What happens when a QR subscription expires?

Providers handle lapse differently, and the difference matters enormously if you have codes in the wild.

The variation is not accidental. Keeping codes resolving costs the provider money whether or not you are paying, so how a provider behaves at lapse says what it thinks a printed code is worth — and that is a better signal than the price on the plan page.

Few providers switch a code off the moment a card fails, because switching off codes in the wild generates support tickets. The usual sequence is a failed payment, a few emails, a grace period of days or weeks, and then a change in behavior — often not a hard stop but a downgrade.

The important part is that the first symptom is rarely visible to you. The person who scans gets the error, so unless someone tells you, a code on a poster in a waiting room can be dead for weeks before anyone mentions it.

Before printing at scale, read what the terms say about lapse, and prefer a provider whose free tier keeps codes alive. Where possible, run the redirects on a domain you control so you can move providers without reprinting.

Three habits cover most of the risk: know which plan keeps codes resolving, keep the billing details current, and put the renewal date somewhere a person will actually see it. The last one sounds trivial and is the most common cause of an accidental lapse.

Reactivate the account if you can — codes usually resume instantly. If the provider is gone, the code cannot be rescued, and the only route is a new code with a redirect from the old destination page where you still control it.

Work out which codes are actually affected before you tell anyone. Most accounts hold dozens of codes and only a handful sit in public, and the ones on packaging or in a waiting room are the ones that cost money to fix. A short list of those, with a decision per code, is usually the whole recovery.

Expiry is not bad luck, it is a pricing model expressing itself. A subscription that has to keep charging to fund redirects will eventually stop serving codes for someone who stopped paying — the only question is whether that happens loudly, at the end of a plan you chose, or quietly, in the middle of a campaign.

The durable answer is structural rather than careful: a domain you own in front of the code, so a change of provider is a configuration change rather than a print run, and a plan chosen for what it does at the end rather than what it costs at the start.