US 11,748,744 B2
Source independent consistent tokenization
Vijay Royyuru, Norristown, PA (US); Renee Goodheart, Midland Park, NJ (US); Lanny Byers, Ridgefield, CT (US); Timothy Horton, Papillion, NE (US); Kathryn Whalen, New York, NY (US); and Lixia Zhu, New York, NY (US)
Assigned to FIRST DATA CORPORATION, Coral Springs, FL (US)
Filed by First Data Corporation, Coral Springs, FL (US)
Filed on Apr. 1, 2020, as Appl. No. 16/837,718.
Claims priority of provisional application 62/828,729, filed on Apr. 3, 2019.
Prior Publication US 2020/0320516 A1, Oct. 8, 2020
Int. Cl. G06Q 20/36 (2012.01); G06Q 20/38 (2012.01)
CPC G06Q 20/3674 (2013.01) [G06Q 20/3672 (2013.01); G06Q 20/388 (2013.01)] 14 Claims
OG exemplary drawing
 
1. A system for source independent consistent tokenization, the system comprising:
one or more processors; and
one or more memories having stored thereon instructions that, upon execution by the one or more processors, cause the one or more processors to:
receive, from a merchant server, a first authorization request for a first transaction, the first authorization request comprising a primary account number for an account of a customer;
generate a merchant-facing token associated with the primary account number;
request a first authorization for the first transaction from an issuing host platform based on the primary account number;
receive, from the issuing host platform, the first authorization for the first transaction;
transmit, to the merchant server, an indication of the first authorization for the first transaction comprising the merchant-facing token;
receive, from the merchant server, a second authorization request for a second transaction, the second authorization request comprising a second token representing the account of the customer, wherein the second token is not the merchant-facing token or the primary account number;
detokenize the second token;
identify the merchant-facing token based on the detokenized second token;
request a second authorization for the second transaction from the issuing host platform based on the second token;
receive, from the issuing host platform, the second authorization for the second transaction; and
transmit, to the merchant server, an indication of the second authorization for the second transaction comprising the merchant-facing token.