...
a file is pushed to the terminal to feed the required tags.
File Format:
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) | |
Agnos RuPay Key FF34 | Composed TLV | Tag containing each 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 FF34 | |
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 | |
DF99 | unsigned char[5] | RuPay Terminal Service Qualifier part of composed FF03 |
in a FF32 tag, we can have one or more keys (FF34)
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.
...
must contains one of more service definition handled by the terminal