How to Understand Trigger Events in Terminals: Difference between revisions

Latest revision as of 07:34, 7 April 2024

Please visit new link of same subject:

https://smartpossdk.gitbook.io/cloudpossdk/faq/hardware-repair/learning-tampered-events

We're making a move! Our site's content is migrating to a new URL, to provide you with an enhanced browsing experience. Please update your bookmarks accordingly. Thank you for your continuous support!

@@ Line 1: / Line 1: @@
-== Cause of terminal being triggered ==
+{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/hardware-repair/learning-tampered-events}}
-* Terminal is disassembled.
-* Terminal fall and is broken.
-== 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.
-== About the recovery of terminal being triggered ==
-* Please contact the sales or contactor of wizarPOS, describe the detail information and token file, then apply for the recovery process.
-* How to get the token file: insert a TF-card into the triggered terminal, restart the terminal, and a token file will be generated in the TF-card.
-* If your application is approved, you will get a one time re-active sig file.
-* Copy the sig file to the same directory of the token file on the same TF-card(Please do not delete the token file).
-* Restart the terminal. If the operation is successful, the terminal can enter the system.