How to Understand Trigger Events in Terminals

From wizarPOS
Revision as of 05:53, 19 April 2019 by Mahong (talk | contribs) (Created page with "== Triggered reason == * Disassemble the terminal. * When fall down, the HSM occasionally loose. * Other circumstances that can make the HSM loose. == Triggered result == Aft...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Triggered reason

  • Disassemble the terminal.
  • When fall down, the HSM occasionally loose.
  • Other circumstances that can make the HSM loose.

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.
Retrieved from "http://sdkwiki.wizarpos.com/index.php?title=How_to_Understand_Trigger_Events_in_Terminals&oldid=1057"