IP Library Granted Patent US 12,549,367
Granted Patent B2
US 12,549,367 · App. 18/353,763 · Granted Feb 10, 2026

Systems and methods for tokenization

Inventors: Wojciech Chowanski (Toronto, CA); Méliné N. Nikoghossian (Toronto, CA)
Assignee: The Toronto-Dominion Bank
H04L9/3213H04L9/3297
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,549,367
App. No.
18/353,763
Filed
Jul 17, 2023
Granted
Feb 10, 2026
Kind
B2
Art Unit
2495
USPC
726/9
Abstract

Computer-implemented systems and methods for tokenization. The system includes a network, at least one token database coupled to the network, and a real-time tokenization server coupled to the at least one token database via the network. The server is configured to receive a request in real-time, determine one or more payload to be tokenized, and transmit the one or more payload to the at least one token database for tokenization. The at least one token database is configured to tokenize the one or more payload to generate one or more tokens and store an association between each of the one or more payload and respective one or more tokens along with a timestamp. The real-time tokenization server is further configured to receive at least one token from the token database and return the at least one token in response to the request.

Claims (48)

1 . A tokenization system, the system comprising:

a network;

at least one token database coupled to the network;

a real-time tokenization server coupled to the at least one token database via the network, the real-time tokenization server configured to:

receive a request in real-time;

in real-time, determine one or more payload to be tokenized and transmit one or more payload to the at least one token database for tokenization;

the at least one token database configured to:

tokenize the one or more payload to generate one or more tokens, and

store an association between each of the one or more payload and respective one or more tokens along with a timestamp;

the real-time tokenization server further configured to:

receive at least one token from the at least one token database; and

return the at least one token in response to the request.

2 . The tokenization system of claim 1 , further comprising:

a batch tokenization server coupled to the at least one token database via the network, the batch tokenization server having a token table, the batch tokenization server configured to:

receive at least one batch request response comprising a delta table;

in response to each of the at least one batch request response, retrieve a plurality of recent tokens, based on a time of last update of the token table, from the at least one token database and update the token table with the plurality of recent tokens;

using the token table, determine a new payload from the one or more payload to be tokenized;

generate a new token corresponding to the new payload; and

update the token table and the at least one token database with the new token.

3 . The tokenization system of claim 2 , wherein the one or more payload is used a key.

4 . The tokenization system of claim 2 , wherein the one or more payload is preprocessed to generate a key.

5 . The tokenization system of claim 4 , wherein the one or more payload is truncated based on a set of predetermined rules and wherein the set of predetermined rules includes at least identifying a particular portion of the one or more payload to be used as the key.

6 . The tokenization system of claim 1 , wherein the real-time tokenization server is a microservice.

7 . The tokenization system of claim 1 , wherein the at least one token database includes a SQL database.

8 . The tokenization system of claim 2 , wherein the token table is stored in a local database of the batch tokenization server, the local database distinct from the at least one token database.

9 . A method comprising:

receiving, by a real-time tokenization server, a request;

determining, in real-time by the real-time tokenization server, one or more payload to be tokenized;

transmitting, by the real-time tokenization server, the one or more payload to at least one token database for tokenization;

receiving, by the real-time tokenization server, at least one token from the at least one token database; and

returning, by the real-time tokenization server, the at least one token in response to the request.

10 . The method of claim 9 , wherein:

retrieving, in response to at least one batch request response, by a batch tokenizer server, a plurality of recent tokens, based on a time of last update of the token table, from the at least one token database and updates the token table with the plurality of recent tokens;

determining a new payload from the one or more payload to be tokenized, using the token table;

generating a new token corresponding to the new payload; and

updating the token table and the at least one token database with the new token.

11 . The method of claim 10 , further comprising using the one or more payload as a key.

12 . The method of claim 10 , further comprising preprocessing the one or more payload to generate a key.

13 . The method of claim 12 , further comprising truncating the one or more payload based on a set of predetermined rules and wherein the set of predetermined rules includes at least identifying a particular portion of the one or more payload to be used as the key.

14 . The method of claim 9 , wherein the real-time tokenization server is a microservice.

15 . The method of claim 9 , wherein the at least one token database is a SQL database.

