TW201801018A - System and method for secure transactions - Google Patents

Abstract

The present invention provides a digital transaction device and method therefor. The digital transaction device includes: a data assist device (DAD) including a user interface and a DAD transmitter; and a digital transaction card (DTC) including a DTC receiver and a digital transaction processing unit (DTPU) . The device is configured to store at least one digit note. The DAD is configured to allow the user to face the selection of the stored at least one of the digits and transmit the selection to the DTC. The DTC is configured to implement the selected digit note such that the DTC is enabled to operate as the token associated digital transaction file represented by the selected digit.

Description

System and method for secure transactions

The present invention is generally directed to apparatus and methods for implementing secure digital transactions, including both financial and non-financial transactions. The apparatus and method are particularly useful for secure transactions involving credit cards and/or financial cards.

Credit cards, financial cards, stored value cards and gift cards are examples of cards used for financial transactions worldwide. In addition, other types of cards (such as passes, labels, and brochures) (which may be collectively referred to as transaction documents) are used for a variety of financial and non-financial transactions. For example, some jurisdictions require an age card for transactions (such as buying alcohol or entering age-restricted places). Other examples of proof of age or identification documents include a driver's license, which is sometimes used for identification of transactions. In some countries, passports and/or other similar identification documents are issued in the form of a card or a booklet and can be used for transactions in which identification is required, including cross-border travel or establishment of a bank account. Many transaction files have a magnetic strip that can be encoded using information such as a unique identification number, expiration date, or other digital or alphanumeric information. Other types of transaction documents include contactless stored value smart cards, for example, closed loop transport cards (such as Myki in Melbourne, Australia and Octopus cards in Hong Kong). The transaction file may comprise a wafer, a smart chip or a smart card chip (in the present specification, such chips or devices and other similar types of microcircuits will be commonly referred to as digital transaction processing units or DTPUs). The DTPU usually includes a central processing unit (CPU), a read only memory (ROM), a random access memory (RAM), an electrically erasable programmable read only memory (EEPROM), a cryptographic compile coprocessor, and One or more of an input/output (I/O) system. For example, credit cards often use an EMV device (where EMV is one of Europay, MasterCard, and Visa (Europay, MasterCard, and Visa)). The EMV device (or other type of DTPU) contains cryptographic material related to the type of transaction(s) that will use the file. By direct contact or lending to a wafer connection electrode by a scanner (for example, using non-contact, close-range communication according to ISO/IEC 14443, which is referred to as near field communication (through the specification NFC)) The EMV device is read by other methods of obtaining data from the wafer. The enabling of such transactional documents for use in digital transactions by means of a wafer, a magnetic strip, a wafer and magnetic strip or radio frequency identification (RFID) is referred to throughout this specification as a digital transaction file. The digital transaction file is configured to operate with various components in a digital trading system that includes a terminal. For example, credit and debit cards operate in conjunction with EFTPOS (point of sale electronic transfer system) terminals and ATM (automated teller machine) terminals for point-of-sale (POS) transactions. Other digital trading files are configured to work with other types of terminals. Such terminals may be operatively connected to financial institutions or other third party organizations to enable digital transactions to occur by authorizing transactions or performing association processing to enable transactions. In another example, an identification card (such as an age certification card) is implemented using a wafer (or DTPU) containing some or all of the information of the card owner, along with verification information confirming the authenticity of the card. The identification card can be used in a digital transaction whereby it is inserted into a terminal, slid or placed around a terminal to confirm the age of the card holder. Other non-financial transactions can be implemented in a similar manner. A terminal for trading with a digital transaction file is referred to throughout this specification as a digital transaction system device. For "Card-Present" transactions, digital trading system devices can include, for example, POS/EFTPOS terminals, ATMs, and network connections or read-only readings for reading other types of non-financial transaction files. Device. Digital trading devices can also be used for "Card Not-present" transactions (for example, online transactions, mail orders/phone order (MOTO) transactions), and can include Internet-connected PCs, smart Phone and tablet. In addition, the digital transaction system device includes a telephone for communicating with an operator who enters transaction file data using, for example, a network-connected terminal. A digital transaction file has a unique identification (unique ID), usually with a number, an alphanumeric ID, or a unique name. The unique ID can be located on or in the digital transaction file, for example, printed or imprinted on the document. The unique ID is also typically recorded on a database, for example, by the issuer of the digital transaction file, with additional information (such as the name, address, age associated with the user/owner of the digital transaction file). And/or financial information). Where a digital transaction file has a wafer, an EMV device, or other type of DTPU, the unique ID is typically stored on the wafer, EMV device, or DTPU, respectively. Credit cards are typically stamped or printed with a personal/primary account number (PAN) to uniquely identify the account card holder. A standardized PAN has four fields, namely, a system number, a bank/product number, a user account number, and a check digit. This type of PAN typically has 16 digits, but may have a number between 13 and 19 (for example, an American Express PAN has 17 digits). The first digital card issuer type (for example, Visa, MasterCard, or American Express), and the next 5 to 7 digits are often referred to as a bank identification number (BIN) and represent the card network, bank, and Bank products. The last digit is reserved as one of the previous numbers of the PAN. An expiration date is associated with a PAN and typically contains one month and a year code with four numbers but with a limited range. The cardholder's PAN, name or business and the expiration date of the card are usually stamped or printed on the front side of the card. Previously, some types of credit cards had a magnetic stripe that encoded some or all of the card information. Recently, financial transaction cards have carried a card verification value (CVV) or card verification code (CVC) on a magnetic stripe to make it more difficult to copy a card for fraudulent purposes. CVC is usually established by a cryptogram, based on card data (for example, including card PAN and expiration date), and a bank (or a personalization bureau) master key, and The personalized information is printed on the card after it is typed on the card. Therefore, an attempt to use a card for fraudulent purposes requires a sufficient period of time to make a copy of the magnetic strip to copy the card, or to read the card and manually record the card number, expiration date, and other printed on the card. detail. Subsequently, the same principle is applied to a second CVC (sometimes referred to as Card Verification Value 2 (CVV2), which is typically printed on the signature panel on the back of the card). CVV2 is mainly used to help protect e-commerce and MOTO transaction security. This is the second unique password established from the card data and the bank's master key (however, this is a different password than one of the magnetic stripe CVC). CVV2 does not exist on the magnetic strip. Some credit cards also have an associated personal identification number (PIN) code that is primarily used for "physical card" transactions. The PIN must usually be kept secret and must be typed on a secure and authenticated terminal to ensure that no one has access to the PIN. Moreover, in modern credit cards, the PIN can be stored on the wafer (e.g., an EMV device) in an encrypted form within a cryptographic block. There are two main categories of transactions using credit cards, including: "no card" transactions, when using the Internet or MOTO; and "physical card" transactions, such as with POS/EFTPOS and ATM terminals. Physical card transactions involve EMV device readers (including physical contact readers using electrode pins on a card and non-contact reading using, for example, near field communication (NFC)) and/or magnetic strips Reader. These transactions typically use a full 13 to 19 digit PAN and a 4-digit expiration date. Cardless transactions typically require the user to read the PAN and due date numbers to an operator or to a computer. In some cases, the CVC/CVV2 number is also required. Other types of digital transaction files may use various forms of security, such as PINs, passwords, and the like. However, some other types of digital transaction files do not use this external security and rely solely on the authenticity of the file itself, for example, using holograms and other security devices that are difficult to replicate. In addition, some types of non-credit card digital transaction files may use wafers for security, including wafers similar to EMV devices. For example, using a radio frequency (RF) signal to power the card's EMV internal microprocessor and associated transmitter can cause the card (or other digital transaction file) data to be stolen. Typically, card information (such as PAN, expiration date, and cardholder's name) is transmitted to a wireless terminal. The terminal can be a portable or fixed wireless terminal, and once it is close to a card, the RF signal is used to supply energy to the card: first, extracting the card data and copying some card data to a memory storage device, or copying To online storage (such as the cloud); and second, to use one of the card-type terminals to extract money as a contactless payment (for example, a PayWave and /) Or tap a payment, which is referred to by traders as tap-and-pay or tap-and-go. The stolen card information can then be uploaded to a copy of a fake card or used in an online transaction for fraudulent purchases. Yet another method for stealing card data for fraudulent use involves invading a computer database of stored card data. This material is then used for the transaction, and a card owner may only be aware of this when they see a list of transactions detailing the completion of their card or card information. Other ways of stealing card data include phishing scams, which trick cardholders into typing a security code along with other card details via a fraudulent website. Therefore, phishing reduces the effectiveness of security codes as an anti-fraud means. However, merchants that do not use security codes typically experience higher card processing costs for transactions, and fraudulent transactions without security codes are more likely to facilitate cardholder cracking, which increases the cost of the merchant. Yet other ways of damaging the security of the transaction are by skimming and man-in-the-middle attacks. With the advent of e-commerce, more and more transactions are cardless type transactions. However, this type of transaction is subject to increasing attacks from fraudsters, including attacks that have resulted in increased verification that has resulted in a cardholder legal but a transaction rejected. Several solutions have been developed to address this growing fraud, including the use of virtual account numbers, the identification of cardholders separately from transactions, and the use of one of the hardware tokens used to authenticate users. Another proposed solution includes a mechanism, such as a bank that sends a code to a user (usually a smart phone that is sent to the user via SMS), which can then be used to authenticate a cardless transaction. This configuration is often referred to as out-of-band (OOB) messaging, which was unfortunately recently attacked. In any case, many of these solutions require expensive infrastructure changes (merchants prefer to avoid such changes) and may only provide protection for a limited time until the configuration is compromised. As more and more cardless transactions are made, one of the suggested methods for conducting such transactions is the e-wallet (e-wallet), which is also known as a digital wallet. An e-wallet provides a means for paying for a purchase from an enabled online merchant. After registration, a user can store their card, billing, and shipping information on one of the websites hosted by a suitable document (such as a bank) and can access the information to pay for the goods or services. However, an e-wallet on an NFC-enabled device (such as a smart phone) cannot be used in a large number of physical card transactions (for example, POS/EFTPOS or ATM transactions) because such online transaction devices typically do not support Contactless payment, and in the currently available contactless payment configuration, involves different backend programs and merchant agreements. Therefore, the establishment and use of e-wallets has experienced limited commercial success and at the same time they remain available to consumers, only approximately 10% of consumers have chosen to install an e-wallet, however the consumer's take-up rate is now begin descending. Users may prefer to have and carry many of their available credit cards, financial cards, stored value cards, government agency cards, and loyalty cards, as the user preferences actually hold and control the possession of such cards. In addition, the user may need an ID card, driver's license, age verification card or passport. Carrying a large number of personal digital transaction files with you can be very inconvenient. Moreover, a person with so many physical transaction files may become confused about the location of a particular digital transaction file (for example, a particular credit card) in all other digital transaction files. An alternative solution to e-wallet that solves the problem of users carrying a large number of credit or debit cards has been developed, one of which has a keyboard (or a touchpad configured to simplify the keyboard) and a small limited-function graphic use. A user interface (GUI), which is used to select a card among a number of cards stored on the device, and to type in data for various transactions. However, the keyboard has limited functionality due to its limited number of keys in a relatively small space (area of an average credit card) available on the card. Keyboards are also considered to be difficult to use due to their small size, and thus may require a large number of keystrokes to achieve any particular function. In addition, a keyboard on a credit card is not a solution for other types of digital transaction files, such as files for identification or proof of age. Other attempted solutions include products such as Plastc, Coin, Final, and Wocket. However, the Plastec solution has some operational limitations, and the Wocket solution requires a specific Wocket device. None of these solutions have been widely accepted commercially. In addition, it has been found that a card containing a keyboard has an unacceptably high failure rate when given to a customer in view of repetition, perhaps daily use. It is believed that a high failure rate may be due, at least in part, to the complexity of having a keyboard on a card that has limited the space for such a complex electronic device. Another problem associated with attempting to accommodate multiple credit cards, financial cards, or other digital transaction files on a single card is the limitation imposed by the use of proprietary or standardized wafers. These wafers or DTPUs are configured to only securely store information for a digital transaction file. For example, a credit card chip (such as an EMVCo standard chip) securely stores information that typically includes a credit card PAN, expiration date, a security code (such as a CCV2 code), and a PIN. A transaction device (such as a POS/EFTPOS terminal) securely communicates with the DTPU to obtain some or all of the information from the DTPU to authorize and verify a transaction. Many DTPUs are also configured to resist attempts to write to DTPU Secure Record Memory (which may also be referred to as a secure element, or a portion of a secure element), as many are made by those who attempt to fraudulently use the card. These attempts. It will be appreciated that a secure element can include secure memory and an execution environment and is a dynamic environment in which application code and application data can be stored and managed securely. In addition, it will be appreciated that in a secure element, secure execution of an application can occur. A secure element can be located in a highly secure encrypted chip (otherwise referred to as a smart card chip). The security of the DTPU also prevents the legal entry of one or more new digital transaction files (including PAN, token due date, PIN, and other data attributes of such files) into the DTPU's secure record memory (secure element). The DTPU is unable to assume the personality of another file (a term used herein to describe a digital transaction file (or logical digit transaction file) and its attributes). Accordingly, in view of the required infrastructure changes (including modified DTPUs (such as EMVCo devices), modified digital transaction devices (for example, modified POS/EFTPOS terminals), along with credit/debit card payment infrastructure Any other modifications required in other sections), it is difficult to encourage the use of a single physical card with multiple traits (multiple credit cards and/or financial cards represented or representable on a single physical card). In addition to technical issues, program providers (such as Visa and MasterCard) have a variety of additional needs, including one of the plans for the full image and the trademark on the physical card. In this regard, it is desirable to provide a single EMV (or EMV type device) or other type of DTPU on a digital transaction card (DTC) (for example, a credit card size card) that is capable of selectively employing a number of different digits. The nature of the transaction file (or logical digital transaction file). For example, a user may attempt to make a transaction using a MasterCard account, but use a Visa account for a different transaction. Alternatively, a user may attempt to use the DTC as a credit card, but then use it as an age identity card. However, to date, there has not been a sufficiently efficient, efficient, and/or safe means and/or method for adapting a DTPU (such as an EMVCo designated device) to reflect different qualities of the DTPU than originally installed. . Another problem with current digital transaction documents is the ability to obtain information from a credit card or other transaction file. Although devices such as EMV devices have been introduced to try to limit data theft, such configurations have not proven to be completely successful in preventing this type of crime. Increasingly, credit card fraud can incur the cost of a bank, a merchant, a user, or all three parties. In addition, identity theft is a growing concern for users because it can be used to conduct fraudulent financial transactions and other types of crimes as a result of stealing identity. For some digital trading files (such as credit cards), sometimes the use of tokens to improve the security of the transaction. For credit cards, the token is usually the same length as the PAN of the credit card and replaces the number of the PAN in a transaction. The token should not be decrypted operatively to obtain the original PAN by attempting to fraudulently use one of the credit cards, and thus the person cannot imitate the credit card and cannot use the credit card PAN and other personal details of the cardholder for online transactions. Accordingly, if a credit card is used in a high-risk, low-security environment, the token is a means of protecting sensitive data. The security of the token is mainly based on the determination of the infeasibility of the original PAN (or other material) when only the proxy token value is known. The tokenization can be used in place of or in combination with other encryption techniques for transactions with digital transaction files. A token (or digit) can be generated by a third party, such as a credit card issuer, a financial institution, or one of the credit card security providers. The token is also used to protect the security of other non-financial transactions such as those involving driving licenses. The input can be generated as a password using, for example, a credit card PAN (or some other unique ID of a digital transaction file) and/or one of the card's expiration dates. The token for a transaction may be selected from a number of tokens in an episode based on the ID of the merchant or terminal in which the transaction is occurring, the date of the transaction, the time of the transaction, or various other criteria. The de-charging of the original PAN is typically performed during the processing of a transaction and is typically performed by a credit card issuer, financial institution, or security provider that issues the token. Typically, a token is generated during the process of establishing and issuing a credit card to its owner/user. Each card may have one or more associated tokens. In the case where a card has multiple tokens, the tokens can be selectively used for different transactions or different transaction types. The token has several issues, including that it cannot be selected by the user to allow the user to control security and how to use the token. For example, a user may attempt to be able to select a token for certain transactions or transaction types. Another problem is that the same token may need to be used for several different transactions, thus limiting the security provided by the token. This is particularly the case for a digital transaction file such as a credit card. Even if a digital transaction file has several associated tokens, it will still be necessary to reuse or reissue the tokens after several transactions. It is difficult, for example, to issue a new token to a credit card, as it has been developed to issue a new token infrastructure to issue such new tokens when a new credit card is created and issued. One way to prevent fraudulent use of a stolen or stolen credit card or other type of transaction is to simply cancel the file, including the unique identifier that cancels the file (for example, canceling a credit card account), and the issue has one A new file for one of the new due dates. The provider of the file may have a mechanism to invalidate the old file (for example, invalidating the old account) and issue a new number to the existing user. However, sometimes it takes a lot of time to deliver a new file (for example, a credit card is delivered by mail), and the delay is extremely inconvenient for the user. In the case of a credit card, the issuance of a new card causes the user to temporarily suspend the ability to maintain payment by self-confidence with account auto-transfer. In addition, file owners generally prefer immediate or near-immediate ("instant") feedback on their cards for financial transactions or other types of transactions (such as a card or other such document for identification, travel, and other purposes). . The card owner may also prefer instant feedback on account balances and other information related to such cards or other digital transaction files. In addition, owners of cards and other digital transaction files may prefer the ability to block the use of a file on the fly or with minimal delay. This may be useful if the owner is aware of or suspects fraudulent transactions (several) using one or more of its (several) digital transaction files. One object of the present invention is to overcome or at least ameliorate at least one of the above problems in the prior art and/or to provide at least one useful alternative to prior art devices, systems and/or methods.

In one aspect, The present invention provides a digital transaction device that can be operated with a plurality of digits. Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein each digit identifier represents a digitized transaction file for tokenization associated with one of the digit transactions of at least one digital transaction device, The digital trading device includes: a data aid (DAD), It comprises a user interface and a DAD transmitter; And a digital trading card (DTC), It includes a DTC receiver and a digital transaction processing unit (DTPU). Wherein the device is configured to store at least one of the plurality of digits, Wherein the DAD is configured to allow selection by the user to face one of the stored at least one digits and to transmit the selection to the DTC, And wherein the DTC is configured to implement the selected digit note, The DTC is enabled to operate as the token associated digital transaction file represented by the selected digit.  In another aspect, The present invention provides a DTC operation that can be paired with a digital transaction card (DTC) receiver and a digital transaction processing unit (DTPU). And can be combined with a number of digital data manipulation operations (DAD), Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein each digit identifier represents a digitized transaction file for tokenization associated with one of the digit transactions of at least one digital transaction device, The DAD includes a user interface and a DAD transmitter. Wherein the DAD is configured to store at least one of the plurality of digits in cooperation with the DTC, Causing the at least one token to be stored in the DTC, In the DAD or both the DTC and the DAD, And wherein the DAD is configured to allow the user to face the selection of the stored at least one of the digits and transmit the selection to the DTC, The DTC is enabled to operate as the token associated digital transaction file represented by the selected digit.  In yet another aspect, The present invention provides a DAD operation that can be combined with a user interface and a data assist device (DAD) transmitter. And can be combined with a number of digits to operate the digital trading card (DTC), Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein each digit identifier represents a digitized transaction file for tokenization associated with one of the digit transactions of at least one digital transaction device, The DTC includes a DTC receiver and a digital transaction processing unit (DTPU). Wherein the DTC is configured to store at least one of the plurality of digits in cooperation with the DAD, Causing the at least one token to be stored in the DTC, In the DAD or both the DTC and the DAD, Wherein the DTC is configured to accept data from the DAD transmission indicating that the one selected by storing at least one of the digits is selected, And wherein the DTC is configured to implement the selected digit note, The DTC is enabled to operate as the token associated digital transaction file represented by the selected digit.  In a further aspect, The present invention provides a method for transacting a digital transaction device including a data assist device (DAD) having a user interface and a DAD transmitter, The digital transaction device also includes a digital transaction card (DTC) having a DTC receiver and a digital transaction processing unit (DTPU). Wherein the digital trading device can be operated with a plurality of digits. Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein each digit identifier represents a digitized transaction file for tokenization associated with one of the digit transactions of at least one digital transaction device, The method includes implementing a selected number of digits, The DTC is enabled to operate as the token associated digital transaction file represented by the selected digit.  In yet another further aspect, The present invention provides a method of transacting using a digital transaction device having a DAD having a user interface and a data assist device (DAD) transceiver, The digital transaction device also includes a DTC having a digital transaction card (DTC) receiver and a digital transaction processing unit (DTPU). Wherein the digital trading device can be operated with a plurality of digits. Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein each digit identifier represents a digitized transaction file for tokenization associated with one of the digit transactions of at least one digital transaction device, The method includes operating the user interface to select one of at least one of the plurality of digits stored in the device.  In yet another aspect, The present invention provides a method, One of the users receives a digital transaction card (DTC) from an issuer for use in accordance with any one or more of the statements set forth above.  In yet another aspect, The present invention provides a method, One of the issuers issues a digital transaction card (DTC) in accordance with any one or more of the statements above.  In yet another aspect, The present invention provides a method, One of the issuers issues a Digital Transaction Card (DTC) for use in accordance with any one or more of the statements above.  In a further aspect, The present invention provides a method, One of the issuers issues an opcode containing software and/or firmware to a data-assisted device (DAD) and/or to a digital transaction card (DTC) for use in accordance with any one or more of the statements set forth above.  Summary of (Several) Embodiments of the Invention In an embodiment, The present invention provides a digital transaction device that can be operated with a plurality of digits. Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein each digit identifier represents a digitized transaction file for tokenization associated with one of the digit transactions of at least one digital transaction device, The digital trading device includes: a data aid (DAD), It contains a processor, a user interface, a DAD transceiver and DAD memory; And a digital trading card (DTC), It contains a DTC transceiver, a digital transaction processing unit (DTPU) and DTC memory, Wherein the DTC may only be connected to the DAD to exclude all other DADs to achieve secure transmission of data between the DAD and the DTC by respective transceivers. Wherein the device is configured to store at least one of the plurality of digits, Wherein the DAD is configured to allow selection by the user to face one of the stored at least one digits and to transmit the selection to the DTC, Wherein the DTC is configured to implement the selected digit note, Enabling the DTC to operate as the token associated digital transaction file represented by the selected digit, And wherein the DTC is configured to interface with the at least one digital transaction device, The digital transaction is thus implemented when the DTC is operable to encode the associated digital transaction file.  In an embodiment, The invention provides a TC with a DTC transceiver, One DTC operation of a DTPU and DTC memory, And can be combined with a number of digits to operate the DAD, Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein each digit identifier represents a digitized transaction file for tokenization associated with one of the digit transactions of at least one digital transaction device, The DAD includes a processor, a user interface, a DAD transceiver and DAD memory, Only the DAD can be connected to the DTC to exclude all other DADs to achieve secure transmission of data between the DAD and the DTC by respective transceivers. Wherein the DAD memory is configured to store at least one of the plurality of digits in cooperation with the DTC memory, Causing the at least one token to be stored in the DTC memory, In the DAD memory or the DTC memory and the DAD memory, And wherein the DAD is configured to allow the user to face the selection of the stored at least one of the digits and transmit the selection to the DTC, The DTC is enabled to operate as the token associated digital transaction file represented by the selected digit.  In an embodiment, The invention provides a collocation with a processor, a user interface, One DAD transceiver and one DAD operation of DAD memory, And can be combined with a number of digits to operate the DTC, Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein each digit identifier represents a digitized transaction file for tokenization associated with one of the digit transactions of at least one digital transaction device, The DTC includes a DTC transceiver, a DTPU and DTC memory, Wherein the DTC may only be connected to the DAD to exclude all other DADs to achieve secure transmission of data between the DAD and the DTC by respective transceivers. Wherein the DTC memory is configured to store at least one of the plurality of digits in cooperation with the DAD memory, Causing the at least one token to be stored in the DTC memory, In the DAD memory or the DTC memory and the DAD memory, Wherein the DTC is configured to accept data from the DAD transmission indicating that the one selected by storing at least one of the digits is selected, Wherein the DTC is configured to implement the selected digit note, Enabling the DTC to operate as the token associated digital transaction file represented by the selected digit, And wherein the DTC is configured to interface with the at least one digital transaction device for effecting the digital transaction when the DTC is operable to register the associated digital transaction file.  In an embodiment, The present invention provides a use comprising a processor, a user interface, A method of trading a digital transaction device of a DAD transceiver and one of the DAD memories, The digital transaction device also includes a DTC transceiver, One DTC of DTPU and DTC memory, Wherein the DTC can be linked to only one DAD to exclude all other DADs. The digital trading device can be operated with a plurality of digits. Each digit is associated with a digital transaction file. And each digital transaction file is associated with one or more digits, Wherein the digitic note indicates that the digital transaction file is associated with one of the digital transactions of one of the at least one digital trading device, The method includes: Operating the user interface to select one of at least one of the plurality of digits stored in the device; Connecting the DAD to the DTC to enable data representing the selected digit to be transmitted from the DAD to the DTC by a respective transceiver, Wherein the DTC is configured to implement the selected digit note, The DTC is enabled to operate as the token associated digital transaction file represented by the selected digit.  In still other embodiments, The DTC can be coupled to the DAD using a physical connector, such as a data cable. In these embodiments, The data cable can be adapted to be inserted into one of the USB ports on the DAD at one end. The other end is adapted to be clamped or clamped to a portion of the DTC. The DTC can have electrodes or metal plates at or toward one of its edges to allow for clamping or clamping of the other end of the data cable.  In some embodiments, At least one of the plurality of digits is stored on the DAD. In other embodiments, Store at least one of the plurality of digits on the DTC, Wherein the digitizer is selected by the DAD by an indicator or name associated with a digit. But the digit note itself is not stored on the DAD. Passing the selection of the token to the DTC via the data indicating which token has been selected, And the DTC implements the selected token from its memory based on the indication data. In still other embodiments, A portion of each of at least one of the plurality of digits is stored on the DAD. Storing another portion of each of the plurality of digits in the DTC on the DTC. The selection is based on the portion stored on the DAD. Transfer the portion of the selected digit to the DTC, And in this way, the DTC is determined to match the portion of the digit of the selected portion, You can combine the two parts of the digit to form the entire digit. It can then be implemented by the DTC.  In an embodiment, The DAD is enabled to store and/or provide a selection of a logical digit transaction file implemented as one of a digital transaction file on the DTC. Each logical digit transaction file has a unique identification, (for example) a personal/primary account number (PAN) for a credit card. The selection of the file can occur before the selection of one of the tokens associated with the file. In the case that a file has only one token, The choice of file can be considered as the choice of the associated token. This is because there is no need for a further selection procedure. In some embodiments, The selection of a note automatically indicates the logical digit transaction file to be selected. This is because the token is only associated with one file.  As in the case of a digital note, Logical digit transaction files can be stored in DAD memory, In DTC memory, Or a portion of each logical digit transaction file can be stored in both the DAD memory and the DTC memory. The selection of the logical digit transaction file can be by a representative graphic or a similar screen display. In an embodiment, The user selects the desired digital transaction file and then selects the desired digit indicia associated with the selected transaction file. In another embodiment, The user can select a digital transaction file and select a predetermined token based on the context of the content determined by the DAD. For example, If the DAD senses different positions, Then, an token can be automatically selected based on the sensed position.  In the case where the logical digit transaction file and the token are stored in whole or in part on the DTC, The DAD can have a representation of selectable files and tokens. But all or part of the unique identification (unique ID) information of non-documents and tokens. In this embodiment, The selected files and tokens can be passed to the DTC as representative data. It only indicates the selected file and token and does not contain the entire unique ID information of the file and the token. For example, The DAD may only contain a portion of the PAN of a credit card. And a part of the token associated with the credit card. In another example, The DAD may only have any part of the PAN or token number assigned to one of the credit card and token names or nicknames without being stored thereon.  In various embodiments, Some digital trading files will only have one associated token and other digit trading files will have multiple associated tokens. It should be understood that The embodiments discussed in this specification contain two options, One embodiment is not possible unless otherwise stated or unless two options are included.  In various embodiments, A digital transaction file will not need to be stored in the device (DAD memory or DTC memory). This is because the (several) tokens stored in the device will be sufficient to identify (or) (several) associated digital transaction files. For example, In the case where the digital transaction file is a credit card, The card number (PAN) is not stored on the device and is instead, The token associated with the credit card is sufficient to identify a particular credit card. In this example, A credit card PAN may include identifying the card as having a particular type or brand (MasterCard, 4 typical leading numbers for Visa, etc.). One of the specific credit cards can have the same four leading numbers. But with different remaining numbers, Make the token identify the card it is associated with. It should be understood that (For example) not storing a PAN in the device (in DAD memory or DTC memory) should increase the security of the digital transaction file. In these examples, Only the digits are selected by the DAD. The associated digital transaction files are automatically identified and selected.  In various embodiments, A digital transaction file can be a credit card, Debit Card, Bank account, Stored value card, passport, ID card, Age verification card, membership card, Government agency card, Driver's license and / or will usually be implemented as a card, Documents or brochures or various other types and types of digital trading documents electronically implemented. It should be understood that In this specification, The term "logic" refers to a collection of features for each digit transaction file. Features can include data, a unique ID such as a digital transaction file, Ownership information and due date. The identification information can be a unique ID number. A change from one representation of a digital transaction file to a DTC that expresses another digital transaction file may also be referred to as a change in the DTC "trait".  In various embodiments, Digital trading devices can include point-of-sale/point-of-sale electronic transfer systems (POS/EFTPOS) terminals, Automatic teller machine (ATM), Internet connection to a computer or personal computer (PC) and other such electronic devices. Digital trading devices can also include infrastructure. It contains one of the phones and call centers that are enabled for mail order/telephone order (MOTO) type transactions.  In an embodiment, The unique ID of the digital transaction file can be a PAN. Or a unique type of unique ID, Such as a unique alphanumeric ID or a unique name.  In other embodiments, DAD can be a smart phone, Computer tablet, Laptop, PC, A lock ring device or other suitable device for storing digits and operable to allow a user to select a digit and transmit information indicative of the selected digit. The DAD may also contain a custom DAD suitable for this purpose. In other embodiments, The DAD can be a wearable device (such as a smart watch), Or can be enabled to operate with this wearable device.  In an embodiment, The selection via a user interface can include a touch-activated screen selection from, for example, a smart phone. Touch-activated screens can be displayed by Drop-down list or other screen design operations, Or you can use the graphic on the screen. The user interface can also be a simple display having, for example, a button on a lock ring. In the case of a DAD, a PC or a laptop, It can use a screen and a keyboard to provide a user interface. however, The user usually prefers the DAD to be a portable DAD.  In various other embodiments, DTC can contain other features. For example, Used to display the selected digits, A graphical user interface (GUI) of the selected logical digit transaction file and/or information about it. For example, If the logical digit transaction file is a credit card, Then the GUI on the DTC can display PAN, The selected token associated with the selected logical digit transaction file, Card brand logo, The expiration date of the credit card, It can also display one of the credit card brands as a virtual or imitated hologram. In another embodiment, The DTC can display only the selected symbols and does not display the associated PAN. The DTC may also contain a true hologram displayed somewhere on its surface.  In other embodiments, DTC can be included for processing requirements (for example, Safety requirements, Storage requirements) one of the processors. The processor can also control the GUI display.  In various embodiments, The DTC can also include a button or a similar device to initiate a connection to the DAD. In some embodiments, The respective transceivers for DAD and DTC are suitable for BluetoothTM, Low Energy BluetoothTM, Wi-Fi, Near Field Communication (NFC), ANT+ or other types of contactless or wireless communication transceivers. In other embodiments, The transceiver may require contact between the DAD and the DTC to transfer data. Or to establish a link between the two.  In an alternative embodiment, The memory on the DTC can be on an EMV chip (it is Europay, MasterCard and Visa (Europay,  MasterCard,  And Visa) is an abbreviation) or another type of similar or compatible wafer.  In still other embodiments, The DTC is configured to be plugged into a POS/EFTPOS terminal or an ATM.  In still other embodiments, For example, If the DTC contains a non-static memory bank or some form of power transceiver (such as BluetoothTM), The DTC then contains one of the batteries for memory storage. A battery can also be used to power the DTC to handle encryption. And for changing the digital transaction file and/or the digital character represented by the DTC by implementing the change of the logical digit transaction file and/or the associated digit record stored on the DTC.  In an embodiment, DTC can be adapted to express a default "return to zero" trait. The information in place of the logical digit transaction file requiring one of the unique IDs may be a series of predetermined numbers (for example, All zero). In one example, In the case where the logical digit transaction file is a credit card, The unique ID can be a credit card PAN or an associated digit note. And returning the DTC setting to the expression-return-to-zero trait is performed by using all zeros to rewrite or replace the PAN or associated digits.  In an alternative embodiment, The DTC can also be configured to store a logical digit transaction file and/or associated digits for a selection period. The period may be predetermined by the publisher of the DTC and/or the issuer of the digital token (which may be one of the publishers different from the publisher of the DTC). Alternatively, The storage period can be selected by the user. Among other changes, The period can be dynamically selected, And can be selected by the user for each transaction or for a single logical digit transaction file and/or (several) associated digits on the DTC. In other embodiments, The shelf life of the logical digit transaction file and/or the number of associated digits on the DTC may be determined based on the selected logical digit transaction file and/or (several) digits or based on the transaction type or both.  In an embodiment, DTC and digital trading devices can be interfaced to each other by various methods. In some embodiments, Interfacing can be achieved by inserting the DTC into a digital transaction device. In other embodiments, The interface between DTC and trading devices can be through NFC, Wherein the DTC and/or the device each have a transceiver and an antenna for communication. In still other embodiments, The DTC can contain a magnetic strip. The digital transaction device includes a magnetic strip reader. In still other embodiments, The DAD can include a transceiver. It is configured to communicate with digital trading devices, Make it possible to trade directly through the DAD as it is.  In an embodiment, A DTC contains a wearable payment device, It contains incorporation into several pieces of jewelry (such as a ring, Payment device in bracelets and pendants. DTC also includes any implantable payment device, It includes a wafer (DTPU) and transceiver configuration that can also be suitably configured for subcutaneous implantation.  In other embodiments, The DAD can be a smart phone or other suitable device. Such as being configured to operate as a lock ring or keychain for a DAD. In some embodiments, The DAD can be or can include a wearable device, Such as a watch or other jewelry pieces. At this point, Some smart phones are currently operated using wearable wrist (or watch) devices. Imagine that future smart phones can be fully integrated into a wearable device, And DAD can be a device. In the case where the DAD includes a smart phone with a wearable wrist (or watch) device, It should be understood that A wearable component can have its own unique ID. It can be used to secure the connection and data transfer between the DAD and the DTC in cooperation with a unique ID for a smart phone and DTC.  In an embodiment, Each DAD can be linked to multiple DTCs. however, Each DTC can be linked to only one DAD to exclude all other DADs.  In an embodiment, The connection between the DTC and the DAD can be implemented by using one unique ID of the DTC and another unique ID of the DAD. In some embodiments, The link between the DTC and the DAD can occur (at least in part) before the DTC is sent to a user. For example, The link can be implemented by a DTC issuer. Contains a bank, One card (or DTC) distribution facility, One card (or DTC) "personalized" facility or other type of third party institution capable of implementing a "partial" link. In one example, By having the DTC issuer set up the DTC and provide a DAD that is ready to be downloaded by a user to the user (eg, One of the applications of a smart phone) implements a part of the link, Launching the application will cause the smart phone to find and link to the DTC issued to the user. In other embodiments, The link can be implemented by the user. And can occur when the user receives the DTC.  In some embodiments, The link between DTC and DAD is permanent or semi-permanent, It is not possible to unlink or relink without the permission and action required by, for example, one of the aforementioned third parties. For example, To unlink a DTC and the only DAD that is linked to the DTC, A unique code can be typed on the DAD and uploaded to the DTC. This resets the DTC to a preset state. In the default state, DTC can "find" a newly assigned unique ID for one of the different DADs (for example, One of the smart phones has an IMEI number or another suitable for a unique ID). When a user replaces their DAD (such as a smart phone), This unlink/relink can be useful. In still other embodiments, The link can be temporary and can be performed by the user. For example, A user can form a link within a short period of time before an expected transaction occurs. And the link can be unlinked after one of the short durations after the transaction is completed.  In a further embodiment, The DTC can have a magnetic strip. And the DAD can have a magnetic strip reader and/or writer.  In still another embodiment, The DTC is configured to store only one logical digit transaction file and (several) associated digits at any given time. At this point, In order to change the logical digit transaction file stored on the DTC, If there is a logical digit transaction file embodied in DTC at the time, Then a user must rewrite or delete a previously stored logical digit transaction file and (several) its associated token.  In another embodiment, The DTC can be configured to store more than one logical digit transaction file and (several) associated tokens for each file.  In another embodiment, The DTC can be configured to store a primary logical digit transaction file and (several) its associated tokens. And a secondary logical digit transaction file and (several) its associated token. In still another embodiment, The DTC can be configured to store a primary logical digit transaction file and (several) its associated tokens. And one or more secondary logical digit transaction files and (several) associated tokens of each logical digit transaction file. In some embodiments, The main logical digit transaction file and (several) its associated tokens can be permanently stored on the DTC. The one or one or more logical digit transaction files and the (several) associated tokens of the respective logical digit transaction files are temporarily stored on the DTC. In still other embodiments, The one or more secondary logical digit transaction files and the associated identifiers of the respective logical digit transaction files may be permanently stored on the DTC and referenced by one of the codes stored on the DAD.  In which DTC and DAD are dynamically linked (ie, In one embodiment, the user is linked at a selected time, The linking and selection of the desired logical digit transaction files from the DAD can occur in any order.  In an embodiment, In order to have secure communication between DTC and DAD, Security can be implemented by linking DTC and DAD. Or it can be implemented for data transmission between DTC and DAD. In other embodiments, Security can be enforced for both link and data transfer.  In still other embodiments, The DAD can contain an e-wallet. It can be configured to operate in conjunction with one or more of a logical digit transaction file and a number of associated tokens stored on the DAD. In the case where the logical digit transaction file is a financial card or a credit card, This configuration can be used to make up the funds. In addition, The DAD may include allowing a user to instantly observe the use of the DTC (or by other means, The functionality of a transaction such as an online transaction. This may allow the user to monitor all transactions completed by all of the logical digit transaction files in the device (which may include multiple DTCs linked to the DAD or may be linked to the DAD) in a single screen or using a single smart phone application. . In addition, The user can be presented with associated digits for a transaction. If the user detects or perceives that one or more logical digit transaction files have been abused or fraudulently used, Then this can further allow the user to cancel, stop, Suspend or otherwise properly handle one or more logical digit transaction files. The system can also be adapted to allow the user to cancel on a one-by-one basis, stop, Suspending or otherwise properly disposing of one or more logical digit transaction files, So that only the specific token associated with a file is deactivated. You can still use files with other associated tokens. If the user attempts to limit, for example, the cost of using one or more logical digit transaction files or other financial or non-financial transactions, The user can also cancel, stop, Suspend or otherwise properly handle one or more logical digit transaction files. This can also be done on a case-by-case basis.  In another embodiment, When using DTC for a transaction or for selecting a category or type of transaction, The DAD can be enabled to send an alert to the user. For example, The DAD can alert the user that a logical digit transaction file (such as a passport) has been used for identification at an airport. In addition, Alerts can be implemented on a case-by-case basis. In another example, The DAD may alert the user that a credit card has been used to purchase goods or services (such as taking a taxi) that are not included in a list of authorized transaction categories selected by the user, such as purchasing fuel and groceries.  In other embodiments, The DAD and/or DTC can be configured to allow a user to classify transactions. Categories can be predefined and/or defined by the user. Classification can be configured to allow users to monitor and/or limit transactions, Such as credit spending within this category. A category may be associated with only one (logical) digital transaction file, Or may be related to several logical digit transaction files. The token can also be used for the classification of transactions using a digital trading document.  In still another embodiment, The DAD can be configured to allow the user to transfer funds to another user with one DAD. Transfers can be limited to the same or similar (logical) digital transaction file types. And it can be limited in number. In a further embodiment, The DTC can be configured to transfer funds to another DTC (which is owned by the user or owned by another user), Or to another DAD (owned by the user or another user).  In addition, In another embodiment, Third parties (such as financial institutions, Policemen, customs, government, employer, spouse, Parents and other interested parties) may be authorized and able to cancel, stop, Suspend or otherwise properly handle one or more logical digit transaction files in the system or (several) selected tokens associated with the file. For example, If a user has a game addiction, And prefer to have a third party monitoring and prevent against credit cards, Debit Card, Access to bank accounts or other types of financial logic digital transaction files to prevent excessive game play by users, This can be useful.  In other embodiments, The DAD can be configured to store a loyalty point that is associated with a (logical) digital transaction file or a plurality of (logical) digital transaction files, Information on frequent flyer points or other related transactions. DAD can also be enabled to update loyalty points during or after a transaction, or at other times, Frequent flyer points and other related transactions related documents. For example, Loyalty points can be used during a transaction to reduce the cost of purchasing one item using DTC and DAD. If a user visits a particular shopping store or is within a predetermined distance of the store, DAD can also be enabled to increase loyalty points, Frequent flyer points and other related transactions related documents.  In still another embodiment, If the DTC contains, for example, one of the main logical digit transaction files permanently stored on the DTC, The main logical digit transaction file can be an error or forged logical digit transaction file. Data copied from DTC (where only the primary logical digit transaction file is stored on the DTC) will be useless for any digital transaction. Alternatively, Can be incomplete, One of the expired or all zero unique IDs (such as a return-to-zero identity) represents the primary logical digit transaction file. For example, In the case where the main digital transaction file is a credit card, The card's PAN can be incomplete, Expired or all zeros. In this embodiment, The secondary logical digit transaction file stored only on the DTC will be authentic and can be used for a digital transaction when embodied on a DTC as a digital transaction file. In addition, A pair of logical digit transaction files and (several) associated digitic symbols can be stored or embodied as one of the DTC tokenized digit transaction files for only a short period of time (eg, five minutes), In order to reduce the risk of misappropriation of data representing logical digit transaction files and tokens. This configuration reduces the risk that an unauthorized user can emulate an associated digital transaction file and token. Alternatively, The main logical digit transaction file stored on the DTC may include incomplete data. Causes DTC not to be used for digital transactions until a user downloads the secondary data and saves the secondary data to the DTC (and associated token data). So that the main logical digit transaction file is complete and can be used for digital transactions.  In still another embodiment, Each subset of logical digit transaction files or logical digit transaction files stored on the DAD may have a personal identification number (PIN) associated therewith. The PIN can be a static PIN. Or it can be a dynamically generated PIN. In other embodiments, The PIN can be displayed on the user interface of the DAD. The PIN can be accessed by a secure method to display it on the DAD screen. Such as finger sliding or other such security methods such as are typically implemented on smart phones. In another embodiment, The DAD can be configured to allow a user to update a PIN for a particular logical digit transaction file or a number of logical digit transaction files. In an embodiment, The PIN can also be associated with a specific token of a file. Make each token of the file have a different PIN.  In an embodiment, The method includes operating the activated DTC with a digital transaction device to perform a digital transaction.  In some embodiments, A token for a primary logical digit transaction file is provided prior to issuing the DTC to a user. The token can be sent to the DAD over a secure network so that a transaction can be selected for a transaction at the time of the transaction for the associated logical digit transaction file (which has been stored on the DTC at the time of issue). Alternatively, The token associated with the main file can be loaded onto the DTC at the time of release. One of them is selected by DAD at the time of the transaction. The secondary logical digit transaction file can be issued to the user through a secure network component to the DAD after the DTC is issued. And the associated digits of each sub-file can be issued along with the associated sub-file.  In other embodiments, The token can be issued to the DTC for storage on it. Among them, one of the transactions is selected via the DAD at the time of the transaction.  In still another embodiment, The token can be a fixed or expandable pool. Use the token in a circular way, The next token is selected in order. Alternatively, The tokens can be randomly (or pseudo-randomly) selected from the collection area. In a further embodiment, The token may only be used once, Wherein each of the tokens in the pool has been used or expired to replace one of the used or expired tokens. The token zone can also be added before each token is used or expired. For example, When there are ten unused or unexpired tokens in the pool, The user can be warned to need to add a supplement. Will understand, A single-use token can improve the security of an associated digital transaction file and transaction.  In another embodiment, The user can choose when to replace the token in the token collection area. In this embodiment, The user may request a token provider to extend a new pool or one of its existing token pools.  In a further embodiment, A primary user of a given digital transaction file can assign a token to a sub-user of the file. For example, A primary credit card holder may assign (several) tokens from a token zone to an affiliate holder of the credit card. This can be used to control the cost of the affiliate credit card user to the cost limit, One way of quantity or category.  In still other embodiments, In the case where the token is assigned only for certain transaction types, a third party (such as a note issuer, Government agencies or other controllers used by the tokens have the right to allow the issuance of tokens only for the type of transaction selected. In one example, The power to issue the control token may only be allowed for credit card issue tokens for one of the non-gaming payouts.  In some embodiments, The token is only generated by the third party provider who issued the token to one of the users. In other embodiments, The token can also be issued by another third party provider. Alternatively, In an embodiment, The token can be generated by the user (for example) by the DAD at the local end. The token generated by the local end can be securely copied to a third party to match during a transaction to thereby authorize the transaction. You can use one or more of the following to generate a token as a password: The unique ID of the associated file, expiry date, The unique ID of the DAD, time, date, Location and various other random, Pseudo-random or non-random input.  Readers familiar with the relevant art will understand that In an embodiment of the invention, A digital transaction device containing and requiring one of a data aid (DAD) and a digital transaction card (DTC) for a digital transaction provides a multi-factor authentication for digital transactions (including authorization, Identification and authorization and identification), The factor is the user (for example, A person attempting to pay for goods and/or services using a financial digital transaction requires two items (ie, DAD and DTC and also on how to use the two items to achieve a transaction knowledge). therefore, If a person has both a DAD and a DTC in an attempt to conduct a digital transaction, Significantly reduce this person by fraud, The possibility of stealing or defrauding to obtain two items. For example, If the DAD is a smart phone, Then when compared to a single stolen, such as a legitimate credit card currently used for digital transactions, It is impossible for one of the individuals who attempted to commit a fraudulent transaction to be able to steal a legitimate DTC and the owner's smart phone. In addition, If an attempted fraudulent transaction seeks to steal a legitimate DTC, Then the person will be extremely difficult to emulate or deceive the smart phone of the DTC owner. Contains any additional hardware and software necessary to work with DTC for a digital transaction.  In an embodiment, DAD and DTC are operable to transfer data between them, It can further assist in reducing the incidence of fraudulent digital transactions. For example, A DAD can be used to transfer a one-time PIN (OTP) to the DTC before each transaction and each transaction. The OTP is requested by a digital trading system device during a digital transaction and requires the user to enter a PIN to complete the transaction. Under any condition, It is expected that the transfer of data between the DAD and the DTC will assist the user in managing and monitoring their digital transactions.  In some embodiments, DTPU is an EMV device, Or one device that conforms to one or more EMVCo specifications. In other embodiments, DTPU is an EMV device (otherwise conforms to one or more EMVCo specifications), It is constructed to read a secure storage area (temporary memory/temporary area) for the purpose of establishing the characteristics of the card in which the DTPU is installed. Secure storage area or scratch memory can be built into the EMV device, In the constructed EMV device storage area (memory), Or in some other secure memory.  In an embodiment, The CPU of the DTPU and/or one of the CPUs outside the DTPU but resident in the DTC (referred to as an external DTC processor) is only started after the CPU or external CPU securely identifies itself to a linked DAD (such as a smart phone). . In some embodiments, DAD (for example, A connection between a smart phone and DTC uses strong encryption for the transmission of IDs and data. Links may be unique to each collection (smart phone and DTC).  In an embodiment, The connection between DAD and DTC is wireless, And can be formed using the respective transceivers of DAD and DTC. In still other embodiments, The DTC can be connected to the DAD using a physical connector (such as a data cable) (ie, Operable to establish communication). In these embodiments, The data cable can be adapted to be inserted into one of the communication ports (such as a USB port) on the DAD at one end, The other end is adapted to be clamped or clamped to a portion of the DTC. The DTC may have an electrode or metal plate at or toward one of its edges to connect to the cable when the other end of the data cable is clamped or clamped to the DTC. In some embodiments, The respective transceivers for DAD and DTC can be adapted for BluetoothTM, Low Energy BluetoothTM, Wi-Fi, NFC, ANT+ or other types of contactless or wireless communication transceivers. In an embodiment, The DTC can include a button or a similar device to initiate a connection to the DAD.  In various embodiments, The DAD is operable to transfer data to the DTC without direct connection between one of the DAD and the DTC. In these embodiments, The DAD is used, for example, to transfer data over a network to a third party connected to the cloud. One link between the DAD used for data transfer and a third party device may be temporary. And once the data has been completely transferred, The link can be terminated. Third party devices connect (for example) to a network (perhaps via another third party, Such as a payment processor), After the network enables third-party devices to form a link with the network, Forming a link and communicating with a digital trading system device such as a point of sale/point of sale electronic transfer system (POS/EFTPOS) terminal or automated teller machine (ATM), And thus connected to the digital trading system device. A third party device is enabled to transfer data previously received from the DAD to the digital transaction system device. One of the DTC holders (which may be different from the owner of the DAD and/or one of the operators) may bring the DTC to the digital transaction device. And by inserting or placing the DTC near the device, DTC holders can obtain information from digital trading system devices. In this way, Information from the DAD can be transferred to the DTC indirectly and asynchronously. It can also reverse this indirect data transfer between DAD and DTC. Having DTC perhaps use the same infrastructure of digital trading system devices to transfer data to the DAD indirectly and asynchronously, The network contains a payment processor, Third-party devices and the Internet. Will understand, Indirect and asynchronous data transfer may be useful in situations where a first person has a DAD and wishes to send data to a DTC that is geographically remote from the control of one of the first persons. For example, A mother who operates his DAD may prefer to increase the spending limit of one of the DTCs operated by his son who is traveling abroad.  In an embodiment, The external DTC CPU controls the DTPU (for example, Reading and re-reading of an EMV device), And update the memory content of the DTPU.  In an embodiment, The connection between the DTC and the DAD can be implemented by using one unique ID of the DTC and another unique ID of the DAD. In some embodiments, The connection of the DTC to the DAD can occur (at least in part) before the DTC is sent to a user. For example, The link can be implemented by a DTC issuer. Contains a bank, One card issuance facility, A card "personalized" facility or other type of third party that is capable of implementing a "partial" link. In one example, The DTC can be established by the DTC issuer and provide a DAD that is ready to be downloaded by a user to the user (eg, One of the applications of a smart phone) implements a part of the link, The launch of the application results in a smart phone search and links to the DTC issued to the user. In other embodiments, The link can be implemented by the user. And can occur when the user receives the DTC.  In some embodiments, The link between DTC and DAD is permanent or semi-permanent, It is not possible to unlink or relink without the permission and action required by, for example, one of the aforementioned third parties. For example, To unlink a DTC and the only DAD that is linked to the DTC, A unique code can be typed on the DAD and uploaded to the DTC. This resets the DTC to a preset state. In the default state, DTC can "find" one of the different DADs to specify a unique identifier (for example, One of the smart phones has an IMEI number or another suitable for a unique ID). When a user replaces their DAD (such as a smart phone), This unlink/relink can be useful. In still other embodiments, Links can be temporary, And executed by the user. For example, A user can form a link within a short period of time before an expected transaction occurs. And the short duration may be unlinked after the transaction is completed and after one of the transactions.  In which DTC and DAD are dynamically linked (ie, In one embodiment, the user is linked at a selected time, The links and selections of the desired LDTDP from the DAD can occur in any order.  In an embodiment, In order to have secure communication between DTC and DAD, Security can be implemented by linking transaction cards and DADs. Or it can be implemented for the transmission of data between the transaction card and the DAD. In other embodiments, Security can be enforced for both link and data transfer.  In various embodiments, Digital trading devices can include POS/EFTPOS terminals, ATM, Internet connection to a computer or personal computer, And other such electronic devices. Digital trading devices can also include infrastructure. Such as one of the telephones and call centers that are enabled for mail order/telephone order (MOTO) type transactions.  In an embodiment, DTC and digital trading devices can be interfaced to each other by various methods. In some embodiments, Interfacing can be achieved by inserting the DTC into a digital transaction device. In other embodiments, The interface between the transaction card and the transaction device can be realized by Near Field Communication (NFC). The card and/or device each have a transceiver and an antenna for communication. In still other embodiments, The DTC can contain a magnetic strip. The digital transaction device includes a magnetic strip reader. In still other embodiments, The DAD can include a transceiver. It is configured to communicate with digital trading devices, Make it possible to trade directly through the DAD as it is. In still other embodiments, The DTC is configured to be plugged into a POS/EFTPOS terminal or an ATM. And approximately the same size as a credit/debit card.  In a further embodiment, The DTC can have a magnetic strip. And the DAD can have a magnetic strip reader and/or writer.  In still another embodiment, The DAD can be configured to allow the user to transfer funds to another user with one DAD. Transfers may be limited to the same or similar LDTDP and associated (logical) digital transaction file types. And it can be limited in number. In a further embodiment, The DTC can be configured to transfer funds to another DTC (either owned by the user or owned by another user), Or to another DAD (owned by the user or another user).  In addition, In another embodiment, Third parties (such as financial institutions, Policemen, customs, government, employer, spouse, Parents and other interested parties) may be authorized and able to cancel, stop, Suspending or otherwise properly disposing (including temporary suspension rights) one or more LDTDPs containing the logical digit transaction file in the device or the selected number(s) associated with the file. For example, If a user has a game addiction, And prefer to have a third party monitoring and prevent against credit cards, Debit Card, Access to bank accounts or other types of financial logic digital transaction files to prevent excessive game play by users, This can be useful. In an instance of a logical digit transaction file that attempts fraudulent transactions and cancellation/reissue, Provide alerts to users. Used to suggest the availability of a file and a replacement file for a DDC for collection/download to a user and subsequent use to implement a transaction using one of the characteristics of the latest issued (replaced) file, DTC.  In an embodiment, The method includes operating the activated DTC with a digital transaction device to perform a digital transaction.  Although familiar artisans understand the various safety and convenience benefits immediately after reading the instructions, However, using one or more configurations in accordance with embodiments of the present invention, To date, there is no one that is adapted to adapt a DTPU (such as an EMVCo designated device) to reflect one of the different qualities of the DTPU originally installed, High efficiency and / or safety means and / or methods.  Although a modification to one of the basic operational firmware of a certified EMV device results in the device losing its authentication credentials, One embodiment of the invention may still be practiced using a firmware modification to one of the existing certified EMV devices. of course, Once the firmware has been modified, Recertification of devices with modified firmware is required before the device can be used.  In this embodiment, The firmware of an existing EMV device is modified to enable the EMV device to receive and execute a set of commands from an external network transaction device, such as an ATM or EFTPOS device (or a device that initiates a network transaction device) , It enables the secure memory of the EMV device to be modified.

在表1中之第一實施例中，DTC (314)需要使用具有一經修改NFC能力之一資料輔助器件(DAD)(諸如一智慧型電話)以將資料傳遞至經韌體修改之一EMV器件。如先前描述，一經韌體修改之EMV器件具有包含韌體之一外部DTC CPU，韌體可操作以將資料(舉例而言，LDTDP資料)寫入至暫存記憶體，使得當啟動DTPU時，DTPU以導致DTC採用一特定卡特質或以某一其他方式輔助進行一數位交易之一方式將資料複製至DTPU中之安全記錄記憶體(安全元件)。可將關於各特質之資料儲存在與DAD相關聯之記憶體中，其中DAD與DTC之間之通信可能呈將資料下載並複製至安全元件中用於更新DTC之特質之目的之指令之形式。經韌體修改之DTC (314)限於搭配一NFC啓用之DAD使用及使用具有經修改非接觸式通信能力之一EMV器件，以便安全地接收自NFC啓用之DAD接收之資料，但具有能夠針對一單一計劃採用多個特質及低成本及低故障傾向之優點，此係因為DTC (314)不包含一MCU、顯示器或捲動鍵/歸位鍵。 經韌體修改之DTC (316)亦需要使用諸如一智慧型電話之一資料輔助器件(DAD)以將資料傳遞至經韌體修改之一EMV器件，如上文中描述。DTC (314)與DTC (316)之間之差異在於DTC (316)包含一MCU，其可儲存關於多個特質之資料(及/或可能與變更一些其他數位交易參數相關之資料)，而非將資料儲存在DAD記憶體中，且可接受具有無線連接能力(NFC或藍芽)之一DAD與含有亦具有無線連接能力(NFC或藍芽)之MCU之DTC之間之一安全工作階段。使用經韌體修改之DTC (316)之優點包含低成本及低故障傾向，不存在針對一NFC啓用之DAD (其中MCU可接受與單獨藍芽啓用(舉例而言)之一電話之通信)之需求、針對一單一計劃採用多個特質之能力，及可輔助自DAD之安全資料傳送且不需要使用具有經修改非接觸式通信能力之一EMV器件之一MCU之存在。 表1中之DTC (318)亦需要使用諸如一智慧型電話之一資料輔助器件(DAD)以將資料傳遞至可經由一非接觸式介面建立具有無線連接能力(NFC及/或藍芽)之一DAD與DTC之間之一安全工作階段之一經韌體修改之EMV器件。DTC (318)包含一MCU，其可自NFC啓用且藍芽啓用之DAD接受無線通信，且可藉此建立大多數電話與含有MCU之DTC之間之一安全工作階段。使用DTC (318)之優點包含低至中等成本、低至中等故障傾向，且不存在單獨使用一NFC啓用之DAD之需求，但鑑於DTC (318)包含一MCU及顯示器(320)，相較於DTC (314)及DTC (316)，存在與DTC (318)之生產相關聯之一更高成本。 當使用表1中描述之DTC (322)時，熟習相關技術的技術人士將理解，不一定必需使用一DAD (諸如一智慧型電話)，但可使用DAD來變更卡之特質或以某一其他方式輔助進行一數位交易。在任何情況中，DAD必需初始設置卡且將多個特質下載/儲存在MCU中，但繼初始設置之後，卡自身可用來使用捲動鍵/歸位鍵(326)變更一卡之特質之操作參數或以某一其他方式輔助數位交易。一MCU用來在一初始設置期間自DAD接受無線通信(藍芽及NFC兩者)，且進一步經程式化以自可(舉例而言)包含捲動鍵/歸位鍵(326)之一本端介面接受命令，且將按鍵動作轉換成命令。當使用捲動鍵/歸位鍵(326)變更DTC (322)之特質或執行輔助數位交易之某一其他任務時，由本端介面授權傳輸，本端介面授權MCU選擇所儲存資料且將所儲存資料複製至安全元件。 DTC (322)具有在本端自儲存在卡上之許多多個並行特質選擇一個特質而不具有在更新或變更(即，狀態/更新之變更)期間發現卡細節之風險之優點，此係因為卡細節未被傳輸。進一步優點包含減少實現更新或變更(即，狀態/更新之變更)之時間、需要傳送最小量資料以實現特質之一變更，及在不使用一DAD之情況下變更DTC特質之能力。然而，DTC (322)具有一較高生產成本且歸因於其複雜性而可具有一較高故障傾向。 在下文中，例示本發明之裝置及方法之實施例，其等討論一個可能邏輯數位交易文件或數位交易文件類型及用於一金融交易之其關聯符記。所例示之邏輯數位交易文件/數位交易文件及其關聯符記涉及作為一主要數位交易文件(主要信用卡)之一信用卡，以及其他副數位交易文件(副信用卡)及其等關聯符記。然而，應理解，本發明可更廣泛應用至其他類型之數位交易文件及其等關聯符記，諸如儲值卡、會員卡、運輸卡、駕駛執照、護照、年齡證明卡、身份證及其他金融及非金融交易文件。 將一數位交易文件視為意謂卡、文件或其他實體物件或(例如)在一銀行帳戶之情況中，意謂該銀行帳戶在一運算系統中之實體存在。一「邏輯」數位交易文件係數位交易文件之一表示，其包含與特定數位交易文件相關之資料。資料可包含文件之一唯一識別(唯一ID)、到期日或唯一識別該數位交易文件之任何其他此資訊以及關於數位交易之其他資訊。 舉例而言，針對一信用卡，唯一ID係一個人/主帳號(PAN)，且(若干)關聯符記係PAN之一替代號碼，其係與經替代PAD相同之數位號碼，但係已經安全產生之一不同號碼。 圖4展示根據本發明之一實施例之一系統中之例示性元件。一個元件係一數位交易卡(DTC)(412)且另一元件係一資料輔助器件(DAD)(414)。在此實例中，DAD係一智慧型電話，但其可係一電腦平板、某一其他形式之攜帶型計算DAD或為了本發明之目的製造之一特定DAD。 系統用於在兩個例示性數位交易器件之一者處之支付，數位交易器件包含一銷售點/銷售點電子轉帳系統(POS/EFTPOS)終端機(16A)及線上交易終端機(16B)。線上交易終端機可包含一個人電腦(PC)或經啟用用於此等線上(無卡/無DTC)交易之任何其他器件。 DTC (412)具有一主要數位交易文件(419)，其係一主要信用卡。作為一邏輯數位交易文件，主要信用卡經載入至DTC (412)上且可在供應至使用者(420)之前完成此。此外，與主要信用卡相關聯之(若干)符記可在供應至使用者之前經載入至DTC上。使用者可將智慧型電話(414)連結(415)至DTC (412)，此係因為DTC (412)經供應有預載入之主要數位交易文件(主要信用卡)(419)及(若干)關聯符記。在展示一DTC (412)之初始設置之圖2、圖3及圖7中進一步詳述連結程序(415)。 圖4展示建立一DTC (412)且將DTC (412)發行至一使用者(420)之例示性步驟。可存在提供一DTC (412)之若干行動者，包含一個人化公司402、一DTC(卡)積分器(404)、一DTC(卡)製造商(406)及一安全性供應者(408)。安全性供應者(408)提供與一給定數位交易文件相關聯之(若干)符記。發行一DTC (412)之其他行動者可包含一發行金融機構(440)，諸如一銀行或其他類似方。發行金融機構(440)可充當一安全性請求者(符記請求者)(442)，其經供應有(例如)一種子(444)。發行金融機構(440)之客戶服務(446)可與使用者(420)互動，使用者(420)請求DTC (412)且將所需資訊供應至金融機構，諸如名稱、出生日期、其DAD之細節(在一智慧型電話之實例中，可為IMEI號碼或智慧型電話之另一適合唯一ID)。 金融機構(440)可接著產生一安全性密碼編譯金鑰，其經提供至個人化公司(402)用於建立DTC (412)。 在此實施例中，DTC (412)係一信用卡式交易卡。DTC (412)具有一EMV晶片(其中EMV係Europay、萬事達卡及Visa (Europay, MasterCard, and Visa)之一縮寫)(數位交易處理單元(DTPU))(422)、一按鈕(423)，其可用於(例如)藉由使用用於完成連結之Bluetooth™而使DTC與智慧型電話(414)連結。DTC (412)亦具有一DTC顯示器(424)，其可係用於展示一所選擇邏輯數位交易文件之一唯一ID之一簡化圖形使用者介面，該唯一ID經載入至DTC上，且實施於DTC (412)上，使得其充當該數位交易文件。在DTC實施為一符記化數位交易文件之情況中，DTC顯示器(424)展示符記號碼。在圖4中展示之實例中，數位交易文件係一主要信用卡或複數個副信用卡之一者。 DTC (412)亦具有顯示正在操作為其之特定數位交易文件之一到期日之構件。DTC亦具有用於擁有DTC之人(420)之名稱之一顯示器(428)之一空間。在一些實施例中，各及每一邏輯數位交易文件之名稱將相同，即，使用者(420)之名稱。然而，在其他實施例中，(例如)若一人使用DTC (412)用於個人使用及公司使用兩者，則與一特定邏輯數位交易文件相關聯之名稱可係不同的。在此點上，DTC名稱空間(428)可僅係一印刷名稱，或可係經啟用用於顯示不同名稱之一簡化圖形使用者介面(GUI)。可取決於針對一交易選擇之符記而顯示不同名稱。 為一智慧型電話之DAD (414)包含一智慧型電話介面(430)，在圖4中，其為一螢幕(430)及鍵盤。替代地，智慧型電話可包含一觸控螢幕，使得不需要鍵盤。 圖4亦描繪一DTC (412)及一智慧型電話(414)之初始設置、建立及發行一DTC涉及之行動者及在交易中使用DTC。圖4亦展示DTC (412)至一智慧型電話(414)之連結(415)。亦圖解說明發行DTC之金融機構(440)(包含行動者)及DTC發行(在一些實施例中，包含主要信用卡之發行)之步驟之細節。 為一智慧型電話之DAD (414)具有一IMEI號碼或另一適合唯一ID以便唯一地識別智慧型電話。智慧型電話可使用Android及/或iOS作業系統或任何其他適合作業系統。在實施例中，智慧型電話(414)包含無線連接技術，(例如)近場通信(NFC)及/或Bluetooth™或Bluetooth™ LE。 DTC (412)具有一DTC晶片(422)，其可係認證智慧卡晶片(DTPU)(422)以便可通常操作以僅與一外部讀取/寫入器件傳遞資料。認證智慧卡晶片之實例可遵守以下認證標準ISO/IEC 7816或ISO/IEC 14443之一者或兩者。此外，認證智慧卡晶片可遵守其他標準，諸如通用準則EAL4+/EAL5+ (ISO/IEC 15408資訊技術-安全性技術-針對IT安全性部分1至3之評估準則)、FIPS 140-2 3及4級、ISO/IEC 7816識別卡、積體電路卡部分1至5、ISO/IEC 14443識別卡-非接觸式積體電路卡-感應卡部分1至4及EMVCo。 圖5展示在具有一DAD (514)(其係具有一智慧型電話介面(30)之一智慧型電話)之一系統中操作之一DTC (512)之一例示性設置。在此實例中，設置開始於使用者(520)自智慧型電話(514)提取IMEI號碼或另一適合唯一ID (503)。將為智慧型電話(514)之一唯一ID之IMEI號碼提供(505)至相關金融機構(502)(其亦稱為發行金融機構)。金融機構(502)記錄且處理經提交IMEI號碼及使用者細節，且在記錄此等細節之後，金融機構查找區段(534)查找記錄且使用種子/秘密金鑰(538)資訊填入一應用程式且經由一帶外(OOB)通知(544)將一應用程式連結(540)發送至智慧型電話(514)。經由(例如)自雲端(556)之一網際網路下載(554)而使智慧型電話(514)之一軟體應用程式(應用軟體(app))中之應用程式連結(540)可用，應用軟體可由使用者(520)在智慧型電話(514)上在其上點選而操作。當將種子/秘密金鑰(538)下載至智慧型電話(514)時，設置之此部分完成且使用者(520)可繼續連結智慧型電話與DTC (512)。 圖5亦展示具有展示一唯一ID (526)之DTC顯示器(524)之DTC (512)，在此情況中，唯一ID (526)係主要信用卡之符記化號碼(有時稱為一動態符記號碼)，即，主要邏輯數位交易文件導致DTC (512)表現為符記化數位交易文件(即，符記化主要信用卡)。 圖5亦展示發行金融機構(502)充當安全性請求者(符記請求者)(504)且獲得金鑰(510)之角色，將金鑰(510)傳遞至客戶服務(508)且接著傳遞至查找(534)，使用一計數器(536)開發種子/秘密金鑰(538)且接著經由應用軟體連結(540)將其傳遞至智慧型電話(514)。 圖6展示設置如由一個人化公司(602)提供之一DTC (612)之例示性步驟，其涉及一DTC積分器(604)及一非接觸式DTC製造商(606)兩者。個人化公司(602)亦搭配一安全性供應者(608)(其係產生各信用卡之一或多個符記之一符記供應者)工作，安全性供應者(608)繼而搭配發行金融機構(610)(其係一安全性請求者(符記請求者)(611))工作。金融機構(610)建立一種子(616)，經由客戶服務(618)將種子(616)供應為載入有智慧型電話之IMEI或智慧型電話之另一適合唯一ID及安全性細節之一應用程式(640)。 以此方式，圖6證實一個例示性方法，其中DTC (612)可經供應經預載入有一主要邏輯數位交易文件(在此實例中為一主要信用卡)及其關聯符記。DTC (612)及智慧型電話(614)各具有主要邏輯數位交易文件及關聯符記之細節，使得使用者(620)可操作智慧型電話(614)以選擇DTC (612)上之主要邏輯數位交易文件，且接著選擇主要邏輯數位交易文件之關聯數位符記之一者，且以便導致DTC (612)充當符記化主要數位交易文件。 在此點上，應意識到，在一些實施例中，邏輯數位交易文件可部分儲存在DTC (612)上，且該等邏輯數位交易文件之其他部分可儲存在智慧型電話(614)上，使得智慧型電話可經操作以選擇一特定邏輯數位交易文件且選擇與用於一交易所要之邏輯數位交易文件相關聯之一符記，且使得智慧型電話可導致DTC (612)充當與所選擇邏輯數位交易文件及所選擇關聯符記相關聯之符記化數位交易文件。 圖7展示一例示性實施例，其中已具有載入至其上之一主要邏輯數位交易文件(主要信用卡)及關聯符記之一DTC (712)可具有經由智慧型電話(714)載入至其上之額外副邏輯數位交易文件(18)及其等(若干)關聯符記。在此實例中，第二邏輯數位交易文件(18)係其他信用卡。 在此實例中，使用者(720)經由主要卡發行金融機構(702)之客戶服務區段(708)將額外卡(18)細節供應或鍵入至主要卡發行金融機構(702)。在一項實施例中，主要卡(或DTC)發行金融機構可藉由進行具有一參考號碼之一轉帳或具有兩個唯一貨幣量之一轉帳及一貸款(其可在增加至主要卡之額外信用卡(18)之各者上進行)而進行驗證。當使用者(720)具有由特定副卡(或DTC)發行金融機構(716)發行之一清單(710)時，清單將展示具有一參考號碼之一轉帳或具有兩個唯一量之一轉帳及一貸款。使用者(720)閱讀清單(710)且鍵入或提交來自清單之行細節以驗證使用者(720)係增加至主要卡(例如，如在圖4中表示)之各額外副信用卡之實際擁有者。當主要卡(或DTC)發行金融機構(702)對於使用者(720)係額外信用卡之正確擁有者滿意時，主要卡發行金融機構可請求使用者將額外卡加入該金融機構(702)且讀取卡以提取用於使用(例如)一POS/EFTPOS終端機之密碼之公開加密密鑰。替代地，主要金融機構(702)可將一請求發送至金融機構(716)，金融機構(716)已針對用於一POS/EFTPOS終端機處之一密碼中之公開加密密鑰發行額外卡。當主要卡發行金融機構(702)對於使用者(720)係額外卡(18)之正確擁有者滿意時，機構(702)可經由一OOB訊息將碼發送至使用者註冊智慧型電話(714)。接著，使用者(720)具有碼，當選擇碼時，其可用於將選自智慧型電話(714)之副邏輯數位交易文件(副信用卡)之一者載入DTC (712)。 在實施例中，可使用圖7中展示之方法論與(若干)副卡同時發行與(若干)副卡18相關聯之數位符記。替代地，可在(若干)副卡之發行之後但仍使用類似於圖7中展示之一方法論發行符記，其中使用上文論述之轉帳/貸款方法驗證若干符記或各符記。 圖8展示用於藉由針對額外信用卡(818)之各者增加額外支付符記而增加額外安全性之程序步驟，經由客戶服務區段(808)經由OOB (810)而將額外安全性符記提供至智慧型電話(814)。針對一交易，選擇一個符記以作為一符記化數位交易文件實施於DTC (812)上，其中DTC (812)在顯示器中顯示符記號碼。符記供應者(806)亦可係用於DTC (812)之晶片(822)之一供應者。符記供應者產生用作信用卡之PAN之一替代之符記。使用者可僅增加符記一次，或(例如)若符記經設定在一特定日期之後到期或若符記係一次性使用符記，則在一定期基礎上增加符記。若符記經指定用於特定交易類型且使用者希望進行該等種類之交易，則使用者亦可尋找進一步符記。 圖9展示一DTC (912)可使用不同類型之智慧型電話進行操作。然而，DTC僅可與一個DAD (智慧型電話)連結而排除全部其他DAD。 如圖9中展示，一使用者可決定購買一新智慧型電話(952)，在該情況中，DTC (912)將需要被更新以便能夠與新智慧型電話連結。在此實例中，一舊智慧型電話(950)與DTC (912)連結，但使用者希望將新智慧型電話(952)與DTC (912)連結。連結係(例如)一雙向加密傳輸。DTC (912)可在製造時經載入匹配種子及動態金鑰以便能夠僅與一個智慧型電話(950)連結。為了使DTC (912)與新智慧型電話(952)連結，自(例如)一動態金鑰建構一動態碼或可使一種子可供經驗證擁有者使用。使用動態金鑰或種子以使舊智慧型電話(950)與DTC (912)斷開或解除連結。DTC可接著經載入有一匹配種子及/或動態金鑰以便與新智慧型電話(952)連結。種子及動態金鑰係基於智慧型電話之IMEI或智慧型電話之另一適合唯一ID。應理解，使DTC連結至智慧型電話之碼必須對於各DTC係唯一的，且對於各DTC之序號可係唯一的。在此點上，一智慧型電話與一DTC之間之連結可僅基於匹配IMEI或智慧型電話之另一適合唯一ID及DTC序號在智慧型電話與DTC之間發生。 圖10展示在用於一智慧型電話(1014)與一DTC (1012)之初始配對(連結)之一實施例程序中之一智慧型電話(1014)上之螢幕。 在第一螢幕(1002)中，智慧型電話顯示一標題「設置」 (1004)，且在標題(1004)下係一「設置」按鈕(1006)，且在按鈕(1006)下係展示「網際網路連接」之一指示符。 下一螢幕(1032)展示一標題「狀態」(1034)，其包含一「申請碼」按鈕(1036)及一「金鑰」鍵入欄位(1038)，以及一「與卡配對」(替代地，「與DTC配對」)按鈕(1040)。在最後螢幕(1042)中，顯示一「恭喜」訊息(1044)，其對使用者(1020)指示智慧型電話(1014)經連結至DTC (1012)。 在一實施例中，亦藉由連結按鈕(1023)而使智慧型電話(1014)與DTC (1012)連結，連結按鈕(1023)經按壓且保持(1046)使得其可連結至智慧型電話(1014)。 圖11展示具有具備若干指示符之一前側(1112f)及一背側(1112r)之一DTC (1112)之一實施例，該等指示符展示(例如)與儲存在DTC (1112)上之主要邏輯數位交易文件相關之個人化細節。在DTC之前側(1112f)上印刷有主要卡(1119)之標誌(1104)，以及附接至DTC (1112)之一全像(1106)。DTC (1112)亦可顯示主要卡到期日(1108)。在DTC (1112)之背側上，可存在用於主要卡擁有者之簽名(1110)之一面板。亦可印刷有卡驗證值(CVV)(1114)，以及其他識別細節。在一些實施例中，在細節經印刷或以其他方式永久標記於DTC (1112)上之情況中，細節將僅關於儲存在DTC (1112)上之主要邏輯數位交易文件，諸如一使用者之名稱、CVV、到期日。在一DTC (1112)在可變更GUI中顯示細節之情況中，該等細節可關於目前表達為DTC之數位交易文件之邏輯數位交易文件(包含主要邏輯數位交易文件及副邏輯數位交易文件)。 在一例示性交易中，商家檢查一有效DTC可包含以下： 1. DTC (1112)包含一全色DTC發行者商標， 2. DTC號碼(或替代地，主要卡號碼)係12至19個數字之一有效長度， 3. 顯示於DTC顯示器上之DTC號碼之前四個數字與直接印刷在下方之數字相同， 4. 到期日在未來且按正確格式「MM/YY」， 5. 全像或全像(Holomag)帶可位於DTC之前側或背側。若位於DTC之前側，則其可位於商標上方，若位於DTC之背側，則其可位於簽名面板之上方或下方， 6. 一磁條存在於DTC上且位於簽名面板之上方，且應看上去平滑且筆直而無篡改之標記。在一些DTC上，可代替磁條而使用全像帶，及 7. 印刷於簽名面板上之四個數字必須匹配帳號之後四個數字，接著為三數位卡驗證碼(CVC)號碼。 圖12A展示使用智慧型電話(1214)選擇一不同邏輯數位交易文件(不同信用卡)用於針對使用所選擇邏輯數位交易文件之一交易更新DTC (1212)之一例示性實施例。第一智慧型電話螢幕(1202)具有一「登入」標題，接著為選擇安全性類型之三個按鈕，包含一「PIN (個人識別號碼)」按鈕(1204)、一「滑動」按鈕1206及一「生物特徵」按鈕(1208)。使用者(1220)選擇選項(1204)、(1206)或(1208)之一者，接著智慧型電話(1214)顯示下一螢幕(1210)，其展示一「支付選項」標題，在該標題下方展示一「當前」標題(1211)，其指示當前在DTC (1212)上操作之文件。在此實例中，智慧型電話螢幕(1210)展示當前操作文件係一「VISA」卡(1213)。 使用者可操作一螢幕(1210)以選擇可在DTC (1212)上操作且在「變更為」標題(1215)下方列出之四個其他文件(信用卡)之一者。用於金融交易之額外文件包含「VISA」按鈕(1217)、「萬事達」按鈕(1218)、「銀行轉帳」按鈕(1219)及「美國運通」按鈕(1221)。使用者(1220)選擇「變更為」標題下方之文件之一者，此接著導致智慧型電話(1214)顯示下一螢幕(1252)，其顯示訊息「支付方法」 (1234)，在該訊息下方顯示兩個按鈕，「是」按鈕(1236)及「否」按鈕(1238)。使用者(1220)可按壓該等按鈕之一者以判定萬事達卡是否將係較佳支付方法。 下一智慧型電話螢幕(1242)展示針對使用者之安全性選項，其具有「變更符記」標題(1244)及一「是」按鈕(1246)以及「否」按鈕(1248)。在螢幕(1242)處，使用者可選擇(例如)是否變更針對目前交易文件操作之目前符記。若選擇「是」 (1246)，則使用者可接著經呈現一關聯符記清單以便能夠選擇該等所列出符記之一者。如先前提及，在各項實施例中，符記可在清單中僅呈現為符記號碼。在其他實施例中，符記可以符號呈現為(例如)圖式。 下一智慧型電話螢幕(1242)展示狀態且包含「狀態」標題(1254)，在其下方係展示「生物特徵設定/不設定」(1256)之一指示符，螢幕(1242)亦展示指令「觸控卡」(替代地，「觸控DTC」)(1256)，以及展示智慧型電話(1214)及DTC已連結之一指示符「卡連結」(替代地，「DTC連結」)(1258)。 智慧型電話(1214)接著將資料傳輸至DTC (1212)以便使用新選擇文件及符記細節更新DTC，且使得DTC GUI顯示器(1224)展示新選擇文件(信用卡)號碼(1260)作為符記化號碼。在其中DTC (1212)僅實施一個文件(信用卡)之一實施例中，作為一額外安全性預防，DTC (1212)亦可印刷單一信用卡之4個前導數字(1267)，使得與該信用卡相關聯之經顯示之全部符記號碼(1260)必須具有相同的4個前導數字。 智慧型電話接著顯示具有進一步安全性之螢幕(1262)，其包含當由使用者(1220)按壓時在一面板(1268)中展示一次性PIN (OTP)之一「建立OTP」按鈕(1264)。 使用者可接著將DTC (1212)呈現至一商家(1270)，接著經由與有效信用卡(數位交易文件)發行金融機構(1274)之通信而處理(1272) DTC。 在一些例項中，一交易可超出標準限制且智慧型電話(1214)可在一螢幕(1280)上顯示一訊息「超出限制交易」(1282)。使用者(1220)可接著藉由按壓在邀請使用者授權交易之一訊息(1286)下方之「是」按鈕(1284)而授權超出限制交易。替代地，使用者(1220)可按壓「否」按鈕(1288)，使得交易不被授權且不繼續。 圖12B (其描繪一無卡交易)係與圖12A類似之一視圖，其中智慧型電話亦顯示具有用於顯示與所選擇邏輯數位交易文件之所選擇符記相關聯之一唯一識別符(在此實例中，所選擇信用卡(數位交易文件)之符記化號碼(1260))之一面板(1263)之螢幕(1262)。智慧型電話螢幕(1261)亦在一標題「到期」(1267)下方顯示到期日(1267)。智慧型電話螢幕(1262)亦可在CVV顯示面板中顯示所選擇文件之CVV (1269)。 圖13展示使用本發明之一實施例中之系統之一例示性店內或實體卡(實體DTC)交易。在此實例中，使用者(1320)決定使用主要卡以進行一購買，且針對該卡選擇一符記。在DTC GUI顯示器(1324)上顯示符記化主要卡號碼。使用者(1320)將DTC (1312)呈現至商家POS/EFTPOS終端機(1316)(其係具有一EMV讀取器之數位交易器件)。EMV讀取器獲得細節，包含密碼、符記、符記到期日及符記請求者ID。POS/EFTPOS終端機經由一商家收單機構(1318)可能藉由使用卡軌(1332)而獲取主要信用卡之細節。接著經由一支付處理器且經由一安全性供應者(符記供應者)(1334)使用安全性程序傳遞安全符記化主要卡細節以解除符記化號碼以便判定PAN (或若非一信用卡文件，則一文件之其他類型之唯一ID)，接著將PAN提供至主要卡發行金融機構(1336)以處理支付(或若非一信用卡文件，則其他類型之交易)。 在一個例示性實施例中，在自DTC (1312)讀取主要卡細節之後，POS/EFTPOS終端機(1316)建立自細節(包含(例如)生物特徵(1338)及其他安全性(符記)保證資料(1340))產生之一密碼，其中將一號碼給定至來自自DTC (1312)中之晶片(DTPU)獲取之細節之授權之類型及位準。密碼亦可包含商家POS/EFTPOS終端機識別號碼、購買價格及用於轉送至商家收單機構(1318)之其他相關細節。 圖13亦展示使用DTC (1312)上之主要信用卡使用一智慧型電話或經由網際網路(1342)之一選用線上或無卡交易。使用者自DTC (1312)或智慧型電話螢幕(1330)讀取信用卡號碼(1321)、到期日及CVV號碼，且線上鍵入該等細節或經由智慧型電話將該等細節讀出至一商家。商家擷取資訊且可使用經提供之正確授權碼發生交易。 圖13亦展示交易DTC (1312)可與一所選擇其他邏輯數位交易文件及關聯所選擇符記一起使用，其等之細節顯示於DTC GUI (1324)上，亦即其他邏輯數位交易文件符記化唯一ID (1344)。 以此方式，系統可用於實體卡(實體DTC)交易及無卡(無DTC)交易。 應理解，在本說明書中，術語「邏輯」係指針對各數位交易文件之一特性集合。特性可包含資料，諸如數位交易文件之唯一ID、擁有權資訊、到期日及類似者。識別資訊可係一唯一ID號碼。自表達一個數位交易文件至表達另一數位交易文件之DTC之一變更亦可稱為DTC 「特質」之一變更。 貫穿本說明書及隨後之發明申請專利範圍，除非內容脈絡另有要求，否則字組「包括(comprise)」及諸如「包括(comprises)」及「包括(comprising)」之變動將理解為意謂包含一陳述整數或步驟，或整數或步驟群組，而非排除任何其他整數或步驟或整數或步驟群組。 熟習相關技術領域者將瞭解，可如實施例中詳述般對本發明作出許多變動及/或修改而不脫離如廣泛描述之本發明之精神或範疇。因此，本實施例應被視為在全部態樣中係闡釋性而非限制性的。1 illustrates a major component of a device (100), including a digital transaction card (DTC) (108), in the form of a smart phone (106), a data aid (DAD), in accordance with an embodiment of the present invention. And a digital transaction device (102), in this example, the digital transaction device (102) is a point of sale/point of sale electronic transfer system (POS/EFTPOS) terminal (102). Such terminals (102) may be referred to herein as merchant terminals and may be contactless between a terminal transceiver (not shown) and a DTC transceiver (114) in accordance with one of ISO/IEC 14443 The short-range communication capability is coupled to the DTC (108). The terminal (102) can also interface with a smart phone transceiver (116) and communicate with it in accordance with the ISO/IEC 14443 communication protocol. The terminal (102) can also be coupled to the DTC (108) or to one of the magnetic strips on the DTC (108) by a physical contact. In the illustrated embodiment, the terminal (102) needs to insert the DTC (108) into the terminal (102) for engagement by physical contacts. In the embodiment of Figure 1, the smart phone (106) is wirelessly coupled to the DTC (108) by NFC, and the DTC (108) is by ISO/IEC 14443 (which is a subset of the NFC communication format) The communication is wirelessly coupled to the terminal (102). It will be appreciated that many types of smart devices or computing devices, such as smart phones (106), cannot interact with many types of POS/EFTPOS terminals (102) and automatic teller machines (ATMs). In order to complete a transaction with one of these terminals, it is necessary to use a financial card or credit card. However, the financial card or credit card will each have a single "trait" or an entity embodiment that includes only a single digit transaction file. For example, at present, a physical transaction card may have only one MasterCard or one Visa card trait, and cannot selectively and continuously adopt the characteristics of both a MasterCard and a Visa card at different times. In the embodiment shown in FIG. 1, the DTPU (104) on the DTC (108) is an EMV device (where EMV is an abbreviation of Europay, MasterCard, and Visa (Europay, Master Card, and Visa)), or a One or more devices of the EMVCo specification that have been adapted to allow expression of several different qualities. Such current DTPU or EMV devices may include read only memory (ROM), random access memory (RAM), and/or electrically erasable programmable read only memory (EEPROM). The DTPU (104) may contain other kinds of memory, and the DTPU (104) may include a central processing unit (CPU) (104) for controlling the operation of the DTPU (104). The DTPU CPU can work in conjunction with one of the tasks of encrypting and decrypting data, the cryptographic coprocessor, thus releasing the DTPU CPU to perform other processing tasks. Communication between the DTPU (104) and the electrodes (112) on the surface of the DTC (108) is accomplished by one of the DTPU (104) system input/output (system I/O) (108). Similar to a standard EMV device, the DTPU (104) of the embodiment shown in Figure 1 is located in a plastic credit card body using electrodes (112) for external communication. However, the DTPU (104) may also use a wireless transceiver to communicate externally with the terminal (102). In one embodiment in which the operational firmware of an EMV device is modified, the DTPU (104) EEPROM can be divided into two memory regions. In some embodiments, the partitioning may be by partitioning (or virtual partitioning), by using a suitable file structure, or by using a suitable directory structure. In this exemplary embodiment, a portion of the EEPROM is used as the scratch memory (scratch area). During operation, the scratch memory has at least one logical digit transaction file packet (LDTDP) written from the LDTDP storage memory into its temporary memory. Use another part of the EEPROM as a secure recording memory (secure element). During operation, at least one LDTDP is taken from the scratch memory and written to the secure element, which is accessed by the DTPU CPU when the DTPU is booted to read the secure element. When the DTPU CPU accesses the LDTDP, the DTPU (104) can take advantage of the traits represented by LDTDP, making the DTC (108) available for transactions with this trait. In other embodiments, instead of using a single EEPROM divided into two memory regions (temporary memory region and secure recording memory region), there may be one of each of a temporary memory and a secure recording memory. Two separate memory chips. These memory devices (or wafers) can be configured in the DTPU (104) to have no direct link for added security, especially for secure recording memory, which should only be specified by some of the DTPUs (104). Components (such as DTPU CPUs) are accessed directly. In DTC (108), in accordance with an embodiment of the present invention, it is possible to locate an external DTC CPU that is different from the DTPU CPU and that is additional. The DTPU (104) can be controlled by controlling the DTPU CPU. The external DTC CPU and its associated firmware allow data (including LDTDP) to be passed to the DTPU (104) through the system I/O. The external DTC CPU and firmware can be operated to instruct the DTPU CPU to copy data (for example, one or more LDTDPs) into the scratch memory. The DTC CPU can also be operated to instruct the DTPU CPU to transfer the data in the scratch memory to the secure record memory. The data containing the LDTDP can be stored in the smart phone (106) or in the LDTDP storage memory on the DTC (108) in one of the memories separated from the memory in the DTPU (104). The configuration depicted in Figure 1 allows the LDTDP to be stored in the LDTDP storage memory and copied from the LDTDP storage memory to the scratch memory. Copying from LDTDP storage memory to scratch memory can be controlled by an external DTC CPU, which in turn controls the operation of the DTPU CPU. The operation of the external DTC CPU can be controlled by the DAD (106), and the DAD (106) is operated by a user via the user DAD user interface 110. In another step of an example operation, data containing one or more LDTDPs is loaded from the scratch memory into the secure record memory of the DTPU (104). In an embodiment, a connection between a smart phone (a DAD) (106) and a DTC (108) is established, using strong encryption for identification and transmission of data therebetween. The link may be unique to one of the pair of smart phones (106) and one DTC (108). The external DTC processor (or DTC CPU) typically only starts after it has been securely identified to the connected smart phone. The DTC processor on DTC (108) controls the read and reread of DTPU (104) and the update of DTPU (104) to express new traits. In some embodiments, the external DTC CPU can be started by pressing one of the DTC (108) on/off switches. In other embodiments, the DTC CPU is powered on (and powered) by the DAD (106). In an embodiment, after securely connecting the smart phone (106) and the DTC (108), the smart phone (106) will properly format the data by the external DTC CPU after meeting certain criteria and passing various compliance checks. (For example, an LDTDP) is uploaded to a designated secure storage area (for example, scratch memory), and then an instruction is transmitted to the DTPU processor for: • checking the specified storage area (temporary memory) Whether it contains data in a specified format (-LDTDP); • If the data meets a specified standard and passes various checks, the DTPU processor copies or moves the data to a designated area (secure record memory) in the DTPU; • The processor then sends an instruction to the DTPU (104) to read the data in the designated area (secure record memory) and take action based on the information contained in the area, which can be stated as expressing in the secure record memory. DTPU (104) of the characteristics of the particular file represented in the LDTDP; • Next, the DTPU processor can be instructed to search for a particular header and other data within a series of parameters prior to effecting on the data. . Those skilled in the relevant art will appreciate that the DTPU (104) can be used to construct an EMV device using an increased storage area that is explicitly instructed to inspect and/or monitor a secure storage area (this can be referred to as a secure recording memory or Safety element). The EMV device can also accept commands from, for example, an external processor resident within the DTC (108). In an embodiment, the external DTC processor only transfers the data to the (several) memory area of the DTPU (104), and upon entering the memory area, the DTPU processor is responsible for further copying, reading, and writing of the data. And / or processing. However, in other embodiments, the data may remain controlled by an external DTC processor, where an external DTC processor (CPU) may issue instructions to the DTPU processor (CPU) to operate to copy, read, write, and/or Processing data. In another embodiment, the DTPU processor verifies the data before transmitting the data to a secure location (secure record memory). In addition, the DTPU processor instructs the EMV device to load the data or update itself after completing the inspection and verification of the data. In various embodiments, all of the memory storage (LDTDP storage memory, scratch memory, and secure recording memory) may be located on the EMV device. Alternatively, some memory banks may be located external to the DTPU but attached to one of the EMV devices. The memory storage can be file-based, using a data file (electronic file) located in a directory file (DF) with a directory or main file (MF). The firmware on the external DTC processor can be native firmware (using machine language), but can be decomposed for execution based on an interpreter-based operating system (including Java Card, MultOS, or BasicCard). Since both the external DTC CPU and the DTPU CPU provide instructions, the external DTC CPU will benefit from having the same firmware as the DTPU CPU, thus allowing instructions to be provided using the same format. At this point, it may be beneficial to update the firmware for the DTPU CPU if and when updating the firmware for the external DTC CPU. In some embodiments, the firmware for both the external DTC CPU and the DTPU CPU can be stored in the same location and can be accessed by both CPUs, thus requiring only an update to one firmware repository. However, a single source of firmware may have security implications. Figure 1 details a DTC (108) that can form a communication link with a smart phone transceiver (116) of a smart phone (106) via a DTC transceiver (114) to enable data transfer therebetween . In an embodiment of the invention in which the digital transaction file is associated with a user attempting to conduct a transaction, the user can operate the user interface (110) of the smart phone (106) to select a particular digital file and at the DTC (108). Start the digital file in ). Once the DTC (108) takes the required characteristics and uses the characteristics of the digital transaction file selected by the user operating its smart phone (106), the DTC (108) can then be used to trade with the DTC (108). At this point, the DTC (108) operates using all of the features of the selected digital transaction file. Once the selected digital transaction file is launched as a file to be installed as a file to which the DTC belongs, the file becomes a DTC trait. In other words, once a DTC becomes a physical instance of a document, the document becomes a "trait" of the DTC. In particular, the DTC (108) having the selected trait for the selection of a digital transaction file can then be used to include a merchant terminal (not shown) and/or one of the merchant terminals shown in FIG. The existing infrastructure of one of the digital payment transaction networks is transacted to achieve a series of transactions. In the case of using a DTC (108) having a selected digit transaction file as its trait, communication with the DTC (108) can be achieved by using any existing communication means between the DTC and the merchant terminal and in FIG. Merchant terminal (102). The illustrated example includes one transaction between the DTC (108) and a merchant terminal (102) by physical contact between the DTC (108) and the merchant terminal (102), the physical contact typically comprising A physical contact between an external contact plate (112), one of the payment devices incorporated in the DTC (108), and an electrode (not shown) resident in the merchant terminal (102). A further example of a transaction between a DTC (108) and a merchant terminal (102) includes the use of the contactless proximity communication capabilities of the DTC (108) and the merchant terminal (102) and in which the DTC (108) In the example containing a magnetic strip, a magnetic strip reader of one of the terminal (102) and the DTC (108) is used to implement the transaction. The embodiment of Figure 1 has been described above in accordance with one embodiment of an EMV device incorporating a firmware modification. Similarly, the embodiments described in Figures 2A, 2B, and 3A through 3D can be implemented using one of the EMV devices involved in a firmware modification. Referring to Figure 2A, a DTC in the form of a physical card (200) having one of the associated DAD user interfaces (202) is graphically illustrated, which progressively performs a procedure for selecting a different trait for the DTC (200). In the embodiment of Figure 2A, the DTC (200) does not have a particular trait at the beginning of the process of selecting a trait. A user can operate a smart phone (204) and communicate with the DTC (200) in accordance with a contactless proximity communication protocol to select the qualities required for the DTC (200). In the particular example of FIG. 2A, the smart phone (204) has executed software to present available card traits to a user who has selected a VISA card as a preferred trait of the DTC (200). In an embodiment, it may be necessary for the user to provide biometric authentication (such as a fingerprint) to operate the smart phone (204) to select a trait of the DTC (200). Once the smart phone (204) passes the user's choice of a VISA card as a trait to be adopted by the DTC (200), the relevant selection and/or information is transmitted from the smart phone (204) to the DTC (200) and accepted. After indicating the selection and/or information of the LDTDP of a VISA card, the DTC immediately adopts the characteristics of the VISA card (206). At a later point in time, the user may prefer to change the trait of the DTC to a MasterCard and operate the software on the smart phone to select a MasterCard trait for the purpose of implementing one of the DTC trait changes. Referring to Figure 2A, the smart phone (204) has been operated to select a MasterCard trait and after passing the relevant selection and/or LDTDP data to the DTC (200), the DTC immediately adopts a MasterCard trait and thereafter, DTC ( 200) will operate as a consumer MasterCard (208). Finally, once a consumer has completed trading with their DTC, they may prefer to cause the DTC to have a zero return trait, and with reference to Figure 2A, the smart phone (204) is operated to identify consumer preferences by The zero return attribute gives the DTC and locks its DTC. After passing the user's request, the smart phone (204) immediately causes the DTC (200) to adopt a zero return trait (200). In the embodiment of FIG. 2A, the DTC (200, 206, 208) is one of the modified software DTPUs that have been modified to allow/make the DTC capable of employing a return based on the data instructions transmitted by the DAD (204) to the DTC. Different qualities of zero traits. Communication between the DAD and the DTC can be achieved by the DAD processor communicating with a DTC external processor via respective transceivers (shown as smart telephony transceiver (116) and DTC transceiver (114), respectively, in FIG. 1) And the DTC external processor, which has received the instructions and/or data from the DAD, cooperatively communicates with the EMV device to cause the EMV device to employ a desired trait based on the instructions and/or data received by the DTC from the DAD. Referring to Figure 2B, the same steps depicted in Figure 2A are illustrated in Figure 2B with respect to changes in the characteristics of a digital transaction card. The reader will note that the DTC in Figure 2B includes a DTC (210) having a user interface with a return-to-zero trait, which is described in more detail below, with particular reference to Figure 3D. In the example of the embodiment depicted in FIG. 2B, the request to change the characteristics of the DTC (210) is implemented by the DTC user interface compared to the DAD user interface (refer to FIG. 2A). Regarding the DTC (200) in FIG. 2A, the zeroing trait DTC (210) in FIG. 2B is operated by the user to operate the zeroing characteristic DTC (210) (which includes the scrolling key and the home key and one of the displays on the DTC) The user interface is converted into a VISA card (206). When attempting to change the trait from a VISA card (206) to a MasterCard (208), the user operates the DTC scroll button to observe the display of the available features sequentially when the scroll button is repeatedly pressed. Once the MasterCard trait is displayed, the user can press the home button and change the DTC trait accordingly. The DTC (208) can be changed to a zeroing trait again by the user operating the DTC user interface to display and select a zeroing trait and achieve a zeroing trait. Referring to Figure 3A, in conjunction with one of the forms of a smart phone (302) and a merchant terminal (304), the DAD illustrates one of the DTCs in the form of a wearable device (300). In this particular embodiment, the wearable device (300) is also provided with a watch that displays the current time function and any other function that is available according to the wearable device (300). Increasingly, wearable devices are employed by consumers to combine the functions of many individual items, thereby reducing the complexity of conducting transactions because once a DTC functionality is incorporated into a wearable device (300), It is no longer necessary to carry a separate DTC. Wearing the wearable device (300) allows the user to trade with the device that they would normally wear. In the example of FIG. 3A, the wearable device (300) is illustrated in communication with a smart phone (302) and a merchant terminal (304) via contactless proximity communication. Of course, although all three devices are illustrated as being in close proximity, those skilled in the relevant art will understand that the wearable device (300) does not have to be both non-compliant with both a smart phone (302) and a merchant terminal (304). Contact close-range communication and communication between the respective devices can occur separately at different times. Referring to FIG. 3B, one of the forms of a ring (306) replaces the wearable device in detail for non-contact proximity communication with one of the DADs in the form of a smart phone (302) and a merchant terminal (304). . Again, in the illustration in FIG. 3B, a smart phone (302), a wearable device in the form of a ring (306), and a merchant terminal (304) are used between the contactless proximity communication. Communication. Referring to Figure 3C, yet another embodiment is illustrated in which the DTC is provided in the form of a smart phone housing (308). In this particular embodiment, one of the DADs in the form of a smart phone (302) communicates with one of the DTCs in the form of a smart phone housing (308), which in turn communicates with a merchant terminal (304). According to the non-contact proximity communication according to ISO/IEC 14443, all communication illustrated in Figure 3C occurs and in this particular embodiment, not a wearable device, the DTC takes the form of another convenient device, i.e., a smart type The phone case (308) is because the user periodically purchases a case for his or her smart phone to protect his or her smart phone from damage. Of course, in the embodiment of FIG. 3C, if a consumer would use one of the DTCs in the form of a smart phone casing (308) and attach the casing (308) to the smart phone (302), then wisdom The DAD in the form of a telephone (302) and the DTC in the form of a smart telephone casing (308) are simultaneously owned by the consumer. The reader will appreciate that DTCs can be configured in a number of different ways and exist from DTCs that have minimal (or limited) functionality/connection capabilities but will be less expensive to produce and less prone to failure, to have maximum functionality and include auxiliary use. The characteristics of the interaction and therefore will be considered more "user-friendly" but will produce one of the DTCs that are more expensive and will be more prone to failure. 3D provides a graphical representation of four DTCs having a credit card outline, thereby each including an EMV device (310) and an optional print identification (312) (in the illustrated embodiment, the name of the card holder), and The characteristics of the functionality/connection capabilities of the four DTCs represent a significant difference in the user experience with respect to digital transactions. For example, the uppermost DTC (314) depicted in Figure 3D represents one card with minimal functionality/connection capability and includes an EMV device (310) that is firmware modified and enables EMV devices with a DAD (302) The NFC wireless connection capability between them changes the characteristics of the DTC (314), but excludes an external DTC processor (called an MCU), Bluetooth connectivity, and any form of display or scroll button/home button. In a particular embodiment, a DTC (314) configured to have minimal functionality/connection capability can be issued to a user such that the EMV device (310) has pre-loaded multiple traits. More generally, after the DTC (314) is delivered to the user, one of the plurality of traits can be transmitted to the EMV device (310) or several traits for simultaneous delivery by the EMV device (310) using the DAD (302). Store. The depicted second DTC (316) also represents one of the cards with minimal functionality/connection capability of an EMV device (310), the EMV device (310) is modified by the firmware and enables the EMV device and a DAD (302) Wireless connectivity (such as Bluetooth and/or NFC) to change the characteristics of DTC (316). The DTC (316) also contains an MCU (not shown in Figure 3D). A DTC (316) configured to have a relatively minimal functionality/connection capability but including an MCU can be issued to a user, wherein the EMV device (310) accesses data that performs to multiple traits. Alternatively, after the DTC (316) is delivered to the user, one of the plurality of traits can be transmitted to the EMV device (310) using the DAD (302) or to transfer several traits for simultaneous storage by the EMV device (310) . The third DTC (318) depicted in Figure 3D represents a medium functionality/connection capability card containing one of the EMV devices (310), the EMV device (310) is firmware modified and the EMV device (310) is enabled with a DAD (302). Between the wireless connectivity capabilities (such as Bluetooth and / or NFC) and change the characteristics of DTC (318). The DTC (318) also includes a display (320) that can be in the form of a simplified 4-digit alphanumeric interface for displaying information, including but not limited to selected on a loaded (or previously stored) card. A trait, a unique ID or abbreviation of a selected trait, a date of expiration for a document, a temporary PIN number, a PAN number or part thereof, and/or a name of one of the card owners. A DTC (318) configured to have a medium functionality/connection capability can be issued to a user such that the EMV device (310) can access information about multiple traits. Alternatively, after the DTC (318) is delivered to the user, one of the plurality of traits can be transmitted to the EMV device (310) or several traits for simultaneous storage by the EMV device (310) using the DAD (302). . The fourth DTC (322) depicted in Figure 3D represents one card having a high level of functionality/connection capability and includes an EMV device (310) that is firmware modified and enables the EMV device (310) with a DAD ( 302) NFC or Bluetooth wireless connectivity capability and transfer of multiple traits to the EMV device (310) after delivery of the card. The DTC (322) also includes a more comprehensive display (324) and a scroll button/home button (326) that enables user input including input to implement a selection of stored traits. Those skilled in the relevant art will appreciate that even when one of the smart phones such as a user, DAD (302), does not exist (for example, if the DAD is not carried by the user or has a discharge battery), the card is on the card. The inclusion of a user interface enables the use of the DTC (322). Table 1 is a graph of one of the DTC embodiments (314, 316, 318, and 322) depicted in Figure 3D when the EMV device associated with the DTC is modified by firmware, which details the combination of features present in the various embodiments. The ✔ symbol indicates the presence of a feature, and the ✘ symbol indicates that a feature does not exist, and it should be understood that the list of embodiments merely represents one of the possible embodiments that may be configured with different combinations of features and is not intended to represent one. Detailed list. Table 1 Firmware modified EMV device

In the first embodiment of Table 1, the DTC (314) needs to use a data assist device (DAD) having a modified NFC capability (such as a smart phone) to transfer data to one of the firmware modified EMV devices. . As previously described, a firmware modified EMV device has an external DTC CPU including firmware, and the firmware is operable to write data (for example, LDTDP data) to the scratch memory so that when the DTPU is activated, The DTPU copies the data to a secure record memory (secure element) in the DTPU in such a way that the DTC uses a particular card trait or assists in a digital transaction in some other way. The information about each trait may be stored in a memory associated with the DAD, where the communication between the DAD and the DTC may be in the form of an instruction to download and copy the data to the security element for the purpose of updating the characteristics of the DTC. The firmware modified DTC (314) is limited to use with an NFC enabled DAD and use one of the EMV devices with modified contactless communication capabilities to securely receive data from NFC enabled DAD reception, but with the ability to target one A single plan takes advantage of multiple traits and low cost and low failure propensity because the DTC (314) does not include an MCU, display or scroll button/home button. The firmware modified DTC (316) also requires the use of a data aid (DAD) such as a smart phone to pass data to one of the firmware modified EMV devices, as described above. The difference between DTC (314) and DTC (316) is that DTC (316) contains an MCU that can store information about multiple traits (and/or may be related to changing some other digital trading parameters) rather than The data is stored in DAD memory and can accept a safe working phase between one of the DADs with wireless connectivity (NFC or Bluetooth) and the DTC with MCUs that also have wireless connectivity (NFC or Bluetooth). The advantages of using firmware-modified DTC (316) include low cost and low failure propensity, there is no DAD enabled for an NFC (where the MCU can accept communication with a single Bluetooth enabled (for example) one of the phones) Requirements, the ability to employ multiple traits for a single plan, and the ability to assist in secure data transfer from DAD without the use of an MCU with one of the EMV devices with modified contactless communication capabilities. The DTC (318) in Table 1 also requires the use of a data aid (DAD) such as a smart phone to transfer data to a wireless connection (NFC and/or Bluetooth) via a contactless interface. One of the safe working phases between a DAD and a DTC is a firmware modified EMV device. The DTC (318) includes an MCU that is enabled from NFC and Bluetooth enabled DAD to accept wireless communications and can thereby establish a secure phase of operation between most phones and DTCs containing MCUs. The advantages of using DTC (318) include low to medium cost, low to medium failure tendency, and there is no need to use an NFC enabled DAD alone, but since DTC (318) includes an MCU and display (320), DTC (314) and DTC (316) have a higher cost associated with the production of DTC (318). When using the DTC (322) described in Table 1, those skilled in the relevant art will understand that it is not necessary to use a DAD (such as a smart phone), but DAD can be used to change the characteristics of the card or to some other The way assists in a digital transaction. In any case, the DAD must initially set up the card and download/store multiple traits in the MCU, but after the initial setup, the card itself can be used to change the traits of a card using the scroll button/home button (326). Parameters or assist in digital trading in some other way. An MCU is used to accept wireless communication (both Bluetooth and NFC) from the DAD during an initial setup, and is further programmed to include, for example, one of a scroll key/home key (326). The interface accepts commands and converts keystrokes into commands. When using the scroll button/home button (326) to change the characteristics of the DTC (322) or perform some other task of the auxiliary digit transaction, the local interface authorizes the transmission, and the local interface authorizes the MCU to select the stored data and store it. The data is copied to the secure element. The DTC (322) has the advantage of selecting a trait at the local end from a number of multiple parallel traits stored on the card without the risk of discovering the card details during an update or change (ie, a change in status/update), because The card details were not transmitted. Further advantages include reducing the time to implement updates or changes (ie, status/update changes), the need to deliver a minimum amount of data to achieve one of the trait changes, and the ability to change DTC traits without using a DAD. However, DTC (322) has a higher production cost and may have a higher tendency to fail due to its complexity. In the following, embodiments of the apparatus and method of the present invention are exemplified, which discuss a possible logical digit transaction file or digital transaction file type and its associated token for a financial transaction. The illustrated logical digit transaction file/digital transaction file and its associated tokens relate to one of a major digital transaction file (primary credit card), as well as other sub-digit transaction files (sub-credit cards) and their associated tokens. However, it should be understood that the present invention is more widely applicable to other types of digital transaction files and their associated tokens, such as stored value cards, membership cards, transportation cards, driver's licenses, passports, age certification cards, identification cards, and other financials. And non-financial transaction documents. A digital transaction file is considered to mean a card, file or other physical object or, for example, in the case of a bank account, meaning that the bank account exists in an operating system entity. A "logical" digital transaction file coefficient bit transaction file indicates that it contains material associated with a particular digital transaction file. The material may include one of the documents uniquely identified (unique ID), the expiration date, or any other such information that uniquely identifies the digital transaction file, as well as other information regarding the digital transaction. For example, for a credit card, the unique ID is a person/primary account number (PAN), and the (number) associated token is a substitute number of the PAN, which is the same digit number as the substitute PAD, but is safely generated. A different number. 4 shows an illustrative element in a system in accordance with an embodiment of the present invention. One component is a digital transaction card (DTC) (412) and the other component is a data assist device (DAD) (414). In this example, the DAD is a smart phone, but it can be a computer tablet, some other form of portable computing DAD, or a particular DAD for the purposes of the present invention. The system is used for payment at one of two exemplary digital transaction devices, including a point of sale/point of sale electronic transfer system (POS/EFTPOS) terminal (16A) and an online transaction terminal (16B). Online trading terminals can include a personal computer (PC) or any other device enabled for use on such online (no card/no DTC) transactions. The DTC (412) has a primary digital transaction file (419) which is a primary credit card. As a logical digital transaction file, the primary credit card is loaded onto the DTC (412) and can be completed prior to being supplied to the user (420). In addition, the (several) token associated with the primary credit card can be loaded onto the DTC prior to being supplied to the user. The user can link (415) the smart phone (414) to the DTC (412) because the DTC (412) is supplied with a preloaded primary digital transaction file (primary credit card) (419) and (several) associations. Symbol. The linking procedure (415) is further detailed in Figures 2, 3 and 7 which show the initial setup of a DTC (412). 4 shows an exemplary step of establishing a DTC (412) and issuing the DTC (412) to a user (420). There may be several actors providing a DTC (412), including a humanized company 402, a DTC (card) integrator (404), a DTC (card) manufacturer (406), and a security provider (408). The security provider (408) provides the (several) token associated with a given digital transaction file. Other actors issuing a DTC (412) may include an issuing financial institution (440), such as a bank or other similar party. The issuing financial institution (440) can act as a security requester (fuji requester) (442) that is supplied with, for example, a child (444). The customer service (446) of the issuing financial institution (440) can interact with the user (420), the user (420) requests the DTC (412) and supplies the required information to the financial institution, such as the name, date of birth, and its DAD. Details (in the case of a smart phone, it can be an IMEI number or another suitable unique ID for a smart phone). The financial institution (440) can then generate a secure cryptographic key that is provided to the personalization company (402) for establishing the DTC (412). In this embodiment, the DTC (412) is a credit card type transaction card. The DTC (412) has an EMV chip (where EMV is an abbreviation of Europay, MasterCard and Visa (Europay, MasterCard, and Visa)) (Digital Transaction Processing Unit (DTPU)) (422), a button (423), which The DTC can be used to connect the smart phone (414), for example, by using BluetoothTM for completing the connection. The DTC (412) also has a DTC display (424) that can be used to display one of the unique IDs of one of the selected logical digit transaction files to simplify the graphical user interface, the unique ID being loaded onto the DTC and implemented On the DTC (412), it acts as the digital transaction file. In the case where the DTC is implemented as a tokenized digit transaction file, the DTC display (424) displays the token number. In the example shown in FIG. 4, the digital transaction file is one of a primary credit card or a plurality of secondary credit cards. The DTC (412) also has the means to display the expiration date of one of the particular digital transaction files being operated on. The DTC also has a space for one of the displays (428) for the name of the person (420) who owns the DTC. In some embodiments, the name of each and every logical digit transaction file will be the same, ie, the name of the user (420). However, in other embodiments, the name associated with a particular logical digit transaction file may be different, for example, if one person uses DTC (412) for both personal use and company use. At this point, the DTC namespace (428) may be just a printed name, or may be enabled to display one of the different names to simplify the graphical user interface (GUI). Different names may be displayed depending on the token selected for a transaction. The DAD (414) for a smart phone includes a smart phone interface (430), which in Figure 4 is a screen (430) and a keyboard. Alternatively, the smart phone can include a touch screen such that no keyboard is required. Figure 4 also depicts the initial setup of a DTC (412) and a smart phone (414), the creation and distribution of a DTC-related actor and the use of DTC in a transaction. Figure 4 also shows the connection (415) of the DTC (412) to a smart phone (414). The details of the steps of the financial institution (440) (including the actor) issuing the DTC and the DTC issue (in some embodiments, including the issuance of the major credit card) are also illustrated. The DAD (414) that is a smart phone has an IMEI number or another suitable unique ID to uniquely identify the smart phone. Smart phones can use Android and/or iOS operating systems or any other suitable operating system. In an embodiment, the smart phone (414) includes wireless connection technology, such as near field communication (NFC) and/or BluetoothTM or BluetoothTM LE. The DTC (412) has a DTC chip (422) that can be authenticated as a smart card chip (DTPU) (422) so as to be generally operable to transfer data only to an external read/write device. Examples of certified smart card chips may comply with one or both of the following certification standards ISO/IEC 7816 or ISO/IEC 14443. In addition, certified smart card chips can comply with other standards such as the general guidelines EAL4+/EAL5+ (ISO/IEC 15408 Information Technology - Security Technology - Evaluation Guidelines for IT Security Sections 1 to 3), FIPS 140-2 3 and 4 , ISO/IEC 7816 identification card, integrated circuit card parts 1 to 5, ISO/IEC 14443 identification card - non-contact integrated circuit card - proximity card parts 1 to 4 and EMVCo. Figure 5 shows an exemplary setup of one of the DTCs (512) operating in a system having a DAD (514) that is a smart phone with a smart phone interface (30). In this example, the setup begins with the user (520) extracting the IMEI number or another suitable unique ID (503) from the smart phone (514). The IMEI number, which is the unique ID of one of the smart phones (514), is provided (505) to the relevant financial institution (502) (which is also referred to as the issuing financial institution). The financial institution (502) records and processes the submitted IMEI number and user details, and after recording such details, the financial institution looks up the section (534) to find the record and populates an application using the seed/secret key (538) information. The program sends an application link (540) to the smart phone (514) via an out-of-band (OOB) notification (544). An application link (540) in a software application (application software) of a smart phone (514) is available via, for example, one of the Internet downloads (554) of the cloud (556), the application software The user (520) can operate by clicking on the smart phone (514). When the seed/secret key (538) is downloaded to the smart phone (514), the portion of the setup is completed and the user (520) can continue to connect the smart phone to the DTC (512). Figure 5 also shows a DTC (512) with a DTC display (524) that displays a unique ID (526), in which case the unique ID (526) is the token number of the primary credit card (sometimes referred to as a dynamic symbol) The number is recorded, ie, the primary logical digit transaction file causes the DTC (512) to behave as a tokenized digit transaction file (ie, to characterize the primary credit card). Figure 5 also shows that the issuing financial institution (502) acts as a security requester (fussing requester) (504) and obtains the role of the key (510), passes the key (510) to the customer service (508) and then passes To find (534), a seed/secret key (538) is developed using a counter (536) and then passed to the smart phone (514) via the application software link (540). 6 shows an illustrative step of setting up a DTC (612) as provided by a personalization company (602), which involves both a DTC integrator (604) and a contactless DTC manufacturer (606). The personalization company (602) also works with a security provider (608) (which generates one or more of the credit card providers), and the security provider (608) is then paired with the issuing financial institution. (610) (which is a security requester (registered requester) (611)) works. The financial institution (610) establishes a sub- (616) to supply the seed (616) as one of the other suitable unique IDs and security details of the IMEI or smart phone loaded with the smart phone via the customer service (618). Program (640). In this manner, FIG. 6 demonstrates an exemplary method in which the DTC (612) may be pre-loaded with a primary logical digit transaction file (in this example, a primary credit card) and its associated tokens. The DTC (612) and the smart phone (614) each have details of the primary logical digit transaction file and associated tokens such that the user (620) can operate the smart phone (614) to select the primary logical digit on the DTC (612). The transaction file, and then one of the associated digits of the primary logical digit transaction file is selected, and causes the DTC (612) to act as a tokenization primary digit transaction file. In this regard, it should be appreciated that in some embodiments, the logical digit transaction file may be partially stored on the DTC (612), and other portions of the logical digit transaction file may be stored on the smart phone (614). Enabling the smart phone to operate to select a particular logical digit transaction file and select one of the tokens associated with the logical digit transaction file for a transaction, and such that the smart phone can cause the DTC (612) to act as The logical digit transaction file and the associated associated token are selected to be associated with the digitized transaction file. 7 shows an exemplary embodiment in which one of the primary logical digit transaction files (primary credit card) and associated token DTC (712) that has been loaded onto it may have been loaded via smart phone (714) to The additional secondary logical digit transaction file (18) and its (several) associated tokens. In this example, the second logical digit transaction file (18) is another credit card. In this example, the user (720) supplies or types additional card (18) details to the primary card issuing financial institution (702) via the customer service section (708) of the primary card issuing financial institution (702). In one embodiment, the primary card (or DTC) issuing financial institution may perform a transfer with one of the reference numbers or one of two unique amounts of money and one loan (which may be added to the primary card) Verification is performed on each of the credit cards (18). When the user (720) has a list (710) issued by a particular secondary card (or DTC) issuing financial institution (716), the list will show a transfer with one of the reference numbers or one of two unique amounts and A loan. The user (720) reads the list (710) and types or submits details from the list to verify that the user (720) is added to the actual owner of each additional credit card of the primary card (eg, as represented in FIG. 4) . When the primary card (or DTC) issuing financial institution (702) is satisfied that the user (720) is the correct owner of the additional credit card, the primary card issuing financial institution may request the user to add the additional card to the financial institution (702) and read The card is fetched to extract a public encryption key for use with, for example, a POS/EFTPOS terminal's password. Alternatively, the primary financial institution (702) may send a request to the financial institution (716) that has issued an additional card for the public encryption key used in one of the passwords at a POS/EFTPOS terminal. When the primary card issuing financial institution (702) is satisfied with the correct owner of the user (720) extra card (18), the institution (702) can send the code to the user registered smart phone via the OOB message (714) . Next, the user (720) has a code that, when selected, can be used to load one of the secondary logical digit transaction files (sub-credit cards) selected from the smart phone (714) into the DTC (712). In an embodiment, the digits associated with the (s) secondary card 18 may be issued simultaneously with the (several) secondary card using the methodology shown in FIG. Alternatively, a method release token similar to one of the ones shown in Figure 7 may be used after the issuance of the (s) secondary card, wherein several tokens or tokens are verified using the transfer/loan method discussed above. 8 shows program steps for adding additional security by adding additional payment tokens to each of the additional credit cards (818), via the customer service section (808) via OOB (810) with additional security tokens Provided to a smart phone (814). For a transaction, a token is selected to be implemented on the DTC (812) as a tokenized digit transaction file, where the DTC (812) displays the token number in the display. The token supplier (806) may also be a supplier to one of the DTC (812) wafers (822). The token supplier generates a token for the replacement of the PAN used as a credit card. The user can only add the token once, or, for example, if the token is set to expire after a certain date or if the token is a one-time token, the token is added on a regular basis. If the token is specified for a particular transaction type and the user wishes to conduct the transaction of the category, the user may also seek further tokens. Figure 9 shows that a DTC (912) can operate using different types of smart phones. However, DTC can only be connected to one DAD (smart phone) to exclude all other DADs. As shown in Figure 9, a user may decide to purchase a new smart phone (952), in which case the DTC (912) will need to be updated to be able to connect with the new smart phone. In this example, an old smart phone (950) is connected to the DTC (912), but the user wishes to connect the new smart phone (952) to the DTC (912). The link is, for example, a two-way encrypted transmission. The DTC (912) can be loaded with matching seeds and dynamic keys at the time of manufacture to enable connection to only one smart phone (950). In order to link the DTC (912) to the new smart phone (952), a dynamic code is constructed from, for example, a dynamic key or a sub-category can be made available to the verified owner. Use a dynamic key or seed to disconnect or unlink the old smart phone (950) from the DTC (912). The DTC can then be loaded with a matching seed and/or dynamic key to interface with the new smart phone (952). The seed and dynamic key are based on the IMEI of the smart phone or another suitable unique ID of the smart phone. It should be understood that the code that links the DTC to the smart phone must be unique to each DTC and unique to the serial number of each DTC. In this regard, the connection between a smart phone and a DTC can occur only between the smart phone and the DTC based on another suitable unique ID and DTC number that matches the IMEI or smart phone. Figure 10 shows a screen on one of the smart phones (1014) in one of the initial pairings (links) for a smart phone (1014) and a DTC (1012). In the first screen (1002), the smart phone displays a title "Settings" (1004), and under the title (1004) is a "Settings" button (1006), and under the button (1006) is displayed "Internet" One of the indicators of the network connection. The next screen (1032) displays a title "Status" (1034), which includes an "Apply Code" button (1036) and a "Key" key field (1038), and a "Pair with Card" (alternatively) , "Pair with DTC" button (1040). In the final screen (1042), a "Congratulations" message (1044) is displayed which indicates to the user (1020) that the smart phone (1014) is linked to the DTC (1012). In one embodiment, the smart phone (1014) is also coupled to the DTC (1012) by a link button (1023), and the link button (1023) is pressed and held (1046) so that it can be connected to the smart phone ( 1014). Figure 11 shows an embodiment having a DTC (1112) with one of a number of indicators on the front side (1112f) and a back side (1112r), such indicators showing, for example, the mains stored on the DTC (1112) Personalized details related to logical digit trading files. A flag (1104) of the primary card (1119) is printed on the front side (1112f) of the DTC, and a full image (1106) attached to the DTC (1112) is attached. DTC (1112) can also display the main card expiration date (1108). On the back side of the DTC (1112), there may be one panel for the signature (1110) of the primary card owner. Card Verification Value (CVV) (1114) can also be printed, along with other identifying details. In some embodiments, where the details are printed or otherwise permanently marked on the DTC (1112), the details will only pertain to the primary logical digit transaction file stored on the DTC (1112), such as the name of a user. , CVV, due date. In the case where a DTC (1112) displays details in a changeable GUI, such details may relate to a logical digit transaction file (including a primary logical digit transaction file and a secondary logical digit transaction file) that is currently expressed as a DTC digital transaction file. In an exemplary transaction, the merchant checks that a valid DTC can include the following: 1. DTC (1112) contains a full-color DTC issuer trademark, 2. DTC number (or alternatively, primary card number) is 12 to 19 digits One of the effective lengths, 3. The four digits before the DTC number displayed on the DTC display are the same as the numbers printed directly below. 4. The expiration date is in the future and in the correct format "MM/YY", 5. Full image or The Holomag band can be located on the front or back side of the DTC. If it is located on the front side of the DTC, it can be located above the trademark. If it is located on the back side of the DTC, it can be located above or below the signature panel. 6. A magnetic strip is present on the DTC and above the signature panel, and should be viewed. Go up smooth and straight without tampering. On some DTCs, the full image strip can be used instead of the magnetic strip, and 7. The four digits printed on the signature panel must match the four digits after the account number, followed by the three digit card verification code (CVC) number. Figure 12A shows an exemplary embodiment of using a smart phone (1214) to select a different logical digit transaction file (different credit card) for transaction update DTC (1212) using one of the selected logical digit transaction files. The first smart phone screen (1202) has a "login" title, followed by three buttons for selecting a security type, including a "PIN (Personal Identification Number)" button (1204), a "Slide" button 1206, and a Biometric button (1208). The user (1220) selects one of the options (1204), (1206) or (1208), and then the smart phone (1214) displays the next screen (1210), which displays a "Payment Options" title below the title. A "current" title (1211) is displayed indicating the file currently operating on the DTC (1212). In this example, the smart phone screen (1210) shows that the current operating file is a "VISA" card (1213). The user can operate a screen (1210) to select one of four other files (credit cards) that can be operated on the DTC (1212) and listed under the "Change to" heading (1215). Additional documents for financial transactions include the "VISA" button (1217), the "MasterCard" button (1218), the "Bank Transfer" button (1219), and the "American Express" button (1221). The user (1220) selects one of the files under the "Change to" heading, which in turn causes the smart phone (1214) to display the next screen (1252), which displays the message "Payment Method" (1234), below the message. Two buttons are displayed, the "Yes" button (1236) and the "No" button (1238). The user (1220) can press one of the buttons to determine if the MasterCard will be the preferred payment method. The next smart phone screen (1242) displays a security option for the user with a "change token" header (1244) and a "yes" button (1246) and a "no" button (1248). At the screen (1242), the user can select, for example, whether to change the current token for the current transaction file operation. If "Yes" is selected (1246), the user can then present a list of associated tokens to enable selection of one of the listed tokens. As mentioned previously, in various embodiments, the tokens may only be presented as token numbers in the list. In other embodiments, the tokens may be symbolized as, for example, a schema. The next smart phone screen (1242) displays the status and includes the "Status" title (1254), below which is displayed one of the "Biometric Settings / No Settings" (1256) indicator, and the screen (1242) also displays the command ""TouchCard" (alternatively, "Touch DTC") (1256), and one of the smart phones (1214) and DTC connected indicators "Card Link" (alternatively, "DTC Link") (1258) . The smart phone (1214) then transmits the data to the DTC (1212) to update the DTC with the new selection file and the note details, and causes the DTC GUI display (1224) to display the newly selected file (credit card) number (1260) as the token. number. In one embodiment in which the DTC (1212) implements only one file (credit card), as an additional security precaution, the DTC (1212) may also print 4 leading digits (1267) of a single credit card to associate with the credit card. All of the displayed token numbers (1260) must have the same 4 leading digits. The smart phone then displays a further security screen (1262) that includes one of the one-time PIN (OTP) "Build OTP" buttons (1264) displayed in a panel (1268) when pressed by the user (1220). . The user can then present the DTC (1212) to a merchant (1270) and then process (1272) the DTC via communication with a valid credit card (digital transaction file) issuing financial institution (1274). In some instances, a transaction may exceed the standard limit and the smart phone (1214) may display a message "Exceeded Restricted Transaction" (1282) on a screen (1280). The user (1220) can then authorize the over-restricted transaction by pressing the "Yes" button (1284) under the message (1286) inviting the user to authorize the transaction. Alternatively, the user (1220) may press the "No" button (1288) so that the transaction is not authorized and does not continue. Figure 12B (which depicts a cardless transaction) is a view similar to Figure 12A, wherein the smart phone is also shown with a unique identifier associated with the selected token for displaying the selected logical digit transaction file (at In this example, the screen (1262) of one of the panels (1263) of the selected credit card (digital transaction file) (1260). The Smart Phone Screen (1261) also displays the due date (1267) under the heading "Expiration" (1267). The smart phone screen (1262) can also display the CVV (1269) of the selected file in the CVV display panel. Figure 13 shows an exemplary in-store or physical card (entity DTC) transaction using one of the systems in one embodiment of the present invention. In this example, the user (1320) decides to use the primary card to make a purchase and select an token for the card. The main card number is indicated on the DTC GUI display (1324). The user (1320) presents the DTC (1312) to the merchant POS/EFTPOS terminal (1316), which is a digital transaction device with an EMV reader. The EMV reader gets the details, including the password, the token, the token expiration date, and the token requester ID. The POS/EFTPOS terminal may obtain the details of the primary credit card by using the card track (1332) via a merchant acquirer (1318). The security token is then passed via a payment processor and via a security provider (character provider) (1334) to pass the security tokenized primary card details to deassert the token number to determine the PAN (or if not a credit card file, Then the other type of unique ID of a file), then the PAN is provided to the primary card issuing financial institution (1336) to process the payment (or other type of transaction if not a credit card file). In an exemplary embodiment, after reading the primary card details from the DTC (1312), the POS/EFTPOS terminal (1316) is built from details (including, for example, biometrics (1338) and other security (character) The warranty data (1340)) generates a password in which a number is given to the type and level of authorization from the details obtained from the wafer (DTPU) in the DTC (1312). The password can also include the merchant POS/EFTPOS terminal identification number, purchase price, and other relevant details for transfer to the merchant acquirer (1318). Figure 13 also shows the use of a smart phone on the DTC (1312) using a smart phone or via one of the Internet (1342) to select an online or no card transaction. The user reads the credit card number (1321), expiration date, and CVV number from the DTC (1312) or smart phone screen (1330) and types the details online or reads the details to a merchant via the smart phone. . The merchant retrieves the information and can trade using the correct authorization code provided. Figure 13 also shows that the transaction DTC (1312) can be used with a selection of other logical digit transaction files and associated selection tokens, the details of which are displayed on the DTC GUI (1324), ie other logical digit transaction file tokens. Unique ID (1344). In this way, the system can be used for physical card (entity DTC) transactions and cardless (no DTC) transactions. It should be understood that in this specification, the term "logic" refers to a set of characteristics for each of the digital transaction files. Features may include information such as the unique ID of the digital transaction file, ownership information, expiration date, and the like. The identification information can be a unique ID number. A change from one representation of a digital transaction file to a DTC that expresses another digital transaction file may also be referred to as a change in the DTC "trait". Throughout this specification and the appended claims, unless the context requires otherwise, the words "comprise" and variations such as "comprises" and "comprising" are understood to mean A statement of an integer or step, or an integer or group of steps, rather than excluding any other integer or step or group of integers or steps. A person skilled in the art will appreciate that many variations and/or modifications may be made to the present invention without departing from the spirit and scope of the invention as broadly described. Therefore, the present embodiments are to be considered in all aspects as illustrative and not restrictive.

16A‧‧‧Point of Sale Electronic Transfer System (POS/EFTPOS) Terminal
16B‧‧‧Online Trading Terminal
18‧‧‧ Logical digit transaction file/extra credit card/extra card
30‧‧‧Smart Phone Interface
100‧‧‧ device
102‧‧‧Digital Trading Device/Point of Sale/Point of Sale Electronic Transfer System (POS/EFTPOS) Terminal/Business Terminal
104‧‧‧Digital Transaction Processing Unit (DTPU)
106‧‧‧Smart Phone/Data Aid Device (DAD)
108‧‧‧Digital Trading Card (DTC)
110‧‧‧User interface
112‧‧‧electrode/external contact plate
114‧‧‧Digital Trading Card (DTC) Transceiver
116‧‧‧Smart Phone Transceiver
200‧‧‧ Physical Card/Digital Trading Card (DTC)
202‧‧‧User interface
204‧‧‧Smart Phone
206‧‧‧VISA Card/Digital Trading Card (DTC)
208‧‧‧ MasterCard/Digital Trading Card (DTC)
210‧‧‧ Zero Qualitative Digital Trading Card (DTC)
300‧‧‧wearable devices
302‧‧‧Smart Phone
304‧‧‧Business terminal
306‧‧‧ Ring
308‧‧‧Smart phone case
310‧‧‧EMV devices
312‧‧‧Print identification
314‧‧‧Top Digital Trading Card (DTC)
316‧‧‧ Second Digital Trading Card (DTC)
318‧‧‧ Third Digital Trading Card (DTC)
320‧‧‧ display
322‧‧‧ Fourth Digital Trading Card (DTC)
324‧‧‧ display
326‧‧‧ scrolling button/home button
402‧‧‧Personalized company
404‧‧‧Digital Trading Card (DTC) Integrator
406‧‧‧Digital Trading Card (DTC) Manufacturer
408‧‧‧Security providers
412‧‧‧Digital Trading Card (DTC)
414‧‧‧Data Assist Device (DAD)/Smart Phone
415‧‧‧Link/link procedure
419‧‧‧ Major digital trading documents
420‧‧‧Users
422‧‧‧EMV Wafer/Digital Transaction Processing Unit (DTPU)
423‧‧‧ button
424‧‧‧Digital Trading Card (DTC) Display
428‧‧‧Display/Digital Trading Card (DTC) Namespace
430‧‧‧Smart Phone Interface/Screen
440‧‧‧ issued financial institutions
442‧‧‧Security Requestor/Requester
444‧‧ ‧ seeds
446‧‧‧Customer Service
502‧‧‧ financial institutions
503‧‧‧IMEI number/unique ID
504‧‧‧Security Requestor/Requester
505‧‧‧ Provided
508‧‧‧Customer Service
510‧‧‧ Key
512‧‧‧Digital Trading Card (DTC)
514‧‧‧Data Aid Device (DAD)/Smart Phone
520‧‧‧Users
524‧‧‧Digital Trading Card (DTC) Display
526‧‧‧ unique ID
534‧‧‧ Financial institution search section
536‧‧‧ counter
538‧‧‧Seed/secret key
540‧‧‧Application Link
544‧‧‧Out-of-band (OOB) notice
554‧‧‧Internet download
556‧‧‧Cloud
602‧‧‧ Personalized company
604‧‧‧Digital Trading Card (DTC) Integrator
606‧‧‧Contactless Digital Trading Card (DTC) Manufacturer
608‧‧‧Security providers
610‧‧‧ issued financial institutions
611‧‧‧Security Requestor/Requester
612‧‧‧Digital Trading Card (DTC)
614‧‧‧Smart Phone
616‧‧ ‧ seeds
618‧‧‧Customer Service
620‧‧‧Users
640‧‧‧Application
702‧‧‧ Major Card Issuing Financial Institutions
708‧‧‧Customer Service Section
710‧‧‧list
712‧‧‧Digital Trading Card (DTC)
714‧‧‧Smart Phone
716‧‧‧Sub-card issuing financial institutions
720‧‧‧Users
806‧‧‧Character supplier
808‧‧‧Customer Service Section
810‧‧OOB (out of band)
812‧‧‧Digital Trading Card (DTC)
814‧‧‧Smart Phone
818‧‧‧Extra credit card
822‧‧‧ wafer
912‧‧‧Digital Trading Card (DTC)
950‧‧‧Old smart phone
952‧‧‧New Smart Phone
1002‧‧‧ first screen
1004‧‧‧"Settings" title
1006‧‧‧"Settings" button
1012‧‧‧Digital Trading Card (DTC)
1014‧‧‧Smart Phone
1020‧‧‧Users
1023‧‧‧Link button
1032‧‧‧Next screen
1034‧‧‧"Status" heading
1036‧‧‧"Application Code" button
1038‧‧‧"Key" type field
1040‧‧‧ "Pair with card" button
1042‧‧‧ final screen
1044‧‧‧"Congratulations" message
1046‧‧‧Keep
1104‧‧‧Primary card logo
1106‧‧‧Full image
1108‧‧‧ Major Card Due Date
1110‧‧‧Signature
1112‧‧‧Digital Trading Card (DTC)
1112f‧‧‧ front side
1112r‧‧‧ Back side
1114‧‧‧Card Validation Value (CVV)
1119‧‧‧ primary card
1202‧‧‧first smart phone screen
1204‧‧‧"PIN (Personal Identification Number)" button
1206‧‧‧"Slide" button
1208‧‧‧"Biometrics" button
1210‧‧‧Next screen/smart phone screen
1211‧‧‧"current" title
1212‧‧‧Digital Trading Card (DTC)
1213‧‧‧"VISA" card
1214‧‧‧Smart Phone
1215‧‧‧"Change to" heading
1217‧‧‧"MasterCard" button
1218‧‧‧ "Bank Transfer" button
1219‧‧‧"American Express" button
1220‧‧‧Users
1221‧‧‧"Dai Lai Card" button
1224‧‧‧Digital Trading Card (DTC) Graphical User Interface (GUI) Display
1234‧‧‧"Setting MasterCard as a Better Payment Method" message
1236‧‧‧"Yes" button
1238‧‧‧ "No" button
1242‧‧‧Smart Phone Screen
1244‧‧‧"Security" title
1246‧‧‧"Yes" button
1248‧‧‧ "No" button
1252‧‧‧Smart Phone Screen
1254‧‧‧"Status" heading
1256‧‧‧"Biometric Settings/No Settings" indicator / "Touch Card" command
1258‧‧‧"Card Link" indicator
1260‧‧‧New selected file number/character number
1262‧‧‧ screen
1263‧‧‧ panel
1264‧‧‧"Create OTP" button
1267‧‧‧4 leading figures/title "expiration date"/expiration date
1268‧‧‧ panel
1269‧‧‧Card Validation Value (CW)
1270‧‧ businesses
Processing 1272‧‧
1274‧‧‧Effective credit card issue financial institutions
1280‧‧‧ screen
1282‧‧‧"Exceeded Restricted Transaction" message
1284‧‧‧"Yes" button
1286‧‧‧Information
1288‧‧‧ "No" button
1312‧‧‧Digital Trading Card (DTC)
1316‧‧‧Business Point of Sale/Point of Sale Electronic Transfer System (POS/EFTPOS) Terminal
1318‧‧‧Business acquirer
1320‧‧‧Users
1321‧‧‧ Credit Card Number
1324‧‧‧Digital Trading Card (DTC) Graphical User Interface (GUI) Display
1330‧‧‧Smart Phone Screen
1332‧‧‧Car track
1334‧‧‧Security providers
1336‧‧‧ Major Card Issuing Financial Institutions
1338‧‧‧Biometric technology
1340‧‧‧Security Assurance Information
1342‧‧‧Internet
1344‧‧‧Other logical digit transaction files tokenized unique ID

For a better understanding of the present invention, and by way of illustration, the embodiments of the invention A graphical representation of one of the devices, comprising an embodiment of a digital transaction card (DTC) and an embodiment of a data aid (DAD) in the form of a smart phone, wherein the device is for use with a digit One of the transaction devices (in this example, a point of sale/point of sale electronic transfer system (POS/EFTPOS) terminal); FIG. 2A is a graphical representation of one of the DTCs in communication with the DAD of FIG. 1 in accordance with an embodiment The operation is to select a digital transaction file by using the DAD, and the selection of the characteristics of the DTC derived from selecting the desired trait on the DAD, and delivering the selected trait to the DTC; Figure 2B illustrates the use of a The DTC user interface selects one of the DTC graphical representations of the digital transaction file. In the embodiment of FIG. 2B, the DTC user interface includes various touch activation switches and a display; FIG. 3A, FIG. 3B, FIG. 3C, and FIG. Presented as a watch, Graphical representation of various embodiments of the DTC, in the form of a smart phone protection enclosure and a credit card body, depicting FIG. 3D in accordance with a minimum feasible product embodiment in the absence of an interface embodiment and with an interface embodiment Figure 4 is a functional flow diagram showing one of various parts of a system and a method in accordance with one embodiment of the present invention; Figure 5 is a diagram showing a method for setting up a digital transaction in accordance with an embodiment of the present invention. A functional flow chart of one of the systems and steps in the method of card (DTC); Figure 6 is a functional flow chart showing one of the initial settings with security; Figure 7 shows one of the steps of adding a secondary logical digit transaction file to the DTC Functional Flowchart; Figure 8 is a functional flow diagram showing one of the steps of increasing the security of a secondary logical digit transaction file; Figure 9 is a diagram showing the steps of linking a data assist device (DAD) to a DTC in accordance with an embodiment of the present invention. One functional flow chart; FIG. 10 is a series of screens in one of the DADs according to one of the embodiments of the present invention; FIG. 11 shows an embodiment of the present invention DTC; Figure 12A shows a screen of a DAD in a method according to one embodiment of the present invention for a physical card transaction; Figure 12B is a view similar to Figure 12A for a cardless transaction; Figure 13 A functional flow diagram of one example of using a DTC DAD payment in accordance with an embodiment of the present invention is shown.

100‧‧‧ device

102‧‧‧Digital Trading Device/Point of Sale/Point of Sale Electronic Transfer System (POS/EFTPOS) Terminal/Business Terminal

104‧‧‧Digital Transaction Processing Unit (DTPU)

106‧‧‧Smart Phone/Data Aid Device (DAD)

108‧‧‧Digital Trading Card (DTC)

110‧‧‧User interface

112‧‧‧electrode/external contact plate

114‧‧‧Digital Trading Card (DTC) Transceiver

116‧‧‧Smart Phone Transceiver

Claims (43)

A digital transaction device that can be operated with a plurality of digits, each digit identifier associated with a digital transaction file, and each digit transaction file associated with one or more digits, wherein each digit representation is used for Correlating a digital transaction file with one of the digital transactions of at least one digital transaction device, the digital transaction device comprising: a data assist device (DAD) including a user interface and a DAD transmitter; and a digital transaction A card (DTC) comprising a DTC receiver and a digital transaction processing unit (DTPU), wherein the device is configured to store at least one of the plurality of digits and the DAD is configured to allow The user is faced with the selection of the stored at least one of the digits and transmits the selection to the DTC, and wherein the DTC is configured to implement the selected digit, such that the DTC is enabled for operation The token-associated digital transaction file is represented by the selected digit. The digital transaction device of claim 1, wherein the DAD further comprises a receiver and the DTC further comprises a transmitter, and thus, data can be transferred between the DAD and the DTC. A digital transaction device as claimed in claim 1 or claim 2, wherein the DAD is operative to select and transmit a plurality of tokens representing one or more selectable traits. The digital transaction device of claim 1, wherein the selection and transmission token comprises one or more instructions. The digital transaction device of claim 4, wherein the one or more instructions comprise an instruction to change one of the current traits of the DTC to one of a plurality of selectable traits. The digital transaction device of any one of claim 3, wherein the plurality of selectable traits are stored on the DAD, and the current trait of the DTC is changed to the selected trait comprising: by the DAD And receiving, by the operation of the DAD user interface, the instruction to change the current trait of the DTC to the selected trait; transmitting, by the DAD transmitter, data related to the selected trait to the DTC receiver; And modifying, in the DTC, from the current trait to one of the selected traits, such that when the DTC is operated with a digital transaction device to implement the digital transaction, the digital transaction device identifies the selected trait. The digital transaction device of claim 3, wherein the plurality of selectable traits are stored on the DTC, and the current trait of the DTC is changed to the selected trait comprising: by the DAD And receiving, by the operation of the DAD user interface, the instruction to change the current trait of the DTC to the selected trait; and the DAD transmitter changes the current trait of the DTC to the selected trait Transmitting an instruction to the DTC receiver; and performing, in the DTC, a change from the current trait to the selected trait according to the instruction, such that when the DTC is operated with a digital transaction device to implement the digital transaction, the digital transaction The device identifies the selected trait. The digital transaction device of claim 1, wherein the DTC comprises a user interface. The digital transaction device of claim 3, wherein the selection from the DAD to the DTC containing information about the plurality of selectable traits is stored on the DTC and can be interfaced by the DTC user Operate and select individually. The digital transaction device of claim 9, wherein changing the current trait of the DTC to the selected trait comprises: changing, by the operation of the DTC user interface, the current trait of the DTC to one of the selected traits Or a plurality of commands; and implementing, in the DTC, a change from the current trait to the selected trait based on the one or more commands such that when the DTC is operated with a digital transaction device to implement the digital transaction, the digit The trading device identifies the selected trait. The digital transaction device of claim 8, wherein the DTC user interface includes a scroll button that allows a user to select a trait from the plurality of traits and the DTC user interface further includes a display indicating the selectable trait. The digital transaction device of claim 1, wherein the DTC includes a DTC external processor for receiving and storing the transmitted symbols. The digital transaction device of claim 1, wherein the DTC includes a display for displaying information. The digital transaction device of claim 1, wherein the DTPU is an EMV device according to one of firmware operations, wherein the firmware has been modified to enable the EMV device to receive and execute to allow writing of data to the EMV device during execution. One of the secure memory elements extends the set of commands. The digital transaction device of claim 14, wherein the writing of the data to the DTPU secure memory requires execution of a plurality of EMV device commands. The digital transaction device of claim 14, wherein the digital transaction device is connected to the entity of the contact terminal of the EMV device or by a contactless connection (ISO 14443 standard) or by being associated with the digital transaction device The interaction between the magnetic strip reader and one of the magnetic strips of the DTC interfaces with the EMV device. The digital transaction device of claim 16, wherein the DTC comprises a wristwatch, a wristband, a ring or a piece of jewelry. The digital transaction device of claim 16, wherein the digital transaction device is any one or more of a POS/EFTPOS terminal, an ATM, an internet connection computer, or a personal computer. The digital transaction device of claim 3, wherein the trait is any one or more of the following: a credit card; a financial card; a bank account; a stored value card; a passport; an identity card; a closed loop stored value card; a membership card; a library card; a mass transit card; a government agency card; a driver's license, or any other card used to identify the owner of the card or document or file. The digital transaction device of claim 1, wherein the DAD is any one or more of: a smart phone; a computer tablet; a laptop computer; a personal computer (PC); a wearable device, A smart watch is included; a FOB device; or any other processing device that includes a user interface and is operative to transmit instructions to a DTC. A data-assisted device (DAD) that can be paired with a DTC operation with a digital transaction card (DTC) receiver and a digital transaction processing unit (DTPU), and can be operated with a plurality of digits, each digit a digital transaction file associated with each digit transaction file associated with one or more digits, wherein each digit representation indicates a digitized transaction file associated with one of the digit transactions of the at least one digital transaction device The DAD includes: a user interface and a DAD transmitter, wherein the DAD is configured to store at least one of the plurality of digits in cooperation with the DTC such that the at least one token is stored in the DAD DTC, the DAD or both the DTC and the DAD, and wherein the DAD is configured to allow selection by the user to face one of the stored at least one digits and to transmit the selection to the The DTC is caused to enable the DTC to operate as the token associated digital transaction file represented by the selected digit. The DAD of claim 21, wherein the DAD further comprises a receiver. A digital transaction card (DTC) that can be paired with a DAD operation with a user interface and a data assist device (DAD) transmitter, and can be operated with a plurality of digits, each digit and a digital transaction file Associated, and each digit transaction file is associated with one or more digits, wherein each digit indicates a digitized transaction file associated with one of the digit transactions of the at least one digit transaction device, the DTC comprising : a DTC receiver and a digital transaction processing unit (DTPU), wherein the DTC is configured to store at least one of the plurality of digits in cooperation with the DAD such that the at least one token is stored in the DTC, the DAD, or both the DTC and the DAD, wherein the DTC is configured to accept data from the DAD transmission indicating that the selected one of the stored at least one digits is selected, and wherein the DTC is grouped The state is implemented to implement the selected digit, such that the DTC is enabled to operate as the token associated digital transaction file represented by the selected digit. The digital transaction card of claim 23, wherein the DTC further comprises a transmitter. A digital transaction device comprising: a data assist device (DAD) having a user interface and a DAD transmitter, the digital transaction device also including a digital transaction card (DTC) having a DTC receiver and a A digital transaction processing unit (DTPU), wherein the digital transaction device can be operated with a plurality of digits, each digit is associated with a digit transaction file, and each digit transaction file is associated with one or more digits. Wherein each of the digits indicates that the digitized transaction file is associated with one of the digit transactions of the at least one digital transaction device, the method comprising implementing a selected digit, such that the DTC is enabled for operation by the premises Selecting the digitizer indicates that the token is associated with the digit transaction file. The digital transaction method of claim 25, wherein the selection and transmission symbols comprise one or more instructions. The digital transaction method of claim 26, wherein the selecting and transmitting the token is related to the plurality of selectable traits and changing the current trait of the DTC to a selected trait comprises: by the DAD and by the DAD user interface The operation receives an instruction to change the current trait of the DTC to the selected trait; transmitting, by the DAD transmitter, data about the selected trait to the DTC receiver; and implementing the data in the DTC according to the data The change from the current trait to one of the selected traits is such that when the DTC is operated with a digital transaction device to effect a digital transaction, the digital transaction device identifies the selected trait. The method of claim 25, wherein the DTC includes a user interface including a home key and a scroll key, and the token selected and transmitted to the DTC is related to a plurality of selectable traits, the method further comprising : selecting, by the DTC user interface, one of the plurality of selectable traits and causing the DTC to subsequently adopt the selected trait. The digital transaction method of claim 28, wherein changing the current trait of the DTC to the selected trait comprises: changing, by the operation of the DTC user interface, the current trait of the DTC to one of the selected traits Or a plurality of instructions; and performing, in the DTC, a change from the current trait to the selected trait based on the one or more instructions such that when the DTC is operated with a digital transaction device to implement the digital transaction, the digit The trading device identifies the selected trait. The digital transaction method of any one of clauses 26 to 29, wherein the DTPU is an EMV device, and the changing from the current trait to the selected trait comprises writing the token for the selected trait To one of the EMV devices, the secure memory component is such that when an EMV device is activated, the EMV device reads the signature in the secure memory component, thereby causing the DTC to adopt the selected trait. The digital transaction method of claim 26, wherein the DTPU comprises one of the firmware EMV devices, the firmware causing the EMV device to be operative to receive and execute an extended set of commands, thereby enabling the EMV device to be implemented from the current The trait is the change to the selected trait. A method of operating a data assist device (DAD), comprising: selecting at least one token by a user interface of the DAD, and transmitting the selected token by a DAD transmitter associated with the DAD To a receiver associated with a digital transaction card (DTC) having a digital processing unit (DTPU); wherein upon subsequent use of the DTC to implement a digital transaction, the DTC operates in accordance with the selection and transmission of the token. A method of operating a digital transaction card (DTC), comprising: receiving at least one user selection token from a data assist device (DAD); implementing a digital transaction by the DTC, wherein the DTC is based on the user selection token operating. The method of claim 33, further comprising: receiving, by the DTC, one or more small applications, the one or more small applications having at least one token defining a trait to enable the DTC to use the at least one A trait that implements the information and/or instructions for the digital transaction. A computer readable medium storing one or more instructions that, when executed by one or more processors associated with a data assist device (DAD), cause the one or more processors to: Receiving, by a user interface of the DAD, a selected at least one token; and transmitting the selected token to a digital transaction card (DTC) having a digital transaction processing unit (DTPU) by a DAD transmitter Corresponding to one of the receivers; wherein when the DTC is subsequently used to implement a digital transaction, the DTC operates according to the selection and transmits a token. A computer readable medium storing one or more instructions that, when executed by one or more processors associated with a digital transaction card (DTC), cause the one or more processors to: A data assist device (DAD) receives a user selection token; and then implements a digital transaction, wherein the DTC operates in accordance with the user selection token. The computer readable medium of claim 36, wherein the instructions further cause the one or more processors to: receive one or more small applications, the one or more small applications having at least one trait defined to enable the DTC to The at least one trait is used to implement a transactional data and/or instruction. A method comprising: receiving a DTC configured to operate according to request item 1 or request item 23 from an issuer. A method comprising: issuing, by an issuer, a DTC configured to operate according to request item 1 or request item 23. A method, comprising: receiving, from an issuer, a DTC configured to operate according to a method as in claim 25 or request item 33. A method comprising: issuing, by an issuer, a DTC configured to operate in accordance with request item 25 or request item 33. A method comprising: issuing, by an issuer, an opcode comprising a software and/or firmware to a data assist device (DAD) and/or a digital transaction card (DTC) to enable the DAD and/or DTC to be requested Item 1 operation. A method comprising: issuing, by an issuer, an opcode comprising a software and/or firmware to a data assist device (DAD) and/or a digital transaction card (DTC) to enable the DAD and/or DTC to be requested Item 25 operation.