> 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.md).

# User Guide (P400)

***

{% columns %}
{% column %}

<figure><img src="/files/Mw4MjiBiEjM8KBG1mgHw" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

{% endcolumn %}

{% column %}
**Version:**\
**Date:**
{% endcolumn %}

{% column %}
1.0.0\
Feb 2026
{% endcolumn %}
{% endcolumns %}

## Reference documents

{% content-ref url="/pages/b4356e67933eeeb1723f245163653eed84cb79b7" %}
[Key import](/kld/key-information/key-import.md)
{% endcontent-ref %}

## Introduction

The Verifone Key Loading Device (VKLD) is a device used for loading security-sensitive keys to a Key Receiving Device (KRD) such as Trinity and Neo payment Terminals.

The Verifone KLD is an Engage P400 (or P400 Plus) device running the KLD application software.

This document describes how to setup and use a Verifone KLD.

We highly recommend reading [Key Concepts](/kld/kld-user-guide/user-guide-p400/key-concepts.md) before continuing.

## Supported Key Types

<table><thead><tr><th width="232">Key Type</th><th>Supported</th></tr></thead><tbody><tr><td>DUKPT BDK Keys</td><td>2TDEA</td></tr><tr><td>Master Session Keys</td><td>2TDEA, 3TDEA, AES-128, AES-192, AES-256</td></tr><tr><td>Fixed Keys</td><td>2TDEA, 3TDEA, AES-128, AES-192, AES-256</td></tr><tr><td>DUKPT Initial Keys</td><td>2TDEA</td></tr></tbody></table>

## Supported Target Terminal Platforms

Currently this Verifone KLD product supports target terminals that fall under 3 specific platforms, namely:

* Trinity (Android)
* Neo
* Victa

{% content-ref url="/spaces/dijxZlL1xtgpr7dUOWO8/pages/edrAnh6CnfRxPzKuyzhM" %}
[Copyright](/terms-and-conditions/copyright-and-warranty/copyright-liability-warranty-etc/copyright.md)
{% endcontent-ref %}


---

# 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.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.