IP Library Granted Patent US 10,320,603
Granted Patent B1
US 10,320,603 · App. 15/368,162 · Granted Jun 11, 2019

Systems and methods for registering computer server event notifications

Inventor: Sachin Pawaskar (Mason, OH)
Assignee: Worldpay, LLC
H04L41/06H04L41/0604H04L41/24
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,320,603
App. No.
15/368,162
Granted
Jun 11, 2019
Kind
B1
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 (68)

1. A computer system for secure transmission of computer server event notifications, the system comprising:

a service gateway configured to:

publish application programming interfaces (APIs) for secure transmission of computer server event notifications over a computer network;

a notification server configured to:

publish APIs for secure transmission of computer server event notifications corresponding to the APIs published by the service gateway;

obtain a new computer server event to report;

determine, using a hardware processor, a subscribed partner to receive an event notification of the new computer server event;

generate the event notification indicating the new computer server event, the generating comprising:

generating a header string and a payload string;

obtaining a message authentication code (MAC) key corresponding to the subscribed partner from a database; and

signing the event notification using the MAC key;

transmit, over the computer network, the event notification to the subscribed partner by way of the service gateway APIs; and

register the event notification in the database.

2. The system of claim 1 , wherein the APIs published by the service gateway include features for secure transmission of event notifications.

3. The system of claim 2 , wherein the features for secure transmission of event notifications include one or more of JSON Web Tokens (JWT) and Hypertext Transfer Protocol Secure (HTTPS).

4. The system of claim 1 , wherein the APIs published by the service gateway include interfaces for receiving computer server events from external services.

5. The system of claim 4 , wherein the notification server is further configured to:

publish APIs for receiving computer server events from external services corresponding to the APIs published by the service gateway; and

receive a new computer server event from an external service by way of the service gateway APIs.

6. The system of claim 1 , wherein the notification server is further configured to:

receive an acknowledgment of the transmitted event notification from the subscribed partner; and

set a status of the new computer server event as completed.

7. The system of claim 6 , wherein the notification server is further configured to:

retransmit the event notification to the subscribed partner when an acknowledgment is not received from the subscribed partner; and

set a status of the new computer server event as failed when a number of failed transmissions of the event notification to the subscribed partner exceeds a predetermined threshold.

8. A method of secure transmission of computer server event notifications, the method comprising:

publishing application programming interfaces (APIs) for secure transmission, over a computer network, of computer server event notifications corresponding to APIs published by a service gateway;

obtaining a new computer server event to report;

determining, using a hardware processor, a subscribed partner to receive an event notification of the new computer server event;

generating the event notification indicating the new computer server event, the generating comprising:

generating a header string and a payload string;

obtaining a message authentication code (MAC) key corresponding to the subscribed partner from a database; and

signing the event notification using the MAC key;

transmitting, over the computer network, the event notification to the subscribed partner by way of the service gateway APIs; and

registering the event notification in the database.

9. The method of claim 8 , wherein the APIs published by the service gateway include features for secure transmission of event notifications.

10. The method of claim 9 , wherein the features for secure transmission of event notifications include one or more of JSON Web Tokens (JWT) and Hypertext Transfer Protocol Secure (HTTPS).

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

12. The method of claim 11 , the method further comprising:

publishing APIs for receiving computer server events from external services corresponding to the APIs published by the service gateway; and

receiving a new computer server event from an external service by way of the service gateway APIs.

13. The method of claim 8 , the method further comprising:

receiving an acknowledgment of the transmitted event notification from the subscribed partner; and

setting a status of the new computer server event as completed.

14. The method of claim 13 , the method further comprising:

retransmitting the event notification to the subscribed partner when an acknowledgment is not received from the subscribed partner; and

setting a status of the new computer server event as failed when a number of failed transmissions of the event notification to the subscribed partner exceeds a predetermined threshold.

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:

publishing application programming interfaces (APIs) for secure transmission, over a computer network, of computer server event notifications corresponding to APIs published by a service gateway, the APIs published by the service gateway including features for secure transmission of event notifications;

obtaining a new computer server event to report;

determining, using a hardware processor, a subscribed partner to receive an event notification of the new computer server event;

generating the event notification indicating the new computer server event, the generating comprising:

generating a header string and a payload string;

obtaining a message authentication code (MAC) key corresponding to the subscribed partner from a database; and

signing the event notification using the MAC key;

transmitting, over the computer network, the event notification to the subscribed partner by way of the service gateway APIs; and

registering the event notification in the database.

16. The non-transitory computer readable medium of claim 15 , wherein the features for secure transmission of event notifications include one or more of JSON Web Tokens (JWT) and Hypertext Transfer Protocol Secure (HTTPS).

17. The non-transitory computer readable medium of claim 15 , wherein the APIs published by the service gateway include interfaces for receiving computer server events from external services.

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

publishing APIs for receiving computer server events from external services corresponding to the APIs published by the service gateway; and

receiving a new computer server event from an external service by way of the service gateway APIs.

19. The non-transitory computer readable medium of claim 15 , the method further comprising:

receiving an acknowledgment of the transmitted event notification from the subscribed partner; and

setting a status of the new computer server event as completed.

20. The non-transitory computer readable medium of claim 19 , the method further comprising:

retransmitting the event notification to the subscribed partner when an acknowledgment is not received from the subscribed partner; and

setting a status of the new computer server event as failed when a number of failed transmissions of the event notification to the subscribed partner exceeds a predetermined threshold.

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 8, 2016
From: PAWASKAR, SACHIN
To: VANTIV, LLC
Reel/Frame 040600/0417 →
Cited By (2)
US 12,388,703 US 12,476,863