#rio_docs
open fossilBOT
👋 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/1403413222035554438
📝 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.
- rio_customerportal-checkout, 1 day ago, 11 messages
iron glen
My understanding is that when a customer adds a card in the CustomerPortal it does not collect some of the neccesary information (name, address, email). So it can't be used to prefill a future checkout session. Is there any way around this? It feels like a real oversight if customers can add cards that they can't use.
let me know if theres anything I can clarify about my question or use case
untold tide
Hi 👋
Unfortunately no, though I agree, this is would be a nice feature to have.
In addition to the necessary billing information not getting collected, it doesn't collect consent for redisplay the way our Checkout and Elements surfaces do which is required in many jurisdictions. Reaching out to our support team https://support.stripe.com/contact can increase the visibility for the demand of a feature like this.
iron glen
Okay, definitely disappointing but thank you for the clarification.
untold tide
I can appreciate that
iron glen
More of an abstract question I guess: Do you know if there any Stripe component or feature that would work better for this purpose?
Currently we use the Checkout for customers to buy subscriptions, then they use the CustomerPortal to switch a subscription's active payment method or change their billing information. An issue that we are running into is that customers get confused by adding a card in the portal and not being able to use it at checkout. However, if we remove the ability to add a card in the portal, they also cannot switch a subscriptions payment method because they are both tied to the features.payment_method_update field of the portal config.
Any solution through Stripe UI or through the API would work
untold tide
You could use a checkout session in setup mode to save a Payment Method for re-use later with out charging anything in the moment
https://docs.stripe.com/payments/checkout/save-and-reuse
iron glen
We looked into a possibility of using set-up mode for saving payment methods and then the CustomerPortal for a switching a subscription's payment method. But because both adding cards and switching cards is tied to features.payment_method_update in the portal config, they can still end up in the situation of adding a card in the portal that doesn't appear at checkout.
untold tide
Yeah, it would give them an option to add a card they can use later, but wouldn't actually prevent a scenario where they add a card in the Customer Portal expecting it to be available elsewhere. I agree this is not optimal.
iron glen
Okay, well.... definitely disappointing, but thank you for your help.
Another quick question. You suggested reaching out to Stripe Support at https://support.stripe.com/contact.
How does the Discord Stripe staff differ from Stripe Support? Is it not the same team?
untold tide
Were a smaller team with a heavy focus on developer API and integration questions. When reaching out to support they have experts covering a wider range of topics. They also take in a lot of feedback.
If a question comes into the support channel that is API / integration related and it can't be addressed by support it gets escalated to us.
iron glen
Makes sense, thank for the clarification and the help. Have a good day