System and method for identity validation for a regulated transaction

[0001] This application claims the benefit of U.S. Provisional Application Ser. No. 60/323,475 entitled SYSTEM AND METHOD FOR IDENTITY VALIDATION and filed on Sep. 19, 2001.

[0002] The present invention relates to the field of systems and methods for identity verification and/or validation for regulated transaction(s).

[0003] Each day, thousands of regulated transactions (e.g., purchasing of alcohol and/or tobacco products, voting, driving in restricted area(s), renting vehicle(s), purchasing fire arm(s), requesting financial aid for college tuition and/or boarding of aircraft) occur. Generally, the ability to engage in a regulated transaction is based, at least in part, upon a person desiring to engage in the regulated transaction possessing certain attribute(s) (e.g., age, gender, registration status with Selective Service, history of conviction of felony and/or inclusion on list(s) of governmental agency and/or private groups). As demonstrated by the recent hijacking of commercial aircraft and the tragic consequences resulting therefrom, there is a need for systems and methods for identity verification and/or validation related to regulated transaction(s).

[0004] The following presents a simplified summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not an extensive overview of the invention. It is not intended to identify key or critical elements of the invention or to delineate the scope of the invention. Its sole purpose is to present some concepts of the invention in a simplified form as a prelude to the more detailed description that is presented later.

[0005] The present invention relates to a system and method for validating and/or verifying identity related to regulated transaction(s). According to an aspect of the present invention, an identification validation system includes an identity transaction engine component and an input component. The identity transaction engine component facilitates searching of data store(s) in order to validate identity (e.g., related to a regulated transaction). The input component facilitates identification of an entity seeking to engage in a regulated transaction.

[0006] Another aspect of the present invention provides for a regulated transaction authorization system to include an identity transaction component, a communications component and input device(s) and/or output device(s). The input device(s) facilitate identifying a person to the regulated transaction authorization system. The output device(s) facilitate communication to user(s) of the regulated transaction authorization system (e.g., results of the identification transaction engine component).

[0007] Yet another aspect of the present invention provides for the identification validation system to search data store(s) having information associated with identification. The data store(s) can store governmental agency and/or private entity information.

[0008] Another aspect of the present invention provides for attribute(s) of a regulated transaction to be obtained by the identity transaction engine component to determine, at least in part, data store(s) to be searched.

[0009] Another aspect of the present invention provides for information stored in the attribute store to act as static and/or dynamic rule(s) to be applied to regulated transaction(s) processed by the transaction engine component. Thus, rule(s) can be defined such that transaction(s) that are improbable or impossible are identified for further processing or review. Also, rule(s) can be applied to data flowing through the transaction engine component to mitigate authorization of undesired regulated transaction(s).

[0010] Yet other aspects of the present invention provides for methods for identification validation, a computer readable medium having computer executable instructions for identification validation and a data packet adapted to be transmitted between two or more computer processes related to identification validation.

[0011] The following description and the annexed drawings set forth in detail certain illustrative aspects of the invention. These aspects are indicative, however, of but a few of the various ways in which the principles of the invention may be employed and the present invention is intended to include all such aspects and their equivalents. Other advantages and novel features of the invention will become apparent from the following detailed description of the invention when considered in conjunction with the drawings.

[0026] The present invention is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It may be evident to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate description of the present invention.

[0027] As used in this application, the term “component” is intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and a computer. By way of illustration, both an application running on a server and the server can be a component.

[0028] “Entity” is intended to include person(s) and/or object(s) (e.g., motor vehicle(s) and/or watercraft) desiring or attempting to engage in a regulated transaction. Further, “regulated transaction” includes transactions regulated and/or restricted by governmental and/or private concerns. Regulated transactions include, but are not limited to, voting, purchasing an alcoholic product, purchasing a tobacco product, sending a letter, shipping a package, shipping a letter, purchasing a ticket for a mode of transportation, boarding a mode of transportation, transporting a hazardous material, entering a restricted area, entering a restricted building, entering a restricted facility, purchasing a fire arm, obtaining employment, retaining employment, requesting financial aid for education, engaging in a financial transaction, obtaining admission to an institution, obtaining permission to enter a country, entering a country, obtaining a license, obtaining an identification document, obtaining permission to vote and/or granting work authorization.

