Patent Description:
Existing biometric systems enable users to authenticate themselves using a biometric input, such as a fingerprint. When biometric systems are used for authenticating transactions, a user may choose a method of payment and then provide a biometric input to authenticate the transaction. The user of such systems must still carry his or her portable financial device, such as a credit card or electronic wallet, for initiating the transaction. Further, existing biometric systems that accept fingerprint inputs only allow for a single fingerprint to be scanned at once.

Individuals often have numerous transaction accounts for making purchases, such as several credit cards specific to different issuer institutions and/or merchants. Different transaction accounts may be associated with different rewards, depending on when, where, and how the transaction account is utilized. To avail themselves of these options, users typically have to carry and manage portable financial devices for each transaction account. Carrying numerous credit cards, for example, increases the likelihood that the cards may be lost, stolen, and/or compromised. Moreover, users have no way of knowing, without conducting research, what rewards are available for each transaction account, the spending limits and/or balances of each transaction account, and/or various other limitations and/or benefits that may be specific to each account.

Moreover, it is increasingly common for multiple users to "split" transactions between multiple transaction accounts. In such scenarios, each user typically hands a physical payment device, such as a credit or debit card, to a merchant agent to divide the transaction value by the number of individuals, and generate individual invoices for each user and each transaction account. This requires the users to relinquish their cards while the merchant is dividing the invoice, which allows for the possibility of fraud, and for each user to be in possession of their respective portable financial devices.

<CIT> discloses a method that enable buyers to pay for goods and services using only their fingerprints at the time and location of purchase. The method is based on buyers registering their fingerprints, associating them with one or more payment methods such as financial credit cards or bank accounts and optionally directing the system into selecting the appropriate payment method based on purchase conditions. Once the registration completes, buyers can use their fingerprints to instantly pay for purchases where the system automatically selects and charges one of the previously stored payment methods.

<CIT> describes a method for facilitating electronic transactions using an intelligent instrument. An authorization server enables users to obtain authorization credentials using the intelligent instrument by issuing a challenge to an intelligent token of the intelligent instrument. The intelligent token generates a challenge response and transmits the challenge response to the authorization server, which assembles credentials including a key for the electronic transaction upon validating the response. The authorization server sends the assembled credentials to the intelligent instrument and the intelligent instrument transmits the assembled credentials to the authorization server during a subsequent transaction. The authorization server validates the assembled credentials and provides authorization for the transaction in response to the validating the assembled credentials.

<CIT> discloses a fingerprint information-based user identity identification method comprising: receiving a plurality of fingerprint information input in a particular sequence from a front-end, wherein the plurality of fingerprint information and an input sequence of the plurality of fingerprint information constitute identity information; and performing a matching process between the identity information and information stored at a back-end to identify a user identity. The information stored at the back-end is fingerprint information stored at the back-end and a current sequence of fingerprints, the current sequence of the fingerprints is a random sequence generated by the back-end, and the random sequence generated by the back-end is presented to the user in the form of a particular symbol.

<CIT> describes a method for use by a mobile device. The method includes launching a software application requiring an identity verification of each of a plurality of users for performing a requested action, the plurality of users including a first user and a second user, receiving a first biometric information of the first user and a second biometric information of the second user, sending the first biometric information of the first user and the second biometric information of the second user to a server, comparing by the server the biometric information with corresponding entries in a user profile database, receiving notifications from the server as to whether the first and second biometric information correspond to biometric information in first user and second user profiles, respectively, presenting a user interface that allows users to approve and authorize the requested action, such as payment of a portions of a transaction, and performing the requested action, if the notifications indicate a match. <CIT> discloses a payment system comprising a payment gateway which receives a payment instruction from a payer and creates a suitable payment authorization request message based on the payment instruction. The payment authorization request message comprises identifying information of the payer's issuing financial institution and is forwarded to a payment network which routes the message to the payer's financial institution.

Accordingly, it is an object of the present invention to provide a system and method for processing biometric inputs that overcomes some or all of the deficiencies of the prior art.

According to a first aspect there is provided a point of sale system according to claim <NUM>.

