Quote from: Zr40 on April 12, 2013, 10:04:27 PM

There are two obvious issues with this:

1. Users can report higher balances than they actually have.
2. Passwords should not be needed; he already has access to the database, and if he really needed to be able to log in as the user, he could just temporarily change the password hash stored for the user.

1. Of course he has to check everything we tell him. But for example in my case some transactions were repeated, so maybe if i tell him exactly were were the errors, that can speed things up.

2. I don't know the database structure, maybe everything is splitted in tables and he has to build a complex query to extract that info. About the password when the hash solution is true, we don't know if the user password encrypted something in order to make it not accessible to him (or the gov) so changing the password might not be a solution in some cases, that's why i said "IF REQUIRED". (i like to to do this things to protect the user from seizures)

But this is anecdotic. The key point is that the initiative is to offer him what he needs in order to help him to help us.