[0029] Referring to FIG. 1, an identification validation system 110 is illustrated. The system 100 includes an identity transaction engine component 120 and an input component 130.

[0030] The input component 130 facilitates identification of an entity (e.g., person(s) and/or object(s)) seeking to engage in a regulated transaction to the identity transaction engine component 120. The input component 130 can receive information from input device(s), for example, a card reader, a magnetic card reader, keyboard, a touch screen device, a DNA fingerprint analyzer, a DNA profile analyzer, an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a smart card or the like. The input component 130 can provide information to the identity transaction engine component 120, for example, identifying a regulated transaction, identifying a requested action and/or identifying an entity desiring to engage in the regulated transaction.

[0031] Based, at least in part, upon information obtained from the input component 130, the identity transaction engine component 120 can search data store(s) in order to validate identification of a person, for example, related to a regulated transaction. It is to be understood and appreciated that the present invention is not limited by these examples and that any appropriate manner of identifying an entity to the input component 130 is encompassed by this invention.

[0032] The identity transaction engine component 120 can search data store(s) in order to validate identity (e.g., related to a regulated transaction). The identity transaction engine component 120 can be adapted to utilize attribute(s) of a regulated transaction in performing a search of data store(s). For example, for age regulated transaction(s) (e.g., voting, purchasing alcohol and/or tobacco product(s)), the identity transaction engine component 120 can utilize the attribute of a person's date of birth and/or age in order to determine whether the regulated transaction should be permitted. Other examples of regulated transactions include, but are not limited to, transporting hazardous material(s), sending a letter, shipping an item (e.g., package and/or letter), driving in restricted area(s), renting vehicle(s), purchasing fire arm(s), requesting financial aid for college tuition, purchasing a ticket for a mode of transportation (e.g., aircraft, bus and/or ship) and/or boarding a mode of transportation. Other examples of attribute(s) include, but are not limited to, DNA fingerprint and/or profile, ethnicity, citizenship, religious affiliation, political affiliation, biometric data, height, weight, health status (e.g., failure to have particular disease(s)), gender, registration status with Selective Service, history of conviction of felony and/or inclusion on list(s) of governmental agencies and/or private groups.

