	US 11,887,079 B2
	Central hub reconciliation system and method
Alexander Godshall, Miami, FL (US); Ximena Bellido Hoefken, Mountain View, CA (US); Juliette Metzger, New York, NY (US); Khyati Shah, Mountain View, CA (US); and Saurabh Chopra, San Francisco, CA (US)
Assigned to Visa International Service Association, San Francisco, CA (US)
Filed by Visa International Service Association, San Francisco, CA (US)
Filed on Mar. 9, 2021, as Appl. No. 17/196,849.
Claims priority of provisional application 62/987,117, filed on Mar. 9, 2020.
Prior Publication US 2021/0279698 A1, Sep. 9, 2021
Int. Cl. G06Q 20/10 (2012.01); G06Q 20/38 (2012.01); G06Q 20/40 (2012.01)

CPC G06Q 20/102 (2013.01) [G06Q 20/3821 (2013.01); G06Q 20/401 (2013.01)]

9 Claims

1. A method comprising:

providing, by a server computer, an API to a request realization computer for establishing a secure communication channel between the server computer and the request realization computer;

receiving, by a server computer, an encrypted data file from a request realization computer using the API previously provided by the server computer;

decrypting, by the server computer, the encrypted data file using a decryption key stored by the server computer to obtain a data file comprising remittance data and payment data, wherein the remittance data is associated with a request provided from a request originating computer to the request realization computer, wherein the payment data includes a plurality of individual payment data associated with a plurality of authorizing entities;

storing, by the server computer, the data file in a database, wherein storing the data file triggers generation of a unique identifier;

generating, by the server computer, the unique identifier for the data file using a number generator, wherein the data file is associated with the unique identifier regardless of the remittance data and the payment data of the data file being associated with one or more transactions;

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;

providing, by the server computer, confirmation of validation and the unique identifier to the request realization computer;

storing, by the server computer, the corrected data file in the database;

for each individual payment data:

generating, by the server computer, a payment information file including the individual payment data and the unique identifier according to a format specification of a corresponding authorizing entity computer, wherein the unique identifier is inserted in a message field of the payment information file;

providing, by the server computer, the payment information file including the individual payment data and the unique identifier to the corresponding authorizing entity computer requesting payment on behalf of the request realization computer, wherein the authorizing entity computer, upon authorizing the request associated with the individual payment data, provides the individual payment data and the unique identifier to the request originating computer;

receiving, by the server computer, communication from the authorizing entity computer regarding processing of the individual payment data and the unique identifier;

formatting, by the server computer, the remittance data into a reformatted remittance data based on a format specification of the request originating computer;

providing, by the server computer, the reformatted remittance data and the unique identifier to the request originating computer,

wherein the data file including the remittance data and the payment data is input to the server computer without the unique identifier, and all data related to the data file is output from the server computer with the unique identifier,

progressively creating, by the server computer, a repository for linking each received remittance data to each received payment data based on communications of the server computer with (1) the request originating computer, (2) the request realization computer, and (3) the authorizing entity computer; and

granting access, by the server computer, to the request realization computer, the request originating computer, and the authorizing entity computer to the repository using the unique identifier, wherein the access is limited to the data file associated with the unique identifier provided by the request realization computer or the request originating computer while remaining data in the repository is blocked from access.