Previous topicNext topic
 XXXX Help
Help > Modules > pinPad >

Notice:there are three key modules of pinpad. The former two modules are suggested.

1.Single application key module: the uppper do not need to care about the index of the main key and work key.

2.Multiple application key module: Simutaneous usage of ten application is supported at present. And the application only need to keep the index of main key, the index of work key can be ignored.

3.Completed user-defined key module. All the key index need to be kept. And this module is not suggested.

 

pinPad module includes key loading and key entering.

Key type is defined in the constant class "com.base win.define.KeyType"

 /**
  * pin key
  */
 public static final int PIN_KEY = 1;
 /**
  * track key
  */
 public static final int TRACK_KEY = 2;

 /**
  * mac key
  */
 public static final int MAC_KEY = 3;

 /**
  * loading key type of pinpad
  */
 public static final int PED_TMK = 0X02;//main key
 public static final int PED_TPK = 0X03;//pin key
 public static final int PED_TAK = 0X04;//mac key
 public static final int PED_TDK = 0X05;//track encrypted key

Notice of Pos security modules:

Shield of power key:

It is suggested to shield power key when sdk interface is used in transaction and some sensitive operations. And the key should be recovered when  other operations is switched, or problems are likely to be occurred.

Example:

    1.When pin pad is called in the transaction, screen-off and low-voltage alert dialog will cause that the pin pad can not be closed and then stop the transaction process.

    2.Print process may be interrupted d by the screen-off operation.

    3.power key failure,AppUtil.TransStart() is called but power key is not recovered.

Application

Power key should be shielded in the transaction and print process and other processes that may be affected by screen-off operation.

Use:

    if  the short click function of power and the alert dialog need to be shielded, AppUtil.TransStart() can be called. It can be recorved by calling AppUtil.TransEnd().

< !--EndFragment-- >