US 10,515,356 B2Granted

Method and system for utilizing authorization factor pools

AssigneeShift4 Corporation

InventorsKevin James Cronic, Steven Mark Sommers, John David Oder, II, John David Oder, Steven Calandrelli, Jeremy B. Fried

Life of this patent

Estimating the term…

patentgrep

Loading patent…

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.

Claims11

Dependent claims

A system for accessing a token associated with cardholder data (CHD) to enable performing a transaction with the CHD, the system comprising:

a token access system comprising computer hardware, the token access system configured to:
receive an authorization factor from a third-party merchant, wherein the authorization factor comprises a set of one or more values associated with the token, and wherein the set of one or more values are not derived from the token, wherein the third-party merchant comprises a merchant that did not receive the CHD from a cardholder associated with the CHD, and wherein the third-party merchant received the authorization factor from a merchant that did receive the CHD from the cardholder and desires to share access to the token associated with the CHD with the third-party merchant enabling the third-party merchant to perform a transaction for the cardholder on behalf of the merchant that received the CHD from the cardholder;
identify an authorization factor pool associated with the authorization factor, wherein the authorization factor pool is one of a plurality of authorization factor pools;
identify a tokenization provider system associated with the authorization factor pool, wherein the tokenization provider system is one of a plurality of tokenization provider systems and wherein each authorization factor pool is associated with one tokenization provider system of the plurality of tokenization provider systems;
identify a token associated with the authorization factor at the tokenization provider system, wherein the token comprises a unique value that serves as a substitute for the CHD, and wherein the token cannot be processed to determine the CHD from the token itself;
and
enable the third-party merchant to perform a transaction with the CHD associated with the token without receiving the CHD from the cardholder associated with the CHD by providing the third-party merchant with access to the token associated with the authorization factor.

4 more elements

A method of accessing a token associated with cardholder data (CHD) to enable performing a transaction with the CHD, the method comprising:

by a token access system implemented in a computing system comprising one or more processors, the token access system associated with a plurality of tokenization provider systems:
receiving an authorization factor from a third-party merchant, wherein the authorization factor comprises a set of one or more values associated with the token, and wherein the set of one or more values are not derived from the token, wherein the third-party merchant comprises a merchant that did not receive the CHD from a cardholder associated with the CHD, and wherein the third-party merchant received the authorization factor from a merchant that did receive the CHD from the cardholder and desires to share access to the token associated with the CHD with the third-party merchant enabling the third-party merchant to perform a transaction for the cardholder on behalf of the merchant that received the CHD from the cardholder;
identifying an authorization factor pool associated with the authorization factor, wherein the authorization factor pool is one of a plurality of authorization factor pools;
identifying a tokenization provider system associated with the authorization factor pool, wherein the tokenization provider system is one of the plurality of tokenization provider systems;
identifying a token associated with the authorization factor at the tokenization provider system, wherein the token comprises a unique value that serves as a substitute for the CHD, and wherein the token cannot be processed to determine the CHD from the token itself;
determining that the third-party merchant is authorized to access the token;
and
providing the third-party merchant with access to the token associated with the authorization factor to enable the third-party merchant to perform a transaction with the CHD associated with the token without receiving the CHD from the cardholder associated with the CHD.

5 more elements

Dependencies are inferred from the claim text.

Facts

Application: 13/941,282Filed 12 Jul 2013 · division
Priority: 15 Apr 2011
Published: US 2013/0191289 A114 Nov 2013
Granted: 24 Dec 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification7 codes

G06Q 20/382
Payment protocols; Details thereof: insuring higher security of transaction
G06Q 20/0855
Involving remote charge determination or related payment systems: involving a third party
G06Q 20/24
Payment schemes or models: credit schemes, i.e. "pay after"
G06Q 20/3821
Insuring higher security of transaction: electronic credentials

Family

Application61/476,194Us provisional application · filed 15 Apr 2011
Application13/303,983Parent of this continuation-in-part · filed 23 Nov 2011
Application61/621,222Us provisional application · filed 6 Apr 2012
Application61/714,959Us provisional application · filed 17 Oct 2012
Application13/797,246Parent of this division · filed 12 Mar 2013
US 2013/0304649 A1Pre-grant publication · published 14 Nov 2013
US 8,688,589 B2Parent of this division
US 9,256,874 B2Parent of this continuation-in-part
Application13/797,246Parent of this continuation-in-part
US 2012/0265631 A1Published application
US 2013/0191289 A1Published application
US 10,515,356 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key