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.