In non-limiting embodiments, the fingerprint reader comprises at least one of the following: an optical fingerprint reader, a capacitive fingerprint reader, an ultrasound fingerprint reader, a thermal fingerprint reader, or any combination thereof.

In non-limiting embodiments, the point-of-sale system may further comprise (e) a biometric input device configured to receive a secondary biometric input, the secondary biometric input comprising at least one of the following: a face, an iris, a retina, hand geometry, finger geometry, an ear shape, DNA, a gait, a signature, a voice, or any combination thereof, wherein the transaction processing server is further programmed or configured to (v) authenticate the transaction message based at least partially on the secondary biometric input. In non-limiting embodiments, the at least one transaction message may be generated by combining the transaction data and fingerprint data derived from the plurality of fingerprints.

According to a second aspect there is provided a computer-implemented method according to claim <NUM>.

These and other features and characteristics of the present invention, as well as the methods of operation and functions of the related elements of structures and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. As used in the specification and the claims, the singular form of "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

Additional advantages and details of the invention are explained in greater detail below with reference to the exemplary embodiments that are illustrated in the accompanying schematic figures, in which:.

For purposes of the description hereinafter, the terms "end," "upper," "lower," "right," "left," "vertical," "horizontal," "top," "bottom," "lateral," "longitudinal," and derivatives thereof shall relate to the invention as it is oriented in the drawing figures. However, it is to be understood that the invention may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments or aspects of the invention. Hence, specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein are not to be considered as limiting.

As used herein, the terms "communication" and "communicate" refer to the receipt, transfer, and/or provision of one or more signals, messages, commands, or other type of data. For one unit (e.g., any device, system, or component thereof) to be in communication with another unit means that the one unit is able to directly or indirectly receive data from and/or provide data to (e.g., transmit, transfer, etc.) the other unit, including but not limited to the use of a direct or indirect connection that is wired and/or wireless in nature. Additionally, two units may be in communication with each other even though the data transmitted may be modified, processed, relayed, and/or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives data and does not actively transmit data to the second unit. As another example, a first unit may be in communication with a second unit if an intermediary unit processes data from one unit and transmits processed data to the second unit. It will be appreciated that numerous other arrangements are possible.

Non-limiting embodiments of the present invention are directed to a system, method, and computer program product for processing biometric inputs. Multiple fingerprints are registered with account identifiers such that different fingerprints can be used to conduct transactions with different accounts. As an example, a user may register three different fingerprints to be associated with three different, corresponding account identifiers. In some examples, multiple fingerprints of one or multiple users may be scanned at a point-of-sale (POS) system during a transaction. The fingerprints are used to identify accounts associated with those users. One or more accounts for conducting the transaction may be determined based on the multiple accounts assigned to the multiple fingerprints. For example, a preferred account may be determined from a plurality of accounts. In some embodiments, a transaction value may be apportioned across multiple accounts of one or more users. Non-limiting embodiments of the present invention are also directed to a POS system including a fingerprint scanner configured to scan multiple fingerprints simultaneously or substantially simultaneously.

As used herein, the term "transaction service provider" may refer to an entity that receives transaction authorization requests from merchants or other entities and provides guarantees of payment, in some cases through an agreement between the transaction service provider and an issuing institution. The term "transaction service provider" may also refer to one or more computer systems operated by or on behalf of a transaction service provider, such as a transaction processing server executing one or more software applications. A transaction processing server may include one or more processors and, in some non-limiting embodiments, may be operated by or on behalf of a transaction service provider.

As used herein, the term "issuer institution" may refer to one or more entities, such as a bank, that provide accounts to customers for conducting payment transactions, such as initiating credit and/or debit payments. For example, an issuer institution may provide an account identifier, such as a personal account number (PAN), to a customer that uniquely identifies one or more accounts associated with that customer. The account identifier may be embodied on a physical financial instrument, such as a payment card, and/or may be electronic and used for electronic payments.

