#damienfa_subscription-updates-bca

1 messages · Page 1 of 1 (latest)

sterile narwhalBOT
#

👋 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/1267490963488505887

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

spring frigate
sharp quest
#

🤔 but we update several time the subscription (everytime a user upgrade its subriptions) and the billing anchor hasn't changed…

spring frigate
#

Share some examples please, req_xxx IDs of the requests where updates where made and the anhcor persisted

sharp quest
#

I mean, how do you explain that in :

  • the request req_lvp9mDkSsEpO0V, the billing anchor hasn't changed (still the August 1st) ;
  • then a similar request req_S1R6TeqA7dqHEO, it is still not changing (still the August 1st) ;
  • then another update (same type of request, quantity changed) : req_TWrEa7XjjQJWL4 , the billing anchor hasn't changed yet
  • ⚠️ then a similar request (req_EyvlQziXR9RCec), and the billing anchor changed to July 22th.
  • then more requests and the the billing anchor stucks to the July 22th : req_QiHC2ztrFdtzjL , req_eQJcvsmmvLIp8h, req_4gGejHMlrVbqJu (this last one is on July 23th and the billing anchor is still the July 22th) …

the request id provied here are in order of execution, for a same subscription (sub_1PY2X8FozK3SDFaCay5xm2J1)

#

We do not understand the behavior.

#

Maybe the only thing which has changed is that we add a new "item" in req_EyvlQziXR9RCec …  🤷🏻‍♂️

#

Should we send the expected billing anchor in every request that updates the subscriptions (quantity, or new item… etc.) ???

spring frigate
#

I'll check on this real soon – server is busy

knotty spindle
#

Hi there 👋 I took a look at the request where the billing cycle anchor (BCA) changed, and believe I see why that happened.

In req_EyvlQziXR9RCec you deleted si_QWLX2JuICWEwVO from the Subscription. At that point that was the only Subscription Item on the Subscription, and was based on the following Price ID which has unit_amount set to 0 and is a free price.
price_1LSRzCFozK3SDFaCvLaD7V69

Additionally, you used price_data to create a new Price dynamically, and set its unit_amount to a non-zero amount.

This triggered our logic that automatically resets the BCA when a Subscription moves from having all free Prices to having a Price with an actual amount:
https://docs.stripe.com/billing/subscriptions/billing-cycle#:~:text=If all the prices are zero-amount%2C adding one or more paid prices immediately resets the billing period
https://docs.stripe.com/billing/subscriptions/upgrade-downgrade#handling-zero-amount-prices-and-quantities

sterile narwhalBOT