A purchase for one study should not silently become a subscription to the whole account. Model what the customer buys before deciding how a payment event changes access.
One-time resource access and recurring account access have different lifecycle rules. Separating them makes refunds, repeated purchases, support repairs, and customer explanations much easier to reason about.
Define the purchased object and its rights
List the resource, owner, included actions, limits, duration if any, and transfer policy. A paid study might permit publishing and collecting responses for that study without changing the customer's rights over every other study.
Keep the account identity separate from the entitlement. Users still need permission to the resource even when payment exists, and a payment reference must map to the intended study rather than whichever draft is currently open in the browser.
Test a fictional second-study purchase
Suppose a founder has one free study and two unpaid drafts. They purchase access to draft B. The trusted purchase record should grant access to B under the defined policy while draft C remains unpaid.
Test returning from checkout in another tab, changing the draft identifier in a request, repeated payment notifications, a failed purchase, a refund, and a study deleted before the update arrives. Verify the actual entitlement records and operations, not just the paid badge.
Add an account with a separate subscription for another capability. Cancelling that subscription should not revoke a one-time study entitlement unless the commercial policy explicitly links them. Likewise, purchasing a study should not revive a cancelled account-wide plan.
Keep support and customer wording aligned
Show what was bought, the affected study, and what remains available. Avoid a generic subscription screen if no recurring agreement exists. Support should be able to locate a purchase by a safe reference and explain the resulting scope without reading private responses.
Refund and transfer behaviour need an explicit rule. If a study has already collected responses, distinguish access changes from retention and export rights. Seek appropriate review of customer-facing terms rather than letting an event handler invent the policy.
The tradeoff is resource-level clarity versus a more detailed entitlement model. One account-wide flag is easy to implement but cannot accurately represent several independently purchased studies. Use the smallest model that preserves the product's actual commercial promise.
The StackFlight case study documents a real product with a free first-study starting point and individually purchased additional studies. It demonstrates delivered workflow, not measured demand, revenue, or the outcome of the fictional tests above.
Questions about paid study access
Does a purchase have to create a subscription?
No. A one-time purchase can grant a scoped resource entitlement. Use the commercial model the product actually offers.
Should access follow the purchaser or the study owner?
Define that relationship explicitly, especially for teams or transfers. Payment alone does not resolve resource ownership.
What should the first acceptance test prove?
Purchase one of two unpaid drafts and confirm that only the intended study changes. Bring ambiguous refund or transfer cases to a paid-access review.