#barney-laurance_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ 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/1282698565193564303
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- barney-laurance_best-practices, 4 days ago, 9 messages
Hi there ๐ it's hard to say without more context or an example of a Payment Method that is being saved in this way. If you have an ID of a Payment Method behaving this way, sharing that would allow me to get more insight about what you're talking about.
Right now I'm not even sure if it's something we would be doing that is saving the Payment Method, or if it's something your integration is doing.
@wind stratus checking in to see if you saw my above message and are still around to tell me more about your flows?
Hi @pastel marlin . Sorry just saw your second message. Let me get you and id of a payment method from our staging environment
๐ stepping in
OK so this payment methid is from a test I did in our staging env: pm_1Px5LiKkGuKkxwBNYa9kijXp . I didn't tick the box to allow redisplay, so it has redisplay: limited on its metatdata
Thanks, taking a look
Okay yeah so there is a difference here in whether a PaymentMethod is attached to a Customer (which is controlled via whether you set setup_future_usage) and whether you allow the redisplay of the PaymentMethod via Payment Element.
The other thing to take into account here is that you can display these limited saved PaymentMethods if you wanted to show the Saved PaymentMethod for a Subscription.
So that is why it would still be attached to the Customer
This is talked about a bit here: https://docs.stripe.com/payments/save-customer-payment-methods#save-a-payment-method-for-a-subscription-or-recurring-transaction
OK thanks - sounds like I should I should adjust the code to turn off setup_future_usage in case that box isn't ticked. Do you know if I need to turn it on for on_session use in case the box is ticked, or does stripe do that implicitly? I guess I can get the choice from the payment method preview.
No we don't set setup_future_usage for you here