Real-time balance updates

Information

  • Patent Grant
  • 8645971
  • Patent Number
    8,645,971
  • Date Filed
    Friday, December 21, 2007
    16 years ago
  • Date Issued
    Tuesday, February 4, 2014
    10 years ago
Abstract
A method and a system that retrieves dynamic data when a notification with dynamic data is triggered. The dynamic data is associated with an account that is associated with a portable consumer device associated with a consumer. The method and system automatically send the notification with the dynamic data to a notification device, wherein the notification with the dynamic data is provided to the consumer.
Description
BACKGROUND

Some prior systems send consumers notices regarding current transactions. For example, an issuer may notify a consumer when their credit card is being used to make a large purchase. These prior systems often rely on contact information in the account information to notify the consumer. If, for example, only the consumer's home address is on file, the notice may not get to the consumer until well after the transaction has been completed.


Consumers with prepaid cards may want to know the balance left on their prepaid cards before a transaction or as soon as a transaction is completed. For example, a consumer may want to know whether they can afford to purchase a product with the prepaid card before they check out or even before they go to the store. Typically, a consumer contacts the issuer of their prepaid card such as a bank to determine their current balance on the prepaid card. In some cases, however, a prepaid card e.g. gift card may not be associated with an account with an issuer such as those cards purchased at retail stores. The consumer may not easily be able to get their current balance.


Embodiments of the present disclosure address these and other problems, individually and collectively.


SUMMARY OF THE INVENTION

Embodiments of the invention relate to automatic notifications, methods of providing and requesting automatic notifications, and systems that provide automatic notifications.


Embodiments of the invention address the above-noted problems by providing methods and systems of providing notifications with dynamic data to the consumer. Dynamic data refers to information that reflects all transactions on a portable consumer device made through the time a notification is triggered. An example of dynamic data is a real-time updated account balance. Examples of dynamic data include real-time updated account balance and a real-time updated rewards information associated with an account on a portable consumer device. When triggered, a notification with dynamic data is sent to the notification device e.g. cellular phone. The notification can be triggered on a periodic basis or when the consumer uses their portable consumer device to make a transaction. The notification can also be triggered when the consumer requests the dynamic data. For example, consumer could request dynamic data by placing their portable consumer device next to their notification device so that a transmitter in the portable consumer device sends a request to a receiver in the notification device. The consumer could also request the dynamic data by selecting a programmed key on their notification device. Dynamic data is then delivered to the notification device and provided to the consumer if the consumer is enrolled to receive the notification.


An embodiment of the invention is directed to a method that retrieves when a notification with dynamic data is triggered. The dynamic data is associated with an account associated with a portable consumer device associated with a consumer. The method also automatically sends the notification to the notification device, wherein the notification with dynamic data is provided to the consumer.


Another embodiment of the invention is directed to a method that triggers a notification with dynamic data using a notification device. The dynamic data is associated with an account on a portable consumer device associated with a consumer. The method also receives the notification on the notification device.


Another embodiment of the invention is directed to a system that includes a payment processing network for generating and storing dynamic data and a notification server coupled to the payment processing network. The notification server is configured to retrieve the dynamic data from the payment processing network when a notification with dynamic data is triggered. The dynamic data is associated with an account associated with a portable consumer device associated with a consumer. The notification server is also configured to automatically send the notification with the dynamic data to the notification device, wherein the notification with dynamic data is provided to consumer.


Another embodiment of the invention is directed to a phone having a processor, a receiver coupled to the processor, an output device coupled to the processor, and a computer readable medium coupled to the processor. The computer readable medium includes code for displaying a notification including dynamic data to the output device after a portable consumer device is used by a consumer.


These and other embodiments of the invention are described in further detail below.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram illustrating a dynamic data notification system, in accordance with an embodiment of the invention.



FIG. 2 is a flow chart illustrating a method of providing dynamic data notifications, in accordance with an embodiment of the invention.



FIG. 3 is a schematic drawing of a cellular phone displaying a real-time balance update, in accordance with an embodiment of the invention.





DETAILED DESCRIPTION

Embodiments of the invention are directed to a method of providing notifications with dynamic data, a method of requesting notifications with dynamic data, and a dynamic data notification system. More specifically, a notification with dynamic data is triggered when the consumer requests the notification or when the consumer uses the portable consumer device. The consumer can also have notifications automatically sent to the notification device on a periodic basis. Once the notification is triggered, dynamic data is retrieved and delivered to the notification device if the consumer is enrolled to receive the notification.


Certain embodiments of the invention may provide one or more technical advantages to issuers and consumers. One technical advantage to a consumer may be knowing their current balance or rewards available on their card without having to contact the issuer which could save time and could save the consumer money. Another technical advantage to a consumer may be that the consumer can request the current balance left on their card so that they can determine whether they have sufficient funds or credit to make a purchase or complete a transaction. A technical advantage to an issuer may be that automatic notifications are sent to consumers and issuer does not have to provide notifications by other means.


Certain embodiments of the invention may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein.



FIG. 1 is a block diagram illustrating a dynamic data notification system 10, in accordance with an embodiment of the invention. Dynamic data notification system 10 includes a consumer 20, a portable consumer device 30, a merchant 40, an acquirer 50, a payment processing network 60, an issuer 70, a notification device 80, an aggregator 90, an enrollment and notification module 100, and a computer 190. Although one consumer 20, one portable device 30, one merchant 40, one acquirer 50, one issuer 70, one notification device 80, and one computer 190 are shown, there may be any suitable number of any of these entities in dynamic data notification system 10.


Dynamic data notification system 10 includes a consumer 20 in operative communication with portable consumer device 30. Dynamic data notification system 10 also includes a merchant 40 having an access device 42 for interacting with portable consumer device 30 and an acquirer 50 associated with merchant 40. Acquirer 50 is in communication with issuer 70 through payment processing network 60.


Dynamic data notification system 10 also includes a notification device 80 in operative communication with consumer 20 for displaying notifications to consumer 20 and for receiving request or instructions for notifications from consumer 20. Notification device 80 is also in communication with portable consumer device 30 for receiving a request for a notification from consumer 20.


Dynamic data notification system 10 also includes an enrollment and notification module 100 for processing notifications and an aggregator 90 for collecting and forwarding notifications from enrollment and notification module 100 to notification device 80. Dynamic data notification system 10 also includes a computer 190 in communication with enrollment notification module 100 and consumer 20. Consumer can use computer 190 to receive notifications and to enroll in notifications. Dynamic data notification system 10 also includes a payment processing network 60 that is in communication with enrollment and notification module 100, with acquirer 50, and with issuer 70.


Consumer 20 refers to an individual or organization such as a business that is capable of purchasing goods or services or making any suitable transaction with merchant 40.


