Financial transactions using a rule-module nexus and a user account registry

• US 8,768,838 B1
• Filed: 04/19/2011
• Issued: 07/01/2014
• Est. Priority Date: 02/02/2005
• Status: Active Grant

• Current Assignee: Edge Mobile Payments LLC
• Original Assignee: Nexus Payments, LLC
• Inventors: Hoffman, Ned
• Primary Examiner(s): Coppola, Jacob C.
• Application Number:
  US13/089,313
• Time in Patent Office: 1,169 Days
• Field of Search: 705/67
• US Class Current: 705/44
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A method and a system for processing an online financial transaction executed at least partially by a computing device coupled to a communications network, comprising a rule-module nexus for processing an online financial transaction, an on-line verification platform, an online user account registry, wherein the on-line financial transaction comprises a payor-payee transaction, wherein the user is the payor and a merchant is the payee, and comprising at least one of the following: (a) the user and the payee are each directly and independently connected to the rule-module nexus during simultaneous logon sessions via a communication network, and wherein upon the user clicking on a website widget of the payee, the rule-module nexus transmits secure socket layer data directly to the user interface apparatus for display to the user via a pop-up window, without requiring application programming interface integration with a website of the payee and without requiring a form re-direct of the user away from the website of the payee; (b) the buyer, the seller, and the acquirer are each directly and independently connected to the rule-module nexus via a communication network, not necessarily during simultaneous logon sessions, and wherein the rule-module nexus hibernates the financial transaction pending verification the user, invocation of a rule-module, selection of the financial account, and submission of the selected financial account to the acquirer.

Claims

1. A computer implemented method for processing an online financial transaction in a computer system executed at least partially by at least one computing device coupled to a communications network, comprising the steps of:

a. registering a rule-module to a user within a rule-module nexus associated with the at least one computing device, each rule-module comprising pattern data associated with an execution command, wherein said pattern data comprises at least four of the following;

(i) a plurality of proprietary financial accounts of the user;

(ii) a thin-client user account registry code;

(iii) a thin-client primary personal verification code, comprising a non-biometric data string formed from the input of alpha-numeric-symbolic characters;

(iv) a thin-client secondary personal verification code, comprising a non-biometric data string formed from the input of alpha-numeric-symbolic characters;

(v) a thin-client unique user code comprising a binary data string and encoded in a nexus access token, and;

(vi) a thin-client private code, comprising a non-biometric data string, distinct from a personal verification code of the user and not used in verifying the user;

presented to the user in the form of visible alpha-numeric-symbolic characters or audible sound;

b. processing an online payor-payee financial transaction, wherein the user is the payor and a merchant is the payee, comprising;

(i) Connecting to the rule-module nexus, comprising at least one of the following;

(a) a device of the user and a device of the payee are each directly and independently connected to the rule-module nexus during simultaneous logon sessions via a communication network, and where upon the user clicking on a website widget of the payee, the rule-module nexus transmits secure socket layer data directly to the user interface apparatus for display to the user via a pop-up window, without requiring application programming interface integration with a web site of the payee and without requiring a form re-direct of the user away from the website of the payee;

(b) the device of the payor, the device of the payee, and a device of an acquirer are each directly and independently connected to the rule-module nexus via a communication network, not necessarily during simultaneous logon sessions, and wherein the rule-module nexus hibernates the financial transaction pending at least one of the following;

verification of the user;

invocation of a rule-module;

selection of the financial account, and;

submission of the selected financial account to the acquirer;

(ii) verifying the user, wherein the user'"'"'s authority to access the rule-module nexus is verified by an on-line verification platform using verification data comprising at least two of the following;

the primary personal verification code provided directly by the user via a user interface apparatus (UIA);

the secondary personal verification code provided directly by the user via the UIA, and;

the unique user code provided via the nexus access token;

(iii) accessing financial accounts, wherein upon the verification platform verifying the user is authorized to access the rule-module nexus, at least one rule-module is invoked enabling the user to access a plurality of proprietary financial accounts via the user'"'"'s online user account registry, for account selection and completion of the on-line financial transaction;

Whereby, an on-line financial transaction is processed via a rule-module nexus and an online user account registry comprising a plurality of proprietary financial accounts of the user.

2. The method of claim 1, wherein the unique user code comprises any of the following:

a telephone number;

a browser cookie;

an email address;

a subscriber identification module card number, and;

an internet protocol address.

3. The method of claim 2, wherein the nexus access token, conjoined with the user'"'"'s UIA, comprises any of the following:

