Interactive digital platform

Information

  • Patent Grant
  • 10217092
  • Patent Number
    10,217,092
  • Date Filed
    Friday, November 22, 2013
    12 years ago
  • Date Issued
    Tuesday, February 26, 2019
    6 years ago
Abstract
A technique is disclosed for generating an interactive digital receipt on a user device, where the receipt offers an engagement platform for merchants and customers to interact on a continuous basis. The interactive digital receipt is generated in response to an occurrence of a particular financial transaction. The receipt includes a plurality of time-based interactive components to enable the merchant and the customer to interact with one another. The plurality of time-based interactive components includes a promotion component, a tipping component, a feedback component, and a loyalty rewards component. Each component is associated with a timeframe which defines a time period for which the customer may interact with the component. Content presented via each component changes corresponding to the time period. The time period can range from a limited time period to an unlimited time period.
Description
BACKGROUND

Due to the increasing popularity and acceptance of the computer and mobile devices, more and more financial transactions between merchants and customers are being conducted electronically. Many merchants have started to provide their customers with receipts electronically to maintain record of the financial transactions. For example, some merchants may provide a receipt through delivery of an electronic mail (i.e., e-mail). In another example, some merchants may make the receipt available through an online customer account on a merchant website. Various solutions are currently available to provide such receipt electronically, such as building an internal solution specific to a merchant's point of sale (POS) system or integrating with a third party solution into the merchant's POS.


The existing receipt solutions, however, are often limited in functionality and present many issues for both merchants and customers. For a customer, the receipts from the different merchants often get delivered in different ways (e.g., format, delivery method, etc.), and as such the customer is unable to manage the receipts digitally. For a merchant, a highly customized infrastructure change to existing POS system is needed in order to have a receipt solution that fits the merchant's needs; the merchant may not be ready to make such changes based on the business size, the cost, and/or the required technical knowledge. Further, the efforts required for such changes do not translate well in terms of a return on investment; the existing digital receipt solutions merely provide a record for the transactions, and nothing more.


Accordingly, a more robust, versatile system for providing a receipt electronically is needed.





BRIEF DESCRIPTION OF THE DRAWINGS

One or more embodiments of the present invention are illustrated by way of example and are not limited by the figures of the accompanying drawings, in which like references indicate similar elements.



FIGS. 1A-1B illustrate a first embodiment of an interactive digital receipt technique implemented on a user device.



FIGS. 1C-1E illustrate a second embodiment of an interactive digital receipt technique implemented on a user device.



FIGS. 1F-1H illustrate a third embodiment of an interactive digital receipt technique implemented on a user device.



FIG. 1I illustrate a fourth embodiment of an interactive digital receipt technique implemented on a user device.



FIG. 2 illustrates a flow diagram of a process for implementing an interactive digital receipt technique on a user device.



FIG. 3 illustrate a screenshot of a receipts dashboard for managing interactive digital receipts implemented on a user device.



FIG. 4 illustrates a screenshot of an engagement dashboard for managing merchant engagements with customers.



FIG. 5 illustrates a screenshot of a feedback dashboard for managing customer feedback.



FIG. 6 illustrates an environment in which the techniques disclosed herein may be implemented.





DETAILED DESCRIPTION

Introduced herein is a technique to provide an interactive digital receipt implemented on a user device, where the receipt offers an interactive platform for merchants and customers to interact on a continuous basis. The interactive digital receipt can be embodied in a text message, an electronic mail (e-mail), or a mobile software application. The interactive digital receipt is generated in response to an occurrence of a particular financial transaction between a merchant and a customer, such as a payment transaction conducted at a completion of service and/or goods provided by the merchant. The financial transaction may be an electronic transaction conducted over the Internet or a card present point-of-sale (POS) transaction where the customer/buyer/payer makes the purchase at a store front, other “brick-and-mortar” location, or simply in the presence of a merchant/payee.


Once the financial transaction takes place (i.e., the payer tenders payment to the payee), the interactive digital receipt is generated to provide the customer with an electronic record of the transaction. In addition to providing the transaction record, the interactive digital receipt provides one or more time-based engagements, or interactive components, to enable the merchant and the customer to engage, or interact, with one another. The time-based engagements include one or more features that are configured to be available (i.e., offered via the interactive receipt) to the user for a limited, predefined time period, allowing the engagements, or the interactions, to take place only until the expiration of the time period.


In some instances, the disclosed technique provides a time-based engagement that includes a gratuity payment feature to allow the customer to add a gratuity amount (i.e., “tip”) on top of a payment amount for a purchase from a particular merchant. The gratuity payment feature allows the customer to tip the merchant after the time of the actual transaction, or purchase. The merchant may set the time limit at which the interactive receipt (for the purchase) is open for receiving the gratuity amount from the customer. The customer may set a nominal gratuity amount to operate as a default amount to be paid to the merchant if no gratuity is added after a predefined time limit. For example, such nominal gratuity amount may be set for a particular favorite merchant of the customer; that is, the customer desires to always tip a nominal amount even he/she forgets to add such amount after a transaction. The time-based gratuity payment feature is beneficial, for example, when the customer has forgotten to tip and desires to tip after he/she has already made the payment and left the merchant's store. The nominal gratuity amount may also be set by the merchant. This is beneficial in scenarios involving special services and/or goods. For example, a restaurant merchant sets a default 25% tip for any transaction involving 10 or more parties dining at the restaurant.


In some instances, the disclosed technique provides a time-based engagement that includes a feedback feature to allow the customer to leave a review (e.g., a write-up, a rating, etc.) for a particular merchant after a transaction is completed. The feedback feature is offered to the customer only within a predefined time period. The merchant may configure the predefined time period. For example, the time period can be an hour, a day, or a week after a payment transaction (e.g., a restaurant visit) has completed. The merchant may configure the predefined time period to be tied to an incentive. For example, the customer is rewarded a 20% Off Coupon via the interactive receipt for submitting a review within an hour of the transaction completion time. Such time-based feedback feature is beneficial, for example, when the merchant wants to increase visibility of the merchant venue (i.e., through reviews), to incentivize the customer to act more quickly in submitting the feedback, and/or to manage the collection of feedback more effectively and in a timely manner (e.g., allowing a review six days after the service is likely ineffective).


In some instances, the disclosed technique provides a time-based engagement that includes a time-based promotion feature to incentivize the customer to interact with a particular merchant within a predefined time period. The time-based promotion feature offers the customer a particular promotional reward associated with the merchant and/or the purchase, where the promotional reward reduces, or decreases in value, corresponding to a decrease in a passage of time. For example, a promotional $10 coupon is generated via the interactive receipt the moment a particular payment transaction has occurred between Store A and Customer X, where the coupon is redeemable at Store B, which is affiliated with Store A, if the coupon is redeemed at Store B within 24 hours. In such example, the $10 value of the promotional coupon decreases based on how long it has been since the transaction at Store A has completed; the value ultimately decreases to $0 in accordance with the passage of time. In this example, the sooner the customer redeems the $10 coupon, the higher the value he/she gets to redeem.


The customer may redeem the time-based promotional reward by completing various redemption (or “promotional”) activities. Some promotional activities include simply revisiting the merchant to make another purchase for goods and/or services. Some promotional activities include participating in a game via the user device. Some promotional activities include visiting another affiliated merchant (e.g., affiliated store, affiliated website, etc.). The promotional activity and the decreasing rate of the promotional reward may be configured by the merchant offering the reward. Such time-based promotional reward feature is beneficial, for example, when the merchant wants to promote certain products or services and/or to engage the customers by offering certain incentives to act more quickly. The customer, on the other hand, benefits, for example, by getting more relevant merchant rewards (e.g., discounts at the merchant's store or affiliated stores).


In some instances, the disclosed technique provides a time-based engagement that includes a loyalty rewards record for the customer, where the loyalty rewards record is associated with every transaction conducted over time between the customer and a particular merchant. The loyalty rewards record (or “rewards record”) tracks the purchases and/or services made by the customer from the particular merchant, and uses the tracking to log reward points for the customer being a “loyal customer.” The rewards record enables the merchant, for example, to reward the customer for purchases (e.g., a free beverage for every 10 beverages bought) and enables the customer, for example, to receive an elite membership status for purchases made within a predefined time period (e.g., 10 beverages bought within a week).


In some instances, the disclosed technique provides a particular customer an interactive transaction record containing all interactive digital receipts of transactions between the particular customer and one or more merchants. The interactive transaction record organizes the interactive digital receipts based on time, location, and merchant. The interactive transaction record is updated along with each new interactive digital receipt that gets generated and or updated. Further, the interactive transaction record allows the customer to access each interactive digital receipt. This can be beneficial when the customer wants to revisit a record for a particular transaction. For example, if a customer wants to review and add a gratuity amount to a payment transaction completed recently, he can access the interactive transaction record to search for the particular transaction and add on a tip to the payment authorization for that transaction.


In some instances, the disclosed technique provides a user interface for a particular merchant to configure various time-based engagements that may be offered via the interactive digital receipts on the user devices of one or more customers. In some instances, the interface allows the merchant to create one or more customized templates for the interactive digital receipts of particular customers. As such, the disclosed technique allows the merchant to dynamically change what is being offered, or displayed, on the user device of the frequent customer.


Other aspects and advantages of the disclosed technique will become apparent from the following description in combination with the accompanying drawings, illustrating, by way of example, the principles of the claimed technique.



FIGS. 1A-1B illustrate a first embodiment of an interactive digital receipt technique implemented on a user device 100. As used herein, the term “user device” refers to any general-purpose computing device capable of data processing. In one example, the user device can be a mobile device, such as 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. In another example, the user device can be a personal computing device, such as a desktop, a laptop, or other wired and wireless personal computers. The user device 100 is equipped with a display screen 102 for displaying various user interfaces to enable a user to interact with content generated by the user device 100.


The user device 100 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. As used herein, a “customer interface component” is a component of a user interface intended for a customer to view and interact with an interactive digital receipt 104. The interactive digital receipt 104 is generated for the customer after an occurrence of a financial transaction between the customer and a merchant (e.g., payment that occurs at the completion of a service and/or tendering of goods), where the interactive digital receipt 104 is displayed on the display screen 102 of the user device 100. It is noted that the interactive digital receipt 104 may take up an entirety or any portion of the display screen 102.


Referring to FIGS. 1A and 1B, the interactive digital receipt 104 includes various interactive components, such as a customer transaction interface component 106 (“transaction component”) and one or more customer engagement interface components 108 (“engagement component”). The transaction component 106 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). For example, when the customer has made a payment to the merchant, the interactive digital receipt is automatically generated on the user device 100, and included on the receipt are details of the purchased items and prices generated by the transaction component 106.


The one or more engagement components 108 displays in real time one or more features for the merchant and the customer to interact or engage with one another. The features generated are configured to be available via the interactive digital receipt 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 to interact with the merchant. Further details regarding the engagement components and the transaction component will be discussed in FIGS. 1C-1H.



