# US 2023/0058933 A1 · Systems and methods for preventing duplicate payments

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0058933 A1
- Document ID: US20230058933A1
- Status: Published application
- Kind: A1
- Application number: 16/443,382
- Filed: 2019-06-17
- Published: 2023-02-23
- Earliest claimed: 2019-06-17
- Applicants: Wells Fargo Bank, N.A.
- Inventors: Gregory R. Connor; Gayatri Malladi
- Web page: https://patentgrep.com/patent/US20230058933A1

## CPC

- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 20/085: {involving remote charge determination or related payment systems}
- G06Q 20/227: {characterised in that multiple accounts are available, e.g. to the payer}
- G06Q 20/405: {Establishing or using transaction specific rules}
- 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

## Abstract

Systems and methods relate to detecting duplicate payments. A system includes a network interface and a processing circuit including a memory and at least one processor. The memory stores instructions that are executable by the at least one processor to provide a user interface to a user device associated with a user; receive a payment request from the user device; and retrieve, based on a first set of rules, a number of payment records from a number of systems of record. The instructions further cause the system to filter, based on a second set of rules, the retrieved number of payment records; perform a first comparison and a second comparison of attribute(s) of the payment request to attribute(s) of each of the retrieved or filtered payment records; determine, based on the comparisons, if the payment request is a duplicate payment request; and present a notification describing the duplicate payment request.

## Claims

### Claim 1

