Patent ID: 12236448

DETAILED DESCRIPTION

According to various exemplary embodiments, a method of payment using rewards points is provided to customers of card issuing entities, such as banks or other financial institutions. The card issuing entity may provide rewards programs and accounts in conjunction with credit card accounts, wherein rewards points are earned by the customer for each purchase the customer makes using a card issued by the entity. The rewards points earned by the customer may be redeemed for a variety of goods and services or cash. A customer seeking to purchase goods or services in a merchant point of sale transaction by redeeming rewards points may provide authentication data to a mobile device, such as a cellular phone, smart phone, personal digital assistant (PDA), tablet device, laptop computer or other device. The mobile device may be proximity enabled by, for example, a near field communications (NFC) or host card emulation (HCE) equipped device.

The authentication data may include, for example, account information such as the customer's name, credit account or credit card number, card expiration data, and rewards account number. The authentication data may further contain, for example, username and password credentials for online access to the customer's credit account and/or rewards account. According to an exemplary embodiment, the customer's authentication data may be received at the mobile device via a contactless smart card that cryptographically generates a code which can be verified by the card issuer's systems for purposes of authenticating the customer. According to another exemplary embodiment, biometric data may be provided to the mobile device for purposes of authenticating the customer, and account data may be stored on the mobile device.

In some embodiments, the customer may execute a mobile application on the mobile device in order to facilitate receiving the authentication data. For example, the customer may tap the contactless smart card to the mobile device in order to execute a mobile application that retrieves the authentication data from the contactless smart card. Alternatively, the mobile application may be executed upon receiving a signal from a merchant's point of sale device, or upon the customer tapping a graphical element displayed on the mobile device.

The mobile device may further receive a payment amount for the merchant point of sale transaction. In embodiments where the customer has executed a mobile application on the mobile device in order to facilitate receiving the authentication data, the customer may input the payment amount via a graphical user interface of the mobile application. For example, the merchant's point of sale device may display the payment amount, or the merchant may verbally convey the payment amount, and the customer may enter this amount in a field provided in the graphical user interface. In other embodiments, the payment amount may be electronically transmitted to the mobile device from the merchant's point of sale device.

The mobile device may send the customer's authentication data and the payment amount to an account management system associated with the card issuing entity. Upon receiving the customer's authentication data and the payment amount, the account management system may authenticate the customer. The account management system may also access the customer's credit account and rewards account. The account management system may determine the amount of rewards points currently available for the customer to redeem and may further determine a number of payment options selectable by the customer. The selectable payment options may include an option to redeem a portion of the rewards points currently available for the customer to fund a portion of the payment amount. For example, the selectable payment options may include an option to redeem a portion of the rewards points to fund the entire payment amount, an option to redeem a portion of the rewards points to fund less than the entire payment amount, and an option not to redeem any of the portion of rewards points.

The selectable payment options may be sent from the account management system to the mobile device. Upon receiving the selectable payment options from the account management system, the mobile device may present them to the customer. In some embodiments where the customer has executed a mobile application on the mobile device in order to facilitate receiving the authentication data, the mobile device may display the selectable payment options via a graphical user interface of the mobile application. The customer may select one of the payment options from the displayed payment options. For example, in some embodiments where the customer has executed a mobile application on the mobile device to display the selectable payment options, the mobile application may be further configured to receive the customer's selection via a graphical user interface.

The customer's selected payment option may be sent to the account management system. Upon receiving the customer's selected payment option, the account management system may send an authorized form of payment to the mobile device. The form of payment may be a single form of payment configured for presentation to the merchant's point of sale device, regardless of whether the customer is funding all, a portion, or none of the payment amount by redeeming rewards points. In some embodiments, the authorized form of payment is displayable by the mobile device, such as a barcode that may be scanned by the merchant's point of sale device. In some embodiments, the form of payment may be configured for electronic transmission from the mobile device to the merchant's point of sale device.