[0033] The identification validation system 110 can communicate with remote system(s) (not shown) (e.g., database(s) and/or data storage system(s). For example, the identification validation system 110 can search the remote system(s) (not shown) based, at least in part, upon information associated with a person's identity (e.g., name, address, social security number, identification number, passport number, selective service number, voter identification number and/or date of birth) in order to validate and/or verify identity and possession of attribute(s) to engage in a regulated transaction.

[0034] The identification validation system 110 can be coupled to remote system(s) (not shown) utilizing, for example, a telephone connection, a network connection, an extranet, an intranet, the Internet, wireless communication, a satellite link, direct serial communication and/or direct parallel communication. Information exchanged between the identification validation system 110 and remote system(s) (not shown) can be accomplished using a variety of format(s). Information exchanged between the identification validation system 110 and remote system(s) (not shown) can be performed in a variety of secure and/or encrypted manners.

[0035] Next, referring to FIG. 2, an identification validation system 210 is illustrated. The system 210 includes an identity transaction engine component 220, a communications component 230 and input device(s) 240. Optionally, the system 210 can include output device(s) 250. The output device(s) 250 can forward data packet(s) to yet other systems (not shown) to provide information about the identity verification transaction, including system decision(s). These other systems (not shown) may utilize the information provided in these data packet(s) to take some predefined further action (e.g., remove passenger baggage from an aircraft, notify the Amber system, etc.).

[0036] The identity transaction engine component 220 facilitates searching of data store(s) (not shown) in order to validate identity related to a regulated transaction. The identity transaction engine component 220 can be adapted to utilize attribute(s) of a regulated transaction in performing a search of data store(s). For example, for a person seeking to board an aircraft, the identity transaction engine component can utilize the attribute(s) of a person's DNA fingerprint, name, date of birth and/or age in order to determine whether the person is on a governmental list of suspected terrorists, fleeing felons and/or fugitives from justice. A person on one of these governmental list(s) would be denied permission to board the aircraft.

[0037] The communications component 230 facilitates communication between the identification validation system 210 and remote system(s) (not shown) utilizing, for example, a network connection, an extranet, an intranet, the Internet, wireless communication, direct serial communication and/or direct parallel communication. Information exchanged between the communications component 230 and remote system(s) (not shown) can be accomplished using a variety of format(s). Information exchanged between the system identification validation system 210 and remote system(s) (not shown) can be performed in a variety of secure and/or encrypted manners. For example, the communications component 230 can be coupled to the remote system(s) (not shown) utilizing a high-speed, secure Internet connection.

[0038] The input device(s) 240 facilitates identification of an entity (e.g., person) seeking to engage in a regulated transaction. The input device(s) 240 can include a card reader, a magnetic card reader, keyboard, a touch screen device, an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a smart card reader, a podium, or the like. Based at least in part upon information obtained from the input device(s), the identity transaction engine component can search data store(s) in order to validate identification of a person, for example, related to a regulated transaction.

[0039] The input device(s) 240 can further include a DNA fingerprint and/or profile analyzer. For example, a DNA sample (e.g., blood, hair and/or skin sample) can be acquired from a person desiring to engage in a regulated transaction. A DNA fingerprint and/or profile of the DNA sample can be sent by the DNA fingerprint and or profile analyzer to the identity transaction engine component 220. The identity transaction component 220 can analyze the DNA sample and/or compare it to DNA fingerprint and/or profile information stored in data store(s). Thus, based at least in part upon the DNA sample, the identity transaction engine component 220 can determine whether the entity possesses attribute(s) required to engage in the regulated transaction.

[0040] It is to be understood and appreciated that the present invention is not limited by these examples and that any appropriate manner of identifying an entity to the identity transaction engine component 220 is encompassed by this invention.

[0041] Optionally, the system 200 can include output device(s) 250 which facilitate communication to user(s) of the system 200. The output device(s) 250 can include, a touch screen device, a computer monitor, a television screen, a printer, a personal digital assistant, a wireless telephone display and/or speaker(s). The output device(s) 250 can facilitate communication of result(s) obtained by the identity transaction engine component 220 to a user of the system 200. It is to be understood and appreciated that the present invention is not limited by these examples and that any appropriate manner of communicating information to and/or from the identity transaction engine component 220 is encompassed by this invention. It is further to be appreciated that based at least in part upon result(s) of the identity transaction engine component 220, the regulated transaction can be allowed, the regulated transaction can be refused and/or other action(s) can be initiated (e.g., based at least in part upon attribute(s) of related to the regulated transaction.)

[0042] Turning to FIG. 3, a regulated transaction authorization system 300 is illustrated. The system 300 includes an identification validation system 310 having an identity transaction engine component 320, a communications component 330, input device(s) 340 and, optionally, output device(s) 350. The system 300 further includes a first data store 360₁ through an Nth data store 360_N, N being an integer greater to or equal to one. The data stores 360₁ through 360_N can be referred to collectively as the data store(s) 360.

[0043] The identity transaction engine component 320 facilitates determination of which data store(s) 360 are relevant to a particular regulated transaction and/or facilitates searching of data store(s) 360 in order to authorize a regulated transaction. The identity transaction engine component 320 can be adapted to utilize attribute(s) of a regulated transaction in performing a search of data store(s) 360 (e.g., regulated transaction(s) can have differing attribute(s)). For example, for a person seeking to vote in an election, the identity transaction engine component can utilize a person's name, date of birth, and/or voter's registration number in order to determine whether the person is a registered voter and/or eligible to vote. Even if the person is officially registered to vote, the identity transaction engine component 320 can determine whether to cross check the official registration against other data store(s) 360 to determine if there are any other impediments to voting (e.g., the voter is deceased, is a felon and/or has renounced his/her citizenship). Further, the identity transaction engine component 320 can determine whether the person has already voted in the subject election. Person(s) not registered to vote, convicted of a felony and/or who had already voted in the subject election would not be permitted to vote. The identity transaction engine component 320 can further facilitate determining whether a proposed regulated transaction is logical (e.g., a person boarding an aircraft in New York should not be simultaneously in Seattle). The identity transaction engine component 320 can determine data store(s) 360 to be searched base at least in part upon information stored in the attribute store 370.

[0044] The communications component 330 facilitates communication between the identification validation system 310 and the data store(s) 360 utilizing, for example, a network connection, an extranet, an intranet, the Internet, wireless communication, direct serial communication and/or direct parallel communication. Information exchanged between the communications component 330 and the data store(s) 360 can be accomplished using a variety of format(s). Information exchanged between the system identification validation system 310 and data store(s) 360 can be performed in a variety of secure and/or encrypted manners. For example, the communications component 330 can be coupled to the data store(s) 360 utilizing a high-speed, secure Internet connection.

[0045] The input device(s) 340 facilitate identification of an entity (e.g., person) seeking to engage in a regulated transaction. The input device(s) 340 can include a card reader, a magnetic card reader, keyboard, a touch screen device, an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a DNA fingerprint analyzer, a DNA profile analyzer, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a smart card or the like. Based at least in part upon information obtained from the input device(s) 340, the identity transaction engine component 320 can search data store(s) 360 in order to determine whether an entity is authorized to engage in a regulated transaction. It is to be understood and appreciated that the present invention is not limited by these examples and that any appropriate manner of identifying an entity to the identity transaction engine component 320 is encompassed by this invention.

[0046] Optionally, the regulated transaction authorization system 300 can include output device(s) 350 which facilitate communication to user(s) of the system 300. The output device(s) 350 can include, a touch screen device, a computer monitor, a television screen, a printer, a personal digital assistant, a wireless telephone display, speaker(s), and/or another computer system. The output device(s) 350 can facilitate communication of result(s) obtained by the identity transaction engine component 320 to a user of the regulated transaction authorization system 300. It is to be understood and appreciated that the present invention is not limited by these examples and that any appropriate manner of communicating information to and/or from the identity transaction engine component 320 is encompassed by this invention.

[0047] The data store(s) 360 include information associated with identification of entities (e.g., people). For example, the data store(s) 360 can be governmental (Federal, state, regional and/or local) data store(s) related to, for example, the Social Security Administration, Drivers' license agencies (e.g., Bureau/Department of Motor Vehicles), state identification card issuing agencies, the Selective Service system, the military, voter registration, birth certificates issuing authorities, the Immigration and Naturalization Service, the Justice Department, the Bureau of Alcohol, Tobacco and Firearms, the Federal Bureau of Investigation and/or the Central Intelligence Agency. The data store(s) 360 can also include private, non-governmental, data store(s) that can include, for example, a periodically updated copy of governmental data and/or a new set of data about an individual. Additionally, the data store(s) 360 can include DNA information (e.g., collected by governmental and/or private entities) and/or other biometric information. Information can be stored in the data store(s) 360 in a variety of format(s) including, but not limited to, hierarchical database(s) and/or relational database(s). Information can be stored in the data store(s) 360 in a variety of data structure(s) including, but not limited to, lists, arrays, databases and/or datacubes. For example, information stored in the data store(s) can be text (e.g., alphanumeric), graphical, audio, video and/or digitally stored DNA information.

[0048] The attribute store 370 can store information related to regulated transaction(s) (e.g., attribute(s)). Based at least in part upon information in the attribute store 370, the identity transaction engine component 320 can determine which data store(s) 360 to search, which output device(s) 350 (if any) to forward the resulting information or decision(s) and/or whether the data is to be re-captured through the input device(s) 340. Information can be stored in the attribute store 370 statically and/or dynamically.

[0049] For example, information stored in the attribute store 370 can act as static and/or dynamic rule(s) to be applied to regulated transaction(s) processed by the transaction engine component 320. Thus, rule(s) can be defined such that transactions that are improbably and/or impossible are identified for further processing and/or review. Additionally, rule(s) can be applied to data flowing through the transaction engine component 320 to mitigate authorization of undesired regulated transaction(s).

[0050] Turning to FIG. 4, a regulated transaction authorization system 400 is illustrated. The system 400 includes an identification validation system 410 having an identity transaction engine component 420, a communications component 430, input device(s) 440 and, optionally, output device(s) 450. The system 400 further includes at least one data store(s) 460 which can be associated with social security records 462, drivers license records 464, state ID records 466, military ID records 468, voter registration records 470, birth records 472, passport records 474 and/or selective service records 476. The data stores set forth in FIG. 4, are only examples of such data stores that can be employed in order to validate identity with regard to regulated transaction(s). Such data stores can be within or outside of the United States of America. Other data stores may include, but are not limited to tax records, identity card data stores, retirement records, pension records and/or baptismal data stores.

[0051] The identity transaction engine component 420 facilitates searching of data store(s) 460 in order to validate and/of verify identification related to a regulated transaction. The identity transaction engine component 420 can be adapted to utilize attribute(s) of a regulated transaction in performing a search of data store(s) 460.

[0052] The communications component 430 facilitates communication between the identification validation system 410 and the at least one data store(s) 460 utilizing, for example, a network connection, an extranet, an intranet, the Internet, wireless communication, direct serial communication and/or direct parallel communication. Information exchanged between the communications component 430 and the at least one data store(s) can be accomplished using a variety of format(s). Information exchanged between the identification validation system 410 and the at least one data store(s) 460 can be performed in a variety of secure and/or encrypted manners. For example, the communications component 430 can be coupled to the at least one data store(s) 460 utilizing a high-speed, secure Internet connection.

[0053] The input device(s) 440 facilitates identification of an entity (e.g., person) seeking to engage in a regulated transaction. The input device(s) 440 can include a card reader, a magnetic card reader, a bar code reader, keyboard, a touch screen device, an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a DNA fingerprint analyzer, a DNA profile analyzer, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a smart card reader or the like. Based at least in part upon information obtained from the input device(s) 440, the identity transaction engine component 420 can search data store(s) 460 in order to validate identification of an entity related to a regulated transaction. It is to be understood and appreciated that the present invention is not limited by these examples and that any appropriate manner of identifying an entity to the identity transaction engine component 420 is encompassed by this invention.

[0054] Optionally, the system 400 can include output device(s) 450 which facilitate communication to user(s) of the system 400. The output device(s) 450 can include, a touch screen device, a computer monitor, a television screen, a printer, a personal digital assistant, a wireless telephone display and/or speaker(s). The output device(s) 450 can facilitate communication of result(s) obtained by the identity transaction engine component 420 to a user of the system 400. It is to be understood and appreciated that the present invention is not limited by these examples and that any appropriate manner of communicating information to and/or from the identity transaction engine component 420 is encompassed by this invention.

[0055] The at least one data store(s) 460 can be, for example, associated with social security records 462, drivers license records 464, state ID records 466, military ID records 468, voter registration records 470, birth records 472, passport records 474 and/or selective service records 476 and include information associated with identification of entities (e.g., persons). Information can be stored in a variety of format(s) including, but not limited to, hierarchical database(s) and/or relational database(s). Information can be stored in a variety of data structure(s) including, but not limited to, lists, arrays, databases and/or datacubes. For example, information stored in the data store(s) 460 can be text, alphanumeric, graphical, audio, video, digitized DNA information and/or a variety of digitized information.

[0056] In view of the exemplary systems shown and described above, methodologies that may be implemented in accordance with the present invention, will be better appreciated with reference to the flow charts of FIGS. 5, 6, 7, 8, 9, 10, 11, 12, 13 and 14. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of blocks, it is to be understood and appreciated that the present invention is not limited by the order of the blocks, as some blocks may, in accordance with the present invention, occur in different orders and/or concurrently with other blocks from that shown and described herein. Moreover, not all illustrated blocks may be required to implement a methodology in accordance with the present invention. In addition, it will be appreciated that the exemplary methods 500, 600, 700, 800, 900, 1000, 1100, 1200, 1300 and 1400 and other methods according to the invention may be implemented in association with the identification validation system illustrated and described herein, as well as in association with other systems and apparatus not illustrated or described.

[0057] The invention may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically the functionality of the program modules may be combined or distributed as desired in various embodiments.

[0058] Turning to FIG. 5, a methodology 500 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. At 510, identification (e.g., DNA sample, driver's license, state identification card, military identification card, vehicle license plate, vehicle identification number, and/or passport) is received (e.g., utilizing a magnetic card reader, or a device appropriate to capture the data from the identification at hand). At 520, attribute(s) regarding the regulated transaction are received. For example, attribute(s) can be age, status of driver's license (e.g., valid, invalid and/or suspended), gender, registration status with Selective Service, status on various governmental agency list(s) and/or status on various private entity list(s)). Next, at 530, data store(s) to be searched are identified, for example, based at least in part upon attribute(s) related to the regulated transaction—driver's license data store(s) can be searched for an alcohol purchasing transaction, while governmental agency list(s) data store(s) can be searched for an airport boarding transaction. At 540, the data store(s) identified are searched (e.g., by an identity transaction engine component). At 550, a determination is made whether the identification is valid. If the determination at 550 is NO, processing continues at 580. If the determination at 550 is YES, at 560, a determination is made whether the person has the attribute(s) for the regulated transaction. If the determination at 560 is NO, processing continues at 580. If the determination at 560 is YES, at 570, the regulated transaction is allowed and no further processing occurs. At 580, the regulated transaction is not allowed and no further processing occurs.

[0059] Turning to FIG. 6, a methodology 600 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. At 610, prescreened identification is received. For example, a person who frequently engages in air travel can voluntarily subject himself to investigation by a prescreening authority (e.g., by a governmental agency and/or private entity) and thus, become, “prescreened”. The prescreening authority (e.g., governmental agency and/or private entity) can, for example, update the person's “prescreened” status (e.g., by monitoring list(s) of suspected terrorists, fleeing felons and/or fugitives from justice). Next, at 620, data store(s) (e.g., a data store of prescreened persons) is searched. At 630, a determination is made whether the identification is valid. If the determination at 630 is NO, processing continues at 670. If the determination at 630 is YES, at 640, the person's identity is confirmed (e.g., utilizing a secure password, DNA fingerprint analyzer, iris scanner, retinal scanner and/or fingerprint reader). At 650 a determination is made whether the identity was properly confirmed. If the determination at 650 is NO, processing continues at 670. If the determination at 650 is YES, at 660, the regulated transaction is allowed and no further processing occurs. At 670, the regulated transaction is denied.

[0060] Referring to FIG. 7, a methodology 700 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. For example, the regulated transaction (e.g., purchase of alcohol and/or tobacco product(s)) can be based at least in part upon a single attribute (e.g., age) or a plurality of attributes. At 710, identification is received (e.g., utilizing a magnetic card reader). At 720, data store(s) are searched (e.g., by an identity transaction engine component). At 730, a determination is made whether the identification is valid. If the determination at 730 is NO, processing continues at 760. If the determination at 730 is YES, at 740, a determination is made whether the person's age is greater to or equal to the minimum age for the transaction (e.g., purchasing alcohol and/or tobacco products). If the determination at 740 is NO, processing continues at 760. If the determination at 740 is YES, at 750, the transaction is permitted and no further processing continues. At 760, the transaction is rejected.

[0061] Next, turning to FIG. 8, a methodology 800 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. For example, the regulated transaction can be related to boarding an aircraft. At 810, identification is received (e.g., utilizing a magnetic card reader). For example, the identification can be a driver's license, state identification card, military identification card and/or passport. At 820, data store(s) (e.g., list(s) of suspected terrorists, fleeing felons and/or fugitives from justice) are searched (e.g., by an identity transaction engine component). At 830, a determination is made whether the identification is valid. If the determination at 830 is NO, processing continues at 870. If the determination at 830 is YES, at 840, a determination is made whether the person is on a suspected terrorist list. If the determination at 840 is YES, processing continues at 880. If the determination at 840 is NO, at 850, a determination is made whether the person has a warrant and/or is an escaped criminal (e.g., fleeing felon and/or fugitive from justice). If the determination at 850 is YES, processing continues at 880. If the determination at 850 is NO, at 860, a boarding pass is issued for the person and no further processing occurs. At 870, the transaction is rejected (e.g., no boarding pass issued) and no further processing occurs. At 880, the transaction is rejected (e.g., no boarding pass issued) and/or the authorities (e.g., Federal, State and/or local law enforcement agencies) are notified.

[0062] Referring next to FIG. 9, a methodology 900 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. For example, the regulated transaction can be voting in an election. At 910, identification is received (e.g., utilizing a magnetic card reader). For example, the identification can be a driver's license, voter's registration card, state identification card, military identification card, vehicle license plate, vehicle identification number, and/or passport. At 920, data store(s) (e.g., list(s) of suspected terrorists, fleeing felons and/or fugitives from justice and/or voter registration record(s)) are searched (e.g., by an identity transaction engine component). At 930, a determination is made whether the identification is valid. If the determination at 930 is NO, processing continues at 970. If the determination at 930 is YES, at 940, a determination is made whether the person is a convicted felon. If the determination at 940 is YES, processing continues at 970. If the determination at 940 is NO, at 950, a determination is made whether the person has already voted in the subject election. If the determination at 950 is YES, processing continues at 970. If the determination at 950 is NO, at 960, the person is allowed to vote and no further processing occurs. At 970, the person is not allowed to vote.

[0063] Turning next to FIG. 10, a methodology 1000 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. For example, the regulated transaction can be related to driving in a restricted area (e.g., through a tunnel). At 1010, identification is received (e.g., utilizing a magnetic card reader). For example, the identification can be a driver's license, state identification card, military identification card, vehicle license plate, vehicle identification number, and/or passport. At 1020, data store(s) (e.g., list(s) of suspected terrorists, fleeing felons and/or fugitives from justice) are searched (e.g., by an identity transaction engine component). At 1030, a determination is made whether the identification is valid. If the determination at 1030 is NO, processing continues at 1070. If the determination at 1030 is YES, at 1040, a determination is made whether the person is on a suspected terrorist list. If the determination at 1040 is YES, processing continues at 1080. If the determination at 1040 is NO, at 1050, a determination is made whether the person has a warrant and/or is an escaped criminal (e.g., fleeing felon and/or fugitive from justice). If the determination at 1050 is YES, processing continues at 1080. If the determination at 1050 is NO, at 1060, the person is permitted to drive in the restricted area and no further processing occurs. At 1070, the person is not permitted to drive in the restricted area and no further processing occurs. At 1080, the person is not permitted to drive in the restricted area and/or the authorities (e.g., Federal, State and/or local law enforcement agencies) are notified and no further processing occurs.

[0064] Referring to FIG. 11, a methodology 1100 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. For example, the regulated transaction can be related to allowing a particular vehicle into a restricted area (e.g., through a tunnel). At 1110, identification is received (e.g., utilizing a transponder and/or transmitter embedded in the vehicle and/or receiving the license plate number). For example, the identification can be a Vehicle Identification Number. At 1120, data store(s) (e.g., list(s) of stolen vehicles) are searched (e.g., by an identity transaction engine component). At 1130, a determination is made whether the vehicle identification is valid. If the determination at 1130 is NO, processing continues at 1160. If the determination at 1130 is YES, at 1140, a determination is made whether the vehicle has been reported stolen. If the determination at 1140 is YES, processing continues at 1170. If the determination at 1140 is NO, at 1150, the vehicle is permitted in the restricted area and no further processing occurs. At 1160, the vehicle is not permitted to drive in the restricted area and no further processing occurs. At 1170, the vehicle is not permitted in the restricted area and/or the authorities (e.g., Federal, State and/or local law enforcement agencies) are notified and no further processing occurs.

[0065] Next, turning to FIG. 12, a methodology 1200 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. For example, the regulated transaction can be related to renting a vehicle. At 1210, identification (e.g., driver's license) is received (e.g., utilizing a magnetic card reader). For example, the identification can be a driver's license, state identification card, military identification card and/or passport. At 1220, data store(s) (e.g., drivers license records, list(s) of suspected terrorists, fleeing felons and/or fugitives from justice) are searched (e.g., by an identity transaction engine component). At 1230, a determination is made whether the identification (e.g., driver's license) is valid. If the determination at 1230 is NO, processing continues at 1270. If the determination at 1230 is YES, at 1240, a determination is made whether the person's age is greater than or equal to the minimum age to rent a vehicle. If the determination at 1240 is NO, processing continues at 1270. If the determination at 1240 is YES, at 1250, a determination is made whether the person has a warrant and/or is an escaped criminal (e.g., fleeing felon and/or fugitive from justice). If the determination at 1250 is YES, processing continues at 1280. If the determination at 1250 is NO, at 1260, the person is permitted to rent the vehicle and no further processing occurs. At 1270, rental of the vehicle is rejected and no further processing occurs. At 1280, rental of the vehicle is rejected and/or the authorities (e.g., Federal, State and/or local law enforcement agencies) are notified and no further processing occurs.

[0066] Referring next to FIG. 13, a methodology 1300 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. For example, the regulated transaction can be related to purchasing a firearm. At 1310, identification (e.g., driver's license) is received (e.g., utilizing a magnetic card reader). For example, the identification can be a driver's license, state identification card, military identification card and/or passport. At 1320, data store(s) (e.g., drivers license records, list(s) of suspected terrorists, fleeing felons and/or fugitives from justice) are searched (e.g., by an identity transaction engine component). At 1330, a determination is made whether the identification is valid. If the determination at 1330 is NO, processing continues at 1390. If the determination at 1330 is YES, at 1340, a determination is made whether the person's age is greater than or equal to the minimum age to purchase a firearm. If the determination at 1340 is NO, processing continues at 1390. If the determination at 1340 is YES, at 1350, a determination is made whether the person is a convicted felon. If the determination at 1350 is YES, processing continues at 1390. If the determination at 1390 is NO, at 1360, a determination is made whether the person has a warrant and/or is an escaped criminal (e.g., fleeing felon and/or fugitive from justice). If the determination at 1360 is YES, processing continues at 1380. If the determination at 1360 is NO, at 1370, the person is permitted to purchase the firearm and no further processing occurs. At 1390, purchase of the firearm is rejected and no further processing occurs. At 1380, purchase of the firearm is rejected and/or the authorities (e.g., Federal, State and/or local law enforcement agencies) are notified and no further processing occurs.

[0067] Turning to FIG. 14, a methodology 1400 for identification validation for a regulated transaction in accordance with an aspect of the present invention is illustrated. For example, the regulated transaction can be related to applying for financial aid for college tuition. At 1410, identification (e.g., driver's license) is received (e.g., utilizing a magnetic card reader). For example, the identification can be a driver's license, state identification card, military identification card and/or passport. At 1420, data store(s) (e.g., drivers license records and/or Selective Service records) are searched (e.g., by an identity transaction engine component). At 1430, a determination is made whether the identification is valid. If the determination at 1430 is NO, processing continues at 1480. If the determination at 1430 is YES, at 1440, a determination is made whether the person's gender is male. If the determination at 1440 is NO, processing continues at 1470. If the determination at 1440 is YES, at 1450, a determination is made whether the person's age is between eighteen years and twenty-six years. If the determination at 1450 is NO, processing continues at 1470. If the determination at 1450 is YES, at 1460 a determination is made whether the person has registered with the Selective Service. If the determination at 1460 is NO, processing continues at 1480. If the determination at 1460 is YES, at, the person is permitted to request (e.g., apply for) financial aid and no further processing occurs. At 1480, the person's request to apply for financial aid is rejected and no further processing occurs.

[0068] Although the invention has been shown and described with respect to certain illustrated aspects, it will be appreciated that equivalent alterations and modifications will occur to others skilled in the art upon the reading and understanding of this specification and the annexed drawings. In particular regard to the various functions performed by the above described components (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure, which performs the function in the herein illustrated exemplary aspects of the invention. In this regard, it will also be recognized that the invention includes a system as well as a computer-readable medium having computer-executable instructions for performing the acts and/or events of the various methods of the invention.

[0069] In addition, while a particular feature of the invention may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “includes”, “including”, “has”, “having”, and variants thereof are used in either the detailed description or the claims, these terms are intended to be inclusive in a manner similar to the term “comprising.”