FIGS. 1C-1E illustrate a second embodiment of an interactive digital receipt technique implemented on a user device 100. As illustrated in FIG. 1C, the interactive digital receipt 104 includes an engagement, or interactive, component for generating a tipping feature 110. The tipping feature 110 allows the customer the option to add a gratuity amount (i.e., “tip”) after the occurrence of a particular transaction with a merchant (e.g., tendering or completion of a payment for goods and/or service); such a transaction may be, for example, payment for a meal at a restaurant visit, where the customer is able to leave a tip after he/she has left the restaurant. The tipping feature enables any tip added by the customer to be directly transmitted to the payment system, without any human interference. For example, after the customer has tendered his credit card to the merchant to pay for a meal, the interactive digital receipt is generated on the customer's mobile device. Using the mobile device, the customer can then proceed to add a tip, and such tip (e.g., credit card authorization of the tip) is directly sent to the payment system to be added together with the already authorized payment amount, without the merchant having to physically enter and submit the tip authorization to the payment system.


The tipping feature 110 may be embodied in the interactive digital receipt in a variety of ways, as illustrated in FIG. 1D. In one example, the interactive digital receipt is a text message 120. In such example, upon receiving the receipt via text, a user can add on a tipping amount to the transaction by replying to the text message 120 and entering a number (e.g., “2.00” for a $2.00 tip). In another example, the interactive digital receipt is displayed as part of a user interface associated with a mobile application (“App”). In such example, the tipping feature 110 is a text box 122A within the interactive receipt (e.g., interactive receipt 104), and the user can add on a tipping amount by entering a number directly in the text box. The tipping feature 110 embodied within the App may also be a user interface component 122B with default tip amounts displayed to the user. The default amounts can be configured to change based on the payment amount associated with the transaction (e.g., an amount equivalent to 15%, 20%, etc.). The user can quickly add the tipping amount by clicking on any of the default amounts displayed. In yet another example, the interactive digital receipt is a Uniform Resource Locator (URL) link 124 which takes the user to a web page to allow adding of the tipping amount. The link 124 can be a part of the text message 120, a part of the text box 122A, the component 122B, or an electronic mail (e-mail).


The tipping feature 110 is configurable in various ways to implement various functionalities. In one embodiment, the tipping feature is configured to be available at any time, and for an unlimited time period, starting after a time instance when payment has been authorized (e.g., after the customer has authorized the payment amount using his/her credit card to pay the merchant). In one embodiment, the tipping feature 110 is configured to be available only for a limited, predefined time period, or timeframe, after the authorization for the payment amount has been granted by the customer. As used herein, the term “timeframe” refers to a time limit during which the tipping feature remains available for receiving a gratuity amount authorization from the customer. The timeframe may be, for example, an hour, a day, a week, or any other desired time period (e.g., unlimited). In some embodiments, the timeframe is configured by the merchant. In other embodiments, the timeframe is configured by an operator of the interactive digital receipt system.


The timeframe of the tipping feature 110 is initialized, or started, at a time instance at which the transaction between the customer and merchant has occurred (i.e., a tender of payment has been completed). The timeframe decreases incrementally, from this time instance, at a rate that corresponds to an ordinary passage of time. For example, once a customer submits a payment (e.g., authorizes payment amount via a debit card), an interactive digital receipt is generated for the customer and the timeframe for tipping associated with that receipt is initialized (i.e., the countdown starts) at the moment the receipt is generated. At the expiration of the timeframe (i.e., the countdown reaches 0), the tipping feature becomes unavailable to the customer (e.g., the feature becomes an invalidated feature). In a real-world setting, such time limitation helps the merchant manage its financial transactions more efficiently. For example, a merchant often processes its financial transactions in batches and would not want to keep any particular transaction open indefinitely.


In one embodiment, the timeframe of the tipping feature 110 may be configured to incorporate a user definition of a default gratuity amount. In particular, a user of the user device 100, such as a customer, may define a nominal gratuity amount to be automatically paid to certain merchants if no gratuity amount is submitted at the expiration of the timeframe. For example, a customer defines the gratuity amount to be $10 for the customer's favorite restaurant. In such example, the $10 tip is automatically authorized for any transaction with that restaurant whenever no gratuity amount is added at the timeframe expiration. The customer can also define the nominal gratuity amount to be zero. In some embodiments, the default gratuity amount may be defined by the merchant. For example, a restaurant merchant may want to configure a nominal gratuity amount to be defined 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 timeframe (e.g., 2 hours), an automatic 20% of the payment amount is authorized on the customer's payment card as the tip amount, and the 20% tip amount gets added in the final transaction payment.


Referring to FIG. 1E, the interactive digital receipt 104 can include two transaction components 106A, 106B, in addition to the tipping feature 110. The transaction component 106A 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., last four digits of a credit card), the date, or the like. The transaction component 106B includes the details of the transaction, such as the name of the items purchased, the quantity, the price, or the like.



FIGS. 1F-1H illustrate a third embodiment of an interactive digital receipt technique implemented on a user device 100. As illustrated in FIG. 1F, the interactive digital receipt 104 can include an engagement, or interactive, component that contains a feedback feature 112. The feedback feature 112 allows the customer (i.e., payer, consumer, or the like) to submit feedback after the completion of a particular transaction with a merchant (i.e., payee). 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, the interactive digital receipt system coordinates, communicates, and links with third party services associated with the merchant in implementing the feedback feature 112. In such embodiments, the feedback is transmitted to the third party services upon submission via the interactive digital receipt. 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 an illustrative example, the feedback feature 112 provides an option for the customer to submit indirectly a write-up review to Yelp.com by using the feedback feature 112. In such example, the customer can write the review in a text box within the interactive receipt and the review is transmitted to Yelp® when the customer clicks Submit.


In one embodiment, the feedback feature 112 is configurable to be available only for a predefined time period, or timeframe. In some embodiments, the timeframe associated with the feedback feature 112 (“feedback timeframe”) is configured to be the same as the timeframe associated with tipping feature 110 (“tipping timeframe”). For example, the timeframe may be set at one hour and at the expiration of the hour, both the tipping feature and the feedback feature are made unavailable to the customer. In some embodiments, the feedback timeframe is configured to be different from the tipping timeframe. For example, the feedback timeframe may be set at one week while the tipping timeframe may be set at one hour. In such example, at the expiration of the tipping timeframe, a customer may still be able to submit feedback for the corresponding transaction.


In some embodiments, the feedback timeframe is configured by an operator of the interactive digital receipt system. For example, the feedback timeframe can be configured to be the same for all participating merchants of the interactive digital receipt system. In other embodiments, the feedback timeframe is configured by a particular merchant. For example, the merchant can configure the feedback timeframe to be one day, one week, or any desired amount.


In one embodiment, a particular merchant may configure the feedback timeframe to be tied to an incentive (i.e., “feedback reward”) for encouraging submission of a feedback. The incentive may be based on a time of submission of the 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 timeframe, e.g., within an hour after the time of completion of a transaction. In another example, if the feedback is submitted within 10 minutes after the completion of the payment transaction between the user and the remote user, the reward is a 20% Off coupon; on the other hand, if the feedback is submitted within 12 hours, but not exceeding the transaction timeframe allowed for the feedback (e.g., 24 hours), the reward is a 5% coupon.


The feedback feature 112 may be provided in the interactive digital receipt 104 in various configurations, as illustrated in FIGS. 1F-1G. Referring to FIG. 1G, the feedback feature 112 can be provided along with contents from the transaction component 106 and another engagement 108. Referring to FIG. 1H, the feedback feature 112 can be provided along with the tipping feature 110. The features 110, 112 may 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 the feedback feature 112 without generating the tipping feature 110. In another example, a merchant in the business of operating a restaurant can choose to have both the tipping feature 110 and the feedback feature 112 be generated in the interactive digital receipt 104. One of ordinary skill in the art will appreciate that other configurations are possible.



FIG. 1I illustrate a fourth embodiment of an interactive digital receipt technique implemented on a user device. As illustrated in FIG. 1I, the interactive digital receipt 104 includes an engagement, or interactive, component for generating a promotional reward feature 114. The promotional reward feature 114 allows a particular merchant to engage and incentivize a customer to interact with the merchant within a predefined time period, or timeframe. In some embodiments, the timeframe associated with the promotional reward feature 114 (“promotion timeframe”) is configured to be the same as the timeframe associated with the feedback feature 112 (“feedback timeframe”), or the timeframe associated with the tipping feature 110 (“tipping timeframe”), or both. For example, the timeframe may be set at one hour, and at the expiration of the hour, the promotional reward feature, the feedback feature, and the tipping feature are all made unavailable to the customer. In some embodiments, the promotion timeframe is configured to be different from each of the feedback timeframe and the tipping timeframe.


The time-based promotional feature 114 offers the customer a particular promotional reward (or “promotion”) associated with the merchant and/or the transaction completed, where the promotional reward reduces, or decreases in value, corresponding to a decrease in the passage of time associated with the timeframe. For example, a $10 coupon is generated via the interactive digital receipt the moment a restaurant payment transaction occurs (e.g., authorization of payment amount is completed). The coupon promotes the restaurant by offering the customer $10 off on a next meal at the restaurant. Such $10 coupon decreases in value from the moment the coupon is generated; ultimately, the coupon decreases to a $0 value unless the customer redeems the coupon (e.g., by buying another meal at the restaurant). As such, the sooner the customer redeems the time-based coupon, the higher the value he/she gets to redeem.


The merchant may configure the rate of the reduction in value and/or the timeframe associated with the promotional reward. In one example, the restaurant sets the $10 coupon to expire after a week, with no reduction in value at all as long as the coupon is redeemed at the end of the week. 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. The value may reduce in accordance with the passage of time or it may reduce according to a rate set by the merchant. For example, the value decreases at an exponential rate.


In some embodiments, the customer may redeem the time-based promotional reward by completing various redemption, or promotional, activities. 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 user device. Some redemption activities include participating in activities with other merchants affiliated with the merchant that offers the promotional reward. For example, the original merchant may offer a 15% Off Coupon, yet that coupon is redeemable only at the original merchant's affiliated store. 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.


The promotional feature 114 may be provided in the interactive digital receipt 104 in various configurations. As illustrated in FIG. 1I, the promotional feature may be combined with the tipping feature 110 and the feedback feature 112. One of ordinary skill in the art will appreciate that other configurations are possible.


Other engagements, or interactive components, not shown in FIGS. 1-1I may also be implemented via the interactive digital receipt displayed on the user device. In one embodiment, the engagement includes an interactive transaction record. The interactive transaction record includes one or more interactive digital receipts that has resulted from one or more financial transactions belonging to the customer. A particular interactive record may be configured to include only interactive digital receipts associated with a particular merchant. A particular interactive record may be 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 his/her interactive digital receipts and provides a comprehensive view of all payment transactions.


In one embodiment, the engagement includes an interactive advertisement component (e.g., promotion for product and/or service) to catch the user's attention using advertisement with various content. Such advertisement may include, for example, the promotional reward feature 114 to entice the user to “click-on” or select a particular offering being displayed on the display screen. In yet another example, the advertisement may be 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 may be related to the completed transaction for which the receipt 104 is 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.