A system for detecting duplicate payments, comprising:
a network interface configured to securely communicate, via a network during a secure encrypted communication session, with a provider computing system and a user device, the provider computing system associated with an accounts provider and the user device associated with a user holding one or more accounts with the accounts provider; and
a processing circuit comprising a memory, at least one processor, a filtering circuit, and a comparison circuit, the memory storing instructions that are executable by the at least one processor to:
provide a user interface to a display device of the user device associated with the user, the user interface to receive a first payment attribute via a first user input, a second payment attribute via a second user input, and a third user input selecting an input option to submit a payment request corresponding to the first payment attribute and the second payment attribute;
establish, via the network interface, a secure encrypted communication session with the user device;
receive, from the user device via the secure encrypted communication session, the first payment attribute associated with the first user input and a second payment attribute associated with the second user input, the first user input and the second user input indicating the user's desire to transfer funds from an account held by the user with the accounts provider, wherein receiving the first payment attribute and the second payment attribute occurs prior to receiving the third user input to submit the payment request and does not comprise submitting the payment request to the provider computing system for processing over the network;
retrieve, based on receiving at least one of the first payment attribute and the second payment attribute, a subset of a plurality of first rules to apply to a first database to retrieve a first plurality of payment records, the subset of the plurality of first rules varying according to an account type associated with a first requested payment records, wherein the first plurality of payment records is a subset of payment records stored in the first database;
selectively retrieve, based on the retrieved subset of the plurality of first rules, the first plurality of payment records from a first database associated with the provider computing system by applying at least a first rule to retrieve processed payments, a second rule to retrieve pending payments, and a third rule to retrieve scheduled payments, wherein the plurality of first rules are specific to the first database;
perform, by the comparison circuit, a first comparison to determine if the first payment attribute and the second payment attribute represent an exact duplicate payment request, wherein performing the first comparison comprises comparing the first payment attribute and the second payment attribute to one or more attributes of each of the retrieved first plurality of payment records;
retrieve, based receiving on at least one of the first payment attribute and the second payment attribute and in response to determining that the first payment attribute and the second payment attribute do not represent an exact duplicate payment request, a subset of a plurality of second rules to apply to a second database that is external to the provider computing system to retrieve a second plurality of payment records, the subset of the plurality of second rules varying according to an account type associated with a second requested payment record, wherein the second plurality of payment records is a subset of payment records stored in the second database;
selectively retrieve, via a second secure encrypted communication session with the second database based on the retrieved subset of the plurality of second rules, the second plurality of payment records from the second database by applying at least a fourth rule to retrieve future recurring payments, wherein the plurality of second rules are specific to the second database and different from the plurality of first rules;
filter, by the filtering circuit, based on a type of payment record in accordance with the subset of the plurality of second rules, the second plurality of payment records to exclude one or more payment records from the second plurality of payment records, wherein the type of payment record comprises at least one of a one-time payment, recurring payment, or automatic payment;
produce, by the filtering circuit, a subset of the filtered second plurality of payment records for a second comparison including an aggregated payment record, wherein the subset of the filtered second plurality of payment records is produced by:
determining that two or more payment records of the filtered second plurality of payment records are associated with a given time period, wherein each payment record of the subset has a respective payment amount; and
producing the aggregated payment record by aggregating the respective payment amounts of the two or more payment records of the filtered second plurality of payment records associated with the time period to create a total payment amount for the two or more payment records of the filtered second plurality of payment records, wherein the total payment amount of the aggregated payment record does not match a single payment record stored on the second database;
transmit, from the filtering circuit to the comparison circuit, the produced subset of the filtered second plurality of payment records, wherein the produced subset of the filtered second plurality of payment records includes fewer payment records than the second plurality of payment records or the filtered second plurality of payment records;
perform, by the comparison circuit, a second comparison, wherein performing the second comparison comprises comparing the first payment attribute and the second payment attribute to one or more attributes of the subset of the filtered second plurality of payment records, wherein at least a first of the one or more attributes of the subset of the filtered second plurality of payment records comprises an aggregated payment amount, and wherein at least a second of the one or more attributes of the subset of the filtered second plurality of payment records comprises a type of the payment record;
determine, based on the second comparison, that the first payment attribute or the second payment attribute represent a potential duplicate payment request with the aggregated payment record;
in response to determining that the first payment attribute or the second payment attribute represent a potential duplicate payment request with the aggregated payment record, provide to the user, via the user interface provided to the display device of the user device, a pop-up notification describing the aggregated payment record, the potential duplicate payment request, and a specific payment attribute causing a potential duplicate condition, the pop-up notification comprising the input option to submit the payment request that is temporarily unselectable and grayed out to indicate to the user the user must change one or more of the first payment attribute and the second payment attribute to submit the payment request, wherein the input option is inoperable until a user input altering the first payment attribute via a first editable field or the second payment attribute via a second editable field is received within the pop-up notification;
receive, from the user via the user interface provided to the display device, a user input altering the first payment attribute or the second payment attribute within the pop-up notification, wherein the user input altering the first payment attribute or the second payment attribute alters the payment request such that the payment request is not a potential duplicate payment request with the aggregated payment record;
allow, based on the received user input, the user to select the input option to submit the payment request within the pop-up notification; and
submit, by the network interface based on the user input selecting the input option, the payment request to the provider computing system.

### Claim 2 (depends on 1)

The system of claim 1, the memory further storing instructions that are executable by the at least one processor to:
determine a total payment amount of a time interval by adding a first payment amount of a first payment record of the first plurality of payment records associated with the time interval to a second payment amount of a second payment record of the first plurality of payment records associated with the time interval,
wherein the first comparison is performed using the determined total payment amount, wherein the determined total payment amount is not associated with a single payment record of the first plurality of payment records.

### Claim 3 (depends on 1)

The system of claim 1, wherein each of the first plurality of payment records is associated with a processed payment, a pending payment, or a scheduled payment.

### Claim 4 (depends on 1)

The system of claim 1, wherein the first payment attribute and the second payment attribute include at least one of a payment funding account, a payment date, a payment amount, a payment source, and a payment destination, wherein performing the first comparison comprises comparing the first payment attribute and the second payment attribute to at least a payment funding account, a payment date, a payment amount, a payment source, and a payment destination of each of the retrieved first plurality of payment records.

### Claim 5 (depends on 4)

The system of claim 4, wherein the instructions cause the system to determine that the first payment attribute or the second payment attribute represent an exact duplicate in response to the first comparison comprising matches between the payment funding account, the payment date, the payment amount, the payment source, and the payment destination of the payment request and a payment record.

### Claim 6 (depends on 5)

