IP Library › Granted Patent US 12,511,653
Granted Patent B1
US 12,511,653 · App. 17/567,600 · Granted Dec 30, 2025

Business-to-business netting

Inventors: Joseph Gregory Delong (San Antonio, TX); Steven James Schroeder (Oak Point, TX); Jonathan Huntington Rhea (North Richland Hills, TX); Alexander Benetto Nagelberg (San Antonio, TX)
Assignee: United Services Automobile Association (USAA)
G06Q20/401G06F9/46G06Q30/08G06Q40/08H04L12/1453G06Q2220/00H04L9/50
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,511,653
App. No.
17/567,600
Granted
Dec 30, 2025
Kind
B1
Abstract

Systems and methods for performing netting of business-to-business payments for settlement of running balances between parties are provided. To that end, blockchain infrastructures allow smart contracts that may be suitable for subrogation and netting operations, and the smart contracts that facilitate the operations. Application-programming interfaces (APIs) are provided that may be used to interact with the smart contracts.

Claims (40)

1 . A system, comprising:

network circuitry configured to communicate with at least one blockchain node of a blockchain system, wherein the blockchain system comprises a plurality of smart contracts;

processing circuitry;

memory comprising instructions that cause the processing circuitry to:

create a first swap request for an oracle smart contract of the plurality of smart contracts, wherein the first swap request is associated with a first party;

create a signature for the first swap request based on an identifier for the first party; and

create a transaction request to the oracle smart contract comprising the first swap request;

the blockchain system, comprising the oracle smart contract, wherein a data structure of the oracle smart contract is configured to store a plurality of swap components, each of the plurality of swap components having a corresponding signature and identifier; and wherein the oracle smart contract is configured to:

receive a set of swap requests, wherein each swap request comprises at least a respective swap identifier and a respective signature, and wherein the set of swap requests comprise swap requests from a plurality of parties;

in response to receiving the set of swap requests, store the set of swap requests via the oracle smart contract;

validate, from the oracle smart contract, each received swap request based on the received swap request's respective signature;

identify, from the oracle smart contract, a match of two or more validated swap requests of the set of swap requests based on determining a first swap identifier associated with the first swap request matches a second swap identifier associated with a second swap request, and wherein the first swap request comprises a debtor swap component and the second swap request comprises a creditor swap component; and

in response to identifying the match of two or more validated swap requests, submit a matched swap request to an accountant smart contract uniquely generated for the matched swap request; and

a plurality of accountant smart contracts, each uniquely generated for a corresponding matched swap request to provide a reduced accountant smart contract size and reduced blockchain costs, the plurality of accountant smart contracts comprising the accountant smart contract uniquely generated for the matched swap request, wherein each of the plurality of accountant smart contracts is configured to enter a swap entry on a system blockchain, wherein the swap entry comprises an indication of a netting between the debtor swap component and the creditor swap component.

2 . The system of claim 1 , wherein the memory comprises instructions to:

request validation data associated with the first party to a registry smart contract of the plurality of smart contracts; and

validate the signature based on the validation of each received swap request.

3 . The system of claim 1 , wherein the memory comprises instructions that cause the processing circuitry to create a third swap request for the oracle smart contract.

4 . The system of claim 1 , wherein creating each swap request comprises creating an individual corresponding smart contract.

5 . The system of claim 1 , wherein the accountant smart contract is associated with the first party and a second party, and is configured to:

receive the matched swap request from the oracle smart contract; and

settle the matched swap request by adjusting a balance between the first and the second party; and

wherein the memory comprises instructions to request the balance between the first and the second party from the accountant smart contract.

6 . The system of claim 5 , wherein the memory comprises instruction to create an off-chain payment transaction request to the accountant smart contract.

7 . A method, comprising;

creating a first swap request, via processing circuitry, for an oracle smart contract, wherein the first swap request is associated with a first party;

creating a signature, via the processing circuitry, for the first swap request based on an identifier for the first party;

