9F04
Amount, Other (Binary)Amount, Other (Binary) is the binary-encoded twin of Amount, Other (9F03, covered earlier): the same secondary amount concept, most commonly the cashback portion of a transaction, but expressed as a 4-byte binary value instead of BCD digits. EMV keeps both encodings available because different downstream consumers - some card kernels, some host integrations - expect one format or the other, and a terminal generally has to be prepared to populate whichever one a given card's CDOL actually requests rather than assuming either is universal. It's related to both 9F03 and the primary Amount, Authorised (9F02), and like its BCD sibling, a card that doesn't request it in its CDOL simply never sees a populated 9F04 - its absence from a given transaction's data means it wasn't asked for, not that anything went wrong. A terminal library that only implements one of the two amount-encoding formats will work correctly against cards that happen to request that format and fail, opaquely, against cards that request the other. See EMV 4.4 Book 3.
Interactive decoder
Paste a hex value for this tag to decode it in your browser. Nothing is sent anywhere.
Binary (4): 00000500
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 00000500
Properties
| Tag | 9F04 |
|---|---|
| Name | Amount, Other (Binary) |
| Format | Binary |
| Length | 4 bytes |
| Source | Terminal |
| Templates | — |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 9F04?
- Amount, Other (Binary) is the binary-encoded twin of Amount, Other (9F03, covered earlier): the same secondary amount concept, most commonly the cashback portion of a transaction, but expressed as a 4-byte binary value instead of BCD digits. EMV keeps both encodings available because different downstream consumers - some card kernels, some host integrations - expect one format or the other, and a terminal generally has to be prepared to populate whichever one a given card's CDOL actually requests rather than assuming either is universal. It's related to both 9F03 and the primary Amount, Authorised (9F02), and like its BCD sibling, a card that doesn't request it in its CDOL simply never sees a populated 9F04 - its absence from a given transaction's data means it wasn't asked for, not that anything went wrong. A terminal library that only implements one of the two amount-encoding formats will work correctly against cards that happen to request that format and fail, opaquely, against cards that request the other. See EMV 4.4 Book 3.
- What format and length does EMV tag 9F04 use?
- Tag 9F04 uses the Binary format and is normally 4 bytes long.
- Is tag 9F04 provided by the card or the terminal?
- Tag 9F04 (Amount, Other (Binary)) is provided by the Terminal.
Sources
- EMV_v4.4_Book_3_Application_Specification, p. 136
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.