US20150332223A1 - Transaction information collection for mobile payment experience - Google Patents

Transaction information collection for mobile payment experience Download PDF

Info

Publication number
US20150332223A1
US20150332223A1 US14/329,638 US201414329638A US2015332223A1 US 20150332223 A1 US20150332223 A1 US 20150332223A1 US 201414329638 A US201414329638 A US 201414329638A US 2015332223 A1 US2015332223 A1 US 2015332223A1
Authority
US
United States
Prior art keywords
transaction
payment
computer system
consumer
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/329,638
Inventor
Paul Aaron
Zachary Brock
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Square Inc
Original Assignee
Square Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201462000251P priority Critical
Application filed by Square Inc filed Critical Square Inc
Priority to US14/329,638 priority patent/US20150332223A1/en
Publication of US20150332223A1 publication Critical patent/US20150332223A1/en
Assigned to SQUARE, INC. reassignment SQUARE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AARON, PAUL, BROCK, ZACHARY
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • G06Q20/045Payment circuits characterized in that the payment protocol involves at least one ticket
    • G06Q20/0453Payment circuits characterized in that the payment protocol involves at least one ticket the ticket being an electronic receipt
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/12Payment architectures specially adapted for electronic shopping systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/20Point-of-sale [POS] network systems
    • G06Q20/202Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/20Point-of-sale [POS] network systems
    • G06Q20/204Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/42Confirmation, e.g. check or permission by the legal debtor of payment

Abstract

Disclosed is a technology for collecting transaction information for interactive payment experience. According to one embodiment, a payment service system receives transaction information from a card payment network. Using the received transaction information, the payment service system can determine a digital transaction receipt that is designed to interact with the consumer. A mobile device of the consumer receives and presents the digital transaction receipt. The interactive interface of the digital transaction receipt enables the consumer to interact with the receipt in various ways, such as specifying tip amount, entering feedback, confirming the transaction, etc.