a cell phone;

a personal computer;

a USB thumb drive;

a car'"'"'s dashboard computer with interactive graphical user interface.

4. The method of claim 1, further comprising transmitting the unique user code by a third-party, wherein the unique user code is transmitted to the verification platform from a third-party with which the user has initiated a secure logon session using the nexus access token and the user interface apparatus.

5. The method of claim 1, wherein the secure socket layer data comprises at least one of the following:

the private code;

a data entry line and a prompt for user input of the primary personal verification code;

a data entry line and a prompt for user input of the secondary personal verification code;

HTTPS data;

S-HTTP data.

6. The method of claim 5, further comprising displaying the private code by the device of the user, whereupon the user inputs verification data via the pop-up window, comprising at least one of the following:

the primary personal verification code, and;

the secondary personal verification.

7. The method of claim 6, wherein upon verification of the user'"'"'s primary and/or secondary personal verification code(s), the rule-module nexus invokes a rule-module comprising at least one of the following:

pre-determined instructions for shipping of a product being purchased by the user from the payee;

a mailing address for the user;

a user-customized rewards incentive;

a user-customized advertisement;

a user-customized default financial account;

the invoking and forwarding to an acquirer by a PVC association platform, of a pre-registered personal identification number associated with a debit financial account.

8. The method of claim 1, wherein the rule-module invokes at least one audible/visible account signature for display to the user via the user interface apparatus.

9. The method of claim 1, further comprising registering a payee, wherein the payee registers a rule-module within the rule-module nexus, said rule-module comprising pattern data associated with an execution command, and said pattern data comprising at least one of the following:

a unique payee code;

a payee account registry code;

a plurality of proprietary financial accounts;

payee positioning system coordinates;

a payee'"'"'s roster of goods and/or services including associated pricing and universal product code(s);

a payee'"'"'s UIA-verification code.

10. The method of claim 9, further comprising verifying the payee, wherein the payee provides a unique payee code to the verification platform for verifying the payee'"'"'s authority to access the rule-module nexus.

11. The method of claim 10, further comprising invoking a payee rule-module, wherein upon the payee being verified by the verification platform, a rule-module of the payee is invoked comprising any of the following:

instructions enabling the payee to access a plurality of proprietary financial accounts via the payee account registry;

instructions authorizing the payee to provide the unique user code of the user to the rule-module nexus;

instructions authorizing the payee to provide a user-customized payment transaction request for transmittal to the user.

12. The method of claim 11, wherein payee access to a plurality of proprietary financial accounts comprises invoking a payee depository account for receipt of funds from the user pursuant to the user-customized payment transaction request.

13. The method of claim 12, further comprising displaying a confirmation code, wherein upon the user'"'"'s completion of the financial transaction and transmittal of a financial transaction response packet to the payee, the user'"'"'s UIA displays a confirmation code for presentation to a UIA of the payee, said confirmation code comprising any of the following:

a computer-readable code, and;

a visually readable alpha-numeric-symbolic code.

14. A computer system for processing an online financial transaction, comprising at least one computing device coupled to a communications network, the at least one computing device operable to perform a method comprising the steps of:

a. registering a rule-module nexus, wherein the rule-module comprises pattern data associated with an execution command, said pattern data comprising at least four of the following;

(i) a plurality of proprietary financial accounts of the user;

(ii) a thin-client user account registry code;

(iii) a thin-client primary personal verification code, comprising a non-biometric data string formed from the input of alpha-numeric-symbolic characters;

(iv) a thin-client secondary personal verification code, comprising a non-biometric data string formed from the input of alpha-numeric-symbolic characters;

(v) a thin-client unique user code comprising a binary data string and encoded in a nexus access token, and;

(vi) a thin-client private code, comprising a non-biometric data string, distinct from a personal verification code of the user and not used in verifying the user;

presented to the user in the form of visible alpha-numeric-symbolic characters or audible sound;

b. processing an online payor-payee financial transaction, wherein the user is the payor and a merchant is the payee, comprising;

(iv) connecting to the rule-module nexus, comprising at least one of the following;

(a) a device of the user and a device of the payee are each directly and independently connected to the rule-module nexus during simultaneous logon sessions via a communication network, and wherein upon the user clicking on a website widget of the payee, the rule-module nexus transmits secure socket layer data directly to the user interface apparatus for display to the user via a pop-up window, without requiring application programming interface integration with a website of the payee and without requiring a form re-direct of the user away from the website of the payee;

