Here's a phone call most subscription teams will recognise. A reader renewed last week, the payment went through, and they still can't get past the paywall. Meanwhile, somewhere else on the file, a reader who lapsed in the spring is happily reading everything.
Both problems have the same cause. The website and the subscription system each have their own idea of who's a subscriber, and nobody is making them agree.
This post is about fixing that: how to connect your website login and paywall to the subscription file so access follows the subscription, automatically.
Decide which system owns the answer
The first decision is the important one. One system has to be the source of truth for "is this person entitled to read this?", and for a publisher that should be the subscription system. It's where orders, payments, renewals, suspensions and cancellations already happen.
The website's job is to ask, not to decide. If the website keeps its own list of subscribers, edited by hand or by an import someone runs on Mondays, you've built two systems that will drift apart. Every renewal, cancellation and change of address then has to happen twice, and sooner or later one of them gets missed.
Ask live, or copy across?
There are two common ways to get the answer to the website.
A live lookup. When a reader logs in or hits a paywalled page, the website asks the subscription system, through an API, whether they're entitled. The answer is always current. The trade-off is that the website depends on the subscription system being available, so it's worth caching the answer for a short while and deciding what happens if the lookup fails.
A regular sync. The subscription system sends a file of entitlements to the website every night, or every hour. It's simpler to build, but there's always a gap. Renew at 9am and you may not get in until tomorrow, which is exactly the phone call we started with.
Either way, send the website only what it needs to make the decision: an identifier, the products the reader is entitled to and the end dates. It doesn't need home addresses, payment history or qualification answers. The ICO's guidance on data minimisation puts it plainly: you shouldn't hold more than you need for the purpose. A website with a copy of the whole subscriber file is also a much bigger problem if it's ever compromised.
Matching the web login to the subscriber
The fiddly bit is knowing that the person logging in is the person on the subscription.
Most sites match on email address, and it mostly works. Where it falls down:
- the subscription was taken in a work email, and the reader registers on the website with a personal one;
- someone else in the office placed the order, using their own email;
- the reader changes job, and their old email stops working.
A few habits help. Store the subscriber's account number on the web login once they've been matched, so the link doesn't depend on the email staying the same. Let readers link their login to a subscription themselves, using their account number and postcode, rather than ringing customer services. And when a match fails, flag it for someone to look at rather than quietly creating a new, unentitled web account. Otherwise you end up with the same person as two records, one paying and one locked out.
Corporate readers are different again. Access by IP range means nobody logs in at all, so the paywall needs to check the reader's IP address against the ranges on each organisation's licence. Those ranges need keeping up to date, as offices move and networks change.
Write the access rules down
The system can only follow rules someone has decided. Before you build anything, agree with your circulation and finance people what should happen in each case:
- Grace period. Does access stop the day a subscription expires, or do you allow a week or two while the renewal comes in? A short grace period saves a lot of calls from readers whose payment is in the post.
- Failed payments. If a direct debit or card payment fails, does access stop straight away or after a retry?
- Suspensions. A suspended order should probably suspend access too, but check that's what you want.
- Trials. Access for the trial period, then on or off depending on whether it converts.
- Print subscribers. Do print-only readers get the website or digital edition too? Whatever the answer, it should come from the product they bought, not from a list someone keeps.
- Bundles and multiple titles. Entitlement should be per product, so a reader who takes one title out of three gets that title only.
Cancellations and the 2027 rules
If you sell auto-renewing subscriptions to consumers, the new subscription rules matter here too. They're due to apply to contracts made from 1 January 2027, subject to Parliament approving the regulations, and the government has published guidance on the subscription contracts rules.
Two points touch the website directly. If a reader could sign up online, they must be able to end the subscription online, in a straightforward way. For most publishers that means a clearly labelled cancel button or form in the reader's account, and that button has to talk to the subscription system, not just send an email to the office. And ending a subscription stops future renewals, but the reader keeps what they've paid for. So the paywall should keep access open until the paid period ends, which it will if access follows the end date on the subscription.
Digital-only subscriptions have a specific rule about cooling-off once access starts. Our guide to the subscription rules goes through it, along with the end of contract notice you'll need to send. Business-to-business subscriptions are out of scope.
Keep the connection tight
The link between your website and your subscriber file is a door into personal data, so treat it like one. The ICO's guide to data security talks about "ensuring appropriate access controls are in place". For an integration, that means a separate key for each system that connects, limited to what that system needs, with every call logged so you can see who asked for what. If the website only needs to read entitlements, it shouldn't be able to change a subscription.
Test it with real cases
Before go-live, run through the awkward cases, not just the happy path. A reader who renews today. One who lapsed yesterday. A failed direct debit. A cancelled trial. A corporate reader on a new IP range. A reader with two email addresses. Check each one gets the access your rules say they should, and that it changes when the subscription changes.
Where we fit in
Avio, our subscription platform for larger publishers, has a read-only REST API for exactly this job. Your website or paywall can look up subscribers and their entitlements, and there's an IP lookup for organisation access. Keys are scoped, calls are rate limited and every call is logged. The licences, seats and IP ranges it reads are the ones your team manage on the corporate subscriptions screens.
In Adeptis, our all-in-one platform for smaller publishers, orders paid through Stripe on your public sites come into Adeptis for review, and approving one creates the contact, the subscription and the payment in one go.
If your paywall and your subscriber file have stopped agreeing, get in touch and we'll talk it through.