I don’t understand why the card reader and the screen are separate units, just combine them like those Square kiosk things that counter order places have.
stripe recommends it for card reader to smartphone at least, and it looks like home depot is an example of why it should be done between the card reader and the pos.
I get the phone thing, because phones are relatively insecure devices, but they could have functionally separate systems in one box.
The main problem I’m trying to solve is the weird UX where I need to select a payment method even after paying on the payment device. If it was designed as a complete set instead of separate units, I think they’d fix that.
I don’t understand why the card reader and the screen are separate units, just combine them like those Square kiosk things that counter order places have.
Security is a big reason to never combine payment processing and user (the store) defined ui.
Could you clarify? Because I’m pretty sure that’s not a thing.
stripe recommends it for card reader to smartphone at least, and it looks like home depot is an example of why it should be done between the card reader and the pos.
https://stripe.com/ie/resources/more/how-do-card-readers-work
https://listings.pcisecuritystandards.org/documents/accepting_mobile_payments_with_a_smartphone_or_tablet.pdf
I get the phone thing, because phones are relatively insecure devices, but they could have functionally separate systems in one box.
The main problem I’m trying to solve is the weird UX where I need to select a payment method even after paying on the payment device. If it was designed as a complete set instead of separate units, I think they’d fix that.
Because at the scale these stores work at. It’s cheaper to have different units you can replace, repair and upgrade at different intervals as needed.