> 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/keys.md).
# Keys
Keys Dialog allows the user to Manage Keys.
* The above dialog shows list of keys.
* Keys can be deleted by clicking the "X" button to the right of menu items.
* By selecting a key, one can edit the key names. Editing keys is limited since key values and algorithms cannot be changed.
* User can delete the key and reimport it if key value or the algorithm needs a change.
* Key Name can be edited.
* The Import button is used to Import Keys through USB thumb drive or as components through the UI. Import process is described below.
* If you single click on the key or key list in the above dialog, it shows the Key or Key List information dialog as shown below. If your key list has lot of keys (say 10,000 keys), it will take a few seconds to display the info dialog. Please wait. User can also edit the Key List Name at the top. Rest of the information cannot be edited.
### **Import**
* Keys can be imported through UI or through files on USB.
* In the Import dialog below, "Enter Components" option allows the user to create keys through UI and the "Import from File" option allows the user to import keys through files on USB.
* See "Import Keys Through UI" section below to create/import keys through UI. See "Import Key Files Through USB" section below to import keys from file.
### **Import Keys Through UI**
* Only BDK and Fixed Keys can be imported through UI. Master Session and Initial Keys can be imported only through files on USB.
* Importing keys through UI does not require KEK.
* KEK name is maximum 32 characters long
* Enter the Plain key components as HEX values.
* The number of key components can be 2 or 3 or 4.
* Each component needs a component check value to make sure key values entered are correct. **If you do not have component check values, user will be asked to re-enter the key values**.
* Component Check Value (CCV) is similar to Key Check Value (KCV), but meant only for that component.
### Create Keys
* Enter a Key name, select the key type, select an algorithm, select the number of key components and enter the plain key HEX values through component entry dialog and Save the key.
* For BDK keys, KSI is a required field. The DID start and End values are optional. Default values are 1 and 524287
 
### **Import Key Edits**
* Key data cannot be edited.
* Key Name can be changed (edited) for all key types.
* On the Key List dialog, click on the key to edit the Key Name.
#### BDK Keys:
In case of BDK Keys, user can edit Key Name, KSI and the DID start and End Values as shown below.
The DID start value is the current DID value. User can only increase the start value (current value) and decrease the end value. Start value cannot be > End value.
### **Import Keys Files Through USB**
* Before using this feature, read the document [Key import](/kld/key-information/key-import.md).
* All key types (BDK, IK, Master Session and Fixed) can be imported through file on USB.
* The BDK and Fixed are keys treated as individual keys. User can see, edit and delete individual keys.
* Master Session and Initial Keys are treated as key lists. A key list can have many keys (even 2000 keys) and all are treated as single set (Key list).
* User can see the Key List name, rename the key list name and delete the key list but cannot see or modify the individual keys inside the key list since there can be too many keys in a list to show on the UI
* Steps to import keys through USB thumb drive
* Select the key type (BDK or IK or Master or Fixed) as shown in the first dialog below.
* If it’s a Key List (Master or IK), select if you want to create a new key list or if you want refill an existing key list as shown below in the second and third dialog below.
* Select a KEK from the list box as shown in the fourth dialog.
* Select the data format in the key file. It can be TR-31 or Cryptogram.
* **For cryptogram format, If the KEK is AES, then KEY cannot be 3TDEA since padding scheme is unknown and is not assumed.**
* Select "Import" button and wait.
* Depending on the number of Key Lists and number of keys in each key list file, it may take few seconds - 5 minutes to import the key data.
* When the import is completed there will be an import statistics/results dialog. Pay attention to the "Total Lines" and the "Lines With Error".
* If there are error lines, action is needed. Refer to the document [Key import](/kld/key-information/key-import.md).
  
 
---
# 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/keys.md?ask=&goal=
```
`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.