As used herein, the term "account identifier" may include one or more PANs, tokens, or other identifiers associated with a customer account. The term "token" may refer to an identifier that is used as a substitute or replacement identifier for another account identifier, such as a PAN. Account identifiers may be alphanumeric or any combination of characters and/or symbols. Tokens may be associated with a PAN or other original account identifier in one or more databases such that they can be used to conduct a transaction without directly using the original account identifier. In some examples, an original account identifier, such as a PAN, may be associated with a plurality of tokens for different users or purposes. An issuer institution may be associated with a bank identification number (BIN) or other unique identifier that uniquely identifies it among other issuer institutions. The terms "issuer institution," "issuer bank," and "issuer system" may also refer to one or more computer systems operated by or on behalf of an issuer institution, such as a server computer executing one or more software applications. For example, an issuer system may include one or more authorization servers for authorizing a payment transaction.

As used herein, the term "acquirer institution" may refer to an entity licensed by the transaction service provider and approved by the transaction service provider to originate transactions using a portable financial device of the transaction service provider. The transactions may include original credit transactions (OCTs) and account funding transactions (AFTs). The acquirer institution may be authorized by the transaction service provider to originate transactions using a portable financial device of the transaction service provider. The acquirer institution may contract with a payment gateway to enable the facilitators to sponsor merchants. An acquirer institution may be a financial institution, such as a bank. The terms "acquirer institution," "acquirer bank," and "acquirer system" may also refer to one or more computer systems operated by or on behalf of an acquirer institution, such as a server computer executing one or more software applications.

As used herein, the term "merchant" may refer to an individual or entity that provides goods and/or services, or access to goods and/or services, to customers based on a transaction, such as a payment transaction. The term "merchant" or "merchant system" may also refer to one or more computer systems operated by or on behalf of a merchant, such as a server computer executing one or more software applications. A "point-of-sale (POS) system," as used herein, may refer to one or more computers and/or peripheral devices used by a merchant to engage in payment transactions with customers, including one or more card readers, near-field communication (NFC) receivers, RFID receivers, and/or other contactless transceivers or receivers, contact-based receivers, payment terminals, computers, servers, input devices, and/or other like devices that can be used to initiate a payment transaction.

As used herein, the term "mobile device" may refer to one or more portable electronic devices that are configured to communicate with one or more networks. As an example, a mobile device may include a cellular phone (e.g., a smartphone or standard cellular phone), a portable computer, a wearable device (e.g., watches, glasses, lenses, clothing, and/or the like), a personal digital assistant (PDA), and/or other like devices.

As used herein, the term "electronic wallet" refers to one or more electronic devices and/or software applications that are configured to initiate and/or conduct payment transactions. An electronic wallet may include an electronic wallet application that is executed by a mobile device operated by a customer and may further include server-side software and databases for maintaining and providing transaction data to the mobile device. An "electronic wallet provider" may include an entity that provides and/or maintains an electronic wallet for a customer, such as Google Wallet™, Android Pay™, Apple Pay®, Samsung Pay®, and/or other like electronic payment systems. In some non-limiting examples, an issuer bank may be an electronic wallet provider.

As used herein, the term "portable financial device" may refer to a payment card (e.g., a credit or debit card), a gift card, a smartcard, smart media, a payroll card, a healthcare card, a wrist band, a machine-readable medium containing account information, a keychain device or fob, an RFID transponder, a retailer discount or loyalty card, a mobile device executing an electronic wallet application, a personal digital assistant, a security card, an access card, a wireless terminal, and/or a transponder, as examples. The portable financial device may include volatile or nonvolatile memory to store information, such as an account identifier or a name of the account holder.

As used herein, the term "payment gateway" may refer to a payment processing system operated by or on behalf of an entity that contracts with an acquirer institution to provide transaction service provider payment services to one or more merchants using portable financial devices managed by the transaction service provider.

