#yagnesh_unexpected

1 messages ยท Page 1 of 1 (latest)

halcyon coyoteBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1498617711801139322

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

rapid flower
#

๐Ÿ‘‹ What are the expected and actual dates you see?

hushed steeple
#

the next charge is supposed to happen on 1st of May,
but the upcoming invoice webhook i got is for the charge on June 8, but there is no payment of June 8 according to subscription phases

rapid flower
#

Looking at the subscription schedule, I think the combination of billing_behavior: prorate_on_next_phase and billing_cycle_anchor: automatic may be the issue. The first defers billing to the next natural billing cycle, and the second preserves the original Feb 6 anchor and I think the first natural cycle date in Phase 2 falls around Jun 6โ€“8, depending on the price's billing interval

#

If you want the charge to happen on May 1 (the phase start date), you would need to recreate the schedule with billing_behavior: prorate_up_front. This would generate an invoice immediately at each phase transition.

hushed steeple
#

so on May 1 no charge will happen even though the phase charge date is May 1?

rapid flower
#

Yes, this is purely a schedule transition event, not a billing event in the current configuration

hushed steeple
#

what if i pass the billing_cycle_anchor: 'phase_start' in phase and update the subscription

rapid flower
#

If you pass that along with billing_behavior: prorate_up_front, I think that should work

hushed steeple
#

Okay,
sub_1TR8qHFKQPzaD7LlsQPSWuvh (test mode)
this also has similar phase generated but it got charged on proper date, i neither passed phase_start or prorate_up_front

rapid flower
#

Looks like the phase durations may align with the billing intervals on that one

hushed steeple
#

sorry i did not get that, can you please expand in simple terms

rapid flower
#

So the phases in the test sub are as follows:

  • Phase 1 starts Apr 28, ends May 6 (8 days)
  • Phase 2 starts May 6, ends May 14 (8 days)
    And the prices used (price_1TR8q5FKQPzaD7LlnLFq3orr, price_1TR8qUFKQPzaD7Ll6rTleTuQ were created with an 8-day billing interval
    So basically, the phases and billing cycle aligned, which is why the charge happened on the phase changes
halcyon coyoteBOT
hushed steeple
#

what is this prorate_upfront used for?

tender hemlock
#

hi! I'm taking over this thread.

hushed steeple
#

Okay in short if i pass the billing_cycle_anchor: 'phase_start', it will charge proper on a given date