> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-inside-emv/configuring-emv/advanced-configuration/capk-configuration.md).

# CAPK Configuration

{% hint style="info" %}
*The CAPK configuration area is read-only. There is no action required at the site level to create or maintain these keys.*
{% endhint %}

CAPKs are specific to each card brand and are used by the EMV cryptographic functions during EMV processing. Keys are set to expire, however each FEP has a mechanism to ensure keys are kept current.

**Ensure that when EMV is being enabled, CAPKs are listed in the CAPK Configuration Table.**

{% hint style="info" %}
*Contact the Helpdesk or your VASC if no CAPKs are listed. CAPK errors will compromise system functionality.*
{% endhint %}

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/Fn0RkYKf5er80t3Hyu6P/Unknown%20image)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-inside-emv/configuring-emv/advanced-configuration/capk-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