Portable consumer device 30 refers to any suitable device that allows the transaction to be conducted with merchant 40. Portable consumer device 30 may be in any suitable form. For example, suitable portable consumer devices 30 can be hand-held and compact so that they can fit into a consumer's wallet and/or pocket (e.g., pocket-sized). They may include smart cards, magnetic stripe cards, keychain devices (such as the Speedpass™ commercially available from Exxon-Mobil Corp.), etc. Other examples of portable consumer devices 30 include cellular phones, personal digital assistants (PDAs), pagers, payment cards, security cards, access cards, smart media, transponders, and the like. In some cases, portable consumer device 30 may be associated with an account of consumer 20 such as a bank account.


In the illustrated example, portable consumer device 30 includes a contactless transmitter 32 for sending wireless signals, a processor 34, and a computer readable medium (CRM) 36. These elements of portable consumer device 30 are in communication with each other. Processor 34 (e.g., a microprocessor) processes the functions of portable consumer device 30.


Contactless transmitter 32 refers to any suitable device for sending wireless signals with information stored in memory (e.g. CRM 36) on portable consumer device 30 to notification device 80. Contactless transmitter 32 transmits signals using a near field communications (NFC) capability to send information from portable consumer device 30 to the contactless receiver 82 on notification device 82. Typically, NFC capability is in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Some examples of NFC capability are radio-frequency identification (RFID), Bluetooth™, infra-red, and other suitable communications capability. In other embodiments, contactless transmitter 32 transmits information via a cellular network by means of an interface (not shown). The interface functions to permit exchange of data between the cellular network (not shown) and contactless transmitter 32.


CRM 36 may be on the body of portable consumer device 30. The body may in the form of a plastic substrate, a housing, or other structure. CRM 36 may be a memory that stores data and may be in any suitable form. Exemplary CRM 36 may be in any suitable form including a magnetic stripe, a memory chip, etc. If portable consumer device 30 is in the form of a card, it may have an embossed region (ER) which is embossed with a PAN (primary account number). CRM 36 may electronically store the PAN as well as other data such as PIN data.


Merchant 40 refers to any suitable entity or entities that makes a transaction with consumer 20. Merchant 40 may use any suitable method to make the transaction. For example, merchant 40 may use an e-commerce business to allow the transaction to be conducted by merchant 40 through the Internet. Other examples of merchant 40 include a department store, a gas station, a drug store, a grocery store, or other suitable business.


Access device 42 may be any suitable device for communicating with merchant 40 and for interacting with portable consumer device 30. Access device 42 can be in any suitable location such as at the same location as merchant 40. Access device 42 may be in any suitable form. Some examples of access devices 42 include POS devices, cellular phones, PDAs, personal computers (PCs), tablet PCs, handheld specialized readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, websites, and the like. Access device 42 may use any suitable contact or contactless mode of operation to send or receive data from portable consumer devices 30.


If access device 42 is a POS terminal, any suitable POS terminal may be used and may include a reader, a processor, and a computer readable medium. Reader may include any suitable contact or contactless mode of operation. For example, exemplary card readers can include radio frequency (RF) antennas, optical scanners, bar code reader, magnetic stripe readers, etc. to interact with portable consumer device 30.


Acquirer 50 refers to any suitable entity that has an account with merchant 40. In some embodiments, issuer 70 may also be acquirer 50.


Issuer 70 refers to any suitable entity that may open and maintain an account associated with portable consumer device 30 for consumer 20. Some examples of issuers may be a bank, a business entity such as a retail store, or a governmental entity. In many cases, issuer 70 may also issue portable consumer device 30 associated with the account to consumer 20.


Payment processing network 60 refers to a network of suitable entities that have information related an account associated with portable consumer device 30. This information includes data associated with the account on portable consumer device 30 such as profile information, dynamic data, and other suitable information. Dynamic data refers to any suitable information that is updated to reflect the transactions made using portable consumer device 30.


Although not shown in the illustrated embodiment, payment processing network 60 may have or operate a server computer and may include a database. The database may include any hardware, software, firmware, or combination of the preceding for storing and facilitating retrieval of information. Also, the database may use any of a variety of data structures, arrangements, and compilations to store and facilitate retrieval of information. The server computer may be coupled to the database and may include any hardware, software, other logic, or combination of the preceding for servicing the requests from one or more client computers. Server computer may use any of a variety of computing structures, arrangements, and compilations for servicing the requests from one or more client computers. In one embodiment, the server computer may be a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a Web server. Server computer services the requests of one or more client computers.


Payment processing network 60 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. An exemplary payment processing network 60 may include VisaNet™. Networks that include VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system which performs clearing and settlement services. Payment processing network 60 may use any suitable wired or wireless network, including the Internet.


Notification device 80 refers to any suitable device for receiving notifications and for providing the notifications to consumer 20. Notifications refer to communications of dynamic data to consumer 20 on notification device 80. Notifications may be in any suitable form and may be delivered by any suitable method. Some examples of notifications includes a phone call, a voice message, a voicemail message, a short message service (SMS) message e.g. a text message, an instant messaging (IM) message, or an email message, or a periodically updated display on a device. An exemplary embodiment of a notification is a real-time balance update. The real-time balance update is a communication to notify consumer 20 of the funds available (balance) on portable consumer device 30 after the last transaction is accounted for. Another embodiment of a notification is real-time rewards information update that is a communication to notify consumer 20 of rewards available for redemption after the last transaction.


Dynamic data refers to any suitable information that reflects all transactions on a portable consumer device 30 made through the time a notification of the dynamic data is triggered. Dynamic data relates to an account associated with a portable consumer device 30 associated with consumer 20. For example, dynamic data can be account balances such as credit card account balances, stored value account balances, rewards balances, checking account balances, savings account balances, investment account balances, brokerage account balances, and other suitable account balances.


Notification device 80 may be in any suitable form. For example, suitable notification devices 80 can be hand-held and compact so that they can fit into a consumer's wallet and/or pocket (e.g., pocket-sized). Some examples of notification device 80 include desktop or laptop computers, cellular phones (e.g., as shown in FIG. 3), personal digital assistants (PDAs), pagers, payment cards, security cards, access cards, smart media, transponders, and the like. In some embodiments, notification device 80 and portable consumer device 30 are embodied in the same device.


Notification device 80 includes a contactless receiver 82 for receiving wireless signals, a processor 84 coupled to the receiver 82, and a computer readable medium (CRM) 36 coupled to processor 84. Although not shown, notification device 80 may also include one or more input devices (e.g., keypads) or output devices (e.g., displays, speakers) coupled to processor 84. Contactless receiver 82 refers to any suitable device for receiving wireless signals. The signals are received by contactless receiver 82 by any suitable method (e.g., using NFC capability). In one example, contactless receiver 82 receives a wireless signal with a request for a notification from contactless transmitter 32 of portable consumer device 30. In another example, contactless receiver 82 receives a wireless signal with a notification(s) from aggregator 90 via a cellular network. Processor 84 (e.g., a microprocessor) processes the functions of notification device 80. CRM 86 comprises code for processing requests for notifications, for receiving notifications, and for providing notifications to consumer 20. An example of code for providing notifications to consumer 20 includes code for displaying notifications including dynamic data to an output device.


