...
...
...
...
...
PayPass v3.1.
...
4
...
The list of options 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 the most up-to-date optional/mantory mandatory features released by payment networks. Please refer to your lab to validate your ICS before any debug or TA.
This reference ICS page doesn't document Mastercard values to be set (i.e., customers' requirements) but Agnos supported values and how to set them in regards with regard to any potential Paypass PayPass ICS.
Reader Characteristics
Reference Values | Agnos | Configuration Values | Recommendations | Comments |
|---|
EntryPoint
Yes/No
Optionnal
PayPass Legacy flag
No
Use agnos.ini to set the value
Mode 1(*)
N/A
Optional
Fixed
Implementation Options | |||||
|---|---|---|---|---|---|
Contactless Mag-stripe | No | Not Supported | Fixed | No |
|
|
Mode 2(*)
N/A
Not Supported
N/A
N/A
N/A
Mode 3(*)
N/A
Not Supported
N/A
N/A
N/A
Mode 4(*)
Send POI Information | Yes/No | Optional | Fixed | No |
_MASTERCARD_SPI_ |
SB-261 | Yes/No | Optional | Fixed | No | |
DE/DS | Yes/No | Optional | Fixed |
N/A
Compile with flags _PAYPASS3X_MAGSTRIPE_MODE_SUPPORTED
Compile with flags _PAYPASS3X_IDS_TORN_SUPPORTED
(*): For security reasons (related to CPOC solutions), ICS options are managed like implementation options.
Worksheet 5: Implementation Information
5.1 Implementation options:
...
Abbreviation
...
Description
...
Supported
...
Contactless Mag-stripe
...
Does the submitted product implement the Contactless Mag-stripe transaction flow ?
If not, then the product only implements the Contactless EMV transaction flow.
(Related to the implementation of the Specification bulletin SB238)
...
- YES
- NO
...
Integrated Data Storage /
Torn Transaction
...
Does the submitted product implement both the Integrated Data Storage and Torn Transaction?
(Related to the implementation of the Specification bulletin SB239)
...
- YES
- NO
...
SEND POI INFORMATION
...
Does the submitted product implement the SPI command?
...
- YES
- NO
...
5.2 Application Selection:
Q: If the product supports a proprietary application selection mechanism prior to activation of Process S, please describe it. See [MCL 3.1.3] section "3.1 Introduction" for further details.
A: Our kernel is not supporting any proprietary mechanism.
5.3 Application Selection Registered Proprietary Data (ASRPD):
Q: If the product supports the ASRPD (see EMVCo bulletin SB-175), please list the values supported/recognized. If so, please also be precise if the product under test implements the related ASRPD mechanism, or if it will be implemented in the Level3 application.
A: ASRPD is not supported.
Worksheet 4: Product Identification
4.4 Automation:
Description
Supported
No | Option should be evaluated in line with SB-261 configuration. | ||||
IDS and Torn | Yes/No | Optional | Fixed | No | Option should be evaluated in line with SB-261 configuration. |
Mobile POS | Yes/No | Optional | Fixed | No | |
Transit | Yes/No | Optional | Fixed | No |
Automation Options | ||
|---|---|---|
Does the product support the automation interface defined in [TestEnv] Annex D? | ||
YES
Do you want your product to be tested in automated mode?
Yes/No | ACE-Client version should be compliant if automation is required. | |
Does the product also support the optional signals? |
| |
|
|
|
|
| ||
Does the product also support the card-product automation interface signals (also called PCD bypass mode)? (*) | NO | |
Implementation Information & Testing Environment | |
|---|---|
Proprietary application selection mechanism | Amadis kernel does not support any proprietary mechanism. |
Application Selection Registered Proprietary Data | ASRPD is not supported. |