System and method for accessing an online user account registry via a thin-client unique user code

• US 8,639,629 B1
• Filed: 10/27/2007
• Issued: 01/28/2014
• Est. Priority Date: 02/02/2005
• Status: Expired due to Fees

• Current Assignee: Edge Mobile Payments LLC
• Original Assignee: Nexus Payments, LLC
• Inventors: Hoffman, Ned
• Primary Examiner(s): Coppola, Jacob C.
• Application Number:
  US11/978,067
• Time in Patent Office: 2,285 Days
• Field of Search: 705 50- 79
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/306 using TV related infrastructures external card used for payment with client device H04N21/4185
• CPC Class Codes: G06Q 20/321 using wearable devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 20/409 Device specific authentication in transaction processing

Abstract

The invention is a system and method for accessing an online user account registry, comprising: a) Approving access to an online user account registry via a verification platform comparing a bid verification data, comprising a unique user code provided from a nexus access token, with a registered verification data; b) Accessing the online user account registry via a rule-module invoked from a rule-module nexus, said online user account registry comprising a plurality of financial accounts of the user; Whereby an online account registry, comprising a plurality of financial accounts, is accessed via a unique user code provided from a nexus access token.

Claims

1. A method for on-line financial transactions, comprising the steps of:

a. registering a user, comprising;

(i) registering a plurality of rule-modules to a user within a rule-module nexus, said registered rule-module further comprising pattern data associated with an execution command;

(ii) registering to the user within an online user account registry, a plurality of proprietary financial accounts, each comprising an account identifier, said account identifier further comprising;

a code identifying an account issuer, as approved by the International Organization for Standardization [(Bank Identification Code, or BIC Code) or (Bank Identification Number, or BIN)];

a code identifying an account issuer, as approved by the Society for Worldwide Interbank Financial Telecommunications (SWIFT Address or SWIFT Code), and;

a code identifying an account issuer, as approved by the American Banker'"'"'s Association (ABA Routing Code);

b. data-storing in a portable nexus access token, wherein a unique user code of the user is stored in the portable nexus access token, and wherein said unique user code is a thin-client data string, unique to a user, comprising data which does not directly identify a specific online financial account of the user;

c. processing an on-line financial transaction, using the portable nexus access token and a user interface apparatus located remotely from the rule-module nexus, comprising;

(i) verifying a user, wherein a user'"'"'s authority to access the rule-module nexus is verified on-line by a verification platform using verification data provided via the user interface apparatus, said verification data comprising a bid unique user code provided directly from the portable nexus access token, and;

(ii) accessing financial accounts, wherein upon the verification platform verifying the user is authorized to access the rule-module nexus, the rule-module nexus enables access to a plurality of proprietary financial accounts of the user for completing the on-line financial transaction;

Whereby, the portable nexus access token and the rule-module nexus provide an authorized user access to a plurality of proprietary financial accounts for processing an on-line financial transaction.

2. The method of claim 1, further comprising processing pan-portfolio analytics, comprising:

a. accessing a plurality of proprietary financial accounts, wherein upon a verification platform verifying a party is authorized to access the online user account registry, the rule-module nexus invokes a rule-module governing the party'"'"'s access to a plurality of proprietary financial accounts within the online user account registry;

b. surveying financial data, wherein a pattern in processing a plurality of online financial transactions is detected by an authorized party via surveying financial data residing within the plurality of proprietary financial accounts;

c. presenting analytics, wherein an analysis of a detected pattern is presented to the authorized party;

Whereby, pan-portfolio analytics are presented by an authorized party accessing a plurality of proprietary financial accounts in an online user account registry via a rule-module nexus.

3. The method of claim 2, wherein the analytics further comprises any of the following:

a pattern of fraud;

a pattern of product purchasing;

a pattern of preferences for processing a financial transaction;

a pattern of financial account selection;

a pattern of rewards redemption;

a pattern of user geographic locations;

a pattern retailer locations;

a pattern of costs in processing a financial transaction;

Whereby pan-portfolio analytics are compiled via a plurality of otherwise inaccessible proprietary financial accounts being rendered accessible by the rule-module nexus.

4. The method of claim 3, wherein the pattern further comprises any of the following:

a prior pattern;

a real-time pattern;

a predictive pattern.

5. The method of claim 1, wherein registering a user further comprises a plurality of rule-modules being registered to a user.

6. The method of claim 1, further comprising a user interface apparatus hardware verification code being verified by the verification platform, and the rule-module nexus invoking a rule-module, said rule-module comprising any of the following:

accessing a financial account of a payee;

a default electronic audible signature;

a default electronic visible signature;

a default financial account of a user;

a private code of a user;

predetermined criteria for tagging and ranking, in a certain order, a plurality of proprietary financial accounts of a user;