Consumer 20 uses computer 190 to receive notifications and/or enroll in a program to receive notifications. Computer 190 can be a desktop computer, a laptop computer, a cellular or mobile phone, a personal digital assistant (PDA), or other suitable device.


Enrollment and notification module 100 comprises a notification enrollment server 105, a notification enrollment application server 110, a database server 120, a notification database 130, a notification server 150 having a dynamic balance module 160 and a dynamic rewards module 170, and a gateway 140. Notification enrollment server 105 in communication with a notification enrollment application server 110 which is in communication with database server 120 for storing and retrieving information to and from notification database 130. Database server 120 is also in communication with notification server 150. Notification server 150 is also in communication with gateway 140, dynamic balance module 160, and dynamic rewards module 170. Although enrollment and notification module 100 is shown as being separate from issuer 70, enrollment and notification module 100 can be at issuer 70 in some embodiments. In these embodiments, issuer 70 processes the notifications sent to notification device 80.


Notification enrollment server 105 refers to a device that receives enrollment information from consumer 20 via computer 190 and sends the enrollment information to notification enrollment application server 110. Notification enrollment application server 110 receives the enrollment information from consumer 20 through notification enrollment server 105 or from issuer 70 and may store the enrollment information in notification database 130. Notification database 130 may receive and store new or updated enrollment information and other account information.


Enrollment information includes trigger information that describes the occurrences that must take place to trigger notifications and the types of dynamic data that consumer 20 wants to receive in the notifications. Consumer 20 may define the trigger information when enrolling in a program to receive notifications.


In some cases, notifications are triggered by actions taken by consumer 20 or another suitable entity. For example, a notification may be triggered by using of portable consumer device 30 at access device 42 by consumer 20 or by merchant 40. In another example, a notification may be triggered by the sending of a request by consumer 20 for a notification using portable consumer device 30, notification device 80, computer 190, or other suitable device. In yet another example, a notification may be triggered by placing portable consumer device 30 near notification device 80 so that a signal with a request for a notification is transmitted from contactless transmitter 32 on portable consumer device 30 to contactless receiver 82 on notification device 80. In another example, a notification may be triggered by the completion of a transaction on an account associated with portable consumer device 30. In other cases, periodic notifications may be triggered by the termination a time period defined by consumer 20. Examples of a time period include a week, a day, and an hour. For example, if consumer 20 selects the time period of a day, daily notifications will be sent to notification device 80. Typically, daily notifications would be sent at approximately the same time every day.


Notification server 150 includes dynamic balance module 160 for processing notifications with dynamic balances and dynamic rewards module 170 for processing notifications with dynamic rewards information.


Notification server 150 processes notifications with dynamic data and sends the notifications through gateway 140 to aggregator 90. If the dynamic data is a dynamic balance, dynamic balance module 160 processes the notification. If the dynamic data is dynamic rewards, dynamic rewards module 170 processes the notification. Gateway 140 is a any suitable device that converts information from the protocol or format used in enrollment and notification module 100 to those used in aggregator 90. Aggregator 90 refers to any suitable entity or device that receives notifications, collects the notifications, and transmits the notifications to notification device 80 for consumer 20. In some cases, aggregator 90 may be a wireless telephone company.


Notification server 150 is triggered to send a notification with dynamic data and processes the notification. Notification server 150 retrieves enrollment information with trigger information from notification database 130 using database server 120. Notification server 150 confirms that consumer 20 is enrolled to receive the notification triggered based on the trigger information. Notification server 150 retrieves the dynamic data from issuer 70 or other suitable entity and sends the notification with the dynamic data through gateway 140 to aggregator 90. Aggregator 90 collects notifications according to enrollment information and forwards the notifications to notification device 80. If the notification triggered is associated with dynamic balance data, dynamic balance module 160 processes the notification. If the notification triggered is associated with dynamic rewards data, dynamic rewards module 170 processes the notification.


In one example embodiment, consumer 20 enrolls in a program using computer 190 to receive notifications on their notification device 80 (e.g. a cellular phone) in the form of text or voice messages. Consumer 20 enrolls to receive notifications with the dynamic balance on the account associated with their portable consumer device 30 (e.g. a prepaid or gift card). Consumer 20 specifies that the notification will be sent every time portable consumer device 30 interacts with access device 42.


In a typical payment transaction, consumer 20 uses portable consumer device 30 at access device 42 to purchase goods or services from merchant 40. For example, a consumer may use a gift card with $50 to buy a $25 game cartridge at a toy store using a POS (point of sale) terminal at the toy store. The consumer may swipe the gift card through a slot in the POS terminal and the POS terminal may read data including an account number from the gift card.


An authorization request message is then forwarded to acquirer 50 and acquirer 50 forwards the message through payment processing network 60 to issuer 70. Using portable consumer device 30 at access device 42 triggers notification server 150 to send a notification.


Issuer 70 determines whether or not to authorize the transaction. The transaction may be authorized if there are sufficient funds, and may be declined if there are insufficient funds. An authorization response message is then sent back through payment processing network 60 to acquirer 50 who forwards it to merchant 40. At the end of the day, a normal clearing and settlement process can be conducted by payment processing network 60. A clearing process is a process of exchanging financial details between and acquirer and an issuer to facilitate posting to a consumer's account and reconciliation of the consumer's settlement position.


In this example, the notification triggered is associated with a dynamic balance and dynamic balance module 160 processes the notification. Dynamic balance module 160 is triggered to send a notification when consumer used portable consumer device 30. For example, dynamic balance module 160 may receive information that the previously described and registered gift card has been used to purchase a $25 game cartridge.


Dynamic balance module 160 retrieves enrollment information with trigger information from notification database 130 using database server 120. Dynamic balance module 160 uses the trigger information to confirm that consumer 20 wants to receive the notification that has been triggered. Dynamic balance module 160 also determines from the trigger information that consumer 20 wants to receive the triggered notification in the form of a text message. Dynamic balance module 160 retrieves the dynamic balance on the account associated with portable consumer device 30. For example, the module 160 may determine that there is the balance on the gift card is $25. The dynamic balance will reflect the last transaction authorized including the transaction associated with the action of using portable consumer device 30 that triggered the notification. Dynamic balance module 160 sends a text message with the dynamic balance to notification device 80. For example, the text message may indicate that the gift card now has a balance of $25 after buying the $25 game cartridge. Notification device 80 provides the text message to consumer 10. For example, the consumer's phone may display the balance of $25 plus the account number associated with the gift card. Consumer 20 may thereafter store this information in the notification device 80 for future use in determining how much money is left on the portable consumer device 30.


Modifications, additions, or omissions may be made to dynamic data notification system 10 without departing from the scope of the disclosure. The components of dynamic data notification system 10 may be integrated or separated according to particular needs. Moreover, the operations of dynamic data notification system 10 may be performed by more, fewer, or other system modules. Additionally, operations of dynamic data notification system 10 may be performed using any suitable logic comprising software, hardware, other logic, or any suitable combination of the preceding.



