# US 2021/0279698 A1 · Central hub reconciliation system and method

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

- Number: US 2021/0279698 A1
- Document ID: US20210279698A1
- Status: Published application
- Kind: A1
- Application number: 17/196,849
- Filed: 2021-03-09
- Published: 2021-09-09
- Earliest claimed: 2020-03-09
- Assignees: Visa International Service Association
- Applicants: Visa International Service Association
- Inventors: Alexander Godshall; Ximena Bellido Hoefken; Juliette Metzger; Khyati Shah; Saurabh Chopra
- Web page: https://patentgrep.com/patent/US20210279698A1

## CPC

- G06Q 20/102: {Bill distribution or payments}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/3821: {Electronic credentials}
- G06Q 20/387: {Payment using discounts or coupons (relating to marketing G06Q30/02)}
- 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/401: {Transaction verification}
- G06Q 20/4037: {Remote solvency checks}
- 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 method and system for central hub reconciliation is disclosed. The central hub reconciliation can provide for improved methods of reconciliation between a buyer (e.g., a request realization party) and a supplier (e.g., a request originating party). A central hub server may receive a data file comprising remittance data and payment data from a request realization computer. The remittance data is associated with a request provided from a request originating computer to the request realization computer. The central hub server ay then generate a unique identifier for the data file, and provide the payment data and the unique identifier to an authorizing entity computer requesting payment on behalf of the request realization computer. The central hub provides the remittance data and the unique identifier to the request originating computer which updates a repository using the payment data and the remittance data upon finding a match.

## Claims

### Claim 1

A method comprising:
receiving, by a server computer, a data file comprising remittance data and payment data from a request realization computer, the remittance data associated with a request provided from a request originating computer to the request realization computer;
generating, by the server computer, a unique identifier for the data file;
providing, by the server computer, the payment data and the unique identifier to an authorizing entity computer requesting payment on behalf of the request realization computer, wherein the authorizing entity computer, upon authorizing the request associated with the payment data, provides payment data and the unique identifier to the request originating computer; and
providing, by the server computer, the remittance data and the unique identifier to the request originating computer, wherein the request originating computer compares the unique identifier received from the authorizing entity computer and the unique identifier received from the server computer and updates a repository using the payment data and the remittance data upon finding a match.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
prior to generating the unique identifier, validating, by the server computer, the remittance data and the payment data;
storing, by the server computer, the data file in a database, wherein storing the data file triggers generation of the unique identifier; and
providing, by the server computer, confirmation of validation and the unique identifier to the request realization computer.

### Claim 3 (depends on 1)

The method of claim 1 further comprising:
prior to generating the unique identifier:
validating, by the server computer, the remittance data and the payment data;
determining, by the server computer, an inaccuracy in the data file;
providing, by the server computer, the unique identifier and an error message identifying the inaccuracy in the data file to the request realization computer;
receiving, by the server computer, corrected data file from the request realization computer;
validating, by the server computer, the corrected data file;
storing, by the server computer, the corrected data file in a database, wherein storing the corrected data file triggers generation of the unique identifier; and
providing, by the server computer, confirmation of validation and the unique identifier to the request realization computer.

### Claim 4 (depends on 1)

The method of claim 1, wherein the authorizing entity computer provides the payment data and the unique identifier to the request originating computer via a transport computer.

### Claim 5 (depends on 1)

The method of claim 1, wherein the server computer receives the data file from the request realization computer via a first API, and the server computer provides the remittance data and the unique identifier to the request originating computer via a second API.

### Claim 6 (depends on 1)

The method of claim 1, wherein the data file received from the request realization computer is in a first format that combines the remittance data and the payment data in a single file, wherein the method further comprises:
validating, by the server computer, the remittance data and the payment data;
storing, by the server computer, the data file in a database in a second format specific to the server computer, wherein storing the data file triggers generation of the unique identifier; and
providing, by the server computer, the remittance data and the unique identifier to the request originating computer in a third format specific to the request originating computer.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
reformatting, by the server computer, at least the remittance data from the first format to the second format, and from the second format to the third format.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
storing, by the server computer, the data file as being associated with the unique identifier at a database;
maintaining, by the server computer, a portal for accessing at least a portion of data stored at the database; and
granting, by the server computer to the request originating computer or the request realization computer access to the portal associated with the database using the unique identifier, wherein the request originating computer or the request realization computer is granted access only to the data file associated with the unique identifier.

