this post was submitted on 18 Jul 2025
1375 points (98.6% liked)
People Twitter
10294 readers
590 users here now
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a pic of the tweet or similar. No direct links to the tweet.
- No international politcs
- Be excellent to each other.
- Provide an archived link to the tweet (or similar) being shown if it's a major celebrity, figure or any politician. If you replace the "x" at their site with xcancel (so it beomes xcancel.com), and you're not on mobile, it will save video. https://web.archive.org/save is another great option. Archive.is is no longer recommended because they remove/alter content.
- If a tweet (or similar) makes a statement of fact, either mark it as "satire" in the body or provide the original source link backing up the statement
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.