As will be appreciated, the methods of payment using rewards points described in the various exemplary embodiments eliminate one of the major limitations on the manner in which points may currently be redeemed by allowing customers to directly redeem their rewards points in merchant transactions. Customers may redeem rewards points for all, some, or none of the payment amount in the same transaction as opposed to redeeming rewards points for predetermined fixed cash amounts using a separate payment device representing the cash value of the redeemed points. That is, customers may conveniently access both their credit account funds and their rewards account at a merchant location.

Furthermore, the methods of payment using rewards points described in the various exemplary embodiments are not limited to rewards points offered by or in partnership with the merchant as opposed to the card issuer, and do not require the merchant to implement and maintain software and hardware updates to point of sale devices in order to process additional customer interactions for points redemption transactions. Rather, the form of payment provided herein may leverage a customer's mobile device in combination with existing merchant point of sale devices, such as barcode scanning devices and NFC devices, without modification to these devices.

Referring now toFIG.1, a data flow diagram illustrating a process100for payment using rewards points according to an exemplary embodiment is shown.FIG.1generally illustrates an embodiment of process100wherein data is variously exchanged between a mobile device101, such as a cellular phone, smart phone, personal digital assistant (PDA) tablet device, laptop computer or other device owned by customer102, an authentication device103, an account management system104operated by a card issuing entity105, and a point of sale device106operated by a merchant107. Although card issuing entity105may typically be described herein as a financial institution, such as a bank, other types of card issuing entities are contemplated as well. Similarly, while merchant107may typically be described herein in the context of a physical location of a department store, all types of merchants are contemplated as well. Furthermore, as contemplated herein, the card issuing entity and the merchant are not affiliated, such that the term “rewards points” as used herein refers to rewards points issued and maintained by the card issuing entity and not by the merchant.

Process100typically begins with customer102entering a store location of merchant107and selecting one or more goods or services for purchase. For example, customer102may enter a department store operated by merchant107and select one or more items of merchandise for purchase. Customer102may proceed to a checkout station having a point of sale device106operated by merchant107. Merchant107may utilize point of sale device106to determine a final payment amount108for the one or more items of merchandise. Customer102may wish to use a credit card issued by card issuing entity105in the form of authentication device103in order to fund the payment amount from a credit account109as opposed to performing a cash transaction. Customer102may further wish to utilize rewards points in a rewards account110maintained by card issuing entity105to fund at least a portion of payment amount108.

In order to initiate payment of the payment amount, in some embodiments customer102may provide authentication data112to a mobile device101so that account management system104will be able to verify that it is in fact customer102initiating the transaction. Authentication data112may include, for example, account data112asuch as customer102's name, credit account or credit card number, card expiration date, and rewards account number. Authentication data110may further contain, for example, username and password credentials112bfor online access to credit account109and/or rewards account110.

In some embodiments, customer102may provide authentication data112to mobile device101via authentication device103. For example, authentication device103may be a contactless EUROPAY, MASTERCARD and VISA (EMV) smart card issued by entity105and mobile device101may be an NFC equipped device capable of receiving data from authentication device103. Authentication device103may store account data112aand/or credentials112b, and may also cryptographically generate a code112cwhich may be verified by card issuing entity105for purposes of authenticating customer102. By presenting EMV authentication device103within range of NFC enabled mobile device101(e.g., tapping authentication device103against mobile device101), authentication data112may be transferred to mobile device101. In some embodiments, authentication device103may not be used to provide authentication data112. In such embodiments, mobile device101may store account data112aand/or credentials112bin a memory location, and biometric data114, such as a fingerprint, may be provided to mobile device101for purposes of authentication.

In some embodiments, customer102may execute a mobile application116on mobile device101in order to facilitate receiving authentication data112. For example, in EMV and/or NFC device embodiments, customer102may tap authentication device103to mobile device101in order to execute mobile application116. Upon detecting authentication device103, mobile device101may automatically launch mobile application116, which in turn facilitates automatic retrieval of authentication data112from the authentication device103.