Referring now to <FIG>, a system <NUM> for processing biometrics inputs is shown according to a non-limiting embodiment. A POS system <NUM> is in communication with a fingerprint scanner <NUM>. The fingerprint scanner <NUM> is integrated with the POS system <NUM>. In some examples not according to the present invention, the fingerprint scanner <NUM> may be part of another device, such as a mobile device, that is in communication with or takes the place of the POS system <NUM>. The POS system <NUM> is also in communication with a payment gateway <NUM>, which is in communication with a transaction processing server <NUM>. It will be appreciated that the POS system <NUM> may also be in communication with the transaction processing server <NUM> without using a payment gateway <NUM> and that an acquirer system <NUM> may also be in communication with the payment gateway <NUM> and/or POS system <NUM> for facilitating a transaction. The POS system <NUM> may communicate with the payment gateway <NUM> and/or transaction processing server <NUM> through a public or private network. The transaction processing server <NUM> is in communication with a data storage device <NUM> which may be local or remote to the transaction processing server <NUM>. The data storage device <NUM> includes a biometric database <NUM> including fingerprint data corresponding to account data. The transaction processing server <NUM> is also in communication with an issuer system <NUM> and an acquirer system <NUM> for settling the transactions.

With continued reference to <FIG>, the POS system <NUM> is in communication with an input device <NUM>, such as but not limited to a barcode scanner, a card scanner, a wireless receiver or transceiver (e.g., NFC, Bluetooth®, RFID, and/or the like), a keyboard, a keypad, a mobile device, a microphone, and/or any combination thereof. The input device <NUM> receives transaction data such as, for example, a transaction value, a product (e.g., good or service) value, rewards account data, loyalty account data, and/or the like. The transaction data may be manually input and/or stored in a one- or two-dimensional barcode, transponder, magnetic strip, mobile device, and/or other like data storage device. To initiate a transaction, one or more users scan their fingerprints using the fingerprint scanner <NUM>. The fingerprints are scanned simultaneously or substantially simultaneously using the fingerprint scanner <NUM>. In response to scanning the fingerprints, the POS system <NUM> receives fingerprint data from the fingerprint scanner <NUM> and combines the fingerprint data with transaction data to generate a transaction message. The fingerprint data may include one or more images, strings of characters (e.g., binary or hexadecimal representations), and/or any other form of data. In some examples, the fingerprint data may be communicated in encrypted form for protection.

The transaction message may be generated based on one or more transaction parameters from the transaction data, such as the transaction amount, a transaction code, a merchant identifier (e.g., a unique merchant identifier, a merchant name, a merchant location, and/or the like) and other information concerning the transaction. The transaction message may include the transaction parameters as fields in the message and the captured fingerprint data is included in the transaction message. In other examples, the transaction message may include two separate messages, one including the fingerprint data and the other including the transaction data. It will be appreciated that there are various other ways to organize the transaction data and fingerprint data for communication to a remote system or device.

Still referring to <FIG>, the POS system <NUM> communicates the transaction message and/or fingerprint data to the payment gateway <NUM>. The payment gateway <NUM>, after identifying the appropriate transaction processing server <NUM>, communicates the transaction message to the transaction processing server <NUM>. As explained above, it will be appreciated that the transaction message also in examples that do not embody the invention be communicated directly to the transaction processing server <NUM> and/or an acquirer system <NUM> for initiating the transaction. The transaction message communicated to the transaction processing server <NUM> may be the same transaction message that was received from the POS system <NUM> or, in other examples, may be a modified or new transaction message based on the first transaction message. Once the transaction processing server <NUM> receives the fingerprint data, it then searches the biometric database <NUM> to match the fingerprint data with one or more account identifiers that have been registered. It will be appreciated that the biometric database <NUM> may be maintained and/or searched by any other entity or system. When one or more account identifiers are determined, the transaction processing server <NUM> determines which account identifiers to use to process the transaction and then authenticates and processes the transaction. For example, the transaction processing server <NUM> may settle the transaction with the issuer system <NUM> and acquirer system <NUM> and communicate a response message to the POS system <NUM> confirming or rejecting the transaction. It will be appreciated that, in further embodiments not according to the present invention, the fingerprint data may be processed at the POS system <NUM>, rather than remotely, to determine one or more account identifiers associated with the fingerprints.

The POS system <NUM> generates multiple transaction messages for a plurality of account identifiers. As an example, in embodiments in which a transaction value is apportioned among multiple accounts, a separate transaction message is generated for each account. It will be appreciated that other variations are possible.

