Share CID Manufacturer_Name Status Firmware_Version Card_PublicKey Settings_Mask Is_Reusable Use_Activation Prohibit_Purge_Wallet Use_Block Allow_SET_PIN1 Allow_SET_PIN2 Use_CVC Prohibit_Default_PIN1 Use_One_CommandAtTime Use_NDEF Use_Dynamic_NDEF Smart_Security_Delay Allow_Unencrypted Allow_Fast_Encryption Protect_Issuer_Data_Against_Replay Allow_Select_Blockchain Disable_Precomputed_NDEF Skip_Security_Delay_If_Validated_By_Issuer Skip_Check_PIN2_and_CVC_If_Validated_By_Issuer Skip_Security_Delay_If_Validated_By_Linked_Terminal Restrict_Overwrite_Issuer_Extra_Data 1 – prohibit overwriting Issuer_Extra_Data Require_Term_Tx_Signature Require_Term_Cert_Signature Check_PIN3_on_Card Card_Data Issuer_Data_PublicKey Curve_ID Max_Signatures Signing_Method Pause_Before_PIN2 Wallet_PublicKey Wallet_Remaining_Signatures Wallet_Signed_Hashes Health Is_Activated Activation_Seed Payment_Flow_Version User_Counter User_Protected_Counter Unique Tangem card ID number Name of Tangem card manufacturer Current status of the card Version of Tangem COS Public key that is used to authenticate the card against manufacturer’s database. It is generated one time during card manufacturing. See Security section for more details. Card settings defined by personalization. Defines what happens when user calls PURGE_WALLET command: \n0 - Card will switch to Purged state \n1 - Card will switch to Empty state and let create a new wallet again 0 – Card will accept PURGE_WALLET command \n1 – Card will reject PURGE_WALLET command Is user allowed to change PIN1 with SET_PIN command Is user allowed to change PIN2 with SET_PIN command All commands requiring PIN2 will also require additional CVC code printed on the card SET_PIN commands will not change PIN1 to default value (‘000000’). Card will execute only one command during one communication session, thus requiring user to physically take the card away from the host after each action (all commands except for READ_CARD). Whether the card should emulate NDEF. In default configuration, two NDEF records are loaded during personalization: (1) Tangem web site address, (2) name of Android App package in Google Play Store. 0 – Disable dynamic generation of NDEF for iOS. See Dynamic NDEF section for more details. \n1 – Enable dynamic NDEF for iOS. Security delay Pause_Before_PIN2 will not be applied if PIN2 is not default. Whether the card supports unencrypted NFC communication. See NFC communication section for more details. Whether the card supports fast encrypted NFC communication. See NFC communication section for more details. 0 – No replay protection on write issuer data \n1 – Enable replay protection on write issuer data (card will require additional Issuer_Data_Counter incremented on each write) 0 – Wallet elliptic curve and blockchain information stored during PERSONALIZE command and never change \n1 – Wallet elliptic curve and blockchain information can be changed on CREATE_WALLET command 0 – Enable precomputed dynamic NDEF to work around iPhone 7+ NFC bug. \n1 – Disable precomputed dynamic NDEF. See Dynamic NDEF section for more details. 0 – Enforce security delay in SIGN command if the issuer validates the transaction (for signing methods 2, 3, 4 and 5). \n1 – Skip security delay in SIGN command if the issuer validates the transaction (for signing methods 2, 3, 4 and 5). 0 – Require and check PIN2 and CVC in SIGN command if the issuer validates the transaction (for signing method 2, 3, 4 and 5). \n1 – Skip checking PIN2 and CVC in SIGN command if the issuer validates the transaction (for signing method 2, 3, 4 and 5). 1 - Store Terminal_PublicKey public key of linked terminal no each SIGN command, skip security delay if valid signature of transaction is made with Terminal_PrivateKey is provided in SIGN command 0 – Skip checking terminal’s signature when signing POS transaction \n1 – Check terminal’s signature when signing POS transaction 0 – Skip checking acquirer’s signature of terminal certificate when signing POS transaction \n1 – Check acquirer’s signature of terminal certificate when signing POS transaction 0 – Additionally encrypt POS transaction signature with key derived from PIN3 when the transaction amount exceeds PIN3 floor limit \n1 – Require terminal to send PIN3 to card when the POS transaction amount exceeds PIN3_Floor_Limit Detailed information about card contents. Format is defined by the card issuer. Cards complaint with Tangem Wallet application should have TLV format described in Personalization section. Public key that is used by the card issuer to sign Issuer_Data field. See Security section for more details. Explicit text name of the elliptic curve used for all wallet key operations. Total number of signatures allowed for the wallet when the card was personalized. Defines what data should be submitted to SIGN command. Delay in seconds before COS executes commands protected by PIN2. Public key of the blockchain wallet. Value returned only if the wallet has already been created by CREATE_WALLET command. See Security section for more details. Remaining number of SIGN operations before the wallet will stop signing transactions. Value returned only if the wallet has already been created by CREATE_WALLET command. Total number of signed single hashes returned by the card in SIGN command responses since card personalization. Sums up array elements within all SIGN commands. Any non-zero value indicates that the card experiences some hardware problems. User should withdraw the value to other blockchain wallet as soon as possible. Non-zero Health tag will also appear in responses of all other commands. Whether the card requires issuer’s confirmation of activation. \n0 – card will require issuer’s confirmation of activation, \notherwise this field will not be returned (card is activated and operational). A random challenge generated by PERSONALIZE command that should be signed and returned to COS by the issuer to confirm the card has been activated. See ACTIVATE_CARD command for more details. \nThis field will not be returned if the card is activated. Version of POS payment scheme supported by COS ([0x02,0x01] for version 2.30) \nReturned only if SigningMethod ‘6’ enabling POS transactions is supported by card. This value can be initialized by App and will be increased by COS with the execution of each SIGN command. For example, this field can store blockchain “nonce” for a quick one-touch transaction on POS terminals. Returned only if SigningMethod =6. This value can be initialized by App (with PIN2 confirmation) and will be increased by COS with the execution of each SIGN command. For example, this field can store blockchain “nonce” for a quick one-touch transaction on POS terminals. Returned only if SigningMethod =6. Batch_ID Manufacture_Date_Time Issuer_Name Blockchain_Name Manufacturer_Signature ProductMask tokenSymbol tokenContractAddress tokenDecimal Tangem internal manufacturing batch ID, should correspond with the data in Tangem’s card list (see Card attestation and UID and CID sections) Timestamp of manufacturing should correspond with the data in Tangem’s card list (see Card attestation section). Name of the issuer Name of the blockchain (once personalized, the target blockchain is fixed for the whole life cycle) Signature of CID with the MANUFACTURER_PRIVATE_KEY Mask of products enabled on card CID Wallet signed hashes Wallet remaining signatures Signature @string/info_response_card_cid Total number of signed single hashes returned by the card in SIGN command responses since card personalization. Sums up array elements within all SIGN commands. Remaining number of SIGN operations before the wallet will stop signing transactions. Array of resulting signatures that App should embed into a raw transaction according to a transaction format of an appropriate blockchain. Is success Is success Size of Issuer Data Issuer Data Issuer Data Signature Issuer Data Counter A size of issuer extra data written on a card. Data defined by the issuer. Issuer data, signed by the issuer with issuer data private key. An optional counter that protects issuer data against replay attack. User Data Protected User Data User Data Counter Protected User Data Counter Data defined by user\'s App Data defined by user’s App (confirmed by PIN2) Counter initialized by user’s App and increased on every signing of new transaction Counter initialized by user’s App (confirmed by PIN2) and increased on every signing of new transaction