#sabrina_api

1 messages ¡ Page 1 of 1 (latest)

clever barnBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1256239769168384000

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

hot carbon
solid ruin
#

Can we do the following:

  1. Create annual subscription on January 1. The next billing date is automatically set to January 1st.
  2. Pause the subscription on January 1
  3. Unpause the subscription on January 15th
  4. Change the subscription's billing cycle anchor to January 15th
  5. All future invoices will be changed on January 15th
hot carbon
#

Do you want a proration to be applied for the time paused?

solid ruin
#

No, I want to extend the subscription to account for the time paused.

hot carbon
#

Ah ok

#

So I think for the behavior you want, the easiest thing to do would be to add a trial to the subscription when you unpause it with a trial end date to be Jan 15th of the next year (in your above example)

#

that ensures the next time the sub is billed is jan 15th the next year and it will continue to be billed on jan 15th each year

solid ruin
#

How would that impact our trial metrics and MRR? In this example the subscription is paid at creation on January 1 and we'd like it to count towards MRR once the subscription is unpaused.

hot carbon
#

Not sure. We're not familiar with the dashboard metrics in here

#

We just help with api questions

solid ruin
#

Ok, so for subscription schedule using the current example, we would reset the billing anchor to be January 15th of the following year. Correct?

#

And alll future invoices would be on January 15th

hot carbon
#

Nah it would be slightly different. This is a more complicated approach. You'd create normal subscription recurring on Jan 1. When customer pauses, you create a subscription schedule from the subscription. When customer goes to unpause, you update the subscription schedule to end the current phase and start a new phase with the same price, which is recurring on the 15th

solid ruin
#

Like this?

  1. Create annual subscription on January 1 2024. The next billing date is automatically set to January 1 2024.
  2. Pause the subscription on January 1. Create a subscription schedule from the subscription.
  3. Unpause the subscription on January 15th
  4. Update the subscription schedule to end the current phase and start a new phase with the same price, which is recurring on the 15th
  5. All future invoices will be changed on January 15th 2025
#

I am confused about this part: subscription schedule from the subscription.

How can we create a subscription schedule if we do not know when the subscription will be unpaused?

hot carbon
#

You're just adding a schedule to the existing sub

#

Just calling that adds your current subscription as the only phase in the sub

solid ruin
#

Understood about adding a schedule but what dates are we using the the schedule if we are unaware of the the subscription will be unpaused.

hot carbon
#

You don't need to add dates

#

current phase will go indefinitely if you just run the above api request

#

Don't add dates until customer unpauses