System and method for processing payment transaction receipts

Information

  • Patent Grant
  • 8650124
  • Patent Number
    8,650,124
  • Date Filed
    Monday, March 25, 2013
    11 years ago
  • Date Issued
    Tuesday, February 11, 2014
    10 years ago
  • Inventors
  • Original Assignees
  • Examiners
    • Havan; Thu Thao
    Agents
    • Kilpatrick Townsend & Stockton
Abstract
Embodiments of the invention are directed to systems and methods for processing payment transaction receipts. When an authorization request message for a transaction of a consumer is received, it is determined whether an account associated with the consumer's portable consumer device is enrolled in an electronic receipt program. If the account is enrolled, an electronic receipt for the transaction is sent to the consumer.
Description
BACKGROUND

The legacy process of transaction receipt generation at point-of-sale transactions involves generating a paper transaction receipt (e.g., charge-slip) and maintaining copies of the paper transaction receipt by both the consumer and the merchant. This existing process of paper-based transaction receipts has many issues associated with it. Such issues include the generation and safe-keep of paper transaction receipts by consumers and merchants, which is a major operational hassle. Additionally, the generation and safe-keep of paper transaction receipts involves extensive inventory management for paper, ink cartridges, and other consumables, which has cost and operational overhead. Furthermore, paper transaction receipts involve elaborate back-office setup at the merchant acquirer for retrieval and processing of transaction receipts in cases of disputes, which also has cost and operational overhead. Paper transaction receipts are also problematic in that frequent disputes arise due to erasure of contents on paper transaction receipts. These issues add substantial inefficiencies to the existing transaction process. Moreover, the emergence of new payment products and form factors warrants the need for new ways of managing transaction receipts that fit into the overall consumer experience.


Embodiments of the invention address these and other problems individually and collectively.


BRIEF SUMMARY

Embodiments of the invention are directed to systems and methods for processing payment transaction receipts.


One embodiment of the invention is directed to a method of sending electronic receipts to a consumer. The method includes receiving an authorization request message associated with a transaction, the authorization request message including transaction information associated with a portable consumer device of the consumer. A server computer associated with a payment processing network determines whether an account associated with the portable consumer device is enrolled in an electronic receipt program. An electronic receipt is sent to the consumer if the account is enrolled in the electronic receipt program. The electronic receipt has financial data associated with the transaction.


Another embodiment of the invention is directed to a server computer. The server computer includes an enrollment module having enrollment information associated with an account for a portable consumer device of a consumer. The enrollment information indicates enrollment in an electronic receipt program. The server computer also includes a payment processing module for receiving an authorization request message associated with a transaction of the portable consumer device. The authorization request message includes transaction information associated with the portable consumer device. The server computer further includes a mobile gateway module for sending an electronic receipt to the consumer if the enrollment information indicates the account is enrolled in the electronic receipt program. The electronic receipt has financial data associated with the transaction.


Yet another embodiment of the invention is directed to a method for receiving electronic receipts. The method includes sending an authorization request message associated with a transaction to a server computer associated with a payment processing network. The authorization request message includes transaction information associated with a portable consumer device of a consumer. The customer then receives an electronic receipt having financial data associated with the transaction if an account associated with the portable consumer device is enrolled in an electronic receipt program. The server computer determines whether the account is enrolled in the electronic receipt program.


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





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 depicts a system for generating paper receipts to the consumer.



FIG. 2(
a) and FIG. 2(b) depict various portable consumer devices.



FIG. 3 depicts a sample receipt.



FIG. 4 is a flowchart for a method of generating a paper receipt associated with a transaction of the consumer.



FIG. 5(
a) and FIG. 5(b) depict various systems for generating electronic receipts to the consumer.



FIG. 6 depicts an exemplary payment processing network for generating electronic receipts to the consumer.



FIG. 7 is a flowchart for a method of generating an electronic receipt associated with a transaction of the consumer.



FIG. 8 depicts an exemplary format for indicating enrollment in an electronic receipt program.



FIG. 9 depicts a block diagram of an exemplary computer apparatus.





DETAILED DESCRIPTION

Embodiments of the invention involve replacing the legacy process of transaction receipt (e.g. charge-slip) generation with a digital/electronic transaction receipt or equivalent record that is easier to safe-keep and that saves overall costs, such as processing and handling costs, in the process. Digitization of the transaction receipt generation and storage process solves many problems associated with the legacy process because the receipt would exist in electronic form and could be stored and sent over various electronic media. This process not only addresses the problems described above but also delivers an environmentally-friendly alternative to the existing model. Further, by providing receipts, the consumer can be notified of the transaction shortly after the transaction has taken place. This allows the consumer to take immediate action in the event that a transaction is potentially fraudulent or in the event that the transaction details are not accurate (e.g., the price on the receipt does not reflect the price that was intended to be paid).


Such embodiments for electronic receipts are also advantageous due to the increased deployment of personal identification numbers (PIN) and electromagnetic vulnerability (EMV) chip-based transactions that obviate the need for a consumer's signature on transaction receipts.


Transaction receipts are universally used in merchant and self-service terminals (e.g., ATMs) as a proof of transaction. A transaction receipt contains a record of a transaction and information including a card number, amount, date, merchant details, etc. In most cases, the merchant also provides a separate receipt with similar details and additionally a breakup of merchandise. Most transactions require multiple copies to be printed for safekeeping at the merchant, consumer, and the acquirer bank. This is largely a legacy of old imprint based card-transactions.


There are many issues with the existing paper transaction receipt system. Generation and safe-keeping of transaction receipts by a consumer and merchant are a major operational hassle. Extensive inventory management and servicing setup for paper, ink-cartridges, etc. is required for generating transaction receipt from a card terminal at a merchant. An elaborate back-office setup is required at the merchant/bank for retrieval and processing of transaction receipts in case of disputes. Frequent conflicts arise due to poor print quality and erasure of print which is an inherent drawback of the small printer used in terminals. Moreover, the existing paper system is environmentally unfriendly.


Embodiments of the invention essentially replace the paper-based credit card transaction receipt process with a more efficient electronic process. This is achieved through converting transaction receipts to an electronic format for easy storage and access, moving the task of generation of receipts away from the access device (i.e. point-of-sale terminal) at the merchant, moving unique information from the credit card receipt to other supplementary documentation used in the transaction, and providing consumers options to access receipts over multiple channels. With these embodiments, little or even no change is required from the merchant's end.


Based on various environmental factors, embodiments of the invention could take various manifestations. Examples of these are described below.



FIG. 1 shows the existing system and process for generating paper transaction receipts. The system of FIG. 1 includes portable consumer device 102, access device 104, acquirer 108, payment processing network 110, issuer 112, and receipt 120. FIG. 1 also depicts the interaction between these elements.


In a typical payment transaction, a consumer may purchase goods or services at the merchant using portable consumer device 102. The consumer may be an individual, or an organization such as a business that is capable of purchasing goods or services. Additionally, the consumer may operate a client computer to transact with the merchant. The client computer can be a desktop computer, a laptop computer, a wireless phone, a personal digital assistant (PDA), etc. The client computer may operate using any suitable operating system including a Windows™ based operating system. The client computer may be used to interact with a merchant (e.g., via merchant access device 104 or via a merchant website).


The payment transaction is initiated when the consumer uses portable consumer device 102 at access device 104, which is located at the merchant. Acquirer 108, which is a financial institution associated with the merchant, can receive the transaction information from access device 104 at the merchant. Acquirer 108 forwards the transaction information to payment processing network 110, which then forwards the transaction information to issuer 112 for approval of the transaction. Issuer 112 is a financial institution associated with portable consumer device 102. The approval (or denial) of the transaction is ultimately sent back to access device 104 for completion of the transaction.