### Claim 9 (depends on 8)

The method of claim 8, wherein the data file includes payment data associated with a plurality of authorizing entities.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
storing, by the server computer, the data file as being associated with the unique identifier at a database for a predetermined amount of time; and
expunging, by the server computer, the data file from the database upon determining that the predetermined amount of time has passed.

### Claim 11 (depends on 1)

The method of claim 1, wherein the data file includes remittance data and payment data associated with a plurality of transactions between the request originating computer and the request realization computer.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
prior to providing the payment data and the unique identifier to the authorizing entity computer and providing the remittance data and the unique identifier to the request originating computer:
validating, by the server computer, the remittance data and the payment data for each transaction in the data file;
determining, by the server computer, an inaccuracy in connection with at least one transaction the data file;
providing, by the server computer, the unique identifier and an error message identifying the inaccuracy in the data file to the request realization computer;
validating, by the server computer, the remittance data and the payment data for remaining transactions in the data file; and
storing, by the server computer, the remittance data and the payment data for the remaining transactions in the data file in a database, wherein the payment data provided to the authorizing entity computer and the remittance data provided to the request originating computer are associated with a validated transaction among the remaining transactions in the data file.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
providing, by the server computer, the remittance data and the unique identifier to the request originating computer in a file including other remittance data and unique identifiers associated with a plurality of transactions associated with a plurality of request originating computers.

### Claim 14

A server computer comprising:
a processor; and
a computer readable medium coupled to the processor, the computer readable medium comprising code that, when executed by the processor, cause the processor to:
receive a data file comprising remittance data and payment data from a request realization computer, the remittance data associated with a request provided from a request originating computer to the request realization computer;
generate a unique identifier for the data file;
provide the payment data and the unique identifier to an authorizing entity computer requesting payment on behalf of the request realization computer, wherein the authorizing entity computer, upon authorizing the request associated with the payment data, provides payment data and the unique identifier to the request originating computer; and
provide the remittance data and the unique identifier to the request originating computer, wherein the request originating computer compares the unique identifier received from the authorizing entity computer and the unique identifier received from the server computer and updates a repository using the payment data and the remittance data upon finding a match.

### Claim 15 (depends on 14)

The server computer of claim 14, wherein the code, when executed by the processor, further causes the processor to:
validate the data file;
store the data file in a database, wherein storing the data file triggers generation of the unique identifier; and
provide confirmation of validation and the unique identifier to the request realization computer.

### Claim 16 (depends on 15)

The server computer of claim 15, wherein the data file received from the request realization computer is in a first format, the data file is stored in the database in a second format specific to the server computer, and the remittance data and the unique identifier are provided to the request originating computer in a third format specific to the request originating computer.

### Claim 17 (depends on 15)

The server computer of claim 15, wherein the code, when executed by the processor, further causes the processor to:
prior to storing the data file in the database:
determine an inaccuracy in the data file;
provide the unique identifier and an error message identifying the inaccuracy in the data file to the request realization computer;
receive corrected data file from the request realization computer;
validate the corrected data file; and
store the corrected data file as the data file in the database.

### Claim 18 (depends on 15)

The server computer of claim 15, wherein the code, when executed by the processor, further causes the processor to:
maintain a portal in communication with the database; and
grant, to the request originating computer or the request realization computer, access to the portal using the unique identifier via a dedicated API, wherein the request originating computer or the request realization computer is granted access only to the data file associated with the unique identifier.

### Claim 19 (depends on 14)

The server computer of claim 14, wherein the code, when executed by the processor, further causes the processor to:
store the data file as being associated with the unique identifier at a database for a predetermined amount of time, wherein the data file is automatically removed from the database when the predetermined amount of time has passed.

### Claim 20 (depends on 14)

The server computer of claim 14, wherein the data file includes remittance data and payment data associated with a plurality of transactions between the request originating computer and the request realization computer, and
wherein the remittance data and the unique identifier are provided to the request originating computer in a single file including other remittance data and unique identifiers associated with multiple transactions associated with a plurality of request originating computers.
