9F13
Last Online Application Transaction Counter (ATC) RegisterLast Online Application Transaction Counter Register is the card's memory of what its own ATC (9F36) was the last time it successfully completed an online authorization - a single reference point the issuer's risk logic uses to measure how far offline the card has since drifted. Compare the two: if the current ATC has only advanced by a small, plausible amount since 9F13 was last updated, the card's offline activity looks normal; if it's jumped by far more transactions than the card's own velocity limits should allow, that gap is one of the stronger cloning or replay signals available, precisely because both numbers come from the card itself rather than from anything the terminal reports. It's the direct counterpart to the PIN Try Counter (9F17) in the card's own risk-state bookkeeping - one tracks transaction velocity since the last online contact, the other tracks verification attempts - and together they're much of what an issuer's offline risk-management logic actually evaluates before deciding whether to let a given card keep transacting offline at all. 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 (2): 0046
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 0046
Properties
| Tag | 9F13 |
|---|---|
| Name | Last Online Application Transaction Counter (ATC) Register |
| Format | Binary |
| Length | 2 bytes |
| Source | Card (ICC) |
| Templates | — |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 9F13?
- Last Online Application Transaction Counter Register is the card's memory of what its own ATC (9F36) was the last time it successfully completed an online authorization - a single reference point the issuer's risk logic uses to measure how far offline the card has since drifted. Compare the two: if the current ATC has only advanced by a small, plausible amount since 9F13 was last updated, the card's offline activity looks normal; if it's jumped by far more transactions than the card's own velocity limits should allow, that gap is one of the stronger cloning or replay signals available, precisely because both numbers come from the card itself rather than from anything the terminal reports. It's the direct counterpart to the PIN Try Counter (9F17) in the card's own risk-state bookkeeping - one tracks transaction velocity since the last online contact, the other tracks verification attempts - and together they're much of what an issuer's offline risk-management logic actually evaluates before deciding whether to let a given card keep transacting offline at all. See EMV 4.4 Book 3.
- What format and length does EMV tag 9F13 use?
- Tag 9F13 uses the Binary format and is normally 2 bytes long.
- Is tag 9F13 provided by the card or the terminal?
- Tag 9F13 (Last Online Application Transaction Counter (ATC) Register) is provided by the Card (ICC).
Sources
- EMV_v4.4_Book_3_Application_Specification, p. 151
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.