Portable consumer device 102 is a payment device that may be in any suitable form. For example, portable consumer device 102 can be hand-held and compact so that it fits into a consumer's wallet and/or pocket (e.g., pocket-sized). Portable consumer device 102 may also be a smart card, ordinary credit or debit card (with a magnetic strip and without a microprocessor), a keychain device (such as the Speedpass™ commercially available form Exxon-Mobil Corp.), etc. Other examples of portable consumer devices include cellular phones, PDAs, pagers, payment cards, security cards, access cards, smart media, transponders, and the like. Portable consumer device 102 can also be a debit device (e.g., a debit card), credit device (e.g., a credit card), or stored value device (e.g., a stored value card). Portable consumer device 102 could also be in the form of a virtual account.



FIG. 2(
a) depicts an example of portable consumer device 102′ in the form of a mobile phone. Computer readable medium 206 may be a memory that stores data and may be in any suitable form including a magnetic stripe, a memory chip, uniquely derived keys, encryption algorithms, etc. Computer readable medium 206 also preferably stores information such as financial information, transit information (e.g., as in a subway or train pass), access information (e.g., as in access badges), etc. Financial information may include information such as bank account information, bank identification number (BIN), credit or debit card number information, account balance information, expiration date, consumer information such as name, date of birth, etc. Any of this information may be transmitted by portable consumer device 102′.


Information in the memory may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder's name as well as account number and other discretionary data. This track is sometimes used by the airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently most commonly used. This is the track that is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of this track and all world banks must abide by it. It contains the cardholder's account, encrypted PIN, plus other discretionary data.


Contactless element 214 is capable of transferring and receiving data using a near field communications (“NFC”) capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Near field communications capability is a short-range communications capability, such as RFID, Bluetooth™, infra-red, or other data transfer capability that can be used to exchange data between portable consumer device 102′ and an interrogation device. Thus, portable consumer device 102′ is capable of communicating and transferring data and/or control instructions via both cellular network and near field communications capability.


Portable consumer device 102′ may also include processor 208 (e.g., a microprocessor) for processing the functions of portable consumer device 102′ and display 210 to allow a consumer to see phone numbers and other information and messages. Portable consumer device 102′ may further include input elements 212 to allow a consumer to input information into the device, speaker 216 to allow the consumer to hear voice communication, music, etc., and microphone 204 to allow the consumer to transmit her voice through portable consumer device 102′. Portable consumer device 102′ may also include an antenna 202 for wireless data transfer (e.g., data transmission).


If portable consumer device 102 is in the form of a debit, credit, or smartcard, portable consumer device 102 may also optionally have features such as magnetic stripes. Such devices can operate in either a contact or contactless mode.



FIG. 2(
b) depicts an example of portable consumer device 102″ in the form of a payment card within a plastic substrate. A contactless element 224 for interfacing with access device 104 may be present on or embedded within the plastic substrate of 102″. Consumer information 220 such as an account number, expiration date, and consumer name may be printed or embossed on the card. Also, magnetic stripe 222 may also be on the plastic substrate of payment card 102″.


As shown in FIG. 2(b), the portable consumer device 102″ may include both a magnetic stripe 222 and a contactless element 224. In other embodiments, both the magnetic stripe 222 and the contactless element 224 may be in portable consumer device 102″. In other embodiments, either the magnetic stripe 222 or the contactless element 224 may be present in the portable consumer device 102″.


Access device 104 is a device used to transmit transaction information from the merchant to acquirer 108. The merchant may be an individual or an organization such as a business that is capable of providing goods and services. The merchant's access device 108 can be any suitable access device with interfaces, including point of sale (POS) devices, cellular phones, PDAs, personal computers (PCs), tablet PCs, handheld specialized readers, set-top boxes, electronic cash registers (ECR), automated teller machines (ATM), virtual cash registers (VCR), kiosks, security systems, access systems, and the like. Access device 104 can interact with portable consumer device 102. For example, a consumer using a credit card to purchase a good or service can swipe it through an appropriate slot in access device 104. Alternatively, access device 104 may be a contactless reader, and portable consumer device 102 may be a contactless device such as a contactless card. As another alternative, a consumer may purchase a good or service via a merchant's website where the consumer enters the credit card information into the client computer and clicks on a button to complete the purchase. Additionally, the client computer may be considered an access device 104.


Acquirer 108 may be in operative communication with the issuer 112 of portable consumer device 102 via payment processing network 110. Acquirer 108 is typically a bank that has a merchant account. Issuer 112 may also be a bank, but could also be a business entity such as a retail store or a mobile phone or telecommunications company. Issuer 112 is the entity issuing portable consumer device 102 to the consumer. Some entities are both acquirers and issuers, and embodiments of the invention include such entities. Acquirer 108 and issuer 112 may each have a server computer and a database associated with the server computer.


Payment processing network 110 is located between (in an operational sense) acquirer 108 and the issuer 112. It may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. For example, payment processing network 110 may include VisaNet™. Payment processing networks such as 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 110 may use any suitable wired or wireless network, including the Internet. Payment processing network 110 may have a server computer and a database associated with the server computer. The server computer may comprise a processor and a computer readable medium. The computer readable medium may comprise code or instructions for performing methods according to embodiments of the invention.


The process for conducting a transaction and generating paper transaction receipt 120 for the consumer, as depicted in FIG. 1, is as follows:

    • Step 1: The consumer offers portable consumer device 102 towards settling dues for a transaction at a merchant.
    • Step 2: The merchant processes the transaction with portable consumer device 102 using access device 104 and submits the transaction to acquirer 108 by sending an authorization request message to acquirer 104.
    • Step 3: Acquirer 108 forwards the authorization request message to payment processing network 110.
    • Step 4: Payment processing network 110 processes the authorization request message and sends it to issuer 112.
    • Step 5: Issuer 112 receives the authorization request message and approves the transaction appropriately by forwarding an authorization response message to payment processing network 110.
    • Step 6: Payment processing network 110 receives the authorization response message and forwards it to acquirer 108.
    • Step 7: Acquirer 108 forwards the authorization response message to access device 104 at the merchant.
    • Step 8: Access device 104 at the merchant receives the authorization response message indicating approval of the transaction at access device 104 and generates multiple copies of transaction receipt 120.


Based on the transaction environment, the consumer may be required to sign the merchant copy of transaction receipt 120. However, in some embodiments, a signature may not be a requirement for PIN and certain EMV chip transactions. FIG. 3 depicts an example of transaction receipt 120.



FIG. 4 depicts a flow chart of a method for generating paper transaction receipts. When a consumer initiates a payment transaction for the purchase of goods or services from a merchant, the transaction information will be received by the merchant via access device 104 (step S402). Access device 104 generates an authorization request message containing the transaction details, including payment information associated with portable consumer device 102, and sends the authorization request message to acquirer 108 (step S404). The authorization request message is then sent from acquirer 108 to payment processing network 110 where it is received (S406). Payment processing network 110 forwards the authorization request message to issuer 112. Issuer 112 determines whether the transaction should be approved and sends an authorization response message indicating approval or denial to payment processing network 110 where it is received (S408). Payment processing network 110 then sends authorization response message to the merchant access device 104 via acquirer 108 (S410). Once the authorization response message is received at the merchant, access device 104 prints a transaction receipt for the consumer to sign (S412). Access device 104 also prints a transaction receipt for the consumer to retain for the consumer's personal records (S414).



