diff --git "a/testdataset" "b/testdataset" deleted file mode 100644--- "a/testdataset" +++ /dev/null @@ -1,5057 +0,0 @@ -[ - { - "id": "VI_MC_0001", - "brand": "VISA", - "type": "contact", - "category": "Testing", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70150877432D1026706D7E805DA846A32C3BB81E3C299000\nC:00B2020C00 \u2192 R:7016B62179273C8EB5BB682575EC87A171AC826A6FCE9000\nC:80AE800000 \u2192 R:770A9F260848478DCB74F213459F3602D2CC9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.337736Z" - } - }, - { - "id": "VI_MC_0002", - "brand": "VISA", - "type": "contact", - "category": "CVM", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701538A39D5E0853964B50AF03B971722F244F58D6699000\nC:00B2020C00 \u2192 R:7016CBEE3772A077021721A278F64F7FD633DBDDE1319000\nC:80AE800000 \u2192 R:770A9F2608CA3766E4D58E72E39F360210279000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.337789Z" - } - }, - { - "id": "VI_MC_0003", - "brand": "VISA", - "type": "contactless", - "category": "Issuer Scripts", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70156C15C0C8E9DF469611A11F5125227C3712DA86A79000\nC:00B2020C00 \u2192 R:70168C49EA20E32684B27B95E909348334896A68F8129000\nC:80AE800000 \u2192 R:770A9F2608D810A485ED03241B9F36024D419000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.337831Z" - } - }, - { - "id": "VI_MC_0004", - "brand": "VISA", - "type": "contact", - "category": "Field 55", - "question": "Why did the terminal queue a reversal after approval? (Scenario 4)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B673BD4755D05AD7853C1F76EB97706CA828BCA09000\nC:00B2020C00 \u2192 R:7016385813DBAD3C681D06BD2AA399DAC946DC59C0999000\nC:80AE800000 \u2192 R:770A9F26086DAEEE6F529A27979F360264019000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.337880Z" - } - }, - { - "id": "VI_MC_0005", - "brand": "VISA", - "type": "contact", - "category": "Terminal Configuration", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 5)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015ED6CFC7403D75E173E4EAEDE5FE878F78E2978AA9000\nC:00B2020C00 \u2192 R:70162447C462DDAED16DC0CF0B9CD7F78DF0CAC5E40C9000\nC:80AE800000 \u2192 R:770A9F260802D4E518CA6EAAC89F3602D82F9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.337918Z" - } - }, - { - "id": "VI_MC_0006", - "brand": "VISA", - "type": "contact", - "category": "Field 55", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B7210760474F36E8B5359309CC6273931BDB2A0D9000\nC:00B2020C00 \u2192 R:7016F3DBE4D58FED8A728E7ECA0FA5F6B8A880627DF79000\nC:80AE800000 \u2192 R:770A9F2608FFE0297C79BFBDAB9F3602E8989000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.337955Z" - } - }, - { - "id": "VI_MC_0007", - "brand": "VISA", - "type": "contact", - "category": "Settlement", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 7)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015A3566F893697B590481194F309FFEA518F32CF219000\nC:00B2020C00 \u2192 R:7016449273D7CEE9D9136682575250DEF91799E2786D9000\nC:80AE800000 \u2192 R:770A9F26083748421599E3E9C89F3602FE219000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338009Z" - } - }, - { - "id": "VI_MC_0008", - "brand": "VISA", - "type": "contactless", - "category": "Integration", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 8)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70150270815FE85DF2FBDAA35ADF9C1E2A8A3C0ED16B9000\nC:00B2020C00 \u2192 R:7016FE16849EF307590D273E34F98DFF7E4C6428DA809000\nC:80AE800000 \u2192 R:770A9F260899F4EFBACEA67C7D9F36021AFC9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338061Z" - } - }, - { - "id": "VI_MC_0009", - "brand": "VISA", - "type": "contact", - "category": "Issuer Scripts", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F14A3E3E04D42F8AC2ACAF127972D33E5901A19B9000\nC:00B2020C00 \u2192 R:7016BD47D5552C7F47E8E80E952EB9D8E96CF37CB9909000\nC:80AE800000 \u2192 R:770A9F2608C801F97B7684319E9F36021B429000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338107Z" - } - }, - { - "id": "VI_MC_0010", - "brand": "VISA", - "type": "contactless", - "category": "Terminal Configuration", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015564B858F9A3E247CB2C083EB8CB37F0A72E9D3419000\nC:00B2020C00 \u2192 R:701619F3374CEBD4D3FD81B6EE7B3BB1C863E2601A749000\nC:80AE800000 \u2192 R:770A9F260862667A40844853049F36020B7A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338146Z" - } - }, - { - "id": "VI_MC_0011", - "brand": "VISA", - "type": "contact", - "category": "Settlement", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70154D32FEB3E719E01FCD3FE22A4248AC9ED336DE7D9000\nC:00B2020C00 \u2192 R:7016AECD3ADA8B4F2222D3B41A3DBD199B364F73BB389000\nC:80AE800000 \u2192 R:770A9F26087D080589AB054C249F3602026C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338183Z" - } - }, - { - "id": "VI_MC_0012", - "brand": "VISA", - "type": "contact", - "category": "Security", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B9A2145128EDFED863BD39F917C10696489A30FD9000\nC:00B2020C00 \u2192 R:701654C7B2C1D0E2ADCD93C0A5EB2D37DC2C9A7A52369000\nC:80AE800000 \u2192 R:770A9F2608BB4734865425FEEA9F3602A4E29000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338219Z" - } - }, - { - "id": "VI_MC_0013", - "brand": "VISA", - "type": "contactless", - "category": "Issuer Scripts", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 13)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701581B29EE11B922CE1E6AF41E3A2517EE5BB9CDA1A9000\nC:00B2020C00 \u2192 R:70162A3C984A24B9C429CA42DB0B956AF67442931A4C9000\nC:80AE800000 \u2192 R:770A9F26084555E1DB7E9E779F9F36026BEE9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338259Z" - } - }, - { - "id": "VI_MC_0014", - "brand": "VISA", - "type": "contactless", - "category": "Issuer Scripts", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701556481FB339258E4D27EB0D1CB7C2B70A3A4419F49000\nC:00B2020C00 \u2192 R:7016FE020864D3979317DE23F0749D0B7D52B20CF1CB9000\nC:80AE800000 \u2192 R:770A9F260880B2B73A41BA5EF59F360242E19000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338296Z" - } - }, - { - "id": "VI_MC_0015", - "brand": "VISA", - "type": "contact", - "category": "CVM", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction? (Scenario 15)", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151A9CF8169B1A83BDCECA5FFB82D2D59A32A99ED59000\nC:00B2020C00 \u2192 R:7016EBE1BD812CB504E1427BBC14EBBE24BCA87305FC9000\nC:80AE800000 \u2192 R:770A9F2608388E69F6342E5E2A9F3602B2999000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338338Z" - } - }, - { - "id": "VI_MC_0016", - "brand": "VISA", - "type": "contact", - "category": "Keys & Certificates", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B73647F0BBE4229CFDD24A2EEB454D134955A7B99000\nC:00B2020C00 \u2192 R:70162868492545A102186D0F99F7C9E215EDFE6A4AAB9000\nC:80AE800000 \u2192 R:770A9F2608C4B3A7E38E74319C9F3602D75A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338376Z" - } - }, - { - "id": "VI_MC_0017", - "brand": "VISA", - "type": "contact", - "category": "Testing", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 17)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015FEF9F02CE76B119FF903D48BCB1C16B92CE8343C9000\nC:00B2020C00 \u2192 R:7016BAB46C1114AFE44AA5C9AF9F0BA3D90F871F5C479000\nC:80AE800000 \u2192 R:770A9F26081360EAD4D6DF146A9F3602FCA59000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338430Z" - } - }, - { - "id": "VI_MC_0018", - "brand": "VISA", - "type": "contactless", - "category": "Security", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B8F67897996FAFB893CCB49192BE8F66884377179000\nC:00B2020C00 \u2192 R:7016713DAF3405DFF69A912715D51CF591093A9EF4E89000\nC:80AE800000 \u2192 R:770A9F260863A5E850A965CDA29F3602C3549000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338468Z" - } - }, - { - "id": "VI_MC_0019", - "brand": "VISA", - "type": "contact", - "category": "Reversals", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701508C7E8A908B713E95C939B774F4EBDF672EB23169000\nC:00B2020C00 \u2192 R:701645AE36F2E1E4DE1E90C80621DB212F19D54DBCEC9000\nC:80AE800000 \u2192 R:770A9F2608C24B35C47009EDC79F36027EB49000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338505Z" - } - }, - { - "id": "VI_MC_0020", - "brand": "VISA", - "type": "contact", - "category": "Card Communication", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151D076231E171CE761497AA7947D9815DF1BCADD49000\nC:00B2020C00 \u2192 R:70169C5F7794E1DD4C786A2EB2618C1266F6A90663F79000\nC:80AE800000 \u2192 R:770A9F26086C7A9CEB98BFE3FA9F36026BAD9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338543Z" - } - }, - { - "id": "VI_MC_0021", - "brand": "VISA", - "type": "contact", - "category": "Integration", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015408D946A7C7FA8FFE5B54F511210D472406EB1FF9000\nC:00B2020C00 \u2192 R:701600D00890D5334768B8C2BCE779212CCCF1052FDA9000\nC:80AE800000 \u2192 R:770A9F26083176F812815A064C9F360229579000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338580Z" - } - }, - { - "id": "VI_MC_0022", - "brand": "VISA", - "type": "contactless", - "category": "Keys & Certificates", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C42B13D72ACA08EF7BCD5C2972284C4CAB3209EB9000\nC:00B2020C00 \u2192 R:701683425DED302B2AC09DC275C54898F425D8D9F2B89000\nC:80AE800000 \u2192 R:770A9F26087F6E3490CACAEAD49F36029A6F9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338615Z" - } - }, - { - "id": "VI_MC_0023", - "brand": "VISA", - "type": "contactless", - "category": "Terminal Configuration", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 23)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015A9F7AC8CB3650E6E92DF49784DC2EFCD1B237B519000\nC:00B2020C00 \u2192 R:7016CAD303877EBCE4B0F39D234B9AE6FBF3EEA291309000\nC:80AE800000 \u2192 R:770A9F2608A35755ADE7C55DC09F36026EDC9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338659Z" - } - }, - { - "id": "VI_MC_0024", - "brand": "VISA", - "type": "contact", - "category": "Keys & Certificates", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 24)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70158235BA6E38FACC3BBE5924A37935B4CD4CD5F55F9000\nC:00B2020C00 \u2192 R:7016945AE1B0F46CFDFDEF5207918795EF338B1E6D379000\nC:80AE800000 \u2192 R:770A9F260891E8B2E376BD54669F36021B859000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338697Z" - } - }, - { - "id": "VI_MC_0025", - "brand": "VISA", - "type": "contactless", - "category": "Brand-specific", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70159834D184474A7CF48DCE22C8BEFA02EB2C6D6F8A9000\nC:00B2020C00 \u2192 R:70169A4FA113E035EE0D649582B82B51C97D2306F2479000\nC:80AE800000 \u2192 R:770A9F2608E00A3D4F27C233AB9F360294C49000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338735Z" - } - }, - { - "id": "VI_MC_0026", - "brand": "VISA", - "type": "contact", - "category": "Transaction Flow", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70155EB64DE62343CBDA4782790966C917FC37F20BA49000\nC:00B2020C00 \u2192 R:7016CDB5F20208611C9DDC24829264AC29D7172D3E199000\nC:80AE800000 \u2192 R:770A9F2608530405FB85B4830A9F3602D8289000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338773Z" - } - }, - { - "id": "VI_MC_0027", - "brand": "VISA", - "type": "contactless", - "category": "Brand-specific", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151F5B5833701071FBC451D7A7DA82B31571C2E99A9000\nC:00B2020C00 \u2192 R:70162E0B6997EBF6740D07B0A0C9367DF148217DBE239000\nC:80AE800000 \u2192 R:770A9F26084C21D4798ACAAE879F360226439000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338827Z" - } - }, - { - "id": "VI_MC_0028", - "brand": "VISA", - "type": "contactless", - "category": "Card Communication", - "question": "Why did the terminal queue a reversal after approval? (Scenario 28)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015EAD3B6E9E8325916A427BC19850CE73E343017469000\nC:00B2020C00 \u2192 R:7016CB282026E42A31E15DCF0CD5B6588E4179FDF1289000\nC:80AE800000 \u2192 R:770A9F2608C4D670CBFFBAC8509F3602A7089000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338870Z" - } - }, - { - "id": "VI_MC_0029", - "brand": "VISA", - "type": "contactless", - "category": "APDU", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B75377817CB557AB0B46F95F121770F0A64A5A109000\nC:00B2020C00 \u2192 R:7016443B2BC3A9A45DFA5B75C99450C15A73F4A27BA59000\nC:80AE800000 \u2192 R:770A9F26082AE08672B8301CED9F36025DFC9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338908Z" - } - }, - { - "id": "VI_MC_0030", - "brand": "VISA", - "type": "contact", - "category": "Brand-specific", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F75E2190A832A5C522AF0D5D513A66D899731CF49000\nC:00B2020C00 \u2192 R:70161B0D29F6306592F39CFF82C5BCB5E18EE87814329000\nC:80AE800000 \u2192 R:770A9F2608BD71CDF7F92C143E9F360255669000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338944Z" - } - }, - { - "id": "VI_MC_0031", - "brand": "VISA", - "type": "contact", - "category": "Card Communication", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015D648A22CCA8E0D3D443339BD8CFF158C4C1CA71F9000\nC:00B2020C00 \u2192 R:70168B0A998F3749EA8D26E6DFB1529C40566171E1B69000\nC:80AE800000 \u2192 R:770A9F26088BEC307BFE5FBB589F3602290C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.338981Z" - } - }, - { - "id": "VI_MC_0032", - "brand": "VISA", - "type": "contact", - "category": "Security", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70157768D00F4507898DCBE86E9C30B993F2A8A889649000\nC:00B2020C00 \u2192 R:701671CA40F98DCC16A7FB95593F485A27B79DAB89E39000\nC:80AE800000 \u2192 R:770A9F2608F12F63C9D1446ADE9F36024A529000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339018Z" - } - }, - { - "id": "VI_MC_0033", - "brand": "VISA", - "type": "contact", - "category": "Keys & Certificates", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015A10E8655F24DDCDFC016B0A60077B943C952199E9000\nC:00B2020C00 \u2192 R:7016AD4AFB65C07746053B1C8113013DEC38F4609D389000\nC:80AE800000 \u2192 R:770A9F26084D33933F6686BD959F36021F6F9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339057Z" - } - }, - { - "id": "VI_MC_0034", - "brand": "VISA", - "type": "contact", - "category": "Keys & Certificates", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701523F422387E98E13519BAD331045ABE82BA53CCE89000\nC:00B2020C00 \u2192 R:7016CFD534153DFE5CB04FF3DE128A07A3D7FBC4105F9000\nC:80AE800000 \u2192 R:770A9F2608F52FA7A817CC72EE9F3602E2FE9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339094Z" - } - }, - { - "id": "VI_MC_0035", - "brand": "VISA", - "type": "contactless", - "category": "Brand-specific", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 35)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701503CD10296EAB17EAFBE3370AB9B315F4D38663C69000\nC:00B2020C00 \u2192 R:7016E6A3D13EE4F01DF5543CACD78CA9E44D9A6669B49000\nC:80AE800000 \u2192 R:770A9F26085A3BFD9D030C41169F360285989000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339140Z" - } - }, - { - "id": "VI_MC_0036", - "brand": "VISA", - "type": "contactless", - "category": "Brand-specific", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701561BE37C791CCDA1086E7B669E52553C1D884580A9000\nC:00B2020C00 \u2192 R:7016E414A19FB2A7525DC2B76AAB96F03BE771AC3C899000\nC:80AE800000 \u2192 R:770A9F26080BEF196A2350266D9F360236D29000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339178Z" - } - }, - { - "id": "VI_MC_0037", - "brand": "VISA", - "type": "contactless", - "category": "APDU", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 37)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015122158278DCECDA0C30212B39929ECC0F574C9499000\nC:00B2020C00 \u2192 R:7016B04310C296B6D455786351E292836FAB473926AF9000\nC:80AE800000 \u2192 R:770A9F2608EA94BAD50A77D8B49F3602AFEE9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339215Z" - } - }, - { - "id": "VI_MC_0038", - "brand": "VISA", - "type": "contactless", - "category": "Card Communication", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701535284682200C618F4BC794E2CB0754E554FB17F79000\nC:00B2020C00 \u2192 R:701628B716BCFE11A3885CCB28C7CBBFF04E572864559000\nC:80AE800000 \u2192 R:770A9F2608B37DA3FFF65D07149F360254149000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339252Z" - } - }, - { - "id": "VI_MC_0039", - "brand": "VISA", - "type": "contact", - "category": "Settlement", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C0926EFF57D4585AE27CC4306D435F132F40DDB19000\nC:00B2020C00 \u2192 R:7016D7FCB3D48F729D860030C6ADB34D88DB8C6DF5BF9000\nC:80AE800000 \u2192 R:770A9F260889BC437E536CA15C9F3602024F9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339290Z" - } - }, - { - "id": "VI_MC_0040", - "brand": "VISA", - "type": "contactless", - "category": "Security", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70157B21CC915FE06961751B70528CBCC60229BB876E9000\nC:00B2020C00 \u2192 R:7016C085D329A388ECF7AEE0F382C77ADB08792CA25F9000\nC:80AE800000 \u2192 R:770A9F2608AB6856F67786767B9F360243329000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339327Z" - } - }, - { - "id": "VI_MC_0041", - "brand": "VISA", - "type": "contact", - "category": "CVM", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015FBAF8F58C741DF1BC5E3EA006C3AB85878FAB5FD9000\nC:00B2020C00 \u2192 R:70166DBBC8E547387DC644F05DF4AF981C35168F3EA89000\nC:80AE800000 \u2192 R:770A9F2608BB8B0D3B659BAFE29F3602C9E49000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339363Z" - } - }, - { - "id": "VI_MC_0042", - "brand": "VISA", - "type": "contactless", - "category": "Field 55", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015DC225A7AA98C8EBED550478265C332F10C23842C9000\nC:00B2020C00 \u2192 R:70169779E44501BAFE8E45ED9BF72E9BD849004B9F0F9000\nC:80AE800000 \u2192 R:770A9F2608F90D970B6DDC75CC9F3602782D9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339400Z" - } - }, - { - "id": "VI_MC_0043", - "brand": "VISA", - "type": "contactless", - "category": "Brand-specific", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 43)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701598D625493EE8F6A041053984E07240F6AD9FBE1A9000\nC:00B2020C00 \u2192 R:70162418C2F568C037CE716E36FC9A5138F96B1637DA9000\nC:80AE800000 \u2192 R:770A9F26080583C701F4B275F29F3602A11B9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339438Z" - } - }, - { - "id": "VI_MC_0044", - "brand": "VISA", - "type": "contact", - "category": "Keys & Certificates", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70154F7ABE60CB481FE9F65BAE8524E98BE0C50B7A2C9000\nC:00B2020C00 \u2192 R:70166F49ADA332145163F631CF81B7206F2E1BDB18129000\nC:80AE800000 \u2192 R:770A9F2608926337C6675D3BED9F3602355C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339480Z" - } - }, - { - "id": "VI_MC_0045", - "brand": "VISA", - "type": "contactless", - "category": "Reversals", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction? (Scenario 45)", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015BAABDDA76C8BEEC0190490976A08431EB448B7789000\nC:00B2020C00 \u2192 R:701692C62AF5F391C21ABDD370C191A4A741CE27D9C49000\nC:80AE800000 \u2192 R:770A9F26084A2F1C82CD44F6FC9F360267729000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339526Z" - } - }, - { - "id": "VI_MC_0046", - "brand": "VISA", - "type": "contactless", - "category": "Brand-specific", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701523DDBB6AB095BE4E176B42317490A39EF0A6668F9000\nC:00B2020C00 \u2192 R:701640C18519681E02C8B309C7C3AF256E0179AFC50B9000\nC:80AE800000 \u2192 R:770A9F2608BB97818C0874AC429F3602C7D79000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339564Z" - } - }, - { - "id": "VI_MC_0047", - "brand": "VISA", - "type": "contactless", - "category": "Settlement", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015AE4646494D45A235A40ADD9E846345087770B2F49000\nC:00B2020C00 \u2192 R:7016FB5CFF45671D08D76625EFAE7DC1CAC13EE17C1C9000\nC:80AE800000 \u2192 R:770A9F2608169EC99E5D914EE29F3602354C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339601Z" - } - }, - { - "id": "VI_MC_0048", - "brand": "VISA", - "type": "contact", - "category": "APDU", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 48)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70155E6E28A5323EB2C5CC15A45451D99E95346080EF9000\nC:00B2020C00 \u2192 R:7016F0F76FEDE207861541B1419A213D5595EB129ABC9000\nC:80AE800000 \u2192 R:770A9F26082D29F438AD66132F9F36029DA89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339639Z" - } - }, - { - "id": "VI_MC_0049", - "brand": "VISA", - "type": "contactless", - "category": "Issuer Scripts", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 49)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015FF5796030E36DD1AB60698299A03AAC056AAFF149000\nC:00B2020C00 \u2192 R:7016F4EAED19A06AB2480AC5C539A18D2F7BE96953B19000\nC:80AE800000 \u2192 R:770A9F260862E0F46AF9A434619F3602EC309000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339677Z" - } - }, - { - "id": "VI_MC_0050", - "brand": "VISA", - "type": "contact", - "category": "Risk Management", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 50)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015AE139096A6698AE384583036BA8497529AE140F19000\nC:00B2020C00 \u2192 R:70163C12DC5EB9A62E42E3E9EF7748BC5AAEF02F3BFE9000\nC:80AE800000 \u2192 R:770A9F260859B43C3A29ECD7759F3602FC2A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339720Z" - } - }, - { - "id": "VI_MC_0051", - "brand": "VISA", - "type": "contactless", - "category": "APDU", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015DA752F3EA3E59C23CAF1264044E9CE66A99DB20C9000\nC:00B2020C00 \u2192 R:7016491B10B3907DCACCCD65F46CBD49440204FD424D9000\nC:80AE800000 \u2192 R:770A9F2608ED5EDECB75D0F78D9F3602B11F9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339757Z" - } - }, - { - "id": "VI_MC_0052", - "brand": "VISA", - "type": "contactless", - "category": "Field 55", - "question": "Why did the terminal queue a reversal after approval? (Scenario 52)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015248E227F291A0FEFADB9951981F51909F24288489000\nC:00B2020C00 \u2192 R:7016880354EB587F51A244FDC7E56B18315ECF9F7CCF9000\nC:80AE800000 \u2192 R:770A9F260884D09ECA13BD8A889F360238CE9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339795Z" - } - }, - { - "id": "VI_MC_0053", - "brand": "VISA", - "type": "contact", - "category": "Issuer Scripts", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015A5A0020D33EB7986102163324C53589E2E8DA8529000\nC:00B2020C00 \u2192 R:701681CCA1885E2F6C5F34D63E831228E0F401C84AC09000\nC:80AE800000 \u2192 R:770A9F2608FFDC270CF3BA9C129F3602BA2E9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339832Z" - } - }, - { - "id": "VI_MC_0054", - "brand": "VISA", - "type": "contact", - "category": "CVM", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151C69C3BF2E641607FC29FE01A1A1C36E47214F0F9000\nC:00B2020C00 \u2192 R:701617405193E5233F726DACA34A615A2384D5B5E7149000\nC:80AE800000 \u2192 R:770A9F26083C50F200529DF4649F36028ED79000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339874Z" - } - }, - { - "id": "VI_MC_0055", - "brand": "VISA", - "type": "contact", - "category": "Settlement", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 55)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70155F29BD07633B7E681634FF5511B96D8AE131550F9000\nC:00B2020C00 \u2192 R:7016327EAD6A73A737D6C72FF1D46E5CB4E6B86A41189000\nC:80AE800000 \u2192 R:770A9F260843EED5A795572DF69F3602FE809000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339925Z" - } - }, - { - "id": "VI_MC_0056", - "brand": "VISA", - "type": "contact", - "category": "Brand-specific", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70157AD740D11F1DCF3EF720D64B9720F95E0EE4C5BE9000\nC:00B2020C00 \u2192 R:701602CA19D862A1B13CBE1BB5264A73F67AB8D812BB9000\nC:80AE800000 \u2192 R:770A9F2608EF3F9EB26E22C5929F360235839000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339963Z" - } - }, - { - "id": "VI_MC_0057", - "brand": "VISA", - "type": "contact", - "category": "Security", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701509D4FBDE096207ADAAFEE949587FB914B9E559559000\nC:00B2020C00 \u2192 R:701645731A4E8B561AB4BE5930CF4EA40A9F94EA3F149000\nC:80AE800000 \u2192 R:770A9F2608390C7EB2A16786029F3602E2C69000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.339999Z" - } - }, - { - "id": "VI_MC_0058", - "brand": "VISA", - "type": "contact", - "category": "Reversals", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015BC4DBCB09BB9E26EDE95DD42469FA2C20D8D5E469000\nC:00B2020C00 \u2192 R:70165C9F199FE700489F39D5F7038F2BFD8F3B08514A9000\nC:80AE800000 \u2192 R:770A9F2608E4B518BDB19926539F36025AA99000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340040Z" - } - }, - { - "id": "VI_MC_0059", - "brand": "VISA", - "type": "contactless", - "category": "Testing", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70153B4049BFDA5364763DE2340FB9B4EA59037447949000\nC:00B2020C00 \u2192 R:7016642D320FD16311F38129033665B0248BB57230669000\nC:80AE800000 \u2192 R:770A9F260895036FB5E35BCD679F3602D3A39000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340077Z" - } - }, - { - "id": "VI_MC_0060", - "brand": "VISA", - "type": "contact", - "category": "Issuer Scripts", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 60)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015FB912AF3C9E9E7D9D62FB50F3CE234CC352B6A6C9000\nC:00B2020C00 \u2192 R:701637DF88CBFCF84E338FF740312F05CA4932FE69FF9000\nC:80AE800000 \u2192 R:770A9F26088A01D3CEACEE11599F36025FD49000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340114Z" - } - }, - { - "id": "VI_MC_0061", - "brand": "VISA", - "type": "contactless", - "category": "Settlement", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 61)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70153FFF51C8FCB9A1014BB0AC3DBBDB177792293A509000\nC:00B2020C00 \u2192 R:7016A1EDD80F0ACCA3F36AFA59BD6F269819C723A82F9000\nC:80AE800000 \u2192 R:770A9F2608D6B299DA6DC8E5059F3602F6E89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340153Z" - } - }, - { - "id": "VI_MC_0062", - "brand": "VISA", - "type": "contact", - "category": "Terminal Configuration", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 62)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70156BE4749DDA26D89587C7346079EFDD16584088519000\nC:00B2020C00 \u2192 R:7016F012A92DB2C47338F273AAC7D643568ED81FB3AD9000\nC:80AE800000 \u2192 R:770A9F2608F784BFB901178C9B9F360237EC9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340196Z" - } - }, - { - "id": "VI_MC_0063", - "brand": "VISA", - "type": "contactless", - "category": "Field 55", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70158927965EAD182FFDAD3582BDAE015E40C69A23579000\nC:00B2020C00 \u2192 R:70164DAEF485A962DB5CC70072E6851CD842B530DEF39000\nC:80AE800000 \u2192 R:770A9F260876689FC4D6696D5D9F360240989000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340233Z" - } - }, - { - "id": "VI_MC_0064", - "brand": "VISA", - "type": "contact", - "category": "Certification Logs", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015BE20F4AC6CD82311A7FB108C9CB41585FAE42AD49000\nC:00B2020C00 \u2192 R:701683A14F8BD988AD5AF4E1641751F85ED3F1EBFEF39000\nC:80AE800000 \u2192 R:770A9F260843B269558605D27F9F36023A099000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340269Z" - } - }, - { - "id": "VI_MC_0065", - "brand": "VISA", - "type": "contact", - "category": "Testing", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 65)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015A402EFE80A1EA4619A12C2C857C2065CC9439FD99000\nC:00B2020C00 \u2192 R:70164B3B6FECF8D2DB5DD21AE74F29ED2F94497D91219000\nC:80AE800000 \u2192 R:770A9F26083DD3E8B8203E55C19F36022D9A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340305Z" - } - }, - { - "id": "VI_MC_0066", - "brand": "VISA", - "type": "contactless", - "category": "Security", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 66)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70158A565283D00C305FECF9BC92440630606F47D6299000\nC:00B2020C00 \u2192 R:7016E4FD0354EFF0E769C1A03DDF91FCFF710DA28DF39000\nC:80AE800000 \u2192 R:770A9F2608FBED0596FBE77AE49F36029CDB9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340342Z" - } - }, - { - "id": "VI_MC_0067", - "brand": "VISA", - "type": "contact", - "category": "Issuer Scripts", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015692F4565F3DF97610B8B5512AD3737F8AB18431E9000\nC:00B2020C00 \u2192 R:7016E33313536B59EF34BA436ED07FA9528BDB74D74D9000\nC:80AE800000 \u2192 R:770A9F2608DDEB0E4022AAC5D19F3602C1419000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340381Z" - } - }, - { - "id": "VI_MC_0068", - "brand": "VISA", - "type": "contactless", - "category": "APDU", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015AB084CE6EBC6921AC49629A500879D31B8B313E99000\nC:00B2020C00 \u2192 R:70160EA77B994C73A6BE34DD221D4F6E2BCC8FDEFD549000\nC:80AE800000 \u2192 R:770A9F26084FE436EF15B3D33B9F360291439000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340421Z" - } - }, - { - "id": "VI_MC_0069", - "brand": "VISA", - "type": "contactless", - "category": "Certification Logs", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701599F044D19965F03B21DF9EACF44EEE4A2DC7CA1E9000\nC:00B2020C00 \u2192 R:70168250932616F0350867E2AC1F0AD5D0AC823359459000\nC:80AE800000 \u2192 R:770A9F26088249D51A5019C3A49F3602DA8C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340457Z" - } - }, - { - "id": "VI_MC_0070", - "brand": "VISA", - "type": "contact", - "category": "Field 55", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70157FC381AED2F0D7083749DE264B57DE10E9501F889000\nC:00B2020C00 \u2192 R:7016CB6915292C348D6AA8E87AA6EA040F005DFC220E9000\nC:80AE800000 \u2192 R:770A9F26083BCBC503EB6E07089F3602B6299000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340495Z" - } - }, - { - "id": "VI_MC_0071", - "brand": "VISA", - "type": "contactless", - "category": "Terminal Configuration", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B18F606C38F5652424878608E0D1ADD83EFB17189000\nC:00B2020C00 \u2192 R:7016DEA0C6A207D2765A9230FD0A873F7A1A72E3E3219000\nC:80AE800000 \u2192 R:770A9F26081CA241E19D23119C9F3602C3D79000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340533Z" - } - }, - { - "id": "VI_MC_0072", - "brand": "VISA", - "type": "contactless", - "category": "Reversals", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 72)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015D3A0EA63302648BDFE5741149DB944F9A9B041719000\nC:00B2020C00 \u2192 R:7016DB6662A6FEAA9DA53E1F7077E67FAC6C50B02B039000\nC:80AE800000 \u2192 R:770A9F260849E6B106695785A79F360256059000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340579Z" - } - }, - { - "id": "VI_MC_0073", - "brand": "VISA", - "type": "contact", - "category": "Card Communication", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70154C3A69E7BB5D234466CBAD71694A7184F62F25CB9000\nC:00B2020C00 \u2192 R:7016FE5ABFFF8C1676E7C69DC5B82429EB71EADEEDDB9000\nC:80AE800000 \u2192 R:770A9F2608FA8C05E782B292879F3602332B9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340618Z" - } - }, - { - "id": "VI_MC_0074", - "brand": "VISA", - "type": "contactless", - "category": "Issuer Scripts", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70156A898648099BCC0F4C776F7EEA2A6DD6EE0B44909000\nC:00B2020C00 \u2192 R:7016FBA7DDC9A0144ACC6C2C6F3AE925351F0562C9679000\nC:80AE800000 \u2192 R:770A9F260892E1B05ADC534DF29F3602C6469000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340698Z" - } - }, - { - "id": "VI_MC_0075", - "brand": "VISA", - "type": "contactless", - "category": "Integration", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015596E8604E2C7AFEE129EB9C5D75DEC53C17589269000\nC:00B2020C00 \u2192 R:7016FD3B23ADE5861E02ECAC6C10834AEFE227E4F8559000\nC:80AE800000 \u2192 R:770A9F260803593C52084EB5619F36026E139000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340735Z" - } - }, - { - "id": "VI_MC_0076", - "brand": "VISA", - "type": "contactless", - "category": "Field 55", - "question": "Why did the terminal queue a reversal after approval? (Scenario 76)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015101C67B7620D00A6273551D3AA66CD3763BA50CA9000\nC:00B2020C00 \u2192 R:70160C6E728B126D9F3583AC4A5AF2A0EC7070397D729000\nC:80AE800000 \u2192 R:770A9F260814BF964C617EA48A9F36021D909000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340779Z" - } - }, - { - "id": "VI_MC_0077", - "brand": "VISA", - "type": "contactless", - "category": "Security", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015A76177CA5E02F26146425672DE9567D5799E68F29000\nC:00B2020C00 \u2192 R:7016BCC5FEDD4F0CD29458CE9E9CF2A4F64600BFCDCB9000\nC:80AE800000 \u2192 R:770A9F2608CF92D13C56D8BFB19F3602CD779000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340816Z" - } - }, - { - "id": "VI_MC_0078", - "brand": "VISA", - "type": "contactless", - "category": "Certification Logs", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015048E4875032CC26D5D89C9D23B486C905F032DD99000\nC:00B2020C00 \u2192 R:7016D55B546F53E6561568DE35292C382A07FF3018019000\nC:80AE800000 \u2192 R:770A9F2608360C8FFADABAA7BC9F3602C1BA9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340853Z" - } - }, - { - "id": "VI_MC_0079", - "brand": "VISA", - "type": "contactless", - "category": "Brand-specific", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701540387BEFD60A0B1AE7FC2BDF3C96414F29E5E3F79000\nC:00B2020C00 \u2192 R:701676523D05AC878F34F2A72ACCD77839232A63B4AC9000\nC:80AE800000 \u2192 R:770A9F26080916CDAB473C0EA49F360297FE9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340891Z" - } - }, - { - "id": "VI_MC_0080", - "brand": "VISA", - "type": "contact", - "category": "Keys & Certificates", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151A938F6F9C1A46715FC950CADFBCC2996C34A19E9000\nC:00B2020C00 \u2192 R:701654EF946660B34CD513BF513AD4C7137CF95C2EC89000\nC:80AE800000 \u2192 R:770A9F2608EB03323F70F835CF9F3602D9439000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340928Z" - } - }, - { - "id": "VI_MC_0081", - "brand": "VISA", - "type": "contact", - "category": "Certification Logs", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C0CF2363550EA31465281239B5D07919E4FAB6319000\nC:00B2020C00 \u2192 R:701671649646B84D288C5CE28D46286B5D4ADC0728339000\nC:80AE800000 \u2192 R:770A9F2608D2A2BA847803C7C39F3602359F9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.340971Z" - } - }, - { - "id": "VI_MC_0082", - "brand": "VISA", - "type": "contactless", - "category": "APDU", - "question": "Why did the terminal queue a reversal after approval? (Scenario 82)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70158315AC5BCF480444C81B7DE5EBE98D7929DA22279000\nC:00B2020C00 \u2192 R:701625129F0D4FF3C060DB71E5752B4B1DFC5B3A73999000\nC:80AE800000 \u2192 R:770A9F2608F9860C691EF1B0EA9F36029B309000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341022Z" - } - }, - { - "id": "VI_MC_0083", - "brand": "VISA", - "type": "contact", - "category": "Risk Management", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015CB03DF624D3F0487FCB9BD583EE54BD0B636914C9000\nC:00B2020C00 \u2192 R:7016DA156F83DFF4ACC433044B071AD0DF99F2D745789000\nC:80AE800000 \u2192 R:770A9F2608387D6F3564734C189F360264D09000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341064Z" - } - }, - { - "id": "VI_MC_0084", - "brand": "VISA", - "type": "contact", - "category": "Terminal Configuration", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 84)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015CD977ADF1D1938B8BD7A15101A69F83D58FBA9339000\nC:00B2020C00 \u2192 R:701604ABBB786C2343166E32A9F64146D8BBE3D2FD059000\nC:80AE800000 \u2192 R:770A9F2608849116CF25ECCC869F360250569000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341101Z" - } - }, - { - "id": "VI_MC_0085", - "brand": "VISA", - "type": "contactless", - "category": "Security", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 85)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015897983571791484817630BBA284D9A10B785803C9000\nC:00B2020C00 \u2192 R:701686E7A86C4E7DB4F2F5E556F590955C6242D7EC349000\nC:80AE800000 \u2192 R:770A9F260803CC0301472840039F3602A2649000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341139Z" - } - }, - { - "id": "VI_MC_0086", - "brand": "VISA", - "type": "contactless", - "category": "Security", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 86)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701559AF4718301393D40707DC4B97C3F53739B2A3B29000\nC:00B2020C00 \u2192 R:7016145DA5D499B38FB82044A4CEF23D842A45CBAFDF9000\nC:80AE800000 \u2192 R:770A9F2608DA47CDFF7C2D727B9F3602060B9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341174Z" - } - }, - { - "id": "VI_MC_0087", - "brand": "VISA", - "type": "contact", - "category": "Transaction Flow", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction? (Scenario 87)", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151BB49E4D7671434C0DB132F504B42720D45F49FD9000\nC:00B2020C00 \u2192 R:7016AE093411550CDE897D582C46C17C52EFACC51BD69000\nC:80AE800000 \u2192 R:770A9F26088332BA07953260969F360261789000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341218Z" - } - }, - { - "id": "VI_MC_0088", - "brand": "VISA", - "type": "contact", - "category": "Field 55", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F11A290B9C6ACB43AD340CF1954E227645AE4A9B9000\nC:00B2020C00 \u2192 R:7016D1C7624F30492F3EA59528BB225E8F8E43F1B9CD9000\nC:80AE800000 \u2192 R:770A9F26084EBAB2DE811704399F3602C5C29000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341265Z" - } - }, - { - "id": "VI_MC_0089", - "brand": "VISA", - "type": "contactless", - "category": "Terminal Configuration", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70152BEEE3253CD6CA2AAF6F38E14F46A1C1BDF6160D9000\nC:00B2020C00 \u2192 R:70168852428C29ED68512DA956BDFF5DBC0624AA04E49000\nC:80AE800000 \u2192 R:770A9F2608FA3D80E4E3166D5C9F36026B669000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341301Z" - } - }, - { - "id": "VI_MC_0090", - "brand": "VISA", - "type": "contactless", - "category": "Terminal Configuration", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 90)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70150993FEDDBBDA35EDB55DC9D932320D3F3E19D67E9000\nC:00B2020C00 \u2192 R:7016C36F3BEDC0B79889D70D1004BAA5D7C6C1D4C5CA9000\nC:80AE800000 \u2192 R:770A9F26085D7343C85A6220D09F3602402C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341338Z" - } - }, - { - "id": "VI_MC_0091", - "brand": "VISA", - "type": "contact", - "category": "Risk Management", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015EB577967C81824033E33498522FB6C3F0D2F26DC9000\nC:00B2020C00 \u2192 R:7016AE5590513ABF058360046B360A472488F62B9EFD9000\nC:80AE800000 \u2192 R:770A9F2608C68568C3956FDED89F3602A3CD9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341375Z" - } - }, - { - "id": "VI_MC_0092", - "brand": "VISA", - "type": "contactless", - "category": "CVM", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70152E518D9BC035AD5B726BB4A30A0A6EA72C9663829000\nC:00B2020C00 \u2192 R:7016DDAA661FF18D33E5AC70900E94C11A02F3D98ABC9000\nC:80AE800000 \u2192 R:770A9F26082AF1C9EF3B3071049F36023AD79000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341412Z" - } - }, - { - "id": "VI_MC_0093", - "brand": "VISA", - "type": "contactless", - "category": "Risk Management", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015018131928AC854E34A4DE37FF8AF72892B7622F19000\nC:00B2020C00 \u2192 R:7016606EC6F3A6A9E4347BCE6C628D5934E3370E580F9000\nC:80AE800000 \u2192 R:770A9F2608EB832BD64CDA1E8B9F360231CD9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341454Z" - } - }, - { - "id": "VI_MC_0094", - "brand": "VISA", - "type": "contactless", - "category": "Risk Management", - "question": "Why did the terminal queue a reversal after approval? (Scenario 94)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701558FD31737311872387CCC378F656B99035F975A29000\nC:00B2020C00 \u2192 R:701655AE40FDA058250BF0F7F3109754339AEFB8F8BE9000\nC:80AE800000 \u2192 R:770A9F26080B9AF3804D74BF079F3602DB629000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341491Z" - } - }, - { - "id": "VI_MC_0095", - "brand": "VISA", - "type": "contactless", - "category": "Terminal Configuration", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 95)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701538E58BACD8961A3DEB930F4E4959F9290E16931F9000\nC:00B2020C00 \u2192 R:701690DB0184B942846D2971FB7CDC38995DA4684D699000\nC:80AE800000 \u2192 R:770A9F2608929E5CD34EABEBDE9F3602DDE09000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341528Z" - } - }, - { - "id": "VI_MC_0096", - "brand": "VISA", - "type": "contactless", - "category": "CVM", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70152497B491C4C0EE12183A39FA13164F474990F6329000\nC:00B2020C00 \u2192 R:70160433763F0EC139CF578E3D4054756FF993FB8CC39000\nC:80AE800000 \u2192 R:770A9F2608EDD409E3C091E1B49F3602EE809000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341565Z" - } - }, - { - "id": "VI_MC_0097", - "brand": "VISA", - "type": "contact", - "category": "Reversals", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015BC254BAE489C2FCF584ABC2105733FFA7735CD219000\nC:00B2020C00 \u2192 R:70168312EB05A3EC4668FE9765D62036140BD2A5F66F9000\nC:80AE800000 \u2192 R:770A9F2608BB42EDC224933F719F3602A0799000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341609Z" - } - }, - { - "id": "VI_MC_0098", - "brand": "VISA", - "type": "contactless", - "category": "Issuer Scripts", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 98)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015259279C13F801AD86A146A17F21B2D2F48131F7B9000\nC:00B2020C00 \u2192 R:7016DF970106C0F1CC4DD43E3BB6AD177207D10712149000\nC:80AE800000 \u2192 R:770A9F2608E591AB794CF322869F3602FB7E9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341664Z" - } - }, - { - "id": "VI_MC_0099", - "brand": "VISA", - "type": "contactless", - "category": "Transaction Flow", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701578A31BDF82647963B417EE30F188C9218CF0CCE19000\nC:00B2020C00 \u2192 R:701676C5D191B0A860ADD13C9ED85CE74088279AC18B9000\nC:80AE800000 \u2192 R:770A9F260888039A85EE0E0E1B9F3602F6D19000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341701Z" - } - }, - { - "id": "VI_MC_0100", - "brand": "VISA", - "type": "contactless", - "category": "Field 55", - "question": "Why did the terminal queue a reversal after approval? (Scenario 100)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70152E5888F475417315EA171880B17B32E3276ABD2D9000\nC:00B2020C00 \u2192 R:7016940ABADBF905B194036AB6C14C227D31FEA8697A9000\nC:80AE800000 \u2192 R:770A9F26087B7EA37EDB2B2BF79F3602ED749000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341744Z" - } - }, - { - "id": "VI_MC_0101", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Risk Management", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015489AA32DD4F65E053D8F341D0524CDB4C793AA319000\nC:00B2020C00 \u2192 R:70162BEDED9F45240BECAE58379FA1D9ACA5416D8A3B9000\nC:80AE800000 \u2192 R:770A9F260895398FE7598378439F360265019000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341782Z" - } - }, - { - "id": "VI_MC_0102", - "brand": "MASTERCARD", - "type": "contact", - "category": "Settlement", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B69DE4E933EDF82483B272A5A8E2A1D3A61074C79000\nC:00B2020C00 \u2192 R:701668F4F5F946260D2F651D8C7BF5979FFCBF93739D9000\nC:80AE800000 \u2192 R:770A9F2608EA7D35EA3BC4FFD79F360209869000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341819Z" - } - }, - { - "id": "VI_MC_0103", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Certification Logs", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70158ADCEDC818F7A19ED7563A400C2AB216B65C795B9000\nC:00B2020C00 \u2192 R:7016AD670103CF1599077183CC48222D0043C69AD0989000\nC:80AE800000 \u2192 R:770A9F2608E638FC9D27D8F97C9F36020FCB9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341862Z" - } - }, - { - "id": "VI_MC_0104", - "brand": "MASTERCARD", - "type": "contact", - "category": "Transaction Flow", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C7EBF39A42356F724CF71F8D9A41AD086FFA7AEF9000\nC:00B2020C00 \u2192 R:701623D2C405356E31DF5F4DC093D98AB5496B8FE6A49000\nC:80AE800000 \u2192 R:770A9F26085F0AD54F209663EA9F360231E59000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341906Z" - } - }, - { - "id": "VI_MC_0105", - "brand": "MASTERCARD", - "type": "contact", - "category": "Security", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B0689D9BC86243685834CA8F650762445F0A214E9000\nC:00B2020C00 \u2192 R:7016DFA937CCCFB9A26584DEF83DB50BEBD66CB506EB9000\nC:80AE800000 \u2192 R:770A9F2608609A3B80818FC1889F360210FE9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341943Z" - } - }, - { - "id": "VI_MC_0106", - "brand": "MASTERCARD", - "type": "contact", - "category": "Risk Management", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151B04542D31E1A3860AA5B0CD1264825E186D50989000\nC:00B2020C00 \u2192 R:7016B3AE2E232525A0506BE2796491C9584AD76865989000\nC:80AE800000 \u2192 R:770A9F2608E82FBBBE51C46DB99F36026A829000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.341980Z" - } - }, - { - "id": "VI_MC_0107", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Integration", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70158135F4EABC1A3B05DFAA35B95E50EEDCF78BAFC99000\nC:00B2020C00 \u2192 R:7016173DD8C0559644A1294BEC5E0465992576D274B09000\nC:80AE800000 \u2192 R:770A9F2608F5B3FC6FCE73C4A49F3602CA9D9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342091Z" - } - }, - { - "id": "VI_MC_0108", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Card Communication", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F0757BBA0C274F6169D2AC5D499CF18D55C3E2B39000\nC:00B2020C00 \u2192 R:7016C05A4CE0FCD19D83EBFAB35DC240A86ED1E913FE9000\nC:80AE800000 \u2192 R:770A9F2608B1B8DA90859BD0EA9F3602913B9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342129Z" - } - }, - { - "id": "VI_MC_0109", - "brand": "MASTERCARD", - "type": "contactless", - "category": "CVM", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015752344FD8BE7E12AB143C2A9DC0582D368971BF69000\nC:00B2020C00 \u2192 R:7016D8581C5980D60D488EA3770A729EDACF0AAABE4E9000\nC:80AE800000 \u2192 R:770A9F2608F65C8C12FB26B99A9F3602EE049000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342168Z" - } - }, - { - "id": "VI_MC_0110", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Security", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 110)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015D09F7C4C33C663955CDB6D8AB3AC7CFE9E55C90A9000\nC:00B2020C00 \u2192 R:7016E53CDDD60742D0A75F2B0C65EB75F6A49206EE7E9000\nC:80AE800000 \u2192 R:770A9F260875E3A57E201DFC2D9F3602830E9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342207Z" - } - }, - { - "id": "VI_MC_0111", - "brand": "MASTERCARD", - "type": "contact", - "category": "Transaction Flow", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70159C1BCED334835BDA47F683A2EF78A9EAE88144909000\nC:00B2020C00 \u2192 R:70167BB9959FE94449C87069408BCF5B4ABCF5F5FC029000\nC:80AE800000 \u2192 R:770A9F2608A79674836BFE076B9F36021C3A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342244Z" - } - }, - { - "id": "VI_MC_0112", - "brand": "MASTERCARD", - "type": "contact", - "category": "Field 55", - "question": "Why did the terminal queue a reversal after approval? (Scenario 112)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151E778577E5188262491677FE31A26F3E2F636F909000\nC:00B2020C00 \u2192 R:7016D3E6E08D8F5AF9987A89E35F0AFF552D93EA56379000\nC:80AE800000 \u2192 R:770A9F2608699AF3964A56C5559F3602AFD89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342309Z" - } - }, - { - "id": "VI_MC_0113", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Settlement", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 113)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70159B49ABAE9DCD0C1DB4E806689B0ADCA66E83275A9000\nC:00B2020C00 \u2192 R:7016FF1CF78C131A8BE93F42AD44962E7A89042ABE659000\nC:80AE800000 \u2192 R:770A9F2608AE7EBA688043DDCF9F360211B09000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342347Z" - } - }, - { - "id": "VI_MC_0114", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Terminal Configuration", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F9A222352E62D8EE4A25AED0C90C007AD487AE6B9000\nC:00B2020C00 \u2192 R:70164646953014B2AA76695D876B04E3C0E6C1EEC66C9000\nC:80AE800000 \u2192 R:770A9F26083253563FBAD662BF9F360283E09000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342384Z" - } - }, - { - "id": "VI_MC_0115", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Testing", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C3BB92D972CF08A14750444F1169BD5D5545B3509000\nC:00B2020C00 \u2192 R:7016F69CB8A00A0F14D1C5530B72D23FEDE409FF84AB9000\nC:80AE800000 \u2192 R:770A9F26083FF64744723C93779F3602859A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342420Z" - } - }, - { - "id": "VI_MC_0116", - "brand": "MASTERCARD", - "type": "contactless", - "category": "CVM", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 116)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70154ADB41C16504175CA0FFB6CE6E8E38AA58AFE3A89000\nC:00B2020C00 \u2192 R:70162BD0437E3394B9ED25C64706B41B75B53574D6819000\nC:80AE800000 \u2192 R:770A9F2608C9CDFEA4902896219F3602D44F9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342458Z" - } - }, - { - "id": "VI_MC_0117", - "brand": "MASTERCARD", - "type": "contact", - "category": "APDU", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C5DC67B2784C346E48A0393F7E93E42A81C83ED59000\nC:00B2020C00 \u2192 R:7016F9732B7FDD13888AD8B203F7F7D83FCC133337BD9000\nC:80AE800000 \u2192 R:770A9F2608C1BEE1CD0650A39D9F36020E8B9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342496Z" - } - }, - { - "id": "VI_MC_0118", - "brand": "MASTERCARD", - "type": "contact", - "category": "Certification Logs", - "question": "Why did the terminal queue a reversal after approval? (Scenario 118)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70158E1AE856ACB5F2AB7A932CAF5C68FBAEB55A03699000\nC:00B2020C00 \u2192 R:701695C2622C84ABC4C392A7E17480F7777E640970FE9000\nC:80AE800000 \u2192 R:770A9F2608D6D5CC8B8DBB7AB29F36024A749000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342533Z" - } - }, - { - "id": "VI_MC_0119", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Risk Management", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015A37B7E81EEFD250E1BF42B2880FD4C6E99A7D4A09000\nC:00B2020C00 \u2192 R:70161B322D567550F3A23CCDCF4A539B5D8F258C67B29000\nC:80AE800000 \u2192 R:770A9F2608AE38011B35000AC99F36020B259000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342570Z" - } - }, - { - "id": "VI_MC_0120", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Risk Management", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 120)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701556B34B5E54E013993B553F64AECE32A7B47F6C1B9000\nC:00B2020C00 \u2192 R:70161F32AC69A4E69DCDC2F0F3AFC9F9116295A1019C9000\nC:80AE800000 \u2192 R:770A9F26086B1D5B163E57A26F9F3602601C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342607Z" - } - }, - { - "id": "VI_MC_0121", - "brand": "MASTERCARD", - "type": "contact", - "category": "Field 55", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015907A5C7BC14478D968D0DDC86F80C1E472335F259000\nC:00B2020C00 \u2192 R:7016A58C999833C62F641FF3371C5227DBE4E166A1049000\nC:80AE800000 \u2192 R:770A9F2608A85BE61CC492756A9F3602E0E29000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342644Z" - } - }, - { - "id": "VI_MC_0122", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Risk Management", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701554A132D05AB14370C01C37120FC9CE7F8BEF4EB79000\nC:00B2020C00 \u2192 R:7016495C85B0D941ED7C4B6CDDEEECEBAAC467666BED9000\nC:80AE800000 \u2192 R:770A9F2608B96C4F3E9D166A5C9F3602D5E09000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342681Z" - } - }, - { - "id": "VI_MC_0123", - "brand": "MASTERCARD", - "type": "contact", - "category": "Card Communication", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701584C64DAE74FA1322001A2AB64692BAEFA59935459000\nC:00B2020C00 \u2192 R:7016D3D5F8734E314CFCF50BE5E0FBA2B2549C436A929000\nC:80AE800000 \u2192 R:770A9F2608BF0D5B8680FA51799F36028EDA9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342718Z" - } - }, - { - "id": "VI_MC_0124", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Field 55", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70152A14009C6FCC18CABDDA4B86F982E2A3043725B29000\nC:00B2020C00 \u2192 R:7016472200A24EA3314625220D7612CA6F6F5F91E5029000\nC:80AE800000 \u2192 R:770A9F2608568463265A75C9D99F36026D8B9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342903Z" - } - }, - { - "id": "VI_MC_0125", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Keys & Certificates", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 125)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701595212FB1D2E02AB28AEBFBF9FA6751BDEEACEEE49000\nC:00B2020C00 \u2192 R:70164CD04AC4CB0D545630CF48A60FC59876FFDD5F1B9000\nC:80AE800000 \u2192 R:770A9F260832AF947F6DF095A99F3602D3499000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342944Z" - } - }, - { - "id": "VI_MC_0126", - "brand": "MASTERCARD", - "type": "contact", - "category": "Integration", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015BF20EBD76A7AF8AA64A777FF0A3C4A2FE82EC6849000\nC:00B2020C00 \u2192 R:7016B1F770ABF48AFA66391697CD09864900D2BE4EC59000\nC:80AE800000 \u2192 R:770A9F2608EA38E86E954A031A9F3602FB4A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.342981Z" - } - }, - { - "id": "VI_MC_0127", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Risk Management", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015AC5A19A114F22443572BBA2DA2FC1DC426E538779000\nC:00B2020C00 \u2192 R:70161017F117744AACC09F0D216167F0B2B5C64098BC9000\nC:80AE800000 \u2192 R:770A9F2608568A6A8C39E0EC659F360231C39000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343018Z" - } - }, - { - "id": "VI_MC_0128", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Card Communication", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701569BE178609065A6FCAEC5FF97230010809EC531B9000\nC:00B2020C00 \u2192 R:701666DB28D0913948E630F50327E880F2462CC01FDE9000\nC:80AE800000 \u2192 R:770A9F2608D501289F680867E09F36021DF79000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343056Z" - } - }, - { - "id": "VI_MC_0129", - "brand": "MASTERCARD", - "type": "contact", - "category": "Security", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015BEF5BB4ABD5CBEB94FDBD284ABEE51A4A546C2D39000\nC:00B2020C00 \u2192 R:7016130857AF3ABCC7BD37E4603F4297C963600093659000\nC:80AE800000 \u2192 R:770A9F2608228E3DBC09ACB69D9F3602F1F19000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343094Z" - } - }, - { - "id": "VI_MC_0130", - "brand": "MASTERCARD", - "type": "contact", - "category": "CVM", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70158FC3DBF0C1F2F82273ECA7F1A9E6D3040E25E8C19000\nC:00B2020C00 \u2192 R:701683F5E9519AD3426FF70C5C1957AF7E335440EFBD9000\nC:80AE800000 \u2192 R:770A9F26080B3DF18DD2228BFC9F360274309000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343149Z" - } - }, - { - "id": "VI_MC_0131", - "brand": "MASTERCARD", - "type": "contact", - "category": "Field 55", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70156EB8F25D3176494C0B1038094A7F66FFF635C2449000\nC:00B2020C00 \u2192 R:701642F257DB78D1D1AC06BCE74FD579F2D0D2241B8C9000\nC:80AE800000 \u2192 R:770A9F26088EA9A9FFC4FA2FA29F360288899000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343187Z" - } - }, - { - "id": "VI_MC_0132", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Certification Logs", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701576B96AD88D6496BA6E53976A5FB7CF8EA48283CC9000\nC:00B2020C00 \u2192 R:70160268FE8D681DF3FDCA3453B11283843D61103A899000\nC:80AE800000 \u2192 R:770A9F2608D7778B740A75C6059F360228F39000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343222Z" - } - }, - { - "id": "VI_MC_0133", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Settlement", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701577E55783079DCE6732DEE4CC086FDAA0FCE6B42C9000\nC:00B2020C00 \u2192 R:70165C66ABC8797CF072E0CBBC0FDED2D8B78B8F55769000\nC:80AE800000 \u2192 R:770A9F26081CB172521828E4949F3602D8579000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343258Z" - } - }, - { - "id": "VI_MC_0134", - "brand": "MASTERCARD", - "type": "contact", - "category": "Brand-specific", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701572159FD5706223853EB54570A5801C451F447B8E9000\nC:00B2020C00 \u2192 R:70167E537512C409EFCCEBC8D5F4162B93DCC9B0AF609000\nC:80AE800000 \u2192 R:770A9F26086D4E49C7407E8FCE9F3602EB6E9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343295Z" - } - }, - { - "id": "VI_MC_0135", - "brand": "MASTERCARD", - "type": "contact", - "category": "Keys & Certificates", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction? (Scenario 135)", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70157439B1BECD29BF1F2BA6950348106B0ECAEBA9B19000\nC:00B2020C00 \u2192 R:70163EFD124CAE84462C8C7119046D6D4D8602518F279000\nC:80AE800000 \u2192 R:770A9F2608E5F32EABF8AA48779F36020DF89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343337Z" - } - }, - { - "id": "VI_MC_0136", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Integration", - "question": "Why did the terminal queue a reversal after approval? (Scenario 136)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015FC19834777E43BDCDA9275F2A1DCD4DF0AB397FF9000\nC:00B2020C00 \u2192 R:7016C6CD7975A5AC232204DF2410F5149BB2159A31219000\nC:80AE800000 \u2192 R:770A9F2608065CF3892942E8539F3602F7919000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343375Z" - } - }, - { - "id": "VI_MC_0137", - "brand": "MASTERCARD", - "type": "contact", - "category": "Transaction Flow", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015FEB99CD79A67E44121343E4429AA7FDD396F1B5C9000\nC:00B2020C00 \u2192 R:70166B2118C5FECAE4ADA5058D2FA4147F865D10BABA9000\nC:80AE800000 \u2192 R:770A9F260803F664A8C6D1E9E19F36029A0D9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343414Z" - } - }, - { - "id": "VI_MC_0138", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Risk Management", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015E7A7E89178C80717E7C0D128D091F6937CA560D29000\nC:00B2020C00 \u2192 R:7016A7F0348598D5D65B3992243072853EA3E3F82B2B9000\nC:80AE800000 \u2192 R:770A9F26085C6802254A56FB0A9F3602CD3C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343450Z" - } - }, - { - "id": "VI_MC_0139", - "brand": "MASTERCARD", - "type": "contactless", - "category": "CVM", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701527FECAB611E60B0BAD0AE24334FFA31A79D913199000\nC:00B2020C00 \u2192 R:701648C48AD2B2F99D009A5243B338AA3562718929939000\nC:80AE800000 \u2192 R:770A9F2608C19D2A8142303F1F9F3602BC389000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343487Z" - } - }, - { - "id": "VI_MC_0140", - "brand": "MASTERCARD", - "type": "contact", - "category": "CVM", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70152A5530F6457D086F71D6C69B4CD9873D8F03C6849000\nC:00B2020C00 \u2192 R:7016537417712C46830630D3A6E443BADC8E646CB67F9000\nC:80AE800000 \u2192 R:770A9F2608F8D180DE511E96D39F360294989000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343524Z" - } - }, - { - "id": "VI_MC_0141", - "brand": "MASTERCARD", - "type": "contact", - "category": "Transaction Flow", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F2EB97E68FC85F7E407FC7438B8389C02379875F9000\nC:00B2020C00 \u2192 R:7016040ADA0F6539D886CB3CF67A1ABF7AF7D02347D19000\nC:80AE800000 \u2192 R:770A9F26086ED23E4766B3180D9F360238E69000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343560Z" - } - }, - { - "id": "VI_MC_0142", - "brand": "MASTERCARD", - "type": "contact", - "category": "CVM", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701532871F850F6DA32780DBBE5030865571566649E19000\nC:00B2020C00 \u2192 R:7016E74136B9D425FC05B15D325624D3D758AE56ED5E9000\nC:80AE800000 \u2192 R:770A9F26088A8606C9CE2341739F3602FC419000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343598Z" - } - }, - { - "id": "VI_MC_0143", - "brand": "MASTERCARD", - "type": "contact", - "category": "Integration", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 143)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015471272A288A451DF64724E2D2AE58A0100002A529000\nC:00B2020C00 \u2192 R:701626F3EB104BAC3998524F9F24591ACF1DE011087C9000\nC:80AE800000 \u2192 R:770A9F2608BA2B84CC37D487AB9F36021B959000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343635Z" - } - }, - { - "id": "VI_MC_0144", - "brand": "MASTERCARD", - "type": "contact", - "category": "APDU", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F1D67DEB05421813C830885FF76C62C87424C9599000\nC:00B2020C00 \u2192 R:7016D9507D4BD63982E1C9C5BB915C7BA59602FC9D899000\nC:80AE800000 \u2192 R:770A9F2608073B758A4E1A19199F360276669000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343673Z" - } - }, - { - "id": "VI_MC_0145", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Security", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 145)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015A3C74323EE316726F64CA71D122FAC3ED00560039000\nC:00B2020C00 \u2192 R:7016AD3407CAFF893D06CBB41292393977CFA04D65569000\nC:80AE800000 \u2192 R:770A9F2608427E8AAD228194D19F3602B0A79000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343709Z" - } - }, - { - "id": "VI_MC_0146", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Card Communication", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015D1334D01616BCC20C4E2A63568AB1D5D3FFD46899000\nC:00B2020C00 \u2192 R:701613790E6A97F4D167B313BE01B29950E85CDC9E299000\nC:80AE800000 \u2192 R:770A9F26084BC74A39096563579F360294DC9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343748Z" - } - }, - { - "id": "VI_MC_0147", - "brand": "MASTERCARD", - "type": "contact", - "category": "Security", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F4C3ED0E56977AB74090BD34DA04CB4D82CCBD269000\nC:00B2020C00 \u2192 R:70160FD346AA3868C4798105F700DCC213C6226A012C9000\nC:80AE800000 \u2192 R:770A9F260818292A1ED56ED41B9F360278809000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343784Z" - } - }, - { - "id": "VI_MC_0148", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Reversals", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C51E4CD44B02FFC15280C82666E724AB56BC3E2E9000\nC:00B2020C00 \u2192 R:70160653250C37D7A4EFBC366E299815A14C913D89179000\nC:80AE800000 \u2192 R:770A9F2608E683CF34EF5520529F3602F5369000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343839Z" - } - }, - { - "id": "VI_MC_0149", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Testing", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70155AFE7D7735AD0A7E0FDC3EF1CF7C40B0C42557BA9000\nC:00B2020C00 \u2192 R:701652CB0AE38C42524ACE187D90541A17D8949A229B9000\nC:80AE800000 \u2192 R:770A9F2608EE1E2B57CECF650E9F36028C229000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343878Z" - } - }, - { - "id": "VI_MC_0150", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Card Communication", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C4DF44A6F1A0C57B180BCCAE103585AB885CEC649000\nC:00B2020C00 \u2192 R:7016B95748C763AC582A5AF5AC55C77AB373CBB0F8CA9000\nC:80AE800000 \u2192 R:770A9F26080AF987069323FF519F36026A789000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343916Z" - } - }, - { - "id": "VI_MC_0151", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Risk Management", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70156C92A9E3AA6365B6DF37DEA10843921B5EC3F14F9000\nC:00B2020C00 \u2192 R:701608B47BC54ADD1ADEE8954FAA8ADBA954932DA0409000\nC:80AE800000 \u2192 R:770A9F26081149B772743AA2609F3602AAF19000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343960Z" - } - }, - { - "id": "VI_MC_0152", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Keys & Certificates", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701553999CCF4F7DEE9D404B5B9626534624640921C09000\nC:00B2020C00 \u2192 R:701627D8F56EB05FC2E55BFEA8B8F4C41A42EC73C15E9000\nC:80AE800000 \u2192 R:770A9F26083F52E66E650A55469F3602D53D9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.343999Z" - } - }, - { - "id": "VI_MC_0153", - "brand": "MASTERCARD", - "type": "contact", - "category": "Risk Management", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction? (Scenario 153)", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701597475AB76A98D3FEF75C970A88F35EE055E251A79000\nC:00B2020C00 \u2192 R:7016EF36FA4744034BC165118FEEB6BB57C1160897C29000\nC:80AE800000 \u2192 R:770A9F2608A3E2B562045B02969F3602F8619000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344036Z" - } - }, - { - "id": "VI_MC_0154", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Brand-specific", - "question": "Why did the terminal queue a reversal after approval? (Scenario 154)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F26F234C1443653EDE413233CC345131E4AE76619000\nC:00B2020C00 \u2192 R:701696DCA605E934953290C4A0A449C406BBC206B4F09000\nC:80AE800000 \u2192 R:770A9F260837E3486DBABC94609F360282409000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344072Z" - } - }, - { - "id": "VI_MC_0155", - "brand": "MASTERCARD", - "type": "contact", - "category": "Card Communication", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 155)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015D3B5F7F8151E2DD0D74493AA8507917130BCFEBD9000\nC:00B2020C00 \u2192 R:701692BEBB9D578F348ED031133160D73EC82F5D103B9000\nC:80AE800000 \u2192 R:770A9F2608E3403A1E261DE3719F3602E7A29000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344108Z" - } - }, - { - "id": "VI_MC_0156", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Field 55", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B8F96C53600D5BBEDD8F0630A66C5E8DCD42B2749000\nC:00B2020C00 \u2192 R:7016F0118CDD39A0231EFE381087280A72A51819FCF79000\nC:80AE800000 \u2192 R:770A9F260826EE3DC93DC346F99F36021FF89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344144Z" - } - }, - { - "id": "VI_MC_0157", - "brand": "MASTERCARD", - "type": "contact", - "category": "APDU", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015AD5693E0285D406E1E532D1508327BE432E0902C9000\nC:00B2020C00 \u2192 R:701689453EB7EBE051081DFAF256C29C225F85D4ECF19000\nC:80AE800000 \u2192 R:770A9F260881B7382D3BD1F75F9F360297AC9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344191Z" - } - }, - { - "id": "VI_MC_0158", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Testing", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 158)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C591D9CC78D08E942E04A3C45B7D84078C71D48C9000\nC:00B2020C00 \u2192 R:7016F4E2D02292637B56D376FD0A5718A3CA05B89F489000\nC:80AE800000 \u2192 R:770A9F260833DA16980DC2FF249F3602810C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344239Z" - } - }, - { - "id": "VI_MC_0159", - "brand": "MASTERCARD", - "type": "contact", - "category": "Integration", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction? (Scenario 159)", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015382E8D37A5CC8D7CE9C92AA8A133451FB7C1B32F9000\nC:00B2020C00 \u2192 R:70162D17C6DA7D438AB1CF0109498519CC8DDFD1AD859000\nC:80AE800000 \u2192 R:770A9F260809ADBFEA0E9A760D9F360247B89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344276Z" - } - }, - { - "id": "VI_MC_0160", - "brand": "MASTERCARD", - "type": "contact", - "category": "Brand-specific", - "question": "Why did the terminal queue a reversal after approval? (Scenario 160)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70155DA913CAB710D5535495EDFF9C4A2C0325832B8C9000\nC:00B2020C00 \u2192 R:70161003FCFF4625BE08E4D85D24351687FA7DBC1EB59000\nC:80AE800000 \u2192 R:770A9F2608B859437A8B811D899F3602B9EA9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344313Z" - } - }, - { - "id": "VI_MC_0161", - "brand": "MASTERCARD", - "type": "contact", - "category": "Risk Management", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 161)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70153464E9F2EEC6795F506C52FB012C718A61C7A4879000\nC:00B2020C00 \u2192 R:7016A790132CEF92DB5888B88D16B2F6E30A734E8CD49000\nC:80AE800000 \u2192 R:770A9F260819AF4F38E48C712C9F360285849000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344352Z" - } - }, - { - "id": "VI_MC_0162", - "brand": "MASTERCARD", - "type": "contact", - "category": "Security", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015E577343F0C56516543130575002CEDC310FC30299000\nC:00B2020C00 \u2192 R:70166BC29179A721F8D46A9DA31060EC50B8ACE2A01D9000\nC:80AE800000 \u2192 R:770A9F2608DCD8220CB922790E9F3602A3C89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344390Z" - } - }, - { - "id": "VI_MC_0163", - "brand": "MASTERCARD", - "type": "contact", - "category": "Transaction Flow", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B6DD694CC5CE07D3FF2B0BD5BE2EC074024DBE5C9000\nC:00B2020C00 \u2192 R:70160920B42EBAA3EFE924F9C523482C4D8554FA2E189000\nC:80AE800000 \u2192 R:770A9F2608B843B9BF1AD4044B9F3602F0019000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344432Z" - } - }, - { - "id": "VI_MC_0164", - "brand": "MASTERCARD", - "type": "contact", - "category": "Issuer Scripts", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015AD81E5648F55A8012F558E724D2CB0F21B123B059000\nC:00B2020C00 \u2192 R:7016E32A5D21B7E14611E2DA00F829A974ED6DB488F39000\nC:80AE800000 \u2192 R:770A9F2608D24F6926218A14BC9F3602752E9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344470Z" - } - }, - { - "id": "VI_MC_0165", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Keys & Certificates", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015E87A4D1C8D1DE6789695A7C9C41AA1EE81CBEAB29000\nC:00B2020C00 \u2192 R:7016BC56501AA31F9037323EC304A9EC1550CB7A82509000\nC:80AE800000 \u2192 R:770A9F2608245EAB105D12A3A69F36025B8E9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344507Z" - } - }, - { - "id": "VI_MC_0166", - "brand": "MASTERCARD", - "type": "contactless", - "category": "CVM", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151F3E64E1BB07210C96906308B416D1922937A5BB9000\nC:00B2020C00 \u2192 R:70167BA41BC211DF00CD12CEF817F846699B700CFEC59000\nC:80AE800000 \u2192 R:770A9F2608AA065B02F6CA84C59F360293E89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344543Z" - } - }, - { - "id": "VI_MC_0167", - "brand": "MASTERCARD", - "type": "contact", - "category": "Integration", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70154779A32011D1B70D870432CCE7409AEAEA525D959000\nC:00B2020C00 \u2192 R:7016C177D504EBB528EE040E32B57056D5352B3F0B3D9000\nC:80AE800000 \u2192 R:770A9F260833D6BA2AEF53C11A9F36027F629000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344581Z" - } - }, - { - "id": "VI_MC_0168", - "brand": "MASTERCARD", - "type": "contact", - "category": "Certification Logs", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F58A91345F501569474418288F86432DB60404169000\nC:00B2020C00 \u2192 R:7016184744EFB437B6142DA1D8C601B7EEEBC37420529000\nC:80AE800000 \u2192 R:770A9F2608D2F9C156308782CC9F360254269000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344617Z" - } - }, - { - "id": "VI_MC_0169", - "brand": "MASTERCARD", - "type": "contact", - "category": "Keys & Certificates", - "question": "Why did the transaction fail after GENERATE AC? (Scenario 169)", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151BCBDCE1C7C42CBB199891EDC6967DB09C5E645C9000\nC:00B2020C00 \u2192 R:70164D329486D4AA8431F3D4792C876A749E5B1B77789000\nC:80AE800000 \u2192 R:770A9F260861722BFC0B8BEC8F9F3602AEC89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344672Z" - } - }, - { - "id": "VI_MC_0170", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Testing", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70157DBF8CCC2D68425A9B00A92A5C4ABCC9E5370E849000\nC:00B2020C00 \u2192 R:70167B385C3918675D39A961ED7E73003FB5432BE28A9000\nC:80AE800000 \u2192 R:770A9F260856B85DE88F13F6509F3602DA479000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344710Z" - } - }, - { - "id": "VI_MC_0171", - "brand": "MASTERCARD", - "type": "contact", - "category": "Security", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015DCAD66E03811B4E20BA1104F54295AE63D09736C9000\nC:00B2020C00 \u2192 R:70162F51636CBB4C505F7B4BB67454E76509BF7B747D9000\nC:80AE800000 \u2192 R:770A9F2608D2B1FC21E15CF3569F3602C1309000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344746Z" - } - }, - { - "id": "VI_MC_0172", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Testing", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70153B752FD88CF6AE8446644503984B455BC1C5A6B19000\nC:00B2020C00 \u2192 R:7016C7F72318CF8370FA793A4027C5C19C7FBC2A8F1B9000\nC:80AE800000 \u2192 R:770A9F2608A8252B2D822AAD809F36022C6A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344783Z" - } - }, - { - "id": "VI_MC_0173", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Keys & Certificates", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701551F04085D502F34249267DCEEC1F625DFF7254EC9000\nC:00B2020C00 \u2192 R:70160EAFDB769632CA960A57341532B0BFC89E9F01049000\nC:80AE800000 \u2192 R:770A9F2608DEC99DFC9EE92D6C9F3602BD189000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344820Z" - } - }, - { - "id": "VI_MC_0174", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Security", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 174)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70157BA7F61C8D5EE23B4C7A61BE05BB355ED6D972A99000\nC:00B2020C00 \u2192 R:7016ACB9DD79A89798293C7788E978D805471AD4F6839000\nC:80AE800000 \u2192 R:770A9F26087530E4153F1FA9B69F36029DBA9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344858Z" - } - }, - { - "id": "VI_MC_0175", - "brand": "MASTERCARD", - "type": "contact", - "category": "Reversals", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70154170198D9C247104B3436EACBC6AAF0D2628B9689000\nC:00B2020C00 \u2192 R:7016ACC7227B16956D541769E958D63097EDC01A48C19000\nC:80AE800000 \u2192 R:770A9F260842FE92E86196A1479F3602B1559000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344915Z" - } - }, - { - "id": "VI_MC_0176", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Integration", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70155EA5664470404AC366070768DEE23DEB0ED4FBA79000\nC:00B2020C00 \u2192 R:7016158B612578F570684149E202E55491B1ED8E3FFA9000\nC:80AE800000 \u2192 R:770A9F26088D3581CB7E4F4A259F36024A1A9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.344960Z" - } - }, - { - "id": "VI_MC_0177", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Security", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015847F76E25342213E17BD12E1F9174B38B5A3F3559000\nC:00B2020C00 \u2192 R:70164FC877E550B9443C5CA8C66066999E09FA08E0509000\nC:80AE800000 \u2192 R:770A9F2608BCB2A6EF85CD65AD9F3602785E9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345029Z" - } - }, - { - "id": "VI_MC_0178", - "brand": "MASTERCARD", - "type": "contact", - "category": "CVM", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70155B40D2CB2440B54932AD614AAC7D7E4D5951DC2A9000\nC:00B2020C00 \u2192 R:701680A36637118752254352B93B4DDFC9033A81C9949000\nC:80AE800000 \u2192 R:770A9F260801C5FEF7AACC9C939F3602D4699000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345066Z" - } - }, - { - "id": "VI_MC_0179", - "brand": "MASTERCARD", - "type": "contact", - "category": "CVM", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015D452650921958639F32FE4D83563017DDD05010B9000\nC:00B2020C00 \u2192 R:701665A6C630A1A58770B5D511ECD5ED7756C66FD2A39000\nC:80AE800000 \u2192 R:770A9F2608C5CE37D9302645679F3602437B9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345104Z" - } - }, - { - "id": "VI_MC_0180", - "brand": "MASTERCARD", - "type": "contact", - "category": "Terminal Configuration", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015FA0CFFC31DB5038724EED3E3BD79BF504CCBCC5B9000\nC:00B2020C00 \u2192 R:701634AE695AA78D0E940E8F4DD92ECF00E9F8B9C8269000\nC:80AE800000 \u2192 R:770A9F260893DE79EA6C3C90899F3602A05C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345141Z" - } - }, - { - "id": "VI_MC_0181", - "brand": "MASTERCARD", - "type": "contact", - "category": "CVM", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015315C4E1CC910588B37061AF97F83BD704EB010619000\nC:00B2020C00 \u2192 R:7016BCC3B60BC9386E9DE1F03F5D1036DB317899841C9000\nC:80AE800000 \u2192 R:770A9F2608F8ADCB591C443ABD9F3602F4AD9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345195Z" - } - }, - { - "id": "VI_MC_0182", - "brand": "MASTERCARD", - "type": "contact", - "category": "Reversals", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701530A769E08F9FC99AB7DA5377A0F249AB635107C49000\nC:00B2020C00 \u2192 R:7016522F74EF5D87BAAA5595B4A3C3AFB2E21A11B9289000\nC:80AE800000 \u2192 R:770A9F2608EE98F7B6B49E93E39F3602B9E69000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345231Z" - } - }, - { - "id": "VI_MC_0183", - "brand": "MASTERCARD", - "type": "contact", - "category": "Brand-specific", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction? (Scenario 183)", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151A7F07636D22675D1F52B5FF609D5A2A53E9DA6A9000\nC:00B2020C00 \u2192 R:70167F133BDF698CF2FEC5C2976C48CD8A10131AF7079000\nC:80AE800000 \u2192 R:770A9F2608A532D9959C89EBE59F3602BFAB9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345281Z" - } - }, - { - "id": "VI_MC_0184", - "brand": "MASTERCARD", - "type": "contact", - "category": "Integration", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151542EE2496E2E0A98A386DF5C325606AD327F28A9000\nC:00B2020C00 \u2192 R:70160053EE1BA4DD67B2A0E0A64C03372074F94AB37D9000\nC:80AE800000 \u2192 R:770A9F260811A3319A1496E6C29F3602AF6C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345319Z" - } - }, - { - "id": "VI_MC_0185", - "brand": "MASTERCARD", - "type": "contactless", - "category": "CVM", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY?", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701526BC76B710AAD2B9E72ACC7F5BB33C97C147FF5E9000\nC:00B2020C00 \u2192 R:701605DCD0A7952C882D213EA6A9D81B31604F6084FD9000\nC:80AE800000 \u2192 R:770A9F26086D43888E37A60D1D9F3602FC809000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345363Z" - } - }, - { - "id": "VI_MC_0186", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Security", - "question": "Why does the contactless flow go online while contact remains offline? (Scenario 186)", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015E8AB37AE4F3E860D33C816962F6FEB776C9FE0839000\nC:00B2020C00 \u2192 R:70167003B6D054C4B851825721BEE4088201F83658B79000\nC:80AE800000 \u2192 R:770A9F260821F93448E0F4C8D69F360255B29000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345400Z" - } - }, - { - "id": "VI_MC_0187", - "brand": "MASTERCARD", - "type": "contact", - "category": "Transaction Flow", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015590865D331169CD3C61F04CE51411A7CD42B6D009000\nC:00B2020C00 \u2192 R:7016AEFA013F74A00E6E261E55236C1F2CF45308A8D39000\nC:80AE800000 \u2192 R:770A9F2608F352F0E897D147999F360245B49000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345446Z" - } - }, - { - "id": "VI_MC_0188", - "brand": "MASTERCARD", - "type": "contact", - "category": "Transaction Flow", - "question": "Why is Field 55 causing ARQC verification failures at the issuer? (Scenario 188)", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70154A56824089EF5C065DBA374FD2E9048BBB3C14339000\nC:00B2020C00 \u2192 R:70163A25DC9D8FDD46EC1089E807E231F942D911C6C49000\nC:80AE800000 \u2192 R:770A9F26086A788D8E1537DA8D9F360254059000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345503Z" - } - }, - { - "id": "VI_MC_0189", - "brand": "MASTERCARD", - "type": "contact", - "category": "Transaction Flow", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F40BA0660100C79CE73002383C002C474F6EE1C09000\nC:00B2020C00 \u2192 R:7016A92DF8C7110877D337E232A2B8A49406802B6A789000\nC:80AE800000 \u2192 R:770A9F2608DD0EAC898CDE41319F360248049000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345541Z" - } - }, - { - "id": "VI_MC_0190", - "brand": "MASTERCARD", - "type": "contact", - "category": "Risk Management", - "question": "Why did the terminal queue a reversal after approval? (Scenario 190)", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:701547E904C41B2F8A4E7B6D957BE0092534A33D25AB9000\nC:00B2020C00 \u2192 R:701609C311E5718DD012474E202564D2B2408B0FDDA79000\nC:80AE800000 \u2192 R:770A9F260889C1954ED79C032A9F360270BF9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345579Z" - } - }, - { - "id": "VI_MC_0191", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Certification Logs", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 191)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015F487BD2FD55A34E5CE0CDCBC4482EDE89FE2516B9000\nC:00B2020C00 \u2192 R:701601D39F9447A86919DC4342AD8B5B850C89233F629000\nC:80AE800000 \u2192 R:770A9F26084E70D797A9528D0C9F3602C80B9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345616Z" - } - }, - { - "id": "VI_MC_0192", - "brand": "MASTERCARD", - "type": "contact", - "category": "Settlement", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015525B96825703C19D07F43C1165163E12281069F39000\nC:00B2020C00 \u2192 R:701673F3ED13C4B1839EAB0326EA7A530F5E0F4E17E39000\nC:80AE800000 \u2192 R:770A9F2608D3D03F446C8FF36F9F3602A71E9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345653Z" - } - }, - { - "id": "VI_MC_0193", - "brand": "MASTERCARD", - "type": "contact", - "category": "Brand-specific", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70150590BBE10589646C553C1CCBE8CF0CEB2D37B42A9000\nC:00B2020C00 \u2192 R:701613D94C20F066B1859637499270093D20A7143B2C9000\nC:80AE800000 \u2192 R:770A9F2608FBC9C77A79220A039F36028FD89000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345689Z" - } - }, - { - "id": "VI_MC_0194", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Integration", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70153AF7AA342EFA347BF3AB84C1E57C0499DB8DEE419000\nC:00B2020C00 \u2192 R:7016B2E30E61E3BC8F7F163FA9705E929AE5C155A8CC9000\nC:80AE800000 \u2192 R:770A9F26084E591EDD840EC64F9F360226A69000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345726Z" - } - }, - { - "id": "VI_MC_0195", - "brand": "MASTERCARD", - "type": "contact", - "category": "Reversals", - "question": "Why did the terminal prompt for signature instead of PIN for a contactless transaction?", - "answer": { - "summary": "CVM selection may have favored signature due to TTQ/CVM limits, or CDCVM was not available/recognized. The terminal must follow kernel CVM processing; signature can appear if PIN is not supported or CVM limit thresholds apply.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015B46DF1D08C751AB780B04F6D2AED80A6ADE1FEFA9000\nC:00B2020C00 \u2192 R:7016B85D207845F6C4E651554F332EBFD3F3D5195B399000\nC:80AE800000 \u2192 R:770A9F26088C71B53D065505D09F3602385C9000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345763Z" - } - }, - { - "id": "VI_MC_0196", - "brand": "MASTERCARD", - "type": "contact", - "category": "Card Communication", - "question": "Why did the terminal queue a reversal after approval?", - "answer": { - "summary": "A reversal was triggered because the terminal did not receive confirmation of capture/settlement from the host, or ARPC/issuer authentication failed after approval. Reversals must reference original STAN and RRN.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70151D02EE062C6E1A019665DE588C73E58ED7071CA89000\nC:00B2020C00 \u2192 R:701615BA3774E5F5253C7B19D14DDECA5E59B6F8B0E09000\nC:80AE800000 \u2192 R:770A9F2608D90DFBD0510351559F36022B979000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345800Z" - } - }, - { - "id": "VI_MC_0197", - "brand": "MASTERCARD", - "type": "contact", - "category": "Brand-specific", - "question": "What causes '6985 Conditions of use not satisfied' during VERIFY? (Scenario 197)", - "answer": { - "summary": "This SW indicates that card conditions for the VERIFY operation are not met\u2014commonly due to PIN block format mismatch, blocked PIN, or security status disallowing VERIFY. Check PIN try counter and card CVM capabilities.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015755B6765057B214BAB137A9A17C96676597C5D409000\nC:00B2020C00 \u2192 R:70160B73488251EACA41347FC62FE9B8520C5826EA349000\nC:80AE800000 \u2192 R:770A9F26085CE273FB7C4D8FA49F3602C8C39000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345836Z" - } - }, - { - "id": "VI_MC_0198", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Certification Logs", - "question": "Why does the contactless flow go online while contact remains offline?", - "answer": { - "summary": "Contactless kernels often have lower floor limits and different risk parameters; contactless may also be configured to always online for certain AIDs. Compare TTQ and kernel risk settings between contact/contactless flows.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:70153E70058A4816532B7AB0A386433971EFE48E4B849000\nC:00B2020C00 \u2192 R:70164278A3509FF1DFC6675DB3B15AE9D81AB65ADF4C9000\nC:80AE800000 \u2192 R:770A9F2608508CF45B96AB2C559F360255B09000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345873Z" - } - }, - { - "id": "VI_MC_0199", - "brand": "MASTERCARD", - "type": "contactless", - "category": "Reversals", - "question": "Why did the transaction fail after GENERATE AC?", - "answer": { - "summary": "The GENERATE AC response returned a cryptogram (9F26) but the host or terminal logic interpreted it as a failure. This can happen for multiple reasons: missing PDOL data, incorrect Unpredictable Number (9F37), or mismatch in ATC (9F36).", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A404000E325041592E5359532E4444463031 \u2192 R: 6F228408325041592E5359532E4444463031A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015C59E5D68502557829500DC5E14DC08A1BD652F919000\nC:00B2020C00 \u2192 R:70160721277B65459E227C01D04EF1AC8C3D1FD4C96B9000\nC:80AE800000 \u2192 R:770A9F260800A7E568D2ED47369F36026D309000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345916Z" - } - }, - { - "id": "VI_MC_0200", - "brand": "MASTERCARD", - "type": "contact", - "category": "Issuer Scripts", - "question": "Why is Field 55 causing ARQC verification failures at the issuer?", - "answer": { - "summary": "Field 55 TLV encoding may be malformed, missing mandatory tags (9F26, 9F36, 95), or has incorrect length encoding for long values, leading to issuer-side ARQC recomputation mismatches.", - "details": [ - "Step 1: Verify APDU trace for missing or malformed PDOL/GET PROCESSING OPTIONS exchange.", - "Step 2: Parse the Field 55 TLV payload and ensure mandatory tags are present and correctly encoded (e.g., 9F26, 9F36, 95, 5F2A).", - "Step 3: Check terminal unpredictable number generation entropy (9F37) and ATC monotonicity.", - "Step 4: Correlate STAN/RRN with host traces to determine whether host-side ARQC recompute failed.", - "Step 5: If issuer authentication (ARPC) is present, validate ARPC format and confirm the terminal's ARPC verification logic if implemented." - ], - "example_log_snippet": "C: 00A4040007A0000000031010 \u2192 R: 6F228408A0000000031010A5138801015F2D04656E6672\nC: 80A8000002830000 \u2192 R: 770A82023800940208010100\nC:00B2010C00 \u2192 R:7015D9463CB8936E5EFCBFD1D689518D2FAA3E02F6599000\nC:00B2020C00 \u2192 R:701651597E9882F578BDA6C8E05B9B7C4D18E56D82009000\nC:80AE800000 \u2192 R:770A9F2608A7AAF852C87A017F9F360228D19000", - "resolution_steps": [ - "Resolution 1: Reconstruct Field 55 from raw APDU traces using a canonical TLV encoder and resend to host for validation.", - "Resolution 2: Ensure GET PROCESSING OPTIONS includes required PDOL elements; update terminal config if fields missing.", - "Resolution 3: Use test CAPKs in certification environment; confirm CAPK RID/Index and modulus/exponent match issuer test keys.", - "Resolution 4: If ARPC is returned and verification fails, escalate to issuer with logs including 9F26, 9F36, 95, and 9F10." - ], - "notes": "Generated for certification batch; created_at: 2025-10-29T06:36:17.345952Z" - } - }, - { - "id": "VI_MC_0201", - "brand": "VISA", - "type": "contact", - "category": "Field 55", - "question": "What exact tags should be present in Field 55 for an online EMV authorization in Visa testing?", - "answer": { - "summary": "For Visa online authorizations, Field 55 should include at minimum the following TLVs: 9F26, 9F27, 9F36, 95, 9B, 5F2A, 9F02, 9F1A, 9A, 9C, 9F37, 82, 94, and 9F10 where applicable.", - "details": [ - "9F26 (Application Cryptogram - ARQC/TC)", - "9F27 (Cryptogram Information Data)", - "9F36 (ATC)", - "95 (TVR)", - "9B (TSI)", - "5F2A (Transaction Currency Code)", - "9F02 (Amount)", - "9F1A (Terminal Country Code)", - "9A (Transaction Date)", - "9C (Transaction Type)", - "9F37 (Unpredictable Number)", - "82 (AIP)", - "94 (AFL)", - "9F10 (Issuer Application Data) - where provided by card" - ], - "example_log_snippet": "Field55(hex): 9F2608A1B2C3D4E5F6019F2701809F3602000195028000045F2A0203569F02060000000010009F1A0203569A032103149C01009F3704A1B2C3D4", - "resolution_steps": [ - "Validate TLV presence and lengths with a canonical parser.", - "If tags missing, enable debug logging in kernel to see why card omitted them or terminal dropped them.", - "Coordinate with host regarding any additional tags they require beyond the common set." - ], - "notes": "Visa-specific; ensure mapping to ISO fields per acquirer guidance." - } - }, - { - "id": "VI_MC_0202", - "brand": "MASTERCARD", - "type": "contactless", - "category": "CVM", - "question": "Why does Mastercard contactless choose signature instead of CDCVM on a mobile wallet?", - "answer": { - "summary": "Mastercard kernel chooses CVM based on TTQ, kernel configuration, and the card's CVM list. If CDCVM is advertised but not accepted by the terminal or kernel flags, signature may be selected.", - "details": [ - "Ensure TTQ indicates support for CDCVM (bit in TTQ).", - "Verify that the mobile wallet actually provided CDCVM indication in the contactless kernel data.", - "Confirm terminal kernel and acquirer support CDCVM mapping to host fields." - ], - "example_log_snippet": "TTQ: E0 00 00 00 ; CVM List: 0E 00 00 ; Kernel: M/Chip Contactless -> 9F34: 1E0300 (signature)", - "resolution_steps": [ - "Update terminal TTQ configuration to advertise CDCVM support.", - "Coordinate with mobile wallet vendor to ensure CDCVM flag is set in the token.", - "If signature is acceptable per merchant, document behavior; otherwise update configuration and retest." - ], - "notes": "Mastercard-specific guidance; CDCVM often involves wallet+terminal coordination." - } - } -] \ No newline at end of file