How to Understand Trigger Events in Terminals: Difference between revisions

From wizarPOS
Line 1: Line 1:
== Triggered reason ==
== Triggered reason ==
* Disassemble the terminal.
* Disassemble the terminal.
* When fall down, the HSM occasionally loose.
* HSM loose due to terminal fall.
* Other circumstances that can make the HSM loose.
* HSM loose due to other reasons.


== Triggered result ==
== Triggered result ==

Revision as of 10:41, 21 March 2020

Triggered reason

  • 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.