#dominik_api

1 messages · Page 1 of 1 (latest)

nova needleBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1444973154140426281

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

proud bluff
#

Hello,

I am about to create a product which I want users to get as a trial or sort of "test version" while already having an active subscription. Since the subscription status is on the subscription level and you can not have a subscription with multiple statusses (obviously), I wonder what the best practice is to let a user test a specific feature while having already a subscription that is active.

Idea is that the user has already a product subscribed (not in a trialing subscription) and then can add a specific "addon" product to his subscription which is in the beginning a trial and free for the user and then later on after the "trial" is over, it gets paid.

sand drum
#

👋 happy to help

#

You mean the same Subscription, have a an active product and a trial for another one ?

proud bluff
sand drum
#

There is no native feature like this, the options I'm seeing are:

  1. You track the trial period in your integration, you update the Subscription to use the new product once the trial is ended (You use Subscription Scheduler and you schedule the update of the new product at the date the trial should end)
#
  1. You add a freemium price, then you schedule an update to a paid price of the product
nova needleBOT
proud bluff
#

Yeah I already thought about this, this just gets really messy with scheduled downgrades for example

I thought there might be a better handling

digital laurel
#

hey there 👋 that's understandable, but we don't have any specific recommended best practice for this use case

overall, when provisioning access to your subscription service, we recommend relying on subscription.status and tracking the Product IDs: https://docs.stripe.com/billing/subscriptions/build-subscriptions?platform=web&ui=elements#provision-access

this would be a little more complex in your case, since you'd need to rely on more than just the status

another option would be to use separate subscriptions, so that the trialling one has its own status, but I can see why your current approach might be preferable - ultimately it's for you to choose

proud bluff
digital laurel
#

at the moment, a workaround would be needed to achieve this

one option, as well as those @sand drum mentioned above, would be to create a separate subscription for the trial, then manually move the item over to the "main" subscription at the end of the trial period

proud bluff