#credonocr-checkout-session
austere bobcat
@hazy night Checkout always creates one subscription
Creating multiple subscriptions is almost always a bad idea since it means multiple separate charges each cycle on the same card and most banks would block that
but overall if you wanted that, you'd use Checkout to create the first one, and then you'd write code to create new subscription afterwards
hazy night
my question is, when the user decrease the number of seats in the next payment how we can handle effectively the subscriptions to replicate that in our data
hazy night
is there a way to link each product quantity to a costumer ?
austere bobcat
Have you read https://stripe.com/docs/billing/subscriptions/quantities
austere bobcat
@hazy night did you have any follow up questions?
hazy night
I have another question, there's a way to handle the modified quantities on customer portal on any webhook event?
fringe ether
Can you clarify your use case and what you hope to achieve?
hazy night
ok
i have 3 seats like github billing process, then remove one seat but that seat is alredy used
so validate that and cancel the update quantity in the customer portal
that make sense?
fringe ether
Not out of the box for customer portal. You can listen to customer.subscription.updated event for any quantity update and check the validity. If the seat it's been used, then re-update the subscription quantity again: https://stripe.com/docs/billing/subscriptions/integrating-customer-portal?platform=billing#quantity-updates
However, I recommend do your own subscription management instead of using customer portal in such use case, so that you can pre-valid before making changes to a subscription