FIG. 2 is a flow chart illustrating a method of providing dynamic data notifications, in accordance with an embodiment of the invention.


Consumer 20 enrolls in a program using computer 190 to receive notifications on their portable consumer device 30 (step 200). Computer 190 sends enrollment information from consumer 20 to notification enrollment server 105. Notification enrollment server 105 sends the enrollment information to notification enrollment application server 110. Notification enrollment application server 110 sends the enrollment information to database server 120 to store it in notification database 130.


A notification is triggered (step 210). Notification server 150 detects that the notification has been triggered. Consumer 20 or other suitable entity triggers the notification.


In one embodiment, consumer 20 or other suitable entity triggers a notification by using portable consumer device 30 at access device 42. In some cases, a notification is only triggered if the transaction is authorized and completed. When portable consumer device 30 is used, information indicating that a notification has been triggered is sent from access device 42 to acquirer 50 which forwards it to notification server 150 through payment processing network 60.


In another embodiment, consumer 20 triggers a notification by requesting it on notification device 80 or computer 190 which forwards the request for a notification to notification server 150. For example, consumer 20 may request a notification by selecting a programmed button on their cellular phone. The cellular phone sends the request to notification server 150.


In another embodiment, consumer 20 triggers a notification by placing portable consumer device 30 next to notification device 80. A signal with a request for a notification is emitted from contactless transmitter 32 in portable consumer device 30 and received by contactless receiver 82 on notification device 80. Notification device 80 forwards the request to notification server 150.


In yet another embodiment, a notification is triggered automatically on a periodic basis by notification server 150. Typically, the notification is triggered at the end of the time period although any time during that time period can be used. Consumer 20 selects the time period such as daily, hourly, or weekly. For example, consumer 20 can select daily notifications sent at 12:00 a.m.


In one example embodiment, consumer 20 enrolls in a program using computer 190 to receive notifications on their notification device 80 e.g. cellular phone in the form of email messages. Consumer 20 enrolls to receive notifications with the dynamic balance on the account on their portable consumer device 30 e.g. a prepaid card. Consumer 20 specifies that the notification will be sent every time portable consumer device 30 interacts with access device 42.


Notification server 150 retrieves enrollment information (step 220) retrieved from notification database 130 using database server 120. The enrollment information is associated with an account on portable consumer device 30. In embodiments where consumer 20 requested the notification, notification server 150 may skip retrieving the enrollment information and checking enrollment for the notification (steps 220 and 230) and go to retrieving dynamic data (step 240).


Notification server 150 analyzes trigger information in the enrollment information to determine whether consumer 20 is enrolled to receive the notification that has been triggered (step 230). If consumer 20 is not enrolled for the notification, the method ends (step 270) and a notification is not sent to consumer 20.


If consumer 20 is enrolled to receive the notification, notification server 150 retrieves the dynamic data (step 240). Notification server 150 generates a notification with the dynamic data and sends it to aggregator 90 through gateway 140. Aggregator 90 forwards the notification to notification device 160 for delivery to consumer 20 (step 250). Notification device 80 provides the notification to consumer 20 (step 260).


In one embodiment, the notification may be shown to consumer 20 on a screen on notification device 80. The display of the notification may be a text message displayed on a screen or other suitable display until consumer 20 turns off the display. In other cases, the notification may be displayed for a predetermined period of time.


In another embodiment, the notification may be sent to consumer in the form of a voice message or voicemail message to consumer 20. For example, the notification may be an automated voice announcement that is sent to the notification device 20.


After providing the notification, the method ends (step 270). Modifications, additions, or omissions may be made to the method without departing from the scope of the disclosure. The method may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order without departing from the scope of the disclosure.



FIG. 3 is a schematic drawing of a cellular phone displaying a real-time balance update, in accordance with an embodiment of the invention. Notification device 80 includes a display 320 for displaying information such as notifications with dynamic data, buttons 330 for inputting information such as requests for notifications, a speaker (not shown) to send aural signals to consumer 20, and a microphone (not shown) to receive aural signals from consumer 20.


Display 320 includes a dynamic data display 322 for displaying the notification of the updated dynamic data consumer 20. In the illustrated example, dynamic data display 322 is showing the real-time balance update on the account associated with portable consumer device 30. Dynamic data can be updated at any suitable time. Some examples of when the dynamic data is updated include when consumer requests the dynamic data, when consumer 20 uses portable consumer device 30, or periodically.


Buttons 330 include a balance request button 334 for requesting a real-time balance update and a rewards request button 336 for requesting a real-time rewards information update. Display 320 also includes a balance request button indicator 324 indicating that selecting balance request button 334 will request a real-time balance update. Display 320 also includes a rewards request button indicator 326 indicating that selecting rewards request button 336 will request a real-time rewards information update.


In operation, consumer 20 selects balance request button 334 to display real-time balance update on dynamic data display 322. The request is forwarded to notification server 150. Notification server 150 retrieves the real-time balance from issuer 70 or other suitable entity over payment processing network 60. Notification server 150 sends the real-time balance update to notification device 80 and notification device 80 displays the update to consumer 20.


Modifications, additions, or omissions may be made to notification device 80 without departing from the scope of the disclosure. For example, notification device 80 and portable consumer device 30 may be integrated into the same device. Also, the components of notification device 80 may be integrated or separated according to particular needs. Moreover, the operations of notification device 80 may be performed by more, fewer, or other modules. Additionally, operations of notification device 80 may be performed using any suitable logic comprising software, hardware, other logic, or any suitable combination of the preceding.


It should be understood that the present disclosure as described above can be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present disclosure using hardware and a combination of hardware and software.


Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.


A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.


The above description is illustrative and is not restrictive. Many variations of the disclosure will become apparent to those skilled in the art upon review of the disclosure. The scope of the disclosure should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.


One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the disclosure.

