In most cases, the cause will have technical reasons (read more here), but it is important to make sure of the following as well:
The driver used the chip's ID in the 'iButton ID' field specified in his profile;
The driver authorized himself in a different way before he started driving;
The driver moved the chip away from the reader too soon, which may have resulted in the authorization failing.