Hey @marin!
RevenueCat can definitely help with this type of setup, however it’ll also take some custom work on your own server to keep track of the content and when the consumable purchases should expire.
You’ll want to use consumable products so that you can purchase several of the same products, however RevenueCat doesn’t support setting expirations for consumable products. The good news though is that RevenueCat can validate your transactions and send events in a consistent format to consume from your server.
In this case, I’d recommend listening to webhooks, and watching for initial purchase events. When you receive an event, store the product, user, and expected expiration date (based on your own logic) in your database. When fetching content for your app, you could then only return content that is still considered valid.
Of course, this is describing it pretty simply, but let me know if that makes sense!