# US 2025/0094978 A1 · Systems and methods for validating client account data

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

- Number: US 2025/0094978 A1
- Document ID: US20250094978A1
- Status: Published application
- Kind: A1
- Application number: 18/968,495
- Filed: 2024-12-04
- Published: 2025-03-20
- Earliest claimed: 2022-12-01
- Assignees: The PNC Financial Services Group, Inc.
- Applicants: The PNC Financial Services Group, Inc.
- Inventors: Stephen Christopher BYERS; Howard Neil FORMAN; Janice Lynne GILL; Robert Kirk MAY; Regis John SCHRANZ
- Web page: https://patentgrep.com/patent/US20250094978A1

## CPC

- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q 20/108: {Remote banking, e.g. home banking}
- G06Q 20/326: {Payment applications installed on the mobile devices}
- G06Q 20/403: {Solvency checks}
- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- 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

A system and method for validating target account data based on inputs from a user. The system may include a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include providing an interface; receiving a first input; receiving a second input; enabling selection of an activatable element; conducting a lookup associated with the received inputs; receiving a result of the lookup; transforming the result of the lookup into a transformed result that predicts the probability of verification; and displaying transformed result to demonstrate the validity of the received inputs.

## Claims

### Claim 1

A system for validating target account data, the system comprising:
at least one processor configured to:
access a platform that enables payment initiation;
receive a first input associated with target account data;
receive a second input associated with target account data;
upon receipt of the first input and the second input, enable selection of an activatable element;
in response to selection of the activatable element, perform a lookup associated with the first input and the second input, to validate the first input and the second input;
receive a result of the lookup;
transform the result of the lookup using machine learning into a transformed result; and
present the transformed result.

### Claim at position 2

-14. (canceled)

### Claim 2 (depends on 1)

The system of claim 1, wherein the transformed result includes a validation of the first input and the second input.

### Claim 3 (depends on 1)

The system of claim 1, wherein the transformed result includes an indication of a no-results.

### Claim 4 (depends on 1)

The system of claim 1, wherein the transformed result includes a caution notification.

### Claim 5 (depends on 1)

The system of claim 1, wherein the transformed result includes at least one of a validation of the first input and the second input, an indication of a no-result, or a caution notification.

### Claim 6 (depends on 1)

The system of claim 1, wherein the lookup is conducted in a repository to validate the first input and the second input.

### Claim 7 (depends on 6)

The system of claim 6, wherein the repository is a national repository.

### Claim 8

A system for validating target account data, the system comprising:
at least one processor configured to:
access a platform that enables payment initiation;
receive a first input associated with target account data;
receive a second input associated with target account data;
upon receipt of the first input and the second input, enable selection of an activatable element;
in response to selection of the activatable element, perform a first lookup in a first repository, to validate the first input and the second input;
upon performance of the first lookup, perform a second lookup in a second repository, to validate the first input and the second input; and
present a result of the first lookup and the second lookup.

### Claim 9 (depends on 8)

The system of claim 8, wherein the processor is further configured to:
receive the result of the first lookup and the second lookup;
transform the result of the first lookup and the second lookup using machine learning into a transformed result; and
present the transformed result.

### Claim 10

A system for validating target account data, the system comprising:
at least one processor configured to:
access a platform that enables payment initiation;
receive a first input associated with target account data;
receive a second input associated with target account data;
enable selection of an activatable element;
in response to selection of the activatable element, perform a lookup associated with the first input and the second input, to validate the first input and the second input;
receive a result of the lookup;
transform the result of the lookup using machine learning into a transformed result;
present a result of the lookup; and
cause a display of a tooltip, wherein the tooltip provides data associated with the result.

### Claim 11 (depends on 10)

The system of claim 10, wherein the data provided by the tooltip is instructional information.

### Claim 12