Referring now to <FIG>, a system <NUM> for processing biometrics inputs is shown according to an example that does not embody the invention. The system <NUM> includes the components shown and discussed in connection with <FIG> in addition to a rules engine <NUM> and a data storage device <NUM> comprising a preference database <NUM> in communication with the transaction processing server <NUM>. The preference database <NUM> stores preference data which may include any type of data used to determine one or more preferred account identifiers from a plurality of account identifiers for a given transaction. For example, the preference data may include user-specified data, such as a ranking of account identifiers (or cards associated with account identifiers), reward preference, and/or spending ranges for the account identifiers (or cards associated with account identifiers), account balance data for accounts associated with the account identifiers, account spending limit data for accounts associated with the account identifiers, discount data for accounts associated with the account identifiers, rewards data for accounts associated with the account identifiers, and/or the like.

With continued reference to <FIG>, the system <NUM> includes a rules engine <NUM> in communication with the transaction processing server <NUM>. The rules engine <NUM> may be one or more software applications and/or hardware components programmed or configured to determine which account identifier of a plurality of account identifiers to use for a given transaction based on the preference data stored in the preference database <NUM>. For example, if a user scans two fingerprints using the fingerprint scanner <NUM>, the transaction processing server <NUM> may access the biometric database <NUM> to match each of the two fingerprints to an account identifiers for that user. After determining the account identifiers associated with the fingerprints, the rules engine <NUM> may apply one or more rules to determine a preferred account identifier. The preference data may be in the form of one or more rules to be executed by the rules engine <NUM>. For example, if the preference data includes a user-specified ranking of accounts and a credit or spending limit for each account, and the highest ranked account corresponding to a fingerprint does not have a sufficient credit or spending limit for the transaction value, the second-highest ranked account may be used or the transaction value may be split among the highest ranked and second-highest ranked accounts. In an example in which two or more fingerprints of a user are scanned, the rules engine <NUM> may determine which account identifier of the two or more account identifiers to use based on which account identifier has a higher cash back reward for that transaction. The rules engine <NUM> may process as inputs various transaction parameters such as, for example, a merchant category, a transaction value, rewards data stored in the preference database <NUM> or in a separate rewards or loyalty database, and/or user input provided through the input device <NUM>, a mobile device, the POS system <NUM>, or otherwise.

With continued reference to <FIG>, the rules engine <NUM> may determine which account identifier of a plurality of account identifiers to use based on a spending limit or account balance provided in the preference database <NUM> or in a separate account database. For example, the rules engine <NUM> may determine to use a first account identifier for transactions having less than a predetermined transaction value and a second account identifier for transactions having more than a predetermined transaction value. In other examples, the rules engine <NUM> may determine to use an account identifier associated with an account having a spending limit or credit limit that accommodates (e.g., is greater than) the transaction value. In still further examples, the rules engine <NUM> may determine to apportion the transaction value across one or more accounts based on user input, spending or credit limits, and/or the like. In some examples, the transaction value may be apportioned across multiple accounts to maximize rewards. It will be appreciated that various other arrangements are possible.

Still referring to <FIG>, the fingerprint scanner <NUM> may be used to scan one or more fingerprints of multiple users in series, simultaneously, or substantially simultaneously. For example, if two users wish to split a transaction among their respective accounts, each of those users may scan one or more fingerprints. If either user scanned more than one fingerprint, the rules engine <NUM> may determine a preferred account identifier for those user(s) as discussed herein. Once the transaction processing server <NUM> identifies one or more preferred account identifiers for each of the two users, the transaction value may be apportioned across those account identifiers. In some examples, the rules engine <NUM> may determine how to apportion the transaction value and, in other examples, the transaction value may be divided by the number of users and/or account identifiers (e.g., a <NUM>% apportionment for two users). In some examples, one or more users may further apportion their respective share of the transaction value across two or more accounts.