The engagement, in another example, can include a loyalty rewards record associated with the customer and a particular merchant. The loyalty rewards record (or “rewards record”) tracks and updates purchases and/or services completed with the merchant over time and maintains a membership status of the customer in relation to the merchant. Reward points are stored and updated in the rewards record for purchases and/or services transacted with the merchant within a predefined time period. For example, the rewards record tracks the number of baked goods bought from a bakery and updates the customer to an “elite status” in relation to that bakery for buying 10 items within 5 days. The customer, with the elite status evident on his/her rewards record, can redeem for a reward with the bakery. Other customer engagements (or interactive components) not discussed above, but consistent with the techniques discussed throughout, may also be envisioned by one of ordinary skill in the art.



FIG. 2 illustrates a flow diagram of a process 200 for implementing an interactive digital receipt technique on a user device. The user device may be the user device 100 of FIGS. 1A-1I. In some embodiments, the process 200 is implemented by the user device. In some embodiments, the process 200 is implemented by an interactive digital receipt system, such as the system 602 of FIG. 6. The interactive digital receipt system may be implemented as a mobile application on the user device, such as a smartphone.


At step 202, the user device receives a signal indicating that a financial transaction, such as a payment transaction, between a user of the user device (e.g., a customer, a payer, a buyer, etc.) and a remote user (e.g., a merchant, a seller, etc.). The signal may be communicated, or transmitted, from the remote user's POS system to indicate that the user has made a payment to the remote user (i.e., to indicate that the transaction has been completed). At step 204, the user device generates an interactive digital receipt to provide an electronic record of the transaction that has been completed between the user and the remote user. The interactive digital receipt may be the receipt 104 of FIGS. 1A-1I. The interactive digital receipt is configured to be a “living” digital receipt that continues to be maintained and updated on the user device. The receipt allows the user to engage in one or more engagements, or interactions, associated with the transaction, even after the transaction has been completed (i.e., payment has been tendered). The one or more engagements provided on the receipt are time-based and may be configured by the remote user, the user, or a combination thereof, as discussed above in the descriptions of FIGS. 1A-1I.


At step 206, the user device initializes a transaction timeframe to count down in response to the interactive digital receipt being generated; that is, the transaction timeframe starts decreasing incrementally until it reaches a null value once the receipt is generated. At step 208, the user device displays the interactive digital receipt on a display screen of the user device. The interactive digital receipt includes one or more engagements being displayed to the user on the display screen.


In one embodiment, the engagements includes a gratuity option that allows the user the capability to authorize a gratuity amount (or “tip”) after the payment amount has been tendered, such as a credit card authorization of the payment amount (i.e., at step 202). The gratuity option allows any tip added by the user to be directly transmitted to the payment system. For example, once a restaurant patron has given the waiter her credit card to pay for the meal, the patron can add the tip amount by herself without needing the waiter to physically enter the additional tip amount into the payment system. In such example, the patron can simply add the tip on top of the original meal amount via the interactive digital receipt, and the additional credit card authorization is directly sent to the payment system; with the gratuity option available, the patron may choose to add the tip while she is still present at the restaurant or after she has left the restaurant.


As discussed above, in one embodiment, the gratuity option is available to the user for an indefinite time. In another embodiment, the gratuity option is limited by the transaction timeframe. In such embodiment, the user must utilize the gratuity option within the transaction timeframe, i.e., before the timeframe reaches the null value. When the timeframe reaches the null value, the gratuity option is disabled and the user is no longer able to authorize an additional transaction amount for gratuity. The timeframe may be configured to be an unlimited time period (i.e., no expiration).


As discussed above in FIGS. 1A-1I, the gratuity option may be provided, or displayed, via the interactive receipt along with other engagements, or interactive components, such as a time-based feedback option, a time-based promotional reward, and/or a rewards record. Accordingly, as discussed above, the transaction timeframe associated with the engagement(s) provided via the receipt may include one or more different timeframes for each type of engagement being displayed on the interactive digital receipt (e.g., tipping timeframe, promotion timeframe, feedback timeframe, etc.).


At step 210, the user device determines whether the transaction timeframe has reached a null value, i.e., “0” time left. If time still remains, then the device continues to display the engagements to engage the user, as indicated in step 208. If no time remains, the user device processes the transaction, as indicated in step 212. Processing the transaction may include updating the interactive digital receipt based on the user's interactions with the one or more engagements displayed on the display screen.


In one embodiment, processing the transaction at step 212 may include transmitting to the remote system (e.g., payment system) an additional payment authorization for a gratuity amount (or “tip”) submitted by the user. In one example, the user may have chosen to interact with the gratuity option displayed at step 208 to add the gratuity amount to the transaction. In another example, the user may have predefined a nominal gratuity amount to be automatically authorized when no gratuity amount is added for a transaction with the remote user. However, if the user does not choose to interact with the gratuity option and/or to define a nominal gratuity amount, no additional payment authorization step is carried out in step 212.


In one embodiment, processing the transaction at step 212 may include updating the remote user's database with feedback completed by the user via the interactive digital receipt. The processing may also include transmitting to the user an incentive reward for completing (i.e., submitting) the feedback. As discussed above, the incentive reward may be based on a time of submission of the feedback.


In one embodiment, processing the transaction at step 212 may include processing for the user (e.g., customer) a time-based reward for completing a redemption activity associated with the remote user (e.g., merchant). The time-based reward may be maintained and accessed via the interactive digital receipt, where the user may choose to use the reward at any time after the redemption activity has been completed.


In one embodiment, processing the transaction at step 212 may include updating one or more records associated with the user. Updating the records may include updating the user's loyalty rewards record and updating the user's interactive transaction record. The interactive transaction record includes one or more interactive digital receipts resulting from one or more financial transactions belonging to the user. A particular interactive record may be configured to include only interactive digital receipts associated with a particular merchant. A particular interactive record may be configured to include all interactive digital receipts associated with the user, including receipts associated with different merchants with whom the user has transacted.


Updating the user's loyalty rewards record may include analyzing details of the transaction between the user and the remote user (i.e., the completed transaction of step 202). Analysis of such details allows the user device to update the quantity of a particular item the user has transacted with the remote user (e.g., 3 purchased beverages) and update the user's membership status.


Updating the user's interactive transaction record may include adding the interactive digital receipt associated with the completed transaction to a list of existing interactive digital receipts. The interactive transaction record may be stored on the user device.



FIG. 3 illustrate a screenshot of a receipts dashboard 300 for managing interactive digital receipts. The receipts dashboard 300 may be embodied as the interactive transaction record discussed above. The receipts dashboard 300 may be implemented on a user interface of a user device (e.g. user device 100 of FIGS. 1A-1I) to allow a user (e.g., a customer, a payer, a buyer, etc.) to view a list of interactive digital receipts. The interactive digital receipts are associated with one or more completed financial transactions between the user and one or more merchants.


Referring to FIG. 3, the receipts dashboard 300 includes a search feature 302 and a selection feature 304. The interactive digital receipts may be viewed and/or organized by using the selection feature 302 to select an organization based on a time, a merchant, an item type, or a transaction amount. The user may search for a particular interactive digital receipt using the search feature 304.



FIG. 4 illustrates a screenshot of an engagement dashboard 400 for managing merchant engagements with customers. The engagement dashboard 400 may be part of a user interface implemented on a merchant computing system, such as the merchant transaction system 606 of FIG. 6. The engagement dashboard 400 is connected to an interactive digital receipt system (e.g., the system 602 of FIG. 6) that is configured to generate one or more interactive digital receipts on a user device of a customer.


The engagement dashboard 400 enables the merchant to customize various time-based engagements that may be offered via the interactive digital receipt to the customer. Using the engagement dashboard 400, the merchant may dynamically change the engagement type that is generated, or displayed, to a particular customer at the completion of every transaction. Further, the merchant may choose between different templates of a particular engagement type to be displayed. Such dynamic capability enables the merchant to utilize the interactive digital receipt according to the business needs of the merchant. For example, for a frequent customer, the merchant may choose to generate a coupon in place of a feedback invitation, which is customarily offered as the default engagement to customers. In such example, the coupon is more suited for the frequent customer who may have already submitted many feedbacks.



FIG. 5 illustrates a screenshot of a merchant feedback dashboard 500 for managing customer feedback. merchant feedback dashboard 500 may be part of a user interface implemented on a merchant computing system, such as the merchant transaction system 606 of FIG. 6. The merchant feedback dashboard 500 is connected to an interactive digital receipt system (e.g., the system 602 of FIG. 6) that is configured to generate one or more interactive digital receipts on a user device of a customer. The merchant feedback dashboard 500 collects and analyzes data extracted from the feedback submitted through one or more interactive digital receipts. A particular merchant may utilize content from the feedback dashboard 500 to improve the merchant's business needs. For example, the feedback dashboard 500 may be integrated with the merchant engagement dashboard 400 to automatically generate appropriate engagements for the interactive digital receipts.



FIG. 6 illustrates an environment 600 in which the techniques disclosed herein may be implemented. The environment 600 includes an interactive digital receipt system 602, a customer device 604, and a merchant transaction system 606. As illustrated in FIG. 6, the interactive digital receipt system 602 is operatively coupled, via a network 608, to the customer device 604 and the merchant transaction system 606. In this way, the interactive digital receipt system 602 can send and receive information, to and from the merchant transaction system 606 and the customer device 604, to facilitate generating an interactive digital receipt for one or more financial transactions between the merchant and the customer. It is noted that FIG. 6 illustrates only one example of an embodiment of the environment 600, and it will be appreciated that in other embodiments, the environment may include more or fewer components and that the components may have a different configuration. Further, the various components shown in FIG. 6 may be implemented by using hardware, software, firmware or a combination thereof, including one or more signal processing and/or application specific integrated circuits.


Referring to FIG. 6, the network 608 may be a communication network based on certain communication protocols, such as TCP/IP protocol. Such network may include, but is not limited to, Internet, Intranet, wide area network (WAN), local area network (LAN), wireless network, Bluetooth, WiFi, and mobile communication network. The physical connections of the network and the communication protocols are well known to those of skill in the art.


The interactive digital receipt system 602 includes a processor 610, communications circuitry 612, an input/output interface 614, and a memory 616. These components may be coupled by one or more communication buses or other signal lines. It is noted that the system 602 can include more or fewer components.


The processor 610 includes one or more processors. The processor 610 is operatively coupled to the communication circuitry 612 and the memory 616. The processor 610 may include a digital signal processor, a microprocessor, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations thereof. The processor may be configured to execute computer/machine readable and executable instructions stored in the local memory 616 or in a remote device memory (not shown). Such instructions are implemented by the processor 610 to perform one or more functions described above. In performing such functions, the processor 610 uses the communication circuitry 612 to communicate with the network 608 and other devices on the network 608, such as the merchant transaction system 606 and the customer device 604.


