#bwurtz-terminal-docs
vague saffronBOT
Hello! We'll be with you shortly. 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.
white leaf
@hybrid iron it's all in the API Reference no? https://stripe.com/docs/api/terminal/readers/object#terminal_reader_object-action shows it's a hash with all the options there
bwurtz-terminal-docs
hybrid iron
ahh yeah it is. I was looking for it in the retrieve section
thanks!
I have another question
If I want to make the credit card reader always able to accept payment, is there a best practice way to do that?
white leaf
That doesn't really make sense to do anything like this. There's no reason for a reader to be "ready to accept payment" at at any time
hybrid iron
We've had issues where people add items to their cart and then tap their card to the card reader without pressing the button that triggers the processPaymentIntent call
and then walk away, thinking they have paid
white leaf
You are expected to have real humans monitoring those devices. They can not be autonomous without any monitoring
hybrid iron
What do you mean by "they can not be autonomous?"
white leaf
Our terms of services require real human supervision for using Terminal. You can't put the reader in a kiosk on its own without any human monitoring, this is forbidden
when I pay at a grocery store using the self checkout there's always a human monitoring that I paid. I couldn't pretend to pay and leave without paying