(b) the device of the payor, the device of the payee, and a device of an acquirer are each directly and independently connected to the rule-module nexus via a communication network, not necessarily during simultaneous logon sessions, and wherein the rule-module nexus hibernates the financial transaction pending at least one of the following;

verification the user;

invocation of a rule-module;

selection of the financial account, and;

submission of the selected financial account to the acquirer;

(v) verifying the user, wherein the user'"'"'s authority to access the rule-module nexus is verified by an on-line verification platform using verification data comprising at least two of the following;

the primary personal verification code provided directly by the user via a user interface apparatus (UIA);

the secondary personal verification code provided directly by the user via the UIA, and;

the unique user code provided via the nexus access token;

(vi) accessing financial accounts, wherein upon the verification platform verifying the user is authorized to access the rule-module nexus, at least one rule-module is invoked enabling the user to access a plurality of proprietary financial accounts via the user'"'"'s online user account registry, for account selection and completion of the on-line financial transaction, said on-line financial transaction comprising a payor-payee transaction, wherein the user is the payor and a merchant is the payee;

Whereby, an on-line financial transaction is processed via a rule-module nexus and an online user account registry comprising a plurality of proprietary financial accounts of the user.

15. The system of claim 14, wherein the unique user code comprises any of the following:

a telephone number;

a browser cookie;

an email address;

a subscriber identification module card number, and;

an internet protocol address.

16. The system of claim 15, wherein the nexus access token, conjoined with the user'"'"'s UIA, comprises any of the following:

a cell phone;

a personal computer;

a USB thumb drive;

a car'"'"'s dashboard computer with interactive graphical user interface.

17. The system of claim 14, wherein the method further comprises transmitting the unique user code by a third-party, wherein the unique user code is transmitted to the verification platform from a third-party with which the user has initiated a secure logon session using the nexus access token and the user interface apparatus.

18. The system of claim 14, wherein the secure socket layer data comprises at least one of the following:

the private code;

a data entry line and a prompt for user input of the primary personal verification code;

a data entry line and a prompt for user input of the secondary personal verification code;

HTTPS data;

S-HTTP data.

19. The system of claim 18, wherein the method further comprises displaying the private code by the device of the user, whereupon the user inputs verification data via the pop-up window, comprising at least one of the following:

the primary personal verification code, and;

the secondary personal verification.

20. The system of claim 19, wherein the method further comprises, upon verification of the user'"'"'s primary and/or secondary personal verification code(s), invoking a rule-module, said rule-module comprising at least one of the following:

pre-determined instructions for shipping of a product being purchased by the user from the payee;

a mailing address for the user;

a user-customized rewards incentive;

a user-customized advertisement;

a user-customized default financial account;

the invoking and forwarding to an acquirer by a PVC association platform, of a pre-registered personal identification number associated with a debit financial account.

21. The system of claim 14, wherein the rule-module invokes at least one audible/visible account signature for display to the user via the user interface apparatus.

22. The system of claim 14, wherein the method further compris comprises registering a payee, wherein the payee registers a rule-module within the rule-module nexus, said rule-module comprising pattern data associated with an execution command, and said pattern data comprising at least one of the following:

a unique payee code;

a payee account registry code;

a plurality of proprietary financial accounts;

payee positioning system coordinates;

a payee'"'"'s roster of goods and/or services including associated pricing and universal product code(s);

a payee'"'"'s UIA-verification code.

23. The system of claim 22, wherein the method further verifying the payee, wherein the payee provides a unique payee code to the verification platform for verifying the payee'"'"'s authority to access the rule-module nexus.

24. The system of claim 23, wherein the method further comprises compris invoking a payee rule-module, where upon the payee being verified by the verification platform, a rule-module of the payee is invoked comprising any of the following:

instructions enabling the payee to access a plurality of proprietary financial accounts via the payee account registry;

instructions authorizing the payee to provide the unique user code of the user to the rule-module nexus;

instructions authorizing the payee to provide a user-customized payment transaction request for transmittal to the user.

25. The system of claim 24, wherein payee access to a plurality of proprietary financial accounts comprises invoking a payee depository account for receipt of funds from the user pursuant to the user-customized payment transaction request.

26. The system of claim 25, wherein the method further comprises comprising means for displaying a confirmation code, where upon the user'"'"'s completion of the financial transaction and transmittal of a financial transaction response packet to the payee, the user'"'"'s UIA displays a confirmation code for presentation to a UIA of the payee, said confirmation code comprising any of the following:

a computer-readable code, and;

a visually readable alpha-numeric-symbolic code.