US 12,217,004 B2
Real-time named entity based transaction approval
Calvin Jun-Gong Lee, Weehawken, NJ (US); Veeral Dilip Patel, Bergenfield, NJ (US); Paul Alexander Meier, Brooklyn, NY (US); Karim Atiyeh, Miami Beach, FL (US); Ariel Petren Langer, San Marino, CA (US); Ori Ephraim Goldfield, New York, NY (US); and Geoffrey Jacques Charles, Brooklyn, NY (US)
Assigned to Ramp Business Corporation, New York, NY (US)
Filed by Ramp Business Corporation, New York, NY (US)
Filed on Jun. 17, 2021, as Appl. No. 17/351,120.
Prior Publication US 2022/0405477 A1, Dec. 22, 2022
Int. Cl. G06F 40/295 (2020.01); G06N 3/08 (2023.01); G06N 20/00 (2019.01); G06Q 30/0201 (2023.01); G06Q 40/02 (2023.01); G06V 30/414 (2022.01); G06V 30/416 (2022.01); G06F 40/205 (2020.01); G06F 40/211 (2020.01); G06F 40/279 (2020.01)
CPC G06F 40/295 (2020.01) [G06N 3/08 (2013.01); G06N 20/00 (2019.01); G06Q 30/0201 (2013.01); G06Q 40/02 (2013.01); G06V 30/414 (2022.01); G06V 30/416 (2022.01); G06F 40/205 (2020.01); G06F 40/211 (2020.01); G06F 40/279 (2020.01)] 20 Claims
OG exemplary drawing
 
7. A computer-implemented method for reducing a response time of a named entity identification process through the use of a rule management server and a separate authorization server that specializes in the efficient identification of named entities, the computer-implemented method, comprising:
receiving, by the authorizer server in communication with the rule management server, a transaction rule from a particular client, the transaction rule involving a list of one or more named entities selected by the particular client through a portal generated by a graphical user interface of a software-as-a-service (SaaS) platform;
storing, by the rule management server in communication with the SaaS platform, past transaction data associated with a plurality of clients, at least one of the clients being different from the particular client, the rule management server having a first response time in identifying a named entity from a transaction data payload;
analyzing, by the rule management server, patterns in the past transaction data to determine a named entity identification rule that is used to identify one or more named entities in the list selected by the particular client;
receiving, by the authorizer server, a transaction data payload related to a pending transaction associated with the particular client, the authorizer server configured to identify named entities in real time, the authorizer server, the authorizer server being a separate server from the rule management server, the authorizer server having a second response time in identifying a named entity from a transaction data payload, the second response time being shorter than the first response time due to the named entity identification rule;
identifying, by the authorizer server, a noisy data field in the transaction data payload, the noisy data field including a representation of a particular named entity and one or more irrelevant strings;
parsing, by the authorizer server, the representation of the particular named entity based on the named entity identification rule;
determining, by the authorizer server, whether the particular named entity is one of the named entities in the list selected by the particular client; and
conducting, by the authorizer server, a transaction evaluation to determine whether to approve the pending transaction based on the list and the transaction rule.