# US 2021/0176060 A1 · Secure Data Transfer

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

- Number: US 2021/0176060 A1
- Document ID: US20210176060A1
- Status: Published application
- Kind: A1
- Application number: 17/111,324
- Filed: 2020-12-03
- Published: 2021-06-10
- Earliest claimed: 2019-12-04
- Assignees: Mastercard International Incorporated
- Applicants: Mastercard International Incorporated
- Inventors: Manu Dharmaiah Kallugudde
- Web page: https://patentgrep.com/patent/US20210176060A1

## CPC

- 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 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- 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

## Abstract

The present invention discloses a method of processing a data transfer request securely over a network, the method comprising the steps of obtaining, by a first entity, a first token associated with sensitive data received from a user; associating the first token with a token reference and storing the token reference; sending the token reference to a second entity; requesting a second token from a second entity upon receiving a data transfer request from a third entity, wherein the second token is derived from the first token using an ad hoc logic; and processing the data transfer request using the second token.

## Claims

### Claim 1

A method of processing a data transfer request securely over a network, the method comprising the steps of:
obtaining, by a first entity, a first token associated with sensitive data received from a user;
associating the first token with a token reference and storing the token reference;
sending the token reference to a second entity;
requesting a second token from a second entity upon receiving a data transfer request from a third entity, wherein the second token is derived from the first token using an ad hoc logic; and
processing the data transfer request using the second token.

### Claim 2 (depends on 1)

The method of claim 1, further comprises requesting a cryptogram from the second entity when requesting the second token.

### Claim 3 (depends on 2)

The method of claim 2, further comprising the steps of:
sending, by the first entity, the second token and the cryptogram over a public network;
validating, by the second entity, the second token and the cryptogram received over the public network;
detokenizing, by the second entity, the second token to retrieve the sensitive data; and
sending, by the second entity, the sensitive data to a fourth entity configured to approve the data transfer request.

### Claim 4 (depends on 3)

The method of claim 3, wherein the fourth entity is configured to optionally authenticate the user before approving the data transfer request.

### Claim 5 (depends on 2)

The method of claim 2, further comprises sending, by the fourth entity, a confirmation of approval of the data transfer request to the first entity and/or the third entity.

### Claim 6 (depends on 1)

The method of claim 1, wherein the second token comprises data transmitted in an electronic message having a card number, an expiry date and a CVV field.

### Claim 7 (depends on 1)

The method of claim 1, wherein the ad hoc logic comprises splitting the first token into three parts and masking at least two of the three parts to generate the second token.

### Claim 8 (depends on 1)

The method of any preceding claim 1, wherein the second entity is configured to store the ad hoc logic and update it each time the second token is generated.

### Claim 9 (depends on 1)

The method of claim 1, wherein the second token has a predefined expiry period.

### Claim 10 (depends on 1)

The method of claim 1, further comprising the second entity verifying credentials of the first entity before issuing the second token.

### Claim 11

A system for processing a data transfer request securely over a network, the system comprising a first entity configured to:
generate a first token associated with sensitive data received from a user;
associate the first token with a token reference and store the token reference;
send the token reference to a second entity;
request a second token from a second entity upon receiving a data transfer request from the user, the second token has been derived from the first token using an ad hoc logic; and
process the data request using the second token.

### Claim 12 (depends on 11)

The system of claim 11, wherein the first entity is further configured to receive a cryptogram and the second token from the second entity, and to send the second token and the cryptogram over a public network.

### Claim 13 (depends on 11)

The system of claim 11, wherein the first entity is a merchant and the second entity is a tokenization platform.

### Claim 14 (depends on 11)

The system of claim 11, wherein the data transfer request is a payment transaction between a merchant and a user.