FIGS. 5(
a) and 5(b) depict systems for generating electronic receipts. In one embodiment of the present invention, payment processing network 110 (or other suitable entity, such as issuer 112) creates a mobile-gateway to generate and send electronic transaction receipts as messages to registered or enrolled consumers. The consumer may enroll to receive transaction receipts in electronic form. The enrollment can be performed by the consumer in any suitable manner, such as a phone call to an enrollment center, through portable consumer device 102, through email, through a website for enrolling in the electronic receipt program, etc. Furthermore, the consumer can indicate whether the consumer wishes to stop receiving paper transaction receipts after a transaction or whether the consumer wishes to receive both the paper transaction receipt and the electronic transaction receipt. Additionally, the consumer can indicate how the consumer wishes to receive the electronic receipt (e.g. by email, text message, etc.).



FIG. 5(
a) shows a system in accordance with an embodiment of the invention. The components (portable consumer device 102, access device 104, acquirer 108, payment processing network 110, issuer 112) are similar to those shown in FIG. 1. The process for generating an electronic receipt to user device 114 is described below. Note that user device 114 can be any device used by the consumer that is capable of receiving an electronic receipt, including but not limited to a mobile phone, PDA, pager, computer, etc.

    • Step 11: The consumer offers portable consumer device 102 towards settling dues for a transaction at a merchant.
    • Step 12: The merchant processes the transaction with portable consumer device 102 using access device 104 and submits the transaction to acquirer 108 by sending an authorization request message to acquirer 104.
    • Step 13: Acquirer 108 forwards the authorization request message to payment processing network 110.
    • Step 14: Payment processing network 110 processes the authorization request message, including determining whether the account associated with portable consumer device 102 is enrolled in an electronic receipt program. Payment processing network 110 sends the authorization request message to issuer 112.
    • Step 15: Issuer 112 receives the authorization request message and approves the transaction appropriately by forwarding an authorization response message to payment processing network 110.
    • Step 16: Payment processing network 110 receives the authorization response message and forwards it to acquirer 108.
    • Step 17: Acquirer 108 forwards the authorization response message to access device 104 at the merchant.
    • Step 18: Payment processing network 110 sends an electronic receipt to user device 114 if payment processing network 110 determines that the account associated with the consumer's portable consumer device 102 is enrolled in the electronic receipt program.


There are a number of advantages to allowing the payment processing network 110 (or a server computer located therein) to send the electronic receipt to the user device 114 after the authorization response message is received from the issuer 112. The payment processing network 110 can act as a “switch” between many different issuers and acquirers (not shown). Thus, a single modification to the payment system shown in FIG. 5 can provide transaction receipts to many different merchants associated with many different acquirers when transactions are made using many different portable consumer devices issued from many different issuers.


In step 18, the electronic receipt can be sent in any form suitable for user device 114. For example, the electronic receipt can be a short message service (SMS) message, a multi-media service (MMS) message (e.g. an image of receipt), an email, etc. It is important to note that the trigger for the electronic receipt could be completion of the online transaction successfully over payment processing network 110, indication of successful completion of transaction by acquirer 108, or at any other suitable point during the transaction. It is also important to note that user device 114 might also be the same device as portable consumer device 102.


The electronic receipt may include any or all of the data elements that are on a paper receipt (such as in FIG. 3). For example, the electronic receipt may include one or more of the following (e.g., at least a combination of 4, 5, 6 or more): a merchant identifier, a store identifier, a cashier identifier, a transaction date, a subtotal for the transaction, a sales tax amount, a total amount, a masked or partially masked payment card account number, a masked expiration date, an approval code, a date of transaction, a time of transaction, and a total payment amount. The transaction receipts may also have, in some cases, digital signatures from either a payment processor, or issuer, to verify its authenticity. That is, the electronic receipts may be used in place of paper receipts (or in addition to them) so the actual electronic receipt must be verifiable as being authentic.


Transaction receipts can also be distinguishable from transaction alerts. Transaction alerts are typically sent as a supplement to paper receipts. Also, transaction alerts typically do not include the same level of detail as transaction receipts, and are not used as proof that a transaction has occurred. Further, the electronic receipts can be used as proof that a transaction occurred, and can be used to return goods to a merchant or get a refund for goods or services.



FIG. 5(
b) shows another embodiment of the system for generating electronic receipts. In this embodiment, payment processing network 110 (or issuer 112 in some embodiments) provides consumer access to electronic transaction receipts over an Internet portal. In other embodiments, the electronic transaction receipt can be sent as an email. Payment processing network 110 (or issuer 112) provides consumer access to electronic transaction receipts over an online portal by maintaining, for example, a website for accessing the consumer's online account associated with portable consumer device 102. The consumer may subscribe to the service. The process for generating and sending electronic receipts in this embodiment is as follows:

    • Step 21: The consumer offers portable consumer device 102 towards settling dues for a transaction at a merchant.
    • Step 22: The merchant processes the transaction with portable consumer device 102 using access device 104 and submits the transaction to acquirer 108 by sending an authorization request message to acquirer 104.
    • Step 23: Acquirer 108 forwards the authorization request message to payment processing network 110.
    • Step 24: Payment processing network 110 processes the authorization request message, including determining whether the account associated with portable consumer device 102 is enrolled in an electronic receipt program. Payment processing network 110 sends the authorization request message to issuer 112.
    • Step 25: Issuer 112 receives the authorization request message and approves the transaction appropriately by forwarding an authorization response message to payment processing network 110.
    • Step 26: Payment processing network 110 receives the authorization response message and forwards it to acquirer 108.
    • Step 27: Acquirer 108 forwards the authorization response message to access device 104 at the merchant.
    • Step 28: Payment processing network 110 sends an electronic receipt to the user account 150 if payment processing network 110 determines that the account associated with the consumer's portable consumer device 102 is enrolled in the electronic receipt program.


In step 28, electronic receipts are available to the consumer's online user account 150 over an internet portal. If the electronic receipt program is being offered by issuer 112, this could be a part of the consumer's regular online account access. It could alternately be sent to a consumer as an email.


In another embodiment of the present invention a merchant copy of the transaction receipt continues in paper form while the consumer copy is sent in electronic form. Legal reasons may make it necessary for the merchant to retain a signed paper copy of a consumer transaction receipt. The consumer may register or enroll to receive transaction receipts in electronic form. The merchant copy of the transaction receipt continues to be printed, however the consumer copy is processed in electronic form.



FIG. 6 depicts an example of payment processing network 110 in accordance with an embodiment of the invention. Payment processing network 110 includes a server computer 300 capable of accessing database 310. Server computer 300 also includes a processor for processing any computer-readable instructions stored on computer-readable media. Server computer 300 contains enrollment module 302, mobile gateway module 304, and payment processing module 306, each of which contains computer-readable instructions stored on computer-readable media for performing at least the functions described below. It should be noted that in other embodiments, the functionality of enrollment module 302, mobile gateway module 304, and payment processing module 306 can reside at issuer 112 or at any other suitable entity.


Enrollment module 306 may enroll a consumer in the electronic receipt program. As described above, enrollment can occur in any suitable manner, such as through a phone call, email, text, online enrollment, etc. That is, a consumer may request enrollment through any suitable means. Once a consumer is enrolled using enrollment module 306, the enrollment information may be sent and stored in database 310. The enrollment information can be subsequently accessed from database 310 during a consumer's transaction in order to determine whether the consumer is enrolled in the electronic receipt program. Enrollment module 306 uses the authorization request message or the authorization response message to look up an account and determine whether the account is enrolled in the electronic receipt program.


Mobile gateway module 304 may be used to provide the electronic receipt to the consumer, whether it is to the consumer's user device 114 or the online user account 150. Mobile gateway module 304 may be used in any suitable manner to notify the consumer that an electronic receipt is ready to be accessed.


Payment processing module 306 is the module that performs a typical payment transaction process. This module receives the authorization request message from acquirer 108, sends the authorization request message to issuer 112 for approval, receives the authorization response message from issuer 112, and sends the authorization response message to acquirer 108.



