IP Library Granted Patent US 10,404,703
Granted Patent B1
US 10,404,703 · App. 15/368,093 · Granted Sep 3, 2019

Systems and methods for third-party interoperability in secure network transactions using tokenized data

Inventor: Brant Peterson (Denver, CO)
Assignee: Worldpay, LLC
H04L63/10H04L63/08G06F2221/0711G06Q50/26
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 10,404,703
App. No.
15/368,093
Granted
Sep 3, 2019
Kind
B1
Abstract

Embodiments include methods and systems for enabling third-party data service interoperability, comprising receiving, from an electronic data server, a request for a low-value token, the low-value token being associated with a subset of sensitive data associated with a user; providing the low-value token to the electronic data server; receiving a request for the subset of sensitive data, from a third-party data service server, the request comprising the low-value token; de-tokenizing the low-value token to obtain the subset of sensitive data; providing the subset of sensitive data to the third-party data service server; receiving, from an electronic data server, the low-value token and a transaction authorization request; determining, based on the low-value token and authorization request, an authorization response; and providing the authorization response to the electronic data server.

Claims (53)

1. A method for enabling third-party data service interoperability, comprising:

receiving, at a transaction processor server from an electronic data server, a request for a low-value token, the request comprising a high-value token, the high-value token being associated with a set of sensitive data associated with a user and being usable by the electronic data server to facilitate subsequent electronic transactions, and the low-value token being a limited-use token configured to obtain a subset of sensitive data associated with the user;

retrieving, by the transaction processor server, the low-value token from a database;

providing, by the transaction processor server, the low-value token to the electronic data server;

receiving, at the transaction processor server from a third-party data service server, a request for the subset of sensitive data, the request comprising the low-value token, the low-value token having been provided to the third-party data service server by the electronic data server;

de-tokenizing, by the transaction processor server, the low-value token to obtain the subset of sensitive data;

providing, by the transaction processor server, the subset of sensitive data to the third-party data service server, the third-party data service server configured to perform a third-party security service based on the subset of sensitive data;

receiving, at the transaction processor server from the electronic data server, the low-value token and a transaction authorization request once the third-party data service server completes the third-party security service;

determining, by the transaction processor server, an authorization response based on the low-value token and authorization request; and

providing, by the transaction processor server, the authorization response to the electronic data server.

2. The method of claim 1 , wherein determining the authorization response further comprises:

receiving, from the electronic data server, third-party data security service data; and

determining the authorization response based on the low-value token, the authorization request, and the third-party security service data.

3. The method of claim 1 , wherein sensitive data comprises social security data, account data, or credit card data of the user.

4. The method of claim 1 , wherein the request for the low-value token specifies the subset of sensitive data with which the low-value token is associated.

5. The method of claim 1 , wherein the third-party data service server is prohibited from forwarding the subset of sensitive data to the electronic data server.

6. The method of claim 1 , wherein the electronic data server uses an Internet browser page with an embedded iFrame element to form the request for the low-value token.

7. A system for enabling third-party data service interoperability, the system comprising:

a data storage device storing instructions for enabling third-party data service interoperability; and

a processor configured to execute the instructions to perform a method comprising:

receiving, from an electronic data server, a request for a low-value token, the request comprising a high-value token, the high-value token being associated with a set of sensitive data associated with a user and being usable by the electronic data server to facilitate subsequent electronic transactions, and the low-value token being a limited-use token configured to obtain a subset of sensitive data associated with the user;

retrieving the low-value token from a database;

providing the low-value token to the electronic data server;

receiving a request for the subset of sensitive data, from a third-party data service server, the request comprising the low-value token, the low-value token having been provided to the third-party data service server by the electronic data server;

de-tokenizing the low-value token to obtain the subset of sensitive data; and

providing the subset of sensitive data to the third-party data service server, the third-party data service server configured to perform a third-party security service based on the subset of sensitive data.

8. The system of claim 7 , further comprising:

receiving, from the electronic data server, the low-value token and a transaction authorization request;

determining, based on the low-value token and authorization request, an authorization response; and

providing the authorization response to the electronic data server.

9. The system of claim 8 , wherein the electronic data server uses an Internet browser page with an embedded iFrame element to form the request for the low-value token.

10. The system of claim 8 , wherein determining the authorization response further comprises:

receiving, from the electronic data server, third-party data security service data; and

determining the authorization response based on the low-value token, the authorization request, and the third-party security service data.

11. The system of claim 8 , wherein sensitive data comprises social security data, account data, or credit card data of the user.

12. The system of claim 8 , wherein the request for the low-value token specifies the subset of sensitive data with which the low-value token is associated.

13. The system of claim 8 , wherein the third-party data service server is prohibited from forwarding the subset of sensitive data to the electronic data server.

14. A non-transitory computer-readable medium storing instructions that, when executed by a transaction processor, cause the transaction processor to perform a method for enabling third-party data service interoperability, the method comprising:

receiving, from an electronic data server, a request for a low-value token, the request comprising a high-value token, the high-value token being associated with a set of sensitive data associated with a user and being usable by the electronic data server to facilitate subsequent electronic transactions, and the low-value token being a limited-use token configured to obtain a subset of sensitive data associated with the user;

retrieving the low-value token from a database;

providing the low-value token to the electronic data server;

receiving a request for the subset of sensitive data, from a third-party data service server, the request comprising the low-value token, the low-value token having been provided to the third-party data service server by the electronic data server;

de-tokenizing the low-value token to obtain the subset of sensitive data;

providing the subset of sensitive data to the third-party data service server, the third-party data service server configured to perform a third-party security service based on the subset of sensitive data.

15. The computer-readable medium of claim 14 , further comprising:

receiving, from the electronic data server, the low-value token and a transaction authorization request;

determining, based on the low-value token and authorization request, an authorization response; and

providing the authorization response to the electronic data server.

16. The computer-readable medium of claim 15 , wherein the request for the low-value token specifies the subset of sensitive data with which the low-value token is associated.

17. The computer-readable medium of claim 15 , wherein the third-party data service server is prohibited from forwarding the subset of sensitive data to the electronic data server.

18. The computer-readable medium of claim 15 , wherein the method of determining the authorization response further comprises:

receiving, from the electronic data server, third-party data security service data; and

determining the authorization response based on the low-value token, the authorization request, and the third-party security service data.

Assignments (6)
RELEASE OF SECURITY INTERESTS RECORDED AT REEL/FRAMES 066626/0655, 066625/0426, 066625/0347, AND 066625/0276 Recorded Jan 12, 2026
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: WORLDPAY, LLC; WORLDPAY ISO AND ECOMMERCE, LLC; PAYMETRIC, LLC; WORLDPAY US, LLC
Reel/Frame 074314/0622 →
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY RECORDED AT R/F 066624/0719 Recorded Jan 12, 2026
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: WORLDPAY, LLC
Reel/Frame 074315/0412 →
SECURITY INTEREST Recorded Feb 19, 2024
From: WORLDPAY, LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 066624/0719 →
SECURITY INTEREST Recorded Feb 19, 2024
From: WORLDPAY, LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 066626/0655 →
CHANGE OF NAME Recorded Aug 6, 2018
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 046723/0234 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 4, 2017
From: PETERSON, BRANT
To: VANTIV, LLC
Reel/Frame 040842/0470 →
Cited By (7)
US 12,238,114 US 12,423,454 US 12,423,455 US 12,609,825 US 12,694,143 US 12,711,332 US 12,719,663