The communications circuitry 612 includes RF circuitry and/or port for sending and receiving information. The RF circuitry permits transmission of information over a wireless link or network to one or more other devices and includes well-known circuitry for performing this function. For example, the RF circuitry may enable WiFi, cellular, Bluetooth, Bluetooth low energy, global positioning system (GPS), near field communication (NFC), or other types of long range or short range communication. The port permits transmission of information over a wired link. The communications circuitry may communicate, for example, with the merchant transaction system 606.


The memory 616 includes one or more memories. The one or more memories may be, for example, cache memory, main memory and secondary memory. The memory 616 includes computer-readable instructions 618, where the computer-readable instructions may be executed by the processor 610 to implement a mobile application on the customer device 604, such as an interactive digital receipt application. In some embodiments, the memory 616 may include data storage (not shown) for storing data created and/or used by to the interactive digital receipt application.


The customer device 604 may be, for example, mobile devices and computing devices that can communicate with the interactive digital receipt system 602 and the merchant transaction system 606 through the network 608. The customer device 604 can be the user device 100 of FIGS. 1A-1I. The customer device 604 includes a processor 630, communications circuitry 632, an input/output (I/O) interface 634, and a memory 636. These components may be coupled by one or more communication buses or other signal lines. It is noted that the device 604 can include more or fewer components.


The processor 630 includes one or more processors. The processor 630 is operatively coupled to the communication circuitry 632 and the memory 636. The processor 630 may include a digital signal processor, a microprocessor, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations thereof. The processor 630 may be configured to execute computer/machine readable and executable instructions stored in the local memory 636 or in a remote device memory (not shown). Such instructions are implemented by the processor 630 to perform one or more functions described above. In performing such functions, the processor 630 uses the communication circuitry 632 to communicate with the network 608 and other devices on the network 608, such as the interactive digital receipt system 602 and the merchant transaction system 606.


The communications circuitry 632 includes one or more mechanisms that enable the interactive digital receipt system 602, the customer device 604, and/or the merchant transaction system 606 to engage in communications over the network 608. The communications circuitry 632 may include RF circuitry and/or port for sending and receiving information. The RF circuitry permits transmission of information over a wireless link or network to one or more other devices and includes well-known circuitry for performing this function. The RF circuitry may enable WiFi, cellular, Bluetooth, Bluetooth low energy, global positioning system (GPS), near field communication (NFC), or other types of long range or short range communication. The port permits transmission of information over a wired link. The communications circuitry 632 can be configured, for example, to aid in the handling, receipt and transmission of secured financial data sent between two or more network devices, such as the interactive digital receipt system 602 and the customer device 604, and/or the interactive digital receipt system 602 and the merchant transaction system 606.


The I/O interface 634 includes one or more user input and output device interface mechanisms. The interface 634 may include a computer keyboard, touchpad, touchscreen, mouse, display device, and the corresponding physical ports and underlying supporting hardware and software to enable communications with other network devices in the system 600. Such communications include, but are not limited to, accepting user data input (e.g., authorization of payment) and providing output information to a user, programming and administering one or more functions to be executed by the corresponding device and the like.


The memory 636 includes one or more memories. The memory 636 may include, but are not limited to, cache memory, main memory and secondary memory. The memory 636 may include computer-readable instructions, where the computer-readable instructions may be executed by the processing system 630. In some embodiments, the memory 636 may include data storage (not shown) for storing data created and/or used by to the customer device 604.


The merchant transaction system 606 may be, for example, mobile devices and computing devices that can communicate with the interactive digital receipt system 602 and the customer device 604 through the network 608. The mobile devices include, but are not limited to, smartphones (e.g., Android®-enabled phones), personal digital assistants (PDAs), portable computers with wired or wireless wide-area-network and/or telecommunication capability such as tablet personal computers and “netbook” personal computers. The computing devices include, but are not limited to, personal computers, electronic point-of-sale cash registry machines, and electronic kiosks.


The merchant transaction system 606 includes a processor 640, communications circuitry 642, an input/output (I/O) interface 644, and a memory 646. These components may be coupled by one or more communication buses or other signal lines. It is noted that the system 606 can include more or fewer components.


The processor 640 includes one or more processors. The processor 640 is operatively coupled to the communication circuitry 642 and the memory 648. The one or more processors may include a digital signal processor, a microprocessor, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations thereof. The processor 640 may be configured to execute computer/machine readable and executable instructions stored in the local memory 648 or in a remote device memory (not shown). Such instructions are implemented by the processor 630 to perform one or more functions described above. In performing such functions, the processor 640 uses the communication circuitry 642 to communicate with the network 608 and other devices on the network 608, such as the interactive digital receipt system 602 and the customer device 604.


The communications circuitry 642 includes one or more mechanisms that enable the interactive digital receipt system 602, the customer device 604, and/or the merchant transaction system 606 to engage in communications over the network 608. The communications circuitry 642 may include RF circuitry and/or port for sending and receiving information. The RF circuitry permits transmission of information over a wireless link or network to one or more other devices and includes well-known circuitry for performing this function. The RF circuitry may enable WiFi, cellular, Bluetooth, Bluetooth low energy, global positioning system (GPS), near field communication (NFC), or other types of long range or short range communication. The port permits transmission of information over a wired link. The communications circuitry 642 can be configured, for example, to aid in the handling, receipt and transmission of secured financial data sent between two or more network devices, such as the merchant transaction system 606 and the customer device 604, and/or the merchant transaction system 606 the interactive digital receipt system 602.


The I/O interface 644 includes one or more user input and output device interface mechanisms. The interface may include a computer keyboard, touchpad, touchscreen, mouse, display device, and the corresponding physical ports and underlying supporting hardware and software to enable communications with other network devices in the system 600. Such communications include, but are not limited to, accepting user data input (e.g., credit card payment data via a POS device) and providing output information (e.g., communicating with the receipt system 602 to deliver an interactive digital receipt) to a user (e.g., user of the customer device 604), programming and administering one or more functions to be executed by the corresponding device and the like.


The memory 648 includes one or more memories. The one or more memories may be, for example, cache memory, main memory and secondary memory. The memory 648 includes computer-readable instructions, where the computer-readable instructions may be executed by the processor 640. In some embodiments, the memory 648 may include data storage (not shown) for storing data related to the financial transaction between the customer and the merchant.

Claims
  • 1. A method of providing an interactive digital receipt, comprising: receiving, by an interactive digital receipt system and from a first mobile device associated with a merchant, an indication of a payment transaction between a customer and the merchant instantiated on the first mobile device;generating, by the interactive digital receipt system as part of the payment transaction, an interactive digital receipt that includes an indication of a payment amount associated with the payment transaction and an interactive promotion component for redeeming a promotional reward;transmitting, by the interactive digital receipt system and to a second mobile device associated with the customer, the interactive digital receipt;receiving, by the second mobile device and from the interactive digital receipt system, the interactive digital receipt;presenting, at the second mobile device, the interactive digital receipt;enabling, by the interactive digital receipt at the second mobile device, the interaction promotion component for a promotion timeframe that defines a time period during which input to the interactive promotion component to redeem the promotional reward is effective;receiving, by the interactive digital receipt system and from the second mobile device, an interactive input submitted by the customer within the promotion timeframe to redeem the promotional reward;disabling, by the interactive digital receipt at the second mobile device after the end of the promotion timeframe, the interaction promotion component; andprocessing, by the interactive digital receipt system, the interactive input to generate the promotional reward, wherein the promotional reward is configured to decrease in value based on a time of submission of the interactive input with respect to the promotion timeframe, the promotional reward having at least a first value at a first time and a second value at a second time, wherein the first time and the second time are before the expiration of the promotion timeframe and the first value is different from the second value.
  • 2. The method of claim 1, wherein the interactive input includes at least one of: participation in an interactive game associated with the merchant; completion of an activity associated with the merchant; or completion of an activity associated with a third party associated with the merchant.
  • 3. The method of claim 1, wherein the promotional reward is configured to decrease in value at a rate configured by the merchant.
  • 4. The method of claim 1, wherein the interactive digital receipt further includes an interactive feedback component for the customer to submit feedback associated with the payment transaction, wherein the interactive feedback component remains available for a feedback timeframe that defines a particular time period for the customer to submit the feedback using the interactive feedback component.
  • 5. The method of claim 1, wherein the interactive digital receipt further includes an interactive loyalty rewards component for the customer to maintain a rewards record of purchases from a plurality of payment transactions over a span of time.
  • 6. The method of claim 4, wherein the interactive feedback component is configured to generate a time-based reward for submission of the feedback, wherein a value of the time-based reward is defined based on a time of submission of the feedback.
  • 7. The method of claim 1, wherein the interactive digital receipt includes an interactive tipping component that enables the customer to submit a gratuity amount associated with the payment transaction subsequent to the interactive digital receipt being transmitted to the customer, the interactive tipping component remaining available for a gratuity timeframe that defines a time period for the customer to submit the gratuity amount using the interactive tipping component.
  • 8. The method of claim 1, further comprising: generating for the customer an interactive transaction record that is accessible via the interactive digital receipt, the interactive transaction record comprising a plurality of transaction records completed between the customer and the merchant; andfor each new financial transaction between the customer and the merchant, updating the interactive transaction record.
  • 9. A non-transitory computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform operations for providing an interactive digital receipt, the operations comprising: receiving, from a first mobile device associated with a merchant, an indication of a payment transaction between a customer and the merchant, the payment transaction being instantiated on the first mobile device;generating, as part of the payment transaction, an interactive digital receipt that includes an indication of a payment amount associated with the payment transaction and an interactive promotion portion for redeeming a promotional reward, the interactive digital receipt configured to enable the interactive promotion portion at a second mobile device associated with the customer for a promotion timeframe that defines a time period during which input to the interactive promotion component to redeem the promotional reward via the interactive promotion portion is effective;transmitting, to the second mobile device, the interactive digital receipt;receiving, from the second mobile device, an interactive input submitted within the promotion timeframe by the customer to redeem the promotional reward; andprocessing the interactive input to generate the promotional reward, wherein the promotional reward is configured to decrease in value based on a time of submission of the interactive input with respect to the promotion timeframe, the promotional reward having at least a first value at a first time and a second value at a second time, wherein the first time and the second time are before the expiration of the promotion timeframe and the first value is different from the second value.
  • 10. The non-transitory computer-readable storage medium of claim 9, wherein the interactive input includes at least one of: participation in an interactive game associated with the merchant; completion of an activity associated with the merchant; or completion of an activity associated with a third party associated with the merchant.
  • 11. The non-transitory computer-readable storage medium of claim 9, wherein the promotional reward is configured to decrease in value at a rate configured by the merchant.
  • 12. The non-transitory computer-readable storage medium of claim 9, wherein the interactive digital receipt further includes an interactive feedback portion enabling the customer to submit feedback associated with the payment transaction, wherein the interactive feedback portion remains available for a feedback timeframe that defines a particular time period for the customer to submit the feedback using the interactive feedback portion.
  • 13. The non-transitory computer-readable storage medium of claim 12, wherein the interactive feedback portion is configured to generate a time-based reward for submission of the feedback, wherein a value of the time-based reward is defined based on a time of submission of the feedback.
  • 14. The non-transitory computer-readable storage medium of claim 9, wherein the interactive digital receipt further includes an interactive loyalty rewards portion for the customer to maintain a rewards record of purchases from a plurality of payment transactions over a span of time.
  • 15. The non-transitory computer-readable storage medium of claim 9, wherein the interactive digital receipt includes an interactive tipping portion that enables the customer to submit a gratuity amount associated with the payment transaction subsequent to the interactive digital receipt being transmitted to the customer, the interactive tipping portion remaining available for a gratuity timeframe that defines a time period for the customer to submit the gratuity amount using the interactive tipping portion.
  • 16. The non-transitory computer-readable storage medium of claim 9, wherein the operations further comprise: generating for the customer an interactive transaction record that is accessible via the interactive digital receipt, the interactive transaction record comprising a plurality of transaction records completed between the customer and the merchant; andfor each new financial transaction between the customer and the merchant, updating the interactive transaction record.
  • 17. A computing system comprising: a memory;one or more processors coupled to the memory;wherein the memory contains first executable code that when executed by the one or more processors, performs operations including: receive an indication of a payment transaction between a customer and a merchant;generate, as part of the payment transaction, an interactive digital receipt that includes an indication of a payment amount associated with the payment transaction and an interactive promotion portion for redeeming a promotional reward,wherein the interactive digital receipt generates instructions that, when executed by one or more processors of a customer device, enable the interactive promotion portion on the customer device for a promotion timeframe that defines a time period during which input to the interactive promotion component to redeem the promotional reward via the interactive promotion portion is effective;transmit the interactive digital receipt to the customer device;receive, from the customer device, an interactive input submitted by the customer within the promotion timeframe to redeem the promotional reward; andprocess the interactive input to generate the promotional reward, wherein the promotional reward is configured to decrease in value based on a time of submission of the interactive input with respect to the promotion timeframe, the promotional reward having at least a first value at a first time and a second value at a second time, wherein the first time and the second time are before the expiration of the promotion timeframe and the first value is different from the second value.
  • 18. The system of claim 17, wherein the interactive digital receipt further includes an interactive feedback portion enabling the customer to submit feedback associated with the payment transaction, wherein the interactive feedback portion remains available for a feedback timeframe that defines a particular time period for the customer to submit the feedback using the interactive feedback portion.
  • 19. The system of claim 18, wherein the interactive feedback portion is configured to generate a time-based reward for submission of the feedback, wherein a value of the time-based reward is defined based on a time of submission of the feedback.
  • 20. The system of claim 17, wherein the interactive receipt module is further configured to: generate for the customer an interactive transaction record that is accessible via the interactive digital receipt, the interactive transaction record comprising a plurality of transaction records completed between the customer and the merchant; andfor each new financial transaction between the customer and the merchant, update the interactive transaction record.
