#Titan-subscription-creation
1 messages · Page 1 of 1 (latest)
Hello! Yes that's the general approach here, as the Subscription would be immutable whilst in the incomplete state (and therefore unable to change the prices)
One side effect to considering is a lot of unused Subscription objects that would be created from user switching plans, just something to bear in mind]
great thanks. What happens in the Stripe dashboard/admin UI for this user, does the frequency plan they didn't end up going for just auto disappear after a while?
oh OK, so if I assume all users want yearly by default, all those that switch to monthly with the toggle will have a dud incomplete yearly subscription against their Stripe account
OK thanks for the clarification, I'll do some testing and see what that looks like in the Stripe UI to our admin teams to make sure they don't get confused by anything they might see
They wouldn't appear in any Dashboard views by default
You'd have to explicitly set the filter to show the incomplete subscriptions
another question if you don't mind me asking here:
Is there a way for the user to select from one of their existing cards in Stripe? Or does it only work with a fresh card element
stripe.confirmCardPayment(clientSecret, {
payment_method: {
card: cardElement,
billing_details: {
name: nameInput.value,
},
}
That is possible yes, but we don't provide any pre-built UI to do that. So you'd fetch those Payment Methods from the API (https://stripe.com/docs/api/payment_methods/customer_list), display them in a custom UI and then pass the object ID (pm_xxx) to confirmCardPayment: https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-data-payment_method
stripe.confirmCardPayment(clientSecret, { payment_method: 'pm_xxx' }
ah great thanks for the clarification on the string option for payment_method 👍
already have the UI for existing cards, so good to go. Thanks!
Np!