#brunogoncalvessq_api
pine zodiacBOT
👋 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/1240718681315737640
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
sturdy gulch
You can specify setup_future_usage: off_session (see https://docs.stripe.com/api/payment_intents/create#create_payment_intent-setup_future_usage) when you create a Payment Intent to indicate that you want to setup the attached paymetn method for future use
noble osprey
Nice, but would that make the payment method the default? (FYI, that's not the intention)
sturdy gulch
It shouldn't set invoice_settings.default_payment_method on the Customer
noble osprey
Perfect, and last question, if the card was used previously, using setup_future_usage: off_session won't create a duplicate entry in the Customer data, right?
sturdy gulch
It actually will create a duplicate - we don't do any deduplication of payment methods on our end
noble osprey
Understood, so if reusing a card, don't set setup_future_usage otherwise, set it to off_session, got it
Thank you very much
sturdy gulch
Actually backing up one second - did you mean reusing a card by passing in an already existing Payment Method ID? Or did you mean pass in new payment_method_data?
noble osprey
already existing Payment Method ID
sturdy gulch
Ah! Then you should be fine passing in setup_future_usage again (it won't create a duplicate entry)
sturdy gulch
👍