IP Library Granted Patent US 11,962,577
Granted Patent B2
US 11,962,577 · App. 18/111,774 · Granted Apr 16, 2024

Resource transfer setup and verification

Inventor: Robert Way (Spring, TX)
Assignee: Ripple Luxembourg S.A.
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 11,962,577
App. No.
18/111,774
Granted
Apr 16, 2024
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 (63)

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

generating, by a connector computing device, a transfer identifier for a set of transfer conditions;

sending, by the connector computing device, transfer instructions based on the set of transfer conditions to a second computing device;

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

receiving, by the connector computing device, a request to verify the transfer record, the request comprising the transfer identifier;

generating, by the connector computing device, a new transfer identifier from the data from the set of transfer conditions stored in the transfer record with the transfer identifier;

comparing, by the connector computing device, the new transfer identifier to the transfer identifier stored with the set of transfer conditions in the transfer record; and

if the new transfer identifier matches the transfer identifier, sending, by the connector computing device, an indication that the transfer record is verified, or if the new transfer identifier does not match the transfer identifier, sending, by the connector computing device, an indication that the transfer record is not verified.

2. The method of claim 1 , wherein generating a transfer identifier for the set of transfer conditions:

representing 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.

3. The method of claim 1 , further comprising generating the set of transfer conditions by:

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

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

4. The method of claim 3 , further comprising:

receiving, by the connector 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 a portion of data from the set of transfer conditions; and

comparing the new message authentication code to the message authentication code stored in the set of transfer conditions to verify the set of transfer conditions before generating the transfer identifier.

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

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

7. A computer-implemented system comprising:

one or more storage devices of a connector computing device; and

a processor, of the connector computing device, that:

generates a transfer identifier for a set of transfer conditions, sends transfer instructions based on the set of transfer conditions to a second computing device,

stores the set of transfer conditions with the transfer identifier as a transfer record in non-volatile storage of the one or more storage devices,

receives a request to verify the transfer record, the request comprising the transfer identifier,

generates a new transfer identifier from the data from the set of transfer conditions stored in the transfer record with the transfer identifier,

compares the new transfer identifier to the transfer identifier stored with the set of transfer conditions in the transfer record, and

if the new transfer identifier matches the transfer identifier, sends an indication that the transfer record is verified, or if the new transfer identifier does not match the transfer identifier, sends an indication that the transfer record is not verified.

8. The system of claim 7 , wherein the processor generates the transfer identifier for the set of transfer conditions by:

representing 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.

9. The system of claim 7 , wherein the processor generates the set of transfer conditions by:

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

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

10. The system of claim 9 , wherein the processor further receives the set of transfer conditions and an indication of an acceptance of the set of transfer conditions by a second computing device,

generates a new message authentication code from a portion of data from the set of transfer conditions, and

compares the new message authentication code to the message authentication code stored in the set of transfer conditions to verify the set of transfer conditions before generating the transfer identifier.

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

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

13. A system comprising: one or more computers and one or more non-transitory 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, with a connector computing device, a transfer identifier for a set of transfer conditions;

sending, with a connector computing device, transfer instructions based on the set of transfer conditions to a second computing device;

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

receiving, with a connector computing device, a request to verify the transfer record, the request comprising the transfer identifier;

generating, with a connector computing device, a new transfer identifier from the data from the set of transfer conditions stored in the transfer record with the transfer identifier;

comparing, with a connector computing device, the new transfer identifier to the transfer identifier stored with the set of transfer conditions in the transfer record; and

if the new transfer identifier matches the transfer identifier, sending, with a connector computing device, an indication that the transfer record is verified, or if the new transfer identifier does not match the transfer identifier, sending an indication that the transfer record is not verified.

14. The system of claim 13 , wherein the instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform the operation of generating a transfer identifier for the set of transfer conditions further cause the one or more computers to perform operations comprising:

representing 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.

15. The system of claim 13 , wherein the instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform the operation of generating the set of transfer conditions further cause the one or more computers to perform operations comprising:

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

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

16. The system of claim 15 , wherein the one or more computers and one or more non-transitory storage devices further store instructions which are operable, when executed by the one or more computers, to cause the one or more computers to further perform operations comprising:

receiving, by the connector 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 a portion of data from the set of transfer conditions; and

comparing the new message authentication code to the message authentication code stored in the set of transfer conditions to verify the set of transfer conditions before generating the transfer identifier.

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

18. The system of claim 17 , 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: RIPPLE LUXEMBOURG S.A.
To: INTERLEDGER FOUNDATION
Reel/Frame 068684/0982 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2024
From: WAY, ROBERT
To: 402 TECHNOLOGIES S.A.
Reel/Frame 066807/0618 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2024
From: 402 TECHNOLOGIES S.A.
To: RIPPLE LUXEMBOURG S.A.
Reel/Frame 066807/0977 →
Continuity (4)
Continuation 16872350 · May 11, 2020
Continuation 16220902 · Dec 14, 2018
Continuation 15227437 · Aug 3, 2016
Related Publication 20230198971A1 · Jun 22, 2023