# US 2023/0245104 A1 · Method and system for enabling merchants to share tokens

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

- Number: US 2023/0245104 A1
- Document ID: US20230245104A1
- Status: Published application
- Kind: A1
- Application number: 18/075,252
- Filed: 2022-12-05
- Published: 2023-08-03
- Earliest claimed: 2011-04-15
- Assignees: Shift4 Corporation
- Applicants: Shift4 Corporation
- Inventors: Kevin James Cronic; Steven Mark Sommers; John David Oder, II; John David Oder; Steven Calandrelli; Jeremy B. Fried
- Web page: https://patentgrep.com/patent/US20230245104A1

## CPC

- G06Q 20/3674: {involving authentication}
- G06Q 20/0855: {involving a third party}
- G06Q 20/24: Credit schemes, i.e. "pay after"
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/4014: {Identity check for transactions}
- 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

One embodiment of the present disclosure provides a system and associated processes for sharing cardholder data (CHD) between a merchant that utilizes tokenization and a second merchant that may or may not utilize tokenization. In one embodiment, the merchant, or an employee of the merchant, can use the system and associated processes to reacquire CHD from a tokenization provider system. In one embodiment, the merchant identifies to the tokenization provider system a desire to share CHD, which is associated with a token, with a second merchant. The merchant and/or the tokenization provider system can then invite the second merchant to register with the tokenization provider system. Once registered with the tokenization provider system, the second merchant can access any CHD that the merchant associated with the second merchant.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A method for sharing a token at a third-party system associated with cardholder data to enable the sharing of access to the cardholder data between users, the method comprising:
by a tokenization provider system comprising one or more hardware processors:
generating a token corresponding to cardholder data (CHD), wherein the tokenization provider system stores the token and the CHD;
generating an authorization factor for the token and associating the authorization factor with the token;
receiving an input from a first computing system;
determining that the input corresponds to the authorization factor;
determining that the first computing system is authorized to access the token in a data store of the tokenization provider system based on receiving the input from the first computing system and determining that the input corresponds to the authorization factor;
in response to determining that the first computing system is authorized to access the token, providing the first computing system with access to the token; and
based on providing the first computing system with access to the token, performing a transaction, on behalf of the first computing system, using the CHD without providing the first computing system with access to the CHD.

### Claim 22 (depends on 21)

The method of claim 21, the method further comprising receiving the CHD from a second computing system.

### Claim 23 (depends on 21)

The method of claim 21, the method further comprising:
receiving the CHD from a second computing system; and
monitoring access to the token of at least one of the first computing system or the second computing system.

### Claim 24 (depends on 21)

The method of claim 21, wherein the tokenization provider system provides limited access to the token.

### Claim 25 (depends on 21)

The method of claim 21, wherein the first computing system is associated with a user, and wherein determining that the first computing system is authorized to access the token comprises determining that the user is authorized to access the token.

### Claim 26 (depends on 21)

The method of claim 21, wherein the first computing system is associated with a user, and wherein providing the first computing system with access to the token comprises associating the token with at least one of the user or the first computing system.

### Claim 27 (depends on 21)

The method of claim 21, wherein providing the first computing system with access to the token comprises associating a first token with the first computing system, the method further comprising:
receiving a second token or an identifier of the second token from the first computing system; and
authenticating the first computing system based on comparing the second token or the identifier of the second token to the first token.

### Claim 28 (depends on 21)

The method of claim 21, further comprising:
obtaining registration information from the first computing system; and
verifying an identity associated with the first computing system based on the registration information, wherein determining that the first computing system is authorized to access the token is further based on verifying the identity.

### Claim 29 (depends on 21)

The method of claim 21, wherein the first computing system is associated with a user, and wherein the method further comprises authenticating the user.

### Claim 30 (depends on 21)

The method of claim 21, further comprising authenticating the first computing system prior to receiving the input from the first computing system.

### Claim 31 (depends on 21)

