> 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-product-work-flow-steps.md).

# Verifone KLD - Product Work Flow Steps

* **Step 1**: Create a minimum of 2 users to login to the product.
* **Step 2**: Create a Signer Key(CSR copied to the USB drive) and Get the Signer Certificate from Verifone Operations team and Import the signer certificate.
* **Step 3**: Get the CRL from Verifone operations team and import.
* **Step 4**: Create a KEK (and/or KBPK) to import key list into KLD. This step is optional if you are not importing keys through file(s).
* **Step 5**: Create or Import keys as needed (DUKPT-BDK, Fixed, Master Session, DUKPT-Initial Key). Master Session and Initial Keys can be only imported through files through USB.
* **Step 6**: Create a Reference Set.
* **Step 7**: Set a default Reference Set (this step is optional since Step 9 below allows the user to select a reference list on the fly)
* **Step 8**: Connect the KLD and the Target Terminal (where keys are to be loaded) to a network (with DHCP) where they can see each other. Internet is not needed. Just local network is enough. WiFi is supported. Essentially, the KLD will discover a Verifone software agent on the Terminal, get the IP address and send the data (encrypted keys) through this channel.
* **Step 9**: Upload Keys to the Terminal by choosing a reference set if a default one is not set.

*Notes:*

* **Step 3** needs to be done every time there is a new CRL. This can be weekly or monthly or some other interval.
* **Step 1** **through Step 7** is done mostly once (or as needed for new keys, users etc.), except step 3 which is needed frequently as mentioned above.
* **Step 8 and Step 9** are repeated for each target terminal to upload keys. In Step 8, the KLD can be left connected to the network. The terminals are connected/disconnected as needed.
* **Step 10 (Optional)**: Export Key Logs for reference. This log shows which key(s) is(are) sent to which Terminal at what date/time.


---

# 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-product-work-flow-steps.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.