#danielncr.

1 messages · Page 1 of 1 (latest)

rustic kilnBOT
#

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.

rotund shell
#

How can I help?

lament tide
#

Hi I'm migrating subscriptions (donations) from a customer's previous system. Some of their memberships are paid far in advance. Our system uses the presense of an active Subscription to tell if someone is a member or not.

#

I tried to create Subscriptions with a future date using billing_cycle_anchor and that works fine if the next payment date is within the next year. But it won't let me me create them if that date is more than a year away.

#

Through a previous question your collegue suggested I use a Subscription Schedule. Which I just tried using and I created one successfully. But the problem is that the Subscription itself won't exist/be active until that future date. And I need the Subscription to be active now to show they are a member now.

#

So, I guess maybe I need to do a free trial? Create a subscription but make it not require a payment?

rotund shell
#

yeah or maybe you can create a backdated subscription? 🤔

lament tide
#

As long as I can set proration_behavior=none?

rotund shell
#

I believe so

#

Have you tried backdating the subscription already?

lament tide
#

Trying right now.

#

I guess not. I still get the error about the billing cycle anchor being too far away:

#

stripe.error.InvalidRequestError: Request req_8JGh7dXBLc5dlz: billing_cycle_anchor cannot be later than next natural billing date (1732225169) for plan

rotund shell
#

you don't need to set a billing cycle anchor though right?

Specifying backdate_start_date for a yearly subscription should take care of it

lament tide
#

I need to tell it at what date to start billing though and that needs to be with billing cycle anchor, right?

#

For this example I need the first charge for the Subscription to be 2024-11-30 00:30:00 (1732948200)

#

But I need the Subscription to be active starting as soon as I create the Subscription.

rotund shell
#

you sent backdate_start_date: "1700516369" meaning 2023-11-20 21:39:29 UTC

#

your billing cycle anchor is 2024-11-30 06:30:00

lament tide
#

I set it to yesterday, yeah.

#

But it failed.

rustic kilnBOT
rotund shell
#

for a yearly product, that doesn't make sense though right?

#

like what happens to the 10 days difference?

lament tide
#

The customer has already paid up through 2024-11-30. They weren't on a strict year with their previous system I guess, but they will be with us.

#

And we can't charge them before that date.

rotund shell
#

For the first price, you can subscribe them to $0 price

lament tide
#

Could that be abbreviated to just the free trial part and the third phase? Why do I need the backdated one?

rotund shell
#

you need the subscription to exist right?

lament tide
#

yes, starting from whenever I finish this import, so the free trial should cover that, no?

rotund shell
#

I mean yeah that should work too

lament tide
#

I've got some of these that stretch out for a couple of years, but I can just extend that free trial phase for as long as necessary, right?

#

Is there a difference between a $0 phase and a free trial phase?

rotund shell
#

not really, but if you test it out you might find some edge cases.
I haven't tested it myself so can't say for sure

#

I've got some of these that stretch out for a couple of years, but I can just extend that free trial phase for as long as necessary, right?
I'd think so yeah

lament tide
#

okay, this sounds like a good approach. Thanks! I'll try it out and come back here if I run into anything.