#vincent_api
robust gulchBOT
👋 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/1329205424955588712
📝 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.
- vincent_api, 18 hours ago, 11 messages
pearl iron
Hi, if you received an email you should not ingore it since it sounds like it's applicable to you. You would need to follow next steps from the email for save card information via Terminal to use at a later time: https://docs.stripe.com/terminal/features/saving-cards/save-after-payment
gusty osprey
The change specifically refers to two endpoints that we do not use:
Terminal.Reader#process_payment_intent.process_config
Terminal.Reader#process_setup_intent
Our process is to collect the details with readReusableCard, then save and charge like we do if you typed out the card details. So that's why I think this change doesn't impact us.
pearl iron
Ah, that is a private feature that we are unable to assist with in this channel. Our support team will be able to assist you better than I can: https://support.stripe.com/contact
gusty osprey
thank you