#aravind_api
zinc flameBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1218170878475636777
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
daring archBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- aravind_api, 7 minutes ago, 8 messages
limber topaz
hi! hmm, no, that's just not really possible or how things work in Stripe.
You have a Customer object and that Customer object can have multiple PaymentMethods attached to it. You can't move a PaymentMethod from one Customer to another except by using Elements etc again on the frontend to collect the card details again to create a new PaymentMethod to attach to the other customer.
What you probably want to do is have one Customer object cus_xxx on your Stripe account be mapped to multiple "users" in your database for example and manage the overall access control in your own system.
dense helm
ok then if that customer deleted. how to overcome it
I am using checkout session object for checkout. majorly is email or customer label is viewed in checkout object
limber topaz
ok then if that customer deleted. how to overcome it
not sure what you mean, can you clarify/describe an example scenario?
majorly is email or customer label is viewed in checkout object
sorry, I don't understand the English in this sentence.
dense helm
if i maintain a single customer from stripe and maintain multiple users in db based on stripe customer.
Assume if new user login application tries for subscribing then in checkout out stripe page. new customer will create
limber topaz
then don't do that.
instead, authenticate the user to your site before they visit Checkout.
if they log in and you identify they are already associated with a Customer, do something different from just redirecting to a fresh CheckoutSession; like charging one of their saved cards directly.