#meek
1 messages · Page 1 of 1 (latest)
Hi, you would want to call Update Subscription instead and pass proration_behavior to always_invoice
If you want to charge for an upgrade immediately, pass proration_behavior as always_invoice to create prorations, automatically invoice the customer for those proration adjustments, and attempt to collect payment.
Okay got it, so once i do that how do i get the user to the invoice page
The Subscription will attempt to charge using the saved payment method. If it can't then the Invoice status will be failed and depends on your setting on https://dashboard.stripe.com/settings/billing/automatic, it will send your customer an email
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
I see, is this the best approach for a per-site model like webflow where you pay per site? Where i just update the quantity of the line items? Or should i be creating new checkout sessions for each site?
The con to the ladder is that the customer will receive 3 different bills for 3 different sites
Actually here is show i want to set this up. I have 3 different prices
- Per site -> $20: Whenever a new site is created, user pays $20
- Per team member -> $10. Whenever you invite a team member to the users main admin account, user pays $10 for each team member
- Per client -> $10. Whenever a client is invited to the site the user created, user pays $10 for each client
It's ... more of modeling your price. Once you have a model which can represents what you want to achieve, then update quantity on existing Subscription is better than creating a new checkout session (which = having new separated Subscription)