#maxime_best-practices

1 messages · Page 1 of 1 (latest)

wide spireBOT
languid saffronBOT
#

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.

wide spireBOT
#

👋 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/1243222249012465664

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

zinc talon
#

Recommend waiting until the customer decides to pay to create the sub

#

Can't think of a reason to create a sub and just pause it immediately

icy bear
#

Thanks that's what I thought. I have been searching for guidelines/rules on this in your doc to forward for people in charge of this but couldn't find anything. Do you have any idea if this is written somewhere?

zinc talon
#

If what is written somewhere?

#

We have docs on pausing subs

#

We really only recommend doing that in specific cases

icy bear
zinc talon
#

Kind of

icy bear
#

I'm trying to make a case that we should at work delay the registration of the user and subscription until the user decides to pay. Because we used to have a trial and create the customer as soon as he was logging in our app (from our API, so totally transparent) and now that they're looking at removing the trial, keeping the same flow would be nice but it's not possible ofc as the user has no payment and it's therefore not possible to create the subscription (at least not without a trial, which is the whole point). So there's a way to work around that by creating the subscription with a 1 day trial and the second after, remove the 1 day trial. That'd be quick to implement but that's really hacky.

I'm trying to convince everyone not to do that and I need arguments.

For context, if that helps

zinc talon
#

Yeah to me you presented good arguments right there 😃

#

It's not great to have hacky code like that

#

Our recommended subscription flows create subscription as soon as it's needed

icy bear
zinc talon
#

It doesn't say it explicitly

icy bear
#

Because while those are good devs argument... It's just very light to present to people above who see a quick way of keeping the same workflow

zinc talon
#

But if you read the recommended integration guide I sent that's what it's doing

icy bear
#

I did read it

#

But yeah it doesn't say explicitely "don't create customer/subscription early" ⚠️

zinc talon
#

yep

icy bear
#

So yeah that's gonna be hard on my side. I thought I read somewhere in TOS or docs that Stripe was asking not to use Stripe to manage people until there's an intent of paying

#

But I cannot find anything 😦

zinc talon
#

Yeah I can't think of a doc that explicitly says that

#

It just doesn't make much sense to create a sub and pause it immediately

#

But I get that this is a decision that's out of your hands

icy bear
#

Well anyway, thanks for your help 🙂 you can close this thread