> For the complete documentation index, see [llms.txt](https://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://docs.verifone.com/kld/kld-user-guide/user-guide-p400/verifone-kld-ui-description/upload-keys-to-target-terminal.md).

# Upload Keys (to target Terminal)

* Make sure your target terminal and the KLD are connected to network (with DCHP server). You can use Ethernet or WiFi.
* If you try to upload keys with network issues, the KLD attempt 3 times (20 seconds each) before showing "KRD Not found" error.
* This menu lets the user to send (upload) keys to the target terminal.
* If the uploading of key fails, the target terminal must be rebooted to retry key loading again.
* In the dialog below, select the reference set. The "Default" reference is automatically selected as shown. If you want to select a different reference set, click the drop down list box and select the reference set.

![](/files/6c78232c0b681047fdce3ac9b4f0380123ca564f)

* Select "Send" and wait for the Key upload to complete.

![](/files/4df6faac37ebd5d9536407edba8134a9d7d50861)

* If you have lot keys in a Key lists, it may take few extra seconds to read these big files and send the keys and delete the sent keys.
  * For example, we tested with Master session key lists. There were 11 keys lists, each list containing about 1500 keys.
    * The KLD will pick one key from each of these 11 lists and send them to the terminal and delete that key from the respective lists.
      * It took about 60 to 70 seconds to upload the 11 keys.
* After sending the keys, there will be status dialog to show results. The dialog is shown below. If there are errors, error code will be listed, and the user will have to export the KLD logs to see more details.

![](/files/f77c6ba54199243cf86281aba7e2e0a41b8e57b4)


---

# 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://docs.verifone.com/kld/kld-user-guide/user-guide-p400/verifone-kld-ui-description/upload-keys-to-target-terminal.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.