Service Configuration
Entry Point Template
See Configuration page.
Transaction Related Data
Use the following tags (5F3601025F2A020356) in Other TLVs section:
5F360102 Transaction Currency Exponent
5F2A020356 Transaction Currency Code
See Transaction page.
Administrative Settings
Set ID Message Display = 1 in Administrative to clarify the identification of the message in the signals tab
For tests requiring the TVR, set Always Receipt = 1 in Administrative. Set Always Receipt = 0 for tests on record printing.
See TMS/Administrative dialog.
Test Case Execution
TA's configurations are driven by the tools that are used to qualify a kernel. For Interac Flash, ICC Solution is accredited. That tool doesn't define any configuration for each test case. Hence, the tester shall adapt the default configuration (CONF_01) depending on the test requirements.
Note:
PROCESSING message display may be removed using flag in DF1B.
Terminal Country Code must be set to 0356 in TERMINAL configuration
Service Terminal Configuration/Service Keys
For test cases requiring Services, some tags are mandatory to initiate the Data Exchange mechanism.
a file is pushed to the terminal to feed the required tags.
Tag FF12 (AGNOS_RUPAY_SERVICES_LIST) must be present for requesting tag DF07 in the final select.
Rupay Service List Data, this FF02 must be present in the configuration. It’s a composed tag containing all services supported and data required for these services (excepted keys).
FF02 Structure:
FF02 variable Length
FF03 Variable Length including these 3 TLVs below:
DF16 Terminal Service ID on 2 bytes
DF45 Terminal Service Data (variable length) AGNOS_SERVICE_DATA_FROM_CONFIGURATION
DF99 RuPay Terminal Service Qualifier on 5 bytes.
FF03 … (for another service supported by terminal) if any…