NFC-based options selection

Information

  • Patent Grant
  • 10580011
  • Patent Number
    10,580,011
  • Date Filed
    Tuesday, December 15, 2015
    8 years ago
  • Date Issued
    Tuesday, March 3, 2020
    4 years ago
Abstract
A mobile electronic device corresponding to the present invention communicates with a point-of-sale terminal using near field data communications when making a purchase, prompting an offer regarding a warranty on an item purchased before the purchase is complete.
Description
BACKGROUND
Field of the Invention

The present invention generally relates to a user mobile device equipped with a near field data communication (NFC) interface that performs a purchase of an item linked to a warranty. More specifically, a mobile electronic device communicates with a point-of-sale terminal using near field data communications when making a purchase, prompting an offer regarding a warranty on an item purchased before the purchase is complete.


Description of the Related Art

Near field data communications (NFC) are currently being used by consumers to make secure financial transactions when purchasing goods or services. NFC is a standardized wireless data communication technology that communicates information over short distances. NFC commonly communicates using a frequency of 13.56 megahertz (MHz) with data rates approaching 424 kilo-bits per second (Kb/sec). NFC equipped devices of various sorts are available in the marketplace today.


Users of NFC-enabled user devices currently cannot purchase a warranty when making a purchase using NFC. A system and method where a user of a user device may purchase a warranty when they make a purchase using a NFC data communication interface on a user device is needed because consumers would benefit by having their purchase covered under a warranty as soon as they make their purchase.


SUMMARY OF THE PRESENTLY CLAIMED INVENTION

Embodiments of the present invention include a system and a method for receiving offers to acquire a warranty on an item at the point-of-sale with a mobile electronic device equipped with a near field communication (NFC) data communication interface. When purchasing an item at an NFC-equipped point-of-sale terminal, a mobile device may receive a communication over a NFC data communication interface indicating that a warranty may be acquired for that item. After receiving the communication, the warranty offer may be displayed in a graphical user interface (GUI) on a display at the mobile electronic device. A user of the mobile device may then accept the warranty offered by touching a selection box displayed in the GUI. After the user accepts the warranty offer, the mobile device may transmit payment information and information relating to the selected warranty over the NFC data communication interface to the point-of-sale terminal, and the transaction may then be processed.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1A is a flowchart illustrating a prior art method for basic authorization process based on near field communication (NFC).



FIG. 1B is a flowchart illustrating a prior art method for basic payment process based on NFC.



FIG. 2 illustrates a network environment in which an exemplary system for providing NFC-based payment with warranty options may be implemented.



FIG. 3 includes an exemplary GUI setup that may be used in a system for providing NFC-based payment with warranty options, as well as a flowchart illustrating an exemplary base software method for providing NFC-based payment with warranty options.



FIG. 4 is a flowchart illustrating an exemplary merchant base software method for providing NFC-based payment with warranty options.



FIG. 5A and FIG. 5B are flowcharts illustrating exemplary warranty network base software methods for providing NFC-based payment with warranty options.



FIG. 6 illustrates a matrix of information that may be stored in an exemplary warranty database used in a system for providing NFC-based payment with warranty options.



FIG. 7 is a flowchart illustrating an exemplary method for providing NFC-based payment with warranty options.





DETAILED DESCRIPTION

Embodiments of the present invention include a system and a method for linking items purchased using mobile electronic devices equipped with near field data communication (NFC) functionality to an offer to warrant the item purchased for a period of time.


Mobile electronic devices described herein include, yet are not limited to, smartphones, IPhones, Android phones, IPads, notebook computers, computers built into a car, and mobile devices dedicated to performing NFC communications. Payment authorization networks, and warranty networks described herein include, yet are not limited to, a computer and a computer server.


The various methods may be performed by software operating in conjunction with hardware. For example, instructions executed by a processor, the instructions otherwise stored in a non-transitory computer readable medium such as memory. Various interfaces may be implemented—both communications and interface. One skilled in the art will appreciate the various requisite components of a mobile device and integration of the same with one or more of the figures and/or descriptions included herein.



FIG. 1A is a flowchart illustrating a prior art method for basic authorization process based on near field communication (NFC). The basic authorization process begins when a customer with an NFC-capable phone sends a purchase order 1a to a merchant with a contactless terminal. The merchant with the contactless terminal then sends a request 2a to the merchant bank. Next, the merchant bank forwards credit card information 3a provided with the purchase order to a credit card payment processing center. The credit card payment processing center then forwards the credit card information 4a to the customer bank, and the customer bank approves or declines the purchase 5a. Next, a message is sent back to the merchant 6a indicating that the purchase has been approved or declined.



