IP Library Granted Patent US 11,416,852
Granted Patent B1
US 11,416,852 · App. 15/843,549 · Granted Aug 16, 2022

Systems and methods for generating and transmitting electronic transaction account information messages

Inventor: Sachin Pawaskar (Mason, OH)
Assignee: WORLDPAY, LLC
G06Q20/382G06Q20/027G06Q20/102G06Q20/4014G06Q20/4018G06Q30/0613
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 11,416,852
App. No.
15/843,549
Granted
Aug 16, 2022
Kind
B1
Abstract

Systems and methods are disclosed for secure transmission of account information messages. One method comprises receiving account information; providing a notification to a third party regarding the account information; receiving a first request for information regarding the notification from the third party; providing a response to the third party regarding the first request; receiving data from the third party; using the data to generate a message including details about the account, wherein at least some of the details about the account are encrypted; receiving a second request for information regarding the notification from the third party; and providing the message to the third party.

Claims (70)

1. A method of secure transmission of account information messages, the method comprising:

receiving, by a distributed computing system, account information, the account information including a request for making an account available for use with a digital payment platform;

transmitting, by the distributed computing system, to a mainframe of the distributed computing system, the account information including the request for making the account available for use with the digital payment platform;

transmitting, by the distributed computing system, a card open notification to a partner distributed computing system;

determining, by the distributed computing system, that an acknowledgment of the card open notification request from the partner distributed computing system has not been received within a time threshold;

incrementing, by the distributed computing system, an attempt count for transmitting the card open notification request to the partner distributed computing system;

determining, by the distributed computing system, to cease the attempt to deliver the card open notification request to the partner distributed computing system based, at least in part, on a threshold attempt count limit;

receiving, by the distributed computing system, via an Application Programming Interface (API) call, a first request for information regarding a notification from the partner distributed computing system;

transmitting, by the distributed computing system, a response to the partner distributed computing system regarding the first request, the response comprising account identifying information without payment card industry data security standard information;

receiving, by the distributed computing system, data including at least one nonce value from the partner distributed computing system, wherein the at least one nonce value includes a server nonce value and a device signature nonce value;

generating, by the distributed computing system, encrypted information by using the at least one nonce value of the data;

generating, by the distributed computing system, a message based on the encrypted information, the message including encrypted payment card industry data security standard information;

receiving, by the distributed computing system, a second request for information regarding the notification from the partner distributed computing system; and

transmitting, by the distributed computing system, the message to a digital payment provider for use on the digital payment platform.

2. The method of claim 1 , further comprising:

receiving an acknowledgement of the notification from the partner distributed computing system; and

indicating that the notification has been sent to a database.

3. The method of claim 2 , wherein the account information includes at least one of a card number, an account holder name, and a card verification value.

4. The method of claim 1 , further comprising:

storing the account information, and

generating the message including details about the account based on the account information.

5. The method of claim 1 , further comprising:

transmitting, by the partner distributed computing system, only encrypted part of the data to the digital payment provider.

6. The method of claim 1 , wherein the response includes at least one of an account holder name, an account number, and an account type.

7. The method of claim 6 , wherein the response further includes an at least partially-masked card number.

8. The method of claim 1 , wherein the notification, the response, and the message do not include unencrypted data subject to a payment card industry data security standard.

9. The method of claim 1 , further comprising:

receiving a request from an account holder to make the account available on a digital payment platform.

10. The method of claim 1 , wherein the message is provided in real time.

11. The method of claim 1 , wherein the response to the partner distributed computing system is in an incomplete format.

12. A computer system for secure transmission of account information messages, the system comprising:

a memory having processor-readable instructions stored therein; and

a processor configured to access the memory and execute the processor-readable instructions, which when executed by the processor configures the processor to perform a plurality of functions, including functions to:

receive, by a distributed computing system, account information, the account information including a request for making an account available for use with a digital payment platform;

