#thibaut_api
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/1451211395680178399
๐ 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.
- thibaut_api, 1 hour ago, 7 messages
hi there!
Hi again soma
I think I already answered that question earlier?
yes but i was not able to answer ๐
two more questions:
- it's a bit weird that i can see it when inspecting the charge object on the stripe dashboard
- If it's not possible, i am trying to find an alternative by finding transactions/charges from the terminal
it's a bit weird that i can see it when inspecting the charge object on the stripe dashboard
can you clarify where you see this exactly? a screenshot would help.
hi there, I'm taking over for soma as they had to step away. please give me a bit to catch up on your request
interesting. that attribute looks like it's inside the payment_method_details.card_present object in the Charge response, but I see no documentation for that parameter here https://docs.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-read_method
the Dashboard uses a different API version than what is publically accessible, so it may only be available there. I'm going to look into it further though, one moment
yeah, this appears to be restricted to the Dashboard and I can't see another pre-built method for doing this. I would concur with my colleague's earlier response that your best option for doing this is to store the reader ID in the metadata of the Payment Intent