Before the Card Comes Out: Subscription UX That Respects the UK’s New Consumer Rules

Subscriptions have a habit of looking simple from the inside. You build a trial, connect Stripe or RevenueCat, add a paywall, and move on. From the customer’s side, though, it’s a sequence of small trust moments: What will I be charged? When? Can I get out? What happens if I forget?

In 2026, UK founders have more reason than ever to design those moments properly. The Digital Markets, Competition and Consumers Act (DMCCA) and the CMA’s continued interest in subscription practices have pushed clarity, reminders and easy exit routes up the product agenda. But the useful way to read all this is not as legal paperwork bolted onto your app. It’s as a set of UX prompts. Get them right and you tend to get fewer refund requests, fewer angry support tickets and a subscription product people are less embarrassed to recommend.

Start before the payment screen

A lot of subscription confusion starts one step too late. By the time someone is typing card details, they’ve already made an emotional commitment. If the important information only appears after that, you’re relying on momentum rather than informed consent.

So put the commercial facts in front of the button, not in a footnote behind it. That means the price, the billing frequency, the minimum term if there is one, and a plain-English description of what happens when the trial ends. If VAT applies, show the total the customer will actually pay. If there’s a one-off fee, show it. If the trial converts automatically, say so next to the trial length — not in a collapsed “terms” accordion that nobody opens on a bus.

A useful test is whether someone could screenshot the payment panel and explain the deal to a friend without scrolling. “Free for 14 days, then £7.99 a month from 24 November. Cancel anytime in Account > Subscription” does more work than three lines of small print and a tick box.

The reminder that earns its keep

Reminder notices are often treated as a compliance chore. That’s a missed opportunity. A well-timed reminder is a genuine product feature: it stops accidental charges, reduces disputes and gives people a reason to stay because they’re choosing to, not because they forgot to leave.

Before a trial converts or a renewal is taken, send a clear notice with the amount, the date, and the easiest way to cancel. Keep it short. Put the cancellation route in the message itself, not three menus away. If you have an in-app subscription centre, link straight to it. If you’re sending email, make sure it comes from a recognisable address and doesn’t look like marketing.

Timing matters more than volume. A reminder three days before a trial ends is usually more useful than one that arrives as the charge lands. For annual plans, a notice a week or two before renewal gives people room to decide. Test the schedule, but don’t test whether to disclose. That’s not an experiment; it’s a trust decision.

Cooling-off shouldn’t feel like a trapdoor

Many UK distance contracts come with a cancellation right, often 14 days, and subscription apps need to think about how that applies to their model. This is where product teams sometimes get twitchy: they worry that making cancellation visible will encourage it. In practice, a clear cooling-off journey tends to reduce the messy outcomes — chargebacks, complaints and support queues — that come from people feeling stitched up.

Show people how to cancel during the cooling-off period without making them email a human or post a letter. Explain what they’ll get back and when. If digital content or immediate access affects the position, say so clearly before sign-up rather than unveiling it at the cancellation screen. And if someone does cancel, confirm it in writing. A clean confirmation email is not a legal nicety; it’s the end of the story, which is exactly what a worried customer wants.

Cancellation should be as easy as sign-up

This is the one UK founders keep underestimating. If signing up takes two taps, cancelling should not require a phone call during office hours, a live chat queue and a “retention specialist” called Kyle.

Put a cancel option in the account area. Make it findable from the subscription screen, the help centre and the reminder email. If you want to offer a pause, a downgrade or a discount, offer it after the cancellation request has been acknowledged — not as a barrier before it. Let people finish the job.

It also helps to be specific about what happens next. Does access continue until the end of the billing period? Will the app switch to a free tier? Is there a refund? Vague endings create support tickets; clear endings create trust.

Measure the boring bits

Compliance work becomes much easier to prioritise when you treat it as product analytics. Track where people drop out of the trial, how many open the reminder, how long cancellation takes and what they ask support afterwards. Read the free-text reasons. If lots of people say “I didn’t realise it would charge”, that’s not a customer education problem. It’s a design problem.

Run A/B tests on wording, timing and layout — never on whether key information is shown. A clearer price panel or a better-timed reminder is fair game. Hiding the renewal date is not “optimisation”; it’s borrowing trouble.

A small pre-launch checklist

Before you ship, check four things: can a customer see the full deal before entering card details; is there a reminder schedule for trial conversion and renewal; can someone cancel in the app without contacting Support; and does your team have a written answer for refunds, cooling-off and access after cancellation?

None of that is glamorous. But subscription UX rarely is. The apps that get it right feel calm, obvious and slightly boring in the best possible way. In the UK’s current climate, that’s not just good compliance. It’s good product design — and it tends to be the version customers keep paying for.