# US 2025/0097023 A1 · 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 2025/0097023 A1
- Document ID: US20250097023A1
- Status: Published application
- Kind: A1
- Application number: 18/962,229
- Filed: 2024-11-27
- Published: 2025-03-20
- 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/US20250097023A1

## 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; and then decrypting, by the digital service server, the token into sensitive data; and validating, by the digital service server, the first cryptogram, based on one or more session keys; and then, based on the first cryptogram not being validated: setting a validation flag to a defined value indicating that the first cryptogram is not valid; and sending, to a user device of a user, an authentication request message, as an authentication step-up, to verify the user and the authenticity of 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; and
validating, by the digital service server, the first cryptogram, based on one or more session keys; and then
based on the first cryptogram not being validated:
setting a validation flag to a defined value indicating that the first cryptogram is not valid; and
sending, to a user device of a user, an authentication request message, as an authentication step-up, to verify the user and the authenticity of the transaction.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, further comprising:
diversifying, by the digital service server, a master key from an issuer master symmetric key, which is specific to an issuer; and
diversifying, by the digital service server, one or more session keys from the diversified master key based on an application transaction count (ATC), the one or more session keys including the one or more diversified session keys.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, further comprising, based on a response to the authentication request message not being received from the user for a predetermined amount time, rejecting, by an issuer server of an issuer, the transaction.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, further comprising, based on a response to the authentication request message not being received from the user after a number of attempts, rejecting, by an issuer server of an issuer, the transaction.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, further comprising:
based on a response to the authentication request message being received:
generating, by an issuer server of an issuer, a first message including a validation result and the sensitive data; and
transmitting, by the issuer server, the first message to MPI computing device.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5, wherein the validation result includes the defined value indicating that the first cryptogram is not valid.

### Claim 7 (depends on 6)

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

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, further comprising:
receiving, by the MPI computing device, from the user device, 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 9 (depends on 8)

The computer-implemented method of claim 8, 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 10

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; and
validate the first cryptogram, based on one or more session keys; and
an issuer server computing device coupled in communication with the digital service server, via a network, the issuer server computing device including 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, based on the first cryptogram not being validated:
set a validation flag to a defined value indicating that the first cryptogram is not valid; and
send, to a user device of a user, an authentication request message, as an authentication step-up, to verify the user and the authenticity of the transaction.

### Claim 11 (depends on 10)

The system of claim 10, wherein the first executable instructions, when executed by the first processor, cause the first processor to:
diversify a master key from an issuer master symmetric key, which is specific to an issuer; and
diversify one or more session keys from the diversified master key, based on an application transaction count (ATC).

### Claim 12 (depends on 10)

The system of claim 10, wherein the second executable instructions, when executed by the second processor, cause the second processor to reject the transaction based on a response to the authentication request message not being received, for a predetermined amount time, from the user.

### Claim 13 (depends on 10)

The system of claim 10, wherein the second executable instructions, when executed by the second processor, cause the second processor to reject the transaction based on a response to the authentication request message not being received, after a number of attempts, from the user.

### Claim 14 (depends on 10)

The system of claim 10, wherein the second executable instructions, when executed by the second processor, cause the second processor to, based on a response to the authentication request message being received:
generate a first message including a validation result and the sensitive data; and
transmit the first message to the MPI computing device.

### Claim 15 (depends on 14)

The system of claim 14, wherein the validation result includes the defined value indicating that the first cryptogram is not valid.

### Claim 16 (depends on 10)

The system of claim 10, further comprising:
the MPI computing device, the MPI computing device including a third processor and a third non-transitory memory, the third non-transitory memory including third executable instructions, which, when executed by the third processor, cause the third processor to:
receive, from the user device, 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 17 (depends on 16)

The system of claim 16, 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 18 (depends on 16)

The system of claim 16, wherein the third executable instructions, when executed by the third processor, further cause the third processor to:
receive an authentication value from the issuer server, via the directory server; and
transmit the authentication value and the token to the issuer server.
