IP Library Granted Patent US 12,314,947
Granted Patent B2
US 12,314,947 · App. 18/110,833 · Granted May 27, 2025

Systems and methods for reconciling electronic transactions facilitated by a commerce platform

Inventor: Girish Balasubramanian (Fremont, CA)
Assignee: Stripe, Inc.
G06Q20/401G06Q20/02G06Q20/10G06Q20/12G06Q20/20G06Q20/3224G06Q20/382G06Q30/06
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,314,947
App. No.
18/110,833
Granted
May 27, 2025
Kind
B2
Abstract

A method and apparatus for reconciling electronic transactions facilitated by a commerce platform are described. The method may include receiving, the commerce platform, requests from a merchant system to authorize a plurality of financial transactions. The method may also include transmitting an authorization to the merchant system authorizing the merchant system to perform the financial transaction. The authorization may include a unique transaction identification (ID) corresponding to the request. The method may also include receiving from the merchant system, for each transaction ID, an order number associated with the transaction ID. The method may also include generating a settlement file comprising the transaction IDs. Each transaction ID may be arranged in an order in the settlement file according to its associated order number. The method may also include transmitting the settlement file to the merchant device.

Claims (34)

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.

2. The method of claim 1 , further comprising:

performing, by the first computing system with the second computing system, a synchronization process of a clock of the first computing system with a transaction clock of the second computing system, the transaction clock used for transaction identification (ID) generation by the second computing system, and the transaction clock indicates a time when electronic transactions occur.

3. The method of claim 1 , wherein transmitting, by the first computing system to the second computing system, the one or more order numbers associated with corresponding one or more unique transaction IDs further comprises sending order number and unique transaction ID pairs to the second computing system.

4. The method of claim 1 , wherein the corresponding plurality of electronic transactions comprises purchases, discounts, refunds, charge backs, or a combination thereof performed by the second computing system on behalf of the first computing system.

5. A non-transitory computer readable storage medium including instructions that, when executed by a processor, cause the processor to perform a method for electronic transaction reconciliation, the method 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.

6. The non-transitory computer readable storage medium of claim 5 , further comprising:

performing, by the first computing system with the second computing system, a synchronization process of a clock of the first computing system with a transaction clock of the second computing system, the transaction clock used for transaction identification (ID) generation by the second computing system, and the transaction clock indicates a time when electronic transactions occur.

7. The non-transitory computer readable storage medium of claim 5 , wherein transmitting, by the first computing system to the second computing system, the one or more order numbers associated with corresponding one or more unique transaction IDs further comprises sending order number and unique transaction ID pairs to the second computing system.

8. The non-transitory computer readable storage medium of claim 5 , wherein the corresponding plurality of electronic transactions comprises purchases, discounts, refunds, charge backs, or a combination thereof performed by the second computing system on behalf of the first computing system.

9. A system that reconciles electronic transactions, the system comprising:

a memory that stores user commerce account information; and

a processor coupled with the memory configured to:

transmit, 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;

receive, 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;

generate, 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;

transmit, by the first computing system to the second computing system, one or more order numbers associated with corresponding one or more unique transaction IDs;

transmit, 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

receive, 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.

10. The system of claim 9 , further comprising the processor configured to:

performing, by the first computing system with the second computing system, a synchronization process of a clock of the first computing system with a transaction clock of the second computing system, the transaction clock used for transaction identification (ID) generation by the second computing system, and the transaction clock indicates a time when electronic transactions occur.

11. The system of claim 9 , wherein transmitting, by the first computing system to the second computing system, the one or more order numbers associated with corresponding one or more unique transaction IDs further comprises sending order number and unique transaction ID pairs to the second computing system.

Assignments (1)
CHANGE OF NAME Recorded Jan 30, 2026
From: STRIPE, INC.
To: STRIPE, LLC
Reel/Frame 074572/0338 →
Continuity (2)
Continuation 16677364 · Nov 7, 2019
Related Publication 20230196359A1 · Jun 22, 2023
References Cited (30)
US 9195984B1 · Spector · 2015 [cited by examiner]
US 20020087467A1 · Mascavage, III · 2002 [cited by examiner]
US 20030126075A1 · Mascavage, III · 2003 [cited by examiner]
US 20060059073A1 · Walzak · 2006 [cited by examiner]
US 20080120129A1 · Seubert · 2008 [cited by examiner]
US 20080272188A1 · Keithley · 2008 [cited by examiner]
US 20120290379A1 · Hoke · 2012 [cited by examiner]
US 20120290382A1 · Martin · 2012 [cited by examiner]
US 20120290400A1 · Hoke · 2012 [cited by examiner]
US 20130275296A1 · Tietzen · 2013 [cited by examiner]
US 20140025578A1 · Evans · 2014 [cited by examiner]
US 20150154579A1 · Teicher · 2015 [cited by examiner]
US 20150317668A1 · Tietzen · 2015 [cited by examiner]
US 20170232300A1 · Tran · 2017 [cited by examiner]
US 20180078843A1 · Tran · 2018 [cited by examiner]
US 20180117446A1 · Tran · 2018 [cited by examiner]
US 20180264347A1 · Tran · 2018 [cited by examiner]
US 20180285840A1 · Hasan · 2018 [cited by examiner]
US 20190130462A1 · Tietzen · 2019 [cited by examiner]
US 20190318402A1 · Schulz · 2019 [cited by examiner]
US 20190361917A1 · Tran · 2019 [cited by examiner]
US 20200151804A1 · Butters · 2020 [cited by examiner]
US 20200410559A1 · Qaudeer · 2020 [cited by examiner]
Pay-Cloak: A Biometric Back Cover for Smartphone (Year: 2017). [cited by examiner]
Instant payment versus smartphone payment: The big fight?, (Year: 2017). [cited by examiner]
Notice of Allowance dated Oct. 26, 2022 for U.S. Appl. No. 16/677,364, 16 pages. [cited by applicant]
Non-final Office Action mailed Sep. 21, 2021 in U.S. Appl. No. 16/677,364, filed Nov. 7, 2019 (U.S. Pat. No. 11,587,082 issued Feb. 21, 2023). [cited by applicant]
Final Office Action mailed Feb. 4, 2022 in application No. U.S. Appl. No. 16/677,364, filed Nov. 7, 2019 (U.S. Pat. No. 11,587,082 issued Feb. 21, 2023). [cited by applicant]
Inter-Bank Payment System on Enterprise Blockchain Platform (Year: 2018). [cited by applicant]
Implementation of Blockchain in Financial Sector to Improve Scalability (Year: 2019). [cited by applicant]