# US 10,320,603 B1 · Systems and methods for registering computer server event notifications > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,320,603 B1 - Document ID: US10320603B1 - Status: Granted - Kind: B1 - Application number: 15/368,162 - Filed: 2016-12-02 - Granted: 2019-06-11 - Earliest claimed: 2016-12-02 - Assignees: Worldpay, LLC - Applicants: Vantiv, LLC - Inventors: Sachin Pawaskar - Web page: https://patentgrep.com/patent/US10320603B1 ## CPC - H04L 41/06: Management of faults, events, alarms or notifications - H04L 41/0604: using filtering, e.g. reduction of information by using priority, element types, position or time - H04L 41/069: using logs of notifications; Post-processing of notifications - H04L 41/24: {using dedicated network management hardware} - H04L 41/28: Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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 ### Claim 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. ### Claim 2 (depends on 1) The system of claim 1, wherein the APIs published by the service gateway include features for secure transmission of event notifications. ### Claim 3 (depends on 2) 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). ### Claim 4 (depends on 1) The system of claim 1, wherein the APIs published by the service gateway include interfaces for receiving computer server events from external services. ### Claim 5 (depends on 4) 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. ### Claim 6 (depends on 1) 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. ### Claim 7 (depends on 6) 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. ### Claim 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. ### Claim 9 (depends on 8) The method of claim 8, wherein the APIs published by the service gateway include features for secure transmission of event notifications. ### Claim 10 (depends on 9) 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). ### Claim 11 (depends on 8) The method of claim 8, wherein the APIs published by the service gateway include interfaces for receiving computer server events from external services. ### Claim 12 (depends on 11) 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. ### Claim 13 (depends on 8) 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. ### Claim 14 (depends on 13) 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. ### Claim 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. ### Claim 16 (depends on 15) 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). ### Claim 17 (depends on 15) 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. ### Claim 18 (depends on 17) 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. ### Claim 19 (depends on 15) 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. ### Claim 20 (depends on 19) 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.