Abstract: A base transaction User Interface (UI) is provided that provides transaction processing for transactions at transaction terminals. The base UI can be customized through independent and decoupled customization/extension files, which provide specific UI customizations for UI screen content, UI screen styles, UI screen views, UI screen workflows, and UI screen resource functionality. Customizations or extensions are achieved without modifying the base UI. The customizations or extensions are dynamically obtained during execution of the base UI from the corresponding files and processed by the base UI as user-defined custom overrides.

Abstract: A touch field is created around a touchscreen display, the field is in front of a touch surface of the display and the field maps to locations on the display. An operator of a terminal during a transaction is presented with transaction interface screens that are visually rendered on the display. The operator makes interface options selections, performs screen navigation, and provides date entry field inputs by placing the operator's hand within the field without touching the touch surface of the display and making hand poses, hand movements, and/or hand gestures. The poses, movements, and/or gestures are translated into touch actions and touch inputs recognized by the transaction interface and processed as operator-provided input during the transaction.

Abstract: A mobile device establishes an indirect network connection to a User Interface (UI) agent of a terminal. The indirect connection managed as a mobile navigational control session maintained through a server or through the server and a proxy. A keyboard widget/object and a navigation-selection widget/object are rendered within a mobile screen on a display of the mobile device. During the session, a user interacts with the keyboard and/or navigation-selection widgets and corresponding UI key events are forwarded to the UI agent. The UI agent provides the UI key events as Human Interface Device (HID) key events to the terminal causing a transaction interface to update transaction screens being rendered on a transaction display of the terminal during a transaction. The user conducts the transaction at the terminal without touching the transaction display and controls the transaction screens for the transaction via the keyboard and navigational widgets from the mobile device.

Abstract: A touch field is created around a touchscreen display, the field is in front of a touch surface of the display and the field maps to locations on the display. An operator of a terminal during a transaction is presented with transaction interface screens that are visually rendered on the display. The operator makes interface options selections, performs screen navigation, and provides date entry field inputs by placing the operator's hand within the field without touching the touch surface of the display and making hand poses, hand movements, and/or hand gestures. The poses, movements, and/or gestures are translated into touch actions and touch inputs recognized by the transaction interface and processed as operator-provided input during the transaction.

Abstract: A base transaction User Interface (UI) is provided that provides transaction processing for transactions at transaction terminals. The base UI can be customized through independent and decoupled customization/extension files, which provide specific UI customizations for UI screen content, UI screen styles, UI screen views, UI screen workflows, and UI screen resource functionality. Customizations or extensions are achieved without modifying the base UI. The customizations or extensions are dynamically obtained during execution of the base UI from the corresponding files and processed by the base UI as user-defined custom overrides.

Abstract: A base transaction User Interface (UI) is provided that provides transaction processing for transactions at transaction terminals. The base UI can be customized through independent and decoupled customization/extension files, which provide specific UI customizations for UI screen content, UI screen styles, UI screen views, UI screen workflows, and UI screen resource functionality. Customizations or extensions are achieved without modifying the base UI. The customizations or extensions are dynamically obtained during execution of the base UI from the corresponding files and processed by the base UI as user-defined custom overrides.

Abstract: A touch field is created around a touchscreen display, the field is in front of a touch surface of the display and the field maps to locations on the display. An operator of a terminal during a transaction is presented with transaction interface screens that are visually rendered on the display. The operator makes interface options selections, performs screen navigation, and provides date entry field inputs by placing the operator's hand within the field without touching the touch surface of the display and making hand poses, hand movements, and/or hand gestures. The poses, movements, and/or gestures are translated into touch actions and touch inputs recognized by the transaction interface and processed as operator-provided input during the transaction.

Abstract: A mobile device establishes an indirect network connection to a User Interface (UI) agent of a terminal. The indirect connection managed as a mobile navigational control session maintained through a server or through the server and a proxy. A keyboard widget/object and a navigation-selection widget/object are rendered within a mobile screen on a display of the mobile device. During the session, a user interacts with the keyboard and/or navigation-selection widgets and corresponding UI key events are forwarded to the UI agent. The UI agent provides the UI key events as Human Interface Device (HID) key events to the terminal causing a transaction interface to update transaction screens being rendered on a transaction display of the terminal during a transaction. The user conducts the transaction at the terminal without touching the transaction display and controls the transaction screens for the transaction via the keyboard and navigational widgets from the mobile device.

Abstract: A touch field is created around a touchscreen display, the field is in front of a touch surface of the display and the field maps to locations on the display. An operator of a terminal during a transaction is presented with transaction interface screens that are visually rendered on the display. The operator makes interface options selections, performs screen navigation, and provides date entry field inputs by placing the operator's hand within the field without touching the touch surface of the display and making hand poses, hand movements, and/or hand gestures. The poses, movements, and/or gestures are translated into touch actions and touch inputs recognized by the transaction interface and processed as operator-provided input during the transaction.

Abstract: A base transaction User Interface (UI) is provided that provides transaction processing for transactions at transaction terminals. The base UI can be customized through independent and decoupled customization/extension files, which provide specific UI customizations for UI screen content, UI screen styles, UI screen views, UI screen workflows, and UI screen resource functionality. Customizations or extensions are achieved without modifying the base UI. The customizations or extensions are dynamically obtained during execution of the base UI from the corresponding files and processed by the base UI as user-defined custom overrides.