How to Understand Trigger Events in Terminals: Difference between revisions

From wizarPOS
No edit summary
Line 1: Line 1:
== Cause of terminal being triggered ==
What Causes the Terminal to Trigger
* Terminal is disassembled.
* Terminal fall and is broken.


== Result of terminal being triggered ==
* '''Disassembly:''' Attempting to disassemble the terminal.
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.
* '''Physical Damage:''' Dropping or breaking the terminal.


== 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.
Consequences of a Triggered Terminal
* 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.
When the terminal detects tampering or damage:
* 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.
* It will initiate a '''tamper event'''.
*
* All payment-related keys are permanently deleted, disabling payment processing.
*
* The terminal locks itself and displays a warning: '''"Tamper detected! Please contact WizarPOS!"'''
 
 
Recovery Process for a Triggered Terminal
 
1. '''Reporting the Issue:'''
 
Contact WizarPOS sales or support. Provide detailed information about the incident and a 'token file' from the terminal.
 
2. '''Obtaining the Token File:'''
 
* Insert a TF-card into the affected terminal.
*
* Restart the terminal. It will automatically generate a 'token file' on the TF-card.
 
3. '''Application for Recovery:'''
 
* Submit your 'token file' for review.
*
* If approved, WizarPOS will provide a one-time reactivation ('re-active sig') file.
 
4. '''Reactivating the Terminal:'''
 
* Place the 're-active sig' file in the same directory as the 'token file' on the TF-card. (Do not delete the 'token file').
*
* Restart the terminal.
*
* Successful operation will allow the system to boot and function normally.

Revision as of 20:20, 20 December 2023

What Causes the Terminal to Trigger

  • Disassembly: Attempting to disassemble the terminal.
  • Physical Damage: Dropping or breaking the terminal.


Consequences of a Triggered Terminal

When the terminal detects tampering or damage:

  • It will initiate a tamper event.
  • All payment-related keys are permanently deleted, disabling payment processing.
  • The terminal locks itself and displays a warning: "Tamper detected! Please contact WizarPOS!"


Recovery Process for a Triggered Terminal

1. Reporting the Issue:

Contact WizarPOS sales or support. Provide detailed information about the incident and a 'token file' from the terminal.

2. Obtaining the Token File:

  • Insert a TF-card into the affected terminal.
  • Restart the terminal. It will automatically generate a 'token file' on the TF-card.

3. Application for Recovery:

  • Submit your 'token file' for review.
  • If approved, WizarPOS will provide a one-time reactivation ('re-active sig') file.

4. Reactivating the Terminal:

  • Place the 're-active sig' file in the same directory as the 'token file' on the TF-card. (Do not delete the 'token file').
  • Restart the terminal.
  • Successful operation will allow the system to boot and function normally.
Retrieved from "http://sdkwiki.wizarpos.com/index.php?title=How_to_Understand_Trigger_Events_in_Terminals&oldid=3387"