Agnos Visa C3 v2.x
The list of options presented presented here reflects the qualification reference used at Amadis to test Agnos kernels with appropriate tools (EVAL or ICC Solutions). It doesn't reflect TA requirements nor most up-to-date optional/mantory features released by payment networks. Please refer to your lab to validate your ICS before any debug or TA.
The VISA checksum is calculated dynamically versus the ICS. A specific tag 0xDF1A is used to set the TTQ. It must be added and updated in all combinations in “Other TLV(s)” section (ENTRYPOINT tab) with the TTQ ICS value.
This reference ICS doesn't document Visa values to be set (i.e., customers requirements) but Agnos supported values and how to set them in regards with any potential MSD/qVSDC ICS.
*VCPS: Visa Contactless Payment Specification
*VCTKS: Visa Contactless Transit Kernel Specification
*VRPTKS: Visa Ready Tap to Phone Kernel Specification
*VOQOS: Visa ODA for qVSDC Online Specification
VCPS and VCTKS Reference ICS
Reader Characteristics | Reference Values | Agnos | Configuration Values | Recommendations | Comments |
|---|---|---|---|---|---|
Additional Interfaces | |||||
1.1 - Is Contact Interface supported? | Yes/No | Optional | Yes | Use TERMINAL and COMBINATION to set the values Depends on the platform | |
1.2 - Does the device support Magnetic Stripe transactions? | Yes/No | Optional | No | Depends on the platform | |
VCPS Options | |||||
2.1 - Does this product support MSD? (Magstripe processing) | Yes/No | Optional | Yes | Might be exclusive. Use COMBINATION to set the values If VCPS v2.2 or higher, select NO. | |
2.2 - Does this product support qVSDC? (EMV Processing) | Yes/No | Optional | Yes | Might be exclusive. Use COMBINATION to set the values If VCPS v2.2 or higher, select YES (Mandatory) | |
2.3 - Does the device support MSD and qVSDC active together? | Yes/No | Optional | Yes | Use COMBINATION to set the value If VCPS v2.2 or higher, select NO. | |
qVSDC Options | |||||
2.4 - Preliminary Transaction Processing is supported? | Yes/No | Optional | N/A | YES | If 3.4 is checked, 3.5, 3.10, 3.11, 3.12 and 3.13 must be checked supported |
2.5 - Status Check is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the value | |
2.6 - Key Revocation is supported? | Yes/No | Optional | N/A | No | Use REVOCATED CAKEYS to activate the option |
2.7 - Exception File is supported? | No | Not Supported | N/A | No | L3 perspective |
2.8 - Signature is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the value | |
2.9 - Online PIN is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the value | |
2.10 - Contactless Floor Limit Check is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the values | |
2.11 - Contactless Transaction Limit Check is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the values | |
2.12 - Amount Authorized Zero Check is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the value | |
2.13 - CVM Required Limit Check is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the values | |
2.14 - Terminal Floor Limit Check is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the value | |
2.15 - Variable Transaction Amount is supported? | Yes/No | Optional | Yes | Use TRD to set the value | |
2.16 - Application Expiry Check is supported? | Yes | Mandatory | Fixed | Yes | |
2.17 - Issuer Update Processing is supported? | No | Not Supported | No | ||
2.18 - Manual Cash is supported? | Yes/No | Optional | No | Use COMBINATION to set the value | |
2.19 - Cashback is supported? | Yes/No | Optional | No | Use COMBINATION to set the value | |
2.20 - Refund is supported? | Yes | Mandatory | Fixed | Yes | |
2.21 - Dynamic Reader Limits is supported? | Yes/No | Optional | No | Use COMBINATION to set the value | |
2.21.1 - Maximum Dynamic Reader Limits sets is supported? | 4 | Mandatory | Fixed | 4 | |
2.22 - Contactless Floor Limit data element is supported? | Yes | Mandatory | Yes | Use COMBINATION to set the value | |
2.23 - The device is offline only? | Yes/No | Optional | No | Use COMBINATION to set the value | |
2.24 - The device is online only? | Yes/No | Optional | No (Yes*) | Use COMBINATION to set the value NOTE: * Only set to Yes if Terminal is intended to be Online Only in the field | |
2.25 - The Contactless Interface powered on even though the contactless interface for applications is not allowed? | No | Not Supported | N/A | No | Depends on the platform |
2.26 - The device supports both online capable and offline capable? | Yes/No | Optional | Yes | Use COMBINATION to set the values | |
2.27 If DF name tag 84 is a mandatory element in Select PPSE Response | No | Mandatory | N/A | No | N/A |
2.28 if DF name tag 0x84 is a mandatory element in Select ADF Response | Yes | Mandatory | N/A | Yes | N/A |
MSD options | |||||
2.30 - Track1 formatting to the host is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the value. In line with MSD support not applicable for VCPS v2.2 | |
2.31 - Track2 formatting to the host is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the value. In line with MSD support not applicable for VCPS v2.2 | |
2.32 - TTQ are sent in online messages? | Yes | Mandatory | Fixed | Yes | not applicable for VCPS v2.2 |
2.33 - Zero Amount Authorized is supported? | Yes | Mandatory | Fixed | Yes | not applicable for VCPS v2.2 |
VCTKS Options | |||||
3.1 - Does the device power down the RF field in between transactions or when certain Status Words are returned | Yes | Mandatory | Fixed | Yes | |
3.2 - Is Key Revocation supported? | Yes/No | Optional | N/A | No | Use REVOCATED CAKEYS to activate the option |
3.3 - Exception File Check supported? | No | Not Supported | N/A | No | L3 perspective |
3.4 - Additional IDs in POI information supported? | Yes | Optional | N/A | Yes | To be left unchecked for VCTKS v1.0.2 |
General Reader Options | |||||
5.1 - The device supports a display? | Yes/No | Optional | N/A | Yes | L3 perspective. Depends on the platform |
5.1.1 - The Amount Authorized is displayed when prompting for card presentation? | Yes/No | Optional | N/A | Yes | L3 perspective (Yes if display supported. Else No) |
5.1.2 - The Available Offline Spending Amount can be displayed? | Yes/No | Conditional | Fixed | Yes | L3 perspective (Yes if display supported. Else No) |
5.2 - The device supports a printer? | Yes/No | Optional | N/A | Yes | L3 perspective. Depends on the platform |
5.2.1 - The Available Offline Spending Amount can be printed? | Yes/No | Conditional | Fixed | Yes | L3 perspective (Yes if printer supported. Else No). Depends on the platform |
5.2.2 - Printing of a receipt for declined transactions supported? | Yes/No | Optional | Always Receipt flag | Yes | L3 perspective (Yes if printer supported. Else No). Use agnos.ini to always print |
5.2.3 - Printing of a receipt for approved transactions supported? | Yes/No | Optional | Always Receipt flag | Yes | L3 perspective (Yes if printer supported. Else No). Use agnos.ini to always print |
Reader Compliant to Visa Contactless Reader Implementation Notes | |||||
IRWIN | No | Not Supported | N/A | N/A | |
VRTPKS ICS
Reader Characteristics | Reference Values | Agnos | Configuration Values | Recommendations | Comments |
|---|---|---|---|---|---|
Recommended qVSDC Options | |||||
3.3 - Signature is supported? | Yes | Mandatory | Yes | Use COMBINATION to set the value | |
3.4 - Online PIN is supported? | Yes/No | Optional | Yes | Use COMBINATION to set the value | |
3.8 - CVM Required Limit Check is supported? | Yes | Mandatory | Yes | Use COMBINATION to set the values | |
3.9 - Refund is supported? | Yes | Mandatory | Fixed | N/A | |
3.11 - The device is online only? | Yes | Mandatory | Yes | Use COMBINATION to set the value | |
Other qVSDC Options | |||||
4.5 - Manual Cash is supported? | Yes/No | Optional | No | Use COMBINATION to set the value | |
4.6 - Cashback is supported? | Yes/No | Optional | No | Use COMBINATION to set the value | |
General Options | |||||
6.1 - The device supports a display? | Yes/No | Optional | N/A | Yes | L3 perspective. Depends on the platform |
6.1.1 - The Amount Authorized is displayed when prompting for card presentation? | Yes/No | Optional | N/A | Yes | L3 perspective (Yes if display supported. Else No) |
6.2 - The device supports a printer? | Yes/No | Optional | N/A | Yes | L3 perspective. Depends on the platform |
6.2.2 - Printing of a receipt for declined transactions supported? | Yes/No | Optional | Always Receipt flag | Yes | L3 perspective (Yes if printer supported. Else No). Use agnos.ini to always print |
6.2.3 - Printing of a receipt for approved transactions supported? | Yes/No | Optional | Always Receipt flag | Yes | L3 perspective (Yes if printer supported. Else No). Use agnos.ini to always print |
Reader Compliant to Visa Contactless Reader Implementation Notes | |||||
IRWIN | No | Not Supported | N/A | N/A | |
ICS VISA Checksum Calculation
1) Preliminary
A unique checksum must be set in the VISA ICS and retrieved using a test tool such as ACE Client.
This describes how to generate it.
2) Checksum Calculation for VISA ICS
The dynamic checksum is function of TTQ options.
This chapter explains how to transcript the VISA ICS features to the TTQ prior to calculate the checksum:
2.1 ) TTQ transcription
1.8 Magstripe Mode:
Reflects the MSD Visa Application:
1.6 EMV Mode:
Reflects the qVSDC Visa Application:
1.5 Emv Contact Chip:
To set if the contact interface is present and used
1.4 OffLine Only:
Static option reflecting this ICS option:
1.3 Online Pin:
Reflects this ICS option:
1.2 Signature:
Reflects this ICS option:
1.1 ODA With online Auth:
Reflects this ICS option:
2.8 Online Cryptogram:
Dynamic flag, by default set to 0 (Reset in transaction pre-processing)
2.7 CVM Required:
Dynamic flag, by default set to 0 (Reset in transaction pre-processing)
2.6 Offline Pin:
Not applicable must be set to 0
3.8 Issuer Script:
Reflects this ICS option, not supported by Agnos, must be set to 0.
3.7 Mobile CVM:
Mandatory, must always be set to 1.
2.2) Procedure to generate the checksum with ACE Client:
2.2.1)O n any VISA combination add a 0xDF1A tag in other TLV section reflecting the ICS’ TTQ
Such as for example:
DF1A04A7004000
2.2.2) Send the ENTRYPOINT updated configuration to the device.
2.2.3) Initiate a PURCHASE transaction
2.2.4) Cancel it on the device
2.2.5) Request the Configuration checksum.
The TTQ displayed after the kernel CLx version, with the checksum must be set accordingly to the VISA ICS TTQ. Even if you change tag 9F66 during the testing the checksum will allways stays at the value reflecting tag 0xDF1A.
For example the default TTQ is the following one:
Tag 0xDF1A must reflect this value.
This gives the following VISA checksum for example:
CL2: C3.2.5 [A7004000]-> v1.1.29_c [0F91F84B91CFD99C499D36C912E14E2C8C332E8E]