#krishna1433-sugscription-schedule

1 messages · Page 1 of 1 (latest)

languid quest
#

Thanks for the info. Looking in to it...

blazing ledge
#

btw I'm not a plus subscriber

languid quest
#

Apologies, dropped off this thread for a bit. It looks like that subscription created an invoice and charged the customer. The next billing date is Dec 23

#

Where are you seeing that that subscription is not charging anyone?

blazing ledge
#

no worries, below are the events,

#

while creating the subscription schedule, I addded 10 phases, 2mins apart

#

as per my understanding, each phase should create a new invoice right

languid quest
#

Why do you have so many changes two minutes apart? Is this for testing?

#

Looking in to that behavior...

blazing ledge
#

Yes this is for testing

This is an actual subscription schedule that I created -
sub_sched_1JyukiBoSDMwkpKizkAg17zB

#

Customer's default payment should be charged when an invoice is created is my requirement actually. And the invoice should be created every month

languid quest
#

Have you tried with a billing_cycle_anchor of phase_start?

#

I don't know if an invoice per phase is expected behavior here.

#

That is currently what is happening, the sub you set up is set to bill every month

blazing ledge
#

so the customer's payment method will be charged every month

#

with the setup I have created

#

PaymentIntent status:
requires_confirmation

#

is what is see and the invoice is not being paid automatically

languid quest
#

Where are you seeing that?

#

On that second subscription schedule, the first start period isn't until next month

#

On the first subscription, there is only one invoice/PI so far and it looks like it is paid

wary viper
#

Hey @blazing ledge I'm stepping in and getting caught up here. Looking at your initial screenshot it's also important to point out that invoices for subscriptions (other than the first) will go into a draft state and finalize about an hour later. So when you're changing the subscription every 2 minutes you aren't allowing enough time for this flow to occur.

#

I also wanted to see if there any outstanding questions that you had from this conversation.

blazing ledge
#

Acha

#

I was worried that this isn't working because of some mistake in code

wary viper
#

I don't think it is, looks like it's just a timing issue.

blazing ledge
#

Awesome thank you