IP Library Granted Patent US 12,561,679
Granted Patent B2
US 12,561,679 · App. 18/585,901 · Granted Feb 24, 2026

Systems and methods for prefetching payment card industry data

Inventors: Sridhar Aravamudhan (Middletown, MD); Howard Spector (Street, MD); Valli Musti (Scarsdale, NY)
Assignee: JPMORGAN CHASE BANK, N.A.
G06Q20/385G06F21/6245G06F21/6254G06Q20/367G06Q20/38215G06Q20/3823G06Q20/3827H04L9/0643H04L9/3213G06Q2220/00H04L67/10
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,561,679
App. No.
18/585,901
Granted
Feb 24, 2026
Kind
B2
Abstract

Systems and methods for prefetching Payment Card Industry (PCI) data. A method may include a tokenization service in a cloud environment: (1) receiving a request to prefetch a plurality of tokens from a client application; (2) generating the plurality of tokens and a co-relation indicator for each of the plurality of tokens; (3) storing the plurality of tokens and the co-relation indicators in a token vault in the cloud environment; (4) returning the plurality of tokens and the co-relation indicators to the client electronic device; (5) receiving a mapping request comprising a source value and the co-relation indicator for one of the plurality of tokens; (6) identifying the token of the plurality of tokens associated with the co-relation indicator; (7) mapping the token to the source value; and (8) returning a message indicating successful mapping to the client application.

Claims (55)

1 . A method, comprising:

receiving, at a tokenization service executed in a cloud environment, a request to prefetch a plurality of tokens from a client application executed by a client electronic device;

generating, by the tokenization service, the plurality of tokens and a co-relation indicator for each of the plurality of tokens;

storing, by the tokenization service, the plurality of tokens and the co-relation indicators in a token vault in the cloud environment;

returning, by the tokenization service, the plurality of tokens and the co-relation indicators to the client electronic device;

in response to the tokenization service being unavailable, mapping, by the client application, a source value to one token of the plurality of tokens;

using, by the client application, the token as a surrogate for the source value;

in response to the tokenization service being available again, sending, by the client application and to the tokenization service, a mapping request comprising the source value and the co-relation indicator for the token;

identifying, by the tokenization service, the token of the plurality of tokens associated with the co-relation indicator;

mapping, by the tokenization service, the token to the source value; and

returning, by the tokenization service, a message indicating successful mapping to the client application.

2 . The method of claim 1 , wherein the request comprises a token format for the plurality of tokens.

3 . The method of claim 2 , wherein the token format comprises a token length.

4 . The method of claim 1 , further comprising:

generating, by the tokenization service, a hash of the source value;

encrypting, by the tokenization service, the source value;

persisting, by the tokenization service, the hash and the token in a source hash table; and

persisting, by the tokenization service, the hash, the encrypted source value, and the token in a token table.

5 . The method of claim 1 , wherein the source value comprises sensitive data.

6 . The method of claim 5 , wherein the sensitive data comprises personally identifiable data.

7 . The method of claim 1 , wherein the source value comprises a primary account number.

8 . A system, comprising:

a client electronic device executing a client application; and

a cloud environment comprising a computer processor executing a tokenization service;

wherein:

the tokenization service is configured to receive a request to prefetch a plurality of tokens from the client application;

the tokenization service is configured to generate the plurality of tokens and a co-relation indicator for each of the plurality of tokens to store the plurality of tokens and the co-relation indicators in a token vault in the cloud environment;

the tokenization service is configured to return the plurality of tokens and the co-relation indicators to the client application;

in response to the tokenization service being unavailable:

the client application is configured to map a source value to one token of the plurality of tokens; and

the client application is configured to use the token as a surrogate for the source value;

in response to the tokenization service being available again, sending, by the client application and to the tokenization service, a mapping request comprising the source value and the co-relation indicator for the token;

the tokenization service is configured to identify the token of the plurality of tokens associated with the co-relation indicator;

the tokenization service is configured to map the token to the source value; and

the tokenization service is configured to return a message indicating successful mapping to the client application.

9 . The system of claim 8 , wherein the request comprises a token format for the plurality of tokens.

10 . The system of claim 9 , wherein the token format comprises a token length.

11 . The system of claim 8 , wherein:

the tokenization service is further configured to generate a hash of the source value;

the tokenization service is further configured to encrypt the source value;

the tokenization service is further configured to persist the hash and the token in a source hash table; and

the tokenization service is further configured to persist the hash, the encrypted source value, and the token in a token table.

12 . The system of claim 8 , wherein the source value comprises sensitive data.

13 . The system of claim 12 , wherein the sensitive data comprises personally identifiable data.

14 . The system of claim 8 , wherein the source value comprises a primary account number.

15 . A method, comprising:

receiving, at an account number generation service, a request to prefetch a plurality of primary account numbers from a client application executed by a client electronic device;

generating, by the account number generation service, the plurality of primary account numbers;

returning, by the account number generation service, the plurality of primary account numbers to the client application;

in response to the account number generation service being unavailable, assigning, by the client application, one of the plurality of account numbers to an account;

sending, by the client application and to a tokenization service, a mapping request comprising one of the plurality of primary account numbers and a co-relation indicator for a token;

identifying, by the tokenization service, the token out of a plurality of tokens associated with the co-relation indicator;

mapping, by the tokenization service, the token to the primary account number; and

returning, by the tokenization service, a message indicating successful mapping to the client application.

16 . The method of claim 15 , wherein the request comprises a bank identification number for the plurality of primary account numbers.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 7, 2025
From: ARAVAMUDHAN, SRIDHAR; SPECTOR, HOWARD; MUSTI, VALLI
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 072821/0772 →
Continuity (2)
Continuation In Part 18527074 · Dec 1, 2023
Related Publication 20250182090A1 · Jun 5, 2025
References Cited (14)
US 8595850B2 · Spies · 2013 [cited by examiner]
US 9237006B2 · Mattsson · 2016 [cited by examiner]
US 10025941B1 · Griffin · 2018 [cited by examiner]
US 10541982B1 · Lee · 2020 [cited by examiner]
US 20150127547A1 · Powell · 2015 [cited by examiner]
US 20150312038A1 · Palanisamy · 2015 [cited by examiner]
US 20170098218A1 · Rios · 2017 [cited by examiner]
US 20180212956A1 · Sanganabhatla · 2018 [cited by examiner]
US 20180247654A1 · Bhaya · 2018 [cited by examiner]
US 20240179003A1 · Bayon · 2024 [cited by examiner]
US 20240249270A1 · Sankaran · 2024 [cited by examiner]
US 20250030547A1 · Chowanski · 2025 [cited by examiner]
Liu et al. “State of the Art: Secure Mobile Payment”, IEEE Access, vol. 8, 2020 (shown as published on Jan. 1, 2020 and date of current version Jan. 23, 2020, pp. 13898-13914) (Year: 2020). [cited by examiner]
“Announcing Major Changes to the Issuer Identification Number (IIN) Standard”, ANSI News and Publications, Jul. 28, 2016, 3 pages (Year: 2016). [cited by examiner]