How to Understand Trigger Events in Terminals: Difference between revisions
| Line 5: | Line 5: | ||
== Result of terminal being triggered == | == Result of terminal being triggered == | ||
If the terminal is triggered, a tamper event will occur, and all payment related keys will be permanently deleted. Payments are not processed in this state. The device will be locked and a warning message "Tamper detected! Please contact WizarPOS!" will be displayed on the screen | If the terminal is triggered, a tamper event will occur, and all payment related keys will be permanently deleted. Payments are not processed in this state. The device will be locked and a warning message "Tamper detected! Please contact WizarPOS!" will be displayed on the screen. | ||
== Triggered recovery == | == Triggered recovery == | ||
Revision as of 10:55, 21 March 2020
Cause of terminal being triggered
- Disassemble the terminal.
- HSM loose due to terminal fall.
- HSM loose due to other reasons.
Result of terminal being triggered
If the terminal is triggered, a tamper event will occur, and all payment related keys will be permanently deleted. Payments are not processed in this state. The device will be locked and a warning message "Tamper detected! Please contact WizarPOS!" will be displayed on the screen.
Triggered recovery
- Insert a tf card to the triggered terminal, restart the terminal, a token file will be generated in the tf card.
- Send the token file to whom you contacted before.
- You will receive a .sig file, copy the .sig file to the same tf card, same path with the token file and don't remove the token file.
- Restart the terminal, if success, the terminal can enter to system.