FIG. 7 depicts a flowchart of a method for generating electronic receipts in accordance with an embodiment of the invention. The merchant receives the transaction information at the merchant's access device 104. As discussed in detail above, the transaction information is received from the consumer's portable consumer device 102 and includes information such as the consumer's account information and purchase details (S502). Access device 104 generates an authorization request message with the transaction information and sends the authorization request message to acquirer 108 (S504). Acquirer then sends the authorization request message to payment processing network 110, where it is received (S506). The authorization request message is then forwarded to issuer 112, and issuer 112 generates an authorization response message indicating whether the transaction is authorized (i.e. whether there are sufficient funds in the consumer's account). Payment processing network 110 receives the authorization response message from issuer 112, including receiving transaction information associated with portable consumer device 102 (S508). Payment processing network 110 then determines (using either the authorization request message or authorization response message) whether the consumer's account is enrolled in the electronic receipt program by accessing the stored enrollment information in database 310 (S510). If the consumer's account is not enrolled in the electronic receipt program, a normal authorization response message is sent to the merchant via acquirer 108 and access device 104 (S512). A paper receipt is then printed by access device 104 for the consumer to sign (S514). Additionally, a paper receipt is printed for the consumer to retain for the consumer's personal records (S516).


If the consumer's account is enrolled in the electronic receipt program, payment processing network 110 will modify the authorization response message received from issuer 112 and send the modified authorization response message to the merchant via acquirer 108 and access device 104 (S518). The authorization response message received from issuer 112 is modified to include an indicator indicating enrollment in the electronic receipt program. Access device 104 can use this indicator to determine that a paper receipt should not be printed for the consumer. An electronic receipt is subsequently sent to the consumer via the consumer's user device 114 or user account 150 (S520).



FIG. 8 depicts one embodiment of a format for indicating the consumer's enrollment in the electronic receipt program in the authorization response message. This data can include the authorization response message received from issuer 112, including a primary account number (PAN), expiration date, service code, PIN verification, CVV data, and any additional discretionary data, such as whether the transaction is authorized. The original authorization response message can be modified to include or add an indicator, which indicates whether the account associated with portable consumer device 102 is enrolled in the electronic receipt program. Additionally, the original authorization response message can be modified to include or add any other enrollment information by modifying the additional discretionary data portion of the message. For example, the modification can indicate that the consumer also wants a printed receipt at the merchant or that a printed receipt should not be given.


The various participants (e.g., access device 104, merchant, acquirer 108, payment processing network 110, and issuer 112) and elements in FIGS. 1, 2(a), 2(b), 5(a), 5(b), and 6 may operate one or more computer apparatuses to facilitate the functions described herein. Any of those elements may use any suitable number of subsystems to facilitate the functions described herein. Examples of such subsystems or components are shown in FIG. 9. The subsystems shown in FIG. 9 are interconnected via a system bus 775. Additional subsystems such as a printer 774, keyboard 778, fixed disk 779 (or other memory comprising computer readable media), monitor 776, which is coupled to display adapter 782, and others are shown. Peripherals and input/output (I/O) devices, which couple to I/O controller 771, can be connected to the computer system by any number of means known in the art, such as serial port 777. For example, serial port 777 or external interface 781 can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner. The interconnection via system bus 775 allows the central processor 773 to communicate with each subsystem and to control the execution of instructions from system memory 772 or the fixed disk 779, as well as the exchange of information between subsystems. The system memory 772 and/or the fixed disk 779 may embody a computer readable medium.


It should be understood that the present invention 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 invention 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.


The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. 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 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 invention.


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

Claims
  • 1. A method comprising: receiving, at a computer apparatus, account information associated with a portable consumer device of a consumer;sending an authorization request message associated with a transaction, the authorization request message including the account information associated with the portable consumer device of the consumer;receiving an authorization response message from a server computer that includes an indicator that an account associated with the portable consumer device is enrolled in an electronic receipt program and indicates whether or not the consumer wants a printed receipt at the merchant, based on a determination using the authorization request message that the account associated with the portable consumer device is enrolled in an electronic receipt program; anddetermining, based on the indicator in the authorization response message, that a paper receipt should not be printed for the consumer, wherein an electronic receipt having financial data associated with the transaction is sent to the consumer.
  • 2. The method of claim 1 wherein the portable consumer device is in the form of a virtual account.
  • 3. The method of claim 1 wherein electronic receipt having financial data associated with the transaction is sent to the consumer via the portable consumer device.
  • 4. The method of claim 1 wherein the electronic receipt includes at least one of the following data elements: a merchant identifier, a store identifier, a cashier identifier, a transaction date, a subtotal for the transaction, a sales tax amount, a total amount, a masked payment card account number, a masked expiration data, an approval code, a time of the transaction, and a total payment amount.
  • 5. The method of claim 1 wherein the electronic receipt comprises a digital signature.
  • 6. A computer apparatus comprising: a processor; anda computer readable medium coupled with the processor, the computer readable medium comprising code to be executed by a processor to perform the method of claim 1.
  • 7. A method comprising: conducting a transaction using a portable consumer device wherein account information associated with the portable consumer device is received by a computer and an authorization request message associated with the transaction is sent that includes the account information associated with the portable consumer device of the consumer, and an authorization response message is received from a server computer that includes an indicator that an account associated with the portable consumer device is enrolled in an electronic receipt program and indicates whether or not the consumer wants a printed receipt at the merchant, based on a determination using the authorization request message that the account associated with the portable consumer device is enrolled in an electronic receipt program;receiving, at a computer apparatus, an electronic receipt having financial data associated with the transaction, based on the indicator in the authorization response message that the account associated with the portable consumer device is enrolled in an electronic receipt program that indicates whether or not the consumer wants a printed receipt at the merchant, based on a determination using the authorization request message that an account associated with the portable consumer device is enrolled in an electronic receipt program.
  • 8. The method of claim 7 further comprising: requesting enrollment in an electronic receipt program to receive transaction receipts in electronic form indicating whether or not the consumer wants a printed receipt at the merchant.
  • 9. The method of claim 7 wherein the electronic receipt comprises a digital signature.
  • 10. The method of claim 7 wherein the portable consumer device is in the form of a virtual account.
  • 11. The method of claim 7 wherein the computer apparatus is the portable consumer device.
  • 12. The method of claim 7 wherein the computer apparatus is a mobile phone, PDA, pager, or computer.
  • 13. A computer readable medium comprising code to be executed by a processor to perform the method of claim 7.
  • 14. A method comprising: receiving at a server computer associated with a payment processing network, an authorization request message associated with a transaction, the authorization request message including transaction information associated with a portable consumer device in the form of a virtual account of the consumer;determining by the server computer associated with the payment processing network, using the authorization request message, whether the virtual account of the consumer is enrolled in an electronic receipt program; andsending, by the server computer associated with the payment processing network, an electronic receipt to the consumer based on determining that the virtual account of the consumer is enrolled in the electronic receipt program, the electronic receipt having financial data associated with the transaction.
  • 15. The method of claim 14, further comprising: receiving an authorization response message from an issuer in response to the authorization request message; andgenerating a modified authorization response message by adding an indicator to the authorization response message based on determining that the virtual account of the consumer is enrolled in the electronic receipt program, wherein the indicator indicates the consumer is enrolled in the electronic receipt program.
  • 16. The method of claim 14, further comprising: sending the authorization response message with the indicator to a merchant facilitating the transaction, wherein the indicator indicates whether the merchant should provide a paper receipt to the consumer.
  • 17. The method of claim 14, further comprising: receiving from the consumer a request to enroll in the electronic receipt program; andenrolling the consumer in the electronic receipt program.
  • 18. The method of claim 14, further comprising: maintaining a website for accessing an online account associated with the portable consumer device; andsending the electronic receipt to the consumer via the online account.
  • 19. The method of claim 14, wherein the electronic receipt is sent to a mobile phone associated with the consumer.
  • 20. The method of claim 14 wherein the electronic receipt comprises a digital signature.
  • 21. A server computer comprising: a processor; anda computer readable medium coupled with the processor, the computer readable medium comprising code to be executed by a processor to perform the method of claim 14.
