Electronic Secure Authentication (ESAT)

 View Only
  • 1.  Food for thought about existing systems

    Posted 05-31-2021 05:47
    Hi all, FYI, Let me share a couple of pictures from a shop in my surroundings, the pics are in google drive under 'shop-example'. It's a very low-tech and little demanding use of QR as replacement for cash, as shop doesn't really have to do anything else than make a contract to get a seller ID, and print out QR code, and customer has an app on phone, which can be easily (even anonymously) charged via ATM. As you can see from zoomed-in picture, user can even choose between 2 payment processors (I believe one is actually charging to your phone bill). The verifcation of payment relies on people's honesty though, as custer just types in the amount of on the receipt, and then shows 'paid' screen the sum to cashier. Not sure how fraudulent cases will be handled though, my best guess that same way as counterfeit money, and I guess forensics will be much more difficult. I'm wondering if and how we should add this use case, or at least acknowledgement of it in the final document. Best regards, Lauri. Attachment: signature.asc Description: This is a digitally signed message part


  • 2.  Re: [External Sender] [esat] Food for thought about existing systems

    Posted 05-31-2021 05:50
    I think acknowledging it at the end as a reference will be fine > On May 30, 2021, at 22:47, Lauri Korts-PÃrn <lauri@cyberdefense.jp> wrote: > > ïHi all, > > FYI, Let me share a couple of pictures from a shop in my surroundings, > the pics are in google drive under 'shop-example'. > > It's a very low-tech and little demanding use of QR as replacement for > cash, as shop doesn't really have to do anything else than make a > contract to get a seller ID, and print out QR code, and customer has an > app on phone, which can be easily (even anonymously) charged via ATM. > As you can see from zoomed-in picture, user can even choose between 2 > payment processors (I believe one is actually charging to your phone > bill). > The verifcation of payment relies on people's honesty though, as custer > just types in the amount of on the receipt, and then shows 'paid' > screen the sum to cashier. > Not sure how fraudulent cases will be handled though, my best guess > that same way as counterfeit money, and I guess forensics will be much > more difficult. > > I'm wondering if and how we should add this use case, or at least > acknowledgement of it in the final document. > > Best regards, > Lauri. This e-mail, and any attachments, is for the intended recipient(s) only, and may contain information that is privileged, confidential and/or proprietary. If you are not the intended recipient, please delete this message.