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

# Data Types and Shared TLV Data Objects

### Data Types and Shared TLV Data Objects

This section defines the primitive and composed data types, TLV (Tag-Length-Value) data objects, file structures, and cryptographic key formats used throughout the device command set, including track data, display strings, EMV configuration file types (ARQC, ARPC, Batch, CA Public Keys), security parameters, TR‑31 key blocks, certificate and CSR file structures, and card emulation.

{% hint style="success" %}
Applies to: All Dyna Family products
{% endhint %}

### Information in this group

| **Section**                                                                                                                                                                                                                                                                 | **Information available**                                                                                                                                                                                         |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [<mark style="color:red;">**Primitive Data Types**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/primitive-data-types.md)                                                                                    | A list of primitive data types used by TLV data objects.                                                                                                                                                          |
| [<mark style="color:red;">**About Track Data**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/about-track-data.md)                                                                                            | Information about parsing EMV ARQC Type or Merchant Data Container data for each track into individual values embedded in the tracks.                                                                             |
| [<mark style="color:red;">**Display Strings**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/display-strings.md)                                                                                              | A pre-defined set of messages by string ID that the host and device use for various user interface features.                                                                                                      |
| [<mark style="color:red;">**Encryption Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/encryption-type.md)                                                                                              | Information on the key type, variant, and other information the host can use to decrypt encrypted data included in various payloads.                                                                              |
| [<mark style="color:red;">**EMV ARQC Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-arqc-type.md)                                                                                                  | Information on how the device formats ARQC messages.                                                                                                                                                              |
| [<mark style="color:red;">**EMV ARPC Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-arpc-type.md)                                                                                                  | Information on how the device formats ARPC messages                                                                                                                                                               |
| [<mark style="color:red;">**EMV Batch Data Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-batch-data-type.md)                                                                                      | Information on the device formats EMV batch data, such as merchant data and pre-defined EMV batch data tags.                                                                                                      |
| [<mark style="color:red;">**EMV Terminal Configuration Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-terminal-configuration-file-type.md)                                                         | Information on loading this file type to control the behavior of the device’s EMV contact kernel.                                                                                                                 |
| [<mark style="color:red;">**EMV Processing Configuration File Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-processing-configuration-file-type.md)                                                | Information on loading this file type to control the behavior of the device’s EMV kernel.                                                                                                                         |
| [<mark style="color:red;">**EMV Entry Point Configuration File Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-entry-point-configuration-file-type.md)                                              | Information on loading this file type to control the behavior of the device’s EMV kernels.                                                                                                                        |
| [<mark style="color:red;">**EMV Configuration CA Public Keys File Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-configuration-ca-public-keys-file-type.md)                                        | Information on loading this file type to control the behavior of the device’s EMV contact and contactless kernels when the device should support Offline Data Authentication (ODA).                               |
| [<mark style="color:red;">**EMV American Express DRL Configuration Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-american-express-drl-configuration-file-type-not-supported-on-expresspay-4.x.md) | Information on loading  this file type to control the behavior of the device’s American Express contactless kernel when the card sends tag 9F70 and one or more DRL is defined. (Not supported on Expresspay 4.x) |
| [<mark style="color:red;">**Signature Capture File Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/signature-capture-file-type-touch-only.md)                                                           | The signature capture file type produced when the host invokes Request Cardholder Signature - Command 0x1801 (Touch Only)                                                                                         |
| [<mark style="color:red;">**Security Operation Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/security-operation-type.md)                                                                              | This non-TLV data structure consists of four or five bytes that describes a security operation, including the algorithms and methods to be used in that operation.                                                |
| [<mark style="color:red;">**Security Parameters Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/security-parameters-type.md)                                                                            | Information on tags used with security parameters.                                                                                                                                                                |
| [<mark style="color:red;">**Key Information Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/key-information-type.md)                                                                                    | Information on tags used to identify key types.                                                                                                                                                                   |
| [<mark style="color:red;">**NFC UID Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/nfc-uid-type-emv-contactless-only.md)                                                                               | Information on tags used with NFC UID Types. (EMV Contactless Only)                                                                                                                                               |
| [<mark style="color:red;">**GPO Response Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/gpo-response-type-emv-contactless-only.md)                                                                     | Information on tags used with GPORT-1 Types. (EMV Contactless Only)                                                                                                                                               |
| [<mark style="color:red;">**MIFARE Card Data Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/mifare-card-data-type-emv-contactless-only.md)                                                             | Information on tags used with MIFARE Card Data. (EMV Contactless Only).                                                                                                                                           |
| [<mark style="color:red;">**TR-31 Key Block Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/tr-31-key-block-type.md)                                                                                    | Information on tags used with TR-31 Key Blocks.                                                                                                                                                                   |
| [<mark style="color:red;">**DUKPT Key Mapping**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/dukpt-key-mapping.md)                                                                                          | Information on tags used with DUKPT Keys.                                                                                                                                                                         |
| [<mark style="color:red;">**Miniature Certificate Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/miniature-certificate-type.md)                                                                        | Information on tags used with miniature certificates.                                                                                                                                                             |
| [<mark style="color:red;">**Common File Structure**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/common-file-structure.md)                                                                                  | Information on file types that conform to the common file structure format.                                                                                                                                       |
| [<mark style="color:red;">**Certificate File Type**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/certificate-file-types.md)                                                                                 | These file types conform to the Common File Structure format. The File Payload of these files contain a certificate in PEM format.                                                                                |
| [<mark style="color:red;">**Certificate Signing Request (CSR) Files Types**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/certificate-signing-request-csr-file-types.md)                                     | Information on CSR File Types.                                                                                                                                                                                    |
| [<mark style="color:red;">**Card Emulation**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/card-emulation.md)                                                                                                | Card emulation enables a DynaFlex/DynaProx device to simulate a Type 4 smart card.                                                                                                                                |

### See Also

* [<mark style="color:red;">**Messages**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/message-format-and-structure.md) **-->** The basics on messages, what they are, and how they work.&#x20;
* [<mark style="color:red;">**Commands**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/commands.md) **-->** Information on device-level commands&#x20;
* [<mark style="color:red;">**Notifications**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/notifications.md) **-->** Information on notices your device my send and the circumstances under which they send them.&#x20;
* [<mark style="color:red;">**Configurations**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/configuration.md) **-->** Information of configuring your devices in various ways.


---

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