IP Library Granted Patent US 12,348,503
Granted Patent B2
US 12,348,503 · App. 18/636,243 · Granted Jul 1, 2025

Resource transfer setup and verification

Inventor: Robert Way (Spring, TX)
Assignee: Interledger Foundation Inc.
H04L63/08G06F9/546G06Q40/04H04L67/02
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,348,503
App. No.
18/636,243
Granted
Jul 1, 2025
Kind
B2
Abstract

Systems and techniques are provided for a resource transfer setup and verification. A request for transfer conditions for a transfer of resources may be received from a first computing device. A set of transfer conditions may be generated in response to the request for transfer conditions and sent to the first computing device. The set of transfer conditions and an indication of an acceptance of the set of transfer conditions by a second computing device may be received from the first computing device. A transfer identifier for the set of transfer conditions may be generated from data from the set of transfer conditions which may specify a first sub-transfer. Transfer instructions may be sent to a third computing device, including instructions for a sub-transfer specified in the set of transfer conditions. The set of transfer conditions may be stored with the transfer identifier as a transfer record in non-volatile storage.

Claims (71)

1. A computer-implemented method performed on a data processing apparatus comprising:

generating, by a connector computing device, a set of transfer conditions in response to a request for transfer conditions;

generating, by the connector computing device, a message authentication code based on a portion of data from the set of transfer conditions;

storing, by the connector computing device, the message authentication code in the set of transfer conditions;

sending, by the connector computing device, the request for transfer conditions to a first computing device;

receiving, by the connector computing device, from the first computing device, the set of transfer conditions and an indication of an acceptance of the set of transfer conditions by a second computing device;

generating, by the connector computing device, a new message authentication code from the portion of data from the set of transfer conditions received from the first computing device;

comparing, by the connector computing device, the new message authentication code to the message authentication code and determining that the new message authentication code does not match the message authentication code; and

in response to determining that the new message authentication code does not match the message authentication code, resending, by the connector computing device, the set of transfer conditions to the first computing device.

2. The method of claim 1 , further comprising:

after resending, by the connector computing device, the set of transfer conditions to the first computing device;

receiving, by the connector computing device, from the first computing device, the set of transfer conditions and an indication of an acceptance of the set of transfer conditions by a second computing device;

generating, by the connector computing device, a second new message authentication code from the portion of data from the set of transfer conditions received from the first computing device;

comparing, by the connector computing device, the second new message authentication code to the message authentication code and determining that the second new message authentication code matches the message authentication code; and

in response to determining that the second new message authentication code matches the message authentication code, verifying the set of transfer conditions.

3. The method of claim 1 , wherein the message authentication code is hash-based.

4. The method of claim 1 , further comprising generating, by the connector computing device, a transfer identifier for the set of transfer conditions from data from the set of transfer conditions, the data comprising at least data specifying a first sub-transfer; and

storing, by the connector computing device, the set of transfer conditions with the transfer identifier as a transfer record in non-volatile storage.

5. The method of claim 4 , wherein generating a transfer identifier for the set of transfer conditions from data from the set of transfer conditions comprises:

representing the data from the set of transfer conditions as a string;

hashing the string to generate a hash value; and

representing the has value as a hexadecimal string.

6. The method of claim 1 , wherein the set of transfer conditions is stored as a data object.

7. The method of claim 5 , wherein the data object is sent and received using HTTP.

8. A method performed by a computer with a storage and a processor, the method comprising:

generating a set of transfer conditions in response to a request for transfer conditions,

generating a message authentication code based on a portion of data from the set of transfer conditions,

storing the message authentication code in the set of transfer conditions,

sending the request for transfer conditions to a first computing device,

receiving from the first computing device, the set of transfer conditions and an indication of an acceptance of the set of transfer conditions by a second computing device,

generating a new message authentication code from the portion of data from the set of transfer conditions received from the first computing device;

comparing the new message authentication code to the message authentication code and determining that the new message authentication code does not match the message authentication code, and

in response to determining that the new message authentication code does not match the message authentication code, resending the set of transfer conditions to the first computing device.

9. The method of claim 8 , wherein the method further comprises, after resending the set of transfer conditions to the first computing device,

receiving from the first computing device, the set of transfer conditions and an indication of an acceptance of the set of transfer conditions by a second computing device,

generating a second new message authentication code from the portion of data from the set of transfer conditions received from the first computing device,

comparing the second new message authentication code to the message authentication code and determining that the second new message authentication code matches the message authentication code, and

in response to determining that the second new message authentication code matches the message authentication code, verifying the set of transfer conditions.

10. The method of claim 8 , wherein the message authentication code is hash-based.

11. The method of claim 8 , further comprising generating a transfer identifier for the set of transfer conditions from data from the set of transfer conditions, the data comprising at least data specifying a first sub-transfer, and

storing the set of transfer conditions with the transfer identifier as a transfer record in non-volatile storage of the storage.

12. The method of claim 11 , wherein generating a transfer identifier for the set of transfer conditions from data from the set of transfer conditions comprises:

representing the data from the set of transfer conditions as a string;

hashing the string to generate a hash value; and

representing the has value as a hexadecimal string.

13. The method of claim 8 , wherein the set of transfer conditions is stored as a data object.

