#Hugues

1 messages · Page 1 of 1 (latest)

lone spearBOT
plucky jungle
proud ginkgo
#

Hi, the subscription id is sub_1NpEEdFGXpRXhvrdHUoRMqQg. I hope that you can use it to find its subscription id. Takes note that all this has been made in "Test Mode".

plucky jungle
#

Taking a look

#

Sorry, I updated the message above as there is no $0 invoice. It's mainly prorations and the small amounts are applied to the customer's balance.

proud ginkgo
#

Are you still there @plucky jungle ?

plucky jungle
#

Looking here

lone spearBOT
plucky jungle
#

We document how prorations with billing cycle anchor works here, https://stripe.com/docs/billing/subscriptions/billing-cycle: 'To create a subscription with a billing cycle anchor in the future and a prorated invoice until the anchor takes effect, you can use the Subscriptions API or Checkout.' In this case, it's prorated from the Subscription creation until the 13th which is the billing cycle anchor date

proud ginkgo
#

I don't understand this idea of having a customer to pay a proration for a service that starts only the 13th of September.

harsh acorn
#

👋 Hopping in here since pgskc has to head out - give me a minute to catch up

#

First I want to clarify - there aren't two separate invoices for $0 and $0.61. There's a single invoice for $0.61 which was automatically paid because the customer had some credit balance, so there was no resulting payment created. That prortion was created because you set a billing_cycle_anchor for 9/13/2023, and the subscription was created on 9/11/2023. If your goal was not to charge for the time betwee 9/11 and 9/13 you need to pass in proration_behavior: none

proud ginkgo
#

I guess that's a property owned by SubscriptionCreateParam?

harsh acorn
#

yup!

proud ginkgo
#

Thanks @harsh acorn & have a nice weekend.