The system of claim 5, wherein the pop-up notification comprises a second input option configured to cancel the payment request.

### Claim 7 (depends on 1)

The system of claim 1, wherein the first payment attribute and the second payment attribute include at least one of a payment amount and a payment destination, wherein performing the second comparison comprises comparing at least the first payment attribute and the second payment attribute to at least a payment amount and a payment destination of each of the subset of the filtered second plurality of payment records.

### Claim 8 (depends on 7)

The system of claim 7, wherein the instructions cause the system to determine that the first payment attribute or the second payment attribute represent is a potential duplicate in response to the second comparison comprising matches between the first payment attribute or the second payment attribute and the payment amount and the payment destination of at least one payment record.

### Claim 9 (depends on 8)

The system of claim 8, wherein the pop-up notification comprises a second input option configured to cancel the payment request.

### Claim 10 (depends on 1)

The system of claim 1, wherein performing the first comparison comprises comparing the first payment attribute and the second payment attribute to one or more attributes of each of the retrieved first plurality of payment records, and wherein performing the second comparison comprises comparing the first payment attribute and the second payment attribute to one or more attributes of each of the subset of the filtered second plurality of payment records.

### Claim 11

(canceled)

### Claim 12 (depends on 1)

The system of claim 1, wherein the instructions further cause the system to, in response to determining that the first payment attribute and the second payment attribute represent is a duplicate payment request with more than one payment record, display the more than one payment record hierarchically within the pop-up notification.

### Claim 13

