> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-terminal-configuration-file-type.md).

# EMV Terminal Configuration File Type

The host uses **Start Send File to Device (Unsecured)**  - **Command 0xD812** to load this file type to control the behavior of the device’s EMV contact kernel. The configuration loaded using this file type must be designed to work together with all instances of **EMV Processing Configuration File Type** and **EMV Entry Point Configuration File Type** the host loads into the device.

MagTek provides tools that allow these settings to be loaded using a Microsoft Excel spreadsheet for more convenient authoring, review, and change tracking. For a reference sample spreadsheet that contains EMVCo approved configurations, contact MagTek Support Services.

This document shows one example of the available Contact Level 2 certified configurations (***DynaFlex C01, Merchant, Attended, ODA***). To see which configurations are supported on the devices you are using, see the list of **Vendor Config IDs** in the device’s ***Letter of Approval for Contact Level 2*** posted in the list of ***Approved / Evaluated*** products on the EMVCo web site. For detailed descriptions of the tags included in this file type, including possible valid values and their effects on device behavior, see ***EMV Integrated Circuit Card Specifications for Payment Systems v4.3***.

## Table EMVTCF-1 - EMV Configuration Terminal File Type

<table><thead><tr><th>Tag</th><th>Len</th><th>Value / Description</th><th width="76">Typ</th><th width="78.66668701171875">Req</th><th width="101.33331298828125">Example</th></tr></thead><tbody><tr><td>File Type Version</td><td>One byte indicating the version of the file type format being used.</td><td></td><td></td><td></td><td>0xAA</td></tr><tr><td>SHA-1 Hash</td><td>20-byte hash of all values that follow.</td><td></td><td></td><td></td><td></td></tr><tr><td>9F1A</td><td>02</td><td>Terminal Country Code</td><td>B</td><td>R</td><td>08 40</td></tr><tr><td>DF79</td><td>01</td><td>Cardholder Confirmation</td><td>B</td><td>R</td><td>01</td></tr><tr><td>9F35</td><td>01</td><td>Terminal Type</td><td>B</td><td>R</td><td>21</td></tr><tr><td>DF0A</td><td>01</td><td>EMV Contact Supported</td><td>B</td><td>R</td><td>01</td></tr><tr><td>9F33</td><td>03</td><td>Terminal Capabilities</td><td>B</td><td>R</td><td>E0 28 C8</td></tr><tr><td>9F40</td><td>05</td><td>Additional Terminal Capabilities</td><td>B</td><td>R</td><td>EF 80 F0 A0 01</td></tr><tr><td>DF55</td><td>01</td><td>EMV Contactless Supported</td><td>B</td><td>R</td><td>01</td></tr><tr><td>DF0B</td><td>01</td><td>Magnetic Stripe Supported</td><td>B</td><td>R</td><td>01</td></tr><tr><td>DF27</td><td>01</td><td>Time allocated to enter a PIN</td><td>B</td><td>R</td><td>0A</td></tr><tr><td>DF06</td><td>01</td><td>Batch / Online Data Capture managed</td><td>B</td><td>R</td><td>01</td></tr><tr><td>DF08</td><td>00</td><td>Advice Managed</td><td>B</td><td>R</td><td>00</td></tr><tr><td>DF7A</td><td>01</td><td>PSE Supported</td><td>B</td><td>R</td><td>01</td></tr><tr><td>DF0D</td><td>00</td><td>AutoRun Mode</td><td>B</td><td>R</td><td>00</td></tr><tr><td>DF10</td><td>03</td><td>Predefined amount for AutoRun mode</td><td>B</td><td>R</td><td>00 00 00</td></tr><tr><td>DF7B</td><td>01</td><td>PIN Bypass Supported</td><td>B</td><td>R</td><td>00</td></tr><tr><td>DF07</td><td>01</td><td>Referral Managed</td><td>B</td><td>R</td><td>01</td></tr><tr><td>DF09</td><td>01</td><td>Default TAC supported when regular TACs are not present</td><td>B</td><td>R</td><td>01</td></tr><tr><td>DF73</td><td>05</td><td>Default TAC default</td><td>B</td><td>R</td><td>00 00 00 00 00</td></tr><tr><td>DF74</td><td>05</td><td>Default TAC denial</td><td>B</td><td>R</td><td>00 00 00 00 00</td></tr><tr><td>DF75</td><td>05</td><td>Default TAC online</td><td>B</td><td>R</td><td>00 00 00 00 00</td></tr><tr><td>DF53</td><td>01</td><td>Random Transaction Selection not supported</td><td>B</td><td>R</td><td>00</td></tr><tr><td>DF54</td><td>01</td><td>Velocity Checking not supported</td><td>B</td><td>R</td><td>00</td></tr><tr><td>DF7C</td><td>01</td><td>CDA Mode</td><td>B</td><td>R</td><td>01</td></tr></tbody></table>


---

# 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://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-terminal-configuration-file-type.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.