The method of claim 21, wherein the authorization factor comprises text, a number, an image, a sound, or a challenge.

### Claim 32 (depends on 21)

The method of claim 21, wherein the first computing system is associated with a first user, the method further comprising receiving the CHD from a second computing system associated with a second user, and wherein determining that the first computing system is authorized to access the token comprises determining that at least one of:
the second computing system has authorized the first computing system to access tokens associated with the second computing system; or
the second user has authorized the first user to access tokens associated with the second user.

### Claim 33 (depends on 21)

The method of claim 21, wherein providing the first computing system with access to the token comprises associating a first token with the first computing system, the method further comprising:
receiving a second token or an identifier of the second token from the first computing system;
authenticating the first computing system based on comparing the second token or the identifier of the second token to the first token; and, the method further comprising,
in response to a triggering event, removing access to the token from the first computing system by disassociating the token with the first computing system.

### Claim 34 (depends on 21)

The method of claim 21, wherein determining that the input corresponds to the authorization factor comprises:
comparing the input to the authorization factor; and
determining that the input corresponds to the authorization factor based on comparing the input to the authorization factor.

### Claim 35

A tokenization provider system comprising:
a memory circuit storing computer-executable instructions; and
a hardware processor configured to execute the computer-executable instructions, wherein execution of the computer-executable instructions causes the hardware processor to:
generate a token corresponding to cardholder data (CHD), wherein the tokenization provider system stores the token and the CHD;
generate an authorization factor for the token and associating the authorization factor with the token;
receive an input from a first computing system;
determine that the input corresponds to the authorization factor;
determine that the first computing system is authorized to access the token in a data store of the tokenization provider system based on receiving the input from the first computing system and determining that the input corresponds to the authorization factor;
in response to determining that the first computing system is authorized to access the token, provide the first computing system with access to the token; and
based on providing the first computing system with access to the token, perform a transaction, on behalf of the first computing system, using the CHD without providing the first computing system with access to the CHD.

### Claim 36 (depends on 35)

The tokenization provider system of claim 35, wherein execution of the computer-executable instructions further causes the hardware processor to:
receive the CHD from a second computing system; and
receive registration information associated with the first computing system from the second computing system.

### Claim 37 (depends on 35)

The tokenization provider system of claim 35, wherein execution of the computer-executable instructions further causes the hardware processor to:
receive the CHD from a second computing system;
receive registration information associated with the first computing system from the second computing system; and
authenticate the first computing system based on the registration information.

### Claim 38 (depends on 35)

The tokenization provider system of claim 35, wherein execution of the computer-executable instructions further causes the hardware processor to:
receive the CHD from a second computing system;
receive registration information associated with the first computing system from the second computing system; and
associate the first computing system with the token based on the registration information.

### Claim 39 (depends on 35)

The tokenization provider system of claim 35, wherein execution of the computer-executable instructions further causes the hardware processor to:
receive the CHD from a second computing system;
receive registration information associated with the first computing system from the second computing system;
associate the first computing system with the token based on the registration information; and
disassociate a third computing system with the token.

### Claim 40

A tokenization provider device comprising:
a memory circuit storing computer-executable instructions; and
a hardware processor configured to execute the computer-executable instructions, wherein execution of the computer-executable instructions causes the hardware processor to:
generate a token corresponding to cardholder data (CHD), wherein the tokenization provider device stores the token and the CHD;
generate an authorization factor for the token and associating the authorization factor with the token;
receive an input from a first computing device associated with a first user;
determine that the input corresponds to the authorization factor;
determine that the first user is authorized to access the token in a data store of the tokenization provider device based on receiving the input from the first computing device and determining that the input corresponds to the authorization factor;
in response to determining that the first user is authorized to access the token, provide the first user with access to the token; and
based on providing the first user with access to the token, perform a transaction, on behalf of the first user, using the CHD without providing the first user with access to the CHD.
