...
Field | Format | Description and Rule | Example |
---|---|---|---|
Version | unsigned char | 0xAA by default | AA |
SHA | unsigned char Sha[20] | SHA signature on contents | |
AGNOS RuPay Key List FF32 | Composed TLV | tag , containing all Key definition (FF34) for the terminal | |
Agnos RuPay Key FF34 | Composed TLV | Tag containing each terminal key definition | |
DF16 | unsigned char[2] | Service ID TLV, part of composed FF34 | DF16021010 |
DF52 | unsigned char[N] | KCV key TLV, part of composed FF34 | |
DF48 | Unsigned char [N] | PRMacq Key TLV, part of composed FF34 | |
DF71 | unsigned char [1] | Key Index TLV, part of composed FF34 | DF710101 |
DF47 | unsigned char [N] | PRMiss Key, part of the composed a single FF34 tag | |
Level 3 Configuration for Services | |||
FF02 | unsigned char [N] | Agnos RuPay Service List composed tag | List of service supported by the terminal |
FF03 | unsigned char [N] | Service Definition composed tag | One Service definition supported by the terminal |
DF16 | unsigned char[2] | Service ID TLV, part of composed FF03 | DF16021010 |
DF45 | unsigned char [N] | Terminal Service Data , part of composed FF03 | DF453B09101506150101112233445566778800000100010061150406125703000000010000020000000A0101000A01020502000102010206000A01010302 |
DF6F | unsigned char[5] | RuPay Terminal Service Qualifier part of composed FF03 | DF6F050810109500 |
in a FF32 tag, we can have one or more keys (FF34).
Tag FF12 FF32 (AGNOS_RUPAY_SERVICES_LIST) must be present for requesting tag DF07 in the final select. It’s a composed tag containing all services supported and data required for these services (excepted keys).
...
Example of Service key / terminal definition file:
...
...
There is one level 3 definition file named SERVICE_CONFXX__RUPAY to sent to the device using TMS->RuPay->Send Service File for each tool SERVICE configuration.