> For the complete documentation index, see [llms.txt](https://sandbox-docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sandbox-docs.verifone.com/s-adk-5.1-programmers-guide/readme/developing_applications/pg_package_signing/pg_fst.md).

# File Signing Tool (FST)

* [Preface](#sec_fst_preface)
* [Overview](#sec_fst_overview)
* [Signing Card](#sec_fst_signing_card)
* [Installation and Set-up](#sec_fst_installation)
* [Start Signing Process](#sec_fst_start_signing)

## Preface <a href="#sec_fst_preface" id="sec_fst_preface"></a>

This document is for programmers and users who want to understand how to install and use VeriShield File Signing Tool (FST).

## Overview <a href="#sec_fst_overview" id="sec_fst_overview"></a>

VeriShield File Signing Tool (FST) is the tool used to sign Software Product binary files prior to installation on a Verifone terminal. The FST tool is for Windows only. This section describes the details of setting up the FST environment. It includes setting up the tools which are necessary for signing the applications.

{% hint style="warning" %}
The FST is offered for use on Trident devices (ADK 4.4 and upper), and on Engage devices that have ADK 4.4, 4.6, or 4.7. On Engage devices which have ADK 4.8 and upper ADK version, the Online Signing Portal must be used instead.
{% endhint %}

## Signing Card <a href="#sec_fst_signing_card" id="sec_fst_signing_card"></a>

The application signing card for V/OS and V/OS2 is the same:

![](/files/yvQGwSfI35JO9xncwopB)

It is used for signing the CertApp. To sign drivers, you need a different (OS) signing card. This card only works for V/OS and V/OS2.

## Installation and Set-up <a href="#sec_fst_installation" id="sec_fst_installation"></a>

1. Install FST (you can find the latest installation file on DevNet under Downloads/Freeware Tools & Utilities/General: VeriShield File Signing Tool)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>This setup is required only if you do not have FST or you have FST older than 07.05.00. Insert the card reader to the PC before installation.</p></div>
2. Run the FST Setup File and follow the wizard to complete the installation.
3. Run FST application, follow the wizard, and configure 2 users:
   * Select "User Management" ![](/files/HpqIUqQEFmeuj196xY3y)
   * Add Officer 1: Select "Add" to add the details of Officer 1 ![](/files/CtfMspK2GfNvzMUYfMnE)
   * Enter Officer 1 details with password and press "Ok"
   * Add Officer 2: Select "Add" to add the details of Officer 2
   * Enter Officer 2 details with password and press "Ok"
   * Press "Close"
4. Log in to FST:
   * Select File/Login ![](/files/lxAvTIrNhvCcsEeWoNaR)
   * Follow the wizards ![](/files/0pR5pngjxuwB2nlu2dSA)
   * Change Officer 1 and Officer 2 passwords to continue

## Start Signing Process <a href="#sec_fst_start_signing" id="sec_fst_start_signing"></a>

1. To start the signing process, the "Sign File - Command Line" should be selected: ![](/files/CwZcbXa3mnce3xtlw6Wi)
2. Select security level: ![](/files/RPDP2NVDtN7smsrNC9Lt)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If a device is a production unit then select "Secured". If an <a href="/pages/jTI4NwkoMjdjuYeoRVBh#sec_device_mode_conversion_using">APP-DEV</a> unit then, select "TEST" as security level and choose the appropriate platform (V/OS or V/OS2) from the dropdown.</p></div>
3. Enter the PIN of Authority Officer 1 and press "OK": ![](/files/XhG2SrOKCNxJfssAbqKL)
4. Enter the PIN of Authority Officer 2 and press "OK"
5. Keep this signing service running before signing the application. ![](/files/7Y1Z6QSRh6Qmg6NFrkXX)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>This service is required for signing the package.</p></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sandbox-docs.verifone.com/s-adk-5.1-programmers-guide/readme/developing_applications/pg_package_signing/pg_fst.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.