#conrad-at-pronto_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/1319461581276581959
๐ 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.
- conrad-at-pronto_api, 22 hours ago, 15 messages
HI ๐
We don't generally help with beta programs here, only GA-d functionality
But, looking at the code snippet in the public docs https://docs.stripe.com/terminal/features/collect-inputs?terminal-sdk-platform=server-driven#collect-inputs, I don't see any relationship to a Payment Intent at all.
So these would be separate actions you perform (collecting details on the reader & collect payment)
Yes agreed
As for question 2
After the customer has either submitted or skipped all inputs, Stripe updates the reader object and sends out the terminal.reader.action_succeeded webhook.
We thought we had to configure collect inputs before payment so that it would go through that flow upon payment completion, but that resulted in card declined
we were able to collect inputs actually without a payment at all
so they seem like completely separate/discrete actions
so they seem like completely separate/discrete actions
Yes, that's what I'm getting too
And when you configure a webhook endpoint to receive the terminal.reader.action_succeeded events, you will need to make sure you specify the beta header as well
terminal_collect_inputs_beta=v1
yes agreed
we previously did a Terminal javascript implementation and with that we were able to know the outcome without relying webhooks
because we are doing server-driven integration, it is expected that we only will know the outcome by listening for terminal.reader.action_succeeded and terminal.reader.action_failed?
As I said, we cannot really provide concrete guidance about betas here. But from my read of the docs, I think you do need to rely on webhooks.
If you want more detailed information I recommend writing in to Support https://support.stripe.com/contact
thank you for your help
I'm happy to shed what little ๐ก I can ๐