IP Library › Granted Patent US 11,803,826
Granted Patent B2
US 11,803,826 · App. 17/664,761 · Granted Oct 31, 2023

Systems and methods of direct account transfer

Inventors: Rodney Kenneth Drury (Havelock North, NZ); Matthew John Vickers (Wellington, NZ)
Assignee: Xero Limited
G06Q20/108G06Q20/102G06Q20/382G06Q20/3823G06Q20/3829G06Q20/023G06Q20/42
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,803,826
App. No.
17/664,761
Granted
Oct 31, 2023
Kind
B2
Abstract

A financial institution and a payment initiator may exchange public keys to enable the secure exchange of data. A business wishing to collect payment can provide its account information to the payment initiator. A customer wishing to pay can instruct the payment initiator to encrypt the business's account information along with details for a particular invoice and transmit the information to the financial institution. The financial institution can decrypt the information and initiate a transfer of money from the customer to the business. The financial institution may present the information about the transaction to the customer for modification or confirmation before initiating the transfer. The information may be sent from the payment initiator to the financial institution via the customer. After the payment has been initiated by the financial institution, a confirmation may be sent to the customer, the payment initiator, the business, or any suitable combination thereof.

Claims (67)

1. A method comprising:

exchanging, by an accounting platform server, with a website of a bank, a public key of the accounting platform server and a public key of the bank, the accounting platform server configured to maintain bookkeeping accounts for a plurality of entities including a user of a client device;

presenting, by the accounting platform server, an invoice including an amount and a payment button to the client device of the user, the payment button being associated with an option to pay the amount to an entity through the bank;

detecting, by the accounting platform server, via the presented payment button, a request to pay the amount through a user account of the bank:

responsive to the detected request to pay:

encrypting, by the accounting platform server and using the public key of the bank, data for processing the invoice;

sending, by the accounting platform server, the encrypted data to the client device; and

redirecting, by the accounting platform server, the client device to the website of the bank;

responsive to the redirection of the web browser by the accounting platform server, at a server of the bank:

receiving, from the accounting platform server via the client device and the network, the encrypted data;

decrypting, using a decryption key, the encrypted data;

automatically causing a second user interface to be presented on the web browser running on the client device, the second user interface comprising an option to transfer a quantity of funds from the account of the user to the account of the entity, the quantity of funds being set by the server of the bank to the amount to be paid based on the decrypted data; and

in response to selection of the option to transfer the quantity of funds, transferring the quantity of funds from the account of the user to the account of the entity.

2. The method of claim 1 , comprising:

receiving, by the accounting platform server, from the website of the bank, an indication that the amount of the invoice was transferred from the user account to the account of the entity.

3. The method of claim 2 , wherein the indication indicates that the amount was transferred via Automated Clearing House (ACH).

4. The method of claim 1 , wherein the encrypted data includes at least one of the following: data identifying the bank of the user, an identity of the user, the amount, a description associated with the invoice, and data identifying the account of the entity.

5. The method of claim 1 , wherein the transfer of the quantity of funds from the account of the user to the account of the entity does not transfer the amount through an intermediate account.

6. The method of claim 1 , wherein the encrypted data is signed using a private key.

7. The method of claim 1 , comprising:

generating a set of banks based on availability of a public key for each bank of the set of banks in a database;

presenting a user interface operable to select the bank from the set of banks; and

detecting a selection of the bank in the user interface.

8. A system comprising:

a memory; and

one or more modules coupled to the memory and configured to:

exchange, by an accounting platform server, with a website of a bank, a public key of the accounting platform server and a public key of the bank, the accounting platform server configured to maintain bookkeeping accounts for a plurality of entities including a user of a client device;

present, by the accounting platform server, an invoice including an amount and a payment button to the client device of the user, the payment button being associated with an option to pay the amount to an entity through the bank;

detect, by the accounting platform server, via the presented payment button, a request to pay the amount through a user account of the bank:

responsive to the detected request to pay:

encrypt, by the accounting platform server and using the public key of the bank, data for processing the invoice;

send, by the accounting platform server, the encrypted data to the client device; and

redirect, by the accounting platform server, the client device to the website of the bank;

