#Titan-subscription-creation

1 messages · Page 1 of 1 (latest)

versed jungle
#

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]

raw geyser
#

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

versed jungle
#

Exactly, yes

#

And there's no way to clean those up (i.e. delete)

raw geyser
#

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

versed jungle
#

They wouldn't appear in any Dashboard views by default

#

You'd have to explicitly set the filter to show the incomplete subscriptions

raw geyser
#
stripe.confirmCardPayment(clientSecret, {
    payment_method: {
      card: cardElement,
      billing_details: {
        name: nameInput.value,
      },
    }
versed jungle
#
stripe.confirmCardPayment(clientSecret, { payment_method: 'pm_xxx' }
raw geyser
#

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!

versed jungle
#

Np!