A method for verifying an identity of a communicating terminal user, including: a preliminary step comprising: - communicating to at least one server dedicated to a service, first identity data of the user, - generating a bi-key - public/private key pair - by the terminal, - generating at the server second identity data of the user, the second data defining an identity derived from the user that is specific to the service, said second identity data being a digital certificate linking said public key to said first identity data, and - storing the second identity data in a secure memory of the terminal, a current step of identity verification comprising: - transmitting from the server to the terminal a token to be signed in order to authorise or not an access to the service to which the server is dedicated, - using in the terminal the private key at least to sign the token, the signed token (C*) being transmitted to the server and verified at the server, and - in the case of a positive verification of the signed token at the server, the server validates the identity verification of the user of the terminal and authorises the access to the service; wherein transmitting the token to be signed and/or the signed token (C*), between the server and the terminal is performed via an equipment requesting access to the service to which the server is dedicated, the access to the service being conditioned by an identity verification of the user from the terminal of the user in said common step. a preliminary step comprising: - communicating to at least one server dedicated to a service, first identity data of the user, - generating a bi-key - public/private key pair - by the terminal, - generating at the server second identity data of the user, the second data defining an identity derived from the user that is specific to the service, said second identity data being a digital certificate linking said public key to said first identity data, and - storing the second identity data in a secure memory of the terminal, - communicating to at least one server dedicated to a service, first identity data of the user, - generating a bi-key - public/private key pair - by the terminal, - generating at the server second identity data of the user, the second data defining an identity derived from the user that is specific to the service, said second identity data being a digital certificate linking said public key to said first identity data, and - storing the second identity data in a secure memory of the terminal, a current step of identity verification comprising: - transmitting from the server to the terminal a token to be signed in order to authorise or not an access to the service to which the server is dedicated, - using in the terminal the private key at least to sign the token, the signed token (C*) being transmitted to the server and verified at the server, and - in the case of a positive verification of the signed token at the server, the server validates the identity verification of the user of the terminal and authorises the access to the service; - transmitting from the server to the terminal a token to be signed in order to authorise or not an access to the service to which the server is dedicated, - using in the terminal the private key at least to sign the token, the signed token (C*) being transmitted to the server and verified at the server, and - in the case of a positive verification of the signed token at the server, the server validates the identity verification of the user of the terminal and authorises the access to the service; wherein transmitting the token to be signed and/or the signed token (C*), between the server and the terminal is performed via an equipment requesting access to the service to which the server is dedicated, the access to the service being conditioned by an identity verification of the user from the terminal of the user in said common step.