EMV TAG 91-为什么最后两个字节为“ 0010”?

发布于 2025-01-24 14:43:12 字数 95 浏览 6 评论 0 原文

EMV标签91
在下面的示例中,为什么最后两个字节为“ 0010”? 示例:TLV [910ABCF266A64FF136630010] 我需要最大的帮助 谢谢!!!

EMV Tag 91
in the following example, why the last 2 bytes are "0010"?
example: TLV [910ABCF266A64FF136630010]
I need most help
Thanks!!!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

智商已欠费 2025-01-31 14:43:12

标签0x91 发行者身份验证数据属于 MasterCard M/chip 规范。

  • 8个字节是授权响应加密图( arpc )。
  • 2个字节是根据M/芯片规范的ARPC响应代码( RC )。

M/芯片卡发行器设置的 RC 值,并提供其他卡命令以重置其上的一些计数器。

示例标签数据分析如下:

# Cheef's parser.
# Copyright (C) 2008-2022 Aleksandr Shevelev. https://iso8583.info/
# lib   : "/lib/MasterCard/M_Chip/4/" # M/Chip 4 Card Application Specifications
# tool  : "TLVs"

# stat  : 11 nodes, 0 lookup tables, 100.00% passed (1/1)

TLVs:#"910ABCF266A64FF136630010" # M/Chip 4, Tag + Length + Value (TLV) series
- x91:#"910ABCF266A64FF136630010" # M/Chip 4, Issuer Authentication Data
  - tag: "91"
  - len: "0A" #  // 10
  - val:#"BCF266A64FF136630010" # Issuer Authentication Data.
    - ARPC: "BCF266A64FF13663" # Authorization Response Cryptogram
    - RC:#"0010" # ARPC Response Code
      - B01:#"00"
        - n0: "0" # bits 8-5, RFU
        - n1: "0" # bits 4-1, PIN try Counter
      - B02: "10"
        # ___1____ - bit 5, Approve online transaction
        # ____0___ - bit 4, Do NOT update PIN Try Counter
        # _____0__ - bit 3, Reset go online on next transaction
        # ______00 - bits 2-1, Do not update offline counters

This Tag 0x91 Issuer Authentication Data belongs to MasterCard M/Chip specification.

  • 8 bytes is Authorization Response Cryptogram (ARPC).
  • 2 Bytes is ARPC Response Code (RC) according to M/Chip specification.

The RC value set by M/Chip card issuer and provide additional card commands to reset some counters on it.

The example Tag data parsed as followed:

# Cheef's parser.
# Copyright (C) 2008-2022 Aleksandr Shevelev. https://iso8583.info/
# lib   : "/lib/MasterCard/M_Chip/4/" # M/Chip 4 Card Application Specifications
# tool  : "TLVs"

# stat  : 11 nodes, 0 lookup tables, 100.00% passed (1/1)

TLVs:#"910ABCF266A64FF136630010" # M/Chip 4, Tag + Length + Value (TLV) series
- x91:#"910ABCF266A64FF136630010" # M/Chip 4, Issuer Authentication Data
  - tag: "91"
  - len: "0A" #  // 10
  - val:#"BCF266A64FF136630010" # Issuer Authentication Data.
    - ARPC: "BCF266A64FF13663" # Authorization Response Cryptogram
    - RC:#"0010" # ARPC Response Code
      - B01:#"00"
        - n0: "0" # bits 8-5, RFU
        - n1: "0" # bits 4-1, PIN try Counter
      - B02: "10"
        # ___1____ - bit 5, Approve online transaction
        # ____0___ - bit 4, Do NOT update PIN Try Counter
        # _____0__ - bit 3, Reset go online on next transaction
        # ______00 - bits 2-1, Do not update offline counters
冷…雨湿花 2025-01-31 14:43:12

前8个字节是强制性的,并包含加密图。

可选的1-8个字节是专有的。因此,您需要知道您正在使用的付款应用程序(和版本):例如MasterCard M/芯片,American Express AEIPS等。

请参见6.5.4 EMV中的6.5.4外部身份验证4.3书3

The first 8 bytes are mandatory and contain the cryptogram.

The optional 1–8 bytes that follow are proprietary. Therefore, you need to know what payment application (and version) you are using: e.g., Mastercard M/Chip, American Express AEIPS, etc.

See 6.5.4 External Authenticate in EMV 4.3 Book 3

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文