PRIORITY CLAIM

This application claims the benefit of U.S. Provisional Patent Application No. 61/901,986, entitled “INTERACTIVE DIGITAL RECEIPT”, filed on Nov. 8, 2013, which is incorporated by reference herein in its entirety.

US Referenced Citations (355)
Number Name Date Kind
5315093 Stewart May 1994 A
5590038 Pitroda Dec 1996 A
5652421 Veeneman et al. Jul 1997 A
5878337 Joao et al. Mar 1999 A
5960411 Hartman et al. Sep 1999 A
6026387 Kesel Feb 2000 A
6154738 Call Nov 2000 A
6175922 Wang Jan 2001 B1
6193155 Walker et al. Feb 2001 B1
6263352 Cohen Jul 2001 B1
6330544 Walker et al. Dec 2001 B1
6341353 Herman et al. Jan 2002 B1
7010495 Samra et al. Mar 2006 B1
7085812 Sherwood Aug 2006 B1
7136448 Venkataperumal et al. Nov 2006 B1
7155411 Blinn et al. Dec 2006 B1
7233843 Budhraja et al. Jun 2007 B2
7406436 Reisman Jul 2008 B1
7475024 Phan Jan 2009 B1
7478054 Adams et al. Jan 2009 B1
7493390 Bobde et al. Feb 2009 B2
7552087 Schultz Jun 2009 B2
7575166 McNamara Aug 2009 B2
7580873 Silver et al. Aug 2009 B1
7603382 Halt, Jr. Oct 2009 B2
7764185 Manz et al. Jul 2010 B1
D621849 Anzures et al. Aug 2010 S
7805378 Berardi et al. Sep 2010 B2
7810729 Morley, Jr. Oct 2010 B2
7818809 Sobel et al. Oct 2010 B1
8060259 Budhraja et al. Nov 2011 B2
8112066 Ben Ayed Feb 2012 B2
8190514 Bishop et al. May 2012 B2
8266551 Boldyrev et al. Sep 2012 B2
8401710 Budhraja et al. Mar 2013 B2
8423459 Green et al. Apr 2013 B1
8434682 Argue et al. May 2013 B1
D683755 Phelan Jun 2013 S
8459544 Casey et al. Jun 2013 B2
8498888 Raff et al. Jul 2013 B1
8571916 Bruce et al. Oct 2013 B1
8577803 Chatterjee et al. Nov 2013 B2
8577810 Dalit et al. Nov 2013 B1
8579203 Lambeth et al. Nov 2013 B1
D695306 Gabouer et al. Dec 2013 S
8602296 Velline et al. Dec 2013 B1
8630586 Dvortsov et al. Jan 2014 B2
8645014 Kozlowski et al. Feb 2014 B1
8676119 Cohen et al. Mar 2014 B2
8682806 Cate et al. Mar 2014 B1
8694357 Ting et al. Apr 2014 B2
8788418 Spodak et al. Jul 2014 B2
8843385 Jurca et al. Sep 2014 B2
8855312 Hodgman et al. Oct 2014 B1
8859337 Gaul et al. Oct 2014 B2
8892462 Borovsky et al. Nov 2014 B1
D720765 Xie et al. Jan 2015 S
D720766 Mandal et al. Jan 2015 S
8939357 Perry Jan 2015 B1
D725133 Smirin et al. Mar 2015 S
D725666 Tseng et al. Mar 2015 S
8972298 Kunz et al. Mar 2015 B2
9010644 Workley Apr 2015 B1
D732059 Andersen et al. Jun 2015 S
9064249 Borovsky et al. Jun 2015 B1
9092767 Andrews et al. Jul 2015 B1
9092776 Dessert Jul 2015 B2
9092828 Hosp Jul 2015 B2
9195985 Domenica et al. Nov 2015 B2
D748114 Leyon Jan 2016 S
D752604 Zhang Mar 2016 S
D752605 Wang Mar 2016 S
D786906 Andersen et al. May 2017 S
9721251 Jen et al. Aug 2017 B1
9799021 Lee Oct 2017 B1
10026062 Sasmaz et al. Jul 2018 B1
20010054003 Chien et al. Dec 2001 A1
20020091646 Lake et al. Jul 2002 A1
20030014317 Siegel et al. Jan 2003 A1
20030061157 Hirka et al. Mar 2003 A1
20030065805 Barnes, Jr. Apr 2003 A1
20030115126 Pitroda Jun 2003 A1
20030115285 Lee et al. Jun 2003 A1
20030204447 Dalzell et al. Oct 2003 A1
20040030601 Pond et al. Feb 2004 A1
20040103065 Kishen et al. May 2004 A1
20040138999 Friedman et al. Jul 2004 A1
20040193489 Boyd et al. Sep 2004 A1
20040204990 Lee Oct 2004 A1
20040215520 Butler et al. Oct 2004 A1
20040219971 Ciancio et al. Nov 2004 A1
20050055582 Bazakos et al. Mar 2005 A1
20050246245 Satchell et al. Nov 2005 A1
20060064373 Kelley Mar 2006 A1
20060085333 Wah et al. Apr 2006 A1
20060131385 Kim Jun 2006 A1
20060146839 Hurwitz et al. Jul 2006 A1
20060261149 Raghavendra Tulluri Nov 2006 A1
20070069013 Seifert et al. Mar 2007 A1
20070073619 Smith Mar 2007 A1
20070208930 Blank et al. Sep 2007 A1
20070244766 Goel Oct 2007 A1
20070255653 Tumminaro et al. Nov 2007 A1
20070255662 Tumminaro Nov 2007 A1
20080035725 Jambunathan et al. Feb 2008 A1
20080037442 Bill Feb 2008 A1
20080040265 Rackley, III et al. Feb 2008 A1
20080052176 Buchheit Feb 2008 A1
20080078831 Johnson et al. Apr 2008 A1
20080133351 White et al. Jun 2008 A1
20080177624 Dohse Jul 2008 A9
20080177826 Pitroda Jul 2008 A1
20080197188 Jagatic et al. Aug 2008 A1
20080262925 Kim et al. Oct 2008 A1
20080270246 Chen Oct 2008 A1
20080277465 Pletz et al. Nov 2008 A1
20080296978 Finkenzeller et al. Dec 2008 A1
20090070228 Ronen Mar 2009 A1
20090099961 Ogilvy Apr 2009 A1
20090106138 Smith et al. Apr 2009 A1
20090112766 Hammad et al. Apr 2009 A1
20090119190 Realini May 2009 A1
20090159663 Mullen et al. Jun 2009 A1
20090192904 Patterson et al. Jul 2009 A1
20090204472 Einhom Aug 2009 A1
20090240558 Bandy et al. Sep 2009 A1
20090266884 Killian et al. Oct 2009 A1
20090271265 Lay et al. Oct 2009 A1
20090288012 Hertel Nov 2009 A1
20090313132 McKenna et al. Dec 2009 A1
20090319421 Mathis et al. Dec 2009 A1
20090319638 Faith et al. Dec 2009 A1
20100010906 Grecia Jan 2010 A1
20100076777 Paretti et al. Mar 2010 A1
20100082420 Trifiletti et al. Apr 2010 A1
20100102125 Gatto Apr 2010 A1
20100125495 Smith et al. May 2010 A1
20100174596 Gilman et al. Jul 2010 A1
20100185514 Glazer et al. Jul 2010 A1
20100223145 Dragt Sep 2010 A1
20100269059 Othmer et al. Oct 2010 A1
20100280896 Postrel Nov 2010 A1
20100306099 Hirson et al. Dec 2010 A1
20110029416 Greenspan Feb 2011 A1
20110047013 McKenzie, III Feb 2011 A1
20110055084 Singh Mar 2011 A1
20110071892 Dickelman Mar 2011 A1
20110087550 Fordyce, III Apr 2011 A1
20110112897 Tietzen et al. May 2011 A1
20110131128 Vaananen Jun 2011 A1
20110145049 Hertel et al. Jun 2011 A1
20110145052 Lin et al. Jun 2011 A1
20110178883 Granbery et al. Jul 2011 A1
20110180598 Morgan et al. Jul 2011 A1
20110218871 Singh Sep 2011 A1
20110246284 Chaikin et al. Oct 2011 A1
20110251892 Laracey Oct 2011 A1
20110251962 Hruska Oct 2011 A1
20110258014 Evangelist et al. Oct 2011 A1
20110258689 Cohen et al. Oct 2011 A1
20110270747 Xu Nov 2011 A1
20110276418 Velani Nov 2011 A1
20110295722 Reisman Dec 2011 A1
20110295750 Rammal Dec 2011 A1
20110302019 Proctor, Jr. et al. Dec 2011 A1
20110302080 White et al. Dec 2011 A1
20110313840 Mason et al. Dec 2011 A1
20110313867 Silver Dec 2011 A9
20110313871 Greenwood Dec 2011 A1
20110320345 Taveau et al. Dec 2011 A1
20120005076 Dessert et al. Jan 2012 A1
20120011072 Lodolo Jan 2012 A1
20120016731 Smith et al. Jan 2012 A1
20120029990 Fisher Feb 2012 A1
20120030044 Hurst Feb 2012 A1
20120059701 van der Veen et al. Mar 2012 A1
20120059718 Ramer et al. Mar 2012 A1
20120059758 Carlson Mar 2012 A1
20120066065 Switzer Mar 2012 A1
20120084210 Farahmand Apr 2012 A1
20120089418 Kamath et al. Apr 2012 A1
20120095867 McKelvey Apr 2012 A1
20120095871 Dorsey et al. Apr 2012 A1
20120110568 Abel et al. May 2012 A1
20120130785 Postrel May 2012 A1
20120143772 Abadir Jun 2012 A1
20120150611 Isaacson Jun 2012 A1
20120150643 Wolfe et al. Jun 2012 A1
20120150742 Poon et al. Jun 2012 A1
20120166311 Dwight et al. Jun 2012 A1
20120185306 Cheng Jul 2012 A1
20120185355 Kilroy Jul 2012 A1
20120197740 Grigg et al. Aug 2012 A1
20120197743 Grigg et al. Aug 2012 A1
20120197794 Grigg et al. Aug 2012 A1
20120198279 Schroeder Aug 2012 A1
20120209749 Hammad et al. Aug 2012 A1
20120209773 Ranganathan Aug 2012 A1
20120214416 Kent et al. Aug 2012 A1
20120244885 Hefetz Sep 2012 A1
20120254031 Walker et al. Oct 2012 A1
20120271707 Harrison et al. Oct 2012 A1
20120271725 Cheng Oct 2012 A1
20120278727 Ananthakrishnan et al. Nov 2012 A1
20120284036 Evans Nov 2012 A1
20120290422 Bhinder Nov 2012 A1
20120290609 Britt Nov 2012 A1
20120296679 Im Nov 2012 A1
20120296726 Dessert et al. Nov 2012 A1
20120323685 Ullah Dec 2012 A1
20130006773 Lutnick et al. Jan 2013 A1
20130019284 Pacyga et al. Jan 2013 A1
20130024341 Jeon et al. Jan 2013 A1
20130024364 Shrivastava et al. Jan 2013 A1
20130024371 Hariramani et al. Jan 2013 A1
20130030889 Davich et al. Jan 2013 A1
20130036065 Chen et al. Feb 2013 A1
20130041824 Gupta Feb 2013 A1
20130048719 Bennett Feb 2013 A1
20130050080 Dahl et al. Feb 2013 A1
20130054320 Dorso et al. Feb 2013 A1
20130065672 Gelman et al. Mar 2013 A1
20130066783 Wolff Mar 2013 A1
20130073363 Boal Mar 2013 A1
20130103574 Conrad et al. Apr 2013 A1
20130103946 Binenstock Apr 2013 A1
20130117329 Bank et al. May 2013 A1
20130124333 Doughty et al. May 2013 A1
20130132140 Amin et al. May 2013 A1
20130132182 Fung et al. May 2013 A1
20130132246 Amin et al. May 2013 A1
20130132274 Henderson et al. May 2013 A1
20130132887 Amin et al. May 2013 A1
20130134962 Kamel et al. May 2013 A1
20130138563 Gilder et al. May 2013 A1
20130144707 Issacson et al. Jun 2013 A1
20130151613 Dhawan et al. Jun 2013 A1
20130159081 Shastry et al. Jun 2013 A1
20130159172 Kim Jun 2013 A1
20130159173 Sivaraman et al. Jun 2013 A1
20130159446 Carlson et al. Jun 2013 A1
20130166402 Parento et al. Jun 2013 A1
20130166445 Issacson et al. Jun 2013 A1
20130173407 Killian et al. Jul 2013 A1
20130179227 Booth et al. Jul 2013 A1
20130181045 Dessert et al. Jul 2013 A1
20130198018 Baig Aug 2013 A1
20130204727 Rothschild Aug 2013 A1
20130204777 Irwin, Jr. et al. Aug 2013 A1
20130204793 Kerridge et al. Aug 2013 A1
20130218697 Kingston et al. Aug 2013 A1
20130218721 Borhan Aug 2013 A1
20130225081 Doss et al. Aug 2013 A1
20130228616 Bhosle et al. Sep 2013 A1
20130236109 Madden et al. Sep 2013 A1
20130246203 Laracey Sep 2013 A1
20130246207 Novak et al. Sep 2013 A1
20130246280 Kirsch Sep 2013 A1
20130246301 Radhakrishnan et al. Sep 2013 A1
20130248591 Look et al. Sep 2013 A1
20130268431 Mohsenzadeh Oct 2013 A1
20130290173 Nemeroff Oct 2013 A1
20130290522 Behm, Jr. Oct 2013 A1
20130291018 Billings et al. Oct 2013 A1
20130295882 Zhao Nov 2013 A1
20130297933 Fiducia et al. Nov 2013 A1
20130317835 Mathew Nov 2013 A1
20130317950 Abraham et al. Nov 2013 A1
20130332354 Rhee et al. Dec 2013 A1
20130332385 Kilroy et al. Dec 2013 A1
20130339253 Sincai Dec 2013 A1
20130346223 Prabhu et al. Dec 2013 A1
20140006205 Berry et al. Jan 2014 A1
20140012754 Hanson et al. Jan 2014 A1
20140019236 Argue Jan 2014 A1
20140025446 Nagarajan et al. Jan 2014 A1
20140032297 Germann et al. Jan 2014 A1
20140052613 Tavakoli et al. Feb 2014 A1
20140052617 Chawla et al. Feb 2014 A1
20140057667 Blankenship et al. Feb 2014 A1
20140058861 Argue et al. Feb 2014 A1
20140059466 Mairs et al. Feb 2014 A1
20140067557 van Niekerk et al. Mar 2014 A1
20140074569 Francis et al. Mar 2014 A1
20140074655 Lim et al. Mar 2014 A1
20140074658 Sanchez Mar 2014 A1
20140074691 Bank et al. Mar 2014 A1
20140074716 Ni Mar 2014 A1
20140081783 Paranjape et al. Mar 2014 A1
20140081853 Sanchez et al. Mar 2014 A1
20140081854 Sanchez et al. Mar 2014 A1
20140084059 Sierchio et al. Mar 2014 A1
20140089073 Jacobs et al. Mar 2014 A1
20140089078 Dessert et al. Mar 2014 A1
20140096179 Ben-Shalom et al. Apr 2014 A1
20140099888 Flanagan et al. Apr 2014 A1
20140100931 Sanchez et al. Apr 2014 A1
20140100973 Brown et al. Apr 2014 A1
20140101737 Rhee Apr 2014 A1
20140108245 Drummond et al. Apr 2014 A1
20140114775 Cloin et al. Apr 2014 A1
20140114781 Watanabe Apr 2014 A1
20140122345 Argue May 2014 A1
20140129135 Holden et al. May 2014 A1
20140129302 Amin et al. May 2014 A1
20140129357 Goodwin May 2014 A1
20140129942 Rathod May 2014 A1
20140129951 Amin et al. May 2014 A1
20140136318 Alberth, Jr. et al. May 2014 A1
20140136349 Dave et al. May 2014 A1
20140143157 Jeffs et al. May 2014 A1
20140149282 Philliou et al. May 2014 A1
20140156508 Argue et al. Jun 2014 A1
20140156517 Argue et al. Jun 2014 A1
20140164234 Coffman et al. Jun 2014 A1
20140180805 Argue Jun 2014 A1
20140184505 Fullerton et al. Jul 2014 A1
20140201067 Lai et al. Jul 2014 A1
20140207669 Rosenberg Jul 2014 A1
20140214567 Llach et al. Jul 2014 A1
20140214652 Zheng et al. Jul 2014 A1
20140236762 Gerber et al. Aug 2014 A1
20140244489 Kessler et al. Aug 2014 A1
20140249947 Hicks et al. Sep 2014 A1
20140250002 Issacson et al. Sep 2014 A1
20140254820 Gardenfors et al. Sep 2014 A1
20140257958 Andrews Sep 2014 A1
20140278589 Rados et al. Sep 2014 A1
20140279098 Ham Sep 2014 A1
20140279184 Lai et al. Sep 2014 A1
20140344102 Cooper Nov 2014 A1
20140351004 Flett Nov 2014 A1
20140379497 Varma et al. Dec 2014 A1
20140379536 Varma et al. Dec 2014 A1
20140379580 Varma et al. Dec 2014 A1
20150012426 Purves et al. Jan 2015 A1
20150025983 Cicerchi Jan 2015 A1
20150032567 Bhatia Jan 2015 A1
20150058146 Gaddam et al. Feb 2015 A1
20150066699 Fisher Mar 2015 A1
20150066765 Banks et al. Mar 2015 A1
20150073907 Purves et al. Mar 2015 A1
20150095134 Parker et al. Apr 2015 A1
20150095228 Su et al. Apr 2015 A1
20150100481 Ghosh et al. Apr 2015 A1
20150112838 Li et al. Apr 2015 A1
20150120418 Cervenka et al. Apr 2015 A1
20150134513 Olson et al. May 2015 A1
20150134528 Fineman et al. May 2015 A1
20150178755 Barroso Jun 2015 A1
20150194023 Brackenridge et al. Jul 2015 A1
20150294312 Kendrick et al. Oct 2015 A1
20150304270 Cook Oct 2015 A1
20160086166 Pomeroy et al. Mar 2016 A1
20180150807 Aaron et al. May 2018 A1
Foreign Referenced Citations (11)
Number Date Country
2017235924 Oct 2017 AU
2018205104 Jul 2018 AU
2 916 603 Dec 2014 CA
2 930 186 May 2015 CA
2530451 Mar 2016 GB
10-2006-0103089 Sep 2006 KR
2014210020 Dec 2014 WO
2015061005 Apr 2015 WO
2015069389 May 2015 WO
2015100378 Jul 2015 WO
2015179316 Nov 2015 WO
Non-Patent Literature Citations (194)
Entry
U.S. Appl. No. 14/513,076 of Borovsky, A., et al., filed Oct. 13, 2014.
U.S. Appl. No. 14/526,361 of White, M.W., et al., filed Oct. 28, 2014.
Advisory Action dated Nov. 18, 2014, U.S. Appl. No. 14/160,490 of Moring, D., et al., filed Jan. 21, 2014.
International search report and written opinion for PCT Application No. PCT/US2014/058398 dated Dec. 24, 2014.
Non-Final Office Action dated Jan. 9, 2015, U.S. Appl. No. 14/145,895 of Aaron, P., et al., filed Dec. 31, 2013.
International search report and written opinion for PCT Application No. PCT/US2014/058447 dated Jan. 15, 2015.
Final Office Action dated Jan. 26, 2015, U.S. Appl. No. 13/837,562, of Chin, H.C.A., et al., filed Mar. 15, 2013.
Notice of Allowance dated Feb. 20, 2015, U.S. Appl. No. 14/513,076, of Borovsky, A., et al., filed Oct. 13, 2014.
Final Office Action dated Mar. 17, 2015, U.S. Appl. No. 14/165,256, of Aaron, P., filed Jan. 27, 2014.
International search report and written opinion for PCT Application No. PCT/US2014/072269 dated Mar. 31, 2015.
Restriction Requirement dated Apr. 9, 2015, U.S. Appl. No. 14/225,338 of Aaron, P., et al., filed Mar. 25, 2014.
U.S. Appl. No. 14/692,655 of Borovsky, A., et al., filed Apr. 21, 2015.
Non-Final Office Action dated Apr. 27, 2015, U.S. Appl. No. 14/184,503 of Borovsky, A., et al., filed Feb. 19, 2014.
U.S. Appl. No. 14/149,754 of Spindel, N., et al. filed Jan. 7, 2014.
U.S. Appl. No. 14/208,800 of Thome, J.P. et al., filed Mar. 13, 2014.
U.S. Appl. No. 14/225,338 of Aaron, P. et al., filed Mar. 25, 2014.
Non-Final Office Action dated Apr. 4, 2014, U.S. Appl. No. 14/172,842 of Borovsky, A. et al., filed Feb. 4, 2014.
Non-Final Office Action dated Apr. 10, 2014, U.S. Appl. No. 14/160,490 of Morig, D., et al., filed Jan. 21, 2014.
Restriction Requirement dated Apr. 28, 2014, U.S. Appl. No. 14/165,256 of Aaron, P., filed Jan. 27, 2014.
Non-Final Office Action dated Apr. 8, 2016, for U.S. Appl. No. 14/526,361, of White, M. W., et al., filed Oct. 28, 2014.
Final Office Action dated Apr. 13, 2016, for U.S. Appl. No. 14/165,256, of Aaron, P., filed Jan. 27, 2014.
Final Office Action dated Apr. 27, 2016, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014.
Final Office Action dated Apr. 28, 2016, for U.S. Appl. No. 14/189,880, of Aaron, P., et al., filed Feb. 25, 2014.
Non-Final Office Action dated May 3, 2016, for U.S. Appl. No. 13/830,350, of Morgan, T. B., et al., filed Mar. 14, 2013.
Non-Final Office Action dated May 9, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2013.
“Another EBay Band-Aid Fails to Fix the New Pricing Structure Flaws,” dated Oct. 18, 2008, Retrieved from the Internet URL: https://thebrewsnews.wordpress.com/2008/10/18/another-ebay-band-aid-fails-to-fix-the-new-pricing-structure-flaws/, pp. 1-5.
“Online Shopping,” dated Nov. 2, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Online_shopping, on Nov. 10, 2014, pp. 1-12.
Goode, L., “Paying With Square's New Mobile-Payments App,” All Things D, dated Apr. 30, 2012, Retrieved from the Internet URL: http://allthingsd.com/20120430/paying-with-squares-new-mobile-payments-app/, on Nov. 7, 2014, pp. 1-3.
Myres, L., “What is Multi-Factor Authentication, and How Will It Change in the Future?,” Intego, dated Aug. 17, 2012, Retrieved from the Internet URL: http://www.intego.com/mac-security-blog/what-is-multi-factor-authentication-and-how-will-it-change-in-the-future/, on Nov. 11, 2014, pp. 1-4.
Wallen, J., “Five Top Apps for Managing Inventory,” Tech Republic, dated Aug. 15, 2012, Retrieved from the Internet URL: http://www.techrepublic.com/blog/five-apps/five-top-apps-for-managing-inventory/, on Nov. 10, 2014, pp. 1-7.
U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013.
U.S. Appl. No. 14/197,704, of Lamba, K., et al., filed Mar. 5, 2014.
U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014.
U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014.
U.S. Appl. No. 14/730,860, of Sasmaz, Y., et al., filed Jun. 4, 2015.
Non-Final Office Action dated Mar. 19, 2015, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014.
Non-Final Office Action dated May 12, 2015, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014.
Non-Final Office Action dated May 20, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Non-Final Office Action dated May 26, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014.
Non-Final Office Action dated May 27, 2015, for U.S. Appl. No. 14/197,704, of Lamba, K., et al., filed Mar. 5, 2014.
Non-Final Office Action dated Jun. 11, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015.
Restriction Requirement dated Jun. 19, 2015, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014.
Non-Final Office Action dated Jul. 2, 2015, for U.S. Appl. No. 14/208,800, of Thome, J.P., et al., filed Mar. 13, 2014.
Non-Final Office Action dated Jul. 10, 2015, for U.S. Appl. No. 14/526,361, of White, M.W., et al., filed Oct. 28, 2014.
Restriction Requirement dated Jul. 24, 2015, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014.
Final Office Action dated Aug. 18, 2015, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013.
International Search Report and Written Opinion for PCT Application No. PCT/US2015/031423 dated Aug. 13, 2015.
Final Office Action dated Aug. 28, 2014, U.S. Appl. No. 14/160,490 of Morig, D., et al., filed Jan. 21, 2014.
Non-Final Office Action dated Aug. 27, 2014, U.S. Appl. No. 14/165,256 of Aaron, P., filed Jan. 27, 2014.
Non-Final Office Action dated May 29, 2014, U.S. Appl. No. 13/837,562 of Chin, H.C.A. et al., filed Mar. 15, 2013.
Notice of Allowance dated Aug. 1, 2014, U.S. Appl. No. 14/172,842 of Borovsky, A. et al., filed Feb. 4, 2014.
“Tracking Inventory,” PayPal, dated Jan. 4, 2010, Retrieved from the Internet URL: https://www.paypal-community.com/t5/How-to-use-PayPal-Archive/Tracking-inventory/td-p/19392, pp. 1-3.
Final Office Action dated Sep. 17, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Notice of Allowance dated Sep. 18, 2015, for U.S. Appl. No. 14/197,704, of Lamba, K, et al., filed Mar. 5, 2014.
Final Office Action dated Sep. 21, 2015, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014.
Non-Final Office Action dated Sep. 30, 2015, for U.S. Appl. No. 14/189,880, of Aaron, P., filed Feb. 25, 2014.
Final Office Action dated Oct. 2, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014.
Final Office Action dated Oct. 5, 2015, for U.S. Appl. No. 14/526,361, of White, M.W., et al., filed Oct. 28, 2014.
Non-Final Office Action dated Oct. 5, 2015, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013.
Non-Final Office Action dated Oct. 6, 2015, for U.S. Appl. No. 14/329,658, of Aaron, P., et al. filed Jul. 11, 2014.
Non-Final Office Action dated Oct. 8, 2015, for U.S. Appl. No. 14/165,256, of Aaron, P., filed Jan. 27, 2014.
Non-Final Office Action dated Oct. 8, 2015, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014.
Final Office Action dated Oct. 16, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015.
Final Office Action dated Oct. 21, 2015, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014.
Non-Final Office Action dated Nov. 18, 2015, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014.
Advisory Action dated Nov. 24, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Advisory Action dated Dec. 4, 2015, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014.
Co-Pending U.S. Appl. No. 13/830,350 by Morgan, T.B. et al., filed Mar. 14, 2013.
Co-Pending U.S. Appl. No. 13/837,562 by Chin, H.C.A. et al., filed Mar. 15, 2013.
Co-Pending U.S. Appl. No. 14/088,113 by Maxwell, D.W. et al., filed Nov. 22, 2013.
Co-Pending U.S. Appl. No. 14/145,895 by Aaron, P., filed Dec. 31, 2013.
Co-Pending U.S. Appl. No. 14/160,490 by Morig, D., et al., filed Jan. 21, 2014.
Co-Pending U.S. Appl. No. 14/165,256 by Aaron, P., filed Jan. 27, 2014.
Co-Pending U.S. Appl. No. 14/168,274 by Odawa, A. et al., filed Jan. 30, 2014.
Co-Pending U.S. Appl. No. 14/172,842 by Borovsky, A. et al., filed Feb. 25, 2014.
Co-Pending U.S. Appl. No. 14/182,655 by Spindel, N., filed Feb. 18, 2014.
Co-Pending U.S. Appl. No. 14/184,503 by Borovsky, A., filed Feb. 19, 2014.
Co-Pending U.S. Appl. No. 14/189,869 by Lamba, K. et al., filed Feb. 25, 2014.
Co-Pending U.S. Appl. No. 14/189,880 by Aaron, P. et al., filed Feb. 25, 2014.
“Merchantindustry.com—Best Merchant Services,” retrieved from internet URL: https://web.archive.org/web/20121020212419/http://www.merchantindustry.com/, on Dec. 30, 2015, pp. 1-7.
Advisory Action dated Dec. 30, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015.
Final Office Action dated Dec. 31, 2015, for U.S. Appl. No. 14/208,800, of Thome, J. P., et al., filed Mar. 13, 2014.
Advisory Action dated Dec. 31, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014.
Advisory Action dated Jan. 21, 2016, for U.S. Appl. No. 14/526,361, of White, M. W., et al., filed Oct. 28, 2014.
Non-Final Office Action dated Jan. 22, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014.
Non-Final Office Action dated Feb. 2, 2016, for U.S. Appl. No. 13/829,080, of Morgan, T, B., et al., filed Mar. 14, 2013.
Non-Final Office Action dated Mar. 14, 2016, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015.
Restriction Requirement dated Mar. 16, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D. W., et al., filed Nov. 22, 2013.
Non-Final Office Action dated Mar. 24, 2016, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013.
Non-Final Office Action dated Jul. 21, 2016, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014.
Final Office Action dated Sep. 1, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014.
Notice of Allowance dated Sep. 13, 2016, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015.
Advisory Action dated Sep. 21, 2016, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013.
Advisory Action dated Sep. 21, 2016, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014.
Non-Final Office Action dated Sep. 21, 2016, for U.S. Appl. No. 14/189,880, of Aaron, P., filed Feb. 25, 2014.
Non-Final Office Action dated Sep. 22, 2016, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014.
Advisory Action dated Sep. 29, 2016, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014.
Final Office Action dated Oct. 11, 2016, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Advisory Action dated Oct. 11, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014.
Final Office Action dated Oct. 12, 2016, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013.
Final Office Action dated Nov. 1, 2016, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014.
Notice of Allowance dated Nov. 8, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014.
Shalmanese, “The Straight Dope Message Board,” message dated Oct. 5, 2013, Retrieved from the internet URL: http://boards.straightdope.com/sdmb/showthread.php?t=703989%BB, on Jul. 18, 2016, pp. 1-10.
Final Office Action dated May 20, 2016, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014.
Non-Final Office Action dated Jun. 7, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D. W., et al., filed Nov. 22, 2013.
Non-Final Office Action dated Jun. 7, 2016, for U.S. Appl. No. 14/208,800, of Thome, J. P., et al., filed Mar. 13, 2014.
Non-Final Office Action dated Jun. 17, 2016, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014.
Final Office Action dated Jun. 17, 2016, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014.
Final Office Action dated Jun. 20, 2016, for U.S. Appl. No. 13/829,658, of Morgan, T. B., et al., filed Mar. 14, 2013.
Non-Final Office Action dated Jul. 14, 2016, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014.
Final Office Action dated Jul. 18, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014.
“Card Not Present Transaction,” Wikipedia, published Mar. 4, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Card_not_present_transaction, on Jun. 6, 2014, pp. 1-2.
“Payment Gateway,” Wikipedia, published May 30, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Pavment gateways, on Jun. 6, 2014, pp. 1-3.
“ProPay JAK Mobile Card Reader,” Propay, published Dec. 27, 2011, Retrieved from the Internet URL: https://web.archive.org/web/20111227055421/https://www.propay.com/products-services/accept-payments/jak-card-reader, pp. 1-2.
“Verified by Visa Acquirer and Merchant Implementation Guide,” U.S. Region, Visa Public, May 2011, pp. 1-114.
“Uber—Android Apps on Google Play,” Published on Nov. 10, 2014, Retrieved from the Internet URL: https://play.google.com/store/apps/details?id=com.ubercab&hl=en, on Nov. 12, 2014, pp. 1-2.
Punch, L., “E-commerce: Just what does card-present mean these days,” dated Oct. 1, 2012, Retrieved from be Internet URL: http://digitaltransactions.net/news/ story/ E-Commerce_-Just-What-Does-Card-Present-Mean-These-Days, on Feb. 17, 2015, pp. 1-4.
Non-Final Office Action dated Dec. 1, 2014, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Non Final Office Action dated Dec. 15, 2014, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Final Office Action dated Apr. 16, 2015, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Final Office Action dated Aug. 31, 2015, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action dated Jan. 14, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action dated Feb. 23, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Non-Final Office Action dated May 5, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action dated Aug. 10, 2016, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014.
Final Office Action dated Sep. 1, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Non-Final Office Action dated Sep. 8, 2016, for U.S. Appl. No. 14/312,371, of Varma, A.K., et al., filed Jun. 23, 2014.
Examination Report No. 1 for Australian Patent Application No. 2014302661, dated Sep. 27, 2016.
Non-Final Office Action dated Nov. 17, 2016, for U.S. Appl. No. 14/701,571, of Jen, M., et al., filed May 1, 2015.
Advisory Action dated Nov. 28, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Final Office Action dated Nov. 28, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Examiner's Requisition for Canadian Patent Application No. 2,916,603, dated Feb. 9, 2017.
Notice of Allowance dated Mar. 23, 2017, for U.S. Appl. No. 14/701,571, of Jen, M., et al., filed May 1, 2015.
Advisory Action dated Apr. 10, 2017, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action dated Apr. 18, 2017, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014.
Final Office Action dated Apr. 19, 2017, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014.
Final Office Action dated Apr. 27, 2017, for U.S. Appl. No. 14/312,371, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action dated Jun. 19, 2017, for U.S. Appl. No. 14/730,860, of Sasmaz, Y., et al., filed Jun. 4, 2015.
Advisory Action dated Jun. 30, 2017, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action dated Jul. 10, 2017, for U.S. Appl. No. 13/830,350, of Morgan, T.B., et al., filed Mar. 14, 2013.
Advisory Action dated Jul. 11, 2017, for U.S. Appl. No. 14/312,371, of Varma, A.K., et al., filed Jun. 23, 2014.
Examination Report No. 1 for Australian Patent Application No. 2015264426, dated Jul. 11, 2017.
International Search Report and Written Opinion for International Application No. PCT/US2014/043891, dated Dec. 10, 2014.
Final Office Action dated Aug. 10, 2017, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014.
Final Office Action dated Sep. 15, 2017, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014.
Examination Report No. 2 for Australian Patent Application No. 2014302661, dated Sep. 26, 2017.
Advisory Action dated Oct. 31, 2017, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014.
Final Office Action dated Nov. 17, 2017, for U.S. Appl. No. 14/730,860, of Sasmaz, Y., et al., filed Jun. 4, 2015.
Notice of Allowance dated Nov. 24, 2017, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013.
Non-Final Office Action dated Dec. 13, 2017, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action dated Dec. 29, 2017, for U.S. Appl. No. 14/165,256, of Aaron, P., filed Jan. 27, 2014.
Examiner's Requisition for Canadian Patent Application No. 2,930,186, dated Jan. 11, 2018.
Final Office Action dated Jan. 22, 2018, for U.S. Appl. No. 13/830,350, of Morgan, T.B., et al., filed Mar. 14, 2013.
Examiner's Requisition for Canadian Patent Application No. 2,916,603, dated Feb. 15, 2018.
Non-Final Office Action dated Jan. 20, 2017, for U.S. Appl. No. 14/168,274, of Odawa, A.W., et al., filed Jan. 30, 2014.
Examiner Requisition for Canadian Patent Application No. 2,930,186, dated Jan. 30, 2017.
Notice of Acceptance for Australian Patent Application No. 2014347192, dated Feb. 16, 2017.
Advisory Action dated Feb. 24, 2017, for U.S. Appl. No. 14/526,361, of White, M.W., et al., filed Oct. 28, 2014.
Corrected Notice of Allowance dated Feb. 27, 2017, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014.
Notice of Allowance dated Mar. 2, 2017, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Final Office Action dated Mar. 2, 2017, for U.S. Appl. No. 14/189,880, of Aaron, P., et al., filed Feb. 25, 2014.
Advisory Action dated Mar. 9, 2017, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014.
Non-Final Office Action dated Mar. 13, 2017, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014.
Non-Final Office Action dated Mar. 15, 2017, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013.
Final Office Action dated Nov. 10, 2016, for U.S. Appl. No. 13/830,350, of Morgan, T.B., et al., filed Mar. 14, 2013.
Final Office Action dated Nov. 14, 2016, for U.S. Appl. No. 14/526,361, of White, M.W., et al., filed Oct. 28, 2014.
Final Office Action dated Nov. 29, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D.W., et al., filed Nov. 22, 2013.
Final Office Action dated Nov. 30, 2016, for U.S. Appl. No. 14/208,800, of Thome, J.P., et al., filed Mar. 13, 2014.
Advisory Action dated Dec. 22, 2016, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013.
Final Office Action dated Dec. 27, 2016, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014.
Notice of Allowance dated Jan. 13, 2017, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014.
Final Office Action dated Jan. 27, 2017, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014.
Examination Report No. 1 for Australian Patent Application No. 2014347192, dated Dec. 15, 2016.
Munson, J., and Gupta, V.K., “Location-Based Notification as a General-Purpose Service,” dated Sep. 28, 2002, Retrieved from the Internet URL—https://ai2-s2-pdfs.s3.amazonaws.com/1bb5/6ae0a70b030e2f2376ed246834bddcabd27b.pdf, pp. 40-44.
Bruene, J., “Capital One Add Rewards to Mobile App, Includes Ability to Redeem from Previous Travel,” netbanker.com, published Apr. 20, 2012, Retrieved from the Internet URL: https://web.archive.org/web/20120425043052/http://www.netbanker.com/2012/04/capital_one_add_rewards_to_mobile_app_includes_ability_to_redeem_for_previous_travel.html, on Aug. 10, 2018, pp. 1-2.
Joy, “Square Wallet—an iOS App updated to send gift cards,” Top Apps, dated Apr. 6, 2013, Retrieved from the Internet URL: http://www.topapps.net/apple-ios/square-wallet-an-ios-app-updated-to-send-gift-cards.html/, pp. 1-3.
Konrad, J., “A Traveler's Review of the Capital One Venture Rewards Card,” Runaway truck, dated on Jul. 11, 2013, Retrieved from the Internet URL: http://web.archive.org/web/20130923122057/http://queenofsubtle.com/rt/travel-tips/a-travelers-review-of-the-capital-one-venture-rewards-card, pp. 1-2.
Non-Final Office Action dated Apr. 4, 2014, for U.S. Appl. No. 14/172,842, of Borovsky, A., et al., filed Feb. 4, 2014.
Notice of Allowance dated Aug. 1, 2014, for U.S. Appl. No. 14/172,842, of Borovsky, A., et al., filed Feb. 4, 2014.
Non-Final Office Action dated Mar. 3, 2015, for U.S. Appl. No. 14/506,534, of Aaron, P., et al., filed Oct. 3, 2014.
Final Office Action dated Jun. 24, 2015, for U.S. Appl. No. 14/506,534, of Aaron, P., et al., filed Oct. 3, 2014.
Non-Final Office Action dated Apr. 8, 2016, for U.S. Appl. No. 14/187,104, of Lee, R., filed Feb. 21, 2014.
Non-Final Office Action dated May 17, 2016, for U.S. Appl. No. 29/530,241, of Andersen, R., et al., filed Jun. 15, 2015.
Final Office Action dated Oct. 5, 2016, for Design U.S. Appl. No. 29/530,241, of Andersen, R., et al., filed Jun. 15, 2015.
Non-Final Office Action dated Dec. 7, 2016, for U.S. Appl. No. 14/187,104, of Lee, R., filed Feb. 21, 2014.
Notice of Allowance dated Jan. 3, 2017, for Design U.S. Appl. No. 29/530,241, of Andersen, R., et al., filed Jun. 15, 2015.
Non-Final Office Action dated Mar. 1, 2017, for U.S. Appl. No. 14/220,064, of Maxwell, D.W., et al., filed Mar. 19, 2014.
Notice of Allowance dated Jun. 21, 2017, for U.S. Appl. No. 14/187,104, of Lee, R., filed Feb. 21, 2014.
Final Office Action dated Sep. 20, 2017, for U.S. Appl. No. 14/220,064, of Maxwell, D.W., et al., filed Mar. 19, 2014.
Notice of Allowance dated Mar. 15, 2018, for U.S. Appl. No. 14/730,860, of Sasmaz, Y., et al., filed Jun. 4, 2015.
Non-Final Office Action dated Apr. 5, 2018, for U.S. Appl. No. 14/088,113, of Maxwell, D.W., et al., filed Nov. 22, 2013.
Examination Report No. 2 for Australian Patent Application No. 2015264426, dated Jun. 20, 2018.
Non-Final Office Action dated Aug. 3, 2018, for U.S. Appl. No. 14/220,064, of Maxwell, D.W., et al., filed Mar. 19, 2014.
Provisional Applications (1)
Number Date Country
61901986 Nov 2013 US