#Stone.D-subscriptions

1 messages ยท Page 1 of 1 (latest)

vernal frost
#

๐Ÿ‘‹ happy to help

#

When subscribing, what are the rules for upgrading from monthly to yearly when Prorations is enabled?
what do you mean by rules?

frigid kite
#

What's the rules about charge cycle and proration?

#

What's the rules about charging cycle and proration of new Subscription?

vernal frost
#

there is no rule I don't understand what do you mean by rule

#

you define how the change will be applied

frigid kite
#

For example, 1/8/2022 subscipted $10 monthly subscription A, 15/8/2022 change the subscription to $100 yearly 15/8/2022 subscription B.

In 15/8/2022, What's the starting Date of subscription B?
How to charge?

vernal frost
#

it really depends on what you want to do

#

if you describe to me what you want to happen I could guide you to how you implement that

frigid kite
#

Let me describe it in detail. On August 1st, I subscribed to a monthly package of $10, and its next billing cycle is September 1st; if I upgrade this subscription package to an annual package of $100 on August 15th. Excuse me, on August 15th, according to Stripe, when will the new annual package start? How is the balance not used up before the upgrade calculated into the new plan?

vernal frost
#

as I mentioned before there are multiple ways you could handle this

#

you could start the cycle on the 15th, or wait until the 1st of September or something totally different

#

it really depends on what your business model is

#

if you describe that, I would be able to help you figure out how to implement that

frigid kite
#

Ok, Our product model is a fixed model, such as: 1000 pictures/$5 per month

#

20000 pics / $50 yearly.

vernal frost
#

I mean what do you want to happen upon upgrade?

stable marsh
#

Hi there ๐Ÿ‘‹ jumping in as my teammate needs to step away soon. Our proration logic is dependent on the values that are provided when adjusting the Subscription and the exact changes being made. The bottom section of the above document explains the scenarios where payment is immediately attempted for a Subscription update. Outside of those scenarios, you have control over what happens to billing cycle anchor and whether an invoice is immediately generated or prorations are included in the next invoice.

#

If you would like to see first-hand how the changes that you intend to make will behave, then I recommend looking into our Test Clock functionality which allows you to create Subscriptions inside of a sandbox where you can advance time to quickly test future scenarios.
https://stripe.com/docs/billing/testing/test-clocks

frigid kite
#

I expect: Subscription start time August 1st after upgrade, billing: Immediately charged $100/12-$10/2 + $100,

stable marsh
#

I will need to conduct some tests to confirm whether that is possible, please bear with me while I do so.

frigid kite
#

Yes, I want to test it ,but i forget to get the portal link hosted in Stripe about upgrade or downgrade

stable marsh
#

I'm sorry, I'm not sure what you're trying to say with the last part of that statement.

frigid kite
#

That's some stuff.

#

Don't pay attention Last part.

stable marsh
#

This isn't easily achievable. Changing the billing frequency of the Subscription also forces the adjustment of the billing_cycle_anchor.

frigid kite
#

i see.

#

If set billing_cycle_anchor, how to charge ?

#

When to charge ?

stable marsh
#

When the billing_cycle_anchor is changed, it's changed to the current time and that is when the Subscription moves to the next period and attempts a payment.

frigid kite
#

Let me check it.

frigid kite
#

I don't understand that billing_cycle_anchor=now can be achive.

stable marsh
#

Sorry, is that a question?