IP Library Granted Patent US 10,728,088
Granted Patent B1
US 10,728,088 · App. 15/843,022 · Granted Jul 28, 2020

Systems and methods for real-time processing and transmitting of high-priority notifications

Inventor: Sachin Pawaskar (Mason, OH)
Assignee: Worldpay, LLC
H04L41/0686H04L41/069
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,728,088
App. No.
15/843,022
Granted
Jul 28, 2020
Kind
B1
Abstract

Systems and methods are disclosed for secure transmission of high-priority computer server event notifications. One method comprises obtaining a new computer server event to report; generating a first notification message pertaining to the computer server event; generating a second notification message pertaining to the computer server event and to the delivery of the first notification message; storing the first notification message; storing the second notification message; and transmitting the first notification message to a partner over a computer network.

Claims (43)

1. A method of secure transmission of high-priority computer server event notifications, the method comprising:

obtaining, by a notification server, a new computer server event to report; generating, by the notification server, a first notification message pertaining to the computer server event;

generating, by the notification server, a second notification message pertaining to the computer server event and to the delivery of the first notification message;

storing the first and second notification messages in a storage;

transmitting, by the notification server, the first notification message to a partner via a secure gateway over a computer network, the secure gateway being situated between the notification server and the partner, and configured to interface with the partner via an application programming interface (API) and determine whether the partner acknowledges the first notification message based on i) a status code received from the partner or ii) whether a preset time for receiving an acknowledgement from the partner has expired;

receiving, by the notification server, a third notification message from the secure gateway, the third notification message indicating whether the partner acknowledges the first notification message: and

upon determining that the partner acknowledges the first notification message based on the third notification message received from the secure gateway, removing, by the notification server, the second notification message from the storage, or

upon determining that the partner does not acknowledge the first notification message based on the third notification message received from the secure gateway, transmitting, by the notification server, the second notification message to a downstream system over the computer network.

2. The method of claim 1 , further comprising registering whether the partner acknowledges the first notification message.

3. The method of claim 1 , wherein the downstream system comprises a consumer credit or risk management service.

4. The method of claim 1 , wherein the secure gateway is further configured to provide security protocols comprising at least one of: message authentication code (MAC) or JavaScript Object Notation (JSON) Web Tokens (JWT).

5. The method of claim 2 , further comprising registering the transmission of the first notification message if the partner acknowledges the first notification message.

6. The method of claim 1 , further comprising registering whether the partner provides an update regarding the computer server event.

7. The method of claim 6 , further comprising transmitting the second notification message to a downstream system if the partner does not provide an update regarding the computer server event.

8. The method of claim 1 , wherein the second notification message is generated based on a service level agreement (SLA).

9. The method of claim 1 , wherein the computer server event is a fraud alert.

10. The method of claim 9 , wherein the first notification message includes details of the fraud alert.

11. The method of claim 1 , wherein the step of transmitting the first notification message occurs in real time.

12. A computer system for secure transmission of computer server event notifications, 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:

obtain a new computer server event to report;

generate a first notification message pertaining to the computer server event;

generate a second notification message pertaining to the computer server event and to the delivery of the first notification message;

store the first and second notification messages in a storage;

transmit the first notification message to a partner via a secure gateway over a computer network, the secure gateway being situated between the notification server and the partner, and configured to interface with the partner via an application programming interface (API) and determine whether the partner acknowledges the first notification message based on i) a status code received from the partner or ii) whether a preset time for receiving an acknowledgement from the partner has expired;

receive a third notification message from the secure gateway, the third notification message indicating whether the partner acknowledges the first notification message; and

upon determining that the partner acknowledges the first notification message based on the third notification message received from the secure gateway, remove the second notification message from the storage, or

upon determining that the partner does not acknowledge the first notification message based on the third notification message received from the secure gateway, transmit the second notification message to a downstream system over the computer network.

13. The computer system of claim 12 , wherein the plurality of functions further includes functions to register whether the partner acknowledges the first notification message.

14. The computer system of claim 13 , wherein the secure gateway is further configured to provide security protocols comprising at least one of: message authentication code (MAC) or JavaScript Object Notation (JSON) Web Tokens (JWT).

15. A non-transitory computer readable medium storing a program causing a computer to execute a method of secure transmission of computer server event notifications, the method comprising:

obtaining a new computer server event to report;

generating a first notification message pertaining to the computer server event;

generating a second notification message pertaining to the computer server event and to the delivery of the first notification message;

storing the first and second notification messages in a storage;

transmitting the first notification message to a partner via a secure gateway over a computer network, the secure gateway being situated between the notification server and the partner, and configured to interface with the partner via an application programming interface (API) and determine whether the partner acknowledges the first notification message based on i) a status code received from the partner or ii) whether a preset time for receiving an acknowledgement from the partner has expired;

receiving a third notification message from the secure gateway, the third notification message indicating whether the partner acknowledges the first notification message; and

upon determining that the partner acknowledges the first notification message based on the third notification message received from the secure gateway, removing the second notification message from the storage, or

upon determining that the partner does not acknowledge the first notification message based on the third notification message received from the secure gateway, transmitting the second notification message to a downstream system over the computer network.

16. The non-transitory computer readable medium of claim 15 , wherein method further comprises registering whether the partner acknowledges the first notification message.

17. The non-transitory computer readable medium of claim 16 , wherein the secure gateway is further configured to provide security protocols comprising at least one of: message authentication code (MAC) or JavaScript Object Notation (JSON) Web Tokens (JWT).

18. The non-transitory computer readable medium of claim 15 , wherein the computer server event is a fraud alert.

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 15, 2017
From: PAWASKAR, SACHIN
To: VANTIV, LLC
Reel/Frame 044404/0938 →