D1
Currency Conversion TableCurrency Conversion Table is the actual conversion data M/Chip's own risk logic uses to translate a transaction's currency into whatever currency the card's cumulative offline limits (CA and CB, both covered earlier) are actually expressed in - the concrete lookup mechanism behind the same currency-comparison problem the core Reference Currency tags (9F3A through 9F3D, covered earlier) solve at the terminal level, just implemented as M/Chip's own card-resident table rather than a terminal-side computation. It's related to the Currency Risk Management Currency Code (C9, covered earlier), which names the currency this table's conversions are actually keyed to. Because this is proprietary M/Chip conversion data rather than a core EMV mechanism, a terminal doesn't typically need to read or interpret D1 directly - the conversion happens inside the card's own M/Chip risk evaluation, with D1 being internal state to that evaluation rather than a value the terminal acts on. Its source citation carries the same verificar vigencia flag as its M/Chip siblings in this cluster. 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 (5): 0102030405
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 0102030405
Related tags
Properties
| Tag | D1 |
|---|---|
| Name | Currency Conversion Table |
| Format | Binary |
| Length | variable |
| Source | Card (ICC) |
| Templates | — |
| Books | Mastercard M/Chip 4 Card Application Spec |
Frequently asked questions
- What is EMV tag D1?
- Currency Conversion Table is the actual conversion data M/Chip's own risk logic uses to translate a transaction's currency into whatever currency the card's cumulative offline limits (CA and CB, both covered earlier) are actually expressed in - the concrete lookup mechanism behind the same currency-comparison problem the core Reference Currency tags (9F3A through 9F3D, covered earlier) solve at the terminal level, just implemented as M/Chip's own card-resident table rather than a terminal-side computation. It's related to the Currency Risk Management Currency Code (C9, covered earlier), which names the currency this table's conversions are actually keyed to. Because this is proprietary M/Chip conversion data rather than a core EMV mechanism, a terminal doesn't typically need to read or interpret D1 directly - the conversion happens inside the card's own M/Chip risk evaluation, with D1 being internal state to that evaluation rather than a value the terminal acts on. Its source citation carries the same verificar vigencia flag as its M/Chip siblings in this cluster. See Mastercard M/Chip 4 Card Application Specification.
- What format and length does EMV tag D1 use?
- Tag D1 uses the Binary format and is normally variable long.
- Is tag D1 provided by the card or the terminal?
- Tag D1 (Currency Conversion Table) is provided by the Card (ICC).
Sources
- MChip4 V1.1 Card Application Specifications for Debit and Credit (Oct06), p. 553
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.