Transaction messaging

Patent metadata

Field	Value
Publication number	US-12051064-B2
Application number	US-202016991386-A
Country	US
Kind code	B2
Filing date	Aug 12, 2020
Priority date	Oct 24, 2014
Publication date	Jul 30, 2024
Grant date	Jul 30, 2024

Abstract

There is described a method for transmitting a transaction message from a transaction device having a transaction device identifier. The method involves encrypting, at a transaction device, a transaction device identifier, generating, at the transaction device, a transaction message for a transaction system, the transaction message comprising, at least, a first data field configured to hold a transaction device identifier and a second data field configured to hold supplementary data, and sending the transaction message to a transaction processing system. The generation of the transaction message comprises providing data in the first data field of the transaction message that does not identify the transaction device and providing the encrypted transaction device identifier in the second data field of the transaction message.

First claim

What is claimed is:

1. A method comprising:
generating, at a transaction device, a public cryptographic key for the transaction device to use in a transaction, by using a transaction device identifier that identifies the transaction device and transaction data associated with the transaction;
generating, at the transaction device, a shared secret using the public cryptographic key and a transaction server public key of a transaction processing server included in a transaction processing system;
encrypting, at the transaction device, the transaction device identifier using the shared secret;
generating, at the transaction device, a transaction message for a transaction system, wherein the transaction message is formatted according to an EMV standard and comprises a plurality of data fields comprising a first data field that, according to the EMV standard, is specified to hold the transaction device identifier, and a second data field that, according to the EMV standard, is specified to hold supplementary data,
wherein the generating the transaction message further comprises:
generating, at the transaction device, a temporary transaction device identifier which does not identify the transaction device,
inserting the temporary transaction device identifier in the first data field of the transaction message in place of the transaction device identifier,
inserting the encrypted transaction device identifier, which is encrypted using the shared secret, in the second data field of the transaction message,
inserting the public cryptographic key of the transaction device in a third data field of the transaction message among the plurality of data fields, and
inserting the transaction data in a fourth data field of the transaction message among the plurality of data fields; and

sending the transaction message to the transaction processing system that (i) decrypts the encrypted transaction device identifier located in the second data field using the shared secret recreated using the received public cryptographic key of the transaction device and a transaction server private key that corresponds to the transaction server public key, and (ii) validates the received transaction data using the decrypted transaction device identifier.

2. The method of claim 1 , wherein the public cryptographic key is generated at least in part using further data different from the transaction device identifier.

3. The method of claim 2 , wherein the public cryptographic key is generated further using a value uniquely associated with the transaction device identifier.

4. The method of claim 2 , further comprising receiving the further data from the transaction processing system.

5. The method of claim 2 , wherein, for a given transaction, at least part of the further data is specific to the given transaction.

6. The method of claim 1 , wherein the generating the temporary transaction device identifier further comprises:
generating the temporary transaction device identifier at least in part using further data, which is different from the transaction device identifier.

7. The method of claim 1 , wherein the transaction device identifier comprises data indicative of a primary account number of a financial instrument.

8. The method of claim 1 , wherein the transaction device identifier is a data element configured to convey information of a primary account number (PAN) of a financial instrument to be used in the transaction, and wherein the first data field is specified by the EMV standard to hold the data element.

9. A transaction device comprising:
a processor; and
a memory storing computer-readable code, which, when executed by the processor, causes the transaction device to perform operations including:
generating a public cryptographic key for the transaction device to use in a transaction, by using a transaction device identifier that identifies the transaction device and transaction data associated with the transaction;
generating a shared secret using the public cryptographic key and a transaction server public key of a transaction processing server included in a transaction processing system;
encrypting the transaction device identifier using the shared secret;
generating a transaction message for a transaction system, wherein the transaction message is formatted according to an EMV standard and comprises a plurality of data fields comprising a first data field that, according to the EMV standard, is specified to hold the transaction device identifier, and a second data field that, according to the EMV standard, is specified to hold supplementary data,
wherein the generating the transaction message further includes:
generating a temporary transaction device identifier which does not identify the transaction device,
inserting the temporary transaction device identifier in the first data field of the transaction message in place of the transaction device identifier,
inserting the encrypted transaction device identifier, which is encrypted using the shared secret, in the second data field of the transaction message,
inserting the public cryptographic key of the transaction device in a third data field of the transaction message among the plurality of data fields, and
inserting the transaction data in a fourth data field of the transaction message among the plurality of data fields; and

sending the transaction message to the transaction processing system that (i) decrypts the encrypted transaction device identifier located in the second data field using the shared secret recreated using the received public cryptographic key of the transaction device and a transaction server private key that corresponds to the transaction server public key, and (ii) validates the received transaction data using the decrypted transaction device identifier.

10. The transaction device of claim 9 , wherein the public cryptographic key is generated at least in part using further data different from the transaction device identifier.

11. The transaction device of claim 10 , wherein the public cryptographic key is generated further using a value uniquely associated with the transaction device identifier.

12. The transaction device of claim 10 , wherein the operations further include receiving the further data from the transaction processing system.

13. The transaction device of claim 10 , wherein, for a given transaction, at least part of the further data is specific to the given transaction.

14. The transaction device of claim 9 , wherein the generating the temporary transaction device identifier further includes:
generating the temporary transaction device identifier at least in part using further data, which is different from the transaction device identifier.

15. The transaction device of claim 9 , wherein the transaction device identifier comprises data indicative of a primary account number of a financial instrument.

Assignees

• Visa Europe Ltd

Inventors

• Sullivan Brian

Classifications

• G06Q20/401

  Transaction verification · CPC title

• G06Q20/3278

  RFID or NFC payments by means of M-devices · CPC title

• G06Q20/385

  using an alias or single-use codes · CPC title

• G06Q20/3825

  Use of electronic signatures · CPC title

• G06Q20/3227 Primary

  using secure elements embedded in M-devices · CPC title