A method for resetting customer-specific security data assigned to a terminal, the method comprising: performing a terminal-token binding process which comprises the steps of: - providing a token with a command to generate a clearing code and store the clearing code in a predetermined memory location on the token; - receiving, from the token, the clearing code and an identification of the predetermined memory location; and - storing, in a memory of the terminal (112, 116), the clearing code in association with the identification of the predetermined memory location such that a subsequent presentation of the token to the terminal (112, 116) causes the terminal (112, 116) to perform a terminal reset process; and subsequent to performing the terminal-token binding process, performing the terminal reset process which comprises the steps of: - receiving, at the terminal (112, 116), a key from the token; - comparing the key with the clearing code stored in memory of the terminal (112, 116); - determining that the key received from the token matches the clearing code stored in the memory of the terminal (112, 116) during the terminal-token binding process; and - allowing the terminal (112, 116) to replace customer-specific security data stored in its memory with generic security data as a part of the terminal reset process in response to determining that the key received from the token matches the clearing code stored in the memory of the terminal (112, 116) during the terminal-token binding process. performing a terminal-token binding process which comprises the steps of: - providing a token with a command to generate a clearing code and store the clearing code in a predetermined memory location on the token; - receiving, from the token, the clearing code and an identification of the predetermined memory location; and - storing, in a memory of the terminal (112, 116), the clearing code in association with the identification of the predetermined memory location such that a subsequent presentation of the token to the terminal (112, 116) causes the terminal (112, 116) to perform a terminal reset process; and - providing a token with a command to generate a clearing code and store the clearing code in a predetermined memory location on the token; - receiving, from the token, the clearing code and an identification of the predetermined memory location; and - storing, in a memory of the terminal (112, 116), the clearing code in association with the identification of the predetermined memory location such that a subsequent presentation of the token to the terminal (112, 116) causes the terminal (112, 116) to perform a terminal reset process; and subsequent to performing the terminal-token binding process, performing the terminal reset process which comprises the steps of: - receiving, at the terminal (112, 116), a key from the token; - comparing the key with the clearing code stored in memory of the terminal (112, 116); - determining that the key received from the token matches the clearing code stored in the memory of the terminal (112, 116) during the terminal-token binding process; and - allowing the terminal (112, 116) to replace customer-specific security data stored in its memory with generic security data as a part of the terminal reset process in response to determining that the key received from the token matches the clearing code stored in the memory of the terminal (112, 116) during the terminal-token binding process. - receiving, at the terminal (112, 116), a key from the token; - comparing the key with the clearing code stored in memory of the terminal (112, 116); - determining that the key received from the token matches the clearing code stored in the memory of the terminal (112, 116) during the terminal-token binding process; and - allowing the terminal (112, 116) to replace customer-specific security data stored in its memory with generic security data as a part of the terminal reset process in response to determining that the key received from the token matches the clearing code stored in the memory of the terminal (112, 116) during the terminal-token binding process.