Scrub and match and payee account match
AssigneeWells Fargo Bank, N.A.
InventorsSabitha Dachepalli, Remo DeLeon, Peter Rozovski
Life of this patent
Estimating the term…
Abstract
Systems and methods for processing payment requests via a series of matching operations are described. Rules that compensate for incomplete or inaccurate information are applied to customer requests and stored merchant information to create identifiers, or “tokens.” Tokens can be searched for, compared, and matched with confirmed merchant information, allowing for the identification of merchants known to financial institutions despite erroneous or missing information in the customer request.
Claims24
A financial institution computing system for processing customer requests, the system comprising:
- a first processor;
- a second processor;
- a database comprising:
- a plurality of profiles of merchant information associated with a plurality of merchants, including merchant names and remittance addresses, and
- a plurality of merchant tokens corresponding to the plurality of merchants in the database, the plurality of merchant tokens managed by one of a plurality of database entities comprising a first database entity configured to store merchant data and associated with the first processor and a second database entity configured to store merchant format mask rules and associated with the second processor;
- a user interface logic comprising machine-executable instructions stored in non-volatile memory, the instructions, when executed by at least one of the first processor and the second processor, directing the computing system to access and exchange, via a remote computing device, data over a network;
- a merchant matching logic comprising machine-executable instructions stored in non-volatile memory, the instructions, when executed by at least one of the first processor and the second processor, directing the computing system to:
- receive from a remote computing device a plurality of customer requests through the user interface logic,
- create a plurality of customer tokens from at least one of the plurality of customer requests by applying one or more rules to the plurality of customer requests based on sets of rules, wherein the at least one of the plurality of customer requests is split into the plurality of customer tokens, and
- generate a match set N by, for each of the plurality of customer tokens, performing the following operations:
- for each of the plurality of customer tokens, searching the first database entity, by executing a first set of instructions by the first processor, and the second database entity, by executing a second set of instructions by the second processor, wherein the first database entity is searched for merchant tokens that match at least one of the plurality of customer tokens based on at least one of the plurality of profiles of merchant information associated with the at least one of the plurality of customer requests, and wherein the second database entity is searched for merchant format mask rules matching a format of the one of the plurality of customer tokens;
- for each of the plurality of customer tokens, collecting corresponding merchant tokens in the database that match the customer tokens;
- transmitting at least one of the plurality of profiles of merchant information associated with the at least one of the plurality of customer requests to the remote computing device based on the match set N;
- and
- a payment processing logic comprising machine-executable instructions stored in non-volatile memory, the instructions, when executed by at least one of the first processor and the second processor, directing the computing system to prepare and cause a paper check or an electronic payment to be issued.
A computer implemented method of processing customer requests, the method comprising:
- maintaining, by a merchant matching logic communicatively coupled to a processing system comprising a first processor and a second processor, a database comprising:
- a plurality of profiles of merchant information associated with a plurality of merchants, including merchant names and remittance addresses, and
- a plurality of merchant tokens corresponding to the plurality of merchants in the database, the plurality of merchant tokens managed by one of a plurality of database entities comprising a first database entity configured to store merchant data and associated with the first processor and a second database entity configured to store merchant format mask rules and associated with the second processor;
- receiving, by a remote computing device comprising a user interface logic, a customer request;
- creating, by the merchant matching logic, a plurality of customer tokens based on the merchant information in the customer request by applying one or more rules to the customer request according to sets of rules wherein the customer request is split into the plurality of customer tokens;
- generating, by the merchant matching logic, a match set N comprising merchant tokens that match the customer tokens by:
- for each of the plurality of customer tokens, searching the first database entity, by executing a first set of instructions by the first processor, and the second database entity, by executing a second set of instructions by the second processor, wherein the first database entity is searched for merchant tokens that match at least one of the plurality of customer tokens based on at least one of the plurality of profiles of merchant information associated with the customer request, and wherein the second database entity is searched for merchant format mask rules matching a format of the one of the plurality of customer tokens;
- for each of the plurality of customer tokens, collecting merchant tokens in the database that match the customer tokens;
- and
- transmitting at least one of the plurality of profiles of merchant information associated with the customer request to the remote computing device based on the merchant tokens collected;
- instructing, by the merchant matching logic, a payment processing logic to issue a paper check or an electronic payment;
- and
- preparing and causing, by the payment processing logic, the paper check or the electronic payment to be issued.
A non-transitory computer readable media having computer-executable instructions embodied therein that, when executed by at least one processor of a financial institution computing system, cause the financial institution computing system to perform operations to issue payments from customer accounts to identified merchants, the operations comprising:
- maintain a database comprising:
- a plurality of profiles of merchant information associated with a plurality of merchants, including merchant names and remittance addresses, and
- a plurality of merchant tokens corresponding to the plurality of merchants in the database, the plurality of merchant tokens managed by one of a plurality of database entities comprising a first database entity configured to store merchant data and associated with a first processor and a second database entity configured to store merchant format mask rules and associated with a second processor;
- receive, via a remote computing device, a customer requests through a user interface logic;
- create customer tokens based on the merchant information in the customer request for each of a plurality of customer tokens, comprising searching the first database entity, by executing a first set of instructions by the first processor, and the second database entity, by executing a second set of instructions by the second processor, wherein the first database entity is searched for merchant tokens that match at least one of the plurality of customer tokens based on at least one of the plurality of profiles of merchant information associated with the customer request, and wherein the second database entity is searched for merchant format mask rules matching a format of the one of the plurality of customer tokens, thereby reducing a match set by eliminating non-matching merchants;
- for each of the plurality of customer tokens, collect merchant tokens in the database that match the customer tokens;
- transmit at least one of the plurality of profiles of merchant information associated with the customer request to the remote computing device based on the merchant tokens;
- and
- prepare and cause a paper or electronic payment to be issued.
Dependencies are inferred from the claim text.