responsive to the redirection of the web browser by the accounting platform server, at a server of the bank:

receive, from the accounting platform server via the client device and the network, the encrypted data;

decrypt, using a decryption key, the encrypted data;

automatically cause a second user interface to be presented on the web browser running on the client device, the second user interface comprising an option to transfer a quantity of funds from the account of the user to the account of the entity, the quantity of funds being set by the server of the bank to the amount to be paid based on the decrypted data; and

in response to selection of the option to transfer the quantity of funds, transfer the quantity of funds from the account of the user to the account of the entity.

9. The system of claim 8 , wherein the one or more modules are further configured to:

receive, by the accounting platform server, from the website of the bank, an indication that the amount of the invoice was transferred from the user account to the account of the entity.

10. The system of claim 9 , wherein the indication indicates that the amount was transferred via Automated Clearing House (ACH).

11. The system of claim 8 , wherein the encrypted data includes at least one of the following: data identifying the bank of the user, an identity of the user, the amount, a description associated with the invoice, and data identifying the account of the entity.

12. The system of claim 8 , wherein the transfer of the quantity of funds from the account of the user to the account of the entity does not transfer the quantity of funds through an intermediate account.

13. The system of claim 8 , wherein the encrypted data is signed using a private key.

14. The system of claim 8 , wherein the one or more modules are further configured to:

generate a set of banks based on availability of a public key for each bank of the set of banks in a database;

present a user interface operable to select the bank from the set of banks; and

detect a selection of the bank in the user interface.

15. A non-transitory machine-readable storage medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:

exchanging, by an accounting platform server, with a website of a bank, a public key of the accounting platform server and a public key of the bank, the accounting platform server configured to maintain bookkeeping accounts for a plurality of entities including a user of a client device;

presenting, by the accounting platform server, an invoice including an amount and a payment button to the client device of the user, the payment button being associated with an option to pay the amount to an entity through the bank;

detecting, by the accounting platform server, via the presented payment button, a request to pay the amount through a user account of the bank:

responsive to the detected request to pay:

encrypting, by the accounting platform server and using the public key of the bank, data for processing the invoice;

sending, by the accounting platform server, the encrypted data to the client device; and

redirecting, by the accounting platform server, the client device to the website of the bank;

responsive to the redirection of the web browser by the accounting platform server, at a server of the bank:

receiving, from the accounting platform server via the client device and the network, the encrypted data;

decrypting, using a decryption key, the encrypted data;

automatically causing a second user interface to be presented on the web browser running on the client device, the second user interface comprising an option to transfer a quantity of funds from the account of the user to the account of the entity, the quantity of funds being set by the server of the bank to the amount to be paid based on the decrypted data; and

in response to selection of the option to transfer the quantity of funds, transferring the quantity of funds from the account of the user to the account of the entity.

16. The non-transitory machine-readable storage medium of claim 15 , wherein the operations further comprise:

receiving, by the accounting platform server, from the website of the bank, an indication that the amount of the invoice was transferred from the user account to the account of the entity.

17. The non-transitory machine-readable storage medium of claim 16 , wherein the indication indicates that the amount was transferred via Automated Clearing House (ACH).

18. The non-transitory machine-readable storage medium of claim 15 , wherein the encrypted data includes at least one of the following: data identifying the bank of the user, an identity of the user, the amount, a description associated with the invoice, and data identifying the account of the entity.

19. The non-transitory machine-readable storage medium of claim 15 , wherein the transfer of the quantity of funds from the account of the user to the account of the entity does not transfer the amount through an intermediate account.

20. The non-transitory machine-readable storage medium of claim 15 , wherein the operations further comprise: generating a set of banks based on availability of a public key for each bank of the set of banks in a database; presenting a user interface operable to select the bank from the set of banks; and detecting a selection of the bank in the user interface.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 24, 2022
From: DRURY, RODNEY KENNETH; VICKERS, MATTHEW JOHN
To: XERO LIMITED
Reel/Frame 060001/0146 →
Continuity (4)
Continuation 14689894 · Apr 17, 2015
Continuation 14446782 · Jul 30, 2014
Provisional Application 61860771 · Jul 31, 2013
Related Publication 20220292466A1 · Sep 15, 2022