Some content of this application is unavailable at the moment.
If this situation persist, please contact us atFeedback&Contact
1. (WO2018037259) IMPLEMENTING SECURE TRANSACTION MANAGEMENT UTILIZING TOKENIZED SENSITIVE INFORMATION IN AN OBJECT-ORIENTED TRANSACTIONAL FRAMEWORK HAVING HIERARCHICALLY ASSEMBLABLE AND SELECTABLE MENU ITEMS
Note: Text based on automatic Optical Character Recognition processes. Please use the PDF version for legal matters

IMPLEMENTING SECURE TRANSACTION MANAGEMENT UTILIZING TOKENIZED SENSITIVE INFORMATION IN AN OBJECT-ORIENTED

TRANSACTIONAL FRAMEWORK HAVING HIERARCHICALLY ASSEMBLABLE AND SELECTABLE MENU ITEMS

CLAIMS

1. A method, performed by an application server computer system (102) at runtime, of implementing secure transaction management in an object-oriented transactional framework (100) having hierarchically assemblable and selectable menu items, the method comprising the steps of:

invoking a tree structure (410) characterizing cooperating objects (412, 414, 416) corresponding to the menu items in response to a request from a client application (104) executing on a client computer (106) for information relating to the cooperating objects (412, 414, 416), the cooperating objects (412, 414, 416) being grouped into a plurality of transaction paths, each transaction path of the plurality of transaction paths representing a transaction instance of an electronic transaction in the transactional framework (100);

providing the menu items in a sequentially assembled form for the each transaction path beginning with at least one category object (412) of the cooperating objects (412, 414, 416) corresponding to an attribute of the transactional framework (100), continuing with at least one user account object (414) of the cooperating objects (412, 414, 416) corresponding to a user account upon which the transaction can be conducted, and ending with an action object (416) of the cooperating objects (412, 414, 416) corresponding to a task request associated with the transaction instance;

performing an aliasing operation (130) on sensitive information associated with the user account to produce tokenized sensitive information;

associating the tokenized sensitive information with the user account to which the user account object (414) contained in the sequentially assembled menu items corresponds;

generating and transferring to the client application (104) codes arranged to render the sequentially assembled menu items containing the tokenized sensitive information on a user interface for a display screen (128) of the client computer (106);

receiving a transaction request from the client application (104) in relation to the tokenized sensitive information; and

authorizing the transaction request based at least in part on the tokenized sensitive information.

The method according to claim 1, wherein the sensitive information include any one or both of a transaction account identifier and a personal information.

The method according to claim 2, wherein the aliasing operation (130) includes retrieving from the transactional framework (100) a telephone number associated with the user account and replacing the transaction account identifier with the telephone number.

The method according to claim 2, wherein the aliasing operation (130) includes generating a random data value and replacing the transaction account identifier with the random data value.

The method according to claim 2, wherein the aliasing operation (130) includes selecting one or more parts of the transaction account identifier, generating a random data value, and appending the random data value to the selected one or more parts of the transaction account identifier.

The method according to claim 2, wherein the aliasing operation (130) includes generating a random data value, selecting one or more parts of the random data value, selecting one or more parts of the transaction account identifier, and appending the selected one or more parts of the transaction account identifier to the selected one or more parts of the random data value.

The method according to claim 2, wherein the aliasing operation (130) includes retrieving from the transactional framework (100) a telephone number associated with the user account, selecting one or more parts of the telephone number, selecting one or more parts of the transaction account identifier, and appending the selected one or more parts of the telephone number to the selected one or more parts of the transaction account identifier.

The method according to claim 2, wherein the aliasing operation (130) includes selecting one or more parts of the personal information, selecting one or more parts of the transaction account identifier, and appending the selected one or more parts of the personal information to the selected one or more parts of the transaction account identifier.

The method according to claim 8, wherein the personal information are selected from a group consisting of name information, maiden name information, home address information, office address information, billing address information, birthdate information, electronic mail address information, social security number, familiar member' s name information, biometric information, and answer information relating to at least one security question.

10. The method according to claim 1, wherein the user account on which the aliasing operation (130) is performed to produce the tokenized sensitive information is a financial account.

11. The method according to claim 10, wherein the financial account is selected from the group consisting of a bank account, a credit card account, an investment account, a mutual fund account, a brokerage account, a loan account, a mortgage account, an electronic commerce account, an escrow account, a fund raising account, an educational account, an insurance account, a charitable account, a loyalty program account, a membership account, a privilege card account, a gift card account, a subscription account, an identification account, a payroll account, a utility account, and a fund transfer account.