a financial account routing code of a payee;

transmitting payee data to the user interface apparatus, and;

transmitting payee data to the portable nexus access token;

settlement of the financial transaction wherein a financial account of the user is debited and a financial account of a payee is credited;

a rewards incentive;

an arbitrage rule-module, and;

a financial transaction processing preference.

7. The method of claim 1, further comprising auto-populating a user'"'"'s pattern data with a plurality of financial accounts, wherein auto-populating comprises:

electronically pulling a credit report of the user;

selecting financial accounts contained in said credit report;

automatically registering said selected financial accounts via the rule-module nexus.

8. The method of claim 7, wherein auto-populating communications occur via a network comprising any of the following:

a cable network;

a wireless network;

a land-line phone network;

the Internet;

an intranet;

a local area network, a wide area network;

an electronic positioning network;

a satellite network, and;

an X.25 network.

9. A method for on-line financial transactions, comprising the steps of:

a. registering a user, wherein a rule-module is registered to a user within a rule-module nexus, said registered rule-module further comprising pattern data associated with an execution command, wherein the pattern data further comprises;

a personal verification code (PVC);

a secondary personal verification code;

a unique user code, wherein said unique user code is a thin-client data string, unique to a user, comprising data which does not directly identify a specific online financial account of the user, and;

a plurality of proprietary financial accounts;

b. associating a personal verification code, comprising;

matching the personal verification code (PVC) with a live personal identification number (PIN) for processing a financial transaction of the user, and;

translating the personal verification code (PVC) into a live personal identification number (PIN) for processing a financial transaction of the user;

c. data-storing in a portable nexus access token, wherein a unique user code of the user is stored in the portable nexus access token;

d. processing an on-line financial transaction, using the nexus access token and a user interface apparatus located remotely from the rule-module nexus, comprising;

(iii) verifying a user, wherein a user'"'"'s authority to access the rule-module nexus is verified on-line by a verification platform using verification data provided via the user interface apparatus, said verification data comprising a bid unique user code provided directly from the portable nexus access token, and;

(iv) accessing financial accounts, wherein upon the verification platform verifying the user is authorized to access the rule-module nexus, the rule-module nexus enables access to a plurality of proprietary financial accounts of the user for completing the on-line financial transaction;

Whereby, the portable nexus access token and the rule-module nexus provide an authorized user access to a plurality of proprietary financial accounts for processing an on-line financial transaction.

10. The method of claim 9, further comprising forwarding a personal verification code (PVC), comprising any of the following:

forwarding the PIN to a debit processing network, and authorizing a PIN-enabled debit financial transaction;

forwarding the PVC to a debit financial transaction processing network, and authorizing a PIN-enabled debit financial transaction;

forwarding the PVC to a financial transaction processing network and authorizing a PIN-enabled financial transaction;

forwarding the PVC to a financial transaction processing network and authorizing a non-PIN enabled financial transaction.

11. A system for on-line financial transactions, comprising:

a. a first computer executable program tangibily embodied on a computer readable medium comprising

i. a rule-module nexus, configured to register a plurality of rule-modules to a user within a rule-module nexus, said rule-module further comprising pattern data associated with an execution command;

ii. an online user account registry, configured to register a plurality of proprietary financial accounts, each comprising an account identifier, said account identifier further comprising;

a code identifying an account issuer, as approved by the International Organization for Standardization [(Bank Identification Code, or BIC Code) or (Bank Identification Number, or BIN)];

a code identifying an account issuer, as approved by the Society for Worldwide Interbank Financial Telecommunications (SWIFT Address or SWIFT Code), and;

a code identifying an account issuer, as approved by the American Banker'"'"'s Association (ABA Routing Code);

b. an on-line financial transaction processing platform, comprising;

i. a nexus access token configured to comprise;

portability, and;

storing a unique user code of the user, wherein said unique user code is a thin-client data string, unique to a user, comprising data which does not directly identify a specific online financial account of the user;

ii. a user interface apparatus located remotely from the rule-module nexus, configured to gather bid verification data of the user, said verification data comprising a bid unique user code provided directly from the nexus access token, and;

iii. a second computer executable program tangibly embodied on a computer readable medium comprising

1. a verification platform configured to verify a user on-line using the bid verification data, wherein a user'"'"'s authority to access the rule-module nexus is verified, and;

2. a user account registry platform configured to access financial accounts via the rule-module nexus, wherein upon the verification platform verifying the user is authorized to access the rule-module nexus, the user is provided on-line access via the rule-module nexus to a plurality of proprietary financial accounts of the user for completing the on-line financial transaction;

Whereby, a nexus access token and a rule-module nexus provide an authorized user access to a plurality of proprietary financial accounts for processing an on-line financial transaction.