Description

    PRIORITY CLAIM
  • This application claims the benefit of U.S. Provisional Patent Application No. 62/000,251, entitled “TRANSACTION INFORMATION COLLECTION FOR MOBILE PAYMENT EXPERIENCE”, which was filed on May 19, 2014, which is incorporated by reference herein in its entirety.
  • BACKGROUND
  • The traditional manner of providing receipts for payment transactions using financial accounts (e.g., credit cards and debit cards) is to print the payment amount and the purchased goods or services on a paper receipt. For instance, when a consumer wishes to pay for an item at a merchant's place of business by using a credit card, the consumer typically runs the credit card through a card reader at the merchant's point-of-sale (POS) terminal. The merchant's POS terminal submits a transaction request to an acquirer. The merchant typically stores all of the day's authorized transactions in a batch, and sends the batch to the acquirer at the end of the day to receive payment. The acquirer sends the batch to a card network (e.g., VISA or MasterCard), which distributes the transactions to credit card issuers. The credit card issuers authorize the transactions and then transfer the transaction amounts to one or more financial accounts of the merchant.
  • After a transaction has been authorized, the credit card issuer sends a confirmation to the POS terminal along a path opposite to that described above. The POS terminal prints out a paper receipt listing the purchases made, the method of payment, and the prices including tax, discounts and other price adjustments. The paper receipt serves as a proof of the purchase for the consumer.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • One or more embodiments of the present invention are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements.
  • FIG. 1 illustrates an environment in which an interactive payment experience technique can be implemented.
  • FIG. 2 illustrates an environment in which a payment service system collects transaction information from a card payment network.
  • FIG. 3 illustrates an environment in which a payment service system collects transaction information from a point-of-sale system.
  • FIG. 4A illustrates a first embodiment of an interactive digital receipt implemented on a mobile device.
  • FIG. 4B illustrates a second embodiment of an interactive digital receipt implemented on a mobile device.
  • FIG. 5A illustrates an example of a process of classifying financial accounts for transaction information collection.
  • FIG. 5B illustrates an example of a process of collecting transaction information by a payment service system.
  • FIG. 6A illustrates an example of a process of classifying financial accounts for transaction information collection in a merchant server.
  • FIG. 6B illustrates an example of a process of supplying item-level transaction information by the merchant server.
  • FIG. 7 is a high-level block diagram showing an example of processing system in which at least some operations related to the interactive payment experience technique can be implemented.
  • DETAILED DESCRIPTION
  • References in this description to “an embodiment”, “one embodiment”, or the like, mean that the particular feature, function, structure or characteristic being described is included in at least one embodiment of the present invention. Occurrences of such phrases in this specification do not necessarily all refer to the same embodiment. On the other hand, the embodiments referred to also are not necessarily mutually exclusive.
  • Introduced here is technology that enables consumers to interact with digital transaction receipts (also referred to as interactive digital receipts) received by their mobile devices. According to one embodiment, a payment service system receives transaction information from a card payment network. Using the received transaction information, the payment service system generates a digital transaction receipt that is designed to interact with the consumer. A mobile device of the consumer receives the digital transaction receipt via a wireless network and displays it to the consumer. The consumer can interact with the digital transaction receipt in any of various ways, such as specifying tip amount, entering feedback, confirming the transaction, etc.
  • In some embodiments, the payment service system can receive transaction information from different entities involved in processing the payment transaction. For example, the payment service system may receive transaction information from the merchant, the acquirer or the issuer. In order to identify the financial accounts that require transaction information collection, the entity supplying the transaction information (e.g., a card payment network) can maintain a database including information of financial accounts having a particular classification (e.g., accounts that are known to be associated with the payment service system). When the entity determines that a requested financial transaction relates to a financial account so classified in the database, the entity transmits the transaction information to the payment service system in real-time or near real-time, so that the payment service system can generate an interactive digital transaction receipt for the consumer.
  • The payment service system can receive messages indicative that a consumer chooses to enroll his or her financial accounts for the interactive payment service. Accordingly the payment service system can send instructions to an entity supplying transaction information (e.g., the card payment network) to adjust the database which identifies financial accounts.
  • In some embodiments, a merchant server can maintain a database including the information of financial accounts having a particular classification. The classification indicates that these financial accounts are associated with the payment service system. When the merchant server determines a requested financial transaction involves a financial account classified in the database, the merchant server transmits the item-level transaction information to the payment service system. The payment service system receives the item-level transaction information in real-time or near real-time and generates an interactive digital transaction receipt for the consumer.
  • FIG. 1 illustrates an environment in which the interactive payment experience technique introduced here can be implemented. The environment includes a merchant POS system of a merchant 100 and a mobile device 102 of a user 101 (also referred to as “customer” or “consumer”). The mobile device 102 can be, for example, a smart phone, tablet computer, notebook computer, or any other form of mobile processing device. A mobile payment application 120 runs on the user's mobile device 102. The environment also includes a computer system 114 of the merchant's acquirer, a computer system 118 of an issuing bank, a computer system 116 of a card payment network, and a computer system 108 of a payment service (hereinafter “payment service system 108”). The payment service system can be operated by an interactive payment experience service provider. The merchant's acquirer is a bank or financial institution that processes payments (e.g., credit or debit card payments) on behalf of a merchant. The acquirer acquires the payments from an issuer. The issuer (or issuing bank) is a bank or financial institution that offered a financial account (e.g., credit or debit card account) to the user 101. The issuer issues payments to the acquirer on behalf of the user 101 (consumer).
  • Each of the aforementioned computer systems can include one or more distinct physical computers and/or other processing devices which, in the case of multiple devices, can be connected to each other through one or more wired and/or wireless networks. All of the aforementioned devices are coupled to each other through an internetwork 106, which can be or include the Internet and one or more wireless networks (e.g., a WiFi network and or a cellular telecommunications network).
  • The environment illustrated in FIG. 1 can accommodate both traditional payment card transactions (i.e., those involving reading of physical card of the customer at the merchant's location), as well as card-not-present (CNP) transactions (i.e., those where the card is not physically presented at the time that the payment is effected). In a traditional credit card transaction, for example, the merchant swipes the user's credit card through a card reader at the POS system 104. The term “swipe” here refers to any manner of triggering a card reader to read data from a card, such as by passing a card into or through a magnetic stripe card reader, optical scanner, smartcard (card with an embedded IC chip) reader (e.g., an EMV-compliant card reader), radio frequency identification (RFID) reader, or the like. The POS system 104 sends data read from the card (e.g., the cardholders name, credit card number, expiration date and card verification value (CVV)) to the computer system 114 of the merchant's acquirer (hereinafter “acquirer 114”). The acquirer 114 sends this data to the computer system 116 of the card payment network (e.g., Visa or MasterCard) (hereinafter “card payment network 116”), which forwards the data to the computer system 118 of the issuing bank (hereinafter “issuer 118”). If the transaction is approved by the issuer 118, a payment authorization message is sent from the issuer 118 to the merchant POS system 104 via a path opposite of that described above.
  • In a card-not-present transaction, for example, the consumer places an online order by transmitting the data of a credit card from the mobile device 102 to the POS system 104. The POS system 104 can include, e.g., a web server for receiving the online order information. Then the POS system 104 sends the data of the card to the acquirer 114. The acquirer 114, the issuer 118 and the card payment network 116 complete the transaction in a way similar to the traditional credit card transaction.
  • The payment service system 108 includes one or more server computers programmed to collect transaction information, and to provide interactive user interface based on the collected information. The payment service system 108 can collect the transaction information from various parties, such as the POS system 104, the acquirer 114, the issuer 118 and the card payment network 116.
  • FIG. 2 illustrates an environment in which a payment service system collects transaction information from a card payment network. The user 101 can enroll his financial accounts for an interactive payment service through a mobile application running on the mobile device 102. Alternatively, the user 101 can enroll through a website. The user 101 may need to enter additional information for account verification purpose, such as card verification value (CVV), registration address, or even a picture of the payment card.
  • The mobile device 102 in turn notifies the payment service system 108 about the enrollment. The enrollment message authorizes the payment service system 108 to collect transaction information regarding the payment transactions that relate to the enrolled financial accounts.
  • The payment service system 108 can include a database for storing the information of the signed-up financial accounts including, e.g., data identifying the signed-up financial accounts, owners of the accounts, etc. The payment service system 108 sends an instruction to the card payment network 116 to cause the card payment network 116 to include the information of the signed-up financial account in a whitelist database. The card payment network 116 (or another entity involved in processing of payment transactions) subsequently uses the whitelist database during processing of a particular payment transaction to determine whether to send transaction information of the particular payment transaction to the payment service system 108.
  • The user 101 initiates a payment transaction process by swiping a payment card through a card reader of the POS system 104 (as a traditional payment card transaction) or sending data of a financial account to the POS system 104 (as a card-not-present transaction). For example, the user 101 can use the mobile device 102 to place an online order by instructing the mobile device 102 to send the data of the financial account to the POS system 104. The POS system 104 receives the order and determines various information such as the total amount and stock availability. Then the POS system 104 generates a request for a payment transaction and sends the request and data of the financial account to the acquirer 114. The data of the financial account can include, e.g., cardholder's name, card number, expiration date and card verification value (CVV).
  • The acquirer 114 send the payment authorization request and data of the financial account to the card payment network 116. Based on the received data of the financial account, the card payment network 116 determines the financial institution (issuer) that issued the financial account and distributes the payment authorization request and data of the financial account to the issuer 118. Once the issuer 118 approves the payment transaction on behalf of the user 101, the issuer 118 sends a payment authorization message to the POS system 104 via a path opposite of that described above.
  • When the card payment network 116 receives the request for the payment transaction, the card payment network 116 immediately determines whether the corresponding financial account is identified in the whitelist database that the card payment network 116 maintains (or to which the payment network 116 has access). If the whitelist database includes that financial account, the card payment network 116 then immediately sends the transaction information to the payment service system 108. Hence, the card payment network 116 makes this determination and, if appropriate, sends this information to the payment service system 108, during the transaction authorization process.
  • The payment service system 108 can communicate with the card payment network 116 through, e.g., a predetermined application programming interface (API). Through the API, the payment service system 108 receives the transaction information that relates to financial accounts that have been enrolled for the interactive payment service. The transaction information of a transaction can include, e.g., an amount of the payment transaction, an identification of the associated financial account, an identity of the merchant, and item-level information. The item-level information relates to the goods or services involved in the payment transaction. The item-level information can include names, identification numbers, prices, or descriptions of the goods or services. For example, item-level information of a purchase in a coffeehouse can include information such as iced coffee and apple pie (i.e., names), SKU 102 and SKU 231 (i.e., stock-keeping unit numbers), $2.99 and $3.49 (i.e., prices).
  • The payment service system 108 may receive transaction information from systems other than the card payment network 116. For example the acquirer 114 or the issuer 118 can also maintain a whitelist database for financial accounts that have been enrolled for the interactive payment service. Similar to the card payment network 116 as illustrated in FIG. 2, the acquirer 114 or the issuer 118 can update the whitelist database when the payment service system 108 sends an instruction to add a new financial account into the database. When the acquirer 114 or the issuer 118 receives a request for processing a payment transaction that relates to a financial account identified by the whitelist database, the acquirer 114 or the issuer 118 sends the transaction information to the payment service system 108.
  • In some alternative embodiments, instead of maintaining a whitelist database for identifying financial accounts for the purpose of transaction information collection, the payment card used by the user 101 can include additional data for transaction information collection purpose. Once the payment card swipes through a card reader of the POS system 104, the POS system 104 sends the additional data along with the data of the payment card to the acquirer 114. The acquirer 114, the card payment network 116 or the issuer 118 can follow the instruction included in the additional data to send the transaction information relating to the payment card to the payment service system 108.
  • Instead of receiving transaction information from the acquirer 114, card payment network 116 and the issuer 118, the payment service system can receive transaction information from the POS system 104. FIG. 3 illustrates an environment in which a payment service system collects transaction information from a point-of-sale (POS) system. The POS system 104 maintains a whitelist database for financial accounts that have been enrolled for the interactive payment service.
  • The POS system 104 can add to or drop from the whitelist database any financial account, based on the instructions received from the payment service system 108. A user 101 can use the mobile device 102 to send messages to the payment service system 108, indicating that the user 101 wants to enroll a financial account for the interactive payment service (or disassociate the financial account with the interactive payment service).
  • Once the user 101 swipes a payment card through a card reader of the POS system 104, or sends data of a financial account to the POS system 104 (e.g., via the mobile device 102), the POS system 140 determines the total amount and generates a request for processing the payment transaction. The POS system sends the request to the acquirer 114. The acquirer 114 further sends the request to the card payment network 116, which identifies the issuer 118 based on the data of the financial account. Once the issuer 118 approves the payment transaction, the issuer 118 sends a payment authorization message to the POS system 104 via a path opposite of that described above.
  • The POS system 104 scans the whitelist database to determine whether the financial account is identified by the whitelist database. If the financial account is identified by the whitelist database, the POS system 104 sends the transaction information to the payment service system 108. The transaction information includes item-level information describing or identifying the goods or services involved in the payment transaction. As an incentive for the POS system 104 of the merchant 100 to supply the transaction information, the merchant 100 may receive a fee discount for processing the payment transaction. In some embodiments, the payment service system 108 can directly confirm the receipt of the transaction information with the card payment network 116 so that the merchant 100 will receive the processing fee discount. Alternatively, the payment service system 108 can send a proof of receiving the transaction information, such as a confirmation code. The POS system 104 forwards the confirmation code to the card payment network 116 to receive the processing fee discount.
  • The payment service system can establish a communication channel with the POS system 104 through an application programming interview (API). Using the communication channel, the payment service system 108 can further monitor the status of the selected payment transaction in real time. The POS system 104 can grant the payment service system 108 access to any payment transaction relating to financial accounts identified by the whitelist database. Thus, the payment service system 108 not only can receive the transaction information, but also can monitor the status of the payment transaction, including being notified of the payment completion in real time.
  • Using the received transaction information, the payment service system 108 can provide the interactive payment service to the user 101 in various ways. For example, the payment service system 108 can generate an interactive digital receipt based on the transaction information and send the interactive digital receipt to the mobile device 102 of the user 101. The mobile device 102 can present the interactive digital receipt in different forms, such as a cell phone message, an email, a webpage, a push notification, or a user interface within the mobile payment application 120. The user 101 can interact with the interactive digital receipt for performing various tasks, such as confirming the total amount, adjusting tip amount, entering feedback, applying promotional discount, etc.
  • The connections between the systems and/or devices in FIGS. 2 and 3 can be either direct or indirect. For example, the connection between the payment service system 108 and the mobile device can be an indirect connection through the internetwork 106 (as illustrated in FIG. 1).
  • FIG. 4A illustrates a first embodiment of an interactive digital receipt implemented on a mobile device 400A. A mobile device can be a smartphone (e.g., iPhone®, Android®-enabled phone, etc.), a personal digital assistant (PDA), a tablet, an e-reader, or other mobile or portable computing devices, a desktop, a laptop, or other wired and wireless personal computers. In the embodiment of FIG. 4A, mobile device 400A is a tablet computer. Mobile device 400A is equipped with a display screen 402 for displaying various user interfaces to enable a user (e.g., customer) to interact with content generated on the mobile device 400A.
  • Mobile device 400A can implement an application, such as an interactive receipt mobile application for use by a mobile user, where the interactive receipt mobile application includes one or more customer interface components of interactive digital receipt 404. The interactive receipt mobile application can be either the same application as mobile payment application 120 or an application separate from the mobile payment application 120. As used herein, the term “customer interactive component” refers to a component of a user interface intended for a customer to view and interact (e.g., submit inputs) with various features offered via interactive digital receipt 404. Interactive digital receipt 404 includes information indicative of the payment transaction, such as transaction information (e.g., payment amount and item description), and various features that allow the customer to perform action associated with the transaction, subsequent to delivery of the receipt to the customer. While interactive digital receipt 404 is embodied in a mobile application according to the embodiment of FIGS. 4A-4B, other embodiments of the receipt are possible in light of the disclosure herein. In some embodiments, interactive digital receipt 404 is embodied in a text message that can be received at a computing device (e.g., devices 400A, 400B). In some embodiment, interactive digital receipt 404 is embodied in an email message that can be received at the computing device.
  • In some embodiments, payment service system 108 generates interactive digital receipt 404 for a customer after completion of a payment transaction between the customer and a merchant (e.g., payment authorization and approval that occurs at the completion of a service and/or tendering of goods). Payment service system 108 then delivers receipt 404 to the customer at the customer's mobile device 400A. In some embodiments, the payment service system 108 includes a digital receipt system that carries out the functionalities associated with implementing receipt 404.
  • The mobile device 400A receives and displays the interactive digital receipt 404 on display screen 402. Interactive digital receipt 404 may take up an entirety or any portion of display screen 402. Interactive digital receipt 404 can include various contents offered to the customer. In the embodiment of FIG. 4A, interactive digital receipt 404 includes a transaction component 406 and one or more interactive components 408, 410, 412. The transaction component 406 displays details associated with a particular transaction between the customer and the merchant, where the transaction details are displayed in real time in response to an occurrence of the particular transaction (e.g., payment transaction at the completion of a service). The interactive components 408, 410, 412 display one or more features for the customer to interact or perform an action associated with the transaction. In some embodiments, the features are generated so as to be available via the interactive digital receipt 404 only within a predefined time period. The predefined time period is configurable by the merchant and allows the merchant to provide time-based incentives to engage the customer.
  • The interactive components and general look and feel of interactive digital receipt 404 can be configured according to a particular merchant's needs. For example, a merchant in the business of selling household supplies can configure the interactive digital receipt to generate a feedback component without generating a tipping component. In another example, a merchant in the business of operating a restaurant can choose to have both the tipping and the feedback components be generated in the interactive digital receipt 404. One of ordinary skill in the art will appreciate that other configurations and components are possible.
  • FIG. 4B illustrates a second embodiment of an interactive digital receipt implemented on a mobile device 400B. According to the embodiment of FIG. 4B, the mobile device 400B is a smartphone. In FIG. 4B, interactive digital receipt 404 includes transaction components 406A, 406B, an interactive tipping component 420, an interactive feedback component 430, an interactive promotion component 440, an interactive loyalty rewards component 450, an interactive transaction records component 460, and an interactive financial accounts component 470.
  • Transaction components 406A, 406B provide transaction information associated with the transaction. Transaction component 406A includes an overview of the transaction completed between the customer and the merchant, such as the total amount of the transaction, the payment card used for the transaction (e.g., payment card name or last four digits of a payment card associated with the payment card), and the date, among others. Transaction component 406B includes details of the transaction, such as the name of the items purchased, the quantity, and the price, among others. For example, the transaction component 406B includes item-level information such as turkey sandwich and iced team (i.e., item names), $8.70 and $2.75 (item prices).
  • Interactive tipping component 420 (or, “tipping component”) allows the customer to submit a gratuity (“tip”) amount at a later time, i.e., subsequent to completion of a payment transaction. An example transaction, for example, is payment for a meal, where the customer can leave a tip after she has left the restaurant using interactive digital receipt 404 on her mobile device 400B, which has been delivered to device 400B automatically after completion of payment. In some embodiments, payment service system 108 receives the customer's tip submission via interactive receipt 404 and communicates the amount to the card payment network 116. The card payment network 116 adds the tip amount to the already authorized payment amount and sends the updated authorization to POS system 104 of the merchant, without requiring any additional payment approval from the customer. The merchant does not have to physically enter and request for an additional authorization for the tip amount from the card payment network 116.
  • In some embodiment, tipping component 420 includes automatically generated tip amounts based on a payment amount associated with the transaction (e.g., 10%, 15%, or 20%). In some embodiments, tipping component 420 includes a text box that allows the customer to enter a number. In some embodiments, where interactive digital receipt 404 is in the form of a text message, tipping component 420 is embodied in a text message prompting the customer to reply with an amount (e.g., “Tip by reply with dollar amount”). In some embodiments, tipping component 420 is a Uniform Resource Locator (URL) link which takes the user to a web page to allow adding of the tip amount. The link can be a part of a text message, a part of the text box within a mobile app, or an email.
  • In some embodiments, tipping component 420 is configured to be available for an unlimited time period. In some embodiments, tipping component 420 is configured to be available for a predefined time period, or timeframe, starting after a time instance when payment has been authorized and approved. The time period may be, for example, an hour, a day, a week, or any other desired time period (e.g., unlimited). In some embodiments, the time period is configured by the merchant. The time period is initialized, or started, at a time instance at which the transaction between the customer and merchant has completed, and decreases incrementally, from this time instance, at a rate that corresponds to an ordinary passage of time. At the expiration of the time period (i.e., the countdown reaches 0), the tipping feature becomes unavailable. In a real-world setting, such time limitation helps the merchant manage its payment transactions more efficiently. For example, a merchant often processes its payment transactions in batches and would not want to keep any particular transaction open indefinitely.
  • In some embodiments, the time period of the tipping component 420 is configured to incorporate a user defined default tip amount. A customer defines a nominal tip to be automatically submitted if no tip is submitted at the time period expiration. For example, customer defines the default tip to be $10 for her favorite restaurant to make sure that merchant always gets a tip. In such example, the $10 tip is automatically authorized for any transaction with that restaurant whenever no tip amount is added at the expiration. In some embodiments, the default tip amount may be defined by the merchant. For example, a restaurant merchant may want to configure a default nominal amount for restaurant services to groups of six parties or more. In such example, when no tip is added to the payment amount at the end of a time period (e.g., 2 hours), an automatic 20% tip is added to the customer's payment card authorization.
  • Interactive feedback component 430 (or, “feedback component”) allows the customer to submit feedback after the completion of a particular transaction with a merchant. The feedback may include submitting, for example, a rating (e.g., 5 stars), a review, a suggestion, or the like, on various aspects of the transaction (e.g., store cleanliness, service, products, overall visit satisfaction, etc.). In some embodiments, the feedback is submitted directly to the merchant. In some embodiments, a digital receipt system, coupled to transaction computer system, coordinates, communicates, and links with third party services associated with the merchant in implementing the feedback feature. In such embodiments, the digital receipt system transmits the feedback, submitted by the customer via receipt 404, to the third party services. The third party services aggregate the feedback in association with other feedback provided by the merchant. Such third party services may include, for example, Yelp.com, Urban Spoon, YP.com, and the like.
  • In some embodiments, feedback component 430 is configured to be available only for a predefined time period, or timeframe. In some embodiments, the time period associated with the feedback component 430 (“feedback time period”) is configured to be the same as the time period associated with tipping component 420 (“tipping time period”). For example, the time periods for both may be set at one hour and at the expiration of the hour, both the tipping and the feedback features become unavailable. In some embodiments, the feedback time period is configured to be different from the tipping time period. For example, the feedback time period may be set at one week while the tipping time period may be set at one hour.
  • In some embodiments, the feedback time period is configured differently depending on a particular merchant. For example, merchant A configures the feedback time period to be one day while merchant B configures the time period to be one week. In such example, feedback component becomes unavailable to the customer only on the receipt generated for merchant A, and the feedback component on the receipt generated for merchant B remains active until the end of the week. In some embodiments, a merchant can configure the feedback time period to be tied to an incentive (i.e., “feedback reward”) to encourage feedback. For example, the customer is rewarded a “20% Off Coupon” incentive, or feedback reward, if a written review is submitted before expiration of the feedback time period. In another example, if the feedback is submitted within 10 minutes after the completion of the payment transaction, the reward is a 20% Off coupon; on the other hand, if the feedback is submitted within 12 hours, but not exceeding the transaction time period allowed for the feedback (e.g., 24 hours), the reward is a 5% coupon.
  • Interactive promotion component 440 (or, “promotion component”) allows a particular merchant to engage and incentivize a customer to interact with the merchant. In some embodiments, promotion component generates one or more promotional rewards (or, “promotion”) associated with the completed transaction. For example, merchant A provides a coupon that can be redeemed at merchant B, an affiliated business with merchant A. In some embodiments, the promotion is time-based, where the customer must redeem the reward within a predefined period, or timeframe. In such embodiments, the promotion is configured to reduce, or decrease in value, corresponding to a decrease in the passage of time associated with the time period. The time period associated with the promotion component 440 (“promotion time period”) may be configured to be the same as, or different from, the feedback time period, and/or the tipping time period.
  • In one example, a “$10 off” coupon is generated via the interactive digital receipt for the customer to redeem at a next meal with the merchant. Such $10 coupon is set to decrease in value (i.e., until $0) from the moment the coupon is generated subsequent to the transaction at the merchant's store. As such, the sooner the customer redeems the time-based coupon, the higher the value she receives. In some embodiments, the merchant configures the rate of reduction. In one example, the restaurant sets the $10 coupon to expire after a week, with no reduction in value as long as the coupon is redeemed. In another example, the restaurant sets the $10 coupon to expire after 3 days, where the value reduces each day until the value reaches $0 at the end of the third day.
  • In some embodiments, the customer redeems the promotion by completing various redemption, or promotional, activities. Details of the activities may be displayed in the promotion component 440. Some redemption activities include simply revisiting the merchant to make another purchase for goods and/or services, as discussed in the example above. Other redemption activities include participating in a game via the mobile device 400B. Some redemption activities include participating in activities with other affiliated merchants. The redemption activity and the decreasing rate of the time-based reward may be configured by the merchant offering the reward. Such configurations are beneficial as they allow the merchant to customize the promotions according to the merchant's business, such as tailoring to an advertising campaign or a targeted customer demographic.
  • In some embodiments, promotion component 440 operates as an advertisement component to promote products and/or services. Such advertisement includes, for example, a promotional reward to entice the user to “click-on” or select a particular offering being displayed. In another example, the advertisement includes a plain display with no interaction required from the customer, where the interaction comes from the advertisement content changing to attract the customer's attention. The advertisement content can change based on the completed transaction for which the receipt 404 has been generated. For example, for a coffee purchase transaction, the advertisement includes information about a sustainable coffee alliance organization. The advertisement can also include information about nearby merchants associated with the venue where the completed transaction has taken place. In some embodiments, the interactive advertisement component is coupled to the interactive transaction record, where advertisement content is changed based on details extracted from the interactive transaction record.
  • Interactive loyalty rewards component 450 (or, “loyalty record component”) allows the customer to maintain and manage loyalty points associated with a particular merchant. Some merchants, for example, choose to reward loyal customers with reward points for their purchases and/or services transacted with the merchant. Loyalty record component 450 tracks those purchases and/or services over time, stores and updates reward points associated with the purchases and/or services, and maintains a membership status of the customer in relation to a particular merchant. In some embodiments, the loyalty record component is configured to be time-based, where the component tracks and maintains the loyalty status and/or rewards based on a predefined time period. For example, the loyalty record component upgrades the loyalty status of the consumer every month, where it calculates the transactions completed by the consumer within the month. The time period associated with the loyalty record component 450 (“loyalty time period”) may be configured to be the same as, or different from, time periods associated with other interactive components of the interactive receipt.
  • In an illustrative example, the rewards record tracks the number of baked goods bought from merchant A's bakery and updates the customer to an “elite status” in relation to that bakery when the customer has bought 10 items within 5 days. The elite status is displayed in the loyalty record component 450. The customer can redeem for a reward at the bakery with the loyalty record. In some embodiments, the merchant's POS system can communicate with the loyalty record component 450 without need for the customer to physically show the loyalty record at time of redemption.
  • Interactive transaction records component 460 (“transaction records component”). Transaction records component 460 includes one or more interactive digital receipts that has resulted from one or more payment transactions carried out by the customer with one or more merchants. In some embodiments, transaction records component 460 is configured to include only interactive digital receipts associated with a particular merchant. In some embodiments, transaction records component 460 is configured to include all interactive digital receipts associated with the customer, including receipts associated with different merchants with whom the customer has transacted. The interactive transaction record allows the customer to organize her interactive digital receipts, to maintain a comprehensive view of all payment transactions, and to perform one or more actions associated with those transactions via respective interactive components of the receipts. Other interactive components not discussed above, but consistent with the techniques discussed throughout, may also be envisioned by one of ordinary skill in the art based on the disclosed technology.
  • Interactive financial accounts component 470 (or, “financial accounts component”) allows the customer to maintain and change financial accounts, or financial accounts, associated with a particular payment transaction in which a payment object (e.g., payment card) is utilized. The financial accounts component allows a customer to review details about the transaction, including the financial accounts that are associated with the consumer's payment object and the particular financial account selected for payment in a particular transaction. In some embodiments, the financial accounts component allows the consumer to change the selected financial account to another financial account associated with the payment object. For example, the consumer, after leaving the merchant's place of business, remembers she has unused credits in a gift card, and accesses the financial accounts component to select the gift card, instead of a VISA credit card, to pay for the transaction. In some embodiments, the financial accounts component 470 is configured to be time-based, where the component enables the consumer to change financial accounts within a predefined time period. For example, the consumer is able to change the selected financial accounts only within one hour after the transaction has been completed (e.g., after authorization and approval). In another example, the consumer is able to change the selected financial accounts within 24 hours after the transaction.
  • FIG. 5A illustrates an example of a process of classifying financial accounts for transaction information collection. Initially, a consumer uses a mobile device 102 to choose signing up a financial account of the consumer for an interactive payment service (step 505). The mobile device 102 sends a message to a payment service system 108 indicative of the consumer's choice (step 510).
  • Upon receiving the message (step 515), the payment service system 108 sends to a card payment network system 116 a classification instruction (step 520). Upon receiving the classification instruction (step 525), the card payment network system 116 applies a predetermined classification to the financial account of the consumer (step 530), i.e., a classification indicative that the account is associated with the payment service system 108. The classification may, but does not necessarily, indicate to the card payment network system 116 that the financial account has been enrolled for the interactive payment service. The classification allows the card payment network system 116 to identify the financial accounts associated with the payment service system 108 so that the card payment network system 116 sends transaction information relating to these financial accounts to the payment service system 108. The card payment network system 116 can, e.g., maintain a database storing information identifying the financial accounts associated with the payment service system 108.
  • FIG. 5B illustrates an example of a process of collecting transaction information by a payment service system. Initially, a consumer instructs his or her mobile device 102 to place an online order (step 535), using, for example, a mobile browser or mobile payment application. Upon receiving the online order from the mobile device 102 (step 540), a merchant server 104 (e.g., the POS system 104 illustrated in FIG. 1) initiates a payment transaction for the online order (step 545). In some alternative embodiments, the merchant server 104 initiates the payment transaction when a payment card swipes through a card reader connected to merchant server 104 or included in the merchant server 104.
  • The merchant server 104 sends to the card payment network system 116 a payment authorization request for the payment transaction (step 550). Upon receiving the payment authorization request (step 555), the card payment network system 116 determines whether the financial account associated with the payment transaction has been applied with the predetermined classification (step 560). The card payment network system 116 can maintain a database including information of financial accounts that have been applied with the predetermined classification and use the database to determine whether a particular financial account is classified or not.
  • If that financial account is classified, the card payment network system 116 sends transaction information of the payment transaction to the payment service system 108, through an application programming interface (API) (step 565). If that financial account is not classified, the card payment network system 116 does not send the transaction information to the payment service system 108 (step 567).
  • The payment service system 108 has access to information of the financial account and information to enable the payment service system 108 to communicate with mobile device 102. The payment service system 108 receives the transaction information from the card payment network system 116 (step 570). Based on the transaction information, the payment service system 108 generates a digital transaction receipt indicative of the payment transaction (step 575). The payment service system 108 then transmits to the mobile device 102 of the consumer an instruction for a mobile application in the mobile device 102 to display (or output in any other manner) the digital transaction receipt to the consumer (step 580). The payment service system 108 is not a participant in processing the payment transaction and is not in a payment transaction message flow between the merchant's POS system 104 and a card issuer or card payment network system 116 involved in the transaction.
  • The mobile device 102 displays (or otherwise outputs) the digital transaction receipt that lists item-level information relating to goods or services involved in the payment transaction and includes an interface element to enable the consumer to specify a gratuity amount of the payment transaction (step 585). Next, the mobile device 102 inputs the gratuity amount specified by the consumer through the interface element (step 590). The mobile device 102 sends a message indicative of the gratuity amount to the payment service system 108 (step 592).
  • Upon receiving the message indicative of the gratuity amount (step 595), the payment service system 108 sends to the card payment network system 116 a request to adjust the total payment amount of the payment transaction based on the gratuity amount that has been specified by the consumer (step 597). Accordingly, the card payment network system 116 adjusts the total amount of the payment transaction based on the gratuity amount (step 598). In some alternative embodiments, a consumer or a merchant can specify a gratuity amount using the POS system 104. Likewise the POS system 104 can present a digital receipt and a user interface for specifying the gratuity amount. Upon receiving the specified gratuity amount, the POS system 104 sends the amount to the payment server system 108 to adjust the total payment transaction amount.
  • In some embodiments, the digital transaction receipt presented by the mobile device 102 includes a user interface element to enable the consumer to specify a promotional code. The payment service system 108 sends a request to the card payment network to confirm the validity of the promotional code and to adjust the amount of the payment transaction based on a promotion associated with the promotional code if the promotional code is valid.
  • In some other embodiments, the digital transaction receipt presented by the mobile device 102 includes an interface element to enable the consumer to specify a comment that relates to a purchase or a merchant associated with the payment transaction. The digital transaction receipt can further include a link to a website or a mobile application for managing the financial account.
  • The mobile device 102 can further send the payment service system 108 the location information regarding the geographical location of the mobile device 102 when the mobile device 102 communicates with the POS system and initiates the payment transaction. The payment service system 108 can then forward the location information to the card payment network system 116. Both the payment service system 108 and the card payment network system 116 can utilize the location information to analyze the behavior pattern of the consumer.
  • In some alternative embodiments, the payment service system 108 receives the transaction information from another payment processing entity involved in the transaction (e.g., an issuer 118, an acquirer 114 or a merchant server), instead of the card payment network system 116. For example the acquirer 114 or the issuer 118 can also maintain a whitelist database for financial accounts that have been applied with a predetermined classification. When the acquirer 114 or the issuer 118 determines that a financial account associated a received payment authorization request has been applied with the predetermined classification, the acquirer 114 or the issuer 118 sends the transaction information to the payment service system 108. The payment processing entity may provide a processing fee discount as an incentive for the merchant server 104 to supply the transaction information.
  • FIG. 6A illustrates an example of a process of classifying financial accounts for transaction information collection in a merchant server. Initially, the merchant server 104 (e.g., the POS system 104) maintains a database containing data identifying financial accounts being classified with a predetermined classification (step 610). To the merchant server 104, the classification does not necessarily indicate that the financial accounts have been enrolled for an interactive payment service. The classification allows the merchant server 104 to identify the particular financial accounts so that the merchant server 104 sends transaction information relating to these financial accounts to the payment service system 108.
  • The merchant server 104 receives from a payment service system 108 an instruction to add a new financial account (step 615). Accordingly, the merchant server 104 adds information of the new financial account to the database (step 620).
  • FIG. 6B illustrates an example of a process of supplying item-level transaction information by the merchant server 104. The merchant server 104 initiates a payment transaction when a payment card swipes through a card reader connected to merchant server 104 or included in the merchant server 104 (step 625). In some alternative embodiments, the merchant server 104 initiates the payment transaction when the merchant server 104 receives a request for placing an online purchase order from a user device (e.g., mobile device 102). The merchant server 104 sends to a processing server of a payment processing entity (e.g., card payment network system 116) a payment authorization request for the payment transaction (step 630). The payment processing entity can be, e.g., an acquirer, a card payment network or an issuer. The payment processing entity may provide a processing fee discount as an incentive for the merchant server 104 to supply the item-level transaction information.
  • The payment processing entity processes the payment transaction according to the request (step 632). Then the merchant server 104 receives a confirmation of completing the payment transaction in response to the payment authorization request (step 635).
  • The merchant server 104 determines whether the financial account involved in the payment transaction is classified as indicated by the data in the database (step 640). If the financial account is classified according to the database, the merchant server 104 sends to the payment service system 108 item-level information about goods or services involved in the payment transaction (step 645). The payment service system 108 has access to information of the financial account and information to enable the payment service system 108 to communicate with mobile device 102. If the financial account is not classified according to the database, the merchant server 104 does not send transaction information to the payment service system 108 (step 647).
  • Upon receiving the item-level transaction information (step 650), the payment service system 108 generates a digital transaction receipt listing the goods or services involved in the payment transaction based on the item-level information (step 655). A mobile device 102 of the consumer receives and represents the digital transaction receipt (step 660). The digital transaction receipt, as illustrated in FIGS. 4A-4B, enables the consumer to interact with the receipt in various ways, such as specifying tip amount, entering feedback, confirming the transaction, etc. The payment service system 108 is not a participant in processing the payment transaction and is not in a payment transaction message flow between the merchant's POS system 104 and a card issuer or card payment network system 116 involved in the transaction.
  • FIG. 7 is a high-level block diagram showing an example of a processing device 700 that can represent any of the devices described above, such as the mobile device 102, merchant server 104, acquirer 114, card payment network 116, issuer 118 or payment service system 108.
  • In the illustrated embodiment, the processing system 700 includes one or more processors 710, memory 711, a communication device 712, and one or more input/output (I/O) devices 713, all coupled to each other through an interconnect 714. The interconnect 714 may be or include one or more conductive traces, buses, point-to-point connections, controllers, adapters and/or other conventional connection devices. The processor(s) 710 may be or include, for example, one or more general-purpose programmable microprocessors, microcontrollers, application specific integrated circuits (ASICs), programmable gate arrays, or the like, or a combination of such devices. The processor(s) 710 control the overall operation of the processing device 700. Memory 711 may be or include one or more physical storage devices, which may be in the form of random access memory (RAM), read-only memory (ROM) (which may be erasable and programmable), flash memory, miniature hard disk drive, or other suitable type of storage device, or a combination of such devices. Memory 711 may store data and instructions that configure the processor(s) 710 to execute operations in accordance with the techniques described above. The communication device 712 may be or include, for example, an Ethernet adapter, cable modem, Wi-Fi adapter, cellular transceiver, Bluetooth transceiver, or the like, or a combination thereof. Depending on the specific nature and purpose of the processing device 700, the I/O devices 713 can include devices such as a display (which may be a touch screen display), audio speaker, keyboard, mouse or other pointing device, microphone, camera, etc.
  • Unless contrary to physical possibility, it is envisioned that (i) the methods/steps described above may be performed in any sequence and/or in any combination, and that (ii) the components of respective embodiments may be combined in any manner.
  • The techniques introduced above can be implemented by programmable circuitry programmed/configured by software and/or firmware, or entirely by special-purpose circuitry, or by a combination of such forms. Such special-purpose circuitry (if any) can be in the form of, for example, one or more application-specific integrated circuits (ASICs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), etc.
  • Software or firmware to implement the techniques introduced here may be stored on a machine-readable storage medium and may be executed by one or more general-purpose or special-purpose programmable microprocessors. A “machine-readable medium”, as the term is used herein, includes any mechanism that can store information in a form accessible by a machine (a machine may be, for example, a computer, network device, cellular phone, personal digital assistant (PDA), manufacturing tool, any device with one or more processors, etc.). For example, a machine-accessible medium includes recordable/non-recordable media (e.g., read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; etc.), etc.
  • Note that any and all of the embodiments described above can be combined with each other, except to the extent that it may be stated otherwise above or to the extent that any such embodiments might be mutually exclusive in function and/or structure.
  • Although the present invention has been described with reference to specific exemplary embodiments, it will be recognized that the invention is not limited to the embodiments described, but can be practiced with modification and alteration within the spirit and scope of the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative sense rather than a restrictive sense.

Claims (24)

1. A method comprising:
sending, from a first computer system operated by an interactive payment experience provider, to a second computer system operated by a payment card network or a payment card issuer, an instruction for associating a financial account of a consumer with an interactive payment service, wherein the first computer system has access to information of the financial account of the consumer;
requesting, by the first computer system, that in response to recognition that a payment transaction involves the financial account that has been associated with the interactive payment service, the second computer system send item-level transaction information of the payment transaction to the first computer system, wherein the item-level transaction information includes item-level information about goods or services involved in the payment transaction, an amount of the payment transaction, an identification of the financial account and an identity of a merchant involved in the payment transaction;
receiving, at the first computer system from the second computer system, the item-level transaction information of the payment transaction, in response to the second computer system receiving a request for authorization of the payment transaction, wherein the interactive payment experience provider is not a participant in processing the payment transaction and is not in a payment transaction message flow between the merchant and a card issuer involved in the transaction;
generating, at the first computer system, a digital transaction receipt based on the item-level transaction information, the digital transaction receipt being indicative of the payment transaction; and
transmitting, from the first computer system to a mobile device of the consumer, an instruction to a mobile application of the mobile device for presenting the digital transaction receipt as an interactive user interface element, wherein the first computer system has information used to communicate with the mobile device of the consumer.
2. The method of claim 1, wherein said transmitting comprises transmitting an instruction to the mobile application for presenting the digital transaction receipt so as to list item-level information associated with the payment transaction, the item-level information relating to goods or services involved in the payment transaction.
3. The method of claim 1, wherein said transmitting comprises transmitting an instruction to the mobile application for presenting the digital transaction receipt so as to include an interface element for the consumer to specify a gratuity amount of the payment transaction; and
the method further comprising:
sending, from the first computer system to the second computer system, a request to adjust the amount of the payment transaction based on the gratuity amount.
4. The method of claim 1, wherein said transmitting comprises transmitting an instruction to the mobile application for presenting the digital transaction receipt so as to include an interface element for the consumer to specify a promotional code; and
the method further comprising:
sending, from the first computer system to the second computer system, a request to confirm a validity of the promotional code and to adjust the amount of the payment transaction based on a promotion associated with the promotional code if the promotional code is valid.
5. The method of claim 1, wherein said transmitting comprises transmitting an instruction to the mobile application for presenting the digital transaction receipt including an interface element for the consumer to specify a comment that relates to the payment transaction.
6. A method comprising:
sending, from a first computer system, an instruction to apply a predetermined classification to a financial account of a consumer, to a second computer system of a payment card network or a payment card issuer;
receiving, at the first computer system from the payment card network or the payment card issuer, transaction information of a payment transaction that involves the financial account of the consumer, the transaction information having been sent to the first computer system in response to initiation of the payment transaction and recognition that the financial account of the consumer has the predetermined classification; and
transmitting, from the first computer system to a mobile device of the consumer, an instruction for the mobile device to present an interactive user interface based on the transaction information of the payment transaction.
7. The method of claim 6, further comprising:
sending, from the first computer system to the second computer system, an instruction for the second computer system to send to the first computer system transaction information of any payment transaction that relates to any financial account represented in a database of financial accounts that have the predetermined classification.
8. The method of claim 6, wherein the receiving comprises:
receiving, at the first computer system from the payment card network or the payment card issuer through an application programming interface (API), transaction information of a payment transaction that involves the financial account of the consumer.
9. The method of claim 6, wherein the transaction information of the payment transaction includes an amount of the payment transaction, an identification of the financial account and an identity of a merchant of the payment transaction.
10. The method of claim 9, wherein the transaction information further includes item-level information associated with the payment transaction, the item-level information including identifications of goods or services involved in the payment transaction.
11. The method of claim 10, further comprising:
generating, at the first computer system, the interactive user interface including providing a digital receipt based on the transaction information, the digital receipt indicating the goods or services involved in the payment transaction.
12. The method of claim 6, further comprising:
generating, at the first computer system, the interactive user interface to include a digital receipt based on the transaction information, the digital receipt including a link to a website or a mobile application for managing the financial account.
13. The method of claim 6, further comprising:
generating, at the first computer system, the interactive user interface to include a digital receipt, the digital receipt including an option to enable the consumer to specify a gratuity amount for the payment transaction.
14. The method of claim 13, further comprising:
receiving, at the first computer system from the mobile device, a message indicative of the gratuity amount specified by the consumer;
sending, from the first computer system to the second computer system, a request to adjust a total payment amount of the payment transaction based on the gratuity amount specified by the consumer.
15. The method of claim 6, further comprising:
generating, at the first computer system, the interactive user interface to include a digital receipt based on the transaction information, the digital receipt including an interface element to enable the consumer to specify feedback about a reaction to a purchased item or a merchant that is associated with the payment transaction.
16. The method of claim 6, further comprising:
receiving, at the first computer system from the mobile device, location information of a geographical location of the mobile device in relation to the payment transaction; and
forwarding the location information of the mobile device from the first computer system to the second computer system.
17. A computer system comprising:
a networking component to communicate with external computer systems;
a processor; and
a memory storing instructions with, when executed by the processor, cause the computer system to perform a process that includes:
receiving, from a mobile device of a consumer, a message indicative of the consumer enrolling a financial account of the consumer for an interactive payment service;
sending, to a first computer device of a payment processing entity, an instruction to include information identifying the financial account in a database, the database including information identifying financial accounts that are enrolled for the interactive payment service;
receiving, from the first computer device, transaction information of a payment transaction that relates to the financial account of the consumer;
in response to the received transaction information, sending, to the mobile device of the consumer, an interactive digital receipt for the payment transaction.
18. The computer system of claim 17, wherein the process further includes:
receiving, from the first computer device, a message confirming that the payment transaction is completed.
19. The computer system of claim 17, wherein the digital receipt includes an interactive element for the merchant to specify a gratuity amount for the payment transaction on the mobile device; and wherein the process further includes: sending, to the first computer device, a request to adjust an amount of the payment transaction based on the gratuity amount.
20. The computer system of claim 17, wherein the digital receipt lists goods or services involved in the payment transaction and includes links to websites or mobile applications that provide further information about the goods or services.
21. A computer system comprising:
a networking component to communicate with external computer systems;
a processor; and
a memory storing instructions which, when executed by the processor, cause the computer system to perform a process including:
maintaining a database including information of financial accounts that have a predetermined classification;
receiving a request for authorizing a payment transaction that involves a financial account of a consumer;
recognizing that the financial account of the consumer has the predetermined classification based on the database; and
in response to recognition that the financial account of the consumer has the predetermined classification, sending transaction information of the payment transaction to a payment service system.
22. The computer system of claim 21, wherein the process further includes:
authorizing the payment transaction in response to the request.
23. The computer system of claim 21, wherein the process further includes:
receiving, from the payment service system, an instruction to apply the predetermined classification to a financial account of the consumer; and
adding information of the financial account of the consumer to the database.
24. The computer system of claim 21, wherein the transaction information includes item-level information relating to goods or services involved in the payment transaction, and wherein said sending comprises:
sending, to a mobile device of the consumer via the external computer system, the item-level information to enable the mobile device to present a digital receipting listing the goods or services involved in the payment transaction to the consumer.
US14/329,638 2014-05-19 2014-07-11 Transaction information collection for mobile payment experience Abandoned US20150332223A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US201462000251P true 2014-05-19 2014-05-19
US14/329,638 US20150332223A1 (en) 2014-05-19 2014-07-11 Transaction information collection for mobile payment experience

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US14/329,638 US20150332223A1 (en) 2014-05-19 2014-07-11 Transaction information collection for mobile payment experience
AU2015264426A AU2015264426A1 (en) 2014-05-19 2015-05-18 Transaction information collection for mobile payment experience
PCT/US2015/031423 WO2015179316A1 (en) 2014-05-19 2015-05-18 Transaction information collection for mobile payment experience
AU2018205104A AU2018205104A1 (en) 2014-05-19 2018-07-11 Transaction Information Collection for Mobile Payment Experience

Publications (1)

Publication Number Publication Date
US20150332223A1 true US20150332223A1 (en) 2015-11-19

Family

ID=54538828

Family Applications (3)

Application Number Title Priority Date Filing Date
US14/329,638 Abandoned US20150332223A1 (en) 2014-05-19 2014-07-11 Transaction information collection for mobile payment experience
US14/329,658 Active US9652751B2 (en) 2014-05-19 2014-07-11 Item-level information collection for interactive payment experience
US15/582,300 Pending US20180150807A1 (en) 2014-05-19 2017-04-28 Item-level information collection for interactive payment experience

Family Applications After (2)

Application Number Title Priority Date Filing Date
US14/329,658 Active US9652751B2 (en) 2014-05-19 2014-07-11 Item-level information collection for interactive payment experience
US15/582,300 Pending US20180150807A1 (en) 2014-05-19 2017-04-28 Item-level information collection for interactive payment experience

Country Status (3)

Country Link
US (3) US20150332223A1 (en)
AU (2) AU2015264426A1 (en)
WO (1) WO2015179316A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2545987A (en) * 2015-11-19 2017-07-05 Wal-Mart Stores Inc Systems and methods for flexibly securing card data
US10192220B2 (en) 2013-06-25 2019-01-29 Square, Inc. Integrated online and offline inventory management

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9940616B1 (en) 2013-03-14 2018-04-10 Square, Inc. Verifying proximity during payment transactions
US9704146B1 (en) 2013-03-14 2017-07-11 Square, Inc. Generating an online storefront
US9836739B1 (en) 2013-10-22 2017-12-05 Square, Inc. Changing a financial account after initiating a payment using a proxy card
US9922321B2 (en) 2013-10-22 2018-03-20 Square, Inc. Proxy for multiple payment mechanisms
US20150134439A1 (en) 2013-11-08 2015-05-14 Square, Inc. Interactive digital receipt
US9619792B1 (en) 2014-03-25 2017-04-11 Square, Inc. Associating an account with a card based on a photo
US9864986B1 (en) 2014-03-25 2018-01-09 Square, Inc. Associating a monetary value card with a payment object
US20160335621A1 (en) * 2015-05-12 2016-11-17 Gopesh Kumar Method for Providing Secured Card Transactions During Card Not Present (CNP) Transactions
US10026062B1 (en) 2015-06-04 2018-07-17 Square, Inc. Apparatuses, methods, and systems for generating interactive digital receipts
US20170221058A1 (en) * 2016-02-02 2017-08-03 Visa International Service Association System and method for secondary account holder payment device control
US20170278085A1 (en) * 2016-03-25 2017-09-28 Stripe Inc. Methods and systems for providing payment interface services using a payment platform

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090106138A1 (en) * 2007-10-22 2009-04-23 Smith Steven E Transaction authentication over independent network
US7818809B1 (en) * 2004-10-05 2010-10-19 Symantec Corporation Confidential data protection through usage scoping
US20130236109A1 (en) * 2012-03-07 2013-09-12 The Western Union Company Identification generation and authentication process application
US20140257958A1 (en) * 2013-03-05 2014-09-11 Google Inc. Merchant incentive programs on proxy card systems

Family Cites Families (218)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5590038A (en) 1994-06-20 1996-12-31 Pitroda; Satyan G. Universal electronic transaction card including receipt storage and system and methods of conducting electronic transactions
US6796492B1 (en) 1995-04-13 2004-09-28 James G. Gatto Electronic fund transfer or transaction system
US20030217005A1 (en) 1996-11-27 2003-11-20 Diebold Self Service Systems, Division Of Diebold, Incorporated Automated banking machine system and method
US6175922B1 (en) 1996-12-04 2001-01-16 Esign, Inc. Electronic transaction systems and methods therefor
US6193155B1 (en) 1996-12-09 2001-02-27 Walker Digital, Llc Method and apparatus for issuing and managing gift certificates
US6341353B1 (en) 1997-04-11 2002-01-22 The Brodia Group Smart electronic receipt system
US5960411A (en) 1997-09-12 1999-09-28 Amazon.Com, Inc. Method and system for placing a purchase order via a communications network
US6263352B1 (en) 1997-11-14 2001-07-17 Microsoft Corporation Automated web site creation using template driven generation of active server page applications
US7308426B1 (en) 1999-08-11 2007-12-11 C-Sam, Inc. System and methods for servicing electronic transactions
US8190514B2 (en) 1999-11-05 2012-05-29 Lead Core Fund, L.L.C. Systems and methods for transaction processing based upon an overdraft scenario
US7478054B1 (en) 1999-11-19 2009-01-13 Amazon.Com, Inc. Sharing information about purchases
US7552087B2 (en) 2000-02-03 2009-06-23 Afterbot, Inc. Electronic transaction receipt system and method
US7487112B2 (en) 2000-06-29 2009-02-03 Barnes Jr Melvin L System, method, and computer program product for providing location based services and mobile e-commerce
US7774231B2 (en) 2000-09-29 2010-08-10 Nokia Corporation Electronic payment methods for a mobile device
US7155411B1 (en) 2000-09-28 2006-12-26 Microsoft Corporation Integrating payment accounts and an electronic wallet
GB0112837D0 (en) 2001-05-25 2001-07-18 Ltd Dedicated Engines Monitoring system
US7805378B2 (en) 2001-07-10 2010-09-28 American Express Travel Related Servicex Company, Inc. System and method for encoding information in magnetic stripe format for use in radio frequency identification transactions
WO2003010701A1 (en) 2001-07-24 2003-02-06 First Usa Bank, N.A. Multiple account card and transaction routing
US7085812B1 (en) 2001-08-06 2006-08-01 Bellsouth Intellectual Property Corporation System and method for selective application of email delivery options
US20030217142A1 (en) 2002-05-15 2003-11-20 Microsoft Corporation Method and system for supporting the communication of presence information regarding one or more telephony devices
US7580873B1 (en) 2002-07-23 2009-08-25 At&T Intellectual Property I, L.P. Electronic financial assistant
WO2004012042A2 (en) 2002-07-25 2004-02-05 The Kroger Co. Reward system
US8224700B2 (en) * 2002-08-19 2012-07-17 Andrew Silver System and method for managing restaurant customer data elements
US20060146839A1 (en) 2002-09-06 2006-07-06 Hurwitz Harlan A Payment and media management
US20040204990A1 (en) 2003-04-11 2004-10-14 Lee Stacy A. Method and system to incentivize a user to perform an activity relating to a network-based marketplace in a timely manner
NZ552892A (en) 2004-06-25 2010-05-28 Ian Charles Ogilvy A transaction processing method, apparatus and system
US8594567B2 (en) 2004-08-16 2013-11-26 Giesecke & Devrient Gmbh Controlled wireless charging of an accumulator in a chipcard
US20060085333A1 (en) 2004-08-25 2006-04-20 Wah Leow O Credit/debit card payment system
GB0427693D0 (en) 2004-12-17 2005-01-19 Ncr Int Inc An automated teller machine
KR20050096853A (en) 2005-03-25 2005-10-06 주식회사 인텔리전스 마케팅 Market research system and method using image data of receipts
US20060229998A1 (en) 2005-03-31 2006-10-12 Mark Harrison Payment via financial service provider using network-based device
US8770477B2 (en) 2005-04-26 2014-07-08 Guy Hefetz Method for identifying the georgrapic location of a router
US20060261149A1 (en) 2005-05-18 2006-11-23 First Data Corporation Automated teller machine with receipt printer and display
US7925022B2 (en) 2005-05-23 2011-04-12 The Invention Science Fund I, Llc Device pairing via device to device contact
US7401731B1 (en) 2005-05-27 2008-07-22 Jpmorgan Chase Bank, Na Method and system for implementing a card product with multiple customized relationships
US7865140B2 (en) 2005-06-14 2011-01-04 The Invention Science Fund I, Llc Device pairing via intermediary device
US7896242B2 (en) 2005-08-26 2011-03-01 Reagan Inventions, Llc System and method for issuing digital receipts for purchase transactions over a network
US8103545B2 (en) 2005-09-14 2012-01-24 Jumptap, Inc. Managing payment for sponsored content presented to mobile communication facilities
US20070073619A1 (en) 2005-09-23 2007-03-29 Smith Rebecca C Biometric anti-fraud plastic card
US7487912B2 (en) 2005-09-28 2009-02-10 First Data Corporation Electronic receipting
US7958355B2 (en) 2006-03-01 2011-06-07 Microsoft Corporation Keytote component
US20070255662A1 (en) 2006-03-30 2007-11-01 Obopay Inc. Authenticating Wireless Person-to-Person Money Transfers
CA2647636A1 (en) 2006-03-30 2008-03-06 Obopay Inc. Mobile person-to-person payment system
US7873573B2 (en) 2006-03-30 2011-01-18 Obopay, Inc. Virtual pooled account for mobile banking
US8939359B2 (en) 2006-05-05 2015-01-27 Cfph, Llc Game access device with time varying signal
US20070288322A1 (en) 2006-05-23 2007-12-13 Toshiba Tec Kabushiki Kaisha Portable terminal and its programs, settlement apparatus, and merchandising information providing apparatus
US9911114B2 (en) 2006-07-06 2018-03-06 Qualcomm Incorporated Methods and systems for making a payment via a stored value card in a mobile environment
EP2047419A4 (en) 2006-07-17 2011-09-28 Next Jump Inc Communication system and method for narrowcasting
US8595348B2 (en) 2006-08-09 2013-11-26 Aol Inc. Content distribution tracking through wireless mesh networks
US20080052176A1 (en) 2006-08-25 2008-02-28 Buchheit Brian K Payment device to allow an automated means for ordering and payment by food establishment patrons
US20090298514A1 (en) 2006-09-14 2009-12-03 Shah Ullah Real world behavior measurement using identifiers specific to mobile devices
EP2097864A4 (en) 2006-10-24 2011-10-05 Mastercard International Inc Method and apparatus for reward messaging, discounting and redemption at the point of interaction
US9600959B2 (en) 2007-01-09 2017-03-21 Cfph, Llp System for managing promotions
US20100010906A1 (en) 2007-01-23 2010-01-14 William Grecia Point of sale payment method for multiple recipients using a digital payment service
US20080270246A1 (en) 2007-04-26 2008-10-30 Grace Chen Global electronic payment system
US8326758B2 (en) 2007-08-06 2012-12-04 Enpulz, L.L.C. Proxy card representing many monetary sources from a plurality of vendors
US20090063312A1 (en) * 2007-08-28 2009-03-05 Hurst Douglas J Method and System for Processing Secure Wireless Payment Transactions and for Providing a Virtual Terminal for Merchant Processing of Such Transactions
US20090070228A1 (en) 2007-09-12 2009-03-12 Guy Ronen Systems and methods for e-commerce and mobile networks for providing purchase experiences of friends in a social network
US20090319421A1 (en) 2007-10-02 2009-12-24 Mathis Kenneth A Method and Apparatus for Performing Financial Transactions
US20090094123A1 (en) 2007-10-03 2009-04-09 Patrick Killian Payment services provider methods in connection with personalized payments system
WO2010108084A1 (en) 2009-03-19 2010-09-23 Mastercard International Inc. Method and apparatus for mobile offer fulfillment
US20090112766A1 (en) 2007-10-25 2009-04-30 Ayman Hammad Device including multiple payment applications
US9141948B2 (en) 2007-11-30 2015-09-22 U.S. Bank National Association Control system arrangements and methods for disparate network systems
US20120029990A1 (en) 2007-12-13 2012-02-02 Blaze Mobile Social Media Marketing Based on Transactions Using a Mobile Device and Associated Secure Element
US20090159670A1 (en) 2007-12-24 2009-06-25 Dynamics Inc. Cards and devices with multifunction magnetic emulators and methods for using the same
US20090192904A1 (en) 2008-01-24 2009-07-30 Barbara Patterson System and Method for Conducting Transactions with a Financial Presentation Device Linked to Multiple Accounts
US20140250002A1 (en) 2008-05-29 2014-09-04 Giftya Llc System and method for processing a gift card via the cloud
US20090271265A1 (en) 2008-04-28 2009-10-29 Cyndigo, Corp. Electronic receipt system and method
WO2009143084A1 (en) 2008-05-18 2009-11-26 Zetawire, Inc. Secured electronic transaction system
US8745166B2 (en) 2008-05-28 2014-06-03 Visa U.S.A. Inc. Gateway service platform
US20130144707A1 (en) 2010-12-14 2013-06-06 Giftya Llc System and method for processing gifts between different exchange mediums
US20120150643A1 (en) 2010-12-14 2012-06-14 Moneyhoney Llc System and method for processing remainder amounts of money from gift cards
US20130166445A1 (en) 2010-12-14 2013-06-27 Giftya Llc System and method for processing gift cards which hide some gift card data
US8788350B2 (en) * 2008-06-13 2014-07-22 Microsoft Corporation Handling payment receipts with a receipt store
US8116749B2 (en) 2008-09-08 2012-02-14 Proctor Jr James Arthur Protocol for anonymous wireless communication
US20100076777A1 (en) 2008-09-23 2010-03-25 Yahoo! Inc. Automatic recommendation of location tracking privacy policies
WO2010036804A2 (en) 2008-09-25 2010-04-01 Visa International Service Association System and method for benefit notification
US8127982B1 (en) 2009-01-09 2012-03-06 Apple Inc. Parental controls
CN105205655A (en) 2009-02-14 2015-12-30 网络文本有限公司 Secure payment and billing method using mobile phone number or account
US8606638B2 (en) 2009-03-02 2013-12-10 First Data Corporation Systems, methods and apparatus for facilitating transactions using a mobile device
US8650072B2 (en) 2009-05-05 2014-02-11 Groupon, Inc. System and methods for providing location based discount retailing
US20110047013A1 (en) 2009-05-21 2011-02-24 Mckenzie Iii James O Merchandising amplification via social networking system and method
US8224727B2 (en) 2009-05-27 2012-07-17 Boku, Inc. Systems and methods to process transactions based on social networking
US8396808B2 (en) 2009-07-31 2013-03-12 Think Computer Corporation Method and system for transferring an electronic payment
US8332320B2 (en) 2009-08-31 2012-12-11 Novell, Inc. Techniques for remote controlled physical transactions with dynamic key generation and authentication
US20130050080A1 (en) 2009-10-07 2013-02-28 Elliptic Laboratories As User interfaces
US20120059701A1 (en) 2009-10-13 2012-03-08 Van Der Veen Larry Systems and methods forfacilitating a rewards program involving multiple payments accounts
TWI453686B (en) 2009-12-10 2014-09-21 Inst Information Industry Consumption management systems and methods integrated with social network
US8859337B2 (en) 2009-12-15 2014-10-14 Soitec Thermal matching in semiconductor devices using heat distribution structures
US20140100973A1 (en) 2009-12-28 2014-04-10 Cryptite, Llc Smartphone virtual payment card
US8645213B2 (en) 2010-01-15 2014-02-04 Ebay, Inc. Transactions associated with a mobile device
US9367834B2 (en) 2010-01-22 2016-06-14 Iii Holdings 1, Llc Systems, methods, and computer products for processing payments using a proxy card
US8788418B2 (en) 2010-03-02 2014-07-22 Gonow Technologies, Llc Portable E-wallet and universal card
US9245267B2 (en) 2010-03-03 2016-01-26 Visa International Service Association Portable account number for consumer payment account
US20110246284A1 (en) 2010-04-01 2011-10-06 Gary Chaikin Systems and Methods for Adding Functionality to Merchant Sales and Facilitating Data Collection.
US8380177B2 (en) 2010-04-09 2013-02-19 Paydiant, Inc. Mobile phone payment processing methods and systems
US20110251962A1 (en) 2010-04-13 2011-10-13 John Hruska Transaction method for secure electronic gift cards
US20110270747A1 (en) 2010-04-28 2011-11-03 Xu Richard H System and Method for Adding Funds to a Prepaid Account for a Mobile Device Associated with Mulitple Communication Profiles
US20110276418A1 (en) 2010-05-07 2011-11-10 S1 Corporation Apparatus, System and Method For Purchaser to Business Payments
US20110313871A1 (en) 2010-05-18 2011-12-22 Laura Greenwood Apparatus, system, and method for facilitating a payment
JP6168990B2 (en) 2010-05-25 2017-07-26 ペイキャッシュ ラブズ アクチエンゲゼルシャフトPayCash Labs AG A method of forming a transaction signal
US20110302080A1 (en) 2010-06-03 2011-12-08 Brigette White Method and apparatus for value interchange pricing
US8266551B2 (en) 2010-06-10 2012-09-11 Nokia Corporation Method and apparatus for binding user interface elements and granular reflective processing
US20110320345A1 (en) 2010-06-29 2011-12-29 Ebay, Inc. Smart wallet
EP2588949A1 (en) 2010-07-01 2013-05-08 Ishai Binenstock Location-aware mobile connectivity and information exchange system
WO2012012445A2 (en) 2010-07-19 2012-01-26 Universal Commerce, Inc. Mobile system and method for payments and non-financial transactions
US8630586B2 (en) 2010-08-31 2014-01-14 Apple Inc. Intelligent pairing of electronic devices
WO2012030836A2 (en) 2010-09-03 2012-03-08 Visa International Service Association Protecting express enrollment using a challenge
US20120084210A1 (en) 2010-09-30 2012-04-05 Arvin Farahmand Mobile device payment system
US9703539B2 (en) 2010-10-29 2017-07-11 Microsoft Technology Licensing, Llc Viral application distribution
US9141945B2 (en) 2010-12-02 2015-09-22 Appmobi Iplc, Inc. Secure distributed single action payment system
US8939357B1 (en) 2010-12-03 2015-01-27 Excentus Corporation System and method for combining disparate commercial transactions under a single identification mechanism
CA2724297C (en) 2010-12-14 2013-11-12 Xtreme Mobility Inc. System and method for authenticating transactions through a mobile device
US20120166311A1 (en) 2010-12-23 2012-06-28 Ebay, Inc. Deferred payment and selective funding and payments
US20130024364A1 (en) 2011-02-22 2013-01-24 Abhinav Shrivastava Consumer transaction leash control apparatuses, methods and systems
US20130024371A1 (en) 2011-02-22 2013-01-24 Prakash Hariramani Electronic offer optimization and redemption apparatuses, methods and systems
US20130159081A1 (en) 2011-07-08 2013-06-20 Vishwanath Shastry Bidirectional bandwidth reducing notifications and targeted incentive platform apparatuses, methods and systems
WO2012097285A2 (en) 2011-01-14 2012-07-19 Suarez Corporation Industries Social shopping apparatus, system and method
US20120197794A1 (en) 2011-01-31 2012-08-02 Bank Of America Corporation Shared mobile wallet
US20120209773A1 (en) 2011-02-10 2012-08-16 Ebay, Inc. Fraud alerting using mobile phone location
SG193481A1 (en) 2011-02-16 2013-10-30 Visa Int Service Ass Snap mobile payment apparatuses, methods and systems
US20120214416A1 (en) 2011-02-23 2012-08-23 Jonathan Douglas Kent Methods and apparatuses for communication between devices
KR20140121764A (en) 2012-01-05 2014-10-16 비자 인터네셔널 서비스 어소시에이션 Transaction visual capturing apparatuses, methods and systems
US10223743B2 (en) 2011-03-29 2019-03-05 Blackberry Limited Communication system providing near field communication (NFC) transaction features and related methods
US8690051B1 (en) 2011-04-07 2014-04-08 Wells Fargo Bank, N.A. System and method for receiving ATM deposits
US9367224B2 (en) 2011-04-29 2016-06-14 Avaya Inc. Method and apparatus for allowing drag-and-drop operations across the shared borders of adjacent touch screen-equipped devices
WO2012150602A1 (en) 2011-05-03 2012-11-08 Yogesh Chunilal Rathod A system and method for dynamically monitoring, recording, processing, attaching dynamic, contextual & accessible active links & presenting of physical or digital activities, actions, locations, logs, life stream, behavior & status
WO2012155081A1 (en) * 2011-05-11 2012-11-15 Visa International Service Association Electronic receipt manager apparatuses, methods and systems
WO2012155005A1 (en) 2011-05-11 2012-11-15 Sierchio Joseph Universal interactive smart card device
US20120296726A1 (en) 2011-05-17 2012-11-22 Firethorn Mobile, Inc. System and Method For Managing Transactions With A Portable Computing Device
US20130204793A1 (en) 2011-05-17 2013-08-08 Kevin S. Kerridge Smart communication device secured electronic payment system
US20120296679A1 (en) 2011-05-20 2012-11-22 Imidus Technologies, Inc. Web integrated point-of-sale system
US20130138563A1 (en) 2011-05-26 2013-05-30 Global Standard Financial, Inc. Systems and methods for prepaid merchant payment services
BR112013031147A2 (en) 2011-06-03 2017-02-07 Visa Int Service Ass devices, methods and virtual wallet card selection system
US20130019284A1 (en) 2011-06-10 2013-01-17 Pacyga James W Automated web based applications with a wireless communication device
US10134023B2 (en) 2011-06-22 2018-11-20 Jpmorgan Chase Bank, N.A. System and method for division and management of expenses
US8498888B1 (en) 2011-06-22 2013-07-30 Amazon Technologies, Inc. Cost-based fulfillment tie-breaking
US20130179227A1 (en) 2011-07-22 2013-07-11 Rafter, Inc. System for and method of managing book sales and rentals
KR20130011821A (en) 2011-07-22 2013-01-30 삼성전자주식회사 Method and apparatus for providing transaction related service
US20130030889A1 (en) 2011-07-26 2013-01-31 PayPerks, Inc. Methods and Systems for Providing a Rewards Program
US9355394B2 (en) 2011-08-11 2016-05-31 Visa International Service Association Systems and methods of aggregating split payments using a settlement ecosystem
WO2013032613A1 (en) 2011-08-30 2013-03-07 Gregory Dorso Systems and methods for fast mobile payment
US20130339253A1 (en) 2011-08-31 2013-12-19 Dan Moshe Sincai Mobile Device Based Financial Transaction System
US20130103574A1 (en) 2011-10-19 2013-04-25 First Data Corporation Payment Delegation Transaction Processing
US9104771B2 (en) 2011-11-03 2015-08-11 International Business Machines Corporation Providing relevant product reviews to the user to aid in purchasing decision
US20130124327A1 (en) 2011-11-11 2013-05-16 Jumptap, Inc. Identifying a same user of multiple communication devices based on web page visits
DE202012100620U1 (en) 2011-11-22 2012-06-13 Square, Inc. System for processing non card payment transactions
US9727068B2 (en) 2011-11-28 2017-08-08 Melrok, Llc Energy search engine with autonomous control
WO2015112108A1 (en) 2012-11-28 2015-07-30 Visa International Service Association Multi disparate gesture actions and transactions apparatuses, methods and systems
US20140052617A1 (en) 2011-12-13 2014-02-20 Visa International Service Association Payment platform interface widget generation apparatuses, methods and systems
US9082129B2 (en) 2011-12-13 2015-07-14 Facebook, Inc. Providing recommendations on a social networking system page
US20130159172A1 (en) * 2011-12-14 2013-06-20 Ho Sup Kim Online remittance system and method using mobile terminal to provide tipping service or support service
US9094356B2 (en) 2011-12-15 2015-07-28 Visa International Service Association Supplemental alert system and method
US20130159173A1 (en) 2011-12-19 2013-06-20 Sridhar Sivaraman Shared Mobile Payments
US9053481B2 (en) 2011-12-21 2015-06-09 Mastercard International Incorporated Methods and systems for providing a payment account with adaptive interchange
US20150032567A1 (en) 2011-12-29 2015-01-29 Shashank Bhatia Collaborative, improved system and method for processing commercial transactions
US9027827B2 (en) 2012-01-16 2015-05-12 Qualcomm Incorporated System and method for providing a personalized shopping experience and personalized pricing of products and services with a portable computing device
WO2013116714A1 (en) 2012-02-01 2013-08-08 Ebay Inc. Automatically emailing receipt at pos
US20130202185A1 (en) 2012-02-08 2013-08-08 Scientific Games International, Inc. Method for optically decoding a debit or credit card
US8966092B2 (en) 2012-02-24 2015-02-24 Wyse Technology L.L.C. System and method for information sharing using near proximity communication
US9092776B2 (en) 2012-03-15 2015-07-28 Qualcomm Incorporated System and method for managing payment in transactions with a PCD
US20130248591A1 (en) 2012-03-22 2013-09-26 Veritec, Inc. Combined event driver and financial card
US8423459B1 (en) 2012-03-30 2013-04-16 Google Inc. Prioritizing potential transaction counter-parties with social network content
CA2870753A1 (en) 2012-03-30 2013-10-03 Ip Payovation Pty Ltd Payment apparatus and method
US8768831B2 (en) 2012-04-10 2014-07-01 Hossein Mohsenzadeh Systems, devices, and methods for managing a payment transaction
US20130290522A1 (en) 2012-04-11 2013-10-31 Edward F. Behm, Jr. Engine, System and Method of Locating a Mobile Device and Reporting on Other Devices Proximately Located Thereto
US20130290173A1 (en) 2012-04-26 2013-10-31 Jordan Michael Nemeroff Method, process and system for providing and receiving compensation or a gratuity through the internet
US20130290848A1 (en) 2012-04-27 2013-10-31 Mobitv, Inc. Connected multi-screen video
US20130317950A1 (en) 2012-05-23 2013-11-28 International Business Machines Corporation Customizing a three dimensional virtual store based on user shopping behavior
US20130317835A1 (en) * 2012-05-28 2013-11-28 Apple Inc. Effecting payments using optical coupling
US9892357B2 (en) 2013-05-29 2018-02-13 Cardlab, Aps. Method for remotely controlling a reprogrammable payment card
EP3379441A1 (en) 2012-06-11 2018-09-26 Samsung Electronics Co., Ltd. Mobile device and control method thereof
US20130332385A1 (en) 2012-06-11 2013-12-12 Yahoo! Inc. Methods and systems for detecting and extracting product reviews
US20140101737A1 (en) 2012-06-11 2014-04-10 Samsung Electronics Co., Ltd. Mobile device and control method thereof
US20130346223A1 (en) 2012-06-26 2013-12-26 Rajen S. Prabhu Processing point-of-sale transactions using a mobile card and mobile phone
US8855312B1 (en) 2012-06-29 2014-10-07 Emc Corporation Mobile trust broker
WO2014005059A1 (en) 2012-06-29 2014-01-03 Berry And Berry Innovations E-check device, system and method thereof
US20140012754A1 (en) 2012-07-06 2014-01-09 Bank Of America Corporation Financial document processing system
WO2014014954A1 (en) 2012-07-16 2014-01-23 Brackenridge Stephanie L Methods and system for processing customers through a point-of-sale system having a multiple-item price scanning apparatus
US20140032297A1 (en) 2012-07-24 2014-01-30 Joerg Germann Mobile device mediated handling of reward points redeemable towards local transportation
US8676709B2 (en) 2012-07-31 2014-03-18 Google Inc. Merchant category codes in a proxy card transaction
CN102843681A (en) 2012-08-15 2012-12-26 腾讯科技(深圳)有限公司 Information interaction method and information interaction device
US10028204B2 (en) 2012-08-24 2018-07-17 Blackberry Limited Supporting device-to-device communication in a rich communication service context
US9576283B2 (en) * 2012-08-27 2017-02-21 Wal-Mart Stores, Inc. Delivering customer specified receipt types at checkout
US20140067557A1 (en) 2012-08-31 2014-03-06 Inspiration LLC Method and system for online redistribution of data
US20140074655A1 (en) 2012-09-07 2014-03-13 David Lim System, apparatus and methods for online one-tap account addition and checkout
US20140081854A1 (en) 2012-09-11 2014-03-20 First Data Corporation Systems and methods for facilitating remote authorization and payment of goods via mobile commerce
US20140074691A1 (en) 2012-09-12 2014-03-13 International Business Machines Corporation Bill split for nfc transactions
US20140081783A1 (en) 2012-09-14 2014-03-20 Jagadish Bhalchandra Paranjape Push Payment Processor
US9092828B2 (en) 2012-09-19 2015-07-28 Mastercard International Incorporated Purchase Data sharing platform
US20140089078A1 (en) 2012-09-21 2014-03-27 Qualcomm Incorporated System and method for managing carbon emission credits at a fuel dispensing station using vehicle on-board diagnostics data
US20140089073A1 (en) 2012-09-21 2014-03-27 Qualcomm Incorporated System and Method For Managing Carbon Emission Credits at a Fuel Dispensing Station Via a Portable Computing Device
US8832783B2 (en) 2012-09-28 2014-09-09 Intel Corporation System and method for performing secure communications
US9088864B2 (en) 2012-10-09 2015-07-21 Brigham Young University Systems and methods for establishing secure communication using close proximity wireless communication
US9760958B2 (en) 2012-10-19 2017-09-12 Ncr Corporation Techniques for restaurant transaction processing
US20140122345A1 (en) 2012-10-31 2014-05-01 Wal-Mart Stores, Inc. Sharing of a receipt among mobile devices
US20140136318A1 (en) 2012-11-09 2014-05-15 Motorola Mobility Llc Systems and Methods for Advertising to a Group of Users
US9524500B2 (en) 2012-11-13 2016-12-20 Apple Inc. Transferring assets
US20140149282A1 (en) 2012-11-27 2014-05-29 AOL, Inc. Systems and methods for processing electronic transactions based on consumer characteristics
US10074082B2 (en) 2012-11-30 2018-09-11 Walmart Apollo, Llc Splitting a purchase among multiple parties using an electronic receipt after the transaction
US9010644B1 (en) 2012-11-30 2015-04-21 Dynamics Inc. Dynamic magnetic stripe communications device with stepped magnetic material for magnetic cards and devices
US10108951B2 (en) 2012-11-30 2018-10-23 Walmart Apollo, Llc Splitting a purchase among multiple parties using an electronic receipt after the transaction
US20140164234A1 (en) 2012-12-12 2014-06-12 Capital One Financial Corporation Systems and methods for splitting a bill associated with a receipt
US9298281B2 (en) 2012-12-27 2016-03-29 Correlated Magnetics Research, Llc. Magnetic vector sensor positioning and communications system
US10223710B2 (en) 2013-01-04 2019-03-05 Visa International Service Association Wearable intelligent vision device apparatuses, methods and systems
US9747632B2 (en) 2013-01-13 2017-08-29 Retail Technologies Corporation Store mobile cloud application system for inventory management and customer order fulfillment and method for retail establishment
US20140201067A1 (en) 2013-01-14 2014-07-17 Hooko Limited System and method for facilitating a transaction
US9438993B2 (en) 2013-03-08 2016-09-06 Blackberry Limited Methods and devices to generate multiple-channel audio recordings
US20140278589A1 (en) 2013-03-12 2014-09-18 Cellco Partnership (D/B/A Verizon Wireless) Mobile device establishment system
US20140279098A1 (en) 2013-03-15 2014-09-18 Brandon Ham Bill Splitting and Payment System and Method
US20150095228A1 (en) 2013-10-01 2015-04-02 Libo Su Capturing images for financial transactions
US20150100481A1 (en) 2013-10-08 2015-04-09 Mastercard International Incorporated Apparatus, method, and computer program product for tender type scaling using an on-line bill payment platform
US8892462B1 (en) 2013-10-22 2014-11-18 Square, Inc. Proxy card payment with digital receipt delivery
US9922321B2 (en) 2013-10-22 2018-03-20 Square, Inc. Proxy for multiple payment mechanisms
US20150120418A1 (en) 2013-10-28 2015-04-30 Visa International Service Association Systems and methods to provide rewards based on purchased items
US20150134439A1 (en) 2013-11-08 2015-05-14 Square, Inc. Interactive digital receipt
US20150134528A1 (en) 2013-11-11 2015-05-14 Visa International Service Association Systems and methods to facilitate the redemption of offer benefits in a form of third party statement credits
US20150178755A1 (en) 2013-12-19 2015-06-25 Lanny Barroso Systems and methods for consumer driven marketing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7818809B1 (en) * 2004-10-05 2010-10-19 Symantec Corporation Confidential data protection through usage scoping
US20090106138A1 (en) * 2007-10-22 2009-04-23 Smith Steven E Transaction authentication over independent network
US20130236109A1 (en) * 2012-03-07 2013-09-12 The Western Union Company Identification generation and authentication process application
US20140257958A1 (en) * 2013-03-05 2014-09-11 Google Inc. Merchant incentive programs on proxy card systems

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10192220B2 (en) 2013-06-25 2019-01-29 Square, Inc. Integrated online and offline inventory management
US10229414B2 (en) 2013-06-25 2019-03-12 Square, Inc. Mirroring a storefront to a social media site
GB2545987A (en) * 2015-11-19 2017-07-05 Wal-Mart Stores Inc Systems and methods for flexibly securing card data

Also Published As

Publication number Publication date
US20180150807A1 (en) 2018-05-31
US9652751B2 (en) 2017-05-16
US20150332237A1 (en) 2015-11-19
WO2015179316A1 (en) 2015-11-26
AU2015264426A1 (en) 2016-12-15
AU2018205104A1 (en) 2018-07-26

Similar Documents

Publication Publication Date Title
AU2009296435C1 (en) Real-time statement credits and notifications
US8799060B2 (en) Method for electronic coupon creation, deployment, transference, validation management, clearance, redemption and reporting system and and method for interactive participation of individuals and groups with coupons
US9135619B1 (en) Merchant identification of payer via payment path
US20130085930A1 (en) System and method for processing gift cards by intercepting a purchasing transaction
US7992781B2 (en) Merchant alerts incorporating receipt data
US20100299195A1 (en) Systems and methods for implementing financial transactions
US8738429B2 (en) Platform for loyalty services
US9436942B2 (en) Flexible mobile gift cards
AU2012209213C1 (en) Systems and methods to facilitate loyalty reward transactions
US8266031B2 (en) Systems and methods to provide benefits of account features to account holders
US20070150411A1 (en) Universal payment system
US20140025451A1 (en) Enhanced transaction processing
US8751295B2 (en) System and method for providing international coupon-less discounts
US20140074569A1 (en) Systems and methods for facilitating loyalty and reward functionality in mobile commerce
US8788333B2 (en) Method, apparatus, and computer program product for facilitating promotions with an E-wallet
US20060253321A1 (en) Loyalty enrollment systems and methods
US20110191150A1 (en) Mobile integrated merchant offer program and customer shopping using product level information
US20130191195A1 (en) Systems and methods to present and process offers
US20110231235A1 (en) Merchant Configured Advertised Incentives Funded Through Statement Credits
US20170053302A1 (en) System and method for targeted marketing and consumer resource management
AU2013249184B2 (en) Systems and methods to use transaction authorization communications to process offers
US20120150611A1 (en) System and method for processing financial transactions
US8489456B2 (en) Consumer offer redemption methods and systems
US20130332362A1 (en) Systems and methods to customize privacy preferences
US20090112767A1 (en) Escrow system and method

Legal Events

Date Code Title Description
AS Assignment

Owner name: SQUARE, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AARON, PAUL;BROCK, ZACHARY;SIGNING DATES FROM 20140929 TO 20170516;REEL/FRAME:042739/0488