# US 12,192,346 B2 · Enhanced security in sensitive data transfer over a network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,192,346 B2
- Document ID: US12192346B2
- Status: Granted
- Kind: B2
- Application number: 18/118,107
- Filed: 2023-03-06
- Published: 2023-06-29
- Granted: 2025-01-07
- Earliest claimed: 2019-10-18
- Assignees: Mastercard International Incorporated
- Applicants: Mastercard International Incorporated
- Inventors: Christopher Eggimann; Manu Dharmaiah Kallugudde
- Web page: https://patentgrep.com/patent/US12192346B2

## CPC

- G06Q 20/12: specially adapted for electronic shopping systems
- H04L 9/0863: {involving passwords or one-time passwords (network architectures or network communication protocols for using one-time keys in a packet data network H04L63/067)}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The present disclosure relates to a computer-implemented method and to a system for authenticating a transaction over a secure network. The method comprises, prior to authorization of a transaction: receiving, by a digital service server, from a merchant plug-in (MPI) computing device, via a directory server, a token and a first cryptogram for the transaction; decrypting, by the digital service server, the token into sensitive data; generating, by the digital service server, a first message including a validation result and the sensitive data; and transmitting, by the digital service server, the first message to an issuer server to authenticate the transaction.

## Claims

### Claim 1

A computer-implemented method for authenticating a transaction over a secure network, the method comprising:
prior to authorization of a transaction:
receiving, by a digital service server, from a merchant plug-in (MPI) computing device, via a directory server, a token and a first cryptogram for the transaction, the first cryptogram unique to the transaction; and then decrypting, by the digital service server, the token into sensitive data;
diversifying, by the digital service server, a master key from an issuer master symmetric key, which is specific to an issuer;
diversifying, by the digital service server, one or more session keys from the diversified master key based on an application transaction count (ATC);
validating, by the digital service server, the first cryptogram, based on the one or more diversified session keys; and then
based on the first cryptogram being validated:
incrementing, by the digital service server, the ATC; and
generating, by the digital service server, a first message including a validation result and the sensitive data; and then
transmitting, by the digital service server, the first message to an issuer server of the issuer to authenticate the transaction.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the validation result includes a first verification value indicative of successful validation of the first cryptogram.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, further comprising:
validating, by the digital service server, the token; and
wherein the validation result includes a second verification value indicative of successful validation of the token.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, further comprising:
receiving, by the MPI computing device, from a computing device associated with a customer, the sensitive data and the first cryptogram;
generating, by the MPI computing device, the token for the sensitive data; and
transmitting, by the MPI computing device, an authentication request to the digital service server, via the directory server, the authentication request including the token and the first cryptogram, but not the sensitive data.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4, wherein the sensitive data includes an account number and one or more of: a customer name, a customer address, a merchant name, and/or a merchant address.

### Claim 6 (depends on 4)

The computer-implemented method of claim 4, further comprising:
receiving, by the MPI computing device, based on the first message, an authentication value from the issuer server, via the directory server; and
transmitting, by the MPI computing device, the authentication value and the token to the issuer server.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, wherein the authentication value further includes one or more of: a directory service nonce (DSN), a log amount for the transaction, a truncated hash of a merchant ID for a merchant involved in the transaction, and/or a currency code.

### Claim 8

A system for authenticating a transaction on a secure network, the system comprising:
a digital service server including a first processor and a first non-transitory memory, the first non-transitory memory including first executable instructions, which, when executed by the first processor, cause the first processor to:
prior to authorization of a transaction:
receive, from a merchant plug-in (MPI) computing device, via a directory server, a token and a first cryptogram for the transaction, the first cryptogram unique to the transaction; and then
decrypt the token into sensitive data;
diversify a master key from an issuer master symmetric key, which is specific to an issuer;
diversify one or more session keys from the diversified master key, based on an application transaction count (ATC);
validate the first cryptogram, based on the one or more diversified session keys; and then
based on the first cryptogram being validated:
increment the ATC; and
generate a first message including a validation result and the sensitive data; and then
transmit the first message to an issuer server to authenticate the transaction.

### Claim 9 (depends on 8)

The system of claim 8, wherein the validation result includes a first verification value indicative of successful validation of the first cryptogram.

### Claim 10 (depends on 9)

The system of claim 9, wherein the first executable instructions, when executed by the first processor, further cause the first processor to validate the token; and
wherein the validation result includes a second verification value indicative of successful validation of the token.

### Claim 11 (depends on 8)

The system of claim 8, further comprising the MPI computing device, which includes a second processor and a second non-transitory memory, the second non-transitory memory including second executable instructions, which, when executed by the second processor, cause the second processor to:
receive the sensitive data and the first cryptogram;
generate the token for the sensitive data; and
transmit an authentication request to the digital service server, via the directory server, the authentication request including the token and the first cryptogram, but not the sensitive data.

### Claim 12 (depends on 11)

The system of claim 11, wherein the sensitive data includes an account number and one or more of: a customer name, a customer address, a merchant name, and/or a merchant address.

### Claim 13 (depends on 11)

The system of claim 11, wherein the second executable instructions, when executed by the second processor, further cause the second processor to:
receive an authentication value, which is based on the first message, from the issuer server, via the directory server; and
transmit the authentication value and the token to the issuer server.

### Claim 14 (depends on 13)

The system of claim 13, wherein the authentication value further includes one or more of: a directory service nonce (DSN), a log amount for the transaction, a truncated hash of a merchant ID for a merchant involved in the transaction, and/or a currency code.