In some embodiments, mobile application116may be executed upon customer102tapping a graphical element corresponding to mobile application116and displayed on mobile device101. For example, customer102may tap an icon displayed on a screen of mobile device101to launch mobile application116, which in turn may prompt customer102to tap authentication device103to mobile device101to begin automatic retrieval of authentication data112from the authentication device103.

In some embodiments, mobile application116may be executed upon receiving a signal from another NFC device, such as point of sale device106. For example, where mobile device101as well as point of sale device106are radio frequency (e.g., RFID) or NFC-enabled, customer102may bring mobile device101within a radio frequency range of point of sale device106in order to execute mobile application116. In one such an arrangement, upon detecting the radio frequency field of point of sale device106, mobile device101automatically launches the mobile application116. Mobile application116may then be used to retrieve authentication data112from the authentication device.

In some embodiments, mobile application116may be configured to, upon being executed, display a graphical user interface118on mobile device101to facilitate receiving authentication data112. For example, referring now toFIG.2, a user interface200that may be used to facilitate receiving authentication data according to an exemplary embodiment is shown. User interface200may be formatted as, for example, a PDF or HTML document capable of being displayed on a mobile device and further configured for data entry using a suitable user interface device. User interface200may include one or more authentication data entry fields202configured to receive data either automatically via pre-population or via a user interface device, such as a keypad (e.g., a physical or virtual keypad) or touch screen display. For example, in the illustrated embodiment, a data entry field202acorresponds to a name for the customer. A data entry field202bcorresponds to credit account or credit card number for the customer. A data entry field202ccorresponds to a card expiration date. A data entry field202dcorresponds to a rewards account number. Data entry fields202may further include, for example, fields202e,202f,202g, and202hfor username and password credentials for online access to corresponding credit accounts and rewards accounts.

Referring again toFIG.1, in some embodiments, graphical user interface118may be automatically populated in full or in part. For example, in embodiments where customer102may tap authentication device103to mobile device101in order to execute mobile application116, authentication data112stored on authentication device103may be used to populate graphical user interface118. Similarly, in embodiments where customer102may tap an icon displayed on a screen of mobile device101to launch mobile application116, customer102may be prompted to tap authentication device103to mobile device101in order to automatically populate graphical user interface118. In other embodiments, graphical user interface118may be manually populated in full or in part.

In some embodiments, graphical user interface118may be further configured to receive biometric data114from customer102, such as in embodiments where an EMV or other authentication device103is not used to provide authentication data112, or where a second level of authentication is desired. For example, referring again toFIG.2, in the illustrated embodiment, a data entry field204corresponds to a fingerprint pad where the customer's fingerprint may be placed in order to be captured.

Referring again toFIG.1, mobile device101may further receive payment amount108. Payment amount108may be, for example, electronically transmitted to mobile device101from point of sale device106(e.g., in embodiments where point of sale device106is an NFC device). In some embodiments, mobile application116is used to facilitate receiving the payment amount. For example, a signal received from point of sale device106conveying payment amount108may cause mobile device101to execute mobile application116, or customer102may have already executed mobile application116on mobile device101in order to facilitate receiving authentication data110.

In some embodiments, customer102may input payment amount108via a graphical user interface of mobile application116. For example, point of sale device106may display payment amount108, or merchant107may verbally convey payment amount108, and customer102may manually enter this amount in a field provided in the graphical user interface. For example, referring again toFIG.2, in the illustrated embodiment, a data entry field206corresponds to a payment amount for a point of sale transaction. In other embodiments, the payment amount may be automatically populated in field206.

Referring again toFIG.1, mobile device101may send authentication data112and payment amount108to an account management system104associated with card issuing entity105. For example, in some embodiments, authentication data112and payment amount108are automatically received by mobile device101and electronically transmitted to account management system104(e.g., upon customer102tapping an EMV authentication device103to an NFC mobile device101, or upon receiving a signal from an NFC point of sale device106). In some embodiments, graphical user interface118provided by mobile application116is used to facilitate receiving and sending authentication data112and payment amount108. For example, referring again toFIG.2, in the illustrated embodiment, a graphical element in the format of a button208that may be tapped by the customer is configured to allow the customer to send data entered via user interface200to an account management system operated by a card issuing entity.

