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: @@
-== Triggered reason ==
+{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/hardware-repair/learning-tampered-events}}
-* Disassemble the terminal.
-* HSM loose due to terminal fall.
-* HSM loose due to other reasons.
-== Triggered result ==
-After a tamper event, all payment related keys are permanently erased. Payments will not be processed in this state. The device will be locked and a warning message display in the screen “Tamper detected! Please contact WizarPOS!”.
-== 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.