14. A system comprising: one or more computers and one or more storage devices storing instructions which are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising:

generating, by a connector computing device, a set of transfer conditions in response to a request for transfer conditions;

generating, by the connector computing device, a message authentication code based on a portion of data from the set of transfer conditions;

storing, by the connector computing device, the message authentication code in the set of transfer conditions;

sending, by the connector computing device, the request for transfer conditions to a first computing device;

receiving, by the connector computing device, from the first computing device, the set of transfer conditions and an indication of an acceptance of the set of transfer conditions by a second computing device;

generating, by the connector computing device, a new message authentication code from the portion of data from the set of transfer conditions received from the first computing device;

comparing, by the connector computing device, the new message authentication code to the message authentication code and determining that the new message authentication code does not match the message authentication code; and

in response to determining that the new message authentication code does not match the message authentication code, resending, by the connector computing device, the set of transfer conditions to the first computing device.

15. The system of claim 14 , wherein the instructions which are operable, when executed by the one or more computers, to further cause the one or more computers to perform operations comprising:

after resending, by the connector computing device, the set of transfer conditions to the first computing device;

receiving, by the connector computing device, from the first computing device, the set of transfer conditions and an indication of an acceptance of the set of transfer conditions by a second computing device;

generating, by the connector computing device, a second new message authentication code from the portion of data from the set of transfer conditions received from the first computing device;

comparing, by the connector computing device, the second new message authentication code to the message authentication code and determining that the second new message authentication code matches the message authentication code; and

in response to determining that the second new message authentication code matches the message authentication code, verifying the set of transfer conditions.

16. The system of claim 14 , wherein the message authentication code is hash-based.

17. The system of claim 14 wherein the instructions which are operable, when executed by the one or more computers, to further cause the one or more computers to perform operations comprising:

generating, by the connector computing device, a transfer identifier for the set of transfer conditions from data from the set of transfer conditions, the data comprising at least data specifying a first sub-transfer; and

storing, by the connector computing device, the set of transfer conditions with the transfer identifier as a transfer record in non-volatile storage.

18. The system of claim 17 , wherein the instructions that cause the one or more computers to perform operations comprising generating a transfer identifier for the set of transfer conditions from data from the set of transfer conditions further cause the one or more computers to perform operations comprising:

representing the data from the set of transfer conditions as a string;

hashing the string to generate a hash value; and

representing the has value as a hexadecimal string.

19. The system of claim 14 , wherein the set of transfer conditions is stored as a data object.

20. The system of claim 19 , wherein the data object is sent and received using HTTP.

Assignments (4)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 68684 FRAME: 982. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Mar 19, 2025
From: RIPPLE LUXEMBOURG S.A.
To: INTERLEDGER FOUNDATION INC.
Reel/Frame 070660/0786 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2024
From: WAY, ROBERT
To: 402 TECHNOLOGIES S.A.
Reel/Frame 068684/0768 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2024
From: 402 TECHNOLOGIES S.A.
To: RIPPLE LUXEMBOURG S.A.
Reel/Frame 068684/0874 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2024
From: RIPPLE LUXEMBOURG S.A.
To: INTERLEDGER FOUNDATION
Reel/Frame 068684/0982 →
Continuity (5)
Continuation 18111774 · Feb 20, 2023
Continuation 16872350 · May 11, 2020
Continuation 16220902 · Dec 14, 2018
Continuation 15227437 · Aug 3, 2016
Related Publication 20240259364A1 · Aug 1, 2024
References Cited (23)
US 5231666A · Matyas · 1993 [cited by applicant]
US 8626617B1 · Bhatt · 2014 [cited by applicant]
US 9721235B2 · Wilkes · 2017 [cited by applicant]
US 20030093355A1 · Issa · 2003 [cited by applicant]
US 20070215684A1 · Jones · 2007 [cited by applicant]
US 20100281522A1 · Hatakeyama · 2010 [cited by examiner]
US 20110238553A1 · Raj · 2011 [cited by examiner]
US 20120084466A1 · Brown · 2012 [cited by applicant]
US 20120221522A1 · Allman · 2012 [cited by applicant]
US 20130218763A1 · Wilkes · 2013 [cited by examiner]
US 20140188738A1 · Huxham · 2014 [cited by applicant]
US 20150074169A1 · Doleh · 2015 [cited by applicant]
US 20150332256A1 · Minor · 2015 [cited by applicant]
US 20150381623A1 · Mattson · 2015 [cited by applicant]
US 20160297401A1 · Haga · 2016 [cited by applicant]
US 20160342959A1 · Thomas · 2016 [cited by applicant]
US 20160342982A1 · Thomas · 2016 [cited by examiner]
US 20160342984A1 · Thomas · 2016 [cited by applicant]
US 20160342988A1 · Thomas · 2016 [cited by applicant]
US 20170243213A1 · Castinado · 2017 [cited by examiner]
AU 783008B2 · 2001 [cited by applicant]
International Search Report and Written Opinion dated Nov. 6, 2017 as received in Application No. PCT/EP2017/069631. [cited by applicant]
International Preliminary Report on Patentability for Application No. PCT/EP2017/069631 date of mailing Feb. 14, 2019, 10 pages. [cited by applicant]