A system for validating target account data, the system comprising:
at least one processor configured to:
access a platform that enables payment initiation;
receive a first input associated with target account data;
receive a second input associated with target account data;
enable selection of an activatable element;
in response to selection of the activatable element, perform a lookup associated with the first input and the second input, to validate the first input and the second input;
present a result of the lookup, wherein the result includes a caution;
wherein the at least one processor is further configured to cause the presentation of a pop-up window on a user device upon presentation of the result.

### Claim 13 (depends on 12)

The system of claim 12, wherein the result includes a no-result.

### Claim 14

A system for validating target account data, the system comprising:
at least one processor configured to:
access a platform that enables repetitive payment initiation;
receive a first input associated with target account data;
receive a second input associated with target account data;
upon receipt of the first input and the second input, automatically perform a lookup in a repository, to validate the first input and the second input; and
present a result of the lookup.

### Claim 15

A system for validating target account data, the system comprising:
a memory storing instructions; and
at least one processor configured to execute the stored instructions to:
generate a platform that enables payment initiation on an endpoint device;
access the platform that enables payment initiation;
receive, through the endpoint device, a first input associated with target account data;
receive, through the endpoint device, a second input associated with target account data;
upon receipt of the first input and the second input, enable selection of an activatable element;
in response to selection of the activatable element, transmit the first input and the second input to a server;
perform a lookup associated with the first input and the second input, to validate the first input and the second input, wherein the lookup is conducted in a national shared database repository to validate the first input and the second input;
receive a result of the lookup from the server;
transform the result of the lookup using machine learning into a transformed result; and
present the transformed result on the endpoint device.

### Claim 16 (depends on 15)

The system of claim 15, wherein the lookup further comprises:
comparing the first input and the second input with data stored in the national shared database repository.

### Claim 17 (depends on 16)

The system of claim 16, wherein the at least one processor is further configured to compare the first input and the second input with data stored in the national repository using fuzzy logic.

### Claim 18 (depends on 15)

The system of claim 15, wherein the lookup results in a match between the data in the national shared database repository and at least one of the first input and the second input.

### Claim 19 (depends on 15)

The system of claim 15, wherein the transformed result includes a validation of at least one of the first input or the second input.

### Claim 20 (depends on 19)

The system of claim 19, wherein the transformed result is presented to indicate the validation of at least one of the first input or the second input.

### Claim 21 (depends on 20)

The system of claim 20, wherein the transformed result presented to indicate the validation of at least one of the first input and the second input further includes an indication of a caution.

### Claim 22 (depends on 21)

The system of claim 21, wherein the indication of caution includes a level of caution.

### Claim 23 (depends on 15)

The system of claim 15, wherein the at least one processor is further configured to display a pop-up window on a user device to present the transformed result.

### Claim 24 (depends on 20)

The system of claim 20, wherein the transformed result includes an indication of a no-results.

### Claim 25 (depends on 15)

The system of claim 15, wherein the lookup results in no matches between the data in the national shared database repository and one of the first input and the second input.

### Claim 26 (depends on 25)

The system of claim 25, wherein the transformed result is presented to indicate no matches between the national shared database repository and one of the first input and the second input.

### Claim 27 (depends on 26)

The system of claim 26, wherein the transformed result presented to indicate no matches includes an indication of caution.

### Claim 28 (depends on 27)

The system of claim 27, wherein the indication of caution includes a level of caution.

### Claim 29

A method comprising:
accessing a platform that enables payment initiation;
receiving a first input associated with target account data;
receiving a second input associated with target account data;
enabling selection of an activatable element;
performing a lookup associated with the first input and the second input, to validate the first input and the second input; wherein the lookup is conducted in a national shared database repository to validate the first input and the second input; and
presenting a result of the lookup.

### Claim 30 (depends on 29)

The method of claim 29, further comprising:
transforming the result of the lookup using machine learning into a transformed result; and
presenting the transformed result.

### Claim 31 (depends on 30)

The method of claim 30, further comprising:
presenting an indication of validation.

### Claim 32 (depends on 30)

The method of claim 30, further comprising:
presenting an indication of no-results.

### Claim 33 (depends on 30)

The method of claim 30, further comprising:
presenting an indication of caution.
