US 12,314,947 B2
Systems and methods for reconciling electronic transactions facilitated by a commerce platform
Girish Balasubramanian, Fremont, CA (US)
Assigned to Stripe, Inc., South San Francisco, CA (US)
Filed by Stripe, Inc., South San Francisco, CA (US)
Filed on Feb. 16, 2023, as Appl. No. 18/110,833.
Application 18/110,833 is a continuation of application No. 16/677,364, filed on Nov. 7, 2019, granted, now 11,587,082.
Prior Publication US 2023/0196359 A1, Jun. 22, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 20/00 (2012.01); G06Q 20/02 (2012.01); G06Q 20/10 (2012.01); G06Q 20/12 (2012.01); G06Q 20/20 (2012.01); G06Q 20/32 (2012.01); G06Q 20/38 (2012.01); G06Q 20/40 (2012.01); G06Q 30/06 (2023.01)
CPC G06Q 20/401 (2013.01) [G06Q 20/02 (2013.01); G06Q 20/10 (2013.01); G06Q 20/12 (2013.01); G06Q 20/20 (2013.01); G06Q 20/3224 (2013.01); G06Q 20/382 (2013.01); G06Q 30/06 (2013.01)] 11 Claims
OG exemplary drawing
 
1. A method for electronic transaction reconciliation comprising:
transmitting, from a first computing system to a second computing system using a communications network, a plurality of authorization requests to authorize a corresponding plurality of electronic transactions;
receiving, by the first computing system for each of at least some of the plurality of electronic requests, an authorization message from the second computing system that authorizes a device associated with the first computing system to perform an electronic transaction, wherein each authorization message is transmitted using the communications network and comprises a unique transaction ID that corresponds to one of the at least some of the plurality of electronic requests;
generating, by the first computing system for each unique transaction ID, an order number associated with the unique transaction ID, wherein the order number corresponding to the unique transaction ID is generated based on transmission time data of the corresponding unique transaction ID, such that a first order number for an earlier transmitted unique transaction ID is smaller than a second order number for a later transmitted unique transaction ID, and wherein the order number generated by an application programming interface (API) executed at the first computing system, the API distributed by the second computing system;
transmitting, by the first computing system to the second computing system, one or more order numbers associated with corresponding one or more unique transaction IDs;
transmitting, by the first computing system to the second computing system, a request for a settlement file that causes the second computing system to generate the settlement file comprising a plurality of unique transaction IDs, wherein each unique transaction ID is arranged according to the associated order number, such that the plurality of unique transaction IDs are ordered chronologically by time; and
receiving, by the first computing system transmitted from the second computing system in response to an ending of a predetermined time period, a settlement file message comprising the settlement file and a plurality of transaction data arranged in an order that substantially matches the order of the plurality of unique transaction IDs in the settlement file, and the settlement file further comprises: a plurality of payment amounts that the first computing system is to pay to the second computing system for each of the unique transaction IDs that correspond to the plurality of electronic requests, and a payout date for the settlement file that specifies a date by which the first computing system will pay the second computing system the payment amounts in the settlement file.