A method of detecting duplicate payments, the method comprising:
providing a user interface to a display device of a user device associated with a user, the user interface to receive a first payment attribute via a first user input, a second payment attribute via a second user input, and a third user input selecting an input option to submit a payment request corresponding to the first payment attribute and the second payment attribute;
establishing, via a network interface, a secure encrypted communication session with the user device over a network, the network interface to communicate with a provider computing system and the user device via a cryptographic method, the provider computing system including a memory, at least one processor, a filtering circuit, and a comparison circuit, the memory storing instructions that are executable by the at least one processor;
receiving, from the user device via the secure encrypted communication session, the first payment attribute associated with the first user input and a second payment attribute associated with the second user input, the first user input and the second user input indicating the user's desire to transfer funds from an account held by the user with an accounts provider, wherein receiving the first payment attribute and the second payment attribute occurs prior to receiving the third user input to submit the payment request and does not comprise submitting the payment request to a provider computing system for processing over the network;
retrieving, based on receiving at least one of the first payment attribute and the second payment attribute, a subset of a plurality of first rules to apply to a first database to retrieve a first plurality of payment records, the subset of the plurality of first rules varying according to an account type associated with a first requested payment records, wherein the first plurality of payment records is a subset of payment records stored in the first database;
selectively retrieving, based on the retrieved subset of the plurality of first rules, a first plurality of payment records from a first database associated with the provider computing system by applying at least a first rule to retrieve processed payments, a second rule to retrieve pending payments, and a third rule to retrieve schedule payments, wherein the plurality of first rules are specific to the first database;
performing, by the comparison circuit of the provider computing system, a first comparison to determine if the first payment attribute and the second payment attribute represent an exact duplicate payment request, wherein performing the first comparison comprises comparing the first payment attribute and the second payment attribute to one or more attributes of each of the retrieved first plurality of payment records;
retrieving, based receiving on at least one of the first payment attribute and the second payment attribute and in response to determining that the first payment attribute and the second payment attribute do not represent an exact duplicate payment request, a subset of a plurality of second rules to apply to a second database that is external to the provider computing system to retrieve a second plurality of payment records, the subset of the plurality of second rules varying according to an account type associated with a second requested payment record, wherein the second plurality of payment records is a subset of payment records stored in the second database;
selectively retrieving, via a second secure encrypted communication session with the database based on the retrieved subset of the second plurality of second rules, the second plurality of payment records from the second database by applying at least a fourth rule to retrieve future payments, wherein the plurality of second rules are specific to the second database and different from the plurality of first rules;
in response to determining that the first payment attribute and the second payment attribute do not represent an the exact duplicate payment request, filtering, by the filtering circuit of the provider computing system and based on a type of payment record in accordance with the plurality of second rules, the second plurality of payment records to exclude one or more payment records from the second plurality of payment records, wherein the type of payment record comprises at least one of a one-time payment, recurring payment, or automatic payment;
producing by the filtering circuit of the provider computing system, a subset of the filtered second plurality of payment records for a second comparison including an aggregated payment record, wherein the subset of the filtered second plurality of payment records is produced by:
determining that two or more payment records of the filtered second plurality of payment records are associated with a given time period, wherein each payment record of the subset has a respective payment amount; and
producing the aggregated payment record by aggregating the payment amounts of the two or more payment records of the filtered second plurality of payment records associated with the time period to create a total payment amount for the two or more payment records of the filtered second plurality of payment records, wherein the total payment amount of the aggregated payment record does not match a single payment record stored on the second database;
transmitting, from the filtering circuit of the provider computing system to the comparison circuit of the provider computing system, the produced subset of the filtered second plurality of payment records, wherein the produced subset of the filtered second plurality of payment records includes fewer payment records than the second plurality of payment records or the filtered second plurality of payment records;
performing, by the comparison circuit of the provider computing system, a second comparison, wherein performing the second comparison comprises comparing the first payment attribute and the second payment attribute to one or more attributes of the subset of the filtered second plurality of payment records, wherein at least a first of the one or more attributes of the subset of the filtered second plurality of payment records comprises an aggregated payment amount, and wherein at least a second of the one or more attributes of the subset of the filtered second plurality of payment records comprises a type of the payment record;
determining, based on the second comparison, if the first payment attribute or the second payment attribute represent is a duplicate payment request with the aggregated payment record;
in response to determining that the first payment attribute or the second payment attribute represent is a potential duplicate payment request, providing to the user, via the user interface provided to the display device of the user device, a pop-up notification describing the aggregated payment record, the potential duplicate payment request, and a specific payment attribute causing a potential duplicate condition, the pop-up notification comprising the input option to submit the payment request that is temporarily unselectable and grayed out to indicate that the user must change one or more of the first payment attribute and the second payment attribute to submit the payment request, wherein the input option is inoperable until a user input altering the first payment attribute via a first editable field or the second payment attribute via a second editable field is received within the pop-up notification;
receiving, from the user via the user interface provided to the display device, a user input altering the first payment attribute or the second payment attribute within the pop-up notification, wherein the user input altering the first payment attribute or the second payment attribute alters the payment request such that the payment request is not a potential duplicate payment request of the aggregated payment record;
allowing, based on the received user input, the user to select the input option to submit the payment request within the pop-up notification;
submitting, by the network interface based on the user input selecting the input option, the payment request to the provider computing system.

### Claim 14 (depends on 13)

The method of claim 13 further comprising:
determining a total payment amount of a time interval by adding a first payment amount of a first payment record of the first plurality of payment records associated with the time interval to a second payment amount of a second payment record of the first plurality of payment records associated with the time interval,
wherein the first comparison is performed using the determined total payment amount, wherein the determined total payment amount is not associated with a single payment record of the first plurality of payment records.

### Claim 15 (depends on 13)

The method of claim 13, wherein each of the first plurality of payment records is associated with a processed payment, a pending payment, or a scheduled payment.

### Claim 16 (depends on 13)

The method of claim 13, wherein the first payment attribute and the second payment attribute include at least one of a payment funding account, a payment date, a payment amount, a payment source, and a payment destination, wherein performing the first comparison comprises comparing the first payment attribute and the second payment attribute to at least a payment funding account, a payment date, a payment amount, a payment source, and a payment destination of each of the retrieved first plurality of payment records or the filtered first plurality of payment records.

### Claim 17 (depends on 13)

The method of claim 13, wherein the first payment attribute and the second payment attribute include at least one of a payment amount and a payment destination, wherein performing the second comparison comprises comparing the first payment attribute and the second payment attribute to at least a payment amount and a payment destination of the subset of the filtered second plurality of payment records.