creating a transaction request, via the processing circuitry, to the oracle smart contract comprising an indication of a transaction corresponding to the first swap request;

receiving a set of swap requests, via the oracle smart contract, wherein each swap request comprises at least a respective swap identifier and a respective signature, and wherein the set of swap requests comprises swap requests from a plurality of parties;

in response to receiving the set of swap requests, storing, via the processing circuitry, the set of swap requests via the oracle smart contract, wherein a data structure of the oracle smart contract is configured to store a plurality of swap components, each of the plurality of swap components having a corresponding signature and identifier;

validating, from the oracle smart contract, each received swap request, via the processing circuitry, based on the received swap request's respective signature; and

identifying, from the oracle smart contract, a match of two or more validated swap requests of the set of swap requests, via the processing circuitry, based on determining a first swap identifier associated with the first swap request matches a second swap identifier associated with a second swap request, and wherein the first swap request comprises a debtor swap component and the second swap request comprises a creditor swap component; and

in response to identifying the match of two or more validated swap requests, submitting, via the processing circuitry, a matched swap request to a corresponding accountant smart contract of a plurality of accountant smart contracts, wherein each of the plurality of accountant smart contracts is uniquely generated for a corresponding matched swap request to provided a reduced accountant smart contract size and reduce blockchain transaction costs and each of the plurality of accountant smart contracts is configured to enter a swap entry on a system blockchain, wherein the swap entry comprises an indication of a netting between the debtor swap component and the creditor swap component.

8 . The method of claim 7 , comprising, requesting and settling the matched swap request comprises a single blockchain transaction request.

9 . The method of claim 7 , wherein the swap requests comprise swap requests from a plurality of parties.

10 . The method of claim 7 , wherein the oracle smart contract comprises an event identifier, and wherein the oracle smart contract is created using an initial swap request comprising the event identifier.

11 . The method of claim 7 , comprising receiving results of the transaction, via the processing circuitry.

12 . The method of claim 11 , where the results of the transaction comprise an output of a member function, acknowledgement of execution of payment, or both.

13 . The method of claim 7 , wherein validating each received swap request comprises verifying, based on the signature of the first swap request, that the first party is an issuer of the first swap request.

14 . The method of claim 7 , wherein the signature is provided via one or more encryption methods.

Continuity (2)
Continuation 16261296 · Jan 29, 2019
Provisional Application 62623904 · Jan 30, 2018
References Cited (20)
US 5970479A · Shepherd · 1999 [cited by examiner]
US 6076074A · Cotton · 2000 [cited by examiner]
US 10963966B1 · Brandmaier et al. · 2021 [cited by applicant]
US 11100477B1 · Kemper et al. · 2021 [cited by applicant]
US 11216813B1 · Delong · 2022 [cited by examiner]
US 20080071664A1 · Silverman et al. · 2008 [cited by applicant]
US 20160292672A1 · Fay et al. · 2016 [cited by applicant]
US 20170186057A1 · Metnick · 2017 [cited by applicant]
US 20170308893A1 · Saraniecki · 2017 [cited by applicant]
US 20180025442A1 · Isaacson et al. · 2018 [cited by applicant]
US 20180091316A1 · Stradling · 2018 [cited by examiner]
US 20180176229A1 · Bathen · 2018 [cited by examiner]
US 20180300741A1 · Leonard · 2018 [cited by examiner]
US 20180365684A1 · Reilly et al. · 2018 [cited by applicant]
US 20190026821A1 · Bathen · 2019 [cited by examiner]
US 20190102736A1 · Hudson · 2019 [cited by applicant]
WO WO2004068293A2 · 2004 [cited by examiner]
WO WO2018127923A1 · 2018 [cited by examiner]
Blockchain—Wikipedia, Jun. 2017. [cited by examiner]
Andreas Antonopoulos, “Mastering Bitcoin”, Dec. 2014, O'Reilly Media, Inc. [cited by examiner]