People Twitter

7707 readers

1309 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 bullying or international politcs
Be excellent to each other.
Provide an archived link to the tweet (or similar) being shown if it's a major figure or a politician.

founded 2 years ago

MODERATORS

SendMeYourTaTas@sh.itjust.works

pelespirit@sh.itjust.works

1216

Learning on the job (lemmy.world)

submitted 1 day ago by The_Picard_Maneuver@lemmy.world to c/whitepeopletwitter@sh.itjust.works

179 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] jumping_redditor@sh.itjust.works 3 points 1 day ago (1 children)

Security is a big reason to never combine payment processing and user (the store) defined ui.

[–] sugar_in_your_tea@sh.itjust.works 1 points 1 day ago (1 children)

Could you clarify? Because I'm pretty sure that's not a thing.

[–] jumping_redditor@sh.itjust.works 2 points 20 hours ago (1 children)

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

[–] sugar_in_your_tea@sh.itjust.works 1 points 9 hours ago

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.