#vincent_api
copper sandBOT
đ 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/1328873926050316369
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
barren hemlock
Apologies for the wait. I'll be with you shortly
past charm
no worries
barren hemlock
Sorry again about the wait. Usually when you receive an email like this, it is targeted for users who use the feature that is mentioned. Are you saying that you don't use this feature and the email was maybe sent in error?
past charm
It's possible. I checked our codebase and can't find anywhere that we use these endpoints.
I'm also searching logs in the stripe dashboard for these, but don't see anything:
POST /v1/terminal/readers/:id/process_setup_intent and
POST /v1/terminal/readers/:id/process_payment_intent
I'm fairly confident we don't use these endpoints. However I'm concerned that this will impact saving payment methods via SetupIntents in general if we don't upgrade (we're using a 2019 API version, I know we should update). Is that something you can comment on?
barren hemlock
Are you using Terminal (card present) to collect card information to save and use later?
copper sandBOT
past charm
We do use Terminal, methods like ::Stripe::Terminal::Reader.create and ::Stripe::Terminal::ConnectionToken.create in Ruby.
I'll have to dig a little deeper to confirm if we use then use the reader to collect card information. I am at the end of the workday so I will be able to give a better answer tomorrow morning. Thanks for your help!