#ram_best-practices

1 messages · Page 1 of 1 (latest)

cyan gladeBOT
#

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

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

jagged sonnetBOT
crisp spoke
livid root
#

right but the upcoming invoice is already paid right?

#

can this be done in 2 steps? initiate pending subscription update first?

crisp spoke
#

No! It's a preview of future invoice with subscription information that plans to be updated

livid root
#

can the invoice be shown in the customer portal?

#

so what's the flow here? i should start with subscription.update?

jagged sonnetBOT
livid root
#

what I'd want to happen:

  1. the customer selects new plan with multiple items
  2. The customer sees how much it's going to cost, as well as prorata info (same as in billingportal)
  3. The customer approves and pays
  4. The new subscription becomes active

This works simply and perfectly with the billing portal for one item subscriptions.

grizzled rivet
#

👋 taking over for my colleague. Let me catch up.

livid root
#

thanks 🙂

grizzled rivet
#

I'm not sure I follow

#

oh sorry i think I get it now

livid root
#

Thanks:)
I know that, this is why I’m asking here

#

What’s a correct alternative

#

I managed to use subscriptions.update correctly but I’d like to break the flow up so the customers can better understand what’s going on

grizzled rivet
#

you will have to build the workflow yourself

#

using the upcoming invoice API as my colleague suggested

livid root
#

But how do I break the subscription update flow?

grizzled rivet
#

ok let's look at your list:

  1. you will offer them the different choices and they select (not Stripe related)
  2. you call the upcoming invoice API and display the invoice lines on your front-end
  3. and 4. you call subscription.update
livid root
#

oh i see, sorry I was missing that separate upcoming invoice call- i thought it's a result of subscription.update

#

thanks! taking a look at it 🙂

#

thanks again, just taken a look

#

is there a ui i can use to show that invoice?

grizzled rivet
#

no you would have to build your own

livid root
#

oh.. there are over 500 fields in that json

grizzled rivet
#

you don't need them all

livid root
#

like an actual invoice

#

yes I understand I probably don't need them all, but it's hard to tell for sure what I need and this is sensitive stuf...

grizzled rivet
#

you need to show the different lines the sub total and the total normally

#

you can try to mimic the view from the Dashboard view if you want

livid root
#

thanks.. I understand, but it's just that there are probably more cases I'm not aware of (customer already has balance, tax stuff, etc..) it's the "unknown" that worries me here

#

I'm trying to do as little ui work as i can and let stripe handle it, is there any other way you can think of that I can do something similar? maybe actually temporarily issuing an invoice?

grizzled rivet
#

no unfortunately I don't

livid root
#

i see, thanks

livid root
grizzled rivet
#

your Stripe dashboard

livid root
#

ok, not sure what exactly you're referring to but I'll try to find out

#

thanks for the help @grizzled rivet

grizzled rivet
livid root
#

also- not sure if you have a feature request option but letting you know I'd be really happy if the billing portal could handle multiple items subscription, at least on subscription_update_confirm ☺️

#

thanks again for everything :)!

grizzled rivet