FIG. 1A also indicates that funds are approved or declined using a combination of the merchant bank, the credit card payment processing center, and the customer bank. Alternate communication pathways for performing the transactions are possible. The alternate communication pathways include a trusted service manager (TSM) communicating with the customer bank and with the credit card payment processing center, as well as a carrier with over the air (OTA) support communicating with the TSM and with the customer phone. The TSM is an entity that serves a trusted intermediary between mobile devices, networks that service mobile devices, and software applications. The TSM securely coordinates payments from a financial institution to a merchant that have been authorized by a mobile device. Examples of a carrier with OTA support are cellular companies like Verizon, AT&T, and T-Mobile. The basic authorization process may be performed using older phone lines, or it may be performed using modern wireless cellular networks.



FIG. 1B is a flowchart illustrating a prior art method for basic payment process based on NFC. The basic payment process of FIG. 1B involves the merchant sending a settlement request 1b to the merchant bank and the merchant bank then sending a settlement request 2b to the customer bank. Then the credit card payment processing company forwards the request 3b. Next, the customer bank transfers funds to the merchant bank 4b. Communications between the merchant bank, the credit card payment processing center, and the customer bank are used to transfer from the customer bank to the merchant bank. The customer phone may also communicate with a carrier with OTA support, as well as with a TSM. Here, the TSM also communicates with the credit card payment system and with the customer bank.



FIG. 2 illustrates a network environment in which an exemplary system providing NFC-based payment with warranty options may be implemented. In such a system, a warranty may be acquired when a mobile device makes a purchase using a near field communication (NFC) interface. The network environment may include a mobile device communicating with a warranty network over the cloud or internet. The mobile device may also communicate with a point-of-sale terminal at a merchant that, in turn, communicates over the cloud or internet. The mobile device may include a memory, a battery, operating system software (OS), a warranty application (App) program, and an NFC data communication interface. The warranty application may include base software and a graphical user interface (GUI).


The warranty network may include a warranty network base software that includes a warranty database and an application program interface (API). The warranty network may communicate with manufacturers and with third parties when a warranty is purchased. The point-of-sale terminal at a merchant may include an NFC data communication interface and a display. Base software may also be running on the point-of-sale terminal or an associated computer at the merchant. A transaction code communicated between the mobile device and the point of sale terminal may include payment and warranty information.


In one embodiment of the invention, a mobile device may use NFC when making a purchase, after which the point-of-sale terminal may communicate one or more warranty options to the mobile device over the NFC data communication interface. A user of the mobile device may open the warranty application GUI, review warranty options, and select a warranty prior to completing the purchase. When a warranty is selected, a warranty code may be appended to the payment information, and the payment may then be processed. Additional details and other information regarding the warranty may then be received by the mobile device either over the NFC data communication interface at the mobile device or over another data communication interface at the mobile device. The mobile device may include a wireless data communication interface, including, yet not limited to, a Bluetooth, Wi-Fi, or a cellular 3G/4G/LTE data communication interface.



FIG. 3 includes an exemplary GUI setup that may be used in a system for providing NFC-based payment with warranty options, as well as a flowchart illustrating an exemplary base software method for providing NFC-based payment with warranty options. The GUI setup may include several warranty options (e.g., manufacturer, third party, no warranty), a profile selection option, and an option to create and save extended code selection. When the profile selection box is selected, a user may enter or update user profile information such as an address, an email address, or a telephone number. Selecting the option to create and save extended code may result in display of a list of warranties that are available for purchase. The list of warranties may cover one or more items purchased by the user.


The base software method flowchart in FIG. 3 may begin when a use of a mobile device accesses a warranty application GUI (e.g., by selecting an associated icon in a display at their mobile device). Additionally, the user may select one or more warranty options, select preferences, create a warranty code attachment for a purchase or future purchases, and send a warranty code to a merchant. The warranty code may include or be appended to a payment code. After the warranty code has been sent to the merchant, the warranty information may be received from a warranty network, and a user of the mobile device may select a warranty to purchase.


In addition, the warranty information may be reviewed by the user via a display on the point-of-sale terminal or on the display of the user mobile device. The user may decide to purchase the warranty, after which transaction information relating to the purchase may be updated to include a warranty token. Then, a new warranty extended code may be created for a next transaction. In the instance when a user decides not to purchase a warranty, the transaction is processed normally without including a warranty code.



FIG. 4 is a flowchart illustrating an exemplary merchant base software method for providing NFC-based payment with warranty options. A merchant system may receive data via an NFC data communication from a mobile device. The data may be related to an item being purchased by a user. It may then be determined whether there is a warranty code included with the data received. The merchant base software may determine whether the warranty code is a valid available warranty code. If so, warranty information may be received from a warranty network, and a list of warranty items may be displayed on a point-of-sale terminal or on the user mobile device. The user may then select a warranty from the display. After receiving a warranty selection, the merchant base software may send information relating to the warranty back to the warranty network. Next, a price for the warranty may be added to the price of the item purchased, and the transaction may then be completed using a general credit card payment approval process. The merchant may receive a commission from the warranty network. Where it may be determined that a warranty code is not valid, the transaction may be processed without a warranty.