Referring now to <FIG>, a system <NUM> for processing biometrics inputs is shown according to a non-limiting embodiment. The system <NUM> includes the components shown and discussed in connection with <FIG> in addition to a mobile device <NUM> in communication with the POS system <NUM> and/or payment gateway <NUM>. The mobile device <NUM> includes or is in communication with a fingerprint scanner <NUM> and is used for initiating transactions with or without the POS system <NUM>. As an example, the mobile device <NUM> may be a cellular phone including a housing with a built-in fingerprint scanner <NUM>. The mobile device <NUM> may include an electronic wallet to initiate a transaction at a POS system <NUM>, such as an NFC payment transaction or an online transaction (e.g., Visa Checkout®), in addition to providing fingerprint data. In other embodiments, the mobile device <NUM> may only be used to provide fingerprint data and the transaction may otherwise be initiated at the POS system <NUM>. A user of the mobile device <NUM> scans one or more fingerprints on the mobile device <NUM> which are then communicated to the POS system <NUM> and used to generate a transaction message.

With continued reference to <FIG>, in non-limiting embodiments, the mobile device <NUM> may communicate with the payment gateway <NUM> and/or transaction processing server <NUM> to initiate the transaction. In such examples, the transaction message may be generated on the mobile device <NUM>. In embodiments in which multiple users provide fingerprint data for apportioning the transaction value between them, one or multiple mobile devices <NUM> may be used to provide the fingerprint data. For example, each user may use their respective mobile devices to provide fingerprint data and/or approve of the transaction. In some non-limiting embodiments, one or multiple mobile devices <NUM> may receive transaction confirmation messages. As an example, in embodiments in which multiple users provide fingerprint data for apportioning the transaction value between them, mobile devices <NUM> for each of the multiple users may receive a transaction confirmation message including an apportioned transaction value, a total transaction value, and other like transaction data. It will be appreciated that various other messages and communications may be transmitted to one or more mobile devices <NUM> before, during, and after a transaction.

Referring now to <FIG>, a POS system <NUM> is shown according to a non-limiting embodiment. The POS system <NUM> includes a processor <NUM>, a fingerprint scanner <NUM>, an input device <NUM>, and a communication device <NUM>. In some examples, the POS system may include a housing that includes the processor <NUM>. The fingerprint scanner <NUM>, input device <NUM>, and communication device <NUM> may be internal or external to the housing. The input device <NUM> may include a barcode scanner, a card scanner, a wireless receiver or transceiver (e.g., NFC, Bluetooth, RFID, and/or the like), a keyboard, a keypad, a mobile device, a microphone, and/or any other input device capable of receiving transaction data such as, for example, a transaction value, a product (e.g., good or service) value, rewards account data, loyalty account data, and/or the like. The communication device <NUM> may include a network adapter, a modem, and/or any other like system or device for communicating a transaction message to a payment gateway and/or transaction processing server. The fingerprint scanner <NUM> may be configured to scan multiple fingerprints simultaneously or substantially simultaneously. The fingerprint scanner <NUM> may also have a surface large enough to accommodate multiple fingers.

Referring now to <FIG>, a flow chart is shown for a method of registering biometrics according to a non-limiting embodiment. A user may participate in a registration process in which the user's fingerprints are scanned and the user's account information is input. One or more graphical user interfaces may be provided to allow a user to assign different fingerprints with different accounts, edit account information, change fingerprint assignments, input preference data, and create rules. At a first step <NUM>, a user scans a fingerprint. The user may scan a fingerprint for registration at a POS system, on a mobile device, and/or on any fingerprint scanner in communication with a processor. At a next step <NUM>, the user or some other entity inputs account data to be associated with that fingerprint. As an example, a user may swipe a payment card at a terminal, manually input an account identifier, and/or the like. The user may be prompted to input account data through one or more databases. At step <NUM>, the fingerprint is assigned to the input account data and stored in a biometric database. It will be appreciated that the fingerprint may also be associated with the account data in any other database, such as an account database.

With continued reference to <FIG>, at step <NUM>, it is determined whether the user wishes to input additional accounts to assign to different fingerprints. As an example, a graphical user interface may prompt the user to end the registration process or to add an additional fingerprint and/or account. If there are more accounts to assign, the method returns to step <NUM> to repeat the flow of steps <NUM>-<NUM> for each fingerprint. If, at step <NUM>, it is determined that there are no more accounts to assign, the method may proceed to step <NUM> where the user inputs preference data. The preference data may be input through a graphical user interface using an input device and/or one or more selectable options. Selectable options may include, for example, one or more drop-down menus, hyperlinks, buttons checkboxes, radio buttons, text input boxes, and/or the like. In some examples, the registration process may be carried out on a combination of devices and systems.

