Transaction application with a tokenized identifier

Abstract

A Digital Transaction Processing Unit (DTPU) including a plurality of transaction applications operable for a digital transaction with a Digital Transaction Device (DTD), each of the plurality of transaction applications being associated with a tokenised primary identifier.

Description

CROSS REFERENCE TO RELATED APPLICATIONS[0001]Continuation of International Application No. PCT / AU2020 / 050302 filed on Mar. 27, 2020. Priority is claimed from Australian Application No. 2019901029 filed on Mar. 27, 2019. Both the foregoing applications are incorporated herein by reference in their entirety.STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT[0002]Not Applicable.NAMES OF THE PARTIES TO A JOINT RESEARCH AGREEMENT[0003]Not Applicable.FIELD OF THE INVENTION[0004]The present invention relates generally to digital payment devices (DPDs). In at least some embodiments, the invention relates to methods of configuring or operating DPDs.[0005]In at least some embodiments, the invention may have application to DPDs capable of hosting credit cards, debit cards, mobile payment cards or non-payment cards and / or documents (including licences, ID cards, passports, and the like). In at least some embodiments, the invention may also have applications to DPDs which operate in...

AI Technical Summary

Benefits of technology

[0150]In embodiments of the present invention and/or in embodiments of its related technologies, the MCU operates with low power consumption to assist in providing longer battery life for the DPD (if having an optional battery). In embodiments of the present invention and/or in embodiments of its related technologies, the MCU is operable to accept provisioning from one or more of a DPD manager, a TSM, and a TSP (synchronously, asynchronously or sele

Problems solved by technology

Such non-payment transaction SEs are usually not operable for hosting EMVCo compliant applications.

Security of payment transactions is a major concern as there have been many instances of fraudulent transaction with stolen physical cards/documents or stolen physical or digital card/document details.

Credit/debit cards may also have a CVV (or CVC on the magnetic stripe) to make it more difficult to replicate a card for fraudulent purposes.

If the counter value is incorrect, the derived session key will be incorrect, and the setup of the secure session will fail.

Further, if the script is encrypted, an incorrect session key will not allow decryption.

However, the Plastc solution had operational limitations, and the Wocket solution requires a specific Wocket device.

None of these solutions has gained wide market acceptance, and some have now closed or ceased operating.

One serious problem causing failure of such prior solutions is not attaining certification from organizations, such as EMVCo, and thus are unsuited to operate with the corresponding payment schemes requiring EMVCo certification and the DTDs in a payment network, which also require compliance with EMVCo standards.

Another problem facing such proposals is that the Service Code includes a requirement that a particular kind of chip is present, and the DTD must request that this type of chip is used, however, as these cards have only a copy of the magnetic stripe (the magnetic stripe card), the required type chip is not present, which will cause transactions to fail.

Further, such proposals do not work because issuer (who owns the cardholders' data) cannot be convinced that:the ISD keys and SSDs of the chip are tightly controlled by the issuer only or an agreed agent of the issuer;the issuer can use their SSD key (key rotation);the card meets all the finance standards;the card Is capable of holding the issuers data and is able to securely generate issuer cryptograms;the proposed cards are capable of having the data installed in a secure personalisation bureau facility to the issuer's specifications; and,the lifecycle of the SE altered by the personalisation bureau is locked to any other changes.

In contrast, a scheme container for a SE of a chipped card is limited to the matching of the issued scheme of the single digital card to the scheme's container, wherein all other containers installed on the SE and not containing the matched digital card are disabled or locked after the personalization process.

Many other operations available to Perso Bureaus and TSMs are not available to others.

This can be difficult if the user is not in a location where a communication link to the TSM can be established.

Notably, SEs (or finance chips) on chipped cards do not have a CASD installed.

Despite the apparent convenience of digital wallets, each MPC in a digital wallet c

Images