transmit, by the distributed computing system, to a mainframe of the distributed computing system, the account information including the request for making the account available for use with the digital payment platform;

transmit, by the distributed computing system, a card open notification to a partner distributed computing system;

determine, by the distributed computing system, that an acknowledgment of the card open notification request from the partner distributed computing system has not been received within a time threshold;

increment, by the distributed computing system, an attempt count for transmitting the card open notification request to the partner distributed computing system;

determine, by the distributed computing system, to cease the attempt to deliver the card open notification request to the partner distributed computing system based, at least in part, on a threshold attempt count limit;

receive, by the distributed computing system, via an Application Programming Interface (AP) call, a first request for information regarding a notification from the partner distributed computing system;

transmit, by the distributed computing system, a response to the partner distributed computing system regarding the first request, the response comprising account identifying information without payment card industry data security standard information;

receive, by the distributed computing system, data including at least one nonce value from the partner distributed computing system, wherein the at least one nonce value includes a server nonce value and a device signature nonce value;

generate, by the distributed computing system, encrypted information by using the at least one nonce value of the data;

generate, by the distributed computing system, a message based on the encrypted information, the message including encrypted payment card industry data security standard information;

receive, by the distributed computing system, a second request for information regarding the notification from the partner distributed computing system; and

transmit, by the distributed computing system, the message to a digital payment provider for use on the digital payment platform.

13. The system of claim 12 , wherein the plurality of functions further includes functions to:

receive an acknowledgement of the notification from the partner distributed computing system; and

indicate that the notification has been sent to a database.

14. The system of claim 13 , wherein the account information includes at least one of a card number, an account holder name, and a card verification value.

15. The system of claim 12 , wherein the plurality of functions further includes functions to store the account information, and to generate the message including details about the account based on the account information.

16. A non-transitory computer readable medium storing a program causing a computer to execute a method of secure transmission of account information messages, the method comprising:

receiving, by a distributed computing system, account information, the account information including a request for making an account available for use with a digital payment platform;

transmitting, by the distributed computing system, to a mainframe of the distributed computing system, the account information including the request for making the account available for use with the digital payment platform;

transmitting, by the distributed computing system, a card open notification to a partner distributed computing system;

determining, by the distributed computing system, that an acknowledgment of the card open notification request from the partner distributed computing system has not bee n received within a time threshold;

incrementing, by the distributed computing system, an attempt count for transmitting the card open notification request to the partner distributed computing system;

determining, by the distributed computing system, to cease the attempt to deliver the card open notification request to the partner distributed computing system based, at least in part, on a threshold attempt count limit;

receiving, by the distributed computing system, via an Application Programming Interface (API) call, a first request for information regarding a notification from the partner distributed computing system;

transmitting, by the distributed computing system, a response to the partner distributed computing system regarding the first request, the response comprising account identifying information without payment card industry data security standard information;

receiving, by the distributed computing system, data including at least one nonce value from the partner distributed computing system, wherein the at least one nonce value includes a server nonce value and a device signature nonce value;

generating, by the distributed computing system, encrypted information by using the at least one nonce value of the data;

generating, by the distributed computing system, a message based on the encrypted information, the message including encrypted payment card industry data security standard information;

receiving, by the distributed computing system, a second request for information regarding the notification from the partner distributed computing system; and

transmitting, by the distributed computing system, the message to a digital payment provider for use on the digital payment platform.

17. The non-transitory computer readable medium of claim 16 , wherein the method further comprises:

receiving an acknowledgement of the notification from the partner distributed computing system; and

indicating that the notification has been sent to a database.

18. The non-transitory computer readable medium of claim 17 , wherein the account information includes at least one of a card number, an account holder name, and a card verification value.

19. The non-transitory computer readable medium of claim 16 , wherein the method further comprises storing the account information, and generating the message including details about the account based on the account information.

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 Dec 18, 2017
From: PAWASKAR, SACHIN
To: VANTIV, LLC
Reel/Frame 044417/0673 →