#ironbeard_best-practices

1 messages · Page 1 of 1 (latest)

solid shellBOT
#

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

📝 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.

vague breach
#

heyo toby 🙂

molten perch
#

Hello 👋

You'll want to create a new Subscription.

#

The first Invoice will already be finalized, and won't include the updates that you make.

vague breach
#

oh, interesting

#

even with payment_behavior: default_incomplete?

molten perch
#

Correct. With default_incomplete, the first Invoice is still finalized when the Subscription is created, but the Payment Intent isn't confirmed immediately.

vague breach
#

what if a user is upgrading an existing subscription? I send an update call with the prices/items in their cart on the GET of the review page...and then if they change their mind and go back to edit their cart, in this case I assume updating the subscription again is the right move?

molten perch
#

I wouldn't update the Subscription until you know for sure what changes need to be made. Since rolling back those updates is really tedious, and may mess up proration calculations.

vague breach
#

yeah, for sure. 🤔

molten perch
vague breach
#

good point, i'm somewhat familiar with those. but if my "Review" page is going to have a link to change your cart, then it seems like I can't create/update the Subscription until after they click the "Submit order" button. I was going to have that button call JS stripe.confirmPayment() with the latest_invoice.payment_intent / .client_secret and a confirmation token.

molten perch
#

I think it still can, just it may need to do some other lifting first depending on the exact flow you're settling on.

vague breach
#

actually, pending-updates seems kind of right:

  1. if new subscription and user changes their cart, delete the subscription and create a new one
  2. if existing subscription, apply pending updates on the GET of /checkout/review/. If they change their mind, the existing subscription hasn't fundamentally changed, so I can do a different pending update after they change their cart and GET /checkout/review/ a second time.

Would I need to do anything to "clear" the initial pending update?

molten perch
#

I don't believe so, and the guide seems to align with that

#

You can clear them though if that is easier

vague breach
#

oh, nice. I need to spend more time with the guide, thank you!