# US 2020/0202335 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 2020/0202335 A1
- Document ID: US20200202335A1
- Status: Published application
- Kind: A1
- Application number: 16/808,783
- Filed: 2020-03-04
- Published: 2020-06-25
- 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/US20200202335A1

## 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 1

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:
receiving cardholder data (CHD) from a first user associated with a first entity;
generating a token corresponding to the CHD;
generating an authorization factor for the token and providing the first user with access to the authorization factor;
receiving a request from a second user to access the token, the second user associated with a second entity differing from the first entity, the request including an authorization factor input;
determining whether the second user is authorized to access the token by at least comparing the authorization factor input to the authorization factor to determine whether the second user is authorized to access the token;
in response to determining that the second user is authorized to access the token, providing the second user with access to the token, wherein providing the second user with access to the token comprises performing a transaction using the CHD associated with the token on behalf of the second user without providing the second user with access to the CHD; and
in response to a triggering event, removing access to the token from the second user by disassociating the token with the second user.

### Claim 2 (depends on 1)

The method of claim 1, wherein the authorization factor comprises a set of words that is associated with the token, the set of words unique to the token.

### Claim 3 (depends on 1)

The method of claim 1, further comprising authenticating the second user prior to receiving the request from the second user to access the token.

### Claim 4 (depends on 1)

The method of claim 1, wherein determining whether the second user is authorized to access the token further comprises determining whether the first user has authorized the second user to access tokens associated with the first user.

### Claim 5 (depends on 1)

The method of claim 1, wherein the triggering event comprises at least one of: receiving a command; the token being accessed a particular number of times; or a time period associated with the token expiring.

### Claim 6 (depends on 1)

The method of claim 1, further comprising disassociating the authorization factor from the token in response to the triggering event.

### Claim 7 (depends on 1)

The method of claim 1, wherein the tokenization provider system is associated with or managed by the first entity.

### Claim 8 (depends on 1)

The method of claim 1, wherein the first entity corresponds to a first merchant environment and the second entity corresponds to a second merchant environment.

### Claim 9 (depends on 1)

The method of claim 1, wherein, in response to determining that the second user is authorized to access the token, the method further comprises:
receiving a transaction request associated with the second user, the transaction request associated with the transaction; and
performing the transaction based on the transaction request.

### Claim 10 (depends on 1)

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

### Claim 11 (depends on 1)

The method of claim 1, wherein the CHD corresponds to a customer of the first entity.

### Claim 12 (depends on 1)

The method of claim 1, further comprising providing the token to the first entity to be stored as a substitute for storage of the CHD at the first entity.

### Claim 13 (depends on 1)

The method of claim 1, wherein providing the authorization factor to the first user comprises emailing the authorization factor to the first user or presenting the authorization factor to the first user via an Internet-based portal.

### Claim 14 (depends on 1)

The method of claim 1, wherein the token comprises random or pseudo-random data that is storable as a substitute for CHD.

### Claim 15 (depends on 1)

The method of claim 1, wherein a value of the token does not correlate to contents of the CHD.

### Claim 16 (depends on 1)

The method of claim 1, further comprising storing a relationship between the token and the CHD at a repository of the tokenization provider system.

### Claim 17 (depends on 1)

The method of claim 1, wherein the token is one of a plurality of tokens associated with the CHD, and wherein at least one token from the plurality of tokens is associated with a different user than at least one other token from the plurality of tokens.

### Claim 18 (depends on 1)

The method of claim 1, wherein the request from the second user to access the token comprises an identity of the token and a set of transaction details associated with the transaction.

### Claim 19 (depends on 1)

The method of claim 1, wherein the request from the second user is received from a point-of-sale system of the second entity.

### Claim 20 (depends on 1)

The method of claim 1, further comprising replacing the token with a second token in response to detecting an unauthorized attempt to access the token.
