#snackdex
tall quiverBOT
Hello! We'll be with you shortly. 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.
molten canopy
👋 Can you share more context on this use case? You likely don't have to use schedules for this if you plan on charging the customer for renewals on the new April 15 date going forward/after the first change
tame plinth
yes. sorry was just making sure i had everything listed out:
we want to charge members on a quarterly basis with a yearly commitment. when we charge the customer we always want to charge them 15 days before the agreed on start date.
example:
today is may 1st and the customer agrees on a start date of may 30th, and they purchase it today on may 1st.
3 months from now they get charged on august 15th. they are still an active subscriber until august 30th.
3 months from then they get charged on nov 15th. they are still an active subscriber until nov 30th
3 months from then they get charged on feb 15th. they are still an active subscriber until the end of feb
molten canopy
Gotcha, sorry for the delay
tame plinth
it's ok. i love the help you guys give 🙂
molten canopy
No, I don't think this is a use case for schedules due to the differences between the active window and the billing cycles
tame plinth
ah ok. could you explain what field i have to pass for the subscription for that? i wasn't able to figure it out
molten canopy
There's no specific field for that kind of flow. I assume on 8/15, 11/15, and 2/15, you want the customer to be charged automatically vs. having until 8/30, 11/30, and 2/28 (or 29) to pay?
tame plinth
correct so they get charged automatically on the 15th
i was thinking that i set the billing_cycle_anchor to the 15th
molten canopy
You could do that but the tricky part will be handling what happens if the automatic charge on the 15th fails. When an automatic charge fails, we'll move the subscription from active to past_due. Is that okay?
tame plinth
yes that is the tricky part. i'm okay if it turns into past_due so long as i can provide a way to charge the customer?
that's the part that i wasn't sure of...like do i send them an invoice where they can pay for it? or do they just update the card information and it gets charged automatically 👀
i know i can share a payment link...but we're soley on react native
molten canopy
We'll retry the charge automatically based on your retry rules. You could also toggle a Dashboard setting to send customers emails when their payments fail and link to a Stripe-hosted page where they can update their card details
tame plinth
is there anyway we could do it with the payment sheet in react native?
molten canopy
You should be able to pull up the PaymentIntent for the Subscription's latest invoice and use that PaymentIntent's client secret to render the payment sheet
tame plinth
oh sweet i didn't think that would work!
one last question, i think...for the quarterly subscription with a year commitment i have to set the interval to a month and the interval count to 3 on the price right? and then manage the whole "year commitment" logic outside of stripe?
molten canopy
yep!
tame plinth
awesome!