FIG. 5A and FIG. 5B are flowcharts illustrating exemplary warranty network base software methods for providing NFC-based payment with warranty options. Such software may be running at a warranty network server.



FIG. 5A illustrates information being loaded into a database at the warranty network. An API in the warranty network base software may receive an input, and in a second step warranty data relating to the input is loaded into a database.



FIG. 5B includes receiving a code from the merchant base software (e.g. merchant base software described with respect to FIG. 4). The warranty network base software may determine whether the code corresponds to a set of warranty options. If so, the warranty database may be searched for warranties that may be offered to a customer. Warranty options relating to the code may be extracted and then sent to the merchant base software. It may then be determined whether a warranty has been selected. If so, information may be exchanged between the merchant base software and the warranty network data base. Then, a commission may be sent to the merchant (when applicable).



FIG. 6 illustrates a matrix of information that may be stored in a warranty database used in a system for providing NFC-based payment with warranty options. The matrix includes a series of data fields for such data as merchant & user identification (ID), transaction number, warranty offered by, warranty cost, warranty length, and whether the warranty is accepted/declined. The merchant & user ID identifies the merchant, and the transaction number identifies the transaction. Warranties may be offered by various parties, such as manufacturers and third party warranty sellers. For example, transaction number 523 may be identified as occurring at merchant 0001 where two different warranties may have been offered by a manufacturer and two different warranties offered by a third party. Each of the warranties offered may have different costs, as well as different lengths of duration. As illustrated, three of the offers made in transaction 523 were declined, and one of the offers was accepted by a customer.



FIG. 7 is a flowchart illustrating an exemplary method for providing NFC-based payment with warranty options. A mobile device may be provided with a warranty application, a warranty GUI, warranty base software, an NFC data communication interface, a memory, a battery, and an OS. A merchant may be provided with a point-of-sale terminal that includes a display, an NFC data communication interface, and with warranty base software to run on a computer at the merchant.


A warranty network may be provided with warranty network software, a warranty network database, a list of third party warranties, a group of manufacturer warranties, and a API. A user may select a warranty application on their mobile device, select a set of warranty options, enter profile information, and select and save an extended code for the current or future transactions.


The mobile device may transmit information over an NFC data communication interface to a point-of-sale terminal. A warranty application running on the mobile device may attach a warranty code to the information transmitted to the point-of-sale terminal. Merchant base software running on the point-of-sale terminal or an associated computer at the merchant may extract the warranty code from the information transmitted from the mobile device and send the warranty code to a warranty network. The information transmitted from the mobile device over the NFC data communication may identify a credit or debit card that the user of the mobile device wished to use when purchasing an item.


The warranty code may be sent to the warranty network, and the warranty network software may then search for manufacturer warranties and third party warranties that are available for the item purchased that corresponds to the warranty code. When the warranty network identifies one or more available warranties, information relating to those warranties may be transmitted to the manufacturer, and that information may be displayed on the point-of-sale terminal or on the mobile device.


A warranty may be selected by the user, and that selection may be sent to the warranty network. A payment may be received and processed using a general credit card purchase approval process, and the merchant may be sent a commission.


In certain instances after a point-of-sale terminal receives a NFC communication from a mobile device, the point-of-sale terminal may display one or more warranty offerings that may be selected on the point-of-sale terminal without sending an NFC communication listing the warranty offerings to the mobile device. After a warranty is purchased, therefore, a confirmation that the warranty has been purchased may be sent to the mobile device by the point-of-sale terminal over the NFC communication interface, or the mobile device may be sent a confirmation from the warranty network over another data communication interface at the mobile device.


While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. The descriptions are not intended to limit the scope of the invention to the particular forms set forth herein. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments. It should be understood that the above description is illustrative and not restrictive. To the contrary, the present descriptions are intended to cover such alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims and otherwise appreciated by one of ordinary skill in the art. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the appended claims along with their full scope of equivalents.

