#aero_schedule-start

1 messages · Page 1 of 1 (latest)

flint basinBOT
#

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

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

solid coral
#

aero_schedule-start

#

@safe basin yeah what you want is impossible today

flint basinBOT
safe basin
#

And there is no way to set default_incomplete as the payment behavior on a schedule, either

#

there is no default_setting where I can specify that for the created subscription before it is created?

solid coral
#

You either create a SubscriptionSchedule with start_date in the future, in which case there's no Subscription, or you create one upfront but you have to "complete" it (pay the first Invoice) before turning it into a SubscriptionSchedule

#

To me it doesn;t make sense to want to make it incomplete in the future. Incomplete is more for the end customer to pay the first Invoice on session while on session

safe basin
#

the thing is that we want the user to approve the paymentintent

#

and get authorization for that subscription

#

subscriptions are created by 3rd parties (connected accounts) so we want the user to confirm the use of the payment method. so we create a separate payment intent for the first invoice

solid coral
#

that doesn't really make sense to me either 😓

#

Why create a separate PaymentIntent, which a subscription in the future?

safe basin
#

So this is the scenario:

  • User A sells subscriptions. They can create subscriptions in the app which might start in the future.
  • User B pays for subscriptions. However, User A might have created it by mistake.

We want users to confirm the first invoice, just as what happens with incomplete subscriptions, but for future schedules

#

If the subscription starts now, the default_incomplete gives the customer 24 hours to confirm

#

We want to collect a mandate before debiting for that subscription

#

The problem is that, for scheduled subcriptions, there is no equivalent of default_incomplete. The subscription becomes Active immediately when hitting the start date.

olive oriole
#

Hello! I'm taking over as @solid coral had to step away, give me a few minutes to catch up on the thread please 🙂

#

I understand you want to create a scheduled subscription such that on the start date its status is incomplete and transitions to active if the PaymentIntent is confirmed within 24 hours or incomplete_expired otherwise, is that correct?

safe basin
#

correct

#

just as if I went and created the subscription with default_incomplete manually on the start date

olive oriole
#

Unfortunately, that is not possible - default_incomplete is meant for immediate subscription creation where you want to collect payment details before activation while subscription schedules are meant for future subscriptions meaning the subscription isn't created until the start date. When that happens, the status is active unless there's no valid payment method.

#

Can you create a different flow to confirm the subscription with users before the start date?

safe basin
#

yeah althought that will be quite complicated

#

we will need to set our on scheduled checks to cancel schedules ahead of time

#

thanks anyway

#

wait...

#

how can I pay the invoice before the start date if there is no invoice yet?

#

I have a question, though. Is it possible to update the collection_method to charge automatically in the middle of a subscription?

#

The most important thing here is that the customer doesn't get automatically charged if the subscription is not authorized.

olive oriole
#

You cannot pay the invoice before the start date because it doesn't exist until the subscription is actually created on the start date. Some options:

  • Collect the payment method with a SetupIntent so you have permission to charge later.
  • Create a one-time charge now then create the subscription with a trial period to account for the pre-paid amount.
  • Apply a customer credit balance https://docs.stripe.com/invoicing/customer/balance
safe basin
#

Ok so then we would cancel the schedule if we don't get the setupintent in time

#

Great, makes sense

#

Thanks for your help

olive oriole
#

Yes! You're welcome 🙂