12. The system of claim 11, further comprising a pan-portfolio analytics processing platform, comprising:

a. means for accessing a plurality of proprietary financial accounts via the verification platform, the rule-module nexus, and the user account registry;

b. means for surveying financial data within said proprietary financial accounts, and detecting a pattern in processing a plurality of online financial transactions;

c. analytics presenting means, comprising means for presenting to the authorized party an analysis of a detected pattern;

Whereby, pan-portfolio analytics are presented by an authorized party accessing a plurality of proprietary financial accounts in an online user account registry via a rule-module nexus.

13. The system of claim 12, wherein the analytics further comprises any of the following:

a pattern of fraud;

a pattern of product purchasing;

a pattern of preferences for processing a financial transaction;

a pattern of financial account selection;

a pattern of rewards redemption;

a pattern of user geographic locations;

a pattern retailer locations;

a pattern of costs in processing a financial transaction.

14. The system of claim 13, wherein the pattern further comprises any of the following:

a prior pattern;

a real-time pattern;

a predictive pattern.

15. The system of claim 11, further comprising an auto-population platform configured to auto-populate a user'"'"'s pattern data with a plurality of financial accounts, comprising:

electronically pulling a credit report of the user;

selecting financial accounts contained in said credit report;

automatically registering said selected financial accounts via the rule-module nexus.

16. The system of claim 15, wherein the auto-population platform auto-populates financial accounts via a network comprising any of the following:

a cable network;

a wireless network;

a land-line phone network;

the Internet;

an intranet;

a local area network, a wide area network;

an electronic positioning network;

a satellite network, and;

an X.25 network.

17. The system of claim 11, the registration platform is further configured to comprise registering a plurality of rule-modules to a user.

18. The system of claim 11, further comprising the verification platform being configured to verify a user interface apparatus hardware verification code, and to invoke a a rule-module from the rule-module nexus, said rule-module comprising any of the following:

accessing a financial account of a payee;

a default electronic audible signature;

a default electronic visible signature;

a default financial account of a user;

a private code of a user;

predetermined criteria for tagging and ranking, in a certain order, a plurality of proprietary financial accounts of a user;

a financial account routing code of a payee;

transmitting payee data to the user interface apparatus, and;

transmitting payee data to the nexus access token;

settlement of the financial transaction wherein a financial account of the user is debited and a financial account of a payee is credited;

a rewards incentive;

an arbitrage rule-module, and;

a financial transaction processing preference.

19. A system for on-line financial transactions, comprising:

a. a first computer executable program tangibily embodied on a computer readable medium comprising

i. a registration platform, configured within a rule-module nexus to comprise registering a rule-module to a user, said rule-module further comprising pattern data associated with an execution command;

ii. a personal verification code (PVC) association platform, comprising;

matching means, wherein the personal verification code (PVC) is matched with a live personal identification number (PIN) for processing a financial transaction of the user, and;

translating means, wherein the personal verification code is translated into a live personal identification number (PIN) for processing a financial transaction of the user;

b. a nexus access token, configured to comprise;

portability, and;

storing a unique user code of the user, wherein said unique user code is a thin-client data string, unique to a user, comprising data which does not directly identify a specific online financial account of the user;

c. an on-line financial transaction processing platform, comprising;

i. a nexus access token;

ii. a user interface apparatus located remotely from the rule-module nexus, configured to gather bid verification data of the user, said verification data comprising a bid unique user code provided directly from the nexus access token, and;

iii. a second computer executable program tangibily embodied on a computer readable medium comprising

1. a verification platform configured to verify a user on-line using the bid verification data, wherein a user'"'"'s authority to access the rule-module nexus is verified, and;

2. a user account registry platform configured to access financial accounts via the rule-module nexus, wherein upon the verification platform verifying the user is authorized to access the rule-module nexus, the user is provided on-line access via the rule-module nexus to a plurality of proprietary financial accounts of the user for completing the on-line financial transaction;

Whereby, a nexus access token and a rule-module nexus provide an authorized user access to a plurality of proprietary financial accounts for processing an on-line financial transaction.

20. The system of claim 19, further comprising a personal verification code (PVC) forwarding platform, comprising any of the following:

forwarding means, wherein the PIN is forwarded to a debit processing network, and a PIN-enabled debit financial transaction is authorized, and;

forwarding means, wherein the PVC is forwarded to a debit financial transaction processing network, and a PIN-enabled debit financial transaction is authorized;

forwarding means, wherein the PVC is forwarded to a financial transaction processing network, and a PIN-enabled financial transaction is authorized;

forwarding means, wherein the PVC is forwarded to a financial transaction processing network, and a non-PIN enabled financial transaction is authorized.