Referring again toFIG.1, upon receiving authentication data112and payment amount108, account management system104may authenticate customer102(e.g., using authentication data112and perhaps biometric data114). Upon authenticating customer102, account management system104may also access credit account109and/or rewards account110. Account management system104may determine the amount of available credit in credit account109and the number of rewards points currently available for customer102to redeem in rewards account110. Based on the amount of available credit in credit account109and the number of rewards points currently available for customer102to redeem in rewards account110, account management system104may further determine a number of payment options120selectable by the customer. Selectable payment options120may include an option to redeem a portion of the rewards points currently available for customer102to fund a portion of payment amount108. The portion of rewards points may be any amount, from zero up to the maximum available amount of rewards points in rewards account110. Similarly, the portion of payment amount108may be any amount, from zero up to the entire amount of payment amount108.

For example, payment amount108received by account management system104may be equal to $100.00. Account management system104may determine that customer102has sufficient available credit in credit account109to fund the entire amount of payment amount108. Account management system104may further determine that customer102also has a sufficient amount of redeemable rewards points in rewards account110to fund the entire amount of payment amount108. In this case, selectable payment options120may include an option120afor customer102to fund the entire amount of payment amount108by redeeming $100.00 worth of rewards points. Selectable payment options120may also include an option120bfor customer102to fund the entire amount of payment amount108without redeeming any rewards points. Selectable payment options120may also include an option120cfor customer102to specify a particular amount of payment amount108, from zero up to the entire amount of payment amount108, for which a portion of the rewards points currently available for customer102should be redeemed.

In another example, payment amount108received by account management system104may again be equal to $100.00. Account management system104may determine that customer102has sufficient available credit in credit account109to fund the entire amount of payment amount108. Account management system104may further determine that customer102does not have a sufficient amount of redeemable rewards points in rewards account110to fund the entire $100.00 amount of payment amount108, but does, however, have a sufficient amount of redeemable rewards points to fund up to a $50.00 portion of payment amount108. In this case, selectable payment options120would not include option120afor customer102to fund the entire amount of payment amount108by redeeming $100.00 worth of rewards points. Selectable payment options120may, however, include option120bfor customer102to fund the entire amount of payment amount108without redeeming any rewards points. Selectable payment options120may also include an option120cfor customer102to specify a particular amount of payment amount108, this time from zero up to the amount of payment amount108for which sufficient redeemable rewards points are currently available for customer102, which in this example is $50.00.

Similarly, in yet another example, payment amount108received by account management system104may again be equal to $100.00. Account management system104may determine that customer102has sufficient available credit in credit account109to fund the entire amount of payment amount108. Account management system104may further determine that customer102does not have a sufficient amount of redeemable rewards points to fund any portion of payment amount108. In this case, selectable payment options120may only include option120bfor customer102to fund the entire amount of payment amount108from credit account109and without redeeming any rewards points from rewards account110. Selectable payment options120may also include an indication that customer102does not have a sufficient amount of redeemable rewards points to fund any portion of payment amount108.

Selectable payment options120may be sent from account management system104to mobile device101. Upon receiving selectable payment options120from account management system104, mobile device101may present them to customer102. In some embodiments, where customer102has executed mobile application116on mobile device101(e.g., in order to facilitate receiving and sending authentication data112and payment amount108), mobile device101may display selectable payment options120via a graphical user interface122generated by mobile application116. Customer102may then select one of payment options120as a selected payment option124. For example, in some embodiments where customer102has executed mobile application116on mobile device101to display selectable payment options120, graphical user interface122may be further configured to receive customer102's selection of selected payment option124(e.g., via customer tapping or otherwise selecting a graphical element corresponding to selected payment option124).

Referring now toFIG.3, a user interface300that may be used to facilitate receiving and sending selectable payment options according to an exemplary embodiment is shown. User interface300may be formatted as, for example, a PDF or HTML document capable of being displayed on a mobile device and further configured for data entry using a suitable user interface device. User interface300may include one or more graphical elements configured to receive input either automatically or via a user interface device, such as a keypad (e.g., a physical or virtual keypad) or touch screen display.

