#menkuichan_73425

1 messages · Page 1 of 1 (latest)

dusky radishBOT
#

Hello menkuichan_73425, 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.
menkuichan_73425, 2 days ago, 19 messages
menkuichan_73425, 3 days ago, 5 messages
menkuichan_73425, 3 days ago, 8 messages
menkui-subscription-draftinvoice, 5 days ago, 13 messages
menkuichan_73425, 5 days ago, 5 messages
menkuichan_73425, 5 days ago, 8 messages
and 1 more

thorn robin
dusky radishBOT
solemn ridge
#

So how it will work in my case?

  1. user created subscription on 1 april 2023 and was successfully charged
  2. next invoice will be 1 april 2024
  3. i need to change next billing date from april 2024 to november 2023
young imp
#

👋 taking over for my colleague. Let me catch up.

#

sorry for the delay, looking at this right now

#

to November 2023 or 2024?

solemn ridge
#

2023!
So it will be earlier than next invoice date.

young imp
#

would you mind sharing the subscription ID?

solemn ridge
#

sub_1MyibMGx60rNljHxGMnaN0Du

young imp
#

taking a look

#

do you want to keep the full initial amount paid, or do you want to calculate prorations?

solemn ridge
#

Full amount.

young imp
#

ok

#

with

  billing_cycle_anchor: "now",```
#

and that's it

solemn ridge
#

Okay!
But should I put Timestamp with 26 November this year somewhere?

#

At billing_cycle_anchor parameter?

young imp
#

if you want the change to happen on the 26th of November

#

then you have to execute the code that same day

#

or you can use subscription schedules