IP Library Granted Patent US 11,165,628
Granted Patent B2
US 11,165,628 · App. 16/696,656 · Granted Nov 2, 2021

Systems and methods for registering computer server event notifications

Inventor: Sachin Pawaskar (Mason, OH)
Assignee: Worldpay, LLC
H04L41/06H04L41/0604H04L41/069H04L41/24H04L41/28
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,165,628
App. No.
16/696,656
Granted
Nov 2, 2021
Kind
B2
Abstract

A system for secure transmission of business event notifications includes a memory, at least one processor, a service gateway configured to: publish application programming interfaces (APIs) for secure transmission of business event notifications, a notification server configured to: publish APIs for secure transmission of business event notifications corresponding to the APIs published by the service gateway, obtain a new business event to report, determine a partner to receive a notification of the new business event, transmit an event notification to the partner by way of the service gateway APIs, and register the event notification in a database.

Claims (41)

1. A method for controlled transmission of computer server event notifications, the method comprising:

receiving, by a notification server, a subscription registration request from a partner system, the subscription registration request comprising at least one event type;

generating, by the notification server, a notification associated with one or more computer server events of the at least one event type in accordance with a quantity threshold indicating a number of server events to associate with the notification, the quantity threshold calculated based on at least one of the at least one event type, the partner system, and a current time;

transmitting, by the notification server, the notification to the partner system in accordance with a time threshold indicating a predetermined time period to associate with the notification, the time threshold calculated based on at least one of the at least one event type, the partner system, and a current time;

receiving, by the notification server, a request for computer server event details from the partner system; and

transmitting, by the notification server, the computer server event details to the partner system in response to the received request.

2. The method of claim 1 , wherein the time threshold defines a length of a time period between two consecutive notifications.

3. The method of claim 2 , wherein the quantity threshold defines a minimum number of computer server events to include in the notification.

4. The method of claim 3 , wherein, if the time threshold is reached before the quantity threshold is reached, the notification is transmitted to the partner system before the quantity threshold is reached.

5. The method of claim 2 , wherein the quantity threshold defines a maximum number of computer server events to include in the notification.

6. The method of claim 5 , wherein, if the quantity threshold is reached before the time threshold is reached, the notification is transmitted to the partner system before the time threshold is reached.

7. The method of claim 1 , further comprising:

publishing, by the notification server, an application programming interface (API) for secure communication with the partner system over a computer network, the API corresponding to an API published by a service gateway,

wherein the notification is transmitted over the computer network by way of the API published by the service gateway.

8. The method of claim 7 , wherein the API published by the service gateway include features for secure transmission of notifications.

9. The method of claim 8 , wherein the features for secure transmission of notifications include one or more of message authentication codes (MAC), JavaScript Object Notation (JSON) Web Tokens (JWT), and Hypertext Transfer Protocol Secure (HTTPS).

10. The method of claim 8 , wherein the API published by the service gateway include interfaces for receiving computer server events from external services.

11. A system for controlled transmission of computer server event notifications, the system comprising:

at least one processor; and

at least one data storage comprising instructions which, when executed by the at least one processor, cause the at least one processor to perform a method comprising:

receiving, by a notification server, a subscription registration request from a partner system, the subscription registration request comprising at least one event type;

generating, by the notification server, a notification associated with one or more computer server events of the at least one event type in accordance with a quantity threshold indicating a number of server events to associate with the notification, the quantity threshold calculated based on at least one of the at least one event type, the partner system, and a current time;

transmitting, by the notification server, the notification to the partner system in accordance with a time threshold indicating a predetermined time period to associate with the notification, the time threshold calculated based on at least one of the at least one event type, the partner system, and a current time;

receiving, by the notification server, a request for computer server event details from the partner system; and

transmitting, by the notification server, the computer server event details to the partner system in response to the received request.

12. The system of claim 11 , wherein the time threshold defines a length of a time period between two consecutive notifications.

13. The system of claim 12 , wherein the quantity threshold defines a minimum number of computer server events to include in the notification.

14. The system of claim 13 , wherein, if the time threshold is reached before the quantity threshold is reached, the notification is transmitted to the partner system before the quantity threshold is reached.

15. The system of claim 12 , wherein the quantity threshold defines a maximum number of computer server events to include in the notification.

16. The system of claim 15 , wherein, if the quantity threshold is reached before the time threshold is reached, the notification is transmitted to the partner system before the time threshold is reached.

17. A non-transitory computer readable medium for controlled transmission of computer server event notifications, the non-transitory computer readable medium comprising instructions which, when executed by at least one processor, cause the at least one processor to perform a method comprising:

receiving, by a notification server, a subscription registration request from a partner system, the subscription registration request comprising at least one event type;

generating, by the notification server, a notification associated with one or more computer server events of the at least one event type in accordance with a quantity threshold indicating a number of server events to associate with the notification, the quantity threshold calculated based on at least one of the at least one event type, the partner system, and a current time;

transmitting, by the notification server, the notification to the partner system in accordance with a time threshold indicating a predetermined time period to associate with the notification, the time threshold calculated based on at least one of the at least one event type, the partner system, and a current time;

receiving, by the notification server, a request for computer server event details from the partner system; and

transmitting, by the notification server, the computer server event details to the partner system in response to the received request.

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

publishing, by the notification server, an application programming interface (API) for secure communication with the partner system over a computer network, the API corresponding to an API published by a service gateway,

wherein the notification is transmitted over the computer network by way of the API published by the service gateway.

19. The non-transitory computer readable medium of claim 18 , wherein the API published by the service gateway include features for secure transmission of notifications.

20. The non-transitory computer readable medium of claim 19 , wherein the features for secure transmission of notifications include one or more of message authentication codes (MAC), JavaScript Object Notation (JSON) Web Tokens (JWT), and Hypertext Transfer Protocol Secure (HTTPS).

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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 27, 2019
From: PAWASKAR, SACHIN
To: VANTIV, LLC
Reel/Frame 051127/0915 →
CHANGE OF NAME Recorded Nov 27, 2019
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 051142/0206 →
Continuity (3)
Continuation 16391838 · Apr 23, 2019
Continuation 15368162 · Dec 2, 2016
Related Publication 20200099571A1 · Mar 26, 2020
Cited By (1)
US 12,476,863