>>Hi Tc,
>>
>>What I am saying is that RFID combined with Credit Cards requires such a mechanism, and so do Passports as well so you have control over when it will accept a scan.
>>
>>I brought this up with one of our banks a couple of years ago when they were looking at introducing this, their reply was "That would never happen", just goes to show you, banks don't understand security.
>
>Look, we're programmers, and we get all sorts of bells ringing in our heads whenever we hear "that would never happen", because we know how many times we wrote code under an assumption that certain things would never happen, only to have to urgently rewrite it when they did. I actually had a comment in code saying "21-sep-1990 xxxx said this type of invoice will never have a rebate on it", so just two years later I pulled it up, pointed the finger at the line and he said "I know, I know".
>
>So the RFID chip is supposed to be incommunicado with the standard POS sensor at distances of more than a couple of inches? And nobody thought of other types of sensors which may reach further? That's sloppy, and a recipe for disaster. I may start carrying my card between two metal sheets, just in case, because here all the cards that I've seen have a chip in them, and all the card readers have a chip reader. I don't know whether these are RFIDs or work on contact (some copper is exposed on the card), though.

That's what I do :) Plus, it's a good log to show that we did consider it at the time. I do the same when I'm implementing something not exactly as I would like to - it could be for any reason - time, command decision, customer paid for a specific functionality with signed docs to back it up, etc. Inevitably someone later will ask "why didn't we? or why did we?".... I also write everything down - what was discussed, what was decided, etc in notebooks by date so a year later I can go back and read why I did something the way I did. I have piles of those notebooks now :)