C7
CDOL1 Related Data LengthCDOL1 Related Data Length is an M/Chip-proprietary single byte stating the length of data related to CDOL1 (8C, covered earlier) that the card uses during the first GENERATE AC - a bookkeeping field specific to how M/Chip's own implementation of the CDOL mechanism tracks the data it's working with, rather than a core EMV concept. Because CDOL1 itself is already a variable-length, self-describing tag-and-length list, a terminal doesn't strictly need C7 to correctly build or parse a CDOL1-driven request - C7's role is internal to how M/Chip's own card-side logic manages that data, which is why a generic EMV implementation typically doesn't need to interpret it beyond recognising its presence. Consistent with the rest of this small M/Chip-proprietary cluster, its source citation in the underlying acervo carries a verificar vigencia flag, preserved unchanged rather than promoted to confirmed. See Mastercard M/Chip 4 Card Application Specification.
Interactive decoder
Paste a hex value for this tag to decode it in your browser. Nothing is sent anywhere.
Binary (1): 06
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 06
Related tags
Properties
| Tag | C7 |
|---|---|
| Name | CDOL1 Related Data Length |
| Format | Binary |
| Length | 1 bytes |
| Source | Card (ICC) |
| Templates | — |
| Books | Mastercard M/Chip 4 Card Application Spec |
Frequently asked questions
- What is EMV tag C7?
- CDOL1 Related Data Length is an M/Chip-proprietary single byte stating the length of data related to CDOL1 (8C, covered earlier) that the card uses during the first GENERATE AC - a bookkeeping field specific to how M/Chip's own implementation of the CDOL mechanism tracks the data it's working with, rather than a core EMV concept. Because CDOL1 itself is already a variable-length, self-describing tag-and-length list, a terminal doesn't strictly need C7 to correctly build or parse a CDOL1-driven request - C7's role is internal to how M/Chip's own card-side logic manages that data, which is why a generic EMV implementation typically doesn't need to interpret it beyond recognising its presence. Consistent with the rest of this small M/Chip-proprietary cluster, its source citation in the underlying acervo carries a verificar vigencia flag, preserved unchanged rather than promoted to confirmed. See Mastercard M/Chip 4 Card Application Specification.
- What format and length does EMV tag C7 use?
- Tag C7 uses the Binary format and is normally 1 bytes long.
- Is tag C7 provided by the card or the terminal?
- Tag C7 (CDOL1 Related Data Length) is provided by the Card (ICC).
Sources
- MChip4 V1.1 Card Application Specifications for Debit and Credit (Oct06), p. 544
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.