As shown inFIG.3, user interface300may include one or more selectable objects (e.g., radio buttons or check boxes) corresponding to a number of selectable payment options that may be selected by a customer. For example, in the illustrated embodiment, user interface300includes selectable objects302,304, and306that may be selected by the customer. Selectable object302corresponds to a selectable payment option for funding an entire $100.00 payment amount by redeeming $100.00 worth of rewards points. Selectable object304corresponds to a selectable payment option for funding the entire $100.00 payment amount from a charge account without redeeming any rewards points. Selectable object306corresponds to an option to specify a particular portion of the $100 payment amount, from zero up to the entire payment amount, for which a portion of the rewards points currently available should be redeemed, with the remainder of the payment account funded from a charge account. The customer may select one of the selectable payment options by, for example, tapping the corresponding selectable object (e.g., via a touch screen display).

As will be appreciated, selectable objects for other payment options are contemplated as well. For example, selectable object306could correspond to an option to specify a particular portion of the $100 payment amount, from zero up to a maximum amount of the payment amount for which an equivalent value of rewards points are currently available (e.g., in situations where the customer does not have a sufficient number of redeemable rewards points available to fund the entire payment amount). Similarly, in some embodiments user interface300may provide an indication that the customer does not have a sufficient amount of redeemable rewards points to fund any portion of the payment amount.

Referring again toFIG.1, mobile device101may send customer102's selected payment option124to account management system104. In some embodiments, graphical user interface122provided by mobile application116is used to facilitate sending customer102's selected payment option124to account management system104. For example, referring again toFIG.3, in the illustrated embodiment, a graphical element in the format of a button308that may be tapped by the customer is configured to allow the customer to send a selected payment option to an account management system operated by a card issuing entity.

Referring again toFIG.1, upon receiving customer102's selected payment option124, account management system104may deduct or place a hold on any corresponding amounts from credit account109and rewards account110. For example, if account management system104receives a selected payment option124indicating that a $50.00 portion of a payment amount of $100.00 should be funded by redeeming $50.00 worth of rewards points, then account management system104may proceed to hold or deduct $50.00 from the current available credit limit of credit account109. Account management system104may further proceed to deduct the equivalent of $50.00 worth of rewards points from rewards account110.

Account management system104may then send an authorized form of payment126to mobile device101. Authorized form of payment126may be a single form of payment configured for presentation to point of sale device106, regardless of whether customer102is funding all, a portion, or none of payment amount108by redeeming rewards points. In some embodiments, authorized form of payment126is displayable by mobile device101. For example, referring now toFIG.4, a single displayable authorized payment form400according to an exemplary embodiment is shown. Payment form400includes a quick response (QR) code402that may be scanned by a merchant's point of sale device to acquire the details of the authorized payment. In other arrangements, a bar code may be used instead of the QR code402.

Referring again toFIG.1, in some embodiments, authorized form of payment126may be configured for electronic transmission from mobile device101to point of sale device106. For example, in embodiments where both mobile device101and point of sale device106are NFC enabled devices, authorized form of payment126may be appropriately formatted according to industry standards for transmission from mobile device101to point of sale device106. In some embodiments, upon receiving selected payment option124, account management system104may deduct or place a hold on any corresponding amounts from credit account109and rewards account110, and customer102may present a credit card (e.g., authentication device103) to merchant107for processing at point of sale device106, rather than sending authorized form of payment126to mobile device101. Account management system may then later reconcile the credit card transaction in accordance with selected payment option124.

