First beware this is already an old blog article from the 10th of August 2013. To me, the article seems (at least) incorrect at two points: 1. The number of P

First beware this is already an old blog article from the 10th of August 2013. To me, the article seems (at least) incorrect at two points: 1. The number of PIN retries cannot be reset. The command described to perform this reset in the blog post is the same as for checking the tries. Checking the tries just doesn't reset the number of tries, only providing the correct PIN does. But please prove me wrong by supplying the correct command to reset the PIN tries... The original paper about this http://fc13.ifca.ai/proc/9-2.pdf http://fc13.ifca.ai/proc/9-2.pdf describes a way to have 2 'free' guesses, but after those 2 guesses, you'll need to try again with a correct PIN. On a hacked reader, you could eventually find out someones PIN if the person uses the reader enough. Once the retries are exhausted, the card is blocked. Beware you'll need up-to 10.000 guesses, so up-to 5000 usages of the card. (note it is actually a little bit less, because not all PIN codes are allowed on production cards) 2. With EMV cards issued the last few years, the Track2 equivalent data on the EMV chip does not contain correct, usable data to create a magstripe card from. The Pin Verification Value in the EMV Track2 Equivalent data record is set to all zeros instead of the original PVV on the magstripe, rendering it pretty useless. So in short, you cannot create a working magstripe card with PIN by using data from the EMV chip.