D3
Card Risk Management (CRM) Currency CodeCard Risk Management Currency Code is D2's direct sibling: the same Discover D-PAS-proprietary pattern applied to currency instead of country, conceptually parallel to the core Transaction Currency Code (5F2A) it's related to, plus a further tag (9F42, the Application Currency Code) that names the currency the application itself operates in. Like D2, it exists inside Discover's own proprietary risk-management logic rather than as a substitute for any core EMV tag - a card carrying D3 still carries whatever core currency tags a generic terminal already reads, with D3 serving Discover's scheme-specific checks on top of, not instead of, that core data. The practical implication for anyone building multi-scheme tooling is the same one D2 raises: a decoder that only understands core EMV tags will report this card as having no currency-related risk-management data at all, when in fact it has plenty - just not in a tag that decoder knows to look for. Its source citation likewise carries the export's verificar vigencia flag, pending confirmation against the acervo. See Discover D-PAS Connect (Card Application Specification) v2.1.1.
Interactive decoder
Paste a hex value for this tag to decode it in your browser. Nothing is sent anywhere.
Numeric (BCD): 0978
Currency (ISO 4217): EUR (Euro)
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 0978
Currency (ISO 4217): EUR (Euro)
Properties
| Tag | D3 |
|---|---|
| Name | Card Risk Management (CRM) Currency Code |
| Format | Numeric (BCD) |
| Length | 2 bytes |
| Source | Card (ICC) |
| Templates | — |
| Books | Discover D-PAS Connect (Card Application Spec) |
Frequently asked questions
- What is EMV tag D3?
- Card Risk Management Currency Code is D2's direct sibling: the same Discover D-PAS-proprietary pattern applied to currency instead of country, conceptually parallel to the core Transaction Currency Code (5F2A) it's related to, plus a further tag (9F42, the Application Currency Code) that names the currency the application itself operates in. Like D2, it exists inside Discover's own proprietary risk-management logic rather than as a substitute for any core EMV tag - a card carrying D3 still carries whatever core currency tags a generic terminal already reads, with D3 serving Discover's scheme-specific checks on top of, not instead of, that core data. The practical implication for anyone building multi-scheme tooling is the same one D2 raises: a decoder that only understands core EMV tags will report this card as having no currency-related risk-management data at all, when in fact it has plenty - just not in a tag that decoder knows to look for. Its source citation likewise carries the export's verificar vigencia flag, pending confirmation against the acervo. See Discover D-PAS Connect (Card Application Specification) v2.1.1.
- What format and length does EMV tag D3 use?
- Tag D3 uses the Numeric (BCD) format and is normally 2 bytes long.
- Is tag D3 provided by the card or the terminal?
- Tag D3 (Card Risk Management (CRM) Currency Code) is provided by the Card (ICC).
Sources
- DGN_D-PAS_Connect_Card_CT_Spec_v2.1.1_20240304, p. 381
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.