Referring now toFIG.5, a flowchart of a process500for payment using rewards points according to an exemplary embodiment is shown. At a step505, authentication data from a customer seeking to purchase goods or services in a merchant point of sale transaction by redeeming rewards points may be received at a mobile device. The mobile device may be, for example, an NFC enabled cellular phone, smart phone, personal digital assistant (PDA), tablet device, laptop computer or other device. The authentication data may include, for example, account information such as the customer's name, credit account or credit card number, card expiration data, and rewards account number. According to an exemplary embodiment, the customer's authentication data may be received at the mobile device via a contactless smart-card that cryptographically generates a code which can be verified by the card issuer's systems for purposes of authenticating the customer. According to another exemplary embodiment, biometric data may be provided to the mobile device for purposes of authenticating the customer. In some embodiments, the customer may execute a mobile application on the mobile device in order to facilitate receiving the authentication data.

At a step510, the mobile device may further receive a payment amount for the merchant point of sale transaction. In some embodiments, the customer may input the payment amount via a mobile application. In some embodiments, the payment amount may be electronically transmitted to the mobile device from the merchant's point of sale device.

At a step515, the mobile device may send the customer's authentication data and the payment amount to an account management system associated with the card issuing entity so that, upon receiving the customer's authentication data and the payment amount, the account management system may authenticate the customer and access the customer's credit account and rewards account. At a step520, the account management system may determine the amount of rewards points currently available for the customer to redeem.

At a step525, the account management system may determine a number of payment options selectable by the customer. The selectable payment options may include an option to redeem a portion of the rewards points currently available for the customer to fund a portion of the payment amount. For example, the selectable payment options may include an option to redeem a portion of the rewards points to fund the entire payment amount, an option to redeem a portion of the rewards points to fund less than the entire payment amount, and an option not to redeem any of the portion of rewards points.

At a step530, the selectable payment options may be sent from the account management system to the mobile device. At a step535, the mobile device may present the selectable payment options to the customer. In some embodiments, the mobile device may display the selectable payment options via a graphical user interface of a mobile application. At a step540, the mobile device may receive a selected payment option selected by the customer from the displayed payment options. In some embodiments, a mobile application may be configured to receive the customer's selected payment option via a graphical user interface.

At a step545, the customer's selected payment option may be sent to the account management system. At a step550, the account management system may send an authorized form of payment to the mobile device. The form of payment may be, for example, a single form of payment configured for presentation to the merchant's point of sale device, regardless of whether the customer is funding all, a portion, or none of the payment amount by redeeming rewards points. At a step555, the mobile device may send the form of payment to the point of sale device. In some embodiments, the authorized form of payment may be displayable by the mobile device, such as a barcode that may be scanned by the merchant's point of sale device. In some embodiments, the form of payment may be configured for electronic transmission from the mobile device to the merchant's point of sale device.

Referring now toFIG.6, a block diagram illustrating a system600for payment using rewards points according to an exemplary embodiment is shown. System600may include, for example, a server602. Server602may be implemented by, for example, general purpose or special purpose computers or other machines with a processor and memory configured to store applications including program code in the form of machine-executable instructions or data structures. In particular, server602may include one or more applications configured to implement the various embodiments of account management systems shown and described above with reference toFIGS.1-5.

In some embodiments, server602may be implemented as a single unit for facilitating payment using rewards points. In other embodiments, system600may distribute functionality across multiple servers. For example, system600may additionally utilize a credit account server604and a rewards account server606for managing credit accounts and rewards accounts as shown and described above with reference toFIGS.1-5.

Server602may include a processor612. Processor612may be implemented in hardware, firmware, software, or any combination of these methods. Server602may have one or more processors612that use the same or a different processing technology. Additionally, processor612may be a separate component or may be embedded within another component of server602. Processor612may execute applications including program code in the form of machine-executable instructions that may be written using one or more programming languages, scripting languages, assembly languages, etc. The instructions may be carried out by, for example, a special purpose computer, logic circuits, or hardware circuits. Processor612may execute, for example, one or more applications configured to implement the various embodiments shown and described above with reference toFIGS.1-5.

Server602may further include a system memory614. System memory614may include, for example, a non-transitory machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media may be any available media that may be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media may comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to carry or store desired applications including program code in the form of machine-executable instructions or data structures and which may be accessed by a general purpose or special purpose computer or other machine. Server602may have one or more system memories614that use the same or a different memory technology.

