Patent Grant
9754278
The present disclosure generally relates to activities in digital channels. More specifically, the present disclosure relates to associating activities in digital channels with one or more transaction accounts to provide rewards, discounts, and/or purchasing opportunities.
Traditional purchasing channels limit a consumer's ability to purchase goods and services. These channels require consumers to visit brick and mortar businesses or e-commerce sites. As such, there is a need to provide non-traditional purchasing channels for a consumer to purchase goods and services.
As e-commerce and digital activities grow and the boundaries of the virtual marketplace and virtual world disappear, consumers are looking for ways to more easily conduct transactions (e.g., purchases or obtaining items from merchants) or take actions associated wills transactions (e.g., spend verified activities and/or reviews). As a result, merchants, payment processors, entertainment providers and other similarly situated entities are also looking for new ways to attract consumers. Such entities are looking to provide alternatives to traditional point of sale interfaces that require payment tokens (e.g., credit/charge/debit cards, NFC, fobs, and the like) or virtual payment terminals that require consumers to provide transaction account information to allow users to more easily purchase the items they desire or require. Further, spend verification of activities allows a user to verify activities by confirming that the user's action associated with the activity is associated with an actual transaction for an item.
The systems, methods and computer program products (collectively “systems”) described herein allow a digital channel to be augmented or supplemented to become a payment channel. In operation, the system is capable of syncing or associating a consumer's channel profile with a consumers transaction account. The information to sync the profile and the transaction account may be captured in the channel, by the transaction account issuer (e.g., at the transaction account issuer website), or by a third party service. In response to the transaction account and the profile being synced, the system may track consumer activities in the digital channel. If an activity is associated with some criteria (e.g., a transaction initiation), the system may initiate an action associated with the transaction account. The system may, for example, initiate a transaction with a merchant, trigger a digital channel to request a review associated with a recently purchased item or service experience, provide a reward based on an in channel accomplishment, and/or the like.
The systems provide a seamless experience for consumers in various digital channels (e.g., social media channels and entertainment channels) by allowing consumers to initiate purchases, earn rewards and/or provide feedback without leaving a channel to engage a traditional payment channel (e.g., a brick and mortar merchant location, an e-commerce site, and/or the like). In this way, the systems consolidate payment channels and digital channels to provide a platform for social commerce. The systems provide flexibility and efficiency for consumers and merchants by allowing them to connect and transact in any channel. Further, the systems allow channel providers to reward consumers and request feedback. As such, these various systems provide consumers, merchants and channel providers with the flexibility to engage in social commerce in any suitable channel.
In the context of a social media channel (e.g. Twitter), the systems may be configured to allow purchases based on an activity in the social media channel (e.g., a Tweet). In response to a sync between the social media channel and the transaction account, a user may broadcast a predefined indicator (e.g., a hashtag), that triggers the system to initiate a purchase. The synced transaction account may be charged for the initiated purchase and that item associated with the purchase may be provided to the user.
In the context of an entertainment channel (e.g., XBox), the system may be configured to allow purchases and/or rewards. In response to a sync between the entertainment channel and the transaction account, a user may use the entertainment channel (e.g. play a video game). During use, the user may reach a predefined level of accomplishment, take an action, and/or make a selection that triggers the system to provide a reward or initiate a purchase. The reward may be provided in any suitable form to the transaction account (e.g., as a monetary credit or an offer that is loaded to the transaction account) and/or credited to a reward account associated with the user and/or the entertainment channel. The synced transaction account may be charged for the initiated purchase and that item associated with the purchase may be provided to the user.
In the context of a review channel (e.g., Trip Advisor), the system may be configured to verify an existing review or request a review in response to a purchase. In response to a sync between the review channel and the transaction account, the system may compare transactions associated with the transaction account to reviews for items associated with the user. If the system matches a review with a transaction, the system may certify or otherwise verify that the review was associated with an actual transaction. The system may also generate requests for reviews, in response to transactions for items being initiated or completed with the transaction account. In response to the review being submitted, the review system may certify or otherwise verify the review.
In the context of a reservation channel (e.g., Open Table), the system may be capable of creating a reservation for an item. In response to a sync between the reservation channel and the transaction account, the system may create a reservation for an item based on a user request. In response to the item being provided to the user by the merchant, the system may be capable of facilitating payment for the item (e.g., a meal) and updating an inventory associated with merchant (e.g., available tables at a restaurant). A record associated with the transaction may also be provided by the merchant to the user in the channel.
In various embodiments, the systems described herein are generally configured to monitor actions in digital channels. The system may associate a transaction account with a digital channel profile. Based on the association, the system may compare an action associated with the digital channel profile to criteria. If the action satisfies the criteria, the system may initiate a transaction based on the action at least partially satisfying the criteria. The system may then transmit transaction information for an item in response to the satisfying.
In various embodiments, the systems may be configured to receive a broadcast from a broadcast channel. The broadcast and the broadcast channel may be associated with a transaction account. The system may compare the broadcast to criteria. In response to the broadcast at least partially satisfying the criteria, the system may request confirmation information. The system may also transmit transaction instructions for an item in response to receiving the confirmation information.
In various embodiments, the system may receive activity information from an entertainment channel. The system may analyze the activity information based on criteria associated with a transaction. If the activity information satisfies a transaction event, the system may evaluate preferences for a transaction. The system may also initiate a transaction based on the preferences.
In various embodiments, the system may receive channel profile information and action information. The system may determine transaction account information based on the channel profile information. The system may also compare the action information to criteria. The system may transmit verification instructions in response to the profile information being associated with the transaction account information and the action information at least partially satisfying the criteria.
In various embodiments, the system may associate a reservation created in a digital channel based on an action in the channel with a transaction account. The channel profile may be associated with the action that is associated with a transaction account. The system may link the transaction information with the reservation. The transaction information may be provided by the merchant through the channel. The system may also initiate a transaction in response to the use of the reserved item and the transaction information being provided by the merchant.
The features and advantages of the present disclosure will become more apparent from the detailed description set forth below when taken in conjunction with the drawings.
In various e-embodiments, the systems, methods and computer program products described herein provide a consumer with the ability to take action in digital channels (e.g., purchases, spend verified activities, and/or the like). The detailed description of various embodiments herein makes reference to the accompanying drawings, which show various embodiments by way of illustration. While these various embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.
Systems, methods and computer program products are provided. In the detailed description herein, references to “various embodiments”, “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in alternative embodiments.
The phrases consumer, customer, user, account holder, account affiliate, cardmember and/or the like shall include any person, entity, business, government organization, business, software, hardware, machine associated with a transaction account, buys merchant offerings offered by one or more merchants using the account and/or is designated for performing transactions on the account, regardless of whether a physical card is associated with the account. For example, the cardmember may include a transaction account owner, a transaction account user, an account affiliate, a child account user, a subsidiary account user, a beneficiary of an account, a custodian of an account, and/or any other person or entity affiliated or associated with a transaction account.
Terms and phrases similar to “sync,” “syncing,” and/or “synchronizing” may include associating, tagging, flagging, correlating, using a look-up table or any other method or system for indicating or creating a relationship between elements such as, for example (i) a transaction account and (ii) an item (e.g., offer, reward, discount) and/or digital channel. Moreover, the sync may occur at any point, in response to any suitable action, event, or period of time. The sync may occur at pre-determined intervals, periodic, randomly, once, more than once, or in response to a suitable request or action.
Terms and phrases similar to “associate” and/or “associating” may include tagging, flagging, correlating, using a look-up table or any other method or system for indicating or creating a relationship between elements, such as, for example, (i) a transaction account and (ii) an item (e.g., offer, reward, discount) and/or digital channel. Moreover, the associating may occur at any point, in response to any suitable action, event, or period of time. The associating may occur at pre-determined intervals, periodic, randomly, once, more than once, or in response to a suitable request or action.
As e-commerce and digital activities grow and the boundaries of the virtual marketplace and virtual world disappear, consumers are looking for ways to more easily conduct transactions (e.g., purchases or obtaining items from merchants) or take actions associated with transactions (e.g., spend verified activities and/or reviews). As a result, merchants, payment processors, entertainment providers and other similarly situated entities are also looking for new ways to attract consumers. Such entities are looking to provide alternatives to traditional point of sale interfaces that require payment tokens (e.g., credit/charge/debit cards, NFC, fobs, and the like) or virtual payment terminals that require consumers to provide transaction account information to allow users to more easily purchase the items they desire or require. Further, spend verification of activities allows a user to verify activities by confirming that the user's action associated with the activity is associated with an actual transaction for an item.
The systems described herein allow any digital channel to be augmented or supplemented to become a payment channel. In operation, the system is capable of syncing or associating a consumer's channel profile with a consumer's transaction account. The information to sync the profile and the transaction account may be captured in the channel, by the transaction account issuer (e.g., at the transaction account issuer website), or by a third party service. In response to the transaction account and the profile being synced, the system may track consumer activities in the digital channel. If an activity meets some criteria (e.g., a transaction initiation), the system may initiate an action associated with the transaction account. The system may, for example, initiate a transaction with a merchant, trigger a digital channel to request a review associated with a recently purchased item or service experience, provide a reward based on an in channel accomplishment, and/or the like.
The systems provide a seamless experience for consumers in various digital channels (e.g., social media channels and entertainment channels) by allowing consumers to initiate purchases, earn rewards and provide feedback, without leaving a channel to engage a traditional payment channel (e.g., a brick and mortar merchant location, an e-commerce site, and/or the like). In this way, the systems consolidate payment channels and digital channels to provide a platform for social commerce. The systems provide flexibility and efficiency for consumers and merchants by allowing them to connect and transact in any channel. Further, the systems allow channel providers to reward consumers and request feedback. As such, these various systems provide consumers, merchants and channel providers with the flexibility to engage in social commerce in any suitable channel In the context of a social media channel (e.g., Twitter), the systems may be configured to allow purchases based on an activity in the social media channel (e.g., a Tweet). In response to a sync between the social media channel and the transaction account, a user may broadcast a predefined indicator (e.g., a hashtag), that triggers the system to initiate a purchase. The synced transaction account may be charged for the initiated purchase and that item associated with the purchase may be provided to the user.
In the context of an entertainment channel (e.g., XBox), the system may be configured to allow purchases and/or rewards. In response to a sync between the entertainment channel and the transaction account, a user may use the entertainment channel (e.g., play a video game). During use, the user may reach a predefined level of accomplishment, take an action, and/or make a selection that triggers the system to provide a reward or initiate a purchase. The reward may be provided in any suitable form to the transaction account (e.g., as a monetary credit or an offer that is loaded to the transaction account) and/or credited to a reward account associated with the user and/or the entertainment channel. The synced transaction account may be charged for the initiated purchase and that item associated with the purchase may be provided to the user.
In the context of a review channel (e.g., Trip Advisor), the system may be configured to verify an existing review or request a review in response to a purchase. In response to a sync between the review channel and the transaction account, the system may compare transactions associated with the transaction account to reviews for items associated with the user. If the system matches a review with a transaction, the system may certify or otherwise verify that the review was associated with an actual transaction. The system may also generate requests for reviews, in response to transactions for items being initiated or completed with the transaction account. In response to the review being submitted, the review system may certify or otherwise verify the review.
In the context of a reservation channel (e.g., Open Table), the system may be capable of creating a reservation for an item. In response to a sync between the reservation channel and the transaction account, the system may create a reservation for an item based on a user request. In response to the item being provided to the user by the merchant, the system may be capable of facilitating payment for the item (e.g., a meal) and updating an inventory associated with merchant (e.g., available tables at a restaurant). A record associated with the transaction may also be provided by the merchant to the user in the channel.
Phrases and terms similar to an “item” may include any good, service, merchant, information, experience, data, content, access, rental, lease, contribution, account, credit, debit, benefit, right, reward, points, coupons, credits, monetary equivalent, anything of value, something of minimal or no value, monetary value, non-monetary value and/or the like.
In various embodiments and as used herein, a digital channel may be any suitable channel available to a user over a network, including for example, a social media channel, an entertainment channel, a service channel, a review channel, a service scheduling channel, and/or the like. The channel may include a user interface and user account that may be created by a user. Moreover, the user may be able to access the digital channel, through a web client on any suitable electronic device. The digital channel may also be considered a non-traditional purchasing channel (e.g., a channel where information about an item may be present, but where the ability to purchase the item is not traditionally available such as, for example, an item page in a social media channel where information about an item is available).
In various embodiments, the systems, methods, and computer program products (collectively, the “system”) described herein may be capable of executing purchases for items, initiating transactions, providing purchase instructions, providing transaction instructions, and/or the like through digital channels (e.g., entertainment channels, social media channels, marketing channels, advertisements, and the like). The systems may also be capable of associating an activity with a transaction, such that the activity is certified, confirmed, or otherwise related to the transaction to verily the action in the channel. The system may sync, link, or otherwise associate a transaction account with a consumer in the channel. In response to the association, the system may track and/or receive information from a digital channel indicative of an activity with a consumer in the channel. If the activity corresponds to a purchase opportunity, the system may initiate a purchase or provide purchase instructions associated with the purchase opportunity. A merchant associated with the purchase opportunity may process the initiation or instructions. In response to the initiation or instructions complying with the terms of the purchase opportunity, the merchant may provide the item to the consumer and receive payment from the associated transaction account. For example, in a broadcast channel such as Twitter, the system may track or receive broadcasts (e.g., tweets) from consumers who have associated their transaction accounts with the broadcast channel. The system may analyze the content of the broadcast to identify a predetermined purchase indicator (e.g., a hashtag). In response to the broadcast including the purchase indicator, the system may initiate or provide instructions to a merchant to initiate a transaction and provide an item to the consumer. The system may require that the consumer confirm that the broadcast was intended to initiate a transaction for an item. As such, the system allows the consumer to purchase an item based on a broadcast and without have to use a traditional merchant channel (e.g., a brick and mortar location, a merchant or third party e-commerce site, and/or the like).
As used herein, a “merchant” may be any person or entity capable of providing a service or an item. A merchant may distribute the item in any way, for example, by exchanging the item for payment. The merchant may be capable of accepting the payment through any suitable payment channel including traditional payment channels including, for example, POS terminals, online payments terminals, transaction account networks and the like. The merchant may also accept payment through non-traditional payment terminals including, for example, social media channels, person to person payments. Further information about person to person payments is described in U.S. patent application Ser. No. 13/640,216, entitled Systems and Methods for Transferring Value via a Social Network, which is herein incorporated by reference in its entirety for any purpose.
In various embodiments and with reference to
In various embodiments, transaction account system 120 may be any hardware, software, or hardware software system capable of associating transaction information with an activity in a digital channel. Transaction account system 120 may comprise a sync module 122, a monitoring module 124, a transaction module 126 and a rewards module 128. Digital channel 130 may comprise an activity monitoring module 132 and a sync module 134.
In various embodiments and with reference to
System 200 may receive transaction account information (Step 210). The transaction account information may be requested by or provided to system 200 through any suitable channel including for example sync module 122 of transaction account system 120 and/or sync module 134 of digital channel 130. For example, system 200 may be associated with a payment processor (e.g., transaction account issuer). In this example, sync module 122 may request the transaction account information through a channel provided by the transaction account issuer (e.g., a transaction account issuer website). The transaction account information may also be captured through sync module 132 at digital channel 130 by a digital channel provider, a third party, or by system 200. The transaction account information may be captured through a fillable form, through an API or other suitable channel interface. Thus, information needed to sync a transaction account with a channel may be captured in a digital channel, by the transaction account issuer, or by a third party.
System 200 may also be capable of receiving consumer profile information for the channel (Step 220). As noted above with respect to the transaction account information, the consumer profile information for the channel may be requested by or provided to system 200 through any suitable channel. The consumer profile information may also be provided in conjunction with or at substantially the same time as the transaction account information. For example, where the transaction account information is provided to system 200 through the digital channel, the consumer profile information for the channel may be automatically sent with the captured transaction account information. More specifically, the system capturing the data may request that the consumer be logged into or otherwise known to the digital channel in response to providing the transaction account information, such that, the digital channel can automatically provide the consumer profile information with the transaction account information. In operation, in response to a user syncing transaction account and consumer profile information through a digital channel, the digital channel may capture the transaction information in the channel through a form or other suitable data capture mechanism. The form may be provided securely by the channel provider or a third party. The transaction data and consumer profile data are sent to the transaction account issuer, so that the transaction account and the consumer profile can be synced.
System 200 may also receive a token or code associated with a channel (Step 220). The token or code may be used to associate the transaction account and a digital channel. For example, a token or code may be provided to the consumer by system 200, a third party, the digital channel and/or the like. The code or token may be presented in the channel (e.g., through an advertisement) or provided outside the channel in any suitable fashion. This token may be provided to system 200, along with transaction account information. Based on the token and transaction account information, system 200 may request, obtain or otherwise determine channel profile information to associate the transaction account with the channel (Step 225). System 200 may be capable of communicating this association back to the channel provider. Based on the association, the channel provider may be capable of monitoring the activities, accomplishments, trends, interests, and/or the like of the consumer. The channel provider may be further capable of communicating these activities, accomplishments, trends, interests, and/or the like to system 200.
System 200 may also provide an indicator or data associated with the transaction account to the channel provider. The channel provider may identify the consumer profile associated with the channel. Based on this identification, the channel provider may monitor or otherwise track and/or report the activities, accomplishments, trends, interests, and/or the like of the consumer in the channel to system 200.
In various embodiments, system 200 may also be capable of requesting, defining, and/or associating preferences with the transaction account and/or consumer profile for the channel (Step 230). System 200 may allow the consumer to define various preference related to activities with a channel, purchasing, shipment, rewards, offers, and/or the like. For example, system 200 may allow the user to select whether to enter confirmation information associated with the transaction account and/or consumer profile for the channel in response to making a purchase in a digital channel. The system may also either request that confirmation is provided for each transaction (e.g., purchase through a digital channel) and/or provide that each transaction is partially or fully completed automatically. Where transactions are completed automatically, system 200 may receive confirmation information associated with the transaction account and/or consumer profile for the channel in response to the consumer defining her initial preferences (Step 235).
As noted above, system 200 may also allow a consumer to partially or fully define other preferences. For example, system 200 may allow a user to define one or more shipping addresses to facilitate fulfillment of a transaction or purchase. System 200 may also allow a user to define how offers and/or rewards are earned, distributed, provided, and the like for transactions and/or purchase events. For additional information on how offers and/or rewards are earned, distributed, and/or provided, see for example, U.S. patent application Ser. No. 13/439,768, filed, Apr. 4, 2012, and entitled System and Method for Providing International Coupon-Less Discounts, U.S. Provisional Patent Application Ser. No. 61/710,461 filed on Mar. 14, 2012 and entitled “GENERATING MERCHANT RECOMMENDATIONS FOR CONSUMERS” and U.S. Provisional Patent Application Ser. No, 61/646,778 filed on May 14, 2012 and entitled “SYSTEMS AND METHODS FOR TAILORED MARKETING BASED ON FILTERING,” each of which is incorporated by reference in its entirety for all purposes.
As part of preference selection, system 200 may provide a user with the option to associate multiple channels with a single transaction account or multiple transaction accounts with one or more channels. For example and with reference to
System 200 may also be capable of associating the transaction account information and consumer profile information for the channel and/or profile (Step 240). This association enables the transaction account to be used for transactions in response to an action being detected in a channel. For example, if the channel is a broadcast service (e.g., Twitter), a broadcast (e.g., a Tweet) may be monitored by system 200 or any other suitable system to determine whether the broadcast contains or conforms to a predefined action (e.g., a hashtag, a keyword, and/the like). In response to detecting or receiving the action (or data indicative of the action), system 200 through transaction module 126 may initiate a purchase for the consumer based on the preferences defined by the user. Moreover, if the channel is an entertainment channel (e.g., XBox), an action (e.g., an in-game accomplishment, an in-game activity, and/or the like) may be monitored by system 200 via monitoring module 124 or any other suitable system to determine whether the activity contains or conforms to a predefined action. In response to detecting or receiving the action or a selection associated with the action (or data indicative of the action or selection), system 200 may initiate a purchase for the consumer based on the preferences defined by the user. In this way, system 200 transforms any digital channel into an e-commerce channel, by tracking actions of digital channel users to identify activities that trigger purchases.
In various embodiments and with reference to
In various embodiments and with reference to
For example, system 300 may analyze the broadcast to confirm that the broadcast satisfies a certain action and/or content, (e.g., a hashtag, a keyword, a code, interest selection, like, thumbs up, or any other suitable action and/or content). System 300 may also analyze the user or source of the broadcast. System 300 may first determine whether the consumer's transaction account and channel profile are suitably associated (Step 320). If the transaction account and channel are not associated, the system 300 may request that the transaction account and channel profile be associated (Step 240). This may be accomplished in any suitable way such as, for example, according to the process described herein with respect to
Where the digital channel is a broadcast channel such as, for example, a short message service (e.g., Twitter), the broadcast channel may receive and distribute all broadcasts. In this way, the broadcast channel may be able to monitor or analyze broadcasts for the specific action. The broadcast channel may also be configured with a mechanism capable of identifying particular actions. In the context of Twitter, the action may be a predefined hashtag, keyword, and/or the like.
The action may be a hashtag that comprises the “#” sign and a symbol or keyword, as is commonly used to characterize or categorize a broadcast. The action may be any other indicator, media, event, data, act, and/or the like that is predetermined or dynamically determined by the entity making or distributing the purchase event. The action may comprise elements or symbols that are associated with the entity offering or distributing the purchase event (e.g., a branded action). For example, a purchasing event sponsored by a merchant and distributed by American Express may comprise elements of the name of the merchant (e.g., ME for Merchant A) and elements of American Express (e.g., AXP for American Express). In this example, the action may be #MEAXP. It should be understood that the action may also comprise text, pictures, video, graphical elements, symbols, sounds, act, media, data and/or the like. The action may also comprise any predetermined or dynamically determined elements or symbols that describe the purchase event or are arbitrary.
Where the hashtag is used and the broadcast channel account used to broadcast the hashtag is public, system 300 or an entity administering a purchase program in the broadcast channel can identify the user who broadcasted the action (e.g., a hashtag, keyword, or the like) by searching for a particular action among publicly available broadcasts. Broadcasts can also be linked to other social media channels or broadcast channels such as Facebook, LinkedIn, or any other publicly accessible website using a broadcast channel API or widget (e.g., the Twitter widget). The broadcasts may be displayed within a social media or publicly accessible website, so that the merchant or entity administering the purchase event can identify what users are broadcasting to take advantage of the purchase event.
The merchant or the entity administering the purchase event may also follow a user who associates a transaction account for purchases based on broadcasts. In this case, the merchant or entity administering the rewards program may receive every broadcast from the user and may be able to determine whether one or more of the user's broadcasts included the action. In response to the merchant or entity administering the purchase event having identified a broadcast that contains the action, a purchase associated with the purchase event may be initiated and an appropriate transaction associated with the purchase may be charged to the transaction account associated with the user.
Purchase events may be advertised, provided, or otherwise distributed to users that follow a merchant, manufacturer, distributor, a sponsoring entity and/or the like on a broadcast channel. Notifications of purchase events may also be distributed through any other suitable channel. The notification may contain details of the item, the digital channel where the purchase event may occur and/or the action for redeeming the purchase event.
Where the digital channel is an entertainment channel such as, for example, gaming channel (e.g. XBox), the channel may receive and distribute all actions. In this way, the entertainment channel may be able to monitor or analyze actions for a predefined action. The entertainment channel may also be configured with a mechanism capable of identifying particular and/or specific actions or levels of actions. In the context of a gaming channel, the action may be a predefined in channel activity, level of accomplishment, activity and/or the like.
The action may be any suitable action in the gaming channel. For example, in a sports game (e.g., a golf game), the action may be the selection of a particular virtual piece of equipment. Similarly, the action may be a particular level of accomplishment in a particular game or with a particular piece of virtual equipment. Moreover, the purchase opportunity may be associated with the action. For example, a level of accomplishment in a particular gaming environment may allow a user to purchase a particular reward. For example, a particular level of accomplishment in a golf theme game may allow a user to purchase tickets or otherwise acquire tickets to a golf theme event (e.g., the Masters Golf Tournament, the Phoenix Open, and/or the like). An action associated with a particular virtual piece of equipment may allow a consumer to purchase the equipment for use on the golf course (e.g., a selection of a virtual club may allow a user to purchase the actual club). Moreover, the particular accomplishment or action may allow the consumer to acquire the item associated with the virtual action or accomplishment at a discounted price or as a reward.
Where the action or accomplishment is available in a public entertainment channel, system 300 or an entity administering a purchase or rewards program in the entertainment channel may be capable of identifying the user associated with the accomplishment or action. The actions may be posted or noticed through any suitable channel. For example, the action and/or accomplishment may be visible or noticed through a publicly available accomplishment board (e.g., a scoreboard, a community accomplishment board, and/or the like). The entertainment channel may also be associated with a social media channel (e.g., Facebook, Twitter, and/or the like) such that the action or accomplishment may be broadcast or otherwise associated with the social media channel. As such, system 300 or an entity responsible for administering a purchasing program in a digital channel (e.g., an entertainment channel) may be capable of monitoring public channels for actions and/or accomplishments.
Purchase events may be advertised, provided, or otherwise distributed to users through the entertainment channel in a virtual environment (e.g., in an in-game experience). Notifications of purchase events may also be distributed through any other suitable channel. The notification may contain details of the item, the digital channel where the purchase event may occur and/or the action for redeeming the purchase event.
Payment confirmation may include a user taking action or may be a notification that a transaction has been partially or fully initiated, processed, or completed. In various embodiments, system 300 may request that the user provide transaction account details to confirm that the transaction is authorized by the user. For example, system 300 may request a verification code, the zip code associated with the billing address, a password, or any other suitable verification information. This information may be requested through the channel or may be requested in any other suitable way (e.g., a link provided to the consumer through an electronic message). In various embodiments, the confirmation details for a transaction may also be automatically supplied if the consumer provided confirmation information in response to the consumer being initially linked to the transaction account and the channel profile. As such, the transaction or purchase initiated based on the in channel action may proceed without requiring a confirming action from the consumer. Based on an action initiating a purchase, the channel or system 300 may provide the consumer with a confirmation notification. This notification may contain purchase details including for example, transaction account information, item information, channel profile information, and/or the like.
As described herein, system 300 may also be configured to monitor and provide rewards for in channel accomplishments. The in channel accomplishments may be any suitable level of achievement (e.g., accomplishing tasks in a video game), duration of use (e.g., using a music service for at least a threshold amount of time), and/or a type of use (e.g., using a music service to listen to music from a particular artist).
In various embodiments and with reference to
In various embodiments, this inventory may be determined based on market projections, initial success of a purchase event campaign, or any other suitable parameter. For example, system 400 may be configured to monitor a purchasing event in substantially real time (e.g., within minutes, hours, or days of an action defined by the merchant offering the purchasing event). Based on this monitoring, system 400 may be capable of providing the merchant with real time interest data for the purchasing event. This real time interest data may enable a merchant to dynamically adjust the inventory of an item available to system 400 based on the interest in the particular purchasing event. This reporting allows the merchant and system 400 to dynamically adjust the inventory of the item in real time.
In various embodiments, the merchant may also define an offer associated with items in the inventory (Step 430). The merchant may provide an offer to system 400 to encourage purchases through the digital channel. These offers may be associated with the pre-defined action provided by the merchant in response to the merchant defining the purchasing event. The offer may also be associated with the item. For example, the merchant may provide an instant rebate offer. In this example, system 400 may receive the predefined action through the digital channel and, based on the action, evaluate available offers for a purchase event or an item. If the action complies with the purchase event or the item, system 400 may adjust the price of the item based on the offer. The offer may apply only to items purchased through the purchasing event. The offer may also apply to the purchase of an item through traditional and/or digital channels.
In various embodiments and with reference to
If the purchasing event is active, system 500 may evaluate the inventory of an item associated with the purchasing event (Step 520). If no inventory is available (or insufficient inventory), system 500 may provide a notification to the consumer indicating that the item is no longer available for purchase or that inventory for an item is not available, but is being requested. If inventory for an item is available, system 500 may analyze the spend history of the transaction account associated with the purchase event (e.g., if the consumer has previously purchased the item associated with the purchase event) (Step 530). If the transaction account associated with the purchase event has already purchase the item, system 500 may request a confirmation for the consumer that a multiple purchase is authorized.
If the consumer has not previously purchased the item or if the consumer indicates the she wishes to purchase multiple items, system may be capable of evaluating the inventory status of the item (Step 540). System 500 may also be capable of determining whether a transaction account is linked for purchasing an item (Step 550). If the transaction account is not linked for purchasing an item through digital channels, system 500 may be capable of requesting that the user link or update the preferences associated with the transaction account to confirm that purchases may be made through digital channels as described above.
Based on the transaction account being linked to the profile to conduct purchases, system 500 may initiate, conduct, transmit, complete or otherwise authorize the purchase of an item (Step 560). In various embodiments, system 500 may also associate an offer, discount, reward, incentive, and/or the like with the purchase and/or action in the channel. Based on the purchase, system 500 may request confirmation as described above or provide a notification or a transaction associated with an action in the channel (Step 570). This notification may be provided through the channel where the purchase was initiated or through an alternative channel. This notification may be provided in substantially real time based on the transaction (e.g., substantially instantly, and/or within minutes or days of the transaction and/or action in the channel).
In various embodiments, and with reference to
System 600 may be capable of triggering a notification or creating notification instructions in response to detecting a transaction or authorization at a merchant associated with the pool (Step 630). The notification or notification instructions may be provided to the channel. System 600 may also be capable of transmitting the notification directly to the user to request that the user perform an action in the channel (Step 640). Similarly, the channel may transmit a request to the user to perform an action in the channel based on, or in response to, receiving the notification from system 600.
The notification may include a link (e.g., a hyperlink) to an item profile (e.g., a merchant profile, a product profile, and/or the like) in the channel. The notification may also contain transaction information and information regarding the action. For example, the notification may request that a user provide a review for a particularly identified transaction that the user recently completed at a merchant and/or for an item. The notification may further indicate that the review will be spend verified based on the transaction.
In various embodiments, and with reference to
In response to the user being a synced user, system 700 may review the transaction history of the identified transaction account against the associated merchant. (Step 740). System 700 may further determine if the user has spent at the merchant based on the transaction history associated with the transaction account (Step 750). System 700 may further analyze the details of the transaction to determine whether a particular transaction can be used for spend verification based on predetermined rules. In response to the transaction information at least partially conforming to the rules, system 700 may provide a verification or verification instructions to the channel such that the action or content is spend verified (Step 760).
As noted herein, a user may define preferences when the user syncs her transaction account and her channel profile. As such, system 700 may be capable of determining whether particular actions or content may be verified based on the preferences defined by the user.
In various embodiments, system 600 and system 700 may be further configured to annotate the reviews and/or content that are spend verified or otherwise certified. For example, system 600 and system 700 may be capable of annotating or otherwise associating an indicator (e.g., a badge) with the user provided review or content to promote, draw attention to, or otherwise verify the review. Moreover, the indicator may include an annotation that indicates the source of the payment or spend (e.g., “American Express Spend Verified”).
In various embodiments, and with reference to
System 800 and/or the channel may receive the action (e.g., a review) from the user. Based on receiving the action, system 800 may present the user with the option to sync the user's transaction account with the channel (Step 840). The sync may be accomplished by any suitable process including the process described herein with respect to
In various embodiments, system 800 may be capable of providing a verification and/or verification instructions if a user is not synced. For example, the channel may provide user information (e.g., an e-mail address) for a channel user in response to the user taking an action or providing content in the channel. The channel may also provide merchant and/or item information associated with the action and/or content. System 800 may associate the channel user information with information associated with a transaction account to determine an identified transaction account. System 800 may also associate the merchant and/or item information with transaction information associated with the identified transaction account. If the transaction information at least partially satisfies the merchant and/or item information provided by the channel, system 800 may provide a verification and/or verification instructions for the action and/or content provided by the user in the channel.
In various embodiments, and with reference to
The verification system may be capable of preparing a look-up or comparison table 900 associated with the submission of channel information by the channel. Table 900 may compare one or more data elements provided by the channel and reconciled by the verification system including, for example, the username (line item 910), the DOB (line item 920), the merchant name (line item 930), and/or the date of action/transaction (line item 840). The verification system may be configured to analyze the elements of table 900 to against predetermined rules. For example, the verification system may be configured to particularly identify a merchant and/or item based on the information provided by the channel. This identification may include an identification code, location, store number, item number (e.g., SKU, UPC, QR code, and/or the like) and/or the like. Moreover, the verification system may be capable of analyzing the channel information and the information associated with the transaction account (e.g., the details of the transaction information) to determine whether a particular transaction is appropriate for a verification of an action. The predetermined rules may be defined as a time period (e.g., less than one (1) year between the date of the review and the date of the transaction), an amount (e.g., a minimum spend), and/or the like. Based on this analysis, the verification system may provide a verification and/or verification instructions for the channel action and/or content.
In various embodiments, and with reference to
In various embodiments and with reference to
The user may use the reserved item (Step 1140). In response to the user using the reserved item, the merchant POS may send a charge associated with the use of the item to the channel (Step 1150). The channel may then provide the charge to the system, a transaction account issuer (e.g., the transaction account system 120), or any other suitable party (Step 1160). In response to the charge being provided, the system, the transaction account issuer, or the third party may process payment (e.g., initiate a transaction associated with the synced transaction account) for the charge (Step 1170).
System 1100 may further evaluate transaction information associated with the payment to determine whether the payment corresponds with an activity associated with the transaction account. In this way, system 110 may function as a fraud detection system. More specifically, system 1100 may compare the transaction information associated with the purchase to reservation information associated with the reservation information associated with a synced transaction account. Where the transaction details comply with the reservation information, system 110 may authorize the transaction. Moreover, where the transaction information corresponds to an item associated with the reservation, system 110 may request a review of the item as described herein. System 1100 may further associated transaction information or provide an indication of a spend verification based on the transaction information and the associated item reservation information. System 1100 may also determine that transaction information is not associated with or contradicts reservation information. In response to the discrepancy, system 1100 may not authorize a transaction. The failure to authorize a charge to the transaction account may be based on a failure of the transaction to comply with business rules (e.g., the transaction information does not correspond to the reservation information).
System 1100 may further trigger a real-time (based on the transaction initiation) notification, or the transaction to the user (1180). The notification may be provided through any suitable channel. For example, the notification may be provided to the user through the digital channel (Step 1190). The notification may be provided through an application on an electronic device (e.g., a Smartphone) or any other suitable channel and/or device.
In various embodiments and with reference to
A user may use the reserved item (Step 1250), associated with the reservation. Moreover, the merchant providing the item may process a payment for the item using the synced transaction account (Step 1260) associated with the reservation and/or the digital channel used to make the reservation. In various embodiments, any suitable entity may process the transaction for the item. For example, a transaction account issuer may be directly or indirectly (e.g., through the digital channel) linked to a payment processor. Based on the stored transaction account information associated with the reservation, system 1200 or another suitable system may initiate and/or complete payment for a reserved item in response to the user using the item.
Where the item used by the user associated with the reservation was previously associated with a digital channel, the status of the item may be updated based on the use in the digital channel (Step 1270). As such, the inventory for the item may be adjusted accordingly by system 1200 as described herein. The use of the item associated with the reservation and/or the charge associated with the use may also cause the total charge for the item to be automatically updated in the digital channel (Step 1280). Moreover, a post-transaction notification, may be sent to the user (Step 1290). The notification may be sent through the digital channel associated with the reservation, the channel associated with the transaction, or any other suitable channel described herein.
For example, in various embodiments and with reference to
As such, the systems described herein facilitate purchases in digital channels. The systems described herein further facilitate monitor and rewarding activities or accomplishments in a digital channel. The systems described herein further facilitate confirmation or verification of activities in digital channels based on transaction information.
Any communication, transmission and/or channel discussed herein may include any system or method for delivering content (e.g. data, information, metadata, etc.), and/or the content itself. The content may be presented in any form or medium, and in various embodiments, the content may be delivered electronically and/or capable of being presented electronically. For example, a channel may comprise a website, a uniform resource locator (“URL”), a document (e.g., a Microsoft Word document, a Microsoft Excel document, an Adobe .pdf document, etc.), an “ebook,” an “emagazine,” an application or microapplication (as described below), an SMS or other type of text message, an email, Facebook, Twitter, MMS and/or other type of communication technology. In various embodiments, a channel may be hosted or provided by a data partner. In various embodiments, the distribution channel may comprise at least one of a merchant website, a social media website, affiliate or partner websites, an external vendor, a mobile device communication, social media network and/or location based service. Distribution channels may include at least one of a merchant website, a social media site, affiliate or partner websites, an external vendor, and a mobile device communication. Examples of social media sites include Facebook®, Foursquare®, Twitter®, MySpace®, LinkedIn®, and the like, Examples of affiliate or partner websites include American Express®, Groupon®, LivingSocial®, and the like. Moreover, examples of mobile device communications include texting, email, and mobile applications for smartphones.
A “consumer profile” or “consumer profile data” may comprise any information or data about a consumer that describes an attribute associated with the consumer (e.g., a preference, an interest, demographic information, personally identifying information, and the like).
in various embodiments, the methods described herein are implemented using the various particular machines described herein. The methods described herein may be implemented using the below particular machines, and those hereinafter developed, in any suitable combination, as would be appreciated immediately by one skilled in the art. Further, as is unambiguous from this disclosure, the methods described herein may result in various transformations of certain articles.
For the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical system.
The various system components discussed herein may include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; and a plurality of databases. Various databases used herein may include: client data; merchant data; financial institution data; and/or like data useful in the operation of the system. As those skilled in the art will appreciate, user computer may include an operating system (e.g., Windows NT, Windows 95/98/3000, Windows XP, Windows Vista, Windows 7, OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as various conventional support software and drivers typically associated with computers.
The present system or any part(s) or function(s) thereof may be implemented using hardware, software or a combination thereof and may be implemented in one or more computer systems or other processing systems. However, the manipulations performed by embodiments were often referred to in terms, such as matching or selecting, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein. Rather, the operations may be machine operations. Useful machines for performing the various embodiments include general purpose digital computers or similar devices.
In fact, in various embodiments, the embodiments are directed toward one or more computer systems capable of carrying out the functionality described herein. The computer system includes one or more processors, such as processor. The processor is connected to a communication infrastructure (e.g., a communications bus, cross over bar, or network). Various software embodiments are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the relevant art(s) how to implement various embodiments using other computer systems and/or architectures. Computer system can include a display interface that forwards graphics, text, and other data from the communication infrastructure (or from a frame buffer not shown) for display on a display unit.
Computer system also includes a main memory, such as for example random access memory (RAM), and may also include a secondary memory. The secondary memory may include, for example, a hard disk drive and/or a removable storage drive, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive reads from and/or writes to a removable storage unit in a well-known manner. Removable storage unit represents a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by removable storage drive. As will be appreciated, the removable storage unit includes a computer usable storage medium having stored therein computer software and/or data.
In various embodiments, secondary memory may include other similar devices for allowing computer programs or other instructions to be loaded into computer system. Such devices may include, for example, a removable storage unit and an interface. Examples of such may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an erasable programmable read only memory (EPROM), or programmable read only memory (PROM)) and associated socket, and other removable storage units and interfaces, which allow software and data to be transferred from the removable storage unit to computer system.
Computer system may also include a communications interface. Communications interface allows software and data to be transferred between computer system and external devices. Examples of communications interface may include a modem, a network interface (such as an Ethernet card), a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communications interface are in the form of signals which may be electronic, electromagnetic, optical or other signals capable of being received by communications interface. These signals are provided to communications interface via a communications path (e.g., channel). This channel carries signals and may be implemented using wire, cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link, wireless and other communications channels.
The terms “computer program medium” and “computer usable medium” are used to generally refer to media such as removable storage drive and a hard disk installed in hard disk drive. These computer program products provide software to computer system.
Computer programs (also referred to as computer control logic) are stored in main memory and/or secondary memory. Computer programs may also be received via communications interface. Such computer programs, when executed, enable the computer system to perform the features as discussed herein. In particular, the computer programs, when executed, enable the processor to perform the features of various embodiments. Accordingly, such computer programs represent controllers of the computer system.
In various embodiments, software may be stored in a computer program product and loaded into computer system using removable storage drive, hard disk drive or communications interface. The control logic (software), when executed by the processor, causes the processor to perform the functions of various embodiments as described herein. In various embodiments, hardware components such as application specific integrated circuits (ASICs). Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).
In various embodiments, the server may include application servers (e.g. WEB SPHERE, WEB LOGIC, JBOSS). In various embodiments, the server may include web servers (e.g. APACHE, IIS, GWS, SUN JAVA SYSTEM WEB SERVER).
A web client includes any device (e.g., personal computer) which communicates via any network, for example such as those discussed herein. Such browser applications comprise Internet browsing software installed within a computing unit or a system to conduct online transactions and/or communications. These computing units or systems may take the form of a computer or set of computers, although other types of computing units or systems may be used, including laptops, notebooks, tablets, hand held computers, personal digital assistants, set-top boxes, workstations, computer-servers, main frame computers, mini-computers, PC servers, pervasive computers, network sets of computers, personal computers, such as iPads, iMacs, and MacBooks, kiosks, terminals, point of sale (POS) devices and/or terminals, televisions, or any other device capable of receiving data over a network. A web-client may run Microsoft Internet Explorer, Mozilia Firefox, Google Chrome, Apple Safari, or any other of the myriad software packages available for browsing the internet.
Practitioners will appreciate that a web client may or may not be in direct contact with an application server. For example, a web client may access the services of an application server through another server and/or hardware component, which may have a direct or indirect connection to an Internet server. For example, a web client may communicate with an application server via a load balancer. In an exemplary embodiment, access is through a network or the Internet through a commercially-available web-browser software package.
As those skilled in the art will appreciate, a web client includes an operating system (e.g., Windows NT, 95/98/3000/CE/Mobiie, OS2, UNIX, Linux, Solaris, MacOS, PalmOS, etc.) as well as various conventional support software and drivers typically associated with computers. A web client may include any suitable personal computer, network computer, workstation, personal digital assistant, cellular phone, smart phone, minicomputer, mainframe or the like. A web client can be in a home or business environment with access to a network. In an exemplary embodiment, access is through a network or the Internet through a commercially available web-browser software package. A web client may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). A web client may implement several application layer protocols including http, https, ftp, and sftp.
In various embodiments, components, modules, and/or engines of system 200 may be implemented as micro-applications or micro-apps. Micro-apps are typically deployed in the context of a mobile operating system, including for example, a Palm mobile operating system, a Windows mobile operating system, an Android Operating System, Apple iOS, a Blackberry operating system and the like. The micro-app may be configured to leverage the resources of the larger operating system and associated hardware via a set of predetermined rules which govern the operations of various operating systems and hardware resources. For example, where a micro-app desires to communicate with a device or network other than the mobile device or mobile operating system, the micro-app may leverage the communication protocol of the operating system and associated device hardware under the predetermined rules of the mobile operating system. Moreover, where the micro-app desires an input from a user, the micro-app may be configured to request a response from the operating system which monitors various hardware components and then communicates a detected input from the hardware to the micro-app.
As used herein, the term “network” includes any cloud, cloud computing system or electronic communications system or method which incorporates hardware and/or software components. Communication among the parties may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant (e.g., iPhone®, Palm Pilot®, Blackberry®), cellular phone, kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although the system is frequently described herein as being implemented with TCP/IP communications protocols, the system may also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH), or any number of existing or future protocols. If the network is In the nature of a public network, such as the Internet, it may be advantageous to presume the network to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS AND PROTOCOLS (1998); JAVA 2 COMPLETE, various authors, (Sybex 1999); DEBORAH RAY AND ERIC RAY, MASTERING HTML 4.0 (1997); and LOSHIN, TCP/IP CLEARLY EXPLAINED (1997) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THE DEFINITIVE GUIDE (3002), the contents of which are hereby incorporated by reference.
The various system components may be independently, separately or collectively suitably coupled to the network via data links which includes, for example, a connection to an Internet Service Provider (ISP) over the local loop as is typically used in connection with standard modem communication, cable modem. Dish networks, ISDN, Digital Subscriber Line (DSL), or various wireless communication methods, see, e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which is hereby incorporated by reference. It is noted that the network may be implemented as other types of networks, such as an interactive television (ITV) network. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein.
“Cloud” or “Cloud computing” includes a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing may include location-independent computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For more information regarding cloud computing, see the NIST's (National Institute of Standards and Technology) definition of cloud computing at http://csrc.nist.gov/publications/nistpubs/900-145/SP900-145.pdf (last visited June 2012), which is hereby incorporated by reference in its entirety.
As used herein, “transmit” may include sending electronic data from one system component to another over a network connection. Additionally, as used herein, “data” may include encompassing information such as commands, queries, files, data for storage, and the like in digital or any other form.
As used herein, “issue a debit”, “debit” or “debiting” refers to either causing the debiting of a stored value or prepaid card-type financial account, or causing the charging of a credit or charge card-type financial account, as applicable.
The system contemplates uses in association with web services, utility computing, pervasive and individualized computing, security and identity solutions, autonomic computing, cloud computing, commodity computing, mobility and wireless solutions, open source, biometrics, grid computing and/or mesh computing.
Any databases discussed herein may include relational, hierarchical, graphical, or object-oriented structure and/or any other database configurations. Common database products that may be used to implement the databases include DB2 by IBM (Armonk, N.Y.), various database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or Microsoft SQL Server by Microsoft Corporation (Redmond, Wash.), MySQL by MySQL AB (Uppsala, Sweden), or any other suitable database product. Moreover, the databases may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields or any other data structure. Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in pre-selected databases or data sectors. Various database tuning steps are contemplated to optimize database performance. For example, frequently used files such as indexes may be placed on separate file systems to reduce In/Out (“I/O”) bottlenecks.
More particularly, a “key field” partitions the database according to the high-level class of objects defined by the key field. For example, certain types of data may be designated as a key field in a plurality of related data tables and the data tables may then be linked on the basis of the type of data in the key field. The data corresponding to the key field in each of the linked data tables is preferably the same or of the same type. However, data tables having similar, though not identical, data in the key fields may also be linked by using AGREP, for example. In accordance with one embodiment, any suitable data storage technique may be utilized to store data without a standard format. Data sets may be stored using any suitable technique, including, for example, storing individual files using an ISO/IEC 7816-4 file structure; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files using a hierarchical filing system; data sets stored as records in a single file (including compression, SQL accessible, hashed via one or more keys, numeric, alphabetical by first tuple, etc.); Binary Large Object (BLOB); stored as ungrouped data elements encoded using ISO/IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) as in ISO/IEC 8824 and 8825; and/or other proprietary techniques that may include fractal compression methods, image compression methods, etc.
In one exemplary embodiment, the ability to store a wide variety of information in different formats is facilitated by storing the information as a BLOB. Thus, any binary information can be stored in a storage space associated with a data set. As discussed above, the binary information may be stored on the financial transaction instrument or external to but affiliated with the financial transaction instrument. The BLOB method may store data sets as ungrouped data elements formatted as a block of binary via a fixed memory offset using either fixed storage allocation, circular queue techniques, or best practices with respect to memory management (e.g., paged memory, least recently used, etc.). By using BLOB methods, the ability to store various data sets that have different formats facilitates the storage of data associated with the financial transaction instrument by multiple and unrelated owners of the data sets. For example, a first data set which may be stored may be provided by a first party, a second data set which may be stored may be provided by an unrelated second party, and yet a third data set which may be stored, may be provided by an third party unrelated to the first and second party. Each of these three exemplary data sets may contain different information that is stored using different data storage formats and/or techniques. Further, each data set may contain subsets of data that also may be distinct from other subsets.
As stated above, in various embodiments, the data can be stored without regard to a common format. However, in one exemplary embodiment, the data set (e.g., BLOB) may be annotated in a standard manner when provided for manipulating the data onto the financial transaction instrument. The annotation may comprise a short header, trailer, or other appropriate indicator related to each data set that is configured to convey information useful in managing the various data sets. For example, the annotation may be called a “condition header”, “header”, “trailer”, or “status”, herein, and may comprise an indication of the status of the data set or may include an identifier correlated to a specific issuer or owner of the data. In one example, the first three bytes of each data set BLOB may be configured or configurable to indicate the status of that particular data set; e.g., LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes of data may be used to indicate for example, the identity of the issuer, user, transaction/membership account identifier or the like. Each of these condition annotations are further discussed herein.
The data set annotation may also be used for other types of status information as well as various other purposes. For example, the data set annotation may include security information establishing access levels. The access levels may, for example, be configured to permit only certain individuals, levels of employees, companies, or other entities to access data sets, or to permit access to specific data sets based on the transaction, merchant, issuer, user or the like. Furthermore, the security information may restrict/permit only certain actions such as accessing, modifying, and/or deleting data sets. In one example, the data set annotation indicates that only the data set owner or the user are permitted to delete a data set, various identified users may be permitted to access the data set for reading, and others are altogether excluded from accessing the data set. However, other access restriction parameters may also be used allowing various entities to access a data set with various permission levels as appropriate. The data, including the header or trailer may be received by a standalone interaction device configured to add, delete, modify, or augment the data in accordance with the header or trailer. As such, in one embodiment, the header or trailer is not stored on the transaction device along with the associated issuer-owned data but instead the appropriate action may be taken by providing to the transaction instrument user at the stand alone device, the appropriate option for the action to be taken. The system may contemplate a data storage arrangement wherein the header or trailer, or header or trailer history, of the data is stored on the transaction instrument in relation to the appropriate data.
One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers or other components of the system may consist of any combination thereof at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.
Encryption may be performed by way of any of the techniques now available in the art or which may become available—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, GPG (GnuPG), and symmetric and asymmetric cryptosystems.
The computing unit of the web client may be further equipped with an Internet browser connected to the Internet or an intranet using standard dial-up, cable, DSL or any other Internet protocol known in the art. Transactions originating at a web client may pass through a firewall in order to prevent unauthorized access from users of other networks. Further, additional firewalls may be deployed between the varying components of CMS to further enhance security.
Firewall may include any hardware and/or software suitably configured to protect CMS components and/or enterprise computing resources from users of other networks. Further, a firewall may be configured to limit or restrict access to various systems and components behind the firewall for web clients connecting through a web server. Firewall may reside in varying configurations including Stateful Inspection, Proxy based, access control lists, and Packet Filtering among others. Firewall may be integrated within a web server or any other CMS components or may further reside as a separate entity. A firewall may implement network address translation (“NAT”) and/or network address port translation (“NAPT”). A firewall may accommodate various tunneling protocols to facilitate secure communications, such as those used in virtual private networking. A firewall may implement a demilitarized zone (“DMZ”) to facilitate communications with a public network such as the Internet. A firewall may be integrated as software within an Internet server, any other application server components or may reside within another computing device or may take the form of a standalone hardware component.
The computers discussed herein may provide a suitable website or other Internet-based graphical user interlace which is accessible by users. In one embodiment, the Microsoft Internet Information Server (IIS), Microsoft Transaction Server (MTS), and Microsoft SQL Server, are used in conjunction with the Microsoft operating system, Microsoft NT web server software, a Microsoft SQL Server database system, and a Microsoft Commerce Server. Additionally, components such as Access or Microsoft SQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be used to provide an Active Data Object (ADO) compliant database management system. In one embodiment, the Apache web server is used in conjunction with a Linux operating system, a MySQL database, and the Perl, PHP, and/or Python programming languages.
Any of the communications, inputs, storage, databases or displays discussed herein may be facilitated through a website having web pages. The term “web page” as it is used herein is not meant to limit the type of documents and applications that might be used to interact with the user. For example, a typical website might include, in addition to standard HTML documents, various forms, Java applets, JavaScript, active server pages (ASP), common gateway interface scripts (CGI), extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX (Asynchronous Javascript And XML), helper applications, plug-ins, and the like. A server may include a web service that receives a request from a web server, the request including a URL (http://yahoo.com/stockquotes/ge) and an IP address (123.56.789.234). The web server retrieves the appropriate web pages and sends the data or applications for the web pages to the IP address. Web services are applications that are capable of interacting with other applications over a communications means, such as the internet. Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methods are well known in the art, and are covered in many standard texts. See, e.g., ALEX NGHIEM, IT WEB SERVICES: A ROADMAP FOR THE ENTERPRISE (3003), hereby incorporated by reference.
Middleware may include any hardware and/or software suitably configured to facilitate communications and/or process transactions between disparate computing systems. Middleware components are commercially available and known in the art. Middleware may be implemented through commercially available hardware and/or software, through custom hardware and/or software components, or through a combination thereof. Middleware may reside in a variety of configurations and may exist as a standalone system or may be a software component residing on the Internet server. Middleware may be configured to process transactions between the various components of an application server and any number of internal or external systems for any of the purposes disclosed herein. WebSphere MQTM (formerly MQSeries) by IBM, Inc. (Armonk, N.Y.) is an example of a commercially available middleware product. An Enterprise Service Bus (“ESB”) application is another example of middleware.
Practitioners will also appreciate that there are a number of methods for displaying data within a browser-based document. Data may be represented as standard text or within a fixed list, scrollable list, drop-down list, editable text field, fixed text field, pop-up window, and the like. Likewise, there are a number of methods available for modifying data in a web page such as, for example, free text entry using a keyboard, selection of menu items, check boxes, option boxes, and the like.
The system and method may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language such as C, C++, C#, Java, JavaScript, VBScript, Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly, PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX shell script, and extensible markup language (XML) with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system could be used to detect or prevent security issues with a client-side scripting language, such as JavaScript, VBScript or the like. For a basic introduction of cryptography and network security, see any of the following references: (1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” by Bruce Schneier, published by John Wiley & Sons (second edition, 1995); (2) “Java Cryptography” by Jonathan Knudson, published by O'Reilly & Associates (1998); (3) “Cryptography & Network Security: Principles & Practice” by William Stallings, published by Prentice Hall; all of which are hereby incorporated by reference.
As used herein, the term “end user”, “consumer”, “customer”, “cardmember”, “business” or “merchant” may be used interchangeably with each other, and each shall mean any person, entity, government organization, business, machine, hardware, and/or software. A bank may be part of the system, but the bank may represent other types of card issuing institutions, such as credit card companies, card sponsoring companies, or third party issuers under contract with financial institutions. It is further noted that other participants may be involved in some phases of the transaction, such as an intermediary settlement institution, but these participants are not shown.
Each participant is equipped with a computing device in order to interact with the system and facilitate online commerce transactions. The customer has a computing unit in the form of a personal computer, although other types of computing units may be used including laptops, notebooks, hand held computers, set-top boxes, cellular telephones, touch-tone telephones and the like. The merchant has a computing unit implemented in the form of a computer-server, although other implementations are contemplated by the system. The bank has a computing center shown as a main frame computer. However, the bank computing center may be implemented in other forms, such as a mini-computer, a PC server, a network of computers located in the same of different geographic locations, or the like. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein
The merchant computer and the bank computer may be interconnected via a second network, referred to as a payment network. The payment network which may be part of certain transactions represents existing proprietary networks that presently accommodate transactions for credit cards, debit cards, and other types of financial/banking cards. The payment network is a closed network that is assumed to be secure from eavesdroppers. Exemplary transaction networks may include the American Express®, VisaNet® and the Veriphone®networks.
The electronic commerce system may be implemented at the customer and issuing bank. In an exemplary implementation, the electronic commerce system is implemented as computer software modules loaded onto the customer computer and the banking computing center. The merchant computer does not require any additional software to participate in the online commerce transactions supported by the online commerce system.
As will be appreciated by one of ordinary skill in the art, the system may be embodied as a customization of an existing system, an add-on product, a processing apparatus executing upgraded software, a stand alone system, a distributed system, a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, any portion of the system or a module may take the form of a processing apparatus executing code, an internet based embodiment, an entirely hardware embodiment, or an embodiment combining aspects of the internet, software and hardware. Furthermore, the system may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, optical storage devices, magnetic storage devices, and/or the like.
The system and method is described herein with reference to screen shots, block diagrams and flowchart illustrations of methods, apparatus (e.g., systems), and computer program products according to various embodiments. It will be understood that each functional block of the block diagrams and the flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions.
These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions. Further, illustrations of the process flows and the descriptions thereof may make reference to user windows, webpages, websites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise in any number of configurations including the use of windows, webpages, web forms, popup windows, prompts and the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single webpages and/or windows but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple webpages and/or windows but have been combined for simplicity.
The term “non-transitory” is to be understood to remove only propagating transitory signals per se from the claim scope and does not relinquish rights to all standard computer-readable media that are not only propagating transitory signals per se. Stated another way, the meaning of the term “non-transitory computer-readable medium” and “non-transitory computer-readable storage medium” should be construed to exclude only those types of transitory computer-readable media which were found in In Re Nuijten to fall outside the scope of patentable subject matter under 35 U.S.C. §101.
In yet another embodiment, the transponder, transponder-reader, and/or transponder-reader system are configured with a biometric security system that may be used for providing biometrics as a secondary form of identification. The biometric security system may include a transponder and a reader communicating with the system. The biometric security system also may include a biometric sensor that detects biometric samples and a device for verifying biometric samples. The biometric security system may be configured with one or more biometric scanners, processors and/or systems. A biometric system may include one or more technologies, or any portion thereof, such as, for example, recognition of a biometric. As used herein, a biometric may include a user's voice, fingerprint, facial, ear, signature, vascular patterns, DNA sampling, hand geometry, sound, olfactory, keystroke/typing, iris, retinal or any other biometric relating to recognition based upon any body part, function, system, attribute and/or other characteristic, or any portion thereof.
Phrases and terms similar to an “entity” may include any individual, consumer, customer, group, business, organization, government entity, transaction account issuer or processor (e.g., credit, charge, etc.), merchant, consortium of merchants, account holder, charitable organization, software, hardware, and/or any other type of entity. The terms “user,” “consumer,” “purchaser,” and/or the plural form of these terms are used interchangeably throughout herein to refer to those persons or entities that are alleged to be authorized to use a transaction account.
Phrases and terms similar to “account”, “account number”, “account code” or “consumer account” as used herein, may include any device, code (e.g., one or more of an authorization/access code, personal identification number (“PIN”), Internet code, other identification code, and/or the like), number, letter, symbol, digital certificate, smart chip, digital signal, analog signal, biometric or other identifier/indicia suitably configured to allow the consumer to access, interact with or communicate with the system. The account number may optionally be located on or associated with a rewards account, charge account, credit account, debit account, prepaid account, telephone card, embossed card, smart card, magnetic stripe card, bar code card, transponder, radio frequency card or an associated account.
The system may include or interface with any of the foregoing accounts, devices, and/or a transponder and reader (e.g. RFID reader) in RF communication with the transponder (which may include a fob), or communications between an initiator and a target enabled by near field communications (NFC). Typical devices may include, for example, a key ring, tag, card, cell phone, wristwatch or any such form capable of being presented for interrogation. Moreover, the system, computing unit or device discussed herein may include a “pervasive computing device,” which may include a traditionally non-computerized device that is embedded with a computing unit. Examples may include watches, Internet enabled kitchen appliances, restaurant tables embedded with RF readers, wallets or purses with imbedded transponders, etc. Furthermore, a device or financial transaction instrument may have electronic and communications functionality enabled, for example, by: a network of electronic circuitry that is printed or otherwise incorporated onto or within the transaction instrument (and typically referred to as a “smart card”); a fob having a transponder and an RFID reader; and/or near field communication (NFC) technologies. For more information regarding NFC, refer to the following specifications all of which are incorporated by reference herein: ISO/IEC 18092/ECMA-340, Near Field Communication Interface and Protocol-1 (NFCIP-1); ISO/IEC 21481/ECMA-352, Near Field Communication Interface and Protocol-2 (NFCIP-2); and EMV 4.2 available at http://www.emvco.com/default.aspx.
The account number may be distributed and stored in any form of plastic, electronic, magnetic, radio frequency, wireless, audio and/or optical device capable of transmitting or downloading data from itself to a second device. A consumer account number may be, for example, a sixteen-digit account number, although each credit provider has its own numbering system, such as the fifteen-digit numbering system used by American Express. Each company's account numbers comply with that company's standardized format such that the company using a fifteen-digit format will generally use three-spaced sets of numbers, as represented by the number “0000 000000 00000”. The first five to seven digits are reserved for processing purposes and identify the issuing bank, account type, etc. In this example, the last (fifteenth) digit is used as a sum check for the fifteen digit number. The intermediary eight-to-eleven digits are used to uniquely identify the consumer. A merchant account number may be, for example, any number or alpha-numeric characters that identify a particular merchant for purposes of account acceptance, account reconciliation, reporting, or the like.
In various embodiments, an account number may identify a consumer. In addition, in various embodiments, a consumer may be identified by a variety of identifiers, including, for example, an email address, a telephone number, a cookie id, a radio frequency identifier (RFID), a biometric, and the like.
Phrases and terms similar to “financial institution” or “transaction account issuer” may include any entity that offers transaction account services. Although often referred to as a “financial institution,” the financial institution may represent any type of bank, lender or other type of account issuing institution, such as credit card companies, card sponsoring companies, or third party issuers under contract with financial institutions. It is further noted that other participants may be involved in some phases of the transaction, such as an intermediary settlement institution.
The terms “payment vehicle,” “financial transaction instrument,” “transaction instrument” and/or the plural form of these terms may be used interchangeably throughout to refer to a financial instrument.
Phrases and terms similar to “merchant,” “supplier” or “seller” may include any entity that receives payment or other consideration. For example, a supplier may request payment tor goods sold to a buyer who holds an account with a transaction account issuer.
Phrases and terms similar to a “buyer” may include any entity that receives goods or services in exchange for consideration (e.g. financial payment). For example, a buyer may purchase, lease, rent, barter or otherwise obtain goods from a supplier and pay the supplier using a transaction account.
Phrases and terms similar to “internal data” may include any data a credit issuer possesses or acquires pertaining to a particular consumer. Internal data may be gathered before, during, or after a relationship between the credit issuer and the transaction account holder (e.g., the consumer or buyer). Such data may include consumer demographic data. Consumer demographic data includes any data pertaining to a consumer. Consumer demographic data may include consumer name, address, telephone number, email address, employer and social security number. Consumer transactional data is any data pertaining to the particular transactions in which a consumer engages during any given time period. Consumer transactional data may include, for example, transaction amount, transaction time, transaction vendor/merchant, and transaction vendor/merchant location. Transaction vendor/merchant location may contain a high degree of specificity to a vendor/merchant. For example, transaction vendor/merchant location may include a particular gasoline filing station in a particular postal code located at a particular cross section or address. Also, for example, transaction vendor/merchant location may include a particular web address, such as a Uniform Resource Locator (“URL”), an email address and/or an Internet Protocol (“IP”) address for a vendor/merchant. Transaction vendor/merchant, and transaction vendor/merchant location may be associated with a particular consumer and further associated with sets of consumers. Consumer payment data includes any data pertaining to a consumer's history of paying debt obligations. Consumer payment data may include consumer payment dates, payment amounts, balance amount, and credit limit. Internal data may further comprise records of consumer service calls, complaints, requests for credit line increases, questions, and comments. A record of a consumer service call includes, for example, date of call, reason for call, and any transcript or summary of the actual call.
Phrases similar to a “payment processor” may include a company (e.g., a third party) appointed (e.g., by a merchant) to handle transactions. A payment processor may include an issuer, acquirer, authorizer and/or any other system or entity involved in the transaction process. Payment processors may be broken down into two types: front-end and back-end. Front-end payment processors have connections to various transaction accounts and supply authorization and settlement services to the merchant banks' merchants. Back-end payment processors accept settlements from front-end payment processors and, via The Federal Reserve Bank, move money from an issuing bank to the merchant bank. In an operation that will usually take a few seconds, the payment processor will both check the details received by forwarding the details to the respective account's issuing bank or card association for verification, and may carry out a series of anti-fraud measures against the transaction. Additional parameters, including the account's country of issue and its previous payment history, may be used to gauge the probability of the transaction being approved. In response to the payment processor receiving confirmation that the transaction account details have been verified, the information may be relayed back to the merchant, who will then complete the payment transaction. In response to the verification being denied, the payment processor relays the information, to the merchant, who may then decline tire transaction. Phrases similar to a “payment gateway” or “gateway” may include an application service provider service that authorizes payments for e-businesses, online retailers, and/or traditional brick and mortar merchants. The gateway may be the equivalent of a physical point of sale terminal located in most retail outlets. A payment gateway may protect transaction account details by encrypting sensitive information, such as transaction account numbers, to ensure that information passes securely between the customer and the merchant and also between merchant and payment processor.
Benefits, other advantages, and solutions to problems have been described herein with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of the disclosure. The scope of the disclosure is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.” Moreover, where a phrase similar to ‘at least one of A, B, and C’ or ‘at least one of A, B, or C’ is used in the claims or specification, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C. Although the disclosure includes a method, it is contemplated that it may be embodied as computer program instructions on a tangible computer-readable carrier, such as a magnetic or optical memory or a magnetic or optical disk. All structural, chemical, and functional equivalents to the elements of the above-described exemplary embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the present disclosure, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. No claim element herein is to be construed under the provisions of 35 U.S.C. 112, sixth paragraph, unless the element is expressly recited using the phrase “means for.” As used herein, the terms “comprises”, “comprising”, or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
This application claims priority to, and the benefit of, U.S. Provisional Ser. No. 61/701,683, filed Sep. 16, 2012 and entitled “PURCHASING IN A DIGITAL-CHANNEL,”which is hereby incorporated by reference in its entirety for all purposes. This application further claims priority to, and the benefit of, U.S. Provisional Ser. No. 61/701,685, filed Sep. 16, 2012, which is hereby incorporated by reference in its entirety for all purposes. This application also claims priority to U.S. Provisional Ser. No. 61/701,686, filed Sep. 16, 2012, which is hereby incorporated by reference in its entirety for all purposes. This application also claims priority to U.S. Provisional Ser. No. 61/701,688, filed Sep. 16, 2012, which is hereby incorporated by reference in its entirety for all purposes. This application also claims priority to U.S. Provisional Ser. No. 61/754,354, filed Jan. 18, 2013, which is hereby incorporated by reference in its entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4833308 | Humble | May 1989 | A |
| 4882675 | Nichtberger et al. | Nov 1989 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5467269 | Flaten | Nov 1995 | A |
| 5471669 | Lidman | Nov 1995 | A |
| 5729693 | Holda-Fleck | Mar 1998 | A |
| 5918211 | Sloane | Jun 1999 | A |
| 5923016 | Fredregill et al. | Jul 1999 | A |
| 5948040 | DeLorme et al. | Sep 1999 | A |
| 5953706 | Patel | Sep 1999 | A |
| 6009411 | Kepecs | Dec 1999 | A |
| 6018718 | Walker et al. | Jan 2000 | A |
| 6035280 | Christensen | Mar 2000 | A |
| 6039244 | Finsterwald | Mar 2000 | A |
| 6222914 | McMullin | Apr 2001 | B1 |
| 6266649 | Linden et al. | Jul 2001 | B1 |
| 6321208 | Barnett et al. | Nov 2001 | B1 |
| 6330543 | Kepecs | Dec 2001 | B1 |
| 6332126 | Peirce et al. | Dec 2001 | B1 |
| 6336099 | Barnett et al. | Jan 2002 | B1 |
| 6343317 | Glorikian | Jan 2002 | B1 |
| 6360167 | Millington et al. | Mar 2002 | B1 |
| 6370514 | Messner | Apr 2002 | B1 |
| 6381603 | Chan et al. | Apr 2002 | B1 |
| 6414635 | Stewart et al. | Jul 2002 | B1 |
| 6430539 | Lazarus et al. | Aug 2002 | B1 |
| 6434534 | Walker et al. | Aug 2002 | B1 |
| 6542814 | Polidi et al. | Apr 2003 | B2 |
| 6584448 | Laor | Jun 2003 | B1 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6606619 | Ortega et al. | Aug 2003 | B2 |
| 6691915 | Thaxton et al. | Feb 2004 | B1 |
| 6738711 | Ohmura et al. | May 2004 | B2 |
| 6748365 | Quinlan et al. | Jun 2004 | B1 |
| 6882290 | French et al. | Apr 2005 | B2 |
| 6883708 | Fiedler et al. | Apr 2005 | B1 |
| 6904408 | McCarthy et al. | Jun 2005 | B1 |
| 6915265 | Johnson | Jul 2005 | B1 |
| 6937995 | Kepecs | Aug 2005 | B1 |
| 7003476 | Samra et al. | Feb 2006 | B1 |
| 7010497 | Nyhan et al. | Mar 2006 | B1 |
| 7016856 | Wiggins | Mar 2006 | B1 |
| 7016860 | Modani et al. | Mar 2006 | B2 |
| 7054830 | Eggleston et al. | May 2006 | B1 |
| 7072851 | Wilcox et al. | Jul 2006 | B1 |
| 7107238 | Hatakama et al. | Sep 2006 | B2 |
| 7120591 | Solomon et al. | Oct 2006 | B1 |
| 7139793 | Lala et al. | Nov 2006 | B2 |
| 7146328 | Solomon et al. | Dec 2006 | B1 |
| 7165037 | Lazarus et al. | Jan 2007 | B2 |
| 7302429 | Wanker | Nov 2007 | B1 |
| 7392224 | Bauer et al. | Jun 2008 | B1 |
| 7428505 | Levy et al. | Sep 2008 | B1 |
| 7430521 | Walker et al. | Sep 2008 | B2 |
| 7455226 | Hammond | Nov 2008 | B1 |
| 7472073 | Masi | Dec 2008 | B1 |
| 7493268 | Kepros et al. | Feb 2009 | B2 |
| 7496520 | Handel et al. | Feb 2009 | B1 |
| 7499889 | Golan et al. | Mar 2009 | B2 |
| 7506805 | Chakravarthy | Mar 2009 | B1 |
| 7512551 | Postrel | Mar 2009 | B2 |
| 7596566 | Patwardhan | Sep 2009 | B1 |
| 7599858 | Grady et al. | Oct 2009 | B1 |
| 7618318 | Ciancio et al. | Nov 2009 | B2 |
| 7630935 | Loeger et al. | Dec 2009 | B2 |
| 7647278 | Foth | Jan 2010 | B1 |
| 7653572 | Thompson | Jan 2010 | B1 |
| 7660743 | Messa et al. | Feb 2010 | B1 |
| 7665660 | Degliantoni et al. | Feb 2010 | B2 |
| 7668749 | Kepros et al. | Feb 2010 | B2 |
| 7676467 | Kozyrczak et al. | Mar 2010 | B1 |
| 7681786 | Chakravarthy | Mar 2010 | B1 |
| 7706808 | Aggarwal et al. | Apr 2010 | B1 |
| 7711586 | Aggarwal et al. | May 2010 | B2 |
| 7734486 | Mortimore, Jr. | Jun 2010 | B2 |
| 7739134 | Mortimore, Jr. | Jun 2010 | B2 |
| 7742954 | Handel et al. | Jun 2010 | B1 |
| 7743002 | Hernandez | Jun 2010 | B2 |
| 7747524 | Brown | Jun 2010 | B2 |
| 7752328 | Mortimore, Jr. et al. | Jul 2010 | B2 |
| 7765119 | Messa et al. | Jul 2010 | B2 |
| 7788141 | Sim | Aug 2010 | B1 |
| 7797199 | Forshaw et al. | Sep 2010 | B2 |
| 7801760 | Handel et al. | Sep 2010 | B2 |
| 7806328 | Chakravarthy | Oct 2010 | B2 |
| 7814029 | Siegel | Oct 2010 | B1 |
| 7844488 | Merriman et al. | Nov 2010 | B2 |
| 7844490 | Patterson | Nov 2010 | B2 |
| 7865513 | Welch et al. | Jan 2011 | B2 |
| 7870022 | Bous et al. | Jan 2011 | B2 |
| 7899704 | Thompson | Mar 2011 | B1 |
| 7925540 | Orttung et al. | Apr 2011 | B1 |
| 7933810 | Morgenstern | Apr 2011 | B2 |
| 7937330 | Handel et al. | May 2011 | B2 |
| 7941374 | Orttung et al. | May 2011 | B2 |
| 7958017 | Rempe et al. | Jun 2011 | B1 |
| 7962381 | Handel et al. | Jun 2011 | B2 |
| 7966213 | Messa et al. | Jun 2011 | B2 |
| 7970666 | Handel | Jun 2011 | B1 |
| 7991664 | Stone | Aug 2011 | B1 |
| 8073719 | Orttung et al. | Dec 2011 | B2 |
| 8078496 | Postrel | Dec 2011 | B2 |
| 8082270 | Goyal | Dec 2011 | B2 |
| 8090707 | Orttung et al. | Jan 2012 | B1 |
| 8095402 | Orttung et al. | Jan 2012 | B2 |
| 8108304 | Loeger et al. | Jan 2012 | B2 |
| 8117073 | Orttung et al. | Feb 2012 | B1 |
| 8121953 | Orttung et al. | Feb 2012 | B1 |
| 8126771 | Walker et al. | Feb 2012 | B2 |
| 8126776 | Messa et al. | Feb 2012 | B2 |
| 8131588 | Walker et al. | Mar 2012 | B2 |
| 8140387 | Heywood | Mar 2012 | B2 |
| 8145522 | Warren et al. | Mar 2012 | B2 |
| 8160922 | Postrel | Apr 2012 | B2 |
| 8170916 | Dicker et al. | May 2012 | B1 |
| 8175926 | Handel et al. | May 2012 | B1 |
| 8180682 | Narayanaswami et al. | May 2012 | B2 |
| 8180796 | Mah et al. | May 2012 | B1 |
| 8213423 | Breau | Jul 2012 | B1 |
| 8249934 | Agarwal et al. | Aug 2012 | B2 |
| 8438061 | Grimes | May 2013 | B2 |
| 8459551 | Lee et al. | Jun 2013 | B2 |
| 8463643 | Bennett | Jun 2013 | B2 |
| 8463706 | Cervenka et al. | Jun 2013 | B2 |
| 8463851 | Bennett et al. | Jun 2013 | B2 |
| 8468053 | Bennett | Jun 2013 | B2 |
| 8473334 | Gibbs | Jun 2013 | B2 |
| 8484088 | Orttung et al. | Jul 2013 | B1 |
| 8484093 | Bennett et al. | Jul 2013 | B2 |
| 8489456 | Burgess et al. | Jul 2013 | B2 |
| 8494901 | Magadi et al. | Jul 2013 | B2 |
| 8494914 | Mesaros | Jul 2013 | B2 |
| 8504423 | Rotbard et al. | Aug 2013 | B2 |
| 8515810 | Grimes | Aug 2013 | B2 |
| 8517258 | Taylor et al. | Aug 2013 | B2 |
| 8543470 | Grady et al. | Sep 2013 | B2 |
| 8560389 | Burgess et al. | Oct 2013 | B2 |
| 8573477 | Bennett et al. | Nov 2013 | B2 |
| 8573491 | Bennett et al. | Nov 2013 | B2 |
| 8606630 | Fordyce, III et al. | Dec 2013 | B2 |
| 8615426 | Carlson | Dec 2013 | B2 |
| 8621068 | Zohar et al. | Dec 2013 | B2 |
| 8621215 | Iyer | Dec 2013 | B1 |
| 8626579 | Fordyce, III et al. | Jan 2014 | B2 |
| 8639567 | Winters | Jan 2014 | B2 |
| 8650071 | Pointer et al. | Feb 2014 | B2 |
| 8655695 | Qu | Feb 2014 | B1 |
| 8725635 | Klein et al. | May 2014 | B2 |
| 8874674 | Allison et al. | Oct 2014 | B2 |
| 9009082 | Marshall et al. | Apr 2015 | B1 |
| 9031866 | Ng et al. | May 2015 | B1 |
| 9430773 | Aloni et al. | Aug 2016 | B2 |
| 20010014868 | Herz et al. | Aug 2001 | A1 |
| 20010020242 | Gupta et al. | Sep 2001 | A1 |
| 20010037254 | Glikman | Nov 2001 | A1 |
| 20010054003 | Chien et al. | Dec 2001 | A1 |
| 20020052841 | Guthrie | May 2002 | A1 |
| 20020069079 | Vega | Jun 2002 | A1 |
| 20020069312 | Jones | Jun 2002 | A1 |
| 20020082920 | Austin et al. | Jun 2002 | A1 |
| 20020095357 | Hunter et al. | Jul 2002 | A1 |
| 20020099824 | Bender | Jul 2002 | A1 |
| 20020138343 | Weatherford et al. | Sep 2002 | A1 |
| 20020178056 | Lim | Nov 2002 | A1 |
| 20030004802 | Callegari | Jan 2003 | A1 |
| 20030027630 | Kelly et al. | Feb 2003 | A1 |
| 20030028518 | Mankoff | Feb 2003 | A1 |
| 20030033211 | Haines et al. | Feb 2003 | A1 |
| 20030061093 | Todd | Mar 2003 | A1 |
| 20030078832 | Alvarez et al. | Apr 2003 | A1 |
| 20030208442 | Cockrill et al. | Nov 2003 | A1 |
| 20030233278 | Marshall | Dec 2003 | A1 |
| 20040006509 | Mannik et al. | Jan 2004 | A1 |
| 20040039686 | Klebanoff | Feb 2004 | A1 |
| 20040098326 | James | May 2004 | A1 |
| 20040098332 | Dvir | May 2004 | A1 |
| 20040122736 | Strock et al. | Jun 2004 | A1 |
| 20040153389 | Lortscher | Aug 2004 | A1 |
| 20040225509 | Andre et al. | Nov 2004 | A1 |
| 20040225573 | Ling | Nov 2004 | A1 |
| 20040243468 | Cohagan et al. | Dec 2004 | A1 |
| 20050010394 | Bergeron | Jan 2005 | A1 |
| 20050010428 | Bergeron | Jan 2005 | A1 |
| 20050010472 | Quatse et al. | Jan 2005 | A1 |
| 20050021401 | Postrel | Jan 2005 | A1 |
| 20050033583 | Bergeron | Feb 2005 | A1 |
| 20050033605 | Bergeron | Feb 2005 | A1 |
| 20050065848 | Mitchell et al. | Mar 2005 | A1 |
| 20050071225 | Bortolin et al. | Mar 2005 | A1 |
| 20050071227 | Hammad et al. | Mar 2005 | A1 |
| 20050071228 | Bortolin et al. | Mar 2005 | A1 |
| 20050071230 | Mankoff | Mar 2005 | A1 |
| 20050096976 | Nelms | May 2005 | A1 |
| 20050149394 | Postrel | Jul 2005 | A1 |
| 20050159996 | Lazarus | Jul 2005 | A1 |
| 20050192863 | Mohan | Sep 2005 | A1 |
| 20050240477 | Friday et al. | Oct 2005 | A1 |
| 20050246272 | Kitada et al. | Nov 2005 | A1 |
| 20050273388 | Roetter | Dec 2005 | A1 |
| 20060004633 | Ashbaugh | Jan 2006 | A1 |
| 20060026067 | Nicholas et al. | Feb 2006 | A1 |
| 20060041480 | Briggs | Feb 2006 | A1 |
| 20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
| 20060064372 | Gupta | Mar 2006 | A1 |
| 20060074749 | Kline | Apr 2006 | A1 |
| 20060076400 | Fletcher | Apr 2006 | A1 |
| 20060085240 | Salehi-sedeh et al. | Apr 2006 | A1 |
| 20060095434 | McCullough et al. | May 2006 | A1 |
| 20060111930 | Ayer et al. | May 2006 | A1 |
| 20060116800 | Obradovich et al. | Jun 2006 | A1 |
| 20060122874 | Postrel | Jun 2006 | A1 |
| 20060129426 | Pearson | Jun 2006 | A1 |
| 20060136299 | Ruhmkorf | Jun 2006 | A1 |
| 20060155603 | Abendroth et al. | Jul 2006 | A1 |
| 20060155641 | Postrel | Jul 2006 | A1 |
| 20060167753 | Teague et al. | Jul 2006 | A1 |
| 20060173672 | Bergeron | Aug 2006 | A1 |
| 20060178932 | Lang | Aug 2006 | A1 |
| 20060195359 | Robinson et al. | Aug 2006 | A1 |
| 20060212355 | Teague et al. | Sep 2006 | A1 |
| 20060224449 | Byerley et al. | Oct 2006 | A1 |
| 20060241859 | Kimchi et al. | Oct 2006 | A1 |
| 20060242011 | Bell et al. | Oct 2006 | A1 |
| 20060253321 | Heywood | Nov 2006 | A1 |
| 20060258397 | Kaplan et al. | Nov 2006 | A1 |
| 20060259364 | Strock et al. | Nov 2006 | A1 |
| 20060271552 | McChesney et al. | Nov 2006 | A1 |
| 20070000997 | Lambert et al. | Jan 2007 | A1 |
| 20070010942 | Bill | Jan 2007 | A1 |
| 20070022019 | Sherwin et al. | Jan 2007 | A1 |
| 20070033104 | Collins et al. | Feb 2007 | A1 |
| 20070038515 | Postrel | Feb 2007 | A1 |
| 20070038516 | Apple et al. | Feb 2007 | A1 |
| 20070050258 | Dohse | Mar 2007 | A1 |
| 20070061216 | Jain et al. | Mar 2007 | A1 |
| 20070061223 | Rodriguez et al. | Mar 2007 | A1 |
| 20070073599 | Perry et al. | Mar 2007 | A1 |
| 20070083428 | Goldstein | Apr 2007 | A1 |
| 20070094114 | Bufford | Apr 2007 | A1 |
| 20070129995 | Brandow | Jun 2007 | A1 |
| 20070130000 | Assanassios | Jun 2007 | A1 |
| 20070136135 | Loeger et al. | Jun 2007 | A1 |
| 20070146812 | Lawton | Jun 2007 | A1 |
| 20070150349 | Handel et al. | Jun 2007 | A1 |
| 20070192178 | Fung et al. | Aug 2007 | A1 |
| 20070192192 | Haberman et al. | Aug 2007 | A1 |
| 20070198354 | Senghore et al. | Aug 2007 | A1 |
| 20070198432 | Pitroda et al. | Aug 2007 | A1 |
| 20070208879 | Liu | Sep 2007 | A1 |
| 20070210152 | Read | Sep 2007 | A1 |
| 20070214040 | Patel et al. | Sep 2007 | A1 |
| 20070233517 | Dayal | Oct 2007 | A1 |
| 20070244741 | Blume et al. | Oct 2007 | A1 |
| 20070244811 | Tumminaro | Oct 2007 | A1 |
| 20070260513 | Pavlov | Nov 2007 | A1 |
| 20070260523 | Schadt | Nov 2007 | A1 |
| 20070288312 | Wang | Dec 2007 | A1 |
| 20070288372 | Behar et al. | Dec 2007 | A1 |
| 20080004917 | Mortimore, Jr. | Jan 2008 | A1 |
| 20080004919 | Stubbs | Jan 2008 | A1 |
| 20080004980 | Hernandez | Jan 2008 | A1 |
| 20080005148 | Welch et al. | Jan 2008 | A1 |
| 20080021772 | Aloni et al. | Jan 2008 | A1 |
| 20080032720 | Mamdani et al. | Feb 2008 | A1 |
| 20080033857 | Moses | Feb 2008 | A1 |
| 20080040211 | Walker et al. | Feb 2008 | A1 |
| 20080040288 | Mortimore, Jr. et al. | Feb 2008 | A1 |
| 20080052140 | Neal et al. | Feb 2008 | A1 |
| 20080052151 | Xie et al. | Feb 2008 | A1 |
| 20080059220 | Roth et al. | Mar 2008 | A1 |
| 20080065491 | Bakman | Mar 2008 | A1 |
| 20080082418 | Fordyce et al. | Apr 2008 | A1 |
| 20080091445 | Mihic | Apr 2008 | A1 |
| 20080091528 | Rampell et al. | Apr 2008 | A1 |
| 20080091537 | Miller et al. | Apr 2008 | A1 |
| 20080091549 | Chang et al. | Apr 2008 | A1 |
| 20080091828 | Mortimore, Jr. | Apr 2008 | A1 |
| 20080092162 | Lundy et al. | Apr 2008 | A1 |
| 20080109317 | Singh | May 2008 | A1 |
| 20080109489 | Sherwood | May 2008 | A1 |
| 20080120155 | Pliha | May 2008 | A1 |
| 20080126515 | Chambers et al. | May 2008 | A1 |
| 20080147450 | Mortimore, Jr. | Jun 2008 | A1 |
| 20080147514 | Shuster et al. | Jun 2008 | A1 |
| 20080147773 | Aaron | Jun 2008 | A1 |
| 20080154664 | Kuo et al. | Jun 2008 | A1 |
| 20080162206 | Mak et al. | Jul 2008 | A1 |
| 20080167991 | Carlson et al. | Jul 2008 | A1 |
| 20080189169 | Turpin et al. | Aug 2008 | A1 |
| 20080195475 | Lambert et al. | Aug 2008 | A1 |
| 20080196060 | Varghese | Aug 2008 | A1 |
| 20080201197 | Orttung et al. | Aug 2008 | A1 |
| 20080201224 | Owens et al. | Aug 2008 | A1 |
| 20080201432 | Orttung et al. | Aug 2008 | A1 |
| 20080210753 | Plozay et al. | Sep 2008 | A1 |
| 20080255940 | Perreault et al. | Oct 2008 | A1 |
| 20080262925 | Kim | Oct 2008 | A1 |
| 20080263135 | Olliphant | Oct 2008 | A1 |
| 20080270223 | Collins et al. | Oct 2008 | A1 |
| 20080270251 | Coelho | Oct 2008 | A1 |
| 20080276270 | Kotaru et al. | Nov 2008 | A1 |
| 20080281710 | Hoal | Nov 2008 | A1 |
| 20080294624 | Kanigsberg et al. | Nov 2008 | A1 |
| 20080300894 | John | Dec 2008 | A1 |
| 20080300979 | Abhyanker | Dec 2008 | A1 |
| 20090006142 | Orttung et al. | Jan 2009 | A1 |
| 20090006143 | Orttung et al. | Jan 2009 | A1 |
| 20090006188 | Guo et al. | Jan 2009 | A1 |
| 20090006194 | Sridharan et al. | Jan 2009 | A1 |
| 20090012839 | Fusillo et al. | Jan 2009 | A1 |
| 20090018916 | Seven et al. | Jan 2009 | A1 |
| 20090030609 | Orttung et al. | Jan 2009 | A1 |
| 20090030742 | Orttung et al. | Jan 2009 | A1 |
| 20090030769 | Orttung et al. | Jan 2009 | A1 |
| 20090030779 | Tollinger et al. | Jan 2009 | A1 |
| 20090037264 | Del Favero et al. | Feb 2009 | A1 |
| 20090055292 | Chong et al. | Feb 2009 | A1 |
| 20090063268 | Burgess et al. | Mar 2009 | A1 |
| 20090063351 | Schmeyer | Mar 2009 | A1 |
| 20090076912 | Rajan et al. | Mar 2009 | A1 |
| 20090094048 | Wallace | Apr 2009 | A1 |
| 20090132347 | Anderson et al. | May 2009 | A1 |
| 20090140799 | Kasperkovitz | Jun 2009 | A1 |
| 20090150272 | Blythe | Jun 2009 | A1 |
| 20090156310 | Fargo | Jun 2009 | A1 |
| 20090163227 | Collins | Jun 2009 | A1 |
| 20090164314 | Blythe | Jun 2009 | A1 |
| 20090171842 | Blythe | Jul 2009 | A1 |
| 20090171853 | Georgiou et al. | Jul 2009 | A1 |
| 20090182718 | Waclawik et al. | Jul 2009 | A1 |
| 20090210261 | Mortimore, Jr. et al. | Aug 2009 | A1 |
| 20090228365 | Tomchek et al. | Sep 2009 | A1 |
| 20090247193 | Kalavade | Oct 2009 | A1 |
| 20090247282 | Cheng | Oct 2009 | A1 |
| 20090248457 | Munter et al. | Oct 2009 | A1 |
| 20090248543 | Nihalani et al. | Oct 2009 | A1 |
| 20090259499 | Bhojwani et al. | Oct 2009 | A1 |
| 20090265236 | Schultz et al. | Oct 2009 | A1 |
| 20090271263 | Regmi et al. | Oct 2009 | A1 |
| 20090276306 | Hicks | Nov 2009 | A1 |
| 20090287562 | Bosch et al. | Nov 2009 | A1 |
| 20090288012 | Hertel et al. | Nov 2009 | A1 |
| 20090288140 | Huber | Nov 2009 | A1 |
| 20090289111 | Motycka et al. | Nov 2009 | A1 |
| 20090313109 | Bous et al. | Dec 2009 | A1 |
| 20090319353 | Palmeri | Dec 2009 | A1 |
| 20090327062 | Botes | Dec 2009 | A1 |
| 20090327174 | Honkala | Dec 2009 | A1 |
| 20100002722 | Porat | Jan 2010 | A1 |
| 20100057565 | Au-Yeung et al. | Mar 2010 | A1 |
| 20100076777 | Paretti et al. | Mar 2010 | A1 |
| 20100079336 | Skibiski et al. | Apr 2010 | A1 |
| 20100082418 | Loeger et al. | Apr 2010 | A1 |
| 20100082446 | Hjelm et al. | Apr 2010 | A1 |
| 20100088174 | Cohagan et al. | Apr 2010 | A1 |
| 20100094697 | Cananaugh | Apr 2010 | A1 |
| 20100094698 | Cawley | Apr 2010 | A1 |
| 20100094699 | Beal | Apr 2010 | A1 |
| 20100106568 | Grimes | Apr 2010 | A1 |
| 20100106569 | Grimes | Apr 2010 | A1 |
| 20100106578 | Allio et al. | Apr 2010 | A1 |
| 20100106596 | Grimes | Apr 2010 | A1 |
| 20100114661 | Alderfer | May 2010 | A1 |
| 20100114686 | Carlson et al. | May 2010 | A1 |
| 20100131342 | Thibedeau | May 2010 | A1 |
| 20100131840 | Walker et al. | May 2010 | A1 |
| 20100138299 | Preston et al. | Jun 2010 | A1 |
| 20100145744 | Beck et al. | Jun 2010 | A1 |
| 20100145762 | Coladonato et al. | Jun 2010 | A1 |
| 20100145778 | Fordyce et al. | Jun 2010 | A1 |
| 20100145786 | Fordyce, III et al. | Jun 2010 | A1 |
| 20100145860 | Pelegero | Jun 2010 | A1 |
| 20100153194 | Oram | Jun 2010 | A1 |
| 20100179879 | Cunningham et al. | Jul 2010 | A1 |
| 20100191572 | Newman et al. | Jul 2010 | A1 |
| 20100211419 | Nickolayev et al. | Aug 2010 | A1 |
| 20100228613 | Anderson et al. | Sep 2010 | A1 |
| 20100241502 | Walker et al. | Sep 2010 | A1 |
| 20100241559 | O'Connor et al. | Sep 2010 | A1 |
| 20100250351 | Gillenson et al. | Sep 2010 | A1 |
| 20100250356 | Gillenson et al. | Sep 2010 | A1 |
| 20100257047 | Foodman et al. | Oct 2010 | A1 |
| 20100262456 | Feng et al. | Oct 2010 | A1 |
| 20100312629 | Wolf et al. | Dec 2010 | A1 |
| 20100324990 | D'Angelo et al. | Dec 2010 | A1 |
| 20100332307 | Parento | Dec 2010 | A1 |
| 20110004497 | Mortimore, Jr. et al. | Jan 2011 | A1 |
| 20110022448 | Strock et al. | Jan 2011 | A1 |
| 20110022455 | Wolf et al. | Jan 2011 | A1 |
| 20110029363 | Gillenson et al. | Feb 2011 | A1 |
| 20110029364 | Roeding et al. | Feb 2011 | A1 |
| 20110029367 | Olson et al. | Feb 2011 | A1 |
| 20110035266 | Patterson | Feb 2011 | A1 |
| 20110040539 | Szymczyk et al. | Feb 2011 | A1 |
| 20110047023 | Lieblang et al. | Feb 2011 | A1 |
| 20110055880 | Archer | Mar 2011 | A1 |
| 20110066483 | Salmon et al. | Mar 2011 | A1 |
| 20110066548 | Rodin | Mar 2011 | A1 |
| 20110078030 | Borst et al. | Mar 2011 | A1 |
| 20110078055 | Faribault et al. | Mar 2011 | A1 |
| 20110083101 | Sharon et al. | Apr 2011 | A1 |
| 20110087530 | Fordyce et al. | Apr 2011 | A1 |
| 20110087531 | Winters et al. | Apr 2011 | A1 |
| 20110093327 | Fordyce et al. | Apr 2011 | A1 |
| 20110093335 | Fordyce et al. | Apr 2011 | A1 |
| 20110093361 | Morales | Apr 2011 | A1 |
| 20110106607 | Alfonso et al. | May 2011 | A1 |
| 20110119133 | Igelman et al. | May 2011 | A1 |
| 20110125561 | Marcus | May 2011 | A1 |
| 20110125565 | MacIlwaine et al. | May 2011 | A1 |
| 20110137716 | Reuthe et al. | Jun 2011 | A1 |
| 20110137717 | Reuthe et al. | Jun 2011 | A1 |
| 20110137721 | Bansal | Jun 2011 | A1 |
| 20110145047 | Chetty et al. | Jun 2011 | A1 |
| 20110145149 | Valdes et al. | Jun 2011 | A1 |
| 20110161149 | Kaplan | Jun 2011 | A1 |
| 20110161154 | McLaughlin et al. | Jun 2011 | A1 |
| 20110178928 | Carmichael et al. | Jul 2011 | A1 |
| 20110184792 | Butcher et al. | Jul 2011 | A1 |
| 20110191150 | Blackhurst et al. | Aug 2011 | A1 |
| 20110213670 | Strutton | Sep 2011 | A1 |
| 20110218031 | Bryant et al. | Sep 2011 | A1 |
| 20110225033 | Schmeyer et al. | Sep 2011 | A1 |
| 20110231224 | Winters | Sep 2011 | A1 |
| 20110231235 | MacIlwaine et al. | Sep 2011 | A1 |
| 20110231246 | Bhatia et al. | Sep 2011 | A1 |
| 20110238469 | Gershman et al. | Sep 2011 | A1 |
| 20110246280 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246281 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246287 | Wright et al. | Oct 2011 | A1 |
| 20110246299 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251883 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251891 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251934 | Satyavolu et al. | Oct 2011 | A1 |
| 20110264490 | Durvasula et al. | Oct 2011 | A1 |
| 20110270617 | Pacheco E Murta et al. | Nov 2011 | A1 |
| 20110270666 | Welsh et al. | Nov 2011 | A1 |
| 20110276373 | Juszczak et al. | Nov 2011 | A1 |
| 20110276377 | Kim et al. | Nov 2011 | A1 |
| 20110282702 | Mortimore, Jr. | Nov 2011 | A1 |
| 20110288918 | Cervenka et al. | Nov 2011 | A1 |
| 20110295689 | Brady | Dec 2011 | A1 |
| 20110295749 | Scalisi | Dec 2011 | A1 |
| 20110302011 | Yoder et al. | Dec 2011 | A1 |
| 20110313840 | Mason et al. | Dec 2011 | A1 |
| 20110313874 | Hardie et al. | Dec 2011 | A1 |
| 20110320250 | Gemmell et al. | Dec 2011 | A1 |
| 20120004964 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004965 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004966 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004967 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004968 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004969 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004970 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004975 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010932 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010933 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010934 | Walker et al. | Jan 2012 | A1 |
| 20120010936 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010937 | Hanson et al. | Jan 2012 | A1 |
| 20120022923 | Walker et al. | Jan 2012 | A1 |
| 20120023122 | Gregov et al. | Jan 2012 | A1 |
| 20120029996 | Lang et al. | Feb 2012 | A1 |
| 20120030048 | Manley et al. | Feb 2012 | A1 |
| 20120035997 | Burgess et al. | Feb 2012 | A1 |
| 20120036079 | Sushil et al. | Feb 2012 | A1 |
| 20120036178 | Gavini et al. | Feb 2012 | A1 |
| 20120046958 | Pynadath | Feb 2012 | A1 |
| 20120047008 | Alhadeff et al. | Feb 2012 | A1 |
| 20120053987 | Satyavolu et al. | Mar 2012 | A1 |
| 20120059701 | Van der Veen et al. | Mar 2012 | A1 |
| 20120066037 | Glen | Mar 2012 | A1 |
| 20120066046 | Satyavolu et al. | Mar 2012 | A1 |
| 20120066050 | Satyavolu et al. | Mar 2012 | A1 |
| 20120066051 | Black et al. | Mar 2012 | A1 |
| 20120066062 | Yoder et al. | Mar 2012 | A1 |
| 20120072270 | Waylonis et al. | Mar 2012 | A1 |
| 20120078689 | Rothschild | Mar 2012 | A1 |
| 20120101881 | Taylor et al. | Apr 2012 | A1 |
| 20120109751 | Binenstock et al. | May 2012 | A1 |
| 20120150740 | Isaacson et al. | Jun 2012 | A1 |
| 20120196568 | Bakshi | Aug 2012 | A1 |
| 20120197707 | Cohagan | Aug 2012 | A1 |
| 20120203604 | Baker et al. | Aug 2012 | A1 |
| 20120203846 | Hull et al. | Aug 2012 | A1 |
| 20120209672 | Winner et al. | Aug 2012 | A1 |
| 20120209695 | Winner et al. | Aug 2012 | A1 |
| 20120209696 | Winner et al. | Aug 2012 | A1 |
| 20120209771 | Winner et al. | Aug 2012 | A1 |
| 20120220308 | Ledlie | Aug 2012 | A1 |
| 20120221437 | Yoo | Aug 2012 | A1 |
| 20120221479 | Schneck et al. | Aug 2012 | A1 |
| 20120226530 | Gebb et al. | Sep 2012 | A1 |
| 20120239417 | Pourfallah | Sep 2012 | A1 |
| 20120239479 | Amaro et al. | Sep 2012 | A1 |
| 20120253852 | Pourfallah | Oct 2012 | A1 |
| 20120253957 | Bakshi | Oct 2012 | A1 |
| 20120278127 | Kirakosyan et al. | Nov 2012 | A1 |
| 20120296724 | Faro et al. | Nov 2012 | A1 |
| 20120303425 | Katzin et al. | Nov 2012 | A1 |
| 20120303430 | Tiku et al. | Nov 2012 | A1 |
| 20130013396 | Vinson et al. | Jan 2013 | A1 |
| 20130024256 | Wolf et al. | Jan 2013 | A1 |
| 20130040654 | Parish | Feb 2013 | A1 |
| 20130041902 | Swann et al. | Feb 2013 | A1 |
| 20130060623 | Walker et al. | Mar 2013 | A1 |
| 20130073336 | Heath | Mar 2013 | A1 |
| 20130073361 | Silver | Mar 2013 | A1 |
| 20130073366 | Heath | Mar 2013 | A1 |
| 20130073371 | Bosworth et al. | Mar 2013 | A1 |
| 20130073374 | Heath | Mar 2013 | A1 |
| 20130073376 | Heath | Mar 2013 | A1 |
| 20130073377 | Heath | Mar 2013 | A1 |
| 20130073387 | Heath | Mar 2013 | A1 |
| 20130073388 | Heath | Mar 2013 | A1 |
| 20130073389 | Heath | Mar 2013 | A1 |
| 20130073400 | Heath | Mar 2013 | A1 |
| 20130073473 | Heath | Mar 2013 | A1 |
| 20130073568 | Federov et al. | Mar 2013 | A1 |
| 20130091000 | Hagey et al. | Apr 2013 | A1 |
| 20130103472 | Burgess et al. | Apr 2013 | A1 |
| 20130110555 | Dunham | May 2013 | A1 |
| 20130110604 | Rooke et al. | May 2013 | A1 |
| 20130124283 | Kaulbach | May 2013 | A1 |
| 20130132175 | Claessen et al. | May 2013 | A1 |
| 20130132183 | Klein et al. | May 2013 | A1 |
| 20130145016 | Vantalon | Jun 2013 | A1 |
| 20130151602 | McClelland et al. | Jun 2013 | A1 |
| 20130173320 | Bank et al. | Jul 2013 | A1 |
| 20130173478 | Farhi | Jul 2013 | A1 |
| 20130178280 | Ganz | Jul 2013 | A1 |
| 20130179246 | Ross et al. | Jul 2013 | A1 |
| 20130191195 | Carlson et al. | Jul 2013 | A1 |
| 20130212177 | Friedman | Aug 2013 | A1 |
| 20130218653 | Rooke et al. | Aug 2013 | A1 |
| 20130238412 | Boncyk et al. | Sep 2013 | A1 |
| 20130246146 | Fischer et al. | Sep 2013 | A1 |
| 20130246185 | Hardman et al. | Sep 2013 | A1 |
| 20130260727 | Knudson et al. | Oct 2013 | A1 |
| 20130262209 | Boyer | Oct 2013 | A1 |
| 20130268333 | Ovick et al. | Oct 2013 | A1 |
| 20130275192 | Aissa | Oct 2013 | A1 |
| 20130304563 | Haupt et al. | Nov 2013 | A1 |
| 20130325946 | Allison, Jr. et al. | Dec 2013 | A1 |
| 20130346170 | Epstein et al. | Dec 2013 | A1 |
| 20140006129 | Heath | Jan 2014 | A1 |
| 20140006132 | Barker | Jan 2014 | A1 |
| 20140025451 | Knowles et al. | Jan 2014 | A1 |
| 20140025452 | Knowles et al. | Jan 2014 | A1 |
| 20140025453 | Knowles et al. | Jan 2014 | A1 |
| 20140025460 | Knowles et al. | Jan 2014 | A1 |
| 20140046675 | Harwood | Feb 2014 | A1 |
| 20140046744 | Hagey | Feb 2014 | A1 |
| 20140046748 | Nagarajan et al. | Feb 2014 | A1 |
| 20140108108 | Artman et al. | Apr 2014 | A1 |
| 20140164199 | Wilkes | Jun 2014 | A1 |
| 20150039393 | Jain | Feb 2015 | A1 |
| 20150170256 | Pettyjohn | Jun 2015 | A1 |
| 20150248702 | Chatterton | Sep 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 0186378 | Nov 2001 | WO |
| 2012024109 | Feb 2012 | WO |
| 2012106114 | Aug 2012 | WO |
| 2012170088 | Dec 2012 | WO |
| 2013015846 | Jan 2013 | WO |
| 2014106207 | Jul 2014 | WO |
| 2015102889 | Jul 2015 | WO |
| 2015134947 | Sep 2015 | WO |
| Entry |
|---|
| USPTO; Final Office Action dated Apr. 11, 2011 in U.S. Appl. No. 12/857,389. |
| USPTO; Final Office Action dated Apr. 5, 2011 in U.S. Appl. No. 12/857,424. |
| Todorova, Aleksandra, “The Best Rewards Programs,” www.smartmoney.com, Sep. 2005, pp. 1-2. |
| Todorova, Aleksandra, “Capital One Tests a New Type of Debit Card,” www.smartmoney.com, Jun. 2007, pp. 1-2. |
| Nickel, “Citi Thank You Redemptions: No Thanks,” www.fivecentnickel.com, Sep. 2005. |
| www.americanexpress.com/gift Feb. 25, 2005, 2 pages. |
| USPTO; Office Action dated Nov. 26, 2010 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Nov. 26, 2010 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Apr. 30, 2010 in U.S. Appl. No. 11/779,734. |
| USPTO; Advisory Action dated Jan. 6, 2011 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Oct. 15, 2010 in U.S. Appl. No. 11/779,734. |
| USPTO; Advisory Action dated Jul. 11, 2011 in U.S. Appl. No. 12/857,389. |
| USPTO; Advisory Action dated Jul. 11, 2011 in U.S. Appl. No. 12/857,424. |
| PCT; International Search Report and Written Opinion dated Nov. 27, 2011 in Application No. PCT/US2011/047012. |
| USPTO; Office Action dated Nov. 10, 2011 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Apr. 5, 2012 in U.S. Appl. No. 13/153,890. |
| PCT; International Search Report and Written Opinion dated May 8, 2012 in Application No. PCT/US2012/021648. |
| PCT; International Search Report and Written Opinion dated Jun. 19, 2012 in Application No. PCT/US2012/027810. |
| PCT; International Search Report and Written Opinion dated Jul. 6, 2012 in Application No. PCT/US2012/027664. |
| USPTO; Office Action dated Aug. 3, 2012 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Aug. 17, 2012 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Aug. 30, 2012 in U.S. Appl. No. 13/188,693. |
| USPTO; Office Action dated Aug. 30, 2012 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Sep. 6, 2012 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Sep. 14, 2012 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Sep. 17, 2012 in U.S. Appl. No. 13/021,237. |
| USPTO; Office Action dated Oct. 9, 2012 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Oct. 9, 2012 in U.S. Appl. No. 13/477,806. |
| USPTO; Office Action dated Oct. 12, 2012 in U.S. Appl. No. 13/439,768. |
| USPTO; Final Office Action dated Oct. 12, 2012 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Oct. 15, 2012 in U.S. Appl. No. 13/594,528. |
| USPTO; Office Action dated Oct. 18, 2012 in U.S. Appl. No. 13/593,204. |
| USPTO; Office Action dated Oct. 19, 2012 in U.S. Appl. No. 13/411,281. |
| Dan Oshinsky, “Jet Blue's $1 Million Twitter Hashtag,” Aug. 18, 2010, 4 pages, retrieved from: http://danoshinsky.com/2010/08/18/a-social-media-case-study-jetblue-vs-sun-country/. |
| USPTO; Office Action dated Nov. 15, 2012 in U.S. Appl. No. 13/443,100. |
| USPTO; Advisory Action dated Nov. 23, 2012 in U.S. Appl. No. 13/466,412. |
| International Preliminary Report on Patentability dated Dec. 7, 2012 in Application No. PCT/US2011/047012. |
| MG Seigler, “Want Everyone to See your Credit Card Transactions? Of Course you do. Meet Blippy.”, techcrunch.com, Dec. 11, 2009, 3 pages. |
| Tsotsis, Alexia, “The End of Blippy as We Know it.” techcrunch.com, May 19, 2011, 3 pages. |
| USPTO; Office Action dated Jan. 4, 2013 in U.S. Appl. No. 13/593,204. |
| USPTO; Office Action dated Jan. 7, 2013 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Jan. 7, 2013 in U.S. Appl. No. 13/466,445. |
| USPTO; Advisory Action dated Mar. 15, 2013 in U.S. Appl. No. 13/593,204. |
| USPTO; Advisory Action dated Mar. 18, 2013 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Mar. 19, 2013 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Mar. 19, 2013 in U.S. Appl. No. 13/468,931. |
| International Search Report and Written Opinion dated Mar. 22, 2013 in Application No. PCT/2013/028209. |
| USPTO; Advisory Action dated Mar. 28, 2013 in U.S. Appl. No. 13/411,281. |
| USPTO; Office Action dated Apr. 11, 2013 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Apr. 12, 2013 in U.S. Appl. No. 13/467,910. |
| USPTO; Office Action dated May 23, 2013 in U.S. Appl. No. 13/734,693. |
| International Preliminary Report on Patentability dated on May 23, 2013 in Application No. PCT/US2012/027810. |
| USPTO; Advisory Action dated Jun. 6, 2013 in U.S. Appl. No. 13/466,445. |
| International Preliminary Report on Patentability dated on Jun. 28, 2013 in Application No. PCT/US2012/027664. |
| International Preliminary Report on Patentability dated on May 7, 2013 in Application No. PCT/US2012/021648. |
| USPTO; Advisory Action dated May 9, 2013 in U.S. Appl. No. 13/477,806. |
| USPTO; Advisory Action dated May 22, 2013 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Mar. 1, 2013 in U.S. Appl. No. 13/439,768. |
| USPTO; Final Office Action dated Mar. 4, 2013 in U.S. Appl. No. 13/594,528. |
| USPTO; Final Office Action dated Mar. 6, 2013 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Jan. 10, 2013 in U.S. Appl. No. 13/468,931. |
| USPTO; Final Office Action dated Jan. 31, 2013 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jan. 31, 2013 in U.S. Appl. No. 13/467,910. |
| USPTO; Final Office Action dated Feb. 14, 2013 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Feb. 25, 2013 in U.S. Appl. No. 13/477,806. |
| USPTO; Office Action dated May 2, 2013 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Jul. 19, 2013 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Aug. 14, 2013 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Aug. 14, 2013 in U.S. Appl. No. 12/857,424. |
| USPTO; Final Office Action dated Aug. 28, 2013 in U.S. Appl. No. 13/443,100. |
| USPTO; Office Action dated Aug. 27, 2013 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Sep. 23, 2013 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Oct. 4, 2013 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Nov. 22, 2013 in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated Oct. 30, 2013 in U.S. Appl. No. 11/779,734. |
| USPTO; Restriction Requirement dated Oct. 30, 2013 in U.S. Appl. No. 13/889,288. |
| USPTO; Final Office Action dated Nov. 5, 2013 in U.S. Appl. No. 13/889,285. |
| USPTO; Advisory Action dated Nov. 5, 2013 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Nov. 26, 2013 in U.S. Appl. No. 13/734,693. |
| USPTO; Office Action dated Nov. 6, 2013 in U.S. Appl. No. 13/889,272. |
| USPTO; Notice of Allowance dated Dec. 17, 2013 in U.S. Appl. No. 13/594,528. |
| USPTO; Office Action dated Jan. 3, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Office Action dated Jan. 15, 2014 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jan. 29, 2014 in U.S. Appl. No. 13/889,307. |
| USPTO; Office Action dated Jan. 30, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Feb. 3, 2014 in U.S. Appl. No. 13/593,204. |
| International Preliminary Report on Patentability dated on Feb. 3, 2014 in Application No. PCT/US2013/028209. |
| USPTO; Advisory Action dated Feb. 5, 2014 in U.S. Appl. No. 13/734,693. |
| USPTO; Final Office Action dated Feb. 11, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Feb. 12, 2014 in U.S. Appl. No. 13/468,931. |
| Golson, “Major League Baseball Rolling out Thousands of iBeacons for Opening Day,” Jan. 30, 2014, pp. 2-3, retrieved from http://www.macrumors.com/2014/01/30/mlb-ibeacon-rollout/ on Feb. 12, 2014. |
| D Arthur, S Vassilvitskii , “k-means++: The advantages of careful seeding”, Proceedings of the eighteenth annual ACM-SIAM symposium on Discrete algorithms, pp. 1027-1035, 2007, dl.acm.org. |
| AK Jain, “Data clustering: 50 years beyond K-means”, Pattern Recognition Letters, 2010, pp. 1-33, Elsevier. |
| K-means++ Wikipedia Page, pp. 1-4, page last modified on Nov. 18, 2013, http://en.wikipedia.org/wiki/K-means++ retrieved from the web Nov. 21, 2013. |
| USPTO; Advisory Action dated Jan. 14, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Final Office Action dated May 5, 2014 in U.S. Appl. No. 13/411,281. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/021,237. |
| UUSPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Mar. 7, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/466,445. |
| Uspto; Office Action dated Mar. 11, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Mar. 13, 2014 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Apr. 25, 2014 in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated Apr. 28, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Advisory Action dated Apr. 30, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Oct. 17, 2014 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Jul. 30, 2014 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Jul. 30, 2014 in U.S. Appl. No. 13/411,281. |
| Examination Report dated Aug. 11, 2014 in New Zealand Application No. 623019. |
| USPTO; Final Office Action dated Aug. 13, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated Aug. 14, 2014 in U.S. Appl. No. 13/794,145. |
| USPTO; Office Action dated Aug. 14, 2014 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Aug. 15, 2014 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/021,237. |
| USPTO; Office Action dated Oct. 17, 2014 in U.S. Appl. No. 11/779,734. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Advisory Action dated Jul. 30, 2014 in U.S. Appl. No. 13/593,204. |
| USPTO; Office Action dated Oct. 20, 2014 in U.S. Appl. No. 13/941,306. |
| USPTO; Office Action dated Sep. 17, 2014 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Sep. 26, 2014 in U.S. Appl. No. 13/477,806. |
| USPTO; Office Action dated Oct. 3, 2014 in U.S. Appl. No. 12/857,424. |
| USPTO; Advisory Action dated Sep. 02, 2014 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Oct. 9, 2014 in U.S. Appl. No. 13/926,789. |
| USPTO; Advisory Action dated Jul. 31, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Advisory Action dated Aug. 7, 2014 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Oct. 8, 2014 in U.S. Appl. No. 13/734,693. |
| USPTO; Office Action dated Oct. 23, 2014 in U.S. Appl. No. 13/715,770. |
| USPTO; Advisory Action dated Oct. 24, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated Oct. 29, 2014 in U.S. Appl. No. 13/926,884. |
| USPTO; Office Action dated Oct. 29, 2014 in U.S. Appl. No. 13/926,895. |
| USPTO; Office Action dated Nov. 7, 2014 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Nov. 7, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Dec. 29, 2014 in U.S. Appl. No. 13/188,693. |
| USPTO; Office Action dated Jan. 9, 2015 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Jan. 16, 2015 in U.S. Appl. No. 13/889,299. |
| Written Opinion dated Aug. 5, 2015 in Singapore Application No. 11201400788P. |
| USPTO; Advisory Action dated Sep. 29, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Notice of Allowance dated Sep. 29, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Oct. 8, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Advisory Action dated Oct. 13, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Oct. 16, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Oct. 16, 2015 in U.S. Appl. No. 13/443,100. |
| USPTO; Advisory Action dated Oct. 22, 2015 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Oct. 26, 2015 in U.S. Appl. No. 13/476,910. |
| USPTO; Final Office Action dated Oct. 26, 2015 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Nov. 17, 2015 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Nov. 17, 2015 in U.S. Appl. No. 13/468,880. |
| Examination Report dated Mar. 24, 2015 in Australian Application No. 2012316453. |
| USPTO; Final Office Action dated Mar. 25, 2015 in U.S. Appl. No. 13/477,806. |
| USPTO; Final Office Action dated Mar. 25, 2015 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Mar. 27, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Apr. 3, 2015 in U.S. Appl. No. 13/926,884. |
| USPTO; Final Office Action dated Apr. 3, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Final Office Action dated Apr. 7, 2015 in U.S. Appl. No. 13/926,895. |
| USPTO; Advisory Action dated Apr. 8, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Office Action dated Apr. 8, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Apr. 8, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Final Office Action dated Apr. 13, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Apr. 17, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Final Office Action dated Apr. 17, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Advisory Action dated Apr. 23, 2015 in U.S. Appl. No. 13/794,334. |
| USPTO; Advisory Action dated Apr. 23, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Final Office Action dated Apr. 30, 2015 in U.S. Appl. No. 12/857,424. |
| Notice of Acceptance dated May 8, 2015 in New Zealand Application No. 623019. |
| USPTO; Advisory Action dated May 8, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated May 13, 2015 in U.S. Appl. No. 11/779,734. |
| USPTO; Office Action dated May 19, 2015 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated May 28, 2015 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Jun. 3, 2015 in U.S. Appl. No. 13/794,226. |
| USPTO; Advisory Action dated Jun. 3, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Jun. 10, 2015 in U.S. Appl. No. 13/477,806. |
| USPTO; Advisory Action dated Jun. 11, 2015 in U.S. Appl. No. 13/926,789. |
| Burke, “Hybrid Recommender Systems: Survey and Experiments,” User modeling and user-adapted interaction, 2002, Kluwer Academic Publishers, pp. 331-370. |
| Aimeur et al., “Alambic: a privacy-preserving recommender system for electronic commerce,” Feb. 27, 2008, Springer-Verlag, pp. 307-334. |
| Tang, “Approac to detection of community's consensus and interest,” Institute of Systems Science, 2008, Springer-Verlag, pp. 17-29. |
| Lee et al., “iJADE eMiner—A Web Based Mining Agent Based on Intelligent Java Agent Development Environment (iJADE) on Internet Shopping,” Advances in Knowledge Discovery and Data Mining, 2001, Springer-Verlag, pp. 28-40. |
| USPTO; Advisory Action dated Jun. 15, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Jun. 19, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Office Action dated Jun. 25, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Jun. 25, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Jun. 26, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Advisory Action dated Jun. 29, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Jul. 10, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Jul. 10, 2015 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Jul. 10, 2015 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jul. 17, 2015 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Jul. 20, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Advisory Action dated Jul. 21, 2015 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Jul. 23, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Aug. 4, 2015 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Aug. 5, 2015 in U.S. Appl. No. 13/926,789. |
| USPTO; Final Office Action dated Aug. 5, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Aug. 7, 2015 in U.S. Appl. No. 13/889,299. |
| USPTO; Office Action dated Aug. 11, 2015 in U.S. Appl. No. 13/926,895. |
| USPTO; Final Office Action dated Aug. 12, 2015 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Aug. 17, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Aug. 17, 2015 in U.S. Appl. No. 13/439,768. |
| USPTO; Office Action dated Aug. 19, 2015 in U.S. Appl. No. 13/926,884. |
| USPTO; Office Action dated Aug. 28, 2015 in U.S. Appl. No. 13/794,272. |
| USPTO; Final Office Action dated Jan. 28, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Final Office Action dated Jan. 30, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Final Office Action dated Feb. 11, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Final Office Action dated Feb. 13, 2015 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Feb. 26, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Office Action dated Feb. 27, 2015 in U.S. Appl. No. 13/443,100. |
| USPTO; Office Action dated Mar. 2, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Final Office Action dated Mar. 13, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Final Office Action dated Mar. 23, 2015 in U.S. Appl. No. 13/926,789. |
| Search Report and Written Opinion dated Feb. 16, 2015 in Singapore Application No. 11201400788P. |
| USPTO; Office Action dated May 7, 2014 in U.S. Appl. No. 13/477,806. |
| USPTO; Final Office Action dated May 13, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Final Office Action dated May 20, 2014 in U.S. Appl. No. 13/593,204. |
| USPTO; Notice of Allowance dated May 22, 2014 in U.S. Appl. No. 13/245,636. |
| USPTO; Final Office Action dated May 29, 2014 in U.S. Appl. No. 13/468,931. |
| USPTO; Advisory Action dated Jun. 2, 2014 in U.S. Appl. No. 13/889,272. |
| USPTO; Office Action dated Jun. 5, 2014 in U.S. Appl. No. 11/779,734. |
| USPTO; Office Action dated Jun. 11, 2014 in U.S. Appl. No. 13/188,693. |
| International Search Report and Written Opinion dated Dec. 7, 2012 in Application No. PCT/2012/056231. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Jun. 24, 2014 in U.S. Appl. No. 13/468,880. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Jun. 30, 2014 in U.S. Appl. No. 13/021,237. |
| USPTO; Notice of Allowance dated Jul. 2, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Advisory Action dated Jul. 2, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Office Action dated Jul. 3, 2014 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Jul. 8, 2014 in U.S. Appl. No. 13/889,299. |
| International Preliminary Report on Patentability dated on Aug. 22, 2013 in Application No. PCT/US2012/056231. |
| USPTO; Office Action dated Oct. 11, 2013 in U.S. Appl. No. 13/245,636. |
| USPTO; Office Action dated Feb. 5, 2014 in U.S. Appl. No. 13/245,636. |
| USPTO; Office Action dated Dec. 4, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Office Action dated Dec. 17, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Dec. 31, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Final Office Action dated Dec. 30, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Advisory Action dated Jan. 6, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Jan. 11, 2016 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Jan. 11, 2016 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Jan. 14, 2016 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Jan. 14, 2016 in U.S. Appl. No. 13/794,301. |
| USPTO; Office Action dated Jan. 15, 2016 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Jan. 15, 2016 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Jan. 20, 2016 in U.S. Appl. No. 13/889,307. |
| Pashtan, et al., “Personal Service Areas for Mobile Web Applications,” IEEE Internet Computing, 2004, ieeexplore.ieee.org, 7 pages. |
| Pandey, et al., “Exploiting User Profiles to Support Differentiated Services in Next-Generation Wireless Networks,” Network, IEEE, 2004, ieeexplore.ieee.org, 23 pages. |
| Liapis, et al., Implementing a Low-Cost, Personalized and Location Based Service for Delivering Advertisements to Mobile Users, Athens Information Technology, Oct. 2008, ieeexplore.ieee.org, 49 pages. |
| Park, et al., “Location-Based Recommendation System using Bayesian User's Preference Model in Mobile Devices,” Ubiquitous Intelligence and Computing, 2007, Springer-Verlag Berlin Heidelberg, 10 pages. |
| Office Action dated Oct. 26, 2015 in Canadian Application No. 2,863,576. |
| Notice of Acceptance dated Nov. 30, 2015 in Australian Application No. 2012316453. |
| Office Action dated Dec. 10, 2015 in Canadian Application No. 2,849,271. |
| Examination Report dated Feb. 26, 2016 in Australian Application No. 2015201925. |
| USPTO; Office Action dated Mar. 31, 2016 in U.S. Appl. No. 13/889,288. |
| USPTO; Final Office Action dated Apr. 14, 2016 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Apr. 15, 2016 in U.S. Appl. No. 13/188,693. |
| USPTO; Advisory Action dated Apr. 15, 2016 in U.S. Appl. No. 13/926,789. |
| USPTO; Notice of Allowance dated Apr. 18, 2016 in U.S. Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Apr. 21, 2016 in U.S. Appl. No. 13/794,272. |
| USPTO; Advisory Action dated Apr. 22, 2016 in U.S. Appl. No. 13/794,374. |
| Office Action dated Apr. 25, 2016 in Canadian Application No. 2,888,085. |
| USPTO; Advisory Action dated May 2, 2016 in U.S. Appl. No. 13/926,884. |
| USPTO; Advisory Action dated May 2, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated May 16, 2016 in U.S. Appl. No. 13/153,890. |
| Uspto; Office Action dated May 26, 2016 in U.S. Appl. No. 13/477,806. |
| USPTO; Office Action dated May 19, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Notice of Allowance dated May 25, 2016 in U.S. Appl. No. 13/439,768. |
| Pang, et al., “Opinion mining and sentiment analysis”, Foundations and trends in information retrieval, vol. 2, No. 1-2 (2008) 1-135. |
| Pavlovic, “Dynamics, robustness and fragility of trust”, Formal Aspects in Secruity and Trust, 2009—Springer. |
| Resnick, et al., “Recommender Systems”, Mar. 1997, Communications of the ACM, vol. 40,No. 3, pp. 56-58. |
| Ricci, et al.; “Recommendation and Personalization in eCommerce”, Proceedings of the AH'2002 Workshop on Recommendation and Personalization in eCommerce, Malaga, Spain, May 28, 2002, pp. 1-160. |
| Ghose, et al., “Opinion Mining using Econometrics: A case study on Reputation Systems”, Department of Information, Operations, and Management Sciences, Annual Meeting, 2007. |
| USPTO; Office Action dated Feb. 1, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Feb. 2, 2016 in U.S. Appl. No. 13/926,789. |
| USPTO; Final Office Action dated Feb. 2, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated Feb. 9, 2016 in U.S. Appl. No. 13/794,374. |
| USPTO; Final Office Action dated Feb. 9, 2016 in U.S. Appl. No. 13/794,272. |
| USPTO; Final Office Action dated Feb. 11, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Feb. 11, 2016 in U.S. Appl. No. 13/926,884. |
| USPTO; Final Office Action dated Feb. 12, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Office Action dated Feb. 12, 2016 in U.S. Appl. No. 13/593,204. |
| USPTO; Office Action dated Mar. 4, 2016 in U.S. Appl. No. 13/466,412. |
| Office Action dated Feb. 29, 2016 in Canadian Application No. 2,874,582. |
| USPTO; Office Action dated Feb. 29, 2016 in U.S. Appl. No. 13/686,608. |
| USPTO; Office Action dated Mar. 7, 2016 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Mar. 4, 2016 in U.S. Appl. No. 13/794,226. |
| Noyes, “Card-Linked Offers Update,” Transaction World Magazine, Jul. 2012, 2 pages. |
| USPTO; Office Action dated Feb. 19, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Advisory Action dated Mar. 18, 2016 in U.S. Appl. No. 13/439,768. |
| USPTO; Advisory Action dated Mar. 18, 2016 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Mar. 25, 2016 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Mar. 28, 2016 in U.S. Appl. No. 14/065,883. |
| White, “Deals as Debit Rewards? Bank of America Brings Back Debit Card Rewards With a Twist,” Jan. 25, 2012 2 pages, retrieved from http://moneyland.time.com/2012/01/25/deals-as-debit-rewards-bank-of-america-brings-back-Jebit-card-rewards-with-a-twist/. |
| Owen, et al. “Improving the Value and Performance of Online Offers,” A First Data White Paper, First Data Corporahon, 2012, 10 pages. |
| IP Australia; Examination Report dated Aug. 3, 2016 in Australian Application No. 2015201925. |
| USPTO; Advisory Action dated Aug. 17, 2016 in U.S. Appl. No. 12/857,389. |
| CIPO; Notice of Allowance dated Aug. 18, 2016 in Canadian Application No. 2,863,576. |
| USPTO; Advisory Action dated Aug. 18, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Notice of Allowance dated Aug. 24, 2016 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Aug. 24, 2016 in U.S. Appl. No. 13/686,608. |
| USPTO; Office Action dated Aug. 24, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Aug. 25, 2016 in U.S. Appl. No. 13/466,445. |
| USPTO; Advisory Action dated Aug. 25, 2016 in U.S. Appl. No. 13/794,145. |
| USPTO; Final Office Action dated Aug. 26, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Aug. 30, 2016 in U.S. Appl. No. 13/889,307. |
| USPTO; Office Action dated Sep. 2, 2016 in U.S. Appl. No. 13/467,503. |
| USPTO; Final Office Action dated Sep. 2, 2016 in U.S. Appl. No. 12/857,424. |
| USPTO; Final Office Action dated Sep. 7, 2016 in U.S. Appl. No. 13/153,890. |
| USPTO; Notice of Allowance dated Sep. 9, 2016 in U.S. Appl. No. 13/926,789. |
| USPTO; Advisory Action dated Sep. 21, 2016 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Sep. 14, 2016 in U.S. Appl. No. 13/477,806. |
| “What is a token in programming?” Quora, pp. 1-3, retrieved from https://www.quora.com/What-is-a-token-in-programming on May 31, 2016. |
| USPTO; Final Office Action dated Sep. 22, 2016 in U.S. Appl. No. 13/889,288. |
| USPTO; Advisory Action dated Sep. 22, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Final Office Action dated Sep. 23, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Sep. 29, 2016 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Sep. 29, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Final Office Action dated Sep. 30, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Office Action dated Oct. 7, 2016 in U.S. Appl. No. 13/715,770. |
| USPTO; Notice of Allowance dated Oct. 11, 2016 in U.S. Appl. No. 13/926,884. |
| USPTO; Office Action dated Oct. 11, 2016 in U.S. Appl. No. 13/794,145. |
| USPTO; Office Action dated Oct. 11, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Oct. 11, 2016 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Oct. 20, 2016 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Oct. 27, 2016 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Jun. 3, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Jun. 3, 2016 in U.S. Appl. No. 12/857,424. |
| USPTO; Notice of Allowance dated Jun. 3, 2016 in U.S. Appl. No. 13/593,204. |
| USPTO; Final Office Action dated Jun. 8, 2016 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Jun. 9, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Final Office Action dated Jun. 10, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Final Office Action dated Jun. 13, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Final Office Action dated Jun. 15, 2016 in U.S. Appl. No. 13/686,608. |
| USPTO; Office Action dated Jun. 17, 2016 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Jun. 17, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated Jun. 17, 2016 in U.S. Appl. No. 13/794,145. |
| USPTO; Advisory Action dated Jun. 24, 2016 in U.S. Appl. No. 131715,770. |
| USPTO; Final Office Action dated Jul. 1, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Final Office Action dated Jul. 28, 2016 in U.S. Appl. No. 13/889,272. |
| USPTO; Advisory Action dated Jul. 6, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Jul. 7, 2016 in U.S. Appl. No. 14/284,817. |
| USPTO; Notice of Allowance dated Jul. 13, 2016 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Aug. 12, 2016in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated Jan. 19, 2017 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Jan. 20, 2017 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Jan. 23, 2017 in U.S. Appl. No. 14/464,439. |
| USPTO; Advisory Action dated Jan. 25, 2017 in U.S. Appl. No. 14/284,817. |
| USPTO; Office Action dated Jan. 30, 2017 in U.S. Appl. No. 14/464,474. |
| USPTO; Notice of Allowance dated Feb. 2, 2017 in U.S. Appl. No. 12/857,389. |
| USPTO; Advisory Action dated Feb. 7, 2017 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Feb. 8, 2017 in U.S. Appl. No. 13/715,770. |
| USPTO; Final Office Action dated Feb. 9, 2017 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Feb. 14, 2017 in U.S. Appl. No. 13/466,412. |
| USPTO; Notice of Allowance dated Feb. 14, 2017 in U.S. Appl. No. 13/794,226. |
| USPTO; Notice of Allowance dated Feb. 15, 2017 in U.S. Appl. No. 13/794,145. |
| USPTO; Notice of Allowance dated Feb. 16, 2017 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Feb. 27, 2017 in U.S. Appl. No. 13/468,880. |
| USPTO; Final Office Action dated Feb. 27, 2017 in U.S. Appl. No. 13/926,895. |
| Examination Report dated Jan. 11, 2017 in Australian Application No. 2016201509. |
| Examination Report dated Jan. 23, 2017 in Australian Application No. 2015201925. |
| Examination Report dated Feb. 24, 2017 in Australian Application No. 2015201925. |
| Pocket-lint, Apple's iBeacons explained: What it is and why it matters, retrieved from Internet on Feb. 21, 2017, http://web.archive.org/web/20130925141212/http://www.pocket-lint.com/news/123730-apple-sibeacons-explained-what-it-is-and-why-it-matters> published on Sep. 25, 2013 as per Wayback Machine, 10 pages. |
| Supplementary Examination Report dated Oct. 17, 2016 in New Zealand Application No. 11201400788P. |
| Notice of Eligibility for Grant dated Nov. 1, 2016 in Singapore Application No. 11201400788P. |
| Examination Report dated Nov. 22, 2016 in Australian Application No. 2015201925. |
| USPTO; Advisory Action dated Oct. 31, 2016 in U.S. Appl. No. 13/889,288. |
| USPTO; Office Action dated Nov. 10, 2016 in U.S. Appl. No. 13/476,910. |
| USPTO; Final Office Action dated Nov. 1, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Notice of Allowance dated Nov. 2, 2016 in U.S. Appl. No. 13/477,806. |
| USPTO; Office Action dated Dec. 15, 2016 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Nov. 1, 2016 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Nov. 4, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Advisory Action dated Dec. 8, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Final Office Action dated Nov. 10, 2016 in U.S. Appl. No. 14/284,817. |
| USPTO; Advisory Action dated Nov. 15, 2016 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Nov. 3, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Notice of Allowance dated Nov. 17, 2016 in U.S. Appl. No. 12/857,424. |
| USPTO; Final Office Action dated Nov. 17, 2016 in U.S. Appl. No. 13/188,693. |
| USPTO; Notice of Allowance dated Nov. 18, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Dec. 2, 2016 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated Nov. 18, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Office Action dated Jan. 13, 2017 in U.S. Appl. No. 13/794,374. |
| USPTO; Office Action dated Nov. 28, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Advisory Action dated Dec. 14, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Dec. 15, 2016 in U.S. Appl. No. 13/468,880. |
| USPTO; Advisory Action dated Nov. 04, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Advisory Action dated Nov. 16, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Office Action dated Jan. 4, 2017 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Dec. 14, 2016 in U.S. Appl. No. 13/941,306. |
| Number | Date | Country | |
|---|---|---|---|
| 20140081776 A1 | Mar 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61754354 | Jan 2013 | US | |
| 61701683 | Sep 2012 | US | |
| 61701685 | Sep 2012 | US | |
| 61701686 | Sep 2012 | US | |
| 61701688 | Sep 2012 | US |