Claims
  • 1. A method for providing near field communication (NFC)-based options, the method comprising: initiating a purchase transaction of at least one item over an NFC interface at an NFC-enabled mobile device, wherein the purchase transaction is initiated at a point-of-sale (POS) terminal;sending one or more options associated with the at least one item from the POS terminal to the NFC-enabled mobile device, wherein the options each correspond to a different additional item associated with the at least one item in the initiated purchase transaction and displayed for selection at the NFC-enabled mobile device;receiving a code associated with at least one selection from the options displayed at the NFC-enabled mobile device, the code sent by the NFC-enabled mobile device to the POS terminal; andmodifying the initiated purchase transaction provided to an NFC-based authorization system, wherein the initiated purchase transaction is modified in accordance with the at least one selected option associated with the received code, and wherein the modified purchase transaction includes at least one additional item corresponding to the at least one selection associated with the received code.
  • 2. The method of claim 1, wherein the at least one selection specifies a plurality of selected options, and wherein the received code is an extended code associated with the plurality of selected options.
  • 3. The method of claim 2, wherein the extended code is further associated with profile information specific to the NFC-enabled mobile device.
  • 4. The method of claim 2, wherein the extended code is stored in memory of the NFC-enabled mobile device, wherein the extended code is retrieved for a subsequent transaction.
  • 5. The method of claim 2, wherein the NFC-enabled mobile device generates the extended code based on the plurality of selection options.
  • 6. The method of claim 1, wherein the code is sent over a communication network from the NFC-enabled mobile device to a network server.
  • 7. The method of claim 1, further comprising: extracting the code from an NFC communication sent by the NFC-enabled mobile device to the POS terminal;sending the extracted code from the POS terminal to a network server; andreceiving information regarding the at least one selected option sent by the network server to the POS terminal in response to the extracted code, wherein modifying the purchase transaction is based on the received information.
  • 8. The method of claim 1, further comprising identifying that the received code is valid before modifying the purchase transaction.
  • 9. The method of claim 1, further comprising stored information regarding a plurality of options in memory, wherein sending the one or more options comprises identifying the one or more options associated with the at least one item.
  • 10. A apparatus for providing near field communication (NFC)-based options, the apparatus comprising: an NFC interface that: initiates a purchase transaction of at least one item with an NFC-enabled mobile device at a point-of-sale (POS) terminal;sends one or more options associated with the at least one item from the POS terminal to the NFC-enabled mobile device, wherein the options each correspond to a different additional item associated with the at least one item in the initiated purchase transaction and displayed for selection at the NFC-enabled mobile device; andreceives a code associated with at least one selection from the options displayed at the NFC-enabled mobile device, the code sent by the NFC-enabled mobile device to the POS terminal; anda processor that executes instructions stored in memory, wherein execution of the instructions by the processor modifies the initiated purchase transaction provided to an NFC-based authorization system, wherein the initiated purchase transaction is modified in accordance with the at least one selected option associated with the received code, and wherein the modified purchase transaction includes at least one additional item corresponding to the at least one selection associated with the received code.
  • 11. The apparatus of claim 10, wherein the at least one selection specifies a plurality of selected options, and wherein the received code is an extended code associated with the plurality of selected options.
  • 12. The apparatus of claim 11, wherein the extended code is further associated with profile information specific to the NFC-enabled mobile device.
  • 13. The apparatus of claim 11, wherein the extended code is stored in memory of the NFC-enabled mobile device, wherein the extended code is retrieved for a subsequent transaction.
  • 14. The apparatus of claim 11, wherein the NFC-enabled mobile device generates the extended code based on the plurality of selected options.
  • 15. The apparatus of claim 10, wherein the code is sent over a communication network from the NFC-enabled mobile device to a network server.
  • 16. The apparatus of claim 10, wherein the processor executes further instructions to extract the code from an NFC communication sent by the NFC-enabled mobile device to the POS terminal, and further comprising a network communication interface that: sends the extracted code from the POS terminal to a network server; andreceives information regarding the at least one selected option sent by the network server to the POS terminal in response to the extracted code, wherein modifying the purchase transaction is based on the received information.
  • 17. The apparatus of claim 10, wherein the processor executes further instructions to identify that the received code is valid before modifying the purchase transaction.
  • 18. The apparatus of claim 10, further comprising memory that stores information regarding a plurality of options, wherein the processor executes further instructions to identify the one or more options associated with the at least one item.
  • 19. A non-transitory computer-readable storage medium, having embodied thereon a program executable by a processor to perform a method for providing near field communication (NFC)-based options, the method comprising: initiating a purchase transaction of at least one item over an NFC interface at an NFC-enabled mobile device, wherein the purchase transaction is initiated at a point-of-sale (POS) terminal;sending, over an NFC interface, one or more options associated with the at least one item from the POS terminal to the NFC-enabled mobile device, wherein the options each correspond to a different additional item associated with the at least one item in the initiated purchase transaction and displayed for selection at the NFC-enabled mobile device;receiving a code associated with at least one selection from the options displayed at the NFC-enabled mobile device, the code sent by the NFC-enabled mobile device to the POS terminal; andmodifying the initiated purchase transaction provided to an NFC-based authorization system, wherein the initiated purchase transaction is modified in accordance with the at least one selected option associated with the received code, and wherein the modified purchase transaction includes at least one additional item corresponding to the at least one selection associated with the received code.
CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the priority benefit of U.S. provisional application No. 62/093,298 filed Dec. 17, 2014 entitled “Payment Processes with Warranty Options,” the disclosure of which is hereby incorporated by reference.

