#eirik-checkout-savedcard

1 messages ยท Page 1 of 1 (latest)

trail shadowBOT
autumn kite
#

eirik-checkout-savedcard

lean current
#

Yes, I'm passing in an existing Customer ID, and the existing email address gets populated, but I don't see any of the saved payment methods offered up. (This is all in test mode, not live mode.)

autumn kite
#

Does that Customer have a saved PaymentMethod?

lean current
#

Yes, confirmed, and a billing address as well.

#

To be clear, what does "saved PaymentMethod" mean? When I am testing, they have another existing subscription, and thus an active default PaymentMethod. But I didn't create a PaymentMethod using the API; it was entered by the customer during a previous Checkout session.

autumn kite
#

Can you give me a customer id and a Checkout Session so I can look?

lean current
#

OK, in the process of creating a fresh test user with my latest settings, it worked, and the existing card is now offered.

#

Follow-up question: Can I prevent the existing card from being offered upon Checkout, and always require the user to enter new payment details?

autumn kite
#

no

#

you could detach/delete it, but that won't work for you since you do Subscriptions

lean current
#

OK, that's useful to know. The reason I'm researching this is because I'm looking for allow multiple users to access the billing account in various ways in enterprise settings. So I'd like to be able to have e.g. multiple billing managers, but on the other hand, I don't want anyone else than an actual cardholder to be able to consent to new charges. Are there some best practices around this?

autumn kite
#

No I can't think of a solution here. Our vision of the products like Checkout and Customer Portal today are that the Customer is one person/entity and not a group of people so that wouldn't really fit unfortunately

lean current
#

Well, one "entity" is usually a group of people.

#

in the case of a corporate customer

#

But I suppose a cardholder is always an individual.

autumn kite
#

usually even with a group of people there's one person that manages the account

#

But I agree we will need to support "multiple users per account" or such in the future, just not on our roadmap for now ๐Ÿ˜ฆ

lean current
#

OK, all of this is actually perfectly fine--I just wanted to know what the best practice is here. If Stripe doesn't support it, then I won't either ๐Ÿ™‚

#

I think that answers my questions; thank you very much!