9F23
Upper Consecutive Offline LimitUpper Consecutive Offline Limit is the hard ceiling on the same consecutive-offline-transaction count its sibling, the Lower Consecutive Offline Limit (9F14), starts watching more gently: once the number of transactions approved offline in a row reaches this threshold, the card's own logic is expected to force the next transaction online regardless of amount or any other condition, precisely because too many consecutive offline approvals is itself a risk signal independent of any single transaction's specifics. It's related to the same Application Transaction Counter (9F36) both consecutive-offline tags ultimately depend on to know how many transactions have actually occurred. This tag exists for the same structural reason the Terminal Floor Limit (9F1B, covered earlier) does: an amount-based floor limit alone can't catch a pattern of many small offline transactions that each individually stay under the floor but that collectively represent exactly the kind of unmonitored offline activity an issuer wants bounded - 9F23 is the frequency-based backstop the amount-based one can't provide on its own. 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 (1): 0A
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 0A
Properties
| Tag | 9F23 |
|---|---|
| Name | Upper Consecutive Offline Limit |
| Format | Binary |
| Length | 1 bytes |
| Source | Card (ICC) |
| Templates | 70, 77 |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 9F23?
- Upper Consecutive Offline Limit is the hard ceiling on the same consecutive-offline-transaction count its sibling, the Lower Consecutive Offline Limit (9F14), starts watching more gently: once the number of transactions approved offline in a row reaches this threshold, the card's own logic is expected to force the next transaction online regardless of amount or any other condition, precisely because too many consecutive offline approvals is itself a risk signal independent of any single transaction's specifics. It's related to the same Application Transaction Counter (9F36) both consecutive-offline tags ultimately depend on to know how many transactions have actually occurred. This tag exists for the same structural reason the Terminal Floor Limit (9F1B, covered earlier) does: an amount-based floor limit alone can't catch a pattern of many small offline transactions that each individually stay under the floor but that collectively represent exactly the kind of unmonitored offline activity an issuer wants bounded - 9F23 is the frequency-based backstop the amount-based one can't provide on its own. See EMV 4.4 Book 3.
- What format and length does EMV tag 9F23 use?
- Tag 9F23 uses the Binary format and is normally 1 bytes long.
- Is tag 9F23 provided by the card or the terminal?
- Tag 9F23 (Upper Consecutive Offline Limit) is provided by the Card (ICC).
Sources
- EMV_v4.4_Book_3_Application_Specification, p. 161
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.