US Referenced Citations (173)
Number Name Date Kind
5473143 Vak et al. Dec 1995 A
6973172 Bitove et al. Dec 2005 B1
7828204 Fiebiger et al. Nov 2010 B2
7832646 Leason Nov 2010 B1
7844512 Richards et al. Nov 2010 B2
8065190 Collas et al. Nov 2011 B2
8105772 Mardikar et al. Apr 2012 B2
8306860 Dunsmore et al. Nov 2012 B2
8474701 Meek et al. Jul 2013 B1
8494913 Cavagnaro Jul 2013 B2
8498900 Spirin et al. Jul 2013 B1
8577803 Chatterjee et al. Nov 2013 B2
8690054 Cummins et al. Apr 2014 B1
8714439 Brendell et al. May 2014 B2
8718554 Abel May 2014 B2
8762211 Killian et al. Jun 2014 B2
8783561 Wesley Jul 2014 B2
8788324 Shetty et al. Jul 2014 B1
8799085 Fisher Aug 2014 B2
8805726 Fisher Aug 2014 B2
8811895 Reisgies et al. Aug 2014 B2
8954004 Wang et al. Feb 2015 B1
9582826 Calman et al. Feb 2017 B2
9646303 Karpenko et al. May 2017 B2
9672511 Lim Jun 2017 B2
9734091 Kadi et al. Aug 2017 B2
9985699 Cronin May 2018 B1
10262311 Cronin Apr 2019 B1
10262318 Cronin Apr 2019 B1
10348368 Cronin Jul 2019 B2
10516964 Dotan et al. Dec 2019 B2
20020026348 Fowler et al. Feb 2002 A1
20020062249 Iannacci May 2002 A1
20040010597 Kirschner et al. Jan 2004 A1
20040220876 Liu Nov 2004 A1
20050004839 Bakker et al. Jan 2005 A1
20050210240 Barron Sep 2005 A1
20060131390 Kim Jun 2006 A1
20060206378 Ficalora Sep 2006 A1
20070022375 Walker Jan 2007 A1
20070032225 Konicek et al. Feb 2007 A1
20070190939 Abel Aug 2007 A1
20070192198 Schwarzkopf Aug 2007 A1
20070203850 Singh et al. Aug 2007 A1
20080011837 Wesley Jan 2008 A1
20080078831 Johnson et al. Apr 2008 A1
20080109335 Keohane et al. May 2008 A1
20080120155 Pliha May 2008 A1
20080133351 White et al. Jun 2008 A1
20080147496 Bal et al. Jun 2008 A1
20080150678 Giobbi et al. Jun 2008 A1
20080167017 Wentker et al. Jul 2008 A1
20080167961 Wentker et al. Jul 2008 A1
20090082001 Rahul et al. Mar 2009 A1
20090132362 Fisher et al. May 2009 A1
20090138365 Mueller et al. May 2009 A1
20090156190 Fisher Jun 2009 A1
20090192935 Griffin et al. Jul 2009 A1
20090276305 Clopp Nov 2009 A1
20100010887 Karlin et al. Jan 2010 A1
20100088149 Sullivan et al. Apr 2010 A1
20100114677 Carlson et al. May 2010 A1
20100124914 Schmidt et al. May 2010 A1
20100125510 Smith et al. May 2010 A1
20100190437 Buhot Jul 2010 A1
20100211507 Aabye et al. Aug 2010 A1
20100211679 Kumar et al. Aug 2010 A1
20100274691 Hammad et al. Oct 2010 A1
20100274853 Carlson et al. Oct 2010 A1
20100309807 Rautiainen Dec 2010 A1
20100312692 Teicher Dec 2010 A1
20110016050 Evans Jan 2011 A1
20110153438 Dragt Jun 2011 A1
20110167133 Jain Jul 2011 A1
20110202402 Fowler et al. Aug 2011 A1
20110218849 Rutigliano et al. Sep 2011 A1
20110230209 Kilian Sep 2011 A1
20110258249 Biggs et al. Oct 2011 A1
20110313922 Ben Ayed Dec 2011 A1
20110320345 Taveau et al. Dec 2011 A1
20120036076 Vanderwall et al. Feb 2012 A1
20120078701 Woods Mar 2012 A1
20120078735 Bauer et al. Mar 2012 A1
20120089461 Greenspan Apr 2012 A1
20120101882 Todd Apr 2012 A1
20120109730 Yoder et al. May 2012 A1
20120136732 McMillen et al. May 2012 A1
20120148077 Aldaz et al. Jun 2012 A1
20120160912 Laracey Jun 2012 A1
20120166332 Naaman Jun 2012 A1
20120185315 VanDerheide et al. Jul 2012 A1
20120209749 Hammad et al. Aug 2012 A1
20120221401 Brown et al. Aug 2012 A1
20120253913 Richard Oct 2012 A1
20120330744 Aissa Dec 2012 A1
20130006773 Lutnick et al. Jan 2013 A1
20130006782 Schwarzkopf et al. Jan 2013 A1
20130020389 Barnett Jan 2013 A1
20130059534 Sobalvarro et al. Mar 2013 A1
20130067546 Thavasi et al. Mar 2013 A1
20130080241 Fisher Mar 2013 A1
20130080972 Moshrefi et al. Mar 2013 A1
20130085835 Horowitz Apr 2013 A1
20130095755 Moreton et al. Apr 2013 A1
20130097040 Fisher Apr 2013 A1
20130110261 Lee et al. May 2013 A1
20130110682 Rosenblatt et al. May 2013 A1
20130132282 Shakkarwar May 2013 A1
20130144715 Kranzley et al. Jun 2013 A1
20130191213 Beck et al. Jul 2013 A1
20130191246 Calman et al. Jul 2013 A1
20130204728 Lichterman et al. Aug 2013 A1
20130211987 Louie et al. Aug 2013 A1
20130215467 Fein et al. Aug 2013 A1
20130218682 Alterman et al. Aug 2013 A1
20130268378 Yovin Oct 2013 A1
20140006205 Berry et al. Jan 2014 A1
20140006272 Calman Jan 2014 A1
20140058955 Calman Feb 2014 A1
20140074637 Hammad Mar 2014 A1
20140074691 Bank et al. Mar 2014 A1
20140081855 Hankins et al. Mar 2014 A1
20140089178 Lee et al. Mar 2014 A1
20140089672 Luna et al. Mar 2014 A1
20140100983 Cavagnaro Apr 2014 A1
20140129357 Goodwin May 2014 A1
20140138435 Khalid May 2014 A1
20140172660 Louie et al. Jun 2014 A1
20140173063 Jeong et al. Jun 2014 A1
20140180826 Boal Jun 2014 A1
20140189836 Eyler Jul 2014 A1
20140201085 Brendell et al. Jul 2014 A1
20140207680 Rephlo Jul 2014 A1
20140214673 Baca et al. Jul 2014 A1
20140222670 Concannon Aug 2014 A1
20140274014 Dodla Sep 2014 A1
20140277805 Browne et al. Sep 2014 A1
20140279474 Evans et al. Sep 2014 A1
20140298027 Roberts et al. Oct 2014 A1
20140351057 Kwon et al. Nov 2014 A1
20140351071 Hong et al. Nov 2014 A1
20140351147 Castrechini et al. Nov 2014 A1
20150019439 Phillips Jan 2015 A1
20150073907 Purves et al. Mar 2015 A1
20150088626 Salmon et al. Mar 2015 A1
20150088631 Mitchell Mar 2015 A1
20150095224 Blythe Apr 2015 A1
20150100443 Van Heerden et al. Apr 2015 A1
20150100803 Chen et al. Apr 2015 A1
20150120473 Jung Apr 2015 A1
20150127549 Khan May 2015 A1
20150154634 Chiu et al. Jun 2015 A1
20150156311 Adams et al. Jun 2015 A1
20150186871 Laracey Jul 2015 A1
20150220915 Rosenberg Aug 2015 A1
20150302398 Desai et al. Oct 2015 A1
20150339318 O'Toole et al. Nov 2015 A1
20150356551 Dogin et al. Dec 2015 A1
20160055512 Godsey et al. Feb 2016 A1
20160057619 Lopez Feb 2016 A1
20160117667 Kang et al. Apr 2016 A1
20160162882 McClung Jun 2016 A1
20160192123 Lim Jun 2016 A1
20160321641 Cady et al. Nov 2016 A1
20170024733 Purves Jan 2017 A1
20170287321 Ann et al. Oct 2017 A1
20170295032 Shin et al. Oct 2017 A1
20180041591 Yoden Feb 2018 A1
20180050450 Parrott et al. Feb 2018 A1
20180248589 Cronin Aug 2018 A1
20190172035 Cronin Jun 2019 A1
20190325426 Cronin Oct 2019 A1
20190326957 Cronin Oct 2019 A1
Foreign Referenced Citations (4)
Number Date Country
103679475 Mar 2014 CN
2 533 186 Dec 2012 EP
WO 2012051071 Apr 2012 WO
WO 2013096486 Jun 2013 WO
Non-Patent Literature Citations (93)
Entry
U.S. Appl. No. 14/970,304, John Cronin, NFC Transaction Choices, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,311, John Cronin, NFC Triggered Incentives at Point-of-Sale, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,314, John Cronin, NFC Ubiquitous Modular Payment Terminal, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,319, John Cronin, NFC ATM Vending Machine With Added Two Way Non-financial Data, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,328, John Cronin, Payments Data Source Tagging for Accounts Statements, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,056, John Cronin, NFC-Based Payment as a Service, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,069, John Cronin, NFC Improving Content Transfer in Low Bandwidth NFC Payments Systems, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,080, John Cronin, NFC Increased Biometrics Based on Transactions Parameters, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,091, John Cronin, Interaction With Purchaser in NFC-Based Transaction, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,102, John Cronin, NFC Center, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,340, John Cronin, Real Time Credit Offers, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,125, John Cronin, NFC Transaction With Financial and Non-financial Data, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,139, John Cronin, Bill Splitting and Account Delegation for NFC, filed Dec. 15, 2015.
U.S. Appl. No. 14/970,144, John Cronin, Automatic Shopping Based on Historical Data, filed Dec. 15, 2015.
Airplus—Mobile Payment—How It Will Transform Corporate Travel and Expense Management, Apr. 18, 2012.
Case Study—Bill Splitting App for Restaurantst, 2013.
AuthenTec—AuthenTec Fingerpring Technology Featured in Two New Fujitsu NFC-enabled Mobile Phones from NTT Docomo, Nov. 16, 2011.
Balaban, Dan; “Spanish Bank Installs ‘First’ Contactless ATMs”, NFC Times, Apr. 5, 2011.
Blaze Mobile Wallet, Jan. 2008.
Boden, Rian; “PrivatBank cuts ATM costs with NFC”, NFC World, Nov. 5, 2013.
Borison, Rebecca; “Google Wallet adds geolocated loyalty to iOS, combats Passbook”, Mobile Commerce Daily, Feb. 7, 2014.
Carson, Biz; “BitPay brings one-touch payments to bitcoin with new NFC-compatible checkout app.” Nov. 4, 2014.
Cluckey, Suzanne; “New guide offers a comprehensive view of ATM and mobile integration”, Mobile Payments Today, Nov. 28, 2014.
CommBank Small Business app User Guide, CommonwealthBank. Jul. 11, 2014.
Dai, Weihui; “An Integrated Mobile Phone Payment System Based on 3G Network”, Journal of Networks, vol. 6, No. 9, Sep. 2011.
Dragt, Bruce; “Universal Commerce: A Seamless, Personalized Purchase Experience for Today's Connected Consumers”, A First Data White Paper, 2012.
Fraser, Jeff; “The Mobile Shopper: Lose Your Wallet.” Jun. 1, 2014.
Girt Mobile—Mobile Application Development Ireland, Dec. 2, 2014.
Google Wallet Privacy Policy, Nov. 16, 2011.
Hoyos Labs, Nov. 28, 2014.
I-Free Unveils New and Improved “Wallet”: NFC Mobile App Now Stores Contactless Transport Cards and Discount Coupons, i-Free News, Nov. 7, 2013.
FAQ and Support—CashCloud.com, Dec. 3, 2014.
Itautec Mobicash, Feb. 13, 2013. Link: https://youtu.be/-qaL2QHliok (youtube video, no pdf).
Khan, Vaseem; “Contactless card reader by Diebold leverages NFC technology at ATM's to give cash”, NFC, Payments, Oct. 10, 2013.
Keane, Byran; “Key Takeaways From Money2020 Industry Conf”, Deutsche Bank Markets Research. Oct. 10, 2013.
Lawler, Ryan; “Square's Order App Can Now Predict When You'll Arrive to Pick Up Your Cappuccino”, TechCrunch, Oct. 8, 2014.
Ma et al., Xiaohua; “The Architecture of Mobile Wallet System Based on NFC (Near Field Communication)”, Research Journal of Applied Sciences, Engineering and Technology 7(12): 2589-2595, 2014, ISSN: 2040-7459; e-ISSN: 2040-7467, Mar. 29, 2014.
Mastin, Michelle; “Square vs.. Intuit GoPayment: Mobile Credit Card Systems Compared”, Bizfeed, PCWorld, Sep. 6, 2011.
Mobile_Commerce_NFC_Coupons_and_Loyalty_Acceptance—Technical Proposal, Version 1.0, Jul. 1, 2014.
More Magic: Mobile Banking & Payment Applications, Nov. 30, 2014.
NEC—Integrated E-Money Solution, Jan. 20, 2014.
“New breed of ATM Visits Times Square”, Mobileinfo.com, Issue #2001, Jul. 30, 2001.
NFC & Contactless—Mobile and card solutions, NFC & Mobile Money Summit, Oct. 14-17, 2013.
NFC ReTag Free—WidgApp Mobile Solutions Tools, Google Play, Jul. 17, 2014.
NFC White Paper—Alcatel-Lucent Mobile Wallet Service, Dec. 2011.
NXP—NFC for embedded applications: Your Critical link for the Internet of Things, Aug. 21, 2014.
Patni, Chandra; “Pouch NFC PayPass & PayWave Card Issuance, pouch-let your mobile pay!”, www.yes-wallet.com, Apr. 13, 2012.
“Pay2You Places: shopping by geolocation”, Connexions, Jul. 5, 2013.
Pourghomi et al., Pardis; “Cloud-based NFC Mobile Payments”, Journal of Internet Technology and Secured Transactions (JITST), vol. 2, Issues 1/2/3/4, Mar.-Dec. 2013.
Pourghomi et al., Pardis; “A Proposed NFC Payment Application”, International Journal of Advanced Computer Science and Applications, vol. 4, No. 8, 2013).
Reardon, Marguerite; Tibken, Shara; “Apple takes NFC maintstream on iPhone 6; Apple Watch with Apple Pay”, CNET, Sep. 9, 2014.
Rodrigues et al., Helena; “MobiPag: Integrated Mobile Payment, Ticketing and Couponing Solution Based on NFC”, Sensors 2014, 14, 13389-13415;ISSN 124-8220, Jul. 24, 2014.
Sreekumar, Shiny; “Biometric Authentication in Mobile Payments”, Master Thesis, Information Management, Faculty of Computer Sciences, Sep. 2010.
Tamas, Fabian; “NFC-enabled Automated Teller Machine”, Obuda University, NIK. Nov. 28, 2014.
TapWise—Near Field Communication (NFC) Services and Cloud-Based Tag Management, Dec. 1, 2014.
VoxLoc—Mastercard announces high level of success with biometric system. Sep. 23, 2014.
White Paper—Beyond the Hype: Mobile Payments for Merchants, 2013.
White Paper—Cloud Based Ticketing: Next Generation Fare Collection, Mar. 23, 2014.
White Paper—Mobile Commerce in Retail: Loyalty and Couponing, Jan. 2014.
White Pater—The Role of the Trusted Service Manager in Mobile Commerce, Dec. 2013.
Wollenhaupt, Gary; “Five Ways Mobile Technology will Revolutionize ATMs”, White Paper—ATM MarketPlace, 2013.
U.S. Appl. No. 14/970,102 Office Action dated May 1, 2017.
U.S. Appl. No. 14/970,102 Final Office Action dated Nov. 30, 2017.
U.S. Appl. No. 15/967,068, John Cronin, Managing NFC Data, filed Apr. 30, 2018.
U.S. Appl. No. 14/970,304 Final Office Action dated Oct. 1, 2018.
U.S. Appl. No. 14/970,080 Final Office Action dated Sep. 21, 2018.
U.S. Appl. No. 15/967,068 Office Action dated Sep. 4, 2018.
U.S. Appl. No. 14/970,125 Office Action dated Jun. 29, 2018.
U.S. Appl. No. 14/970,319 Final Office Action dated Jan. 28, 2019.
U.S. Appl. No. 14/970,125 Final Office Action dated Jan. 28, 2019.
U.S. Appl. No. 14/970,139 Final Office Action dated Jan. 18, 2019.
U.S. Appl. No. 14/970,144 Final Office Action dated Jan. 7, 2019.
U.S. Appl. No. 16/378,262, John Cronin, Transaction Modification Based on Real-Time Offers, filed Apr. 8, 2019.
U.S. Appl. No. 14/970,311 Final Office Action dated Jun. 13, 2019.
U.S. Appl. No. 14/970,056 Final Office Action dated Nov. 2, 2018.
U.S. Appl. No. 14/970,304 Office Action dated Jan. 12, 2018.
U.S. Appl. No. 14/970,314 Office Action dated Mar. 8, 2018.
U.S. Appl. No. 14/970,328 Office Action dated Feb. 14, 2018.
U.S. Appl. No. 14/970,069 Office Action dated Mar. 28, 2018.
U.S. Appl. No. 14/970,080 Office Action dated Feb. 26, 2018.
U.S. Appl. No. 14/970,311 Office Action dated Apr. 4, 2018.
U.S. Appl. No. 14/970,319 Office Action dated Jun. 26, 2018.
U.S. Appl. No. 14/970,056 Office Action dated Apr. 5, 2018.
U.S. Appl. No. 14/970,091 Office Action dated Jun. 1, 2018.
U.S. Appl. No. 14/970,340 Office Action dated Apr. 5, 2018.
U.S. Appl. No. 14/970,139 Office Action dated May 31, 2018.
U.S. Appl. No. 14/970,144 Office Action dated May 17, 2018.
U.S. Appl. No. 16/503,358, John Cronin, Managing NFC Devices Based on Downloaded Data, filed Jul. 3, 2019.
U.S. Appl. No. 14/970,304 Office Action dated Jul. 12, 2019.
U.S. Appl. No. 14/970,319 Office Action dated Jul. 10, 2019.
U.S. Appl. No. 14/970,080 Office Action dated Aug. 15, 2019.
U.S. Appl. No. 16/503,358 Office Action dated Jan. 7, 2020.
U.S. Appl. No. 14/970,311 Office Action dated Oct. 2, 2019.
Provisional Applications (1)
Number Date Country
62093298 Dec 2014 US