Referring now to <FIG>, a flow chart is shown for a method of processing biometrics inputs according to a non-limiting embodiment. At a first step <NUM>, a transaction is initiated at a POS system and/or on a mobile device. The transaction may be initiated by inputting transaction data into a POS system and/or a mobile device. At a next step <NUM>, one or more fingerprints are scanned using a fingerprint scanner. At step <NUM>, a transaction message is generated based on the fingerprint data and transaction data concerning the transaction being initiated. At step <NUM>, the transaction message is communicated to a transaction processing server. At step <NUM>, the transaction processing server determines at least one account identifier corresponding to the fingerprint data by matching the fingerprint data to other fingerprint data stored in a database and associated with account identifiers. At step <NUM>, the transaction is processed using the one or more account identifiers determined in step <NUM>.

The fingerprint data is additionally used to authenticate a user. The transaction processing server authenticates the user based on the fingerprint data. The authentication may occur before, during, or after identifying a corresponding and/or preferred account identifier. Moreover, the user may be authenticated using the same biometric database used to identify corresponding account identifiers or, in other examples, may be authenticated with one or more separate and/or third-party systems.

Referring to <FIG>, a fingerprint scanner <NUM> is shown according to a non-limiting embodiment. In the illustrated example, a first finger <NUM> of a first user and a second finger <NUM> of a second user are placed on the fingerprint scanner <NUM>. It will be appreciated that, in other non-limiting embodiments, a single user may have registered fingerprints of two fingers <NUM>, <NUM> on two different hands. As described herein, the fingerprint scanner may scan both the first finger <NUM> and second finger <NUM> simultaneously or substantially simultaneously. In other embodiments, the fingers <NUM>, <NUM> may be scanned in series. The fingerprint scanner <NUM> then communicates the fingerprint data to a POS system, server, or other system for processing. The transaction value may then be apportioned among accounts respectively associated with the first and second users. As described herein, the transaction value may be apportioned in various ways. It will be appreciated that the fingerprint scanner <NUM> may be any shape and/or size to accommodate any number of fingers. In some embodiments, each user may use separate fingerprint scanners <NUM>. Further, in some examples, multiple users may each scan multiple fingers such that their apportioned share of the transaction value is charged to a preferred account or apportioned further between multiple accounts for that user.

Claim 1:
A system for processing biometric inputs comprising a point-of-sale system (<NUM>), a transaction processing server (<NUM>), a payment gateway (<NUM>), and a data storage device (<NUM>) including a biometric database (<NUM>), the point-of-sale system (<NUM>) comprising:
(a) a fingerprint reader (<NUM>) configured to receive a plurality fingerprint data simultaneously or substantially simultaneously;
(b) an input device (<NUM>) configured to receive transaction data for a transaction, the transaction data comprising a transaction value;
(c) a communication device (<NUM>); and
(d) at least one processor (<NUM>) in communication with the fingerprint reader (<NUM>), the input device (<NUM>), and the communication device (<NUM>), the at least one processor programmed or configured to:
(i) generate a plurality of transaction messages, wherein a separate transaction message is generated for each of a plurality of account identifiers which relate to accounts among which the transaction value is to be apportioned and the plurality of account identifiers correspond to the plurality of fingerprint data received by the fingerprint reader, wherein the plurality of transaction messages for a transaction are based at least partially on the transaction data received by the input device and fingerprint data from the fingerprint reader, the plurality of transaction messages comprising an apportionment of the transaction value among the plurality of account identifiers; and
(ii) communicate, with the communication device, the plurality of transaction messages to the payment gateway (<NUM>);
wherein the payment gateway is configured to identify an appropriate transaction processing server (<NUM>) and communicate transaction messages to the transaction processing server;
wherein the transaction processing server is configured to:
in response to receiving fingerprint data in each transaction message, search the biometric database (<NUM>) to match the fingerprint data with one or more account identifiers that have been registered; and
once one or more account identifiers are determined, determine which account identifiers to use to process the transaction and then authenticate the transaction based on the fingerprint data and process the transaction.