16 . The method of claim 10 , wherein the token table is stored in a local database od the batch tokenization server, the local database distinct from the at least one token database.

17 . A non-transitory computer readable medium storing computer executable instructions which, when executed by at least one computer processor, cause the at least one computer processor to carry out a method comprising:

receiving, by a real-time tokenization server, a request;

determining, in real-time by the real-time tokenization server, one or more payload to be tokenized;

transmitting, by the real-time tokenization server, the one or more payload to at least one token database for tokenization;

receiving, by the real-time tokenization server, at least one token from the at least one token database; and

returning, by the real-time tokenization server, the at least one token in response to the request.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 5, 2023
From: CHOWANSKI, WOJCIECH; NIKOGHOSSIAN, MÉLINÉ
To: TORONTO-DOMINION BANK
Reel/Frame 064795/0992 →
Continuity (1)
Related Publication 20250030547A1 · Jan 23, 2025
References Cited (45)
US 10135763B2 · Sheth · 2018 [cited by applicant]
US 10817621B2 · Takahashi · 2020 [cited by applicant]
US 10878126B1 · Koduru · 2020 [cited by examiner]
US 11074238B2 · Kessler · 2021 [cited by applicant]
US 11093476B1 · Neeman · 2021 [cited by applicant]
US 11171930B2 · Baig · 2021 [cited by applicant]
US 11449627B2 · Bayon · 2022 [cited by applicant]
US 11507692B2 · Vemula · 2022 [cited by applicant]
US 11520925B1 · Sumner · 2022 [cited by applicant]
US 11521207B2 · Braundmeier · 2022 [cited by applicant]
US 11537737B2 · Koduru · 2022 [cited by applicant]
US 11651380B1 · Arnab · 2023 [cited by applicant]
US 11757837B2 · Sofer · 2023 [cited by applicant]
US 12164542B1 · Rahman · 2024 [cited by applicant]
US 20030217033A1 · Sandler · 2003 [cited by examiner]
US 20140304825A1 · Gianniotis · 2014 [cited by examiner]
US 20170104756A1 · Rosenthal · 2017 [cited by examiner]
US 20180211055A1 · Balijepalli · 2018 [cited by applicant]
US 20200117680A1 · Bapat · 2020 [cited by examiner]
US 20220012241A1 · Colcord · 2022 [cited by examiner]
US 20220067184A1 · Lindsay · 2022 [cited by examiner]
US 20220067205A1 · Lindsay · 2022 [cited by examiner]
US 20220067206A1 · Lindsay · 2022 [cited by examiner]
US 20220067207A1 · Lindsay · 2022 [cited by examiner]
US 20220075878A1 · Begg · 2022 [cited by examiner]
US 20220140997A1 · Lam · 2022 [cited by examiner]
US 20220164474A1 · Netke · 2022 [cited by applicant]
US 20220366064A1 · Nikoghossian · 2022 [cited by applicant]
US 20230140723A1 · Balasubramanian · 2023 [cited by examiner]
US 20230143636A1 · Busjaeger · 2023 [cited by examiner]
US 20230342481A1 · Nikoghossian · 2023 [cited by examiner]
US 20240070306A1 · Jurat · 2024 [cited by applicant]
US 20240143839A1 · Lindsay · 2024 [cited by examiner]
US 20240184923A1 · Lindsay · 2024 [cited by examiner]
US 20240394684A1 · Sarin · 2024 [cited by examiner]
US 20250028852A1 · Chowanski · 2025 [cited by examiner]
US 20250030547A1 · Chowanski · 2025 [cited by examiner]
US 20250045274A1 · Cseri · 2025 [cited by examiner]
US 20250068646A1 · Rahman · 2025 [cited by applicant]
JP 4987203B2 · 2012 [cited by examiner]
WO WO03098465A1 · 2003 [cited by examiner]
WO 2024148028A1 · 2024 [cited by applicant]
WO WO2025094194A1 · 2025 [cited by examiner]
Office Action (Non-Final Rejection) dated Mar. 24, 2025 for U.S. Appl. No. 18/353,526 (pp. 1-11). [cited by applicant]
Office Action (Notice of Allowance and Fee(s) Due) mailed Dec. 30, 2025 in U.S. Appl. No. 18/353,526 (11 pages). [cited by applicant]