System memory614may store one or more applications configured to implement the various embodiments shown and described above with reference toFIGS.1-5. For example, system memory614may store an application configured to generate a graphical user interface when executed by processor612, such as one or more dynamically generated web pages presented to customers via browser or mobile applications operating on mobile devices. The graphical user interface may prompt the customers to take certain actions and may receive user inputs provided in response to such prompting.

Server602may be accessed via, for example, a communication network618. Communication network618may allow other devices to link to server602by, for example, a wired, wireless or combination local area network, wide area network (Internet), etc. Communication network618may include any necessary hardware and/or software to facilitate secure transmission of data.

Server602may also be accessed by a customer using a mobile device620. Mobile device620may be, for example, a cellular phone, smart phone, personal digital assistant (PDA), tablet device, laptop computer, or other device. Mobile device620may include a display622, a user interface624, a processor626, a system memory628, and a system bus that couples various system components including system memory628to processor626. In particular, mobile device620may be configured to implement the various embodiments of mobile devices shown and described above with reference toFIGS.1-5.

Display622may be, for example, an LED or LCD display which may also include a touch screen. User interface624may include, for example, a keyboard, a keypad, a mouse, joystick or other input device performing a similar function. Processor626may be implemented in hardware, firmware, software, or any combination of these methods. Mobile device620may have one or more processors626that use the same or a different processing technology. Additionally, processor626may be a separate component of mobile device620, or may be embedded within another component of mobile device620. Processor626may execute applications including program code in the form of machine-executable instructions that may be written using one or more programming languages, scripting languages, assembly languages, etc. The instructions may be carried out by, for example, a special purpose computer, logic circuits, or hardware circuits. Processor626may execute, for example, email, browser or mobile applications stored in memory628. The email, browser or mobile applications stored in memory628may be any type of software that is capable of communicating with server602via a network connection. System memory628may be, for example, RAM, ROM, EPROM, EEPROM, CD-ROM or any other medium which may be used to carry or store desired applications including program code in the form of machine-executable instructions or data structures. System memory628may also store other data such as, for example, authentication data as shown or described with reference toFIGS.1-5.

Mobile device620may communicate with server602via communication network618through, for example, a wired, wireless or combination local area network, wide area network (Internet), etc. Programs may run on respective computers to create a client-server relationship. For example, in some embodiments, mobile device620may execute a web browser or mobile application to interact with server602, and data may be provided to a user interface of the web browser or mobile application executing on mobile device620. For example, server602may provide content to the web browser or mobile application of mobile device620in response to a request received from the mobile device.

Mobile device620may also communicate with an authentication device630and a point of sale device640through, for example, a wireless communication link using secure NFC standards and protocols such as ECMA-340 and ISO/IEC 14443 and 18092. In some embodiments, mobile device620may execute a browser or mobile application to interact with authentication device630and/or point of sale device640, and data may be provided to a user interface of the browser or mobile application executing on mobile device620. In some embodiments, mobile device620may receive biometric information using a known mobile biometric application.

Authentication device630may be, for example, a contactless EMV smart card capable of being configured to implement the various embodiments of authenication devices shown and described above with reference toFIGS.1-5. Point of sale device640may be, for example, a magnetic stripe card reader, an RFID device, barcode reader, cash register, computing device, smart card reader, scanning device or other device employed for processing merchant transactions. In particular, mobile device640may be configured to implement the various embodiments of point of sale devices shown and described above with reference toFIGS.1-5. In some embodiments, point of sale device640may be configured for communication using secure NFC standards and protocols. In some embodiments, point of sale device640may be further configured to communicate with server602either directly via communication network618, or via a credit transaction facilitator such as VISA, MASTER CARD, DISCOVER, OR AMERICAN EXPRESS in order to, for example, reconcile credit transactions as shown and described above with reference toFIGS.1-5.