### Claim 18 (depends on 13)

The method of claim 13, wherein the first payment attribute or the second payment attributer represent a duplicate payment request with more than one payment record, and wherein the method further comprises displaying the more than one payment record hierarchically within the pop-up notification.

### Claim 19 (depends on 13)

The method of claim 13, wherein performing the first comparison comprises comparing the first payment attribute and the second payment attribute to one or more attributes of each of the retrieved first plurality of payment records, and wherein performing the second comparison comprises comparing the first payment attribute and the second payment attribute to one or more attributes of each of the subset of the filtered second plurality of payment records.

### Claim 20

(canceled)

### Claim 21

A duplicate payment detection system, comprising:
a network interface configured to communicate, via a network during an encrypted communication session, with a provider computing system and a user device, the provider computing system associated with an accounts provider and the user device associated with a user holding one or more accounts with the accounts provider; and
a processing circuit comprising a memory, at least one processor, a filtering circuit, and a comparison circuit the memory storing instructions that are executable by the at least one processor to:
provide a user interface to a display device of the user device associated with the user, the user interface to receive a first payment attribute via a first user input, a second payment attribute via a second user input, and a third user input selecting an input option to submit a payment request corresponding to the first payment attribute and the second payment attribute;
establish, via the network interface, a secure encrypted communication session with the user device;
receive, from the user device via the secure encrypted communication session, the first payment attribute associated with the first user input and a second payment attribute associated with the second user input, the first user input and the second user input indicating the user's desire to transfer funds from an account held by the user with the accounts provider, wherein receiving the first payment attribute and the second payment attribute occurs prior to receiving the third user input to submit the payment request and does not comprise submitting the payment request to the provider institution computing system for processing over the network;
retrieve, based on receiving at least one of the first payment attribute and the second payment attribute, a subset of a plurality of first rules to apply to a first database to retrieve a first plurality of payment records, the subset of the plurality of first rules varying according to an account type associated with a first requested payment records, wherein the first plurality of payment records is a subset of payment records stored in the first database;
selectively retrieve, based on the retrieved subset of the plurality of first rules, the first plurality of payment records from a plurality of systems of record associated with the provider computing system by applying at least a first rule to retrieve processed payments, a second rule to retrieve pending payments, and a third rule to retrieve scheduled payments, wherein the plurality of first rules are specific to the provider computing system;
compare, by the comparison circuit, the first payment attribute and the second payment attribute a to one or more attributes of each of the retrieved plurality of payment records to determine if the first payment attribute and the second payment attribute represent an exact duplicate payment request;
determine the first payment attribute and the second payment attribute do not represent an exact duplicate payment request in response to determining that the one or more attributes of each of the received first plurality of payment records do not match each of the first payment attribute and the second payment attribute;
retrieve, based receiving on at least one of the first payment attribute and the second payment attribute and in response to determining that the first payment attribute and the second payment attribute do not represent an exact duplicate payment request, a subset of a plurality of second rules to apply to a second database that is external to the provider computing system to retrieve a second plurality of payment records, the subset of the plurality of second rules varying according to an account type associated with a second requested payment record, wherein the second plurality of payment records is a subset of payment records stored in the second database;
selectively retrieve, via a second secure encrypted communication session with the second database based on the retrieved subset of the plurality of second rules, the second plurality of payment records from the second database;
filter, by the filtering circuit, based on a type of payment record and a given time period in accordance with the subset of the plurality of second rules comprising a fourth rule, the second plurality of payment records to exclude one or more payment records from the plurality of payment records outside of the given time period by applying at least the fourth rule to identify future recurring payments, wherein the second plurality of payment records are retrieved from a second database that is external to the provider computing system in response to the determination that the payment request is not an exact duplicate payment request;
prepare the second plurality of payment records for comparison to the first payment attribute and the second payment attribute based on the type of the second plurality of payment records in accordance with the plurality of second rules, by producing, by the filtering circuit, a subset of the filtered second plurality of payment records for a second comparison including an aggregated payment record, wherein the subset of the second plurality of payment records is produced by:
determining that two or more payment records of the subset of the filtered second plurality of payment records are associated with a given time period, wherein each payment record of the subset of the filtered second plurality of payment records has a respective payment amount; and
producing the aggregated payment record by aggregating the respective payment amounts of the two or more of the filtered second plurality of payment records associated with the time period to create a total payment amount for the two or more of the filtered second plurality of payment records, wherein the total payment amount of the aggregated payment record does not match a single payment record stored on the second database;
compare, by the comparison circuit, the first payment attribute and the second payment attribute to one or more attributes of the prepared, filtered second plurality of payment records to determine if the first payment attribute or the second payment attribute represents a potential duplicate payment request, wherein at least a first of the one or more attributes of the prepared, filtered second plurality of payment records comprises an aggregated payment amount, wherein the aggregated payment amount is not associated with a single payment record of the plurality of second payment records;
determine the first payment attribute or the second payment attribute represents a potential duplicate payment request in response to one or more of the first payment attribute or the second payment attribute matching the one or more attributes of the aggregated payment record;
in response to determining that the first payment attribute or the second payment attribute represents a potential duplicate payment request, provide to the user, via the user interface provided to the display device of the user device, a pop-up notification describing the aggregated payment record, the potential duplicate payment request, and a specific payment attribute causing a potential duplicate condition, the pop-up notification comprising an input option configured to submit the payment request that is temporarily unselectable and grayed out to indicate that the user must change one or more of the first payment attribute or the second payment attribute to submit the payment request, wherein the input option is inoperable until a user input altering the first payment attribute via a first editable field or the second payment attribute via a second editable field request is received within the pop-up notification;
receive, from the user via the user interface provided to the display device, a user input altering the first payment attribute or the second payment attribute within the pop-up notification, wherein the user input altering the first payment attribute or the second payment attribute alters the payment request such that the payment request is not a potential duplicate payment request with the aggregated payment record;
allow, based on the received user input, the user to select the input option to submit the payment request within the pop-up notification; and
submit, by the network interface based on the user input selecting the input option, the payment request to the provider computing system.

