#s123317_api
charred cipherBOT
👋 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/1446139501826146304
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
distant echo
Hello, not immediately sure on this myself. Looking in to it and will get back with what I can find
balmy crest
Thank you
distant echo
To be clear are you using the Signature screen from this page or are you using something else for this? https://docs.stripe.com/terminal/features/collect-inputs
distant echo
So the docs don't say that any data is added to the intent itself but it does say you can listen to terminal.reader.action_succeeded events to know when these actions succeed.
https://docs.stripe.com/terminal/features/collect-inputs?terminal-sdk-platform=server-driven#receive-input-data
This looks to be the signature event for that intent was this one because it happened right before that intent was confirmed:
https://dashboard.stripe.com/test/events/evt_1SaHG3IpbbIMMVWQWjs8XM6k
balmy crest
Ah thank you 🙂
I can't see much information there about setup intent or customer, how can i link it to the customer?
distant echo
I think the simplest way would be to add the customer's ID as metadata:
http://docs.stripe.com/terminal/features/collect-inputs?terminal-sdk-platform=server-driven#metadata
There isn't anything data-wise tying the action to the customer. I think the idea is that because your system is sending these inputs and payment to the reader in sequence it is already tracking this as some kind of overall process.