CROSS-REFERENCES TO RELATED APPLICATIONS

The present application is a continuation of non-provisional application U.S. Ser. No. 12/962,571, filed on Dec. 7, 2010, now U.S. Pat. No. 8,429,048 entitled “System and Method for Processing Payment of Transaction Receipts”, which is a non-provisional of and claims priority to U.S. provisional Application No. 61/290,391, filed on Dec. 28, 2009, the entire contents of which are herein incorporated by reference for all purposes in their entirety.

US Referenced Citations (373)
Number Name Date Kind
3935933 Tanaka et al. Feb 1976 A
4011433 Tateisi et al. Mar 1977 A
4108350 Forbes, Jr. Aug 1978 A
4114027 Slater et al. Sep 1978 A
4124109 Bissell et al. Nov 1978 A
4195864 Morton et al. Apr 1980 A
4412631 Haker Nov 1983 A
4544590 Egan Oct 1985 A
4568403 Egan Feb 1986 A
4649515 Thompson et al. Mar 1987 A
4674041 Lemon et al. Jun 1987 A
4723212 Mindrum et al. Feb 1988 A
4742215 Daughters et al. May 1988 A
4794530 Yukiura et al. Dec 1988 A
4825053 Caille Apr 1989 A
4837422 Dethloff et al. Jun 1989 A
4841712 Roou Jun 1989 A
4868376 Lessin et al. Sep 1989 A
4882675 Nichtberger et al. Nov 1989 A
4910672 Off et al. Mar 1990 A
4930129 Takahira May 1990 A
4941090 McCarthy Jul 1990 A
4949256 Humble Aug 1990 A
4954003 Shea Sep 1990 A
4970658 Durbin et al. Nov 1990 A
4985615 Iijima Jan 1991 A
4992940 Dworkin Feb 1991 A
5019452 Watanabe et al. May 1991 A
5019695 Itako May 1991 A
5025372 Burton et al. Jun 1991 A
5056019 Schultz et al. Oct 1991 A
5060793 Hyun et al. Oct 1991 A
5060804 Beales et al. Oct 1991 A
5063596 Dyke Nov 1991 A
5115888 Schneider May 1992 A
5117355 McCarthy May 1992 A
5128752 Von Kohorn Jul 1992 A
5161256 Iijima Nov 1992 A
5173851 Off et al. Dec 1992 A
5185695 Pruchnicki Feb 1993 A
5200889 Mori Apr 1993 A
5202826 McCarthy Apr 1993 A
5227874 Von Kohorn Jul 1993 A
5256863 Ferguson et al. Oct 1993 A
5285278 Holman Feb 1994 A
5287181 Holman Feb 1994 A
5287268 McCarthy Feb 1994 A
5299834 Kraige Apr 1994 A
5308120 Thompson May 1994 A
5353218 De Lapa et al. Oct 1994 A
5380991 Valencia et al. Jan 1995 A
RE34915 Nichtberger et al. Apr 1995 E
5402549 Forrest Apr 1995 A
5412756 Bauman et al. May 1995 A
5417458 Best et al. May 1995 A
5420606 Begum et al. May 1995 A
5450938 Rademacher Sep 1995 A
5466010 Spooner Nov 1995 A
5471669 Lidman Nov 1995 A
5473690 Grimonprez et al. Dec 1995 A
5483444 Heintzeman et al. Jan 1996 A
5484998 Bejnar et al. Jan 1996 A
5491326 Marceau et al. Feb 1996 A
5491838 Takahisa et al. Feb 1996 A
5500681 Jones Mar 1996 A
5501491 Thompson Mar 1996 A
5513102 Auriemma Apr 1996 A
5515270 Weinblatt May 1996 A
5530232 Taylor Jun 1996 A
5531482 Blank Jul 1996 A
5535118 Chumbley Jul 1996 A
5537314 Kanter Jul 1996 A
5559313 Claus et al. Sep 1996 A
5564073 Takahisa Oct 1996 A
5577266 Takahisa et al. Nov 1996 A
5577915 Feldman Nov 1996 A
5578808 Taylor Nov 1996 A
5579537 Takahisa Nov 1996 A
5590038 Pitroda Dec 1996 A
5594493 Nemirofsky Jan 1997 A
5612868 Off et al. Mar 1997 A
5621812 Deaton et al. Apr 1997 A
5642485 Deaton et al. Jun 1997 A
5644723 Deaton et al. Jul 1997 A
5649114 Deaton et al. Jul 1997 A
5649118 Carlisle et al. Jul 1997 A
5650209 Ramsburg et al. Jul 1997 A
5687322 Deaton et al. Nov 1997 A
5689100 Carrithers et al. Nov 1997 A
5710886 Christensen et al. Jan 1998 A
5727153 Powell Mar 1998 A
5734838 Robinson et al. Mar 1998 A
5739512 Tognazzini Apr 1998 A
5742845 Wagner Apr 1998 A
5754762 Kuo et al. May 1998 A
5761648 Golden et al. Jun 1998 A
5765141 Spector Jun 1998 A
5767896 Nemirofsky Jun 1998 A
5774870 Storey Jun 1998 A
5776287 Best et al. Jul 1998 A
5790677 Fox et al. Aug 1998 A
5791991 Small Aug 1998 A
5794210 Goldhaber et al. Aug 1998 A
5797126 Helbling et al. Aug 1998 A
5802519 De Jong Sep 1998 A
5804806 Haddad et al. Sep 1998 A
5806044 Powell Sep 1998 A
5806045 Biorge et al. Sep 1998 A
5815658 Kuriyama Sep 1998 A
5822735 De Lapa et al. Oct 1998 A
5822737 Ogram Oct 1998 A
5832457 O'Brien et al. Nov 1998 A
5844218 Kawan et al. Dec 1998 A
5845259 West et al. Dec 1998 A
5855007 Jovicic et al. Dec 1998 A
5857175 Day et al. Jan 1999 A
5859419 Wynn Jan 1999 A
RE36116 McCarthy Feb 1999 E
5865340 Alvern Feb 1999 A
5865470 Thompson Feb 1999 A
5868498 Martin Feb 1999 A
5878337 Joao et al. Mar 1999 A
5880769 Nemirofsky et al. Mar 1999 A
5884271 Pitroda Mar 1999 A
5884277 Khosla Mar 1999 A
5884278 Powell Mar 1999 A
5887271 Powell Mar 1999 A
5890135 Powell Mar 1999 A
5892824 Beatson et al. Apr 1999 A
5892827 Beach et al. Apr 1999 A
5898838 Wagner Apr 1999 A
5899998 McGauley et al. May 1999 A
5903732 Reed et al. May 1999 A
5905246 Fajkowski May 1999 A
5905908 Wagner May 1999 A
5907350 Nemirofsky May 1999 A
5907830 Engel et al. May 1999 A
5909486 Walker et al. Jun 1999 A
5912453 Gungl et al. Jun 1999 A
5915019 Ginter et al. Jun 1999 A
5915244 Jack et al. Jun 1999 A
5921686 Baird et al. Jul 1999 A
5923735 Swartz et al. Jul 1999 A
5923884 Peyret et al. Jul 1999 A
5924072 Havens Jul 1999 A
5926795 Williams Jul 1999 A
5928082 Clapper, Jr. Jul 1999 A
5931947 Burns et al. Aug 1999 A
5943651 Oosawa Aug 1999 A
5950173 Perkowski Sep 1999 A
5953047 Nemirofsky Sep 1999 A
5953705 Oneda Sep 1999 A
5956694 Powell Sep 1999 A
5956695 Carrithers et al. Sep 1999 A
5958174 Ramsburg et al. Sep 1999 A
5960082 Haenel Sep 1999 A
5963917 Ogram Oct 1999 A
5969318 Mackenthun Oct 1999 A
5970469 Scroggie et al. Oct 1999 A
5974399 Giuliani et al. Oct 1999 A
5974549 Golan Oct 1999 A
5978013 Jones et al. Nov 1999 A
5987795 Wilson Nov 1999 A
5997042 Blank Dec 1999 A
6000608 Dorf Dec 1999 A
6002771 Nielsen Dec 1999 A
6003113 Hoshino Dec 1999 A
6003134 Kuo et al. Dec 1999 A
6005942 Chan et al. Dec 1999 A
6009411 Kepecs Dec 1999 A
6012635 Shimada et al. Jan 2000 A
6014634 Scroggie et al. Jan 2000 A
6024286 Bradley et al. Feb 2000 A
6035280 Christensen Mar 2000 A
6038551 Barlow et al. Mar 2000 A
6041309 Laor Mar 2000 A
6047325 Jain et al. Apr 2000 A
6049778 Walker et al. Apr 2000 A
6052468 Hillhouse Apr 2000 A
6052690 De Jong Apr 2000 A
6052785 Lin et al. Apr 2000 A
6055509 Powell Apr 2000 A
6055573 Gardenswartz et al. Apr 2000 A
6061660 Eggleston et al. May 2000 A
6067526 Powell May 2000 A
6067529 Ray et al. May 2000 A
6070147 Harms et al. May 2000 A
6073238 Drupsteen Jun 2000 A
6076068 Delapa Jun 2000 A
6076069 Laor Jun 2000 A
6089611 Blank Jul 2000 A
6094656 De Jong Jul 2000 A
6101422 Furlong Aug 2000 A
6101477 Hohle et al. Aug 2000 A
6105002 Powell Aug 2000 A
6105865 Hardesty Aug 2000 A
6105873 Jeger Aug 2000 A
6112987 Lambert et al. Sep 2000 A
6112988 Powell Sep 2000 A
6119933 Wong et al. Sep 2000 A
6119945 Muller et al. Sep 2000 A
6122631 Berbec et al. Sep 2000 A
6129274 Suzuki Oct 2000 A
6135351 Shiobara et al. Oct 2000 A
6142369 Jonstromer Nov 2000 A
6144948 Walker et al. Nov 2000 A
6151586 Brown Nov 2000 A
6151587 Matthias Nov 2000 A
6154751 Ault et al. Nov 2000 A
6161870 Blank Dec 2000 A
6164549 Richards Dec 2000 A
6170061 Beser Jan 2001 B1
6173269 Solokl et al. Jan 2001 B1
6173891 Powell Jan 2001 B1
6179205 Sloan Jan 2001 B1
6179710 Sawyer et al. Jan 2001 B1
6182891 Furuhashi et al. Feb 2001 B1
6183017 Najor et al. Feb 2001 B1
6185541 Scroggie et al. Feb 2001 B1
6189100 Barr et al. Feb 2001 B1
6189878 Meese Feb 2001 B1
6195666 Schneck et al. Feb 2001 B1
6205435 Biffar Mar 2001 B1
6210276 Mullins Apr 2001 B1
6216014 Proust et al. Apr 2001 B1
6216204 Thiriet Apr 2001 B1
6220510 Everett et al. Apr 2001 B1
6222914 McMullin Apr 2001 B1
6230143 Simons et al. May 2001 B1
6237145 Narasimhan et al. May 2001 B1
6241287 Best et al. Jun 2001 B1
6243687 Powell Jun 2001 B1
6243688 Kalina Jun 2001 B1
6244958 Acres Jun 2001 B1
6246997 Cybul et al. Jun 2001 B1
6266647 Fernandez Jul 2001 B1
6267263 Emoff et al. Jul 2001 B1
6269158 Kim Jul 2001 B1
6279112 O'Toole, Jr. et al. Aug 2001 B1
6282516 Giuliani Aug 2001 B1
6292785 McEvoy et al. Sep 2001 B1
6292786 Deaton et al. Sep 2001 B1
6296191 Hamann et al. Oct 2001 B1
6299530 Hansted et al. Oct 2001 B1
6321208 Barnett et al. Nov 2001 B1
6325285 Baratelli Dec 2001 B1
6327576 Ogasawara Dec 2001 B1
6341353 Herman et al. Jan 2002 B1
6385723 Richards May 2002 B1
6390374 Carper et al. May 2002 B1
6394341 Makipaa et al. May 2002 B1
6397194 Houvener et al. May 2002 B1
6442571 Haff et al. Aug 2002 B1
6480935 Carper et al. Nov 2002 B1
6487540 Smith et al. Nov 2002 B1
6516996 Hippelainen Feb 2003 B1
6533168 Ching Mar 2003 B1
6543683 Hoffman Apr 2003 B2
6549773 Linden et al. Apr 2003 B1
6549912 Chen Apr 2003 B1
6561417 Gadd May 2003 B1
6612490 Herrendoerfer et al. Sep 2003 B1
6653940 Collura Nov 2003 B2
6681995 Sukeda et al. Jan 2004 B2
6689345 Lezer Feb 2004 B2
6772434 Godwin Aug 2004 B1
6898598 Himmel et al. May 2005 B2
6975856 Ogasawara Dec 2005 B2
7069240 Spero et al. Jun 2006 B2
7082415 Robinson et al. Jul 2006 B1
7088467 Voss et al. Aug 2006 B1
7318049 Iannacci Jan 2008 B2
7356541 Doughty Apr 2008 B1
7461780 Potts et al. Dec 2008 B2
7487912 Seifert et al. Feb 2009 B2
7552087 Schultz et al. Jun 2009 B2
7725369 Shiftan May 2010 B2
7748621 Gusler et al. Jul 2010 B2
7827077 Shiftan et al. Nov 2010 B2
8025216 Potts et al. Sep 2011 B2
8180682 Narayanaswami et al. May 2012 B2
8429048 Singh Apr 2013 B2
20010016835 Hansmann et al. Aug 2001 A1
20010029483 Schultz et al. Oct 2001 A1
20010037312 Gray et al. Nov 2001 A1
20020002468 Spagna et al. Jan 2002 A1
20020073025 Tanner et al. Jun 2002 A1
20020073043 Herman et al. Jun 2002 A1
20020073331 Candelore Jun 2002 A1
20020076051 Nii Jun 2002 A1
20020077974 Ortiz Jun 2002 A1
20020077992 Tobin Jun 2002 A1
20020087894 Foley et al. Jul 2002 A1
20020128878 Maritzen et al. Sep 2002 A1
20020138354 Seal et al. Sep 2002 A1
20020179704 Deaton Dec 2002 A1
20020188561 Schultz Dec 2002 A1
20030014372 Wheeler et al. Jan 2003 A1
20030055733 Marshall et al. Mar 2003 A1
20030055792 Kinoshita et al. Mar 2003 A1
20030093344 Sesek May 2003 A1
20030121969 Wankmueller Jul 2003 A1
20030126020 Smith et al. Jul 2003 A1
20030182204 Rhee Sep 2003 A1
20030187794 Irwin et al. Oct 2003 A1
20030233279 Shinzaki Dec 2003 A1
20040030601 Pond et al. Feb 2004 A1
20040064373 Shannon Apr 2004 A1
20040128243 Kavanagh et al. Jul 2004 A1
20040141661 Hanna et al. Jul 2004 A1
20040204078 Fare et al. Oct 2004 A1
20040220964 Shiftan et al. Nov 2004 A1
20040225567 Mitchell et al. Nov 2004 A1
20050010505 Darrell Jan 2005 A1
20050018670 Shigematsu et al. Jan 2005 A1
20050076110 Mathew et al. Apr 2005 A1
20050080726 Krajewski et al. Apr 2005 A1
20050165651 Mohan Jul 2005 A1
20050172033 Mathew et al. Aug 2005 A1
20050216354 Bam et al. Sep 2005 A1
20060004746 Angus et al. Jan 2006 A1
20060022033 Smets et al. Feb 2006 A1
20060253392 Davies Nov 2006 A1
20060261149 Raghavendra Tulluri Nov 2006 A1
20060273163 Gusler et al. Dec 2006 A1
20070055630 Gauthier et al. Mar 2007 A1
20070069013 Seifert et al. Mar 2007 A1
20070094154 Rau et al. Apr 2007 A1
20070100691 Patterson May 2007 A1
20070136211 Brown et al. Jun 2007 A1
20070205274 Bridges Sep 2007 A1
20070205275 Nicola et al. Sep 2007 A1
20070214049 Postrel Sep 2007 A1
20080040285 Wankmueller Feb 2008 A1
20080048022 Vawter Feb 2008 A1
20080059375 Abifaker Mar 2008 A1
20080207203 Arthur et al. Aug 2008 A1
20080208743 Arthur et al. Aug 2008 A1
20080208762 Arthur et al. Aug 2008 A1
20080208764 Diffenderffer Aug 2008 A1
20080313062 Williams et al. Dec 2008 A1
20090037281 Devlin et al. Feb 2009 A1
20090089194 Mathis et al. Apr 2009 A1
20090099961 Ogilvy Apr 2009 A1
20090106053 Walker et al. Apr 2009 A1
20090119278 Cross et al. May 2009 A1
20090140839 Bishop et al. Jun 2009 A1
20090248557 Reed et al. Oct 2009 A1
20090265252 Fletcher Oct 2009 A1
20090271211 Hammad et al. Oct 2009 A1
20090271263 Regmi et al. Oct 2009 A1
20090271265 Lay et al. Oct 2009 A1
20100082444 Lin et al. Apr 2010 A1
20100100434 Sock Apr 2010 A1
20100257066 Jones et al. Oct 2010 A1
20110106714 Junger May 2011 A1
20120011009 Lindsey et al. Jan 2012 A1
20120123943 Potts et al. May 2012 A1
20120160911 Smith et al. Jun 2012 A1
20120203605 Morgan et al. Aug 2012 A1
20120203646 Morgan et al. Aug 2012 A1
20120203672 Morgan et al. Aug 2012 A1
20120203695 Morgan et al. Aug 2012 A1
20120203697 Morgan et al. Aug 2012 A1
20120209749 Hammad et al. Aug 2012 A1
20120221446 Grigg et al. Aug 2012 A1
20120253852 Pourfallah et al. Oct 2012 A1
20120253915 Sock Oct 2012 A1
20120253958 Sock et al. Oct 2012 A1
20120271712 Katzin et al. Oct 2012 A1
20120278193 Groat et al. Nov 2012 A1
20120284130 Lewis et al. Nov 2012 A1
20120290422 Bhinder Nov 2012 A1
Foreign Referenced Citations (131)
Number Date Country
200039412 Dec 2000 AU
1002756 May 1991 BE
2293944 Aug 2000 CA
2267041 Sep 2000 CA
2684 434 Jan 2001 CA
2317138 Jan 2002 CA
19522527 Jan 1997 DE
19848712 Apr 2000 DE
19960978 Aug 2000 DE
10015103 Oct 2000 DE
203424 Dec 1986 EP
292248 Nov 1988 EP
475837 Mar 1992 EP
540095 May 1993 EP
658862 Jun 1995 EP
675614 Oct 1995 EP
682327 Nov 1995 EP
875841 Nov 1998 EP
936530 Aug 1999 EP
938050 Aug 1999 EP
938051 Aug 1999 EP
944007 Sep 1999 EP
949595 Oct 1999 EP
982692 Mar 2000 EP
984404 Mar 2000 EP
1085395 Mar 2001 EP
1102320 May 2001 EP
1111505 Jun 2001 EP
1113387 Jul 2001 EP
1113407 Jul 2001 EP
1168137 Jan 2002 EP
1233333 Aug 2002 EP
2772957 Jun 1999 FR
2793048 Nov 2000 FR
2794543 Dec 2000 FR
2796176 Jan 2001 FR
2804234 Jul 2001 FR
2331381 May 1999 GB
2343091 Apr 2000 GB
2351379 Dec 2000 GB
2355324 Apr 2001 GB
2000112864 Apr 2000 JP
2000181764 Jun 2000 JP
2001202484 Jul 2001 JP
2001236232 Aug 2001 JP
2008-140298 Jun 2008 JP
10-2000-0039297 May 2001 KR
2001-0044823 Jun 2001 KR
2001-0058742 Jul 2001 KR
2002-0021237 Mar 2002 KR
10-2002-0051488 Jun 2002 KR
10-0795142 Jan 2008 KR
9016126 Dec 1990 WO
9625724 Aug 1996 WO
9638945 Dec 1996 WO
9642109 Dec 1996 WO
9705582 Feb 1997 WO
9710562 Mar 1997 WO
9739424 Oct 1997 WO
9802834 Jan 1998 WO
9809257 Mar 1998 WO
9820465 May 1998 WO
9843169 Oct 1998 WO
9843212 Oct 1998 WO
9852153 Nov 1998 WO
9910824 Mar 1999 WO
9119846 Apr 1999 WO
9916030 Apr 1999 WO
9944172 Sep 1999 WO
9945507 Sep 1999 WO
9949415 Sep 1999 WO
9949426 Sep 1999 WO
0113572 Feb 2000 WO
0039714 Jul 2000 WO
0046665 Aug 2000 WO
0054507 Sep 2000 WO
0057315 Sep 2000 WO
0057613 Sep 2000 WO
0062265 Oct 2000 WO
0062472 Oct 2000 WO
0067185 Nov 2000 WO
0068797 Nov 2000 WO
0068902 Nov 2000 WO
0068903 Nov 2000 WO
0069183 Nov 2000 WO
0075775 Dec 2000 WO
0077750 Dec 2000 WO
0079411 Dec 2000 WO
0104851 Jan 2001 WO
0106341 Jan 2001 WO
0108087 Feb 2001 WO
0115397 Mar 2001 WO
0118633 Mar 2001 WO
0118746 Mar 2001 WO
0114995 Mar 2001 WO
0129672 Apr 2001 WO
0133390 May 2001 WO
0131535 May 2001 WO
0140908 Jun 2001 WO
0142887 Jun 2001 WO
0144900 Jun 2001 WO
0144949 Jun 2001 WO
0147176 Jun 2001 WO
0150229 Jul 2001 WO
0152575 Jul 2001 WO
0155955 Aug 2001 WO
0159563 Aug 2001 WO
0161620 Aug 2001 WO
0165545 Sep 2001 WO
0167694 Sep 2001 WO
0171648 Sep 2001 WO
0171679 Sep 2001 WO
0173530 Oct 2001 WO
0173533 Oct 2001 WO
0178020 Oct 2001 WO
0180563 Oct 2001 WO
0184377 Nov 2001 WO
0184474 Nov 2001 WO
0184512 Nov 2001 WO
0188705 Nov 2001 WO
0206948 Jan 2002 WO
0210962 Feb 2002 WO
0214991 Feb 2002 WO
0215037 Feb 2002 WO
0221315 Mar 2002 WO
0229577 Apr 2002 WO
02088895 Nov 2002 WO
2005086593 Sep 2005 WO
2006077281 Jul 2006 WO
2007038296 Apr 2007 WO
2007123856 Nov 2007 WO
Non-Patent Literature Citations (62)
Entry
“Internet Based Secure Transactions Using Encrypting Applets and CGI-Scripts Independent of Browser or Server Capabilities”; 1998; pp. 800-801; No. 410116; IBM Research Disclosure.
Anderson, Alan; “Reading Between the Lines”; Aug. 2000, Enterprise Systems Journal, vol. 15, No. 8, pp. 44.
Commerce unplugged: welcome to the world of wireless commerce. Canadian Grocer: Toronto, Jun. 2001. vol. 115, Issue 5, p. 38.
James G Xack; Electronic Project Documentation; AACE International Transaction, Morgantown 2002; PG CD61, 8 pages.
Kennedy, Kristen; “The Incredible Shrinking Form Factor”; 2002, CRN, vol. 996, pp. 46-50.
U.S. Provisional Appl. No. 61/467,710, filed May 2, 2003, 20 pages.
Office Action from U.S. Appl. No. 10/676,508, dated Apr. 16, 2008.
Office Action from U.S. Appl. No. 10/676,508, dated Sep. 26, 2008.
The International Search Report from Application No. PCT/US2008/076770, dated Nov. 18, 2008, 1 page.
The International Written Opinion from Application No. PCT/US2008/076770, dated Nov. 18, 2008, 4 pages.
Office Action from U.S. Appl. No. 10/676,508, dated Mar. 11, 2009.
Office Action from U.S. Appl. No. 12/359,251, dated May 1, 2009.
Office Action from U.S. Appl. No. 12/359,248, dated May 27, 2009.
Office Action from U.S. Appl. No. 12/359,244, dated May 28, 2009.
The International Search Report from Application No. PCT/US2009/046402, dated Jul. 23, 2009, 1 page.
The International Written Opinion from Application No. PCT/US2009/046402, dated Jul. 23, 2009, 5 pages.
Office Action from U.S. Appl. No. 10/676,508, dated Oct. 15, 2009.
U.S. Appl. No. 61/287,071, filed Dec. 16, 2009, 24 pages.
The International Search Report from Application No. PCT/US2009/041951, dated Dec. 17, 2009, 4 pages.
The International Written Opinion from Application No. PCT/US2009/041951, dated Dec. 17, 2009, 7 pages.
U.S. Appl. No. 61/290,391, filed Dec. 28, 2009, 19 pages.
Office Action from U.S. Appl. No. 12/359,248, dated Jan. 7, 2010.
Office Action from U.S. Appl. No. 12/359,244, dated Jan. 8, 2010.
Notice of Allowance from U.S. Appl. No. 12/359,251, dated Jan. 11, 2010.
U.S. Appl. No. 61/306,384, filed Feb. 19, 2010, 12 pages.
U.S. Appl. No. 61/323,235, filed Apr. 12, 2010, 19 pages.
U.S. Appl. No. 10/676,508, filed on Sep. 30, 2003.
Office Action from U.S. Appl. No. 12/359,244, dated Jun. 8, 2010.
Office Action from U.S. Appl. No. 12/359,248, dated Jun. 8, 2010.
Office Action from U.S. Appl. No. 12/359,248, dated Jan. 27, 2012.
Notice of Allowance from U.S. Appl. No. 10/676,508, dated Jun. 25, 2010.
U.S. Appl. No. 61/435,771, filed Jan. 24, 2011, 25 pages.
“Cryptomathic: Use your mobile phone to pay for your groceries and get cash from ATMs; Scandinavian partnership launches secure payment mechanism that turns mobile phones into mobile wallets.” M2 Presswire Feb. 19, 2002 ProQuest Newsstand, ProQuest. Web. Jan. 27, 2011.
Office Action from U.S. Appl. No. 12/359,248, dated Feb. 2, 2011.
Notice of Allowance from U.S. Appl. No. 12/359,244, dated Feb. 4, 2011.
U.S. Appl. No. 61/466,409, filed Mar. 22, 2011, 395 pages.
U.S. Appl. No. 61/467,890, filed Mar. 25, 2011, 79 pages.
U.S. Appl. No. 61/467,969, filed Mar. 25, 2011, 90 pages.
U.S. Appl. No. 61/471,092, filed Apr. 1, 2011, 83 pages.
U.S. Appl. No. 61/485,029, filed May 11, 2011, 20 pages.
The International Search Report for Application PCT/US2010/059299, dated Jun. 28, 2011, 5 pages.
The International Search Report for Application PCT/US2010/061462, dated Aug. 24, 2011, 5 pages.
The International Written Opinion for Application PCT/US2010/061462, dated Aug. 24, 2011, 5 pages.
U.S. Appl. No. 12/953,165, filed Nov. 23, 2010, Ayman A. Hammad, entitled: “Merchant Alerts Incorporating Receipt Data”, 86 pgs.
International Search Report dated Aug. 24, 2011 from International Patent Application No. PCT/US2010/061462, 2 pages.
International Preliminary Report on Patentability Issued in PCT/US2010/061462 on Jul. 12, 2012, 7 pages.
U.S. Appl. No. 13/470,026, filed May 11, 2012, Juliene Britt, entitled: “Electronic Receipt Manager Apparatuses, Methods and Systems”, 127 pages.
International Search Report and Written Opinion mailed on Sep. 21, 2012 corresponding to PCT/US12/37597.
International Search Report mailed on Nov. 1, 2005 for PCT Patent Application No. PCT/US2004/013850, 1 page.
Written Opinion of the International Searching Authority mailed on Nov. 1, 2005 for PCT Patent Application No. PCT/US2004/013850, 3 pages.
Final Office Action mailed on Jan. 8, 2010 for U.S. Appl. No. 12/359,244, filed Jan. 23, 2009, 14 pages.
Non-Final Office Action mailed on Mar. 19, 2012 for U.S. Appl. No. 12/886,441, filed Sep. 20, 2010, 12 pages.
Non-Final Office Action mailed on Jun. 21, 2012 for U.S. Appl. No. 12/359,896, filed Jan. 26, 2009, 8 pages.
Final Office Action mailed on Jan. 18, 2013 for U.S. Appl. No. 12/359,896, filed Jan. 26, 2009, 14 pages.
Notice of Allowance mailed on Aug. 31, 2012 for U.S. Appl. No. 12/886,441, filed Sep. 20, 2010, 7 pages.
Non-Final Office Action mailed on Jun. 8, 2010 for U.S. Appl. No. 12/359,248, filed Jan. 23, 2009, 14 pages.
Non-Final Office Action mailed on Jun. 21, 2011 for U.S. Appl. No. 12/359,248, filed Jan. 23, 2009, 12 pages.
U.S. Appl. No. 12/359,244, filed Jan. 23, 2009.
U.S. Appl. No. 12/359,248, filed Jan. 23, 2009.
U.S. Appl. No. 12/359,251, filed Jan. 23, 2009.
U.S. Appl. No. 12/359,896, filed Jan. 26, 2009.
Canadian Office Action issued in International Patent Application No. 2,785,040, dated Jul. 2, 2013, 3 pages.
Related Publications (1)
Number Date Country
20130218778 A1 Aug 2013 US
Provisional Applications (1)
Number Date Country
61290391 Dec 2009 US
Continuations (1)
Number Date Country
Parent 12962571 Dec 2010 US
Child 13849685 US