Claims
  • 1. A method comprising: triggering a notification using a notification device of a consumer, wherein the notification is triggered by placing the notification device near a portable consumer device; andreceiving the notification on the notification device,wherein the notification device belongs to the consumer and comprises a contactless receiver, a processor, a computer-readable medium, and a display,wherein the portable consumer device belongs to the consumer and is associated with an account identifier and comprises a payment device and a contactless transmitter,wherein the notification comprises dynamic data associated with the account, andwherein by placing the portable consumer device near the notification device, a signal is sent from the contactless transmitter on the portable consumer device to the contactless receiver on the notification device.
  • 2. The method of claim 1, wherein the dynamic data is a real-time balance update.
  • 3. The method of claim 1, wherein the dynamic data is a real-time rewards information update.
  • 4. The method of claim 1, wherein the notification with the dynamic data is provided to consumer on the display of the notification device.
  • 5. The method of claim 4, wherein the notification with the dynamic data is provided in response to a request for the notification by the consumer on the notification device.
  • 6. A method of claim 1, wherein the notification device is a phone, andwherein the notification sent to the notification device includes at least one of a phone call, voicemail, short message service (SMS), instant message (IM), or email.
  • 7. A method of claim 1, wherein the dynamic data is based on a transaction conducted using the portable consumer device at an access device located at a merchant.
  • 8. The method of claim 1, wherein the notification device sends a request for the notification to a notification server in operative communication with a payment processing network.
  • 9. A method of claim 1, wherein the notification device and the portable consumer device are separate devices.
  • 10. A system comprising: a payment processing network for generating and storing dynamic data; anda notification server, comprising a processor and a computer-readable medium, coupled to the payment processing network, the notification server configured to: when a notification with dynamic data is triggered, retrieve the dynamic data from the payment processing network, wherein the dynamic data is associated with an account associated with a portable consumer device belonging to a consumer, wherein the portable consumer device comprises a payment device and a contactless transmitter; andsend the notification with the dynamic data to a notification device belonging to the consumer, wherein the notification with dynamic data is provided to the consumer and wherein the notification device includes a contactless receiver,wherein the notification with dynamic data is triggered by placing the notification device near the portable consumer device such a contactless signal is sent from the contactless transmitter on the portable consumer device to the contactless receiver on the notification device.
  • 11. The system of claim 10, wherein the notification server is further configured to: retrieve enrollment information; andconfirm that consumer is enrolled to receive the notification based on the enrollment information.
  • 12. The system of claim 10, wherein the dynamic data is based on an amount of a transaction being conducted.
  • 13. The system of claim 10, wherein the dynamic data is based on an amount of rewards available for redemption after a transaction.
  • 14. A system of claim 13, wherein the transaction is a most recent transaction.
  • 15. A method comprising: when a notification with dynamic data is triggered, retrieving the dynamic data associated with an account associated with a portable consumer device belonging to a consumer; andsending the notification with the dynamic data to a notification device belonging to the consumer, wherein the notification with the dynamic data is provided to the consumer,wherein the notification device belongs to the consumer and comprises a contactless receiver, a processor, a computer-readable medium, and a display,wherein the portable consumer device comprises a payment device and a contactless transmitter,wherein the notification comprises dynamic data associated with the account, andwherein the notification is triggered by placing the notification device near the portable consumer device such a contactless signal is sent from the contactless transmitter on the portable consumer device to the contactless receiver on the notification device.
  • 16. A method of claim 15, wherein the dynamic data is a real-time balance update.
  • 17. A method of claim 15, wherein the dynamic data is a real-time rewards information update.
  • 18. A method of claim 15, further comprising: retrieving enrollment information; andconfirming that consumer is enrolled to receive the notification based on the enrollment information.
  • 19. A method of claim 15, wherein the notification is triggered by a request for the notification with dynamic data sent from the notification device.
  • 20. A method of claim 15, wherein the notification with the dynamic data is provided to consumer on a display of the notification device.
  • 21. A method of claim 15, wherein the notification device is a phone, andwherein the notification sent to the notification device includes at least one of a phone call, voicemail, short message service (SMS), instant message (IM), or email.
  • 22. A method of claim 15, wherein the dynamic data is based on an amount of a transaction and the transaction occurs at an access device located at a merchant.
  • 23. A non-transitory computer-readable medium, executable by a processor, for performing a method comprising the steps of: when a notification with dynamic data is triggered, retrieving the dynamic data associated with an account associated with a portable consumer device belonging to a consumer;sending the notification with the dynamic data to a notification device belonging to the consumer, wherein the notification with the dynamic data is provided to the consumer; andwherein the notification device belongs to the consumer and comprises a contactless receiver, a processor, a computer-readable medium, and a display,wherein the portable consumer device comprises a payment device and a contactless transmitter,wherein the notification comprises dynamic data associated with the account, andwherein the notification is triggered by placing the notification device near the portable consumer device such a contactless signal is sent from the contactless transmitter on the portable consumer device to the contactless receiver on the notification device.
CROSS-REFERENCES TO RELATED APPLICATIONS

This is a non-provisional patent application of and claims the benefit of the filing date of U.S. Provisional Patent Application No. 60/871,898 filed on Dec. 26, 2006. This application is herein incorporated by reference in its entirety for all purposes.