The scope of this disclosure should be determined by the claims, their legal equivalents and the fact that it fully encompasses other embodiments which may become apparent to those skilled in the art. All structural, electrical and functional equivalents to the elements of the below-described disclosure that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. A reference to an element in the singular is not intended to mean one and only one, unless explicitly so stated, but rather it should be construed to mean at least one. No claim element herein is to be construed under the provisions of 35 U.S.C. § 112, sixth paragraph, unless the element is expressly recited using the phrase “means for.” Furthermore, no element, component or method step in the present disclosure is intended to be dedicated to the public, regardless of whether the element, component or method step is explicitly recited in the claims.

The embodiments in the present disclosure have been described with reference to drawings. The drawings illustrate certain details of specific embodiments that implement the systems, methods and programs of the present disclosure. However, describing the embodiments with drawings should not be construed as imposing any limitations that may be present in the drawings. The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing its operations. The embodiments of the present disclosure may be implemented using an existing computer processor, or by a special purpose computer processor incorporated for this or another purpose or by a hardwired system.

As noted above, embodiments within the scope of the present invention include program products comprising non-transitory machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media may be any available media that may be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media may comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to carry or store desired program code in the form of machine-executable instructions or data structures and which may be accessed by a general purpose or special purpose computer or other machine with a processor. Thus, any such a connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Embodiments in the present disclosure have been described in the general context of method steps which may be implemented in one embodiment by a program product including machine-executable instructions, such as program code, for example, in the form of program modules executed by machines in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Machine-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.

As previously indicated, embodiments in the present disclosure may be practiced in a networked environment using logical connections to one or more remote computers having processors. Those skilled in the art will appreciate that such network computing environments may encompass many types of computers, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and so on. Embodiments in the disclosure may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

An exemplary system for implementing the overall system or portions of the disclosure might include one or more computers including a processor, a system memory or database, and a system bus that couples various system components including the system memory to the processor. The database or system memory may include read only memory (ROM) and random access memory (RAM). The database may also include a magnetic hard disk drive for reading from and writing to a magnetic hard disk, a magnetic disk drive for reading from or writing to a removable magnetic disk, and an optical disk drive for reading from or writing to a removable optical disk such as a CD ROM or other optical media. The drives and their associated machine-readable media provide nonvolatile storage of machine-executable instructions, data structures, program modules and other data for the computer. User interfaces, as described herein, may include a computer with a monitor, a keyboard, a keypad, a mouse, a joystick or other input devices performing a similar function.

It should be noted that although the diagrams herein may show a specific order and composition of method steps, it is understood that the order of these steps may differ from what is depicted. For example, two or more steps may be performed concurrently or with partial concurrence. Also, some method steps that are performed as discrete steps may be combined, steps being performed as a combined step may be separated into discrete steps, the sequence of certain processes may be reversed or otherwise varied, and the nature or number of discrete processes may be altered or varied. The order or sequence of any element or apparatus may be varied or substituted according to alternative embodiments. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. Such variations will depend on the software and hardware systems chosen and on designer choice. It is understood that all such variations are within the scope of the disclosure. Likewise, software and web implementations of the present invention could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps.

The foregoing description of embodiments has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the subject matter to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the subject matter disclosed herein. The embodiments were chosen and described in order to explain the principals of the disclosed subject matter and its practical application to enable one skilled in the art to utilize the disclosed subject matter in various embodiments and with various modifications as are suited to the particular use contemplated. Other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the embodiments without departing from the scope of the presently disclosed subject matter.

Throughout the specification, numerous advantages of the exemplary embodiments have been identified. It will be understood, of course, that it is possible to employ the teachings herein without necessarily achieving the same advantages. Additionally, although many features have been described in the context of a particular data processor, it will be appreciated that such features could also be implemented in the context of other hardware configurations.

While the exemplary embodiments illustrated in the figures and described above are presently preferred, it should be understood that these embodiments are offered by way of example only. Other embodiments may include, for example, structures with different data mapping or different data. The disclosed subject matter is not limited to a particular embodiment, but extends to various modifications, combinations, and permutations that nevertheless fall within the scope and spirit of the appended claims.