anishsubedi1_83944

[arctic glade]

You want to prevent customers from logging out of link?

[polar quail]

yes

[arctic glade]

Oh as far as I know that's not possible

They'll be able to log out if they want

[polar quail]

I am a bit confused about SetupIntent (create Vs Retirve vs update).

To allow the user to change their credit card (on our page) of an already existing subscription which one should I do ?

[arctic glade]

create

Have you seen https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements ?

Following that guide will create the new payment method

You'd then need to update the subscription with that new payment method, setting it as the default: https://stripe.com/docs/api/subscriptions/update#update_subscription-default_payment_method

[polar quail]

the yea followed this document. And implemented create intent.

However, it does at new credit card. But, why there are multiple guest payments?

[arctic glade]

What do you mean?

Looks like your test cli integration created those

Has nothing to do with setupintent

[polar quail]

looking into it..

So after create setup intent is successful, it should update the user's subscription on default_payment_method ? So, in next billing cycle it will use updated one?

[arctic glade]

it should update the user's subscription on default_payment_method ?
This doesn't happen automatically

You'd need to specifically set it as the subscription's default

[polar quail]

yea, sorry I mean. I should*

Defaut_payment_method = returned successful setupIntentId?

[arctic glade]

No the payment method id created by the setupintent

ie this: https://stripe.com/docs/api/setup_intents/object#setup_intent_object-payment_method