Systems and records
Subscription publishing entitlement data: which access rights change when a subscriber switches plans
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
When a subscriber changes plans, change only the entitlements that differ between the old and new plan, at the time the billing channel's rule sets: app store upgrades apply immediately, downgrades at the next renewal, and access continues through a payment grace period. Verify the result in entitlement records and access logs, not in the plan field or the agent's confirmation.
License terms
Subscription publishing
Key takeaways
- Plan, subscription status, entitlement and access grant are separate records, and agents fail when they conflate them.
- The purchase channel sets the effective time: app store downgrades wait for renewal while upgrades apply at once.
- Grace periods keep access; Google Play's account hold removes it; cancellations usually run to the end of the paid period.
- A gradable task states the starting state, event, expected entitlements, effective time and the records that prove the outcome.
- Grade both missing and extra access, and include counterexamples such as approved retention exceptions.
- Licensing subscriber histories needs a rights and privacy review; de-identification alone does not create the right.
A subscriber changed plans: which access rights should change, and when?
Change exactly the entitlements that differ between the old plan and the new one, at the moment the billing rule says the change takes effect. On the major app store platforms an upgrade applies immediately and a downgrade waits for the next renewal date, so a subscriber who downgrades keeps the higher tier's access until then.
That one sentence hides most of the work. An agent handling the change has to translate a plan into a set of entitlements, find the effective time, apply grants and removals in each system that enforces access, and then prove the end state from records rather than from its own confirmation message.
This page is a worked task case for subscription publishers, membership businesses and other specialist services whose product is access. It builds an entitlement transition and verification task set: starting states, events, expected end states and the evidence that shows whether the outcome was reached. The examples are illustrative and describe no real subscriber.
Plan, subscription status, entitlement and access grant are four different records
Keep four layers apart, because agents fail when they treat one as another. The plan or product is what the subscriber bought. The subscription status says whether billing is active, past due, paused or canceled. The entitlement is a feature the plan confers, such as the full archive, the puzzles app, premium newsletters or a number of gift articles each month. The access grant is what the paywall, app or newsletter platform actually lets the person do right now.
Stripe's entitlements feature models the third layer directly: features are attached to products, and when a customer's entitlements change Stripe sends an event whose payload carries the customer's full current entitlement summary. When a subscription is canceled, revoked features no longer appear in that summary, and the application is expected to disable them.
A subscription can be active while an entitlement has been removed, and an access grant can linger after the entitlement is gone if a downstream cache or a separately provisioned system was never updated. A verified task outcome therefore has to be checked at the access layer, not inferred from the plan name.
Which billing rule sets the effective time of the change?
The platform that collects payment usually decides when a plan change takes effect, so the agent must read the rule for the channel the subscriber bought through. A publisher that sells on the web, in the App Store and on Google Play can have three different correct answers for the same requested downgrade.
| Channel and change | When the new plan applies | What happens to the old entitlement | Record to check |
|---|---|---|---|
| App Store upgrade | Immediately | Replaced at once; Apple refunds the prorated amount of the original subscription | Server notification with subtype UPGRADE |
| App Store downgrade | At the next renewal date | Continues until renewal, then renews at the lower level | Server notification with subtype DOWNGRADE |
| App Store crossgrade | Immediately if same duration; at renewal if durations differ | Depends on the duration rule | Notification subtype and the auto-renew product |
| Google Play change with default time proration | Immediately | Remaining time credited by pushing the next billing date forward | Purchase record for the replacement |
| Google Play deferred change | At renewal | Old item keeps access until the end of the current billing cycle | Old item with auto renew off and an expiry time |
| Web billing on Stripe | When the subscription update or schedule phase applies | Proration items created by default; a mid-period downgrade produces a credit | Entitlement summary event and the invoice preview |
Failed payments, pauses and cancellations are plan changes too
Not every entitlement change starts with the subscriber choosing a new plan. Google Play's guidance says that during a configured grace period after a payment decline the user should keep access to subscription entitlements, and during the account hold that follows the user should not. Apple's GRACE_PERIOD notification subtype likewise tells developers to continue providing access during the grace period.
Pauses and cancellations need the same discipline. A canceled subscription that runs to the end of a paid period should lose access at that end, not at the moment the subscriber clicks cancel, unless the terms say otherwise. Stripe's documentation says pausing a subscription sends events, including an entitlement summary update, that an integration can use to revoke access, and that resuming sends events used to restore it.
Build these into the task set alongside upgrades and downgrades. They are where over-revocation, which locks out a paying customer, and under-revocation, which leaves premium content open, most often happen.
The entitlement transition and verification task set
Each row below is one task an agent should be able to complete and a reviewer should be able to verify. The plan names and features are illustrative; replace them with your own entitlement map before use, and keep the version of that map in every task.
| Task and starting state | Event | Expected entitlements afterward | Effective time | Verification evidence |
|---|---|---|---|---|
| T1: Digital-only, monthly, web | Upgrade to all-access | Digital plus archive, puzzles and premium newsletters | Immediately | Entitlement summary lists the added features; archive request succeeds |
| T2: All-access, annual, App Store | Downgrade to digital-only | Unchanged until renewal; then digital only | Next renewal date | DOWNGRADE notification; archive access denied only after renewal |
| T3: Digital-only, monthly, App Store | Crossgrade to digital-only annual | Unchanged features | Next renewal date, since durations differ | Notification and renewal record show the annual product |
| T4: All-access, web | Cancellation at period end | All features until the paid period ends; none after | End of the paid period | No features in the summary after that date; newsletter list removal logged |
| T5: All-access, Google Play | Renewal payment declined | All features during grace period; none during account hold | Decline date, then hold start | Subscription state history and access log across both windows |
| T6: Group plan, ten seats | Administrator removes one reader | That reader loses group features; other seats unchanged | As the group terms specify | Seat roster and the removed reader's access log |
| T7: Print and digital bundle | Switch to digital-only | Digital features unchanged; print delivery stops | Next delivery cutoff in the terms | Fulfillment stop record and unchanged digital access |
| T8: Digital-only with approved retention offer | Downgrade request plus support-approved archive trial | Archive kept for the approved trial period | Per the approval record | Approval in the support ticket; archive access ends when the trial ends |
| T9: Counterexample, all-access, web | Subscriber asks to downgrade but does not confirm | No change | None | No subscription update; entitlements identical before and after |
Fields every task packet needs before it can be graded
A task is gradable only if a reviewer can reconstruct the starting state, the rule and the expected end state from the packet alone. The fields below make that possible without exposing who the subscriber is.
At a glance
Fields every task packet needs before it can be graded
- Case boundary: the single subscriber account and the period the task covers.
- Pseudonymous subscriber ID that is stable across the billing platform, entitlement service and access logs.
- Plan before and after, with product IDs and the purchase channel.
- Entitlement map version: which features each plan conferred on the task date.
- Event log with timestamps: the request, platform notifications, subscription updates and renewals.
- Terms in force: the subscriber terms version that sets notice periods, delivery cutoffs and group seat rules.
- Approvals: any support or retention exception, who approved it and its expiry.
- Expected end state: the entitlement set and effective time, written before the agent runs.
- Verification queries: the entitlement summary and access log checks that prove the outcome.
- Label: whether the case is drawn from real records or is illustrative.
Illustrative worked case: an annual all-access subscriber downgrades mid-term
This case is illustrative. A subscriber bought an annual all-access plan through the App Store and, partway through the year, chooses digital-only in the same subscription group. The publisher's entitlement map says all-access confers the digital edition, the archive, the puzzles app and two premium newsletters, and digital-only confers the digital edition alone.
Linked evidence: the App Store sends a DID_CHANGE_RENEWAL_PREF notification with subtype DOWNGRADE, which Apple documents as taking effect at the next renewal date. The applicable rule is therefore that nothing changes today. The correct decision is to record the pending change, schedule removal of the archive, puzzles and newsletters for the renewal date, and leave access untouched.
Verified outcome: on the day after renewal, the entitlement record lists only the digital edition, an archive request in the access log is denied, and both newsletter platforms show the address removed from the premium lists. Two plausible wrong outcomes are worth grading explicitly: revoking everything on the day of the request, which locks out a customer who paid for the year, and changing the plan field without removing newsletter access, which a status check would miss.
Counterexample: the same subscriber contacts support before renewal and accepts a retention offer that keeps the archive for a limited trial. The approval record in the support ticket now governs the archive entitlement, and an agent that removes the archive at renewal is wrong even though it followed the platform rule.
Proving the outcome rather than trusting a status field or a final message
Grade the end state in the systems that enforce access. A subscription status of active, a plan field that reads digital-only or an agent message saying the change is complete are all claims; the entitlement summary, the access log and the newsletter list membership are evidence.
Grade both directions. The least privilege principle in NIST's glossary describes restricting access to the minimum necessary for assigned tasks, and the subscription version of that idea is that a subscriber should have exactly the entitlements the plan and any approved exception confer. Missing access and extra access are both failures, and a grader that checks only one of them will rate a careless agent as safe or a cautious one as broken.
Can a publisher license entitlement histories for AI work?
Possibly, but only after a rights and privacy review of the specific records. Subscriber accounts, payment events and reading logs are personal information in many jurisdictions, and platform agreements with app stores or billing providers can restrict how their data is used. Having access to the records, being permitted by privacy law to process them, owning them and holding contractual rights to license them are four separate questions, and de-identification alone does not answer the last one.
The task set above is also useful before any licensing decision: it is a test of whether the business's own records are complete enough to prove what each subscriber was entitled to on a given day. Counsel should review the specific facts; this page is general information, not legal advice.
Preparing subscription records for a licensing assessment
If entitlement histories, plan change logs and related support tickets look like a candidate dataset, the starting point with SourceX is a brief company assessment that asks for no upload. SourceX then handles rights review, contracting, preparation and delivery when a company licenses operating records to AI developers.
Data is delivered only once the business has approved scope and terms and signed, and SourceX may use, sublicense and distribute the de-identified dataset within the limits of that agreement. The de-identification itself is performed by SourceX through approved processing routes.
Frequently asked questions
Should a downgrade remove premium access immediately?
Usually not. On the App Store a downgrade takes effect at the next renewal date, and Google Play's deferred replacement keeps the old entitlement until the billing cycle ends. Web billing depends on how the subscription update or schedule is configured, so check the rule for the channel the subscriber bought through.
Does a subscriber keep access after a failed payment?
During a grace period, the platforms say yes: Google Play says users should keep access during a configured grace period, and Apple's grace period notification says to continue providing access. During Google Play's account hold that follows, access should be removed.
Is the subscription status enough to decide what a subscriber can read?
No. Status says whether billing is active; it does not list which features the plan confers or whether every system enforcing access was updated. Verify entitlements and access logs directly.
How do you test an agent that handles subscription plan changes?
Give it tasks with a written starting state, event, expected entitlement set and effective time, including counterexamples where nothing should change. Grade the end state in the entitlement and access records, checking both missing and extra access.
Can subscriber entitlement records be licensed for AI training?
Only after a rights and privacy review of the specific records, platform agreements and subscriber terms. Access to the data, privacy permission, ownership and licensing rights are separate questions, and de-identification alone does not create a right to license.
Sources
- Apple says an upgrade takes effect immediately with a prorated refund of the original subscription, a downgrade continues until the next renewal date, and a crossgrade starts immediately only when durations match. Source
- Apple's App Store Server Notifications subtype reference says downgrades take effect at the next renewal date, upgrades take effect immediately, and access should continue during a billing grace period. Source
- Google Play's subscription guide describes replacement modes, including immediate time proration by default and deferred replacement that keeps the old entitlement until renewal, and says users keep access during grace period but not during account hold. Source
- Stripe's entitlements documentation attaches features to products and sends an event carrying the customer's full current entitlement summary, from which revoked features disappear. Source
- Stripe's proration documentation says proration_behavior defaults to create_prorations and that a mid-period downgrade generates a credit. Source
- NIST's glossary defines least privilege as restricting users' access privileges to the minimum necessary to accomplish assigned tasks. Source
- Stripe says pausing a subscription sends events, including an entitlement summary update, that an integration can use to revoke access, and resuming sends events used to restore it. Source
See if your company qualifies
A short company assessment. No data uploads are needed.