# US 12,008,585 B2 · System, method, and computer program product for real-time payment gateway event monitoring > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,008,585 B2 - Document ID: US12008585B2 - Status: Granted - Kind: B2 - Application number: 17/947,499 - Filed: 2022-09-19 - Published: 2023-01-19 - Granted: 2024-06-11 - Earliest claimed: 2019-08-16 - Assignees: Visa International Service Association - Applicants: Visa International Service Association - Inventors: Anurag Gupta; Jagadeesh Saravanan; Richa Singh - Web page: https://patentgrep.com/patent/US12008585B2 ## CPC - G06Q 30/0185: {Product, service or business identity fraud} - G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links} - G06Q 20/027: {involving a payment switch or gateway} - G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems - G06Q 20/12: specially adapted for electronic shopping systems - G06Q 20/20: Point-of-sale [POS] network systems - G06Q 20/202: {Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR} - G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction} - G06Q 20/4016: {involving fraud or risk level assessment in transaction processing} - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Described are a system, method, and computer program product for real-time payment gateway event monitoring. The method includes receiving input data from a merchant system including an application URL associated with a merchant control interface having a web socket programmed and/or configured to persistently listen for HTTP POST messages, and an event of a payment gateway system. The method also includes monitoring ongoing events of the payment gateway system associated with ongoing transaction messages communicated from point-of-sale (POS) devices to the payment gateway system and detecting the event in the ongoing events. The method further includes, in response to detection of the event, generating a HTTP POST message including event data of the event, and communicating the HTTP POST message to the application URL to cause the merchant control interface to display the event data in a chart for visual representation of the event data. ## Claims ### Claim 1 A computer-implemented method comprising: generating, with at least one processor, a notification routing table comprising at least one application URL associated with a control interface having a web socket programmed and/or configured to persistently listen for messages; monitoring, with at least one processor, ongoing events of a payment gateway system associated with ongoing transaction messages communicated to the payment gateway system; detecting, with at least one processor, at least one event in the ongoing events; and in response to detection of the at least one event: determining, with at least one processor, an application URL of the at least one application URL based on an identifier of the at least one event; generating, with at least one processor, at least one webhook comprising event data of the at least one event; and communicating, with at least one processor, the at least one webhook to the application URL to cause the control interface to execute an action based on the event data of the at least one webhook. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the notification routing table comprises a plurality of application URLs each associated with one or more events, and wherein the at least one webhook is generated based on the notification routing table and communicated to the application URL based on an association of the application URL with the identifier of the at least one event in the notification routing table. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein the at least one event comprises at least one recurring event, the method further comprising continually monitoring, with at least one processor, the ongoing events to generate a plurality of webhooks triggered from the at least one recurring event, wherein each webhook of the plurality of webhooks is associated with an instance of the at least one recurring event. ### Claim 4 (depends on 3) The computer-implemented method of claim 3, further comprising: storing, with at least one processor in a database, additional event data associated with the plurality of webhooks triggered from the at least one recurring event; and generating, with at least one processor, display data configured to cause the control interface to display searchable records comprising the additional event data. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, wherein the ongoing events comprise authorization request messages, the at least one event comprises detection of a fraudulent authorization request message, and the at least one webhook comprises a categorization of the at least one event as fraudulent, the at least one webhook further configured to cause a merchant system to execute a fraud mitigation process. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, wherein the at least one webhook is generated and communicated to the application URL immediately after detection of the at least one event. ### Claim 7 (depends on 6) The computer-implemented method of claim 6, wherein the at least one webhook is further configured to cause the web socket of the control interface to generate a message to at least one point-of-sale (POS) device identifying the at least one event immediately after detecting the at least one webhook. ### Claim 8 A system comprising at least one server computer including at least one processor, the at least one server computer programmed and/or configured to: generate a notification routing table comprising at least one application URL associated with a control interface having a web socket programmed and/or configured to persistently listen for messages; monitor ongoing events of a payment gateway system associated with ongoing transaction messages communicated to the payment gateway system; detect at least one event in the ongoing events; and in response to detection of the at least one event: determine an application URL of the at least one application URL based on an identifier of the at least one event; generate at least one webhook comprising event data of the at least one event; and communicate the at least one webhook to the application URL to cause the control interface to execute an action based on the event data of the at least one webhook. ### Claim 9 (depends on 8) The system of claim 8, wherein the notification routing table comprises a plurality of application URLs each associated with one or more events, and wherein the at least one webhook is generated based on the notification routing table and communicated to the application URL based on an association of the application URL with the identifier of the at least one event in the notification routing table. ### Claim 10 (depends on 8) The system of claim 8, wherein the at least one event comprises at least one recurring event, wherein the at least one server computer is further programmed and/or configured to continually monitor the ongoing events to generate a plurality of webhooks triggered from the at least one recurring event, wherein each webhook of the plurality of webhooks is associated with an instance of the at least one recurring event. ### Claim 11 (depends on 10) The system of claim 10, wherein the at least one server computer is further programmed and/or configured to: store additional event data associated with the plurality of webhooks triggered from the at least one recurring event; and generate display data configured to cause the control interface to display searchable records comprising the additional event data. ### Claim 12 (depends on 8) The system of claim 8, wherein the ongoing events comprise authorization request messages, the at least one event comprises detection of a fraudulent authorization request message, and the at least one webhook comprises a categorization of the at least one event as fraudulent, the at least one webhook further configured to cause a merchant system to execute a fraud mitigation process. ### Claim 13 (depends on 8) The system of claim 8, wherein the at least one webhook is generated and communicated to the application URL immediately after detection of the at least one event. ### Claim 14 (depends on 13) The system of claim 13, wherein the at least webhook is further configured to cause the web socket of the control interface to generate a message to at least one point-of-sale (POS) device identifying the at least one event immediately after detecting the at least one webhook. ### Claim 15 A computer program product comprising at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to: generate a notification routing table comprising at least one application URL associated with a control interface having a web socket programmed and/or configured to persistently listen for messages; monitor ongoing events of a payment gateway system associated with ongoing transaction messages communicated to the payment gateway system; detect at least one event in the ongoing events; and in response to detection of the at least one event: determine an application URL of the at least one application URL based on an identifier of the at least one event; generate at least one webhook comprising event data of the at least one event; and communicate the at least one webhook to the application URL to cause the control interface to execute an action based on the event data of the at least one webhook. ### Claim 16 (depends on 15) The computer program product of claim 15, wherein the notification routing table comprises a plurality of application URLs each associated with one or more events, and wherein the at least one webhook is generated based on the notification routing table and communicated to the application URL based on an association of the application URL with the identifier of the at least one event in the notification routing table. ### Claim 17 (depends on 15) The computer program product of claim 15, wherein the at least one event comprises at least one recurring event, wherein the program instructions further cause the at least one processor to continually monitor the ongoing events to generate a plurality of webhooks triggered from the at least one recurring event, wherein each webhook of the plurality of webhooks is associated with an instance of the at least one recurring event. ### Claim 18 (depends on 17) The computer program product of claim 17, wherein the program instructions further cause the at least one processor to: store additional event data associated with the plurality of webhooks triggered from the at least one recurring event; and generate display data configured to cause the control interface to display searchable records comprising the additional event data. ### Claim 19 (depends on 15) The computer program product of claim 15, wherein the ongoing events comprise authorization request messages, the at least one event comprises detection of a fraudulent authorization request message, and the at least one webhook comprises a categorization of the at least one event as fraudulent, the at least one webhook further configured to cause a merchant system to execute a fraud mitigation process. ### Claim 20 (depends on 15) The computer program product of claim 15, wherein the at least one webhook is generated and communicated to the application URL immediately after detection of the at least one event, and wherein the at least one webhook is further configured to cause the web socket of the control interface to generate a message to at least one point-of-sale (POS) device identifying the at least one event immediately after detecting the at least one webhook.