US Referenced Citations (327)
Number Name Date Kind
3356021 May et al. Dec 1967 A
4044231 Beck et al. Aug 1977 A
4613904 Lurie Sep 1986 A
4614861 Pavlov et al. Sep 1986 A
4674041 Lemon et al. Jun 1987 A
4701601 Francini et al. Oct 1987 A
4868376 Lessin et al. Sep 1989 A
5034597 Atsumi et al. Jul 1991 A
5305196 Deaton et al. Apr 1994 A
5327508 Deaton et al. Jul 1994 A
5353218 DeLapa et al. Oct 1994 A
5359183 Skodlar Oct 1994 A
5388165 Deaton et al. Feb 1995 A
RE34915 Nichtberger et al. Apr 1995 E
5420606 Begum et al. May 1995 A
5430644 Deaton et al. Jul 1995 A
5448471 Deaton et al. Sep 1995 A
5465206 Hilt et al. Nov 1995 A
5477038 Levine et al. Dec 1995 A
5483444 Heintzeman et al. Jan 1996 A
5500513 Langhans et al. Mar 1996 A
5502636 Clarke Mar 1996 A
5530438 Bickham et al. Jun 1996 A
5564073 Takahisa Oct 1996 A
5577266 Takahisa et al. Nov 1996 A
5579537 Takahisa Nov 1996 A
5592560 Deaton et al. Jan 1997 A
5604921 Alanara Feb 1997 A
5615110 Wong Mar 1997 A
5621201 Langhans et al. Apr 1997 A
5621812 Deaton et al. Apr 1997 A
5627549 Park May 1997 A
5638457 Deaton et al. Jun 1997 A
5642485 Deaton et al. Jun 1997 A
5644723 Deaton et al. Jul 1997 A
5649114 Deaton et al. Jul 1997 A
5659165 Jennings et al. Aug 1997 A
5659469 Deaton et al. Aug 1997 A
5675662 Deaton et al. Oct 1997 A
5678939 Ross Oct 1997 A
5687322 Deaton et al. Nov 1997 A
5708422 Blonder et al. Jan 1998 A
5710886 Christensen et al. Jan 1998 A
5717866 Naftzger Feb 1998 A
5761648 Golden et al. Jun 1998 A
5777903 Piosenka et al. Jul 1998 A
5791991 Small Aug 1998 A
5793972 Shane Aug 1998 A
5806044 Powell Sep 1998 A
5822735 De Lapa et al. Oct 1998 A
5855007 Jovicic et al. Dec 1998 A
5870030 DeLuca et al. Feb 1999 A
5884277 Khosla Mar 1999 A
5905246 Fajkowski May 1999 A
5907830 Engel et al. May 1999 A
5924080 Johnson Jul 1999 A
5959577 Fan et al. Sep 1999 A
5974399 Giuliani et al. Oct 1999 A
5991749 Morrill, Jr. Nov 1999 A
6002771 Nielsen Dec 1999 A
6009411 Kepecs Dec 1999 A
6009415 Shurling et al. Dec 1999 A
6012038 Powell Jan 2000 A
6014634 Scroggie et al. Jan 2000 A
6018718 Walker et al. Jan 2000 A
6029151 Nikander Feb 2000 A
6035280 Christensen Mar 2000 A
6041309 Laor Mar 2000 A
6049778 Walker et al. Apr 2000 A
6055505 Elston Apr 2000 A
6062991 Moriarty et al. May 2000 A
6064990 Goldsmith May 2000 A
6067526 Powell May 2000 A
6067529 Ray et al. May 2000 A
6076068 DeLapa et al. Jun 2000 A
6076069 Laor Jun 2000 A
6076101 Kamakura et al. Jun 2000 A
6128599 Walker et al. Oct 2000 A
6185290 Shaffer et al. Feb 2001 B1
6185541 Scroggie et al. Feb 2001 B1
6227447 Campisano May 2001 B1
6237145 Narasimhan et al. May 2001 B1
6247129 Keathley et al. Jun 2001 B1
6267292 Walker et al. Jul 2001 B1
6279112 O'Toole, Jr. et al. Aug 2001 B1
6292786 Deaton et al. Sep 2001 B1
6307958 Deaton et al. Oct 2001 B1
6318631 Halperin Nov 2001 B1
6321208 Barnett et al. Nov 2001 B1
6330543 Kepecs Dec 2001 B1
6330550 Brisebois et al. Dec 2001 B1
6334108 Deaton et al. Dec 2001 B1
6336098 Fortenberry et al. Jan 2002 B1
6336099 Barnett et al. Jan 2002 B1
6341724 Campisano Jan 2002 B2
6351735 Deaton et al. Feb 2002 B1
6377935 Deaton et al. Apr 2002 B1
6378775 Hayashida Apr 2002 B2
6381324 Shaffer et al. Apr 2002 B1
6424949 Deaton et al. Jul 2002 B1
6424951 Shurling et al. Jul 2002 B1
6434534 Walker et al. Aug 2002 B1
6470181 Maxwell Oct 2002 B1
6484146 Day et al. Nov 2002 B2
6488203 Stoutenburg et al. Dec 2002 B1
6505046 Baker Jan 2003 B1
6516302 Deaton et al. Feb 2003 B1
6529725 Joao et al. Mar 2003 B1
6535855 Cahill et al. Mar 2003 B1
6560581 Fox et al. May 2003 B1
6584309 Whigham Jun 2003 B1
6587835 Treyz et al. Jul 2003 B1
6594376 Hoffman et al. Jul 2003 B2
6601759 Fife et al. Aug 2003 B2
6609104 Deaton et al. Aug 2003 B1
6611811 Deaton et al. Aug 2003 B1
6631849 Blossom Oct 2003 B2
6647257 Owensby Nov 2003 B2
6647269 Hendrey et al. Nov 2003 B2
6664948 Crane et al. Dec 2003 B2
6684195 Deaton et al. Jan 2004 B1
6685093 Challa et al. Feb 2004 B2
6736322 Gobburu et al. May 2004 B2
6747547 Benson Jun 2004 B2
6749118 Kobayashi et al. Jun 2004 B2
6775539 Deshpande Aug 2004 B2
6832721 Fujii Dec 2004 B2
6837425 Gauthier et al. Jan 2005 B2
6868391 Hultgren Mar 2005 B1
6877665 Challa et al. Apr 2005 B2
6892941 Rosenblum May 2005 B2
6912398 Domnitz Jun 2005 B1
6920611 Spaeth et al. Jul 2005 B1
6975852 Sofer et al. Dec 2005 B1
6990330 Voerepalli et al. Jan 2006 B2
7003497 Maes Feb 2006 B2
7007840 Davis Mar 2006 B2
7013286 Aggarwal et al. Mar 2006 B1
7025256 Drummond et al. Apr 2006 B1
7028906 Challa et al. Apr 2006 B2
7039611 Devine May 2006 B2
7040533 Ramachandran May 2006 B1
7051923 Nguyen et al. May 2006 B2
7055031 Platt May 2006 B2
7076329 Kolls Jul 2006 B1
7089208 Levchin et al. Aug 2006 B1
7099850 Mann et al. Aug 2006 B1
7104446 Bortolin et al. Sep 2006 B2
7107250 Harrison Sep 2006 B2
7110954 Yung et al. Sep 2006 B2
7121456 Spaeth et al. Oct 2006 B2
7124937 Myers et al. Oct 2006 B2
7150393 Drummond et al. Dec 2006 B1
7152780 Gauthier et al. Dec 2006 B2
7159770 Onozu et al. Jan 2007 B2
7194437 Britto et al. Mar 2007 B1
7201313 Ramachandran Apr 2007 B1
7203300 Shaffer et al. Apr 2007 B2
7207477 Ramachandran Apr 2007 B1
7213755 Newsome et al. May 2007 B2
7231357 Shanman et al. Jun 2007 B1
7231372 Prange et al. Jun 2007 B1
RE39736 Morrill, Jr. Jul 2007 E
7243853 Levy et al. Jul 2007 B1
7257545 Hung Aug 2007 B1
7280981 Huang et al. Oct 2007 B2
7290704 Ball et al. Nov 2007 B1
7308254 Rissanen Dec 2007 B1
7343149 Benco et al. Mar 2008 B2
7350702 Bortolin et al. Apr 2008 B2
7353187 Emodi et al. Apr 2008 B1
7356516 Richey et al. Apr 2008 B2
7357310 Calabrese et al. Apr 2008 B2
7407094 Myers et al. Aug 2008 B2
7440771 Purk Oct 2008 B2
7447662 Gibson Nov 2008 B2
7464867 Kolls Dec 2008 B1
7653599 Doran et al. Jan 2010 B2
7711783 Violleau et al. May 2010 B1
8127999 Diamond Mar 2012 B2
20010013542 Horowitz et al. Aug 2001 A1
20020013711 Ahuja et al. Jan 2002 A1
20020062249 Iannacci et al. May 2002 A1
20020065713 Awada et al. May 2002 A1
20020091569 Kitaura et al. Jul 2002 A1
20020128903 Kernahan Sep 2002 A1
20020161701 Warmack Oct 2002 A1
20020165775 Tagseth et al. Nov 2002 A1
20020169719 Dively et al. Nov 2002 A1
20020190118 Davenport et al. Dec 2002 A1
20020198777 Yuasa Dec 2002 A1
20030004808 Elhaoussine Jan 2003 A1
20030058261 Challa et al. Mar 2003 A1
20030120593 Bansal et al. Jun 2003 A1
20030126078 Vihinen Jul 2003 A1
20030144907 Cohen et al. Jul 2003 A1
20030172040 Kemper et al. Sep 2003 A1
20030208406 Okamoto et al. Nov 2003 A1
20030212595 Antonucci Nov 2003 A1
20030212642 Weller et al. Nov 2003 A1
20030225618 Hessburg et al. Dec 2003 A1
20030230630 Whipple et al. Dec 2003 A1
20030233292 Richey et al. Dec 2003 A1
20040019522 Bortolin et al. Jan 2004 A1
20040030601 Pond et al. Feb 2004 A1
20040044621 Huang et al. Mar 2004 A1
20040049455 Mohsenzadeh Mar 2004 A1
20040050922 Gauthier et al. Mar 2004 A1
20040054575 Marshall Mar 2004 A1
20040054581 Redford et al. Mar 2004 A1
20040054590 Redford et al. Mar 2004 A1
20040054591 Spaeth et al. Mar 2004 A1
20040064406 Yates et al. Apr 2004 A1
20040117254 Nemirofsky et al. Jun 2004 A1
20040133653 Defosse et al. Jul 2004 A1
20040139021 Reed et al. Jul 2004 A1
20040148224 Gauthier et al. Jul 2004 A1
20040153715 Spaeth et al. Aug 2004 A1
20040158534 Azami et al. Aug 2004 A1
20040186770 Pettit et al. Sep 2004 A1
20040199470 Ferry, Jr. et al. Oct 2004 A1
20040220964 Shiftan et al. Nov 2004 A1
20040243519 Perttila et al. Dec 2004 A1
20040254848 Golan et al. Dec 2004 A1
20040260653 Tsuei et al. Dec 2004 A1
20050021456 Steele et al. Jan 2005 A1
20050029344 Davis Feb 2005 A1
20050035847 Bonalle et al. Feb 2005 A1
20050036611 Seaton, Jr. et al. Feb 2005 A1
20050045718 Bortolin et al. Mar 2005 A1
20050058427 Nguyen et al. Mar 2005 A1
20050071225 Bortolin et al. Mar 2005 A1
20050071226 Nguyen et al. Mar 2005 A1
20050071227 Hammad et al. Mar 2005 A1
20050071228 Bortolin et al. Mar 2005 A1
20050071235 Nguyen et al. Mar 2005 A1
20050075958 Gonzalez Apr 2005 A1
20050097473 Malik et al. May 2005 A1
20050102233 Park et al. May 2005 A1
20050102234 Devine May 2005 A1
20050121506 Gauthier et al. Jun 2005 A1
20050149455 Bruesewitz et al. Jul 2005 A1
20050177510 Hilt et al. Aug 2005 A1
20050199714 Brandt et al. Sep 2005 A1
20050210387 Alagappan et al. Sep 2005 A1
20050219061 Lai et al. Oct 2005 A1
20050222933 Wesby Oct 2005 A1
20050283416 Reid et al. Dec 2005 A1
20050283430 Reid et al. Dec 2005 A1
20050283431 Reid et al. Dec 2005 A1
20050283432 Reid et al. Dec 2005 A1
20050283433 Reid et al. Dec 2005 A1
20060053056 Alspach-Goss et al. Mar 2006 A1
20060059110 Madhok et al. Mar 2006 A1
20060079282 Niimi Apr 2006 A1
20060080243 Kemper et al. Apr 2006 A1
20060085260 Yamagishi Apr 2006 A1
20060111967 Forbes May 2006 A1
20060122881 Walker et al. Jun 2006 A1
20060155644 Reid et al. Jul 2006 A1
20060163345 Myers et al. Jul 2006 A1
20060178957 LeClaire Aug 2006 A1
20060179007 Davis Aug 2006 A1
20060202025 Calabrese et al. Sep 2006 A1
20060206376 Gibbs et al. Sep 2006 A1
20060218086 Campbell et al. Sep 2006 A1
20060224449 Byerley et al. Oct 2006 A1
20060247981 Singh et al. Nov 2006 A1
20060248007 Hofer et al. Nov 2006 A1
20060253390 McCarthy et al. Nov 2006 A1
20060270421 Phillips et al. Nov 2006 A1
20060282382 Balasubramamian et al. Dec 2006 A1
20060290501 Hammad et al. Dec 2006 A1
20060293027 Hammad et al. Dec 2006 A1
20070001000 Nguyen et al. Jan 2007 A1
20070001001 Myers et al. Jan 2007 A1
20070005613 Singh et al. Jan 2007 A1
20070005774 Singh et al. Jan 2007 A1
20070012764 Bortolin et al. Jan 2007 A1
20070017970 Gauthier et al. Jan 2007 A1
20070027803 Brandes et al. Feb 2007 A1
20070034679 Gauthier et al. Feb 2007 A1
20070055597 Patel et al. Mar 2007 A1
20070055630 Gauthier et al. Mar 2007 A1
20070057034 Gauthier et al. Mar 2007 A1
20070057051 Bortolin et al. Mar 2007 A1
20070083465 Ciurea et al. Apr 2007 A1
20070100691 Patterson May 2007 A1
20070125842 Antoo et al. Jun 2007 A1
20070194104 Fukuda Aug 2007 A1
20070203836 Dodin Aug 2007 A1
20070205270 Kemper et al. Sep 2007 A1
20070241189 Slavin et al. Oct 2007 A1
20070244811 Tumminaro Oct 2007 A1
20070250380 Mankoff Oct 2007 A1
20070276764 Mann Nov 2007 A1
20070288373 Wilkes Dec 2007 A1
20080003987 Mechaley Jan 2008 A1
20080006685 Rackley Jan 2008 A1
20080021784 Hessburg et al. Jan 2008 A1
20080040265 Rackley, III et al. Feb 2008 A1
20080041937 Vawter Feb 2008 A1
20080114657 Forzley May 2008 A1
20080120182 Arnold et al. May 2008 A1
20080126145 Rackley, III et al. May 2008 A1
20080133366 Evans et al. Jun 2008 A1
20080154727 Carlson Jun 2008 A1
20080154735 Carlson Jun 2008 A1
20080154772 Carlson Jun 2008 A1
20080167991 Carlson et al. Jul 2008 A1
20080183480 Carlson Jul 2008 A1
20080201226 Carlson Aug 2008 A1
20080208762 Arthur et al. Aug 2008 A1
20080300973 DeWitt et al. Dec 2008 A1
20080319843 Moser et al. Dec 2008 A1
20090076896 DeWitt et al. Mar 2009 A1
20090076925 DeWitt et al. Mar 2009 A1
20090078777 Granucci et al. Mar 2009 A1
20090081990 Granucci et al. Mar 2009 A1
20090094126 Killian et al. Apr 2009 A1
20090112721 Hammad et al. Apr 2009 A1
20090119170 Hammad et al. May 2009 A1
20090182634 Park et al. Jul 2009 A1
20090314840 Granucci et al. Dec 2009 A1
20090327134 Carlson et al. Dec 2009 A1
20090327151 Carlson et al. Dec 2009 A1
20100017275 Carlson et al. Jan 2010 A1
Foreign Referenced Citations (21)
Number Date Country
1652130 Aug 2005 CN
1 096 439 May 2001 EP
1 136 961 Sep 2001 EP
1 517 255 Mar 2005 EP
2 348 781 Nov 2003 GB
10-116306 May 1998 JP
2010116306 May 1998 JP
2000222498 Aug 2000 JP
2002183569 Jun 2002 JP
200322255 Jan 2003 JP
2003108777 Apr 2003 JP
2005122505 May 2005 JP
2006519448 Aug 2006 JP
WO 9613814 May 1996 WO
WO 9745814 Dec 1997 WO
WO 9951038 Jul 1999 WO
WO 0003328 Jan 2000 WO
WO 0077697 Dec 2000 WO
WO 2004077369 Sep 2004 WO
WO 2005052869 Jun 2005 WO
WO 2006024080 Mar 2006 WO
Non-Patent Literature Citations (47)
Entry
“Pervasive Computing Goes the Last Hundred Feet with RFID Systems”, Vince Stanford, 2003, pp. 1-6.
“Virtual Shopping: Straight Goods on Cyber-stores and Security.” Chatelaine; vol. 70, p. 24 (Feb. 1997).
About Us, 1 page downloaded from http://www.cellfire.com/about-us/ on May 10, 2007, 1 page.
bCode™ is the future of Mobile Coupon, Ticketing, Loyalty and Payments, 2 page product brochure downloaded from http://www.bcode.com on May 11, 2007, 2 pages.
bCode™ MediaHub 200 Mobile Coupon, Ticketing Loyalty and Payments, 2 page product brochure, from http://www.bcode.com/news—media.htm on May 11, 2007, 2 pages.
Cellfire—Mobile coupons for your cell phone, 1 page product brochure downloaded from http://www.cellfire.com on May 11, 2007, 1 page.
Cellfire, Coupons on Cellfire, 2 pages downloaded from http://www.cellfire.com/coupons on May 10, 2007, 2 pages.
International Preliminary Report on Patentability from International Application No. PCT/US2007/088289 dated Jun. 30, 2009.
International Preliminary Report on Patentability from International Application No. PCT/US2007/088313 dated Jun. 30, 2009.
International Preliminary Report on Patentability from International Application No. PCT/US2007/088563 dated Jun. 30, 2009.
International Preliminary Report on Patentability from International Application No. PCT/US2007/088659 dated Jun. 30, 2009.
International Preliminary Report on Patentability from International Application No. PCT/US2007/088687 dated Jun. 30, 2009.
International Search Report from International Application No. PCT/US2008/076761 dated Dec. 16, 2008.
International Search Report from International Application No. PCT/US2008/077688 dated Dec. 2, 2008.
Press Release, “Three months after California release, Cellfire™ reports redemption rates n times greater than paper coupons,” issued by Cellfire, Inc. Mar. 22, 2006; pp. 1-2 downloaded from http://www.cellfire.com/about-us/articles/2006-03-22—redemption-rate, 2 pages.
Purdy et al., “When Mobile Coupons Replace Paper Coupons, Everyone Wins,” pp. 1-17 published by Frost & Sullivan.[online]. info.cellfire.com, May 11, 2007, [Retrieved from the Internet: URL: http://info.cellfire.com/cellfire/themes/cellfire/downloads/When—Mobile—Coupons—Replace—Paper—Coupons.pdf], 17 pages.
“Adding value to SmarTrip is as easy as using it”, 1998-2004, WMATA, http://www.wmata.com/riding/smartrip—adding—value.cfm (1 page).
“SmarTrip More Than a Smart Card. It's Pure Genius”, 1998-2004, WMATA, http://www.wmata.com/riding/smartrip.cfm (2 pages).
International Preliminary Report on Patentability and Written Opinion from International Application No. PCT/US2007/088615, dated Jun. 10, 2008.
International Preliminary Report on Patentability from PCT/US2007/088563, dated Jul. 9, 2009.
International Search Report and Written Opinion from International Application No. PCT/US2007/088313, dated Jun. 30, 2008.
International Search Report and Written Opinion from PCT/US2007/088289, dated May 15, 2008.
International Search Report from International Application No. PCT/US2007/088615, dated May 27, 2008.
International Search Report from International Application No. PCT/US2007/088659, dated Jun. 26, 2008.
International Search Report from PCT/US2007/088563, dated May 20, 2008.
U.S. Appl. No. 11/749,366, Carlson.
U.S. Appl. No. 11/767,033, Carlson, et al.
U.S. Appl. No. 11/960,162, Carlson, et al.
U.S. Appl. No. 11/963,736, Carlson, et al.
U.S. Appl. No. 11/963,095, Carlson, et al.
U.S. Appl. No. 11/963,173, Carlson, et al.
Emmerson, Kassidy; “The History of PayPal: One of the Most Successful Online Money Transmitters Today”; 2009, http://www.associatedcontent.com/pop—print.shtrml?content—type=arti . . . , 1 page.
Kageyama, Yuri; “Japanese carrier unveils mobile-phone wallet”; http://usatoday:printthis.clickability.com/pt/cpt?action=apt&title=USATODAY.com+-+Jap . . . , 3 pages.
Korousic, Bojan et al.; “3rd Year Project Report EX-Ca$h: Feasibility Project”; 2003, Electronics Engineering Technology-Telecommunications Systems, Conestoga College, 33 pages.
Subramanian, Hemang C,; SIM Access Profile: Electronic currency using SIM Access Profile; 2003, http:/www-128.ibm.com/developerworks/wireless/library/wi-simacc/, 6 pages.
“Ubiquitous Commerce”; http://www.accenture.com/Global/Services/Accenture—Technology—Labs/R—and—l/Mobile . . . , 1 page.
“M Pay: Frequently Asked Questions”; http://www.m-pay.com/index.php?id=18, 3 pages.
“GSMVend Technical Manual”; http://www.bonusdata.net/IntusJunior/GSMVend/gsmvend.htm, 14 pages.
Examiner's First Report for Austrialian Patent Application No. 2007339930. 2 pages.
Japanese Office Action mailed Dec. 18, 2012 in JP Application No. 2009-544238 filed Dec. 13, 2012.
EP Search Opinion dated Jun. 13, 2012 for PCT/US2007/088704, Application No. 07869831.3. 7 pages.
Chinese Office Action mailed Apr. 27, 2013 in Chinese Application No. 200780050672.1.
International Search Report and Written Opinion mailed Jun. 11, 2008 for Int'l Application No. PCT/US2007/088704 filed Dec. 21, 2007, 9 pages.
First Office Action mailed Mar. 10, 2011 for CN Application No. 200780050672.1 filed Dec. 21, 2007, 13 pages.
Second Office Action mailed Feb. 2, 2012 for CN Application No. 200780050672.1 filed Dec. 21, 2007, 15 pages.
Third Office Action mailed Sep. 17, 2012 for CN Application No. 200780050672.1 filed Dec. 21, 2007, 16 pages.
Fifth Office Action mailed Jul. 26, 2013 in Chinese Patent Application No. 200780050672.1, 10 pages.
Related Publications (1)
Number Date Country
20080163257 A1 Jul 2008 US
Provisional Applications (1)
Number Date Country
60871898 Dec 2006 US