IP Library Granted Patent US 12,657,576
Granted Patent B2
US 12,657,576 · App. 18/943,476 · Granted Jun 16, 2026

Tokenizing a primary account number prior to transmission to a terminal

Inventors: James Zarakas (Centreville, VA); Tyler Locke (Jersey City, NJ)
Assignee: Capital One Services, LLC
G06Q20/3672G06Q20/02G06Q20/202G06Q20/204G06Q20/34G06Q20/341G06Q20/352G06Q20/3821G06Q20/38215G06Q20/385G06Q20/401G06Q2220/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,657,576
App. No.
18/943,476
Granted
Jun 16, 2026
Kind
B2
Abstract

In some implementations, a transaction card may receive transaction data from a transaction terminal based on initiation of a transaction with the transaction terminal; generate a tokenized primary account number, for use with the transaction, based on the transaction data and an actual primary account number of the transaction card; and transmit the tokenized primary account number to the transaction terminal for processing the transaction.

Claims (41)

1 . A first device, comprising:

one or more memories; and

one or more processors, coupled to the one or more memories, configured to:

receive, from a second device, information associated with a transaction;

generate, based on the information associated with the transaction, a first tokenized number and a second tokenized number, for use with the transaction,

wherein the first tokenized number is generated based on one or more first parameters and the second tokenized number is generated based on one or more second parameters; and

transmit, to the second device, the first tokenized number and the second tokenized number.

2 . The first device of claim 1 , wherein the one or more processors, to transmit the first tokenized number and the second tokenized number, are further configured to:

transmit a combined tokenized number that is based on the first tokenized number and the second tokenized number.

3 . The first device of claim 1 , wherein the one or more first parameters change across a plurality of transactions, including the transaction, and

wherein the one or more second parameters do not change across the plurality of transactions.

4 . The first device of claim 1 , wherein the first tokenized number is a single-use tokenized number, and the second tokenized number is a multi-use tokenized number.

5 . The first device of claim 1 , wherein at least one of the first tokenized number or the second tokenized number is generated based on at least a portion of an account number.

6 . The first device of claim 1 , wherein the first device is brought into communicative proximity of the second device for the transaction.

7 . The first device of claim 1 , wherein a first format associated with at least one of the first tokenized number or the second tokenized number is different from a second format associated with an account number.

8 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a first device, cause the first device to:

receive, from a second device, information associated with a transaction;

generate, based on the information associated with the transaction, a first tokenized number and a second tokenized number, for use with the transaction,

wherein the first tokenized number is generated based on one or more first parameters and the second tokenized number is generated based on one or more second parameters; and

transmit, to the second device, the first tokenized number and the second tokenized number.

9 . The non-transitory computer-readable medium of claim 8 , wherein the one or more instructions, that cause the first device to transmit the first tokenized number and the second tokenized number, cause the first device to:

transmit a combined tokenized number that is based on the first tokenized number and the second tokenized number.

10 . The non-transitory computer-readable medium of claim 8 , wherein the one or more first parameters change across a plurality of transactions, including the transaction, and

wherein the one or more second parameters do not change across the plurality of transactions.

11 . The non-transitory computer-readable medium of claim 8 , wherein the first tokenized number is a single-use tokenized number, and the second tokenized number is a multi-use tokenized number.

12 . The non-transitory computer-readable medium of claim 8 , wherein at least one of the first tokenized number or the second tokenized number is generated based on at least a portion of an account number.

13 . The non-transitory computer-readable medium of claim 8 , wherein the first device is brought into communicative proximity of the second device for the transaction.

14 . The non-transitory computer-readable medium of claim 8 , wherein a first format associated with at least one of the first tokenized number or the second tokenized number is different from a second format associated with an account number.

15 . A method, comprising:

receiving, by a first device and from a second device, information associated with a transaction;

generating, based on the information associated with the transaction, a first tokenized number and a second tokenized number, for use with the transaction,

wherein the first tokenized number is generated based on one or more first parameters and the second tokenized number is generated based on one or more second parameters; and

transmitting, by the first device and to the second device, the first tokenized number and the second tokenized number.

16 . The method of claim 15 , wherein transmitting the first tokenized number and the second tokenized number comprises:

transmitting a combined tokenized number that is based on the first tokenized number and the second tokenized number.

17 . The method of claim 15 , wherein the one or more first parameters change across a plurality of transactions, including the transaction, and

wherein the one or more second parameters do not change across the plurality of transactions.

18 . The method of claim 15 , wherein the first tokenized number is a single-use tokenized number, and the second tokenized number is a multi-use tokenized number.

19 . The method of claim 15 , wherein at least one of the first tokenized number or the second tokenized number is generated based on at least a portion of an account number.

20 . The method of claim 15 , wherein the first device is brought into communicative proximity of the second device for the transaction.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 11, 2024
From: ZARAKAS, JAMES; LOCKE, TYLER
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 069203/0873 →
Continuity (9)
Continuation 18515742 · Nov 21, 2023
Continuation 18184092 · Mar 15, 2023
Continuation 17590034 · Feb 1, 2022
Continuation 17302321 · Apr 30, 2021
Continuation 16824935 · Mar 20, 2020
Continuation 16601932 · Oct 15, 2019
Continuation 16376562 · Apr 5, 2019
Continuation 16162094 · Oct 16, 2018
Related Publication 20250069066A1 · Feb 27, 2025
References Cited (19)
US 8151345B1 · Yeager · 2012 [cited by applicant]
US 10296901B1 · Zarakas et al. · 2019 [cited by applicant]
US 10496984B1 · Zarakas et al. · 2019 [cited by applicant]
US 10600051B1 · Zarakas et al. · 2020 [cited by applicant]
US 10997591B2 · Zarakas et al. · 2021 [cited by applicant]
US 11244305B2 · Zarakas et al. · 2022 [cited by applicant]
US 11615400B2 · Zarakas et al. · 2023 [cited by applicant]
US 11861596B2 · Zarakas et al. · 2024 [cited by applicant]
US 12141789B2 · Zarakas · 2024 [cited by examiner]
US 20120039469A1 · Mueller et al. · 2012 [cited by applicant]
US 20140074637A1 · Hammad · 2014 [cited by applicant]
US 20150073983A1 · Bartenstein et al. · 2015 [cited by applicant]
US 20180005227A1 · Sandelov et al. · 2018 [cited by applicant]
US 20190034912A1 · Wilson · 2019 [cited by applicant]
US 20190043045A1 · Wilson · 2019 [cited by applicant]
Malcomvetter T., “Breaking Credit Card Tokenization—Part 1,” Dec. 9, 2015, 1 page. Retrieved from the Internet: [URL:https://www.optiv.com/blog/breaking-credit-card-tokenization-part-1]. [cited by applicant]
Riesen M., “What is Tokenization and How Can I Use it for PCI DSS Compliance?,” Feb. 24, 2016, 2 pages. Retrieved from the Internet: [URL:https://www.securitymetrics.com/blog/what-tokenization-and-how-can-i-use-it-pci-d… [cited by applicant]
Square, Inc., “Payment Tokenization Explained,” Apr. 26, 2016, 8 pages. Retrieved from the Internet: [URL:https://squareup.com/townsquare/what-does-tokenization-actually-mean]. [cited by applicant]
Wikipedia., “Tokenization (Data Security),” Oct. 11, 2018, 7 pages. Retrieved from the Internet: [URL:https://en.wikipedia.org/wiki/Tokenizations_(data_security)]. [cited by applicant]