### Claim 22 (depends on 21)

The system of claim 21, the memory further storing instructions that are executable by the at least one processor to:
determine a total payment amount of a time interval by adding a first payment amount of a first payment record of the first plurality of payment records associated with the time interval to a second payment amount of a second payment record of the first plurality of payment records associated with the time interval,
wherein the first comparison is performed using the determined total payment amount, wherein the determined total payment amount is not associated with a single payment record of the first plurality of payment records.

### Claim 23 (depends on 22)

The system of claim 22, wherein the notification comprises a second input option configured to cancel the payment request.

### Claim 24 (depends on 21)

The system of claim 21, wherein each of the subset of the plurality of first rules and the subset of the plurality of second rules is based on at least one of identities of the plurality of systems of record, payment types of the plurality of payment records, or account types of the plurality of payment records.

### Claim 25 (depends on 21)

The system of claim 21, wherein each of the first plurality of payment records and the second plurality of payment records is associated with a processed payment, a pending payment, a scheduled payment, or a future recurring payment.

### Claim 26 (depends on 21)

The system of claim 21, wherein the first payment attribute and the second payment attribute include at least one of a payment funding account, a payment date, a payment amount, a payment source, and a payment destination, wherein the comparing the first payment attribute and the second payment attribute to one or more attributes of each of the retrieved first payment records includes comparing the first payment attribute and the second payment attribute to at least a payment funding account, a payment date, a payment amount, a payment source, and a payment destination of each of the retrieved first plurality of payment records.

### Claim 27 (depends on 21)

The system of claim 21, wherein the first payment attribute and the second payment attribute include at least one of a payment amount and a payment destination, wherein comparing the first payment attribute and the second payment attribute to one or more attributes of each of the filtered plurality of payment records includes comparing the first payment attribute and the second payment attribute to at least a payment amount and a payment destination of each of the filtered second plurality of payment records.
