SYSTEMS AND METHODS FOR FACILITATING LOYALTY AND REWARD FUNCTIONALITY IN MOBILE COMMERCE

Info

Publication number: 20140074569
Type: Application
Filed: Sep 11, 2013
Publication Date: Mar 13, 2014
Applicant: First Data Corporation (Greenwood Village, CO)
Inventors: Scott Christopher Francis (Atlanta, GA), J. Scott Sanchez (Atlanta, GA), Christopher T. Cox (Sandy Springs, GA)
Application Number: 14/024,199

Abstract

The disclosure relates to systems and methods for facilitating loyalty and reward functionality in mobile commerce. In one embodiment, a method for providing a loyalty/reward program can include receiving an indication that a consumer has entered a predefined merchant location; transmitting a notification to a mobile device associated with the consumer; providing one or more payment tools on a mobile device for the consumer to facilitate a purchase from a merchant associated with the predefined merchant location; generating a loyalty/reward credit for an account associated with the consumer; and receiving an instruction from the consumer to redeem loyalty/reward credit for goods and/or service from the merchant.

Description

Description

RELATED APPLICATIONS

This application claims priority to U.S. Ser. No. 61/699,728, titled “Systems and Methods for Implementing Mobile Commerce,” filed on Sep. 11, 2012, and to U.S. Ser. No. 61/799,676, titled “Systems and Methods for Implementing Mobile Commerce,” filed on Mar. 15, 2013, the entire contents of both are hereby incorporated by reference.

FIELD OF THE DISCLOSURE

The disclosure generally relates to mobile commerce, and more particularly, to systems and methods for facilitating loyalty and reward functionality in mobile commerce.

BACKGROUND

Commercial transactions to purchase certain goods and services are being implemented by consumers using mobile devices, such as smartphones. However, many commercial transactions are still cumbersome to implement since many conventional point-of-sale (POS) terminals and devices, payment processing systems, and smartphone interfaces are not configured for user-friendly transactions.

BRIEF DESCRIPTION OF THE DISCLOSURE

The disclosure relates to systems and methods for facilitating loyalty and reward functionality in mobile commerce.

In one embodiment, a method for providing an opt-in loyalty/reward program can be provided. The method can include receiving an indication that a consumer has entered a predefined merchant location; transmitting a notification to a mobile device associated with the consumer; providing one or more payment tools on a mobile device for the consumer to facilitate a purchase from a merchant associated with the predefined merchant location; generating a loyalty/reward credit for an account associated with the consumer; and receiving an instruction from the consumer to redeem loyalty/reward credit for goods and/or service from the merchant.

In another embodiment, a system for providing an opt-in loyalty/reward program can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can further include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive an indication that a consumer has entered a predefined merchant location; transmit a notification to a mobile device associated with the consumer; provide one or more payment tools on a mobile device for the consumer to facilitate a purchase from a merchant associated with the predefined merchant location; generate a loyalty/reward credit for an account associated with the consumer; and receive an instruction from the consumer to redeem loyalty/reward credit for goods and/or service from the merchant.

In another embodiment, a method for providing an opt-in loyalty/reward program can be provided. The method can include providing a network link for a merchant to access a loyalty/reward application program; receiving an indication that a merchant has opted in to an associated loyalty/rewards program; receiving one or more merchant parameters for a customized merchant loyalty/rewards program; and generating a downloadable app or application program for a consumer to access the customized merchant loyalty/rewards program.

In another embodiment, a system for providing an opt-in loyalty/reward program can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to provide a network link for a merchant to access a loyalty/reward application program; receive an indication that a merchant has opted in to an associated loyalty/rewards program; receive one or more merchant parameters for a customized merchant loyalty/rewards program; and generate a downloadable app or application program for a consumer to access the customized merchant loyalty/rewards program.

In yet another embodiment, a method for providing an opt-in loyalty/reward program can be provided. The method can include receiving a code from a consumer's mobile device located at a merchant location; identifying a merchant's loyalty/reward program; facilitating access to an app or application program associated with the merchant's loyalty/reward program; receiving consumer information via the app or application program; providing one or more payment tools on the consumer's mobile device for the consumer to facilitate a purchase from a merchant associated with the merchant location; and generating loyalty/reward credit for an account associated with the consumer; and receiving an instruction from a consumer to redeem loyalty/reward credit for goods and/or services from the merchant.

In yet another embodiment, a system for providing an opt-in loyalty/reward program can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive a code from a consumer's mobile device located at a merchant location; identify a merchant's loyalty/reward program; facilitate access to an app or application program associated with the merchant's loyalty/reward program; receive consumer information via the app or application program; provide one or more payment tools on the consumer's mobile device for the consumer to facilitate a purchase from a merchant associated with the merchant location; and generate loyalty/reward credit for an account associated with the consumer; and receiving an instruction from a consumer to redeem loyalty/reward credit for goods and/or services from the merchant.

In another embodiment, a method for providing an opt-in loyalty/reward program can be provided. The method can include receiving a merchant loyalty/rewards credit from one merchant loyalty/rewards program; receiving other merchant loyalty/rewards credit from at least one other merchant loyalty/rewards program; determining at least one offer or advertisement based at least in part on the one merchant loyalty/rewards program and the at least one other merchant loyalty/rewards program; outputting the at least one offer or advertisement to a mobile device associated with a consumer; generating or transmitting a notification to the consumer's mobile device upon receiving an indication of at least one of the following: the consumer's mobile device is in a predefined location, an earned reward, a reward threshold, an expiring reward or offer, or a third party product and/or service review; and categorizing, organizing, ranking and/or prioritizing two or more merchants and/or associated merchant loyalty/reward programs based at least in part on consumer use, preference, conduct and/or behavior.

In another embodiment, a system for providing an opt-in loyalty/reward program can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive a merchant loyalty/rewards credit from one merchant loyalty/rewards program; receive other merchant loyalty/rewards credit from at least one other merchant loyalty/rewards program; determine at least one offer or advertisement based at least in part on the one merchant loyalty/rewards program and the at least one other merchant loyalty/rewards program; output the at least one offer or advertisement to a mobile device associated with a consumer; generate or transmit a notification to the consumer's mobile device upon receiving an indication of at least one of the following: the consumer's mobile device is in a predefined location, an earned reward, a reward threshold, an expiring reward or offer, or a third party product and/or service review; and categorize, organize, rank and/or prioritize two or more merchants and/or associated merchant loyalty/reward programs based at least in part on consumer use, preference, conduct and/or behavior.

In yet another embodiment, a method for providing an opt-in loyalty/reward program can be provided. The method can include generating a card/loyalty proxy; linking a merchant and/or affiliate identifier to a payment device via the card/loyalty proxy; linking multiple merchant and/or affiliate identifiers to the payment device via the card/loyalty proxy; associating multiple merchant and/or affiliate identifiers with a universal loyalty credential; receiving an indication that a linked payment device or universal loyalty credential is being used at a point of sale (POS) device, for an online transaction, or via a mobile device transaction; determining a loyalty/reward activity based at least in part on the card/loyalty proxy; and transmitting the card/loyalty proxy or universal loyalty credential to an associated merchant facilitating a transaction.

In another embodiment, a system for providing an opt-in loyalty/reward program can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to generate a card/loyalty proxy; link a merchant and/or affiliate identifier to a payment device via the card/loyalty proxy; link multiple merchant and/or affiliate identifiers to the payment device via the card/loyalty proxy; associate multiple merchant and/or affiliate identifiers with a universal loyalty credential; receive an indication that a linked payment device or universal loyalty credential is being used at a point of sale (POS) device, for an online transaction, or via a mobile device transaction; determine a loyalty/reward activity based at least in part on the card/loyalty proxy; and transmit the card/loyalty proxy or universal loyalty credential to an associated merchant facilitating a transaction.

In yet another embodiment, a method for providing an opt-in loyalty/reward program can be provided. The method can include receiving an indication a consumer has performed a predefined activity; crediting a consumer's account in a loyalty/rewards program based at least in part on the predefined activity; outputting an indication of the credit to the consumer's mobile device; receiving an instruction from the consumer to redeem a loyalty/reward credit on behalf of a third party; determining a loyalty/reward activity based at least in part on the card/loyalty proxy; and transmitting the card/loyalty proxy to an associated merchant facilitating a transaction.

In yet another embodiment, a system for providing an opt-in loyalty/reward program can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can further include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive an indication a consumer has performed a predefined activity; credit a consumer's account in a loyalty/rewards program based at least in part on the predefined activity; output an indication of the credit to the consumer's mobile device; receive an instruction from the consumer to redeem a loyalty/reward credit on behalf of a third party; determine a loyalty/reward activity based at least in part on the card/loyalty proxy; and transmit the card/loyalty proxy to an associated merchant facilitating a transaction.

In another embodiment, a method for checking in to pay can be provided. The method can include receiving an indication that a consumer has arrived at or will arrive at predefined merchant location; transmitting a respective notification to a point of sale (POS) device associated with a merchant; based at least in part on the indication, determining consumer identity, merchant identity and/or merchant's loyalty/reward program; outputting information associated with one or more consumers at the predefined merchant location; receiving a name or unique code with payment information from at least one consumer; authenticating the name or unique code; facilitating payment processing associated with the consumer purchase of a good and/or service from merchant; receiving payment authorization request from consumer; and transmitting payment confirmation, offer and/or loyalty/reward credit confirmation to POS device and/or mobile device associated with consumer.

In another embodiment, a system for checking in to pay can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive an indication that a consumer has arrived at or will arrive at predefined merchant location; transmit a respective notification to a point of sale (POS) device associated with a merchant; based at least in part on the indication, determine consumer identity, merchant identity and/or merchant's loyalty/reward program; output information associated with one or more consumers at the predefined merchant location; receive a name or unique code with payment information from at least one consumer; authenticate the name or unique code; facilitate payment processing associated with the consumer purchase of a good and/or service from merchant; receive payment authorization request from consumer; and transmit payment confirmation, offer and/or loyalty/reward credit confirmation to POS device and/or mobile device associated with consumer.

In yet another embodiment, a method for providing an interruptive alert can be provided. The method can include receiving one or more consumer preferences for alert or notification to be sent to a point-of-sale device near consumer or to one more devices associated with a consumer; determining one or more user-defined thresholds, predefined actions, recent occurrences, or transaction interruptors based at least in part on the one or more consumer preferences; receiving an indication from the consumer to initiate a transaction notification based at least in part on the one or more user-defined thresholds, predefined actions, recent occurrences, or transaction interrupters; configuring at least one trigger when one or more of the user-defined thresholds, predefined actions, recent occurrences, or transaction interrupters are detected or received; transmitting an alert or notification to the point-of-sale device near consumer and/or to one or more devices associated with the consumer; providing a command to consumer to confirm payment and/or cancel purchase transaction; and based at least in part on receipt of the command from the consumer, clear command requests at the point-of-sale device and/or one or more devices associated with the consumer.

In yet another embodiment, a system for providing an interruptive alert can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive one or more consumer preferences for alert or notification to be sent to a point-of-sale device near consumer or to one more devices associated with a consumer; determine one or more user-defined thresholds, predefined actions, recent occurrences, or transaction interruptors based at least in part on the one or more consumer preferences; receive an indication from the consumer to initiate a transaction notification based at least in part on the one or more user-defined thresholds, predefined actions, recent occurrences, or transaction interrupters; configure at least one trigger when one or more of the user-defined thresholds, predefined actions, recent occurrences, or transaction interrupters are detected or received; transmit an alert or notification to the point-of-sale device near consumer and/or to one or more devices associated with the consumer; provide a command to consumer to confirm payment and/or cancel purchase transaction; and based at least in part on receipt of the command from the consumer, clear command requests at the point-of-sale device and/or one or more devices associated with the consumer.

In another embodiment, a method for sharing an offer from a mobile device associated with a consumer can be provided. The method can include receiving an offer at the mobile device; determining a plurality of names in a contacts module of the mobile device; generating a display of the plurality of names on a user interface of the mobile device; receiving a selection of at least one of the plurality of names at the mobile device; determining a contact reference for each of the selected names from the contacts module of the mobile device; and transmitting the offer to each of the selected names at the respective contact reference.

In another embodiment, a system for sharing an offer from a mobile device associated with a consumer can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive an offer at the mobile device; determine a plurality of names in a contacts module of the mobile device; generate a display of the plurality of names on a user interface of the mobile device; receive a selection of at least one of the plurality of names at the mobile device; determine a contact reference for each of the selected names from the contacts module of the mobile device; and direct communication of the offer to each of the selected names at the respective contact reference.

In yet another embodiment, a method for sharing an offer from a mobile device associated with a consumer can be provided. The method can include receiving an offer at the mobile device; receiving access information for at least one social networking website; accessing the at least one social networking website with the access information; determining a plurality of names from the social networking website, wherein each name is associated with a person affiliated with the consumer on the social networking website; generating a display of the plurality of names on a user interface of the mobile device; receiving a selection of at least one of the plurality of names at the mobile device; determining a contact reference for each of the selected names from the social networking website; and transmitting the offer to the person associated with each of the respective selected names at the respective contact reference.

In yet another embodiment, a system for sharing an offer from a mobile device associated with a consumer can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive an offer at the mobile device; receive access information for at least one social networking website; access the at least one social networking website with the access information; determine a plurality of names from the social networking website, wherein each name is associated with a person affiliated with the consumer on the social networking website; generate a display of the plurality of names on a user interface of the mobile device; receive a selection of at least one of the plurality of names at the mobile device; determine a contact reference for each of the selected names from the social networking website; and direct communication the offer to the person associated with each of the respective selected names at the respective contact reference.

In another embodiment, a method for sharing an offer from a mobile device associated with a consumer can be provided. The method can include receiving an offer at the mobile device; receiving access information for at least one social networking website; accessing the at least one social networking website with the access information; determining a plurality of names from the social networking website, wherein each name is associated with a person affiliated with the consumer on the social networking website; generating a display of the plurality of names on a user interface of the mobile device; receiving a selection of at least one of the plurality of names at the mobile device; accessing a page at the social networking website for each of the respective people associated with the selected names; and posting information associated with the offer on each of the accessed pages of the social networking website.

In another embodiment, a system for sharing an offer from a mobile device associated with a consumer can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive an offer at the mobile device; receive access information for at least one social networking website; access the at least one social networking website with the access information; determine a plurality of names from the social networking website, wherein each name is associated with a person affiliated with the consumer on the social networking website; generate a display of the plurality of names on a user interface of the mobile device; receive a selection of at least one of the plurality of names at the mobile device; access a page at the social networking website for each of the respective people associated with the selected names; and post information associated with the offer on each of the accessed pages of the social networking website.

In yet another embodiment, a method for providing an opt-in program to share a received offer can be provided. The method can include receiving a request from a consumer's mobile device to download an application program; identifying a share received offer program based at least in part on the request; facilitating access to an application program associated with the share received offer program; receiving consumer information via the application program associated with the share received offer program; receiving access information for at least one social networking website via the application program associated with the share received offer program; and

receiving a personal identification number for accessing the application program associated with the share receive offer program.

In yet another embodiment, a system for providing an opt-in program to share a received offer can be provided. The system can include at least one processor operable to execute computer-executable instructions. The system can also include at least one memory operable to store computer-executable instructions. The computer-executable instructions can be operable to receive a request from a consumer's mobile device to download an application program; identify a share received offer program based at least in part on the request; facilitate access to an application program associated with the share received offer program; receive consumer information via the application program associated with the share received offer program; receive access information for at least one social networking website via the application program associated with the share received offer program; and receive a personal identification number for accessing the application program associated with the share receive offer program

Some embodiments of the disclosure can have other aspects, elements, features, operations, acts, and steps in addition to or in place of what is described above. These potential additions and replacements are described throughout the rest of the specification.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanying drawings. The use of the same reference numerals indicates similar or identical components or elements; however, different reference numerals may be used as well to indicate components or elements which may be similar or identical. Various embodiments of the disclosure may utilize elements and/or components other than those illustrated in the drawings, and some elements and/or components may not be present in various embodiments. Depending on the context, singular terminology used to describe an element or a component may encompass a plural number of such elements or components and vice versa.

FIG. 1 illustrates an example system for facilitating loyalty and reward functionality in mobile commerce according to certain embodiments of the disclosure.

FIG. 2 illustrates an example mobile commerce program application or module according to certain embodiments of the disclosure.

FIGS. 3-13 illustrate example methods for facilitating loyalty and reward functionality in mobile commerce according to certain embodiments of the disclosure.

FIGS. 14-35 illustrate example user interfaces for implementing certain systems and methods for facilitating loyalty and reward functionality in mobile commerce according to certain embodiments of the disclosure.

DETAILED DESCRIPTION

Certain embodiments of the disclosure will now be described more fully hereinafter with accompanying drawings and corresponding description in FIGS. 1-35. This disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein.

Overview

The disclosure relates to systems and methods for facilitating loyalty and reward functionality in mobile commerce. In one implementation, a mobile commerce application program, also known as a mobile wallet or wallet app, can be downloaded or other otherwise implemented by a consumer and/or merchant via a mobile device or client device, such as a smartphone, cellphone, wearable computer, or tablet computer. The mobile commerce application program can integrate both payment and loyalty functionality for use by merchants and consumers to facilitate payment and/or loyalty/reward transactions for goods and/or services, administer loyalty/reward programs, and receive loyalty/reward credit for a variety of activities, including, for instance, visiting certain merchants during certain days and/or times as well as purchasing goods and/or services. For example, according to certain embodiments of the disclosure, a consumer can download a wallet app to his or her smartphone or other mobile device, input and store payment device information in the wallet app, and then use the wallet app to pay a merchant for a movie ticket by transmitting an indication from the smartphone or other mobile device to the merchant. Using the payment device information, loyalty/reward credit can be generated by the merchant and credited to the consumer via a loyalty/reward program account for visiting the movie theater during an off-peak date/time as well as purchasing the movie ticket. The wallet app can generate an output via the consumer's smartphone or mobile device to reflect the loyalty/reward credit to the consumer's associated loyalty/reward program account as well as an electronic receipt for the consumer's movie ticket purchase. In this manner, loyalty/reward programs can become easier to use for consumers since the mobile commerce application can electronically track credits and various activities by the consumer can earn the consumer additional loyalty/reward credits. Further, different types of consumer loyalty can be rewarded, such as based on visits, spending, performing any number of activities (e.g., sending a friend an email or text, joining a loyalty/reward program, trying something new or different, etc.), or for ad-hoc reasons (e.g., late merchant service).

In another implementation, one or more tools can be provided by a mobile commerce application program to merchants and consumers to build closer ties between them or otherwise connect them through increased and more focused communications. For example, according to certain embodiments of the disclosure, a restaurant merchant can access, via a point of sale (POS) device or client device, a customized mobile commerce application or wallet app that has been downloaded to a consumer's mobile device or client device. When the restaurant merchant wants to communicate with its customers about news, upcoming events, and new menu items, such as announcing a special wine and cheese event for frequent customers. The restaurant merchant can access one or more tools to send notifications or messages to certain selected consumers via the wallet app on consumer's mobile devices or client devices. The tools can facilitate access to demographic and consumer data (spending, visits, etc.); filter data based on the demographic data, consumer data, and demographic and/or consumer groups; manage communication preferences (email, texts, notifications, etc.); and apply consumer preferences to selected communications Consumers could be selected based on, for instance, the number of restaurant visits in the past 30 days. In this manner, the merchant can target certain groups of consumers with focused messages and marketing campaigns, and thereby increase or otherwise improve merchant-consumer contact.

In yet another implementation, a mobile commerce application program can provide customized merchant applications to different merchants. For example, a local restaurant merchant may want to customize a wallet app or mobile commerce application program for downloading to or otherwise accessing via a consumer's mobile device or client device. The merchant can access another mobile commerce application program and utilize one or more tools to, for example, upload a merchant business logo, select parameters for a loyalty/reward program, and select data fields for obtaining consumer information or asking consumer questions. In any instance, after the merchant has customized a wallet app, consumers can access or otherwise download the app to their respective mobile devices or client devices, and initiate communications with the merchant via the customized wallet app. In certain other embodiments, a multi-merchant app can be provided to consumers for download to or access by a mobile device or client device. In that instance, consumers can have the ability to select from a list of merchants that communicate via the multi-merchant app. In certain other embodiments, a mobile commerce application program can provide services to any number of merchants who may have their own respective apps, and the mobile commerce application program can provide a variety of payment, communication, advertising, and loyalty/reward services through, for example, one or more application plug-ins that can interface between the merchant apps and the mobile commerce application program. In this manner, a merchant can customize consumers′ payment and/or loyalty/rewards experiences through a wallet app or mobile commerce application program.

In the above implementations and other embodiments described herein, a mobile commerce application program, sometimes referred to as a wallet app, can be hosted or otherwise stored on a mobile device, client device, server device, or any other processor-based device. Multiple instances of mobile commerce application programs can operate within a network environment, such as described in FIG. 1, and each may have similar or different functionality, such as described in FIG. 2, according to various embodiments and implementations as described herein.

Certain Example Implementations and Embodiments

An example architecture or environment for a system 100 according various embodiments of the disclosure is shown in and described with respect to FIG. 1. A mobile commerce application program or module, such as 102, can be stored in memory 104 at a server device 106. In certain embodiments, a mobile commerce application program or module, such as 108, can be stored in memory 110 at a merchant system computer 112 or associated merchant device 114. In certain embodiments, a mobile commerce application program or module, such as 116(1), can be stored in memory 118(1) at a mobile device 120(1) associated with a consumer 122(1) or user. In any instance, one or more mobile commerce application programs or modules operating on respective computers, servers and/or mobile devices can implement some or all of the functionality described herein.

As shown in FIG. 1, the system 100 may include or otherwise support one or more merchant system computers 112 and/or associated merchant devices 114, one or more consumer or mobile devices 120(1)-120(N), one or more server transaction processing systems 106, and one or more issuer or financial institution systems 124. A wide variety of different types of consumer or mobile devices 120(1)-120(N) may be provided or otherwise supported, such as consumer computers and/or mobile communication devices. As desired, the system 100 may provide or otherwise support a wide variety of other entities associated with payment transactions, such as one or more server transaction processing systems 106. Any number of suitable networks and/or communication channels, such as the illustrated networks 126, may facilitate communication between various components of the system 100.

With reference to FIG. 1, any number of merchant system computers 112 and/or associated merchant devices 114 may be provided or otherwise supported. In certain embodiments, these merchant system computers 112 and/or associated merchant devices 114 may include one or more point-of-sale (POS) devices or terminals. As desired, each merchant system computer 112 and/or associated merchant device 114 may include any number of processor-driven devices, including but not limited to, a server computer, a mainframe computer, one or more networked computers, a desktop computer, a personal computer, a laptop computer, a mobile computer, a smartphone, a tablet computer, a wearable computer device, an application-specific circuit, or any other processor-based device.

A merchant system computer 112 and/or associated merchant device 114 may be any suitable device that facilitates purchase transactions, such as those in retail establishments, e-commerce and/or mobile transactions. In operation, the merchant system computer 112 and/or associated merchant device 114 may utilize one or more processors 128 to execute computer-readable instructions that facilitate the hosting of one or more mobile commerce application program services, the receipt of purchase transaction requests, and/or the processing of payment and/or loyalty/reward transactions. As a result of executing these computer-readable instructions, a special purpose computer or particular machine may be formed that facilitates the purchase and/or loyalty/reward transactions.

In addition to having one or more processors 128, the merchant system computer 112 and/or associated merchant device 114 may further include and/or be associated with one or more memory devices 110, input/output (“I/O”) interface(s) 130, network interface(s), and/or location services 132. The memory 110 may be any computer-readable medium, coupled to the processor(s) 128, such as random access memory (“RAM”), read-only memory (“ROM”), and/or removable storage devices. The memory 110 may store a wide variety of data files and/or various program modules, such as an operating system (“OS”), one or more host modules, and/or one or more transaction modules or transaction applications, such as mobile commerce application program 108. The data files may include any suitable data that facilitates the operation of the merchant system computer 112 and/or associated merchant device 114, and/or interaction of the merchant system computer 112 and/or associated merchant device 115 with one or more other components (e.g., one or more one or more consumer or mobile devices 120(1)-120(N), one or more server transaction processing systems 106, one or more merchant acquiring platforms, one or more issuer systems, one or more financial institution systems 124, etc.) of the system 100. For example, the data files may include information associated with one or more websites 134 (hosted by either a third party and/or merchant), webpages, inventory information associated with available products, acquiring platform information, service provider information, information associated with the generation of payment and/or loyalty/reward transactions and/or routing information for payment and/or loyalty/reward transactions.

The OS may be suitable module that facilitates the general operation of the merchant system computer, as well as the execution of other program modules. For example, the OS may be, but is not limited to, Microsoft Windows®, Apple OSX™ Unix, a mainframe computer operating system (e.g., IBM z/OS, MVS, OS/390, etc.), or a specially designed operating system. The host modules may include any number of suitable host modules that manage interactions and communications between the merchant system computer 112 and/or associated merchant device 114, and external devices, such as the consumer or mobile devices 120(1)-120(N). For example, the host modules may include one or more Web server modules that facilitate the hosting of merchant websites and/or third party websites, such as 134, webpages, and/or transaction processing webpages. As another example, the host modules may include one or more cellular modules and/or systems that facilitate cellular communication with one or more mobile devices 120(1)-120(N).

The transaction modules or applications, such as the mobile commerce application program 108, may include any number of suitable software modules and/or applications that facilitate the collection and/or processing of information association with a purchase transaction, such as one or more identifiers of desired products (e.g., UPC identifiers) and/or services, a desired payment account, a desired type of transaction (e.g., a card present transaction, a card not present transaction, etc.), consumer identification information, and/or an identifier of a consumer or mobile device 120(1)-120(N) (e.g., a mobile device identifier, etc.). Based at least in part upon the collected information, the transaction modules or applications may generate and/or communicate a wide variety of transaction-related requests, such as payment processing and/or authorization requests and/or requests for one or more value added services (“VAS”).

In one example embodiment, a transaction module, such as the mobile commerce application program 108, may receive a request for a purchase and/or loyalty/reward transaction (e.g., a request provided via a web page, etc.). As desired, the transaction module may identify available payment options that are presented to a consumer (e.g., credit account payment options, debit account payment options, stored value account payment options, card present e-commerce payment options, etc.), and a consumer selection of a payment option may be received. In the event that a card present transaction is requested, the transaction module may obtain a mobile device identifier, for example, via an established communications session with a consumer's mobile device or in response to requesting the mobile device identifier from the consumer. The transaction module may then invoke or request that a server transaction processing system 106 invoke one or more suitable applications on the mobile device, such as 120(1), (e.g., a wallet application, a mobile commerce application program, a transaction module, etc.) in order to receive validation information from the mobile device 120(1), such as an mPIN and/or a message (e.g., an encrypted message, etc.) derived from an mPIN and/or other information (e.g., a secure element identifier, an encryption key, etc.). The transaction module (or server transaction processing system) may then associate the validation information with a proposed transaction that is output for communication to an issuer system or financial institution system 124 associated with a selected payment account. For example, the transaction module may append and/or incorporate the validation information into a transaction authorization and/or settlement request. In this regard, the issuer system or financial institution system 124 may verify the validation information and determine whether a card present e-commerce transaction will be allowed.

As desired, prior to the output of a proposed transaction, the transaction module may invoke and/or request (e.g., request a server transaction processing system, etc.) the invocation of a wide variety of VAS associated with a transaction, such as the application of coupons, the award and/or redemption of loyalty rewards, etc. Additionally, in the event that the transaction is authorized, the transaction module may invoke and/or request the invocation of a wide variety of VAS following the transaction, such as receipt delivery services, product registration services, etc. Indeed, a wide variety of suitable operations may be performed by the transaction module.

Similarly, in some embodiments, a payment device, such as 135(1)-135(N), for example a payment card, credit card, debit card, stored value card, smart card, etc., may be associated with a respective consumer, such as 122(1)-122(N). The payment device, such as 135(1), can be used to request a purchase and/or loyalty/reward transaction when presented to a merchant system computer 112 and/or merchant computer device 114, either directly by the consumer 135(1) or via a consumer's mobile device, such as 120(1)-120(N). In these instances, an associated transaction module, such as the mobile commerce application program 108 associated with the merchant computer system 112 and/or merchant computer device 114, can receive payment device information, such as an account number and/or other payment device information, and communicate, via one or more networks 126, some or all of the payment device information to an issuer system or financial institution system 124 with the proposed transaction information for processing.

Example application programs or modules associated with the operations that may be performed by a transaction module or mobile commerce application program 108 and/or the merchant system computer 112 and/or associated merchant device 114 are described in greater detail below with reference to FIG. 2.

With continued reference to the merchant system computer 112 and/or associated merchant device 114, the one or more I/O interfaces 130 may facilitate communication between the merchant system computer 112 and/or associated merchant device 114 and one or more input/output devices; for example, one or more user interface devices, such as a display, a keypad, a mouse, a pointing device, a gesture detection device, an eye movement detection device, a control panel, a touch screen display, a remote control, a microphone, a speaker, a consumer device reader, etc., that facilitate user interaction with the merchant system computer 112 and/or associated merchant device 114. The one or more network interfaces may facilitate connection of the merchant system computer 112 and/or associated merchant device 114 to one or more suitable networks, such as 126, and/or communication links. In this regard, the merchant system computer 112 and/or associated merchant device 114 may receive and/or communicate information to other components of the system 100, such as the consumer or mobile devices, for example 120(1)-120(N), the server transaction processing systems 106, and/or the issuer or financial institution systems 124.

In certain embodiments, a merchant system computer 112 and/or associated merchant device 114 can be associated with a merchant location 136, such as a retail store or “bricks and mortar”-type establishment. The merchant location 136 may include a code 138, such as a QR code, bar code, or other machine readable code, wherein consumers can utilize a respective consumer or mobile device to scan or read the code to obtain information associated with a merchant, such as a merchant loyalty/rewards program.

Additionally, with continued reference to FIG. 1, any number of consumer or mobile devices 120(1)-120(N) may be provided or otherwise supported. Examples of suitable consumer or mobile devices can include, but are not limited to, personal computers and/or mobile communication devices (e.g., mobile phones, smart phones, wearable devices, etc.), etc. According to an aspect of the disclosure, a consumer or mobile device, such as 120(1) may be a suitable device that is capable of interaction with other components of the system 100 during the request and/or completion of an e-commerce transaction. For example, a personal computer or mobile device may be utilized to access one or more e-commerce websites, such as 134, including those hosted by the merchant system computer, such as 112, identify products and/or services to be purchased, request a purchase and/or loyalty/reward transaction, and/or interact with the merchant system computer 112, merchant system device 114, and/or other components of the system 100 (e.g., the server transaction processing system 106, etc.) during the completion of a payment and/or loyalty/reward transaction. In one example embodiment, a mobile device, such as 120(1), may be utilized to request a payment and/or loyalty/reward transaction and/or to provide validation information during the processing of the payment and/or loyalty/reward transaction. In another example embodiment, a personal computer may be utilized to request a payment and/or loyalty/reward transaction, and communication may be established with a mobile device, such as 120(1), in order to facilitate provision of validation information.

As desired, a consumer or mobile device, such as 120(1), may be any number of processor-driven devices, including but not limited to, a personal computer, a mobile computer, an application-specific circuit, a minicomputer, a microcontroller, and/or any other processor-based device. The components of an example mobile device, such as 120(1), will now be described in greater detail, and it will be appreciated that a personal computer may include similar components. With reference to the mobile device 120(1), the mobile device 120(1) may utilize one or more processors 140(1) to execute computer-readable instructions that facilitate the general operation of the mobile device 120(1) (e.g., call functionality, etc.) and/or communication with a merchant system computer 112, merchant system device 114, and/or other components of the system 100 (e.g., the server transaction processing system 106) for payment and/or loyalty/reward transaction purposes. As a result of executing these computer-readable instructions, a special purpose computer or particular machine may be formed that facilitates the completion of payment and/or loyalty/reward transactions.

In addition to having one or more processors, the mobile device, such as 120(1)-120(N), may further include and/or be associated with one or more memory devices 118(1)-118(N), input/output (“I/O”) interface(s) 142(1)-142(N), network interface(s), and/or location services 144(1)-144(N). The memory 118(1)-118(N) may be any computer-readable medium, coupled to the processor(s) 140(1)-140(N), such as random access memory (“RAM”), read-only memory (“ROM”), and/or removable storage devices. The memory 118(1)-118(N) may store a wide variety of data files and/or various program modules, such as an operating system (“OS”) and/or one or more transaction modules or applications, such as a mobile commerce application program 116(1)-116(N). In certain embodiments, a mobile device, such as 120(1), may include one or more secure elements configured to securely store and/or access information, such as payment applications, payment account information, validation information (e.g., a stored mPIN, etc.), encryption information, and/or other transaction-related information. The secure elements may be stored in the memory 118(1) and/or included as a separate component of the mobile device 120(1). For example, a secure element may be a separate chip that is configured to communicate with primary computing functionality for the mobile device. As desired, one or more of the transaction modules, such as the mobile commerce application program 116(1), may be stored on a secure element. The transaction modules may be invoked by other components of the mobile device 120(1) and/or by one or more other components of the system 100, such as the merchant system computer 112, merchant system device 114, and/or the server transaction processing system 106.

The data files may include any suitable data that facilitates the operation of the mobile device, such as 120(1), and/or interaction of the mobile device 120(1) with one or more other components (e.g., a merchant system computer 112, merchant system device 114, a server transaction processing system 106, etc.) of the system 100. For example, the data files may include information associated with accessing the secure elements, information associated with invoking transaction modules, and/or information associated with accessing and/or processing validation data (e.g., an mPIN, etc.). The OS may be a suitable module that facilitates the general operation of the mobile device, such as 120(1), as well as the execution of other program modules. For example, the OS may be, but is not limited to, a suitable mobile OS or a specially designed operating system. As desired, the mobile device 120(1) may also include one or more suitable browser applications that facilitate the access of one or more webpages hosted by the merchant system computer 112, and/or third party or merchant websites, such as 134.

The transaction modules may include one or more suitable software modules and/or applications configured to facilitate purchase transactions, such as payment and/or loyalty/reward transactions, on behalf of the mobile device, such as 120(1). In certain embodiments, a transaction module or mobile commerce application program, such as 116(1), may also facilitate communication with a server transaction processing system, such as 106, or a trusted service manager. A wide variety of suitable techniques may be utilized to install a transaction module on the mobile device, such as 120(1). For example, a transaction module may be provisioned to the mobile device 120(1) by a server transaction processing system 106 and/or by an issuer or financial institution system 124. Additionally, during the installation and/or registration of the transaction module, a wide variety of validation information may be generated and/or identified. For example, a consumer, such as 122(1) may be prompted to enter an mPIN, such as a multi-character and/or multi-numeral code, to an associated mobile device, such as 120(1). As desired, the mPIN may be stored on a secure element. Additionally, the PIN and/or a wide variety of information derived from the mPIN (e.g., an encrypted mPIN, etc.) may be provided to one or more issuer or financial institution systems, such as 124, or an issuer system associated with an issuer of a payment account (e.g., a credit account, a debit account, a stored value account, etc.) that is associated with the transaction module.

According to an aspect of the disclosure, following registration and/or activation of the transaction module, the transaction module may be invoked during a payment and/or loyalty/reward transaction. For example, the transaction module may be invoked by a merchant system computer 112, merchant system device 114, or by a server transaction processing system 106 at the request of the merchant system computer 112 and/or merchant system device 114. In certain embodiments, the transaction module may be invoked following a consumer request to conduct a payment and/or loyalty/reward transaction and the identification of the mobile device, such as 120(1), by the merchant system computer 112, merchant system device 114, or server transaction processing system 106. Following the invocation of the transaction module, a request for validation data and/or payment and/or loyalty/reward account data may be received. As desired, the transaction module may prompt the consumer for entry of an mPIN, and an mPIN value entered by the consumer, such as 122(1), (e.g., by a keypad, touchscreen, etc.) may be identified. A stored mPIN value may then be accessed from the secure element and compared to the entered mPIN value. In this regard, the entered mPIN value may be authenticated. If the entered mPIN value is not authenticated, then the transaction module may reject a proposed transaction and direct the output of a suitable error message.

If, however, the entered mPIN value is authenticated, then the transaction module may provide payment account data and associated validation data to the merchant system computer 112, merchant system device 114, or server transaction processing system 106. A wide variety of different types of validation data may be provided as desired in various embodiments, including but not limited to, an mPIN entered by the consumer 122(1), an indication that the entered mPIN was authenticated by the mobile device 120(1) and/or the secure element, an encrypted version of the entered mPIN, and/or an encrypted version of the stored mPIN. In one example embodiment, an entered mPIN may be authenticated, encrypted, and provided to the merchant system computer (or a server transaction processing system). In this regard, the encrypted mPIN may be provided to the issuer or financial institution system, such as 124, for authentication and/or risk analysis purposes.

Examples of the operations of the transaction module and/or the mobile device are described in greater detail below with reference to the other figures.

The one or more I/O interfaces, such as 142(1)-142(N), may facilitate communication between the mobile device, such as 120(1) and one or more input/output devices; for example, one or more user interface devices, such as a display, a keypad, a touch screen display, a microphone, a speaker, etc., that facilitate user interaction with the mobile device 120(1). Further, the one or more network interfaces may facilitate connection of the mobile device, such as 120(1), to one or more suitable networks, for example, the network(s) 126 illustrated in FIG. 1. In this regard, the mobile device, such as 120(1), may receive and/or communicate information to other components of the system 100.

With continued reference to FIG. 1, as desired in various embodiments, any number of server transaction processing systems, such as 106, may be provided or otherwise supported. A server transaction processing system 106 may facilitate the backend processing of a purchase transaction, such as a payment and/or loyalty/reward transaction. In certain embodiments, an issuer system may include similar components as those discussed above for the merchant system computer 112 and/or merchant system device 114. For example, server transaction processing system 106 may include any number of processors 146, memories, I/O interfaces 148, and/or network interfaces. In certain embodiments, a server transaction processing system 106 can include one or more transaction modules, such as a mobile commerce application program 102 and/or a social network integration program application 150. In any instance, the transaction modules can facilitate communications and/or interactions with any number of consumer or mobile devices such as 120(1)-120(N), merchant computer systems such as 112, merchant computer devices 114, data stores 151, third party websites such as 134, and financial institution systems such as 124. In certain embodiments, a service transaction processing system, such as 106, can host a social network integration program application, such as 150, configured to communicate via any number of social network services and/or websites to obtain information from the services and/or websites, for example, product and/or service data 152 on a third party or merchant website, such as 134.

Furthermore, as desired, a server transaction processing system, such as 106, may provide a wide variety of transaction module provisioning services. Additionally, a server transaction processing system, such as 106, may provide a wide variety of transaction-related and/or value added services (“VAS”) in association with transactions, such as coupon redemption services, loyalty/reward services, location-based services, electronic receipt services, product registration services, warranty services, coupon issuance services, and/or the routing of a proposed transaction to an issuer for approval and/or settlement purposes. In certain embodiments, a server transaction processing system, such as 106, may include similar components as those discussed above for the merchant system computer, such as 112, and/or merchant system device, such as 114. For example, a server transaction processing system, such as 106, may include any number of processors, memories, I/O interfaces, and/or network interfaces.

With continued reference to FIG. 1, as desired in various embodiments, any number of issuer or financial institution systems, such as 124, may be provided or otherwise supported. An issuer or financial institution system, such as 124, may facilitate the backend processing of a payment and/or loyalty/reward transaction, such as a payment for an e-commerce transaction. For example, an issuer or financial institution system, such as 124, may host a payment processing application program, such as 154, or module to facilitate the approval, authentication, and/or settlement of a payment transaction. In certain embodiments, a payment transaction may be routed to an issuer or financial institution system, such as 124, via a suitable transaction network (e.g., a debit network, a credit network, etc.), and the issuer or financial institution system, such as 124, may evaluate the payment transaction via the payment processing application program, such as 154, or module. An approval or rejection of the payment transaction may then be output for communication to a merchant system computer, such as 112, and/or merchant system device 114. The issuer or financial institution system, such as 124, may then facilitate the settlement of the payment transaction. In certain embodiments, an issuer or financial institution system, such as 124, may include similar components as those discussed above for the merchant system computer 112 and/or merchant system device 114. For example, an issuer or financial institution system, such as 124, may include any number of processors 156, memories 158, I/O interfaces 160, and/or network interfaces.

In certain embodiments of the disclosure, an issuer or financial institution system, such as 124, may receive validation information in association with a purchase and/or loyalty/reward transaction.

A wide variety of suitable networks, individually and/or collectively shown as 126 in FIG. 1, may be utilized in association with embodiments of the disclosure. Certain networks may facilitate use of a wide variety of e-commerce-related communication. For example, one or more telecommunication networks, cellular networks, wide area networks (e.g., the Internet), and/or other networks may be provided or otherwise supported. Other networks may facilitate communication of transaction-related communications. For example, one or more transaction networks, such as branded networks (e.g., a VISA network, etc.), debit and/or PIN networks, and/or a wide variety of other suitable transaction networks may facilitate communication of transaction-related communications, such as e-commerce transactions. Due to network connectivity, various methodologies as described herein may be practiced in the context of distributed computing environments. It will also be appreciated that the various networks may include a plurality of networks, each with devices such as gateways and routers for providing connectivity between or among networks. Additionally, instead of, or in addition to, a network, dedicated communication links may be used to connect various devices in accordance with an example embodiment.

The system 100 shown in and described with respect to FIG. 1 is provided by way of example only. Numerous other operating environments, system architectures, and device configurations are possible. Other system embodiments can include fewer or greater numbers of components and may incorporate some or all of the functionality described with respect to the system components shown in FIG. 1.

Accordingly, embodiments of the disclosure should not be construed as being limited to any particular operating environment, system architecture, or device configuration.

FIG. 2 shows an example mobile commerce application program 200, similar to the mobile commerce application programs 102, 108, and 116(1)-116(N) in FIG. 1, that can operate with respect to the system 100 shown in FIG. 1. The mobile commerce application program 200 shown in FIG. 2 can include, for example, a loyalty/rewards module 202, a check-in-to-pay module 204, an interruptive alert module 206, a share redeemed offer module 208, a notification or messaging module 210, a restaurant mobile payment module 212, a check-in-to-pay at QSR module 214, a split the bill module 216, a lifecycle shopping module 218, a linking transaction module 220, a mobile device login module 222, a bill payment module 224, a multi-consumer remote payment module 226, an instant issuance module 228, a check-in to pump gas module 230, a buy car wash module 232, a drive consumer inside module 234, a tokenization module 236, and a code generation module 238. Some or all of the modules 202-238 are described herein with respect to certain mobile commerce functionality, associated processes, and features. FIGS. 3-13 illustrate certain processes associated with some or all of the modules comprising the example mobile commerce application program 200 in FIG. 2.

While the various modules 202-238 are shown by way of example, fewer or greater numbers of modules can be present in various embodiments of a mobile commerce application program. Furthermore, various functionality described with respect to one module may be performed by multiple modules in other embodiments of the disclosure.

Opt-in Mobile Loyalty/Reward Program

In some instances, consumers desire reward credit they feel they deserve at the stores they shop at most frequently. Certain embodiments of the disclosure can provide systems and processes for enabling an opt-in mobile loyalty/reward program, such as a digital “punch card”-type program offered by each merchant the consumer visits. The program can be implemented, for example, by way of a mobile commerce application program, such as 116(1) in FIG. 1, or app accessible by or otherwise executing on a consumer's mobile phone or device, such as 120(1), or other client device. The application program, such as 116(1), or app can launch, for instance, by manually or automatically initiating or executing the application program 116(1) or app, scanning a QR code or bar code, such as 138, exposing a NFC (near field communication) device, or otherwise transmitting a number and/or code associated with a payment device and/or consumer at a merchant location, such as 136. In some instances, the application program, such as 116(1), or app can trigger an alert or notification on the consumer's mobile phone or device 120(1), or other client device, when the consumer 122(1) walks into or otherwise visits a merchant location 136, which could be triggered via a location-based service (LBS) or location service 144(1) associated with the consumer's mobile phone or device 120(1) and that initiates the program. In certain instances, the location service 132 can provide geolocation data to a host or server device, such as 106, via the application program 116(1) or app. The host or server device 106 may use some or all of the geolocation data to determine when the consumer's mobile phone or device 120(1) is at or adjacent a merchant location 136, which may be associated with a merchant computer system 112, merchant computer device 114, and/or location service 132. In certain instances, the application program, such as 116(1), or app can have a set of embedded payment tools so each consumer 122(1)-122(N) can pay for merchant goods and/or services, and earn rewards at each merchant. The payment tools can communicate, via the application program 116(1) or app, with the host or server device 106 and/or a financial institution system 124 to facilitate a payment transaction on behalf of the consumer 122(1) for payment to the merchant. The host or server device 106 can interact with an associated mobile commerce application program, such as 102, and/or a payment processing application program, such as 154, which can facilitate the payment transaction as well as administer one or more rewards to benefit the consumer. In one embodiment, consumers 122(1)-122(N) can obtain loyalty or reward credit from merchants and/or retail establishments the consumers shop at, particularly, those shopped at or visited most frequently. For example, for certain visits and/or payment transactions, the mobile commerce application program 102 and/or a payment processing application program 154 can utilize a set of rules and/or a set of computer-executable instructions to allocate loyalty or reward credit to respective consumers 122(1)-122(N) and track the loyalty or reward credit in a consumer account stored in memory at the server 106 or financial institution.

As shown in FIG. 1, by way of a client device, such as a merchant computer device 114, a merchant can link via a network, such as 126, to a hosted website, such as 134, or otherwise communicate with a loyalty/rewards application program (or module) or mobile commerce application program, such as 102, on a host or server device, such as 106, and configure a customized loyalty/reward program using, for example, a series of templates or predefined user interfaces. For instance, a hosted website 134, loyalty/rewards application program or mobile commerce application program 102 on a server device 106 can implement a set of computer-executable instructions to enable an opt-in mobile loyalty/reward program. When prompted, the merchant can access the loyalty/rewards application program or mobile commerce application program 102 to upload a business logo and select one or more parameters for a loyalty/rewards program, such as a number of points to reward per consumer visit or purchase, and a minimum number of reward points needed to redeem for a reward. After the merchant inputs the business logo and parameters for a loyalty/rewards program, the hosted website 134, loyalty/rewards application program loyalty/rewards application program or mobile commerce application program 102 can execute a set of computer-executable instructions to implement the merchant's loyalty/reward program, such as offering the program as a consumer downloadable application program, such as 116(1), or app in a mobile application store or website, such as 134. In some embodiments, the consumer downloadable application program, such as 116(1), or app may be branded with the merchant's logo and/or name. In some embodiments, the consumer downloadable application program, such as 116(1), or app may be the same application program or app for some or all merchants within a single classification or geographical location. In the manner described above, various merchants, regardless of size, can adopt and implement a loyalty/rewards program.

In one embodiment, as shown by FIG. 1, by way of a mobile device, for example 120(1), or other client device, such as a laptop computer or tablet, a consumer, such as 122(1), can download the merchant-branded consumer downloadable application program, such as 116(1), or app to the mobile device 120(1) or other client device. When prompted by the application program 116(1) or app, the consumer 122(1) can create an account and input certain identification information to the application program 116(1) or app, such as a name, mobile telephone number, email or messaging address, or social media application account name. In some embodiments, the consumer 122(1) can input a payment method, such as adding a bank account number, payment device number, security code, etc., and, in some instances, the consumer can charge, load, or otherwise authorize the account with a pre-paid value for use in purchasing the merchant's goods and/or services. In some embodiments, the consumer 122(1) can create a personal identification number (PIN) or other code for use in accessing the account. In the manner described above, since consumers 122(1)-122(N) can store certain personal and financial information via the application program, such as 116(1), or app, consumers 122(1)-122(N) can readily register for multiple merchants′ respective loyalty/reward programs, and in some instances, registration can be accomplished with a single click or authorization from the consumer 122(1).

In some embodiments, a consumer, such as 122(1), can update or otherwise input his or her personal and/or financial information by swiping or otherwise reading a payment device, such as a debit card, credit card, smartcard, or stored value card, using a card reader device or other payment device reader in communication with the application program, such as 116(1) or app. Some or all of the consumer's personal and/or financial information can be stored by the application program 116(1) or app for subsequent processing and/or retrieval. In some instances, after obtaining some or all of the consumer's personal and/or financial information, the application program 116(1) or app may prompt the consumer 122(1) to input additional information, edit previously obtained information, or confirm previously obtained information.

In one embodiment, a consumer can scan a QR code or otherwise input an identifying code or name associated with the merchant's loyalty/reward program to a mobile application store or website. For example, a consumer, such as 122(1), may use an associated mobile device 120(1) to scan QR code, such as code 138, posted or otherwise provided at a merchant location 136. The consumer's mobile device 120(1) or other client device can communicate, with the server 106 via a network 126, some or all information associated with the QR code or other code or name from the consumer.

Using the information, the server 106 can compare some or all of the information with previously stored information associated with one or more predefined to loyalty/reward programs to identify the merchant's loyalty/reward program, and download the consumer downloadable application program or app, such as 116(1), to the consumer's mobile device 120(1) or other client device.

After the consumer account has been configured, and the hosted website 134 or loyalty/rewards application program, such as 116(1), has stored information associated with the consumer account, the consumer 122(1) can utilize the account via a user interface provided by the consumer downloadable application program, such as 116(1), or app as a digital “punch card” in the merchant's loyalty/rewards program. The program 116(1) or app can provide the consumer 122(1) with any number of tools to facilitate purchases, such as a QR code scanner, a payment button, a keypad, a voice input payment command, etc. In some embodiments, the consumer 122(1) can verify a payment command or instruction by entering his or her PIN or other code. In any instance, after a successful transaction, the consumer 122(1) can be notified via the program 116(1) or app that the payment has been completed and a certain number of rewards have been earned.

In certain embodiments, activity based rewards can be provided to consumers for certain predefined conduct and/or behavior. For example, a star can be rewarded to a consumer 122(1) for downloading the consumer downloadable application program, such as 116(1) or app, to his or her mobile device 120(1) or client device. In another example, a star can be rewarded to a consumer 122(1) for sharing the program 116(1) or app with a friend via a social media program, by referral, or providing a validated email address. In certain embodiments, a star or other reward credit can be transferred or otherwise given by one consumer 122(1) to another consumer, such as 122(N). In any instance, each star or other icon can be correlated to a predefined number of rewards associated with each consumer 122(1)-122(N). Ultimately, the allocation and number of rewards can be managed by a loyalty/rewards application program, such as one accessible via a hosted website 134 or a loyalty/rewards application program or mobile commerce application program 102 on a server device 106.

In certain embodiments, a multi-merchant experience can be implemented. In one embodiment, certain merchant loyalty/rewards programs can be brought together and presented to a consumer with respective offers and/or advertisements for each merchant and/or merchant program. For example, a mobile commerce application program, such as 102, hosted by a server device, such as 106, may manage respective loyalty/reward programs associated with respective and/or multiple merchants. Each merchant may cooperate with other merchants, or an entity associated with hosting and/or managing the mobile commerce application program 102 may organize and/or decide to generate and provide cross-marketing or cross-merchant offers to consumers. For instance, one merchant associated with selling food can, via the mobile commerce application program 102, identify another merchant associated with selling wine, and together, both merchants can cross-market their goods and services to consumer by generating and providing consumers with one or more cross-merchant offers, such as buy a certain amount from one merchant, and receive a discount from another merchant. Mapping and location-based service functionality can be utilized by the mobile commerce application program 102 to notify a consumer, such as 122(1), about nearby merchants in the area the consumer is presently in. As the consumer 122(1) moves from one merchant location, such as 136, to another merchant location, the location services, such as 144(1) on the consumer's mobile device 120(1) may communicate geolocation data directly to the mobile commerce application program 102 and/or via the consumer's mobile commerce application program 116(1) executing on the consumer's mobile device 120(1). The consumer's mobile commerce application program 116(1) can indicate nearby merchant locations that may offer cross-marketing and/or cross-merchant offers by displaying nearby merchant locations and/or offers on an associated display of the consumer's mobile device 120(1). Further, notifications can be generated and transmitted by the mobile commerce application program 102 and/or via the consumer's mobile commerce application program 116(1) to the consumer 122(1) about rewards and/or reward thresholds that have been earned or reached, or that will be earned or reached. In some instances, notifications can be provided by the mobile commerce application program 102 and/or via the consumer's mobile commerce application program 116(1) about rewards and/or offers that may expire soon or on a certain date and/or time.

In certain embodiments, a user interface can be provided to consumers to categorize and/or organize merchants and associated merchant loyalty/rewards programs by ranking or prioritizing the merchants and/or merchant programs according to each consumer's use, preference, or conduct and/or behavior. For example, a mobile commerce application program, such as 102, and/or a consumer's mobile commerce application program, such as 116(1), can generate and display via a consumer's mobile device, such as 120(1), a user interface to permit a consumer 122(1) to view one or merchants and their respective and/or multiple loyalty/rewards programs. User selectable interface options can permit the consumer 122(1) to categorize, organize, rank, and/or prioritize the merchants and/or loyalty/rewards programs by any number of options, such as by consumer usage, consumer preference, consumer conduct, and/or consumer behavior. Usage can include, but is not limited to, the number of times the consumer has visited a merchant or used a merchant loyalty/reward program. Preference can include, but is not limited to, particular selection by a consumer, or ranking by one or more consumers, such as by crowdsourcing or voting for a favorite merchant and/or loyalty/reward program.

In some embodiments, third party product and/or service reviews can be utilized, such as from a review service or website, to identify frequently used merchants, to identify most valuable merchants, or to identify new merchants a particular consumer may like or want to know about. For example, a mobile commerce application program, such as 102, and/or a consumer's mobile commerce application program, such as 116(1), can receive or otherwise access product and/or service data, such as 152, that may be stored on a website, such as 134, or a data storage device, such as 151. In any instance, the product and/or service data 152 can be used to identify one or more merchants based at least in part on consumer and/or third party rankings, ratings, and/or likes for particular merchants. In certain instances, consumer and/or third party reviews and/or comments may be analyzed to determine or identify one or more merchants based on keywords, frequently used terms, and/or frequently reviewed or commented products and/or services. Based at least in part on the product and/or service data, the mobile commerce application program, such as 102, and/or consumer's mobile commerce application program, such as 116(1), can identify or otherwise generate one or more frequently used merchants, frequently commented on or most valuable merchants to certain consumers, and/or new merchants that may appeal to or otherwise interest certain consumers. In some instances, notifications can be provided about rewards and/or offers that may expire soon or on a certain date and/or time. For example, a mobile commerce application program, such as 102, and/or a consumer's mobile commerce application program, such as 116(1), can generate and transmit notifications, such as messages, texts, voice mails, and/or app notifications, via a consumer's mobile device, such as 120(1), to inform consumers, such as 122(1) about merchant rewards and/or offers with predefined expiration dates, and to further inform the consumers how many days and/or the time remaining to redeem certain merchant rewards and/or offers.

In certain embodiments, a card-linked loyalty/rewards and/or a loyalty/rewards proxy can be provided to enable a consumer to link a merchant or affiliate loyalty/rewards identifier to a payment device, such as a payment card. For example, a payment card or payment device, such as 135(1), associated with a consumer, such as 122(1), can be linked to a particular consumer, such as 122(1). The link can be generated and stored by a mobile commerce application program, such as 102 and/or payment processing application program, such as 154, when the payment device 135(1) is provided to or otherwise used by the consumer 122(1). In one embodiment, a unique number or code can be assigned to the link, consumer 122(1), and/or payment device 135(1). In another embodiment, consumer information and/or payment device information can be assigned to the link. In some instances, the link can be requested by the consumer 122(1), and in other instances, the link may be generated without a request from the consumer 122(1). In any instance, when a linked payment card, such as 135(1) is used at a merchant point-of sale (POS) device, such as a merchant computer device 114, a linked loyalty/rewards identifier, such as a unique number or code, can be retrieved from the mobile commerce application program 102 and/or payment processing application program 154, and used to drive appropriate loyalty/rewards activity (points accrual, discount, etc.). In this manner, the need for a loyalty/rewards identifier to be entered (manually or otherwise) as a separate step in the payment transaction (e.g. eliminates separate swipe of a loyalty/rewards card, manual entry of loyalty/rewards card number, etc.) can be eliminated. This can ensure that a consumer never forgets to use merchant or affiliate loyalty/rewards program and that appropriate loyalty/rewards benefits are accrued with every transaction. This can also leverage a merchant's existing loyalty/rewards program by more efficiently delivering loyalty/reward identifier as part of payment transaction at the POS. Once retrieved, a loyalty/reward identifier can be delivered to merchant's existing loyalty/reward program via the POS or can be delivered to a third-party/affiliate loyalty/reward program managed by the mobile commerce application program, such as 102 and/or payment processing application program, such as 154, “in the cloud.” If appropriate, multiple merchant or affiliate loyalty/reward programs can be accessed via the same payment transaction (e.g. by linking multiple loyalty/reward program identifiers to the same payment card).

In one embodiment, an enrollment function (e.g. linking of loyalty/reward identifier to payment device or card) can be enabled to occur at a merchant POS, online, or via mobile device application. In one instance, the linking can occur at a merchant computer system 112 and/or merchant computer device 114 when a consumer, such as 122(1), presents, scans, or swipes a payment device or card, such as 135(1), at a merchant location, such as 136. A mobile commerce application, such as 108, associated with the merchant computer system 112 and/or merchant computer device 114 can generate and store the link, such as establishing an association between the payment device 135(1) and the consumer 122(1), or by generating a loyalty/rewards identifier or proxy, such as a unique number or code to identify the link between the payment device 135(1) and consumer 122(1). In another instance, the linking can occur online at a host or server device, such as 106, when a consumer, such as 122(1), presents, scans, or swipes a payment device or card, such as 135(1), at a merchant location, such as 136, and an associated merchant computer system 112 and/or merchant computer device 114 transmits payment device information to the host or server device 106. A mobile commerce application, such as 102, associated with the host or server device 106 can generate and store the link, such as establishing an association between the payment device 135(1) and the consumer 122(1), or by generating a loyalty/rewards identifier or proxy, such as a unique number or code to identify the link between the payment device 135(1) and consumer 122(1). In yet another instance, the linking can occur at a mobile device, such as 120(1), when a consumer, such as 122(1), enters payment device information, and/or scans or swipes a payment device or card, such as 135(1), at the mobile device 120(1). A mobile commerce application, such as 116(1), associated with the mobile device 120(1) can generate and store the link, such as establishing an association between the payment device 135(1) and the consumer 122(1), or by generating a loyalty/rewards identifier or proxy, such as a unique number or code to identify the link between the payment device 135(1) and consumer 122(1). In other instances, any combination of communications between the merchant computer system 112, merchant computer device 114, host or server device 116, and/or mobile device 120(1) can be used to establish, generate, and store a link between the payment device 135(1) and the consumer 122(1), or to generating and store a loyalty/rewards identifier or proxy, such as a unique number or code to identify the link between the payment device 135(1) and consumer 122(1).

If a consumer is not already enrolled in a particular merchant loyalty/reward program, receipt of a payment device, such as 135(1) or card at a merchant POS, such as a merchant computer system 112 and/or merchant computer device 114, can cause a mobile commerce application program, such as 102, 108, and/or 116(1) to generate a prompt for entry of a loyalty/reward identifier, which can then be linked to the payment device 135(1) or card. The loyalty/reward identifier can, in some instances, be provided to consumers 122(1)-122(N) by way of a QR code, bar code, or other unique code. Linkage between loyalty/reward identifier and payment device 135(1) or card can be stored at a host or server device, such as 106, “in the cloud” so it can be retrieved anytime the payment device 135(1) or card is used. Requests to retrieve a loyalty/reward identifier as part of a payment transaction can include appropriate merchant or loyalty program identifier, such that the correct loyalty/reward identifier can be returned for the specific transaction.

In certain embodiments, such as for a mobile device implementation, a universal loyalty/reward credential can be stored on the mobile device (e.g. in the secure element). For example, a universal loyalty/reward credential can be stored in memory, such as 118(1), of a consumer's mobile device, such as 120(1). One or more merchant or affinity loyalty/reward identifiers can be linked to this universal loyalty/reward credential, instead of to a specific payment device, such as 135(1) or payment card. The mobile device 120(1) can be presented by a consumer 122(1) to a merchant POS, such as a merchant computer system 112 and/or merchant computer device 114, to deliver the stored universal loyalty/reward credential. The merchant POS, such as 112 and/or 114, can send the universal loyalty/reward credential to a host or server device, such as 106, or otherwise “in the cloud” along with the payment transaction. The universal loyalty/reward credential can be used by an associated mobile commerce application program, such as 102, “in the cloud” to determine which specific merchant or affinity loyalty/reward identifier should be associated with the transaction.

In certain embodiments, one or more purchase transactions by a consumer, such as 122(1), using a particular payment device, such as 135(1), can be tracked by a mobile commerce application program, such as 102, 108, and/or 116(1)-116(N). Even though the consumer 122(1) may not be enrolled or otherwise have requested enrollment in a merchant loyalty/reward program associated with a particular merchant, the mobile commerce application program, such as 102, 108, and/or 116(1)-116(N), can allocate, track, and store one or more rewards for the consumer 122(1). The allocation, tracking, and storing can be facilitated when the consumer's payment device 135(1) is linked to the consumer 122(1) by the mobile commerce application program, such as 102, 108, and/or 116(1)-116(N), as described above. After a predefined number of rewards accrues, or when the consumer 122(1) returns to the particular merchant, the mobile commerce application program, such as 102, 108, and/or 116(1)-116(N), may initiate a notification (such as an email or text) to the consumer 122(1) via the consumer's mobile device, such as 120(1)-120(N), and/or initiate a prompt to the consumer 122(1) via a merchant computer system 112 and/or merchant computer device 114, such as a merchant POS device, which can prompt the consumer 122(1) to enroll or otherwise join the merchant loyalty/reward program associated with the particular merchant. In some instances, the notification and/or prompt can include a link to permit the consumer 122(1) to download a mobile commerce application program, such as 116(1), or app to the consumer's mobile device 120(1). If the consumer 122(1) downloads the mobile commerce application program, such as 116(1), or app, the consumer 122(1) can be enrolled into the merchant loyalty/reward program associated with the particular merchant, wherein some or all of the accrued rewards can be obtained and subsequently redeemed by the consumer 122(1). In other instances, the consumer 122(1) can provide personal information, such as email address or other contact information, which can be input to the merchant computer system 112 and/or merchant computer device 114, such as a merchant POS device, and the consumer 122(1) can be enrolled into the merchant loyalty/reward program associated with the particular merchant, wherein some or all of the accrued rewards can be obtained and subsequently redeemed by the consumer 122(1).

In any instance, even if the consumer 122(1) does not enroll into the merchant loyalty/reward program associated with the particular merchant by downloading the mobile commerce application program, such as 116(1), or app, or by providing personal information to the merchant, the mobile commerce application program, such as 102, 108, and/or 116(1)-116(N), can continue to allocate, track, and store one or more rewards for the consumer 122(1). As the consumer's rewards accrue to approach or otherwise reach one or more predefined amounts or levels, the mobile commerce application program, such as 102, 108, and/or 116(1)-116(N), can initiate a notification (such as an email or text) to the consumer 122(1) via the consumer's mobile device, such as 120(1)-120(N), and/or initiate a prompt to the consumer 122(1) via a merchant computer system 112 and/or merchant computer device 114, such as a merchant POS device, which can prompt the consumer 122(1) to obtain a reward by enrolling or otherwise joining the merchant loyalty/reward program associated with the particular merchant. In some instances, the consumer 122(1) may be notified and/or prompted to spend a certain amount of money to obtain additional rewards if the consumer 122(1) enrolls or otherwise joins the merchant loyalty/reward program associated with the particular merchant.

FIGS. 3-8 illustrate example methods according to embodiments of the disclosure. Various operations of the methods described below can be performed by the system components described above and shown in FIGS. 1 and 2. In FIG. 3, the method 300 can begin in block 302. In block 302, an indication can be received that a consumer has entered a predefined merchant location. Block 302 is followed by block 304, in which a notification can be transmitted to a mobile device associated with the consumer. Block 304 is followed by block 306, in which one or more payment tools can be provided on a mobile device for the consumer to facilitate a purchase from a merchant associated with the predefined merchant location. Block 306 is followed by block 308, in which a loyalty/reward credit is generated for an account associated with the consumer. Block 308 is followed by block 310, in which an instruction is received from the consumer to redeem loyalty/reward credit for goods and/or service from the merchant. The method 300 can end after block 310.

In FIG. 4, the method 400 can begin in block 402. In block 402, a network link can be provided for a merchant to access a loyalty/reward application program. Block 402 is followed by block 404, in which an indication can be received that a merchant has opted in to an associated loyalty/rewards program. Block 404 is followed by block 406, in which one or more merchant parameters can be received for a customized merchant loyalty/rewards program. Block 406 is followed by block 408, in which a downloadable app or application program cab be generated for a consumer to access the customized merchant loyalty/rewards program. The method 400 can end after block 408.

In FIG. 5, the method 500 can begin in block 502. In block 502, a code can be received from a consumer's mobile device located at a merchant location. Block 502 is followed by block 504, in which a merchant's loyalty/reward program is identified. Block 504 is followed by block 506, in which access is facilitated to an app or application program associated with the merchant's loyalty/reward program. Block 506 is followed by block 508, in which consumer information is received via the app or application program. Block 508 is followed by block 510, in which one or more payment tools are provided on the consumer's mobile device for the consumer to facilitate a purchase from a merchant associated with the merchant location. Block 510 is followed by block 512, in which loyalty/reward credit is generated for an account associated with the consumer. Block 512 is followed by block 514, in which an instruction is received from a consumer to redeem loyalty/reward credit for goods and/or services from the merchant. The method 500 can end after block 514.

In FIG. 6, the method 600 can begin in block 602. In block 602, a merchant loyalty/rewards credit can be received from one merchant loyalty/rewards program. Block 602 is followed by block 604, in which other merchant loyalty/rewards credit can be received from at least one other merchant loyalty/rewards program. Block 604 is followed by block 606, in which at least one offer or advertisement can be determined based at least in part on the one merchant loyalty/rewards program and the at least one other merchant loyalty/rewards program. Block 606 is followed by block 608, in which the at least one offer or advertisement can be output to a mobile device associated with a consumer. Block 608 is followed by block 610, in which a notification to the consumer's mobile device can be generated upon receiving an indication of at least one of the following: the consumer's mobile device is in a predefined location, an earned reward, a reward threshold, an expiring reward or offer, or a third party product and/or service review. Block 610 is followed by block 612, in which two or more merchants and/or associated merchant loyalty/reward programs can be categorized, organized, ranked and/or prioritized based at least in part on consumer use, preference, conduct and/or behavior. The method 600 can end after block 612.

In FIG. 7, the method 700 can begin in block 702. In block 702, a card/loyalty proxy can be generated. Block 702 is followed by block 704, in which a merchant and/or affiliate identifier can be linked to a payment device via the card/loyalty proxy. Block 704 is followed by block 706, in which multiple merchant and/or affiliate identifiers can be linked to the payment device via the card/loyalty proxy. Block 706 is followed by block 708, in which multiple merchant and/or affiliate identifiers can be associated with a universal loyalty credential. Block 708 is followed by block 710, in which an indication is received that a linked payment device or universal loyalty credential is being used at a point of sale (POS) device, for an online transaction, or via a mobile device transaction. Block 710 is followed by block 712, in which a loyalty/reward activity is determined based at least in part on the card/loyalty proxy. Block 712 is followed by block 714, in which the card/loyalty proxy or universal loyalty credential is transmitted to an associated merchant facilitating a transaction. The method 700 can end after block 714.

In FIG. 8, the method 800 can begin in block 802. In block 802, an indication can be received a consumer has performed a predefined activity. Block 802 is followed by block 804, in which a consumer's account in a loyalty/rewards program can be credited based at least in part on the predefined activity. Block 804 is followed by block 806, in which an indication of the credit can be output to the consumer's mobile device. Block 806 is followed by block 808, in which an instruction can be received from the consumer to redeem a loyalty/reward credit on behalf of a third party. Block 808 is followed by block 810, in which a loyalty/reward activity can be determined based at least in part on the card/loyalty proxy. Block 810 is followed by block 812, in which the card/loyalty proxy can be transmitted to an associated merchant facilitating a transaction. The method 800 can end after block 812.

Using some or all of the above systems and processes, a technical solution with an opt-in mobile loyalty/reward program can be enabled. In certain embodiments, merchants can quickly access tools to create a loyalty/reward program for consumers, and consumers can quickly access tools to utilize the merchants′ loyalty/reward programs. For example, technical solutions involving linking payment devices with consumers can be implemented. By way of further example, technical solutions with loyalty/reward identifiers and universal loyalty/reward credentials can be generated, stored, and used to implement merchant loyalty/reward programs. In this manner, technical solutions can be implemented such that consumers can be connected to merchants via rewards, such as by performing certain activities, and merchants can increase loyalty from participating consumers.

Check in to Pay

In some instances, consumers desire to check in with merchants or merchant locations the consumers are shopping at or otherwise visiting. Certain embodiments of the disclosure can provide systems and processes for facilitating a mobile purchase transaction, such as using a mobile device or phone to pay (as well as redeem offers, redeem loyalty, earn loyalty, etc) at a physical or virtual store utilizing “check in” type functionality. For example, a consumer, such as 122(1) in FIG. 1, using an interface provided by a mobile commerce application, such as 116(1) or app executing on the consumer's mobile device, such as 120(1), can select a particular merchant's store or location, such as 136, facilitated either by location-based service (LBS) or manual selection, and check in to that store or location by selecting or otherwise indicating the merchant's store or location on the interface. In one instance, location services, such as 144(1), associated with the consumer's mobile device 120(1) can provide geolocation data to the mobile commerce application 116(1) or app. In another instance, location services, such as 144(1), associated with the consumer's mobile device 120(1) can provide geolocation data to a mobile commerce application program, such as 108, associated with a merchant computer system, such as 112, or merchant computer device, such as 114. In yet another instance, location services, such as 144(1), associated with the consumer's mobile device 120(1) can provide geolocation data to a mobile commerce application program, such as 102, associated with a host or server device, such as 106. Thus, the relative proximity of the consumer's mobile device 120(1) to a particular merchant location, such as 136, can be determined by comparing the geolocation data from the consumer's mobile device 120(1) to location data associated with the merchant's location, such as location data from a location service, such as 132, associated with a merchant computer system, such as 112, and/or merchant computer device, such as 114, or predefined location data associated with the merchant's location and stored in a data storage device, such as a server device 106 or data store 151.

In any instance, using the mobile commerce application 116(1) or app associated with the consumer's mobile device 120(1), the consumer 122(1) can enter payment device information, or have previously entered and stored the payment device information via the mobile commerce application 116(1) or app. Based at least in part on the geolocation data and payment information from the consumer's mobile device 120(1), the merchant computer system, such as 112, and/or merchant computer device, such as 114, can implement via a mobile commerce application program, such as 108, certain check in to pay functionality. For example, the merchant or merchant cashier can view, at a merchant computer system, such as 112, and/or merchant computer device, such as 114, for instance a point-of-sale (POS) device, a list generated on an interface by a mobile commerce application program, such as 108, of all consumers checked in, and select the corresponding consumer 122(1) desiring to make a purchase based on the consumer 122(1) saying his or her name and/or providing a unique code or identifier to the merchant, and a corresponding input entered to the merchant computer system 112 and/or merchant computer device 114. Rather than focus on a consumer's face or picture to confirm payment after the consumer 122(1) has checked in to the merchant location 136, a person's name and/or unique code or identifier can be used by the merchant computer system 112 and/or merchant computer device 114 to facilitate payment and/or transaction processing. The purchase transaction can then be linked to the consumer's account either by the merchant computer system 112, merchant computer device 114, and/or a host or server device, such as 106, and the purchase transaction can be completed using the consumer's payment device information. In this manner, the purchase transaction can be faciliated, and the consumer's and merchant's need to use “proximity” technology like NFC or QR codes can be alleviated.

Consumers may utilize check in functionality by explicitly checking in and/or implicitly checking in with a merchant location, such as 136. By explictly checking in, a consumer can expressly check in by initiating or otherwise indicating his or her presence to the merchant. In this instance, the consumer 122(1) may initiate the mobile commerce application program 116(1) executing on the consumer's mobile device 120(1) and indicate on a user interface associated with the mobile device 120(1) that the consumer 122(1) wants to check in with the merchant location 136. In another instance, the consumer 122(1) may initiate the mobile commerce application program 116(1) executing on the consumer's mobile device 120(1) and inform the merchant operating a merchant computer system 112 and/or merchant computer device 114 to indicate on a user interface associated with the merchant computer system 112 and/or merchant computer device 114 that the consumer 122(1) wants to check in with the merchant location 136. Likewise, by implicity checking in, a consumer can implicitly check in by initiating an “auto check-in” feature on the mobile commerce application program 116(1) executing on the consumer's mobile device 120(1). In this instance, the geolocation data from the mobile device 120(1) indicates the relative proximity of the consumer from a merchant's location, such as 136. When the consumer's mobile device 120(1) within a predefined distance from the merchant's location 136, the mobile commerce application program 116(1) can implicity check in the consumer with the merchant's location, and the mobile commerce application program 116(1) can communicate with the merchant computer system 112 and/or merchant computer device 114 to complete the check in of the consumer 122(1) with the merchant's location 136.

In one embodiment, by way of a client-type device, such as a merchant computer system 112 and/or merchant computer device 114, a merchant can communicate via at least one network, such as 126, to a hosted website and/or via a check in to pay application program, such as a mobile commerce application program 102, executing on a host or server device, such as 106, and configure the check in to pay application program or mobile commerce application program 102 to facilitate purchase transactions by consumers with the merchant. In another embodiment, a merchant computer system 112 and/or merchant computer device 114 can download a mobile commerce application program, such as 108, from a website, such as 134 and/or host or server device, such as 106, wherein the mobile commerce application program 108 can facilitate check in to pay functionality including purchase transactions by consumers with the merchant. In any instance, a hosted website and/or check in to pay application program or mobile commerce application program 102 on a server device 106, or a mobile commerce application program 108 on a merchant computer system 112 and/or merchant computer device 114 can implement a set of computer-executable instructions to enable a check in to pay system and service. When the check in to pay application program or mobile commerce application program, such as 102 and 108, is configured, the set of computer-executable instructions can receive an indication when a consumer, such as 122(1), visits the merchant location, such as 136, and the check in to pay application program or mobile commerce application program 102, 108 can transmit respective indications to a POS device, such as a merchant computer system 112 and/or merchant computer device 114, associated with the merchant corresponding to consumers that have checked in at the merchant location 136 using respective mobile devices, such as 120(1)-120(N), or other client devices. The POS device, such as a merchant computer system 112 and/or merchant computer device 114, can be configured by a mobile commerce application program, such as 102 and 108, to output via a graphical user interface, profile information and/or information associated with the checked in consumers 122(1)-122(N). In some embodiments, the merchant can receive a consumer name and/or unique code or identifier from the consumer, and the merchant can input or otherwise select corresponding information on the POS device, such as a merchant computer system 112 and/or merchant computer device 114. The set of computer-executable instructions can be further configured to receive a payment command, consumer name, and/or unique code or identifier from the POS device, such as a merchant computer system 112 and/or merchant computer device 114, from the merchant, and to facilitate processing payment information associated with the consumer, such as 122(1), to implement the payment command. After processing the payment device information or otherwise receiving payment authorization or confirmation, the set of computer-executable instructions can transmit a payment confirmation to the POS device, such as a merchant computer system 112 and/or merchant computer device 114, and/or to the consumer 122(1). In some embodiments, the consumer 122(1) may receive a payment authorization request, which may be a single click authorization, PIN, or code. In the manner described above, various merchants, regardless of size, can adopt and implement a check in to pay program or service.

In one embodiment, by way of a mobile device, such as 120(1), or other client device, such as a laptop computer or tablet, a consumer 122(1) can download a check in to pay application program, such as 116(1), or app to the consumer's mobile device 120(1) or other client device. For example, a consumer 122(1) can visit a website, such as 134, using his or her mobile device 120(1), and when prompted by the website 134, the consumer 122(1) can download a mobile commerce application program 116(1) or app onto the mobile device 120(1). Using the mobile commerce application program 116(1) or app, the consumer 122(1) can create an account and input certain personal or identification information to the mobile commerce application program 116(1) or app, such as a name, mobile telephone number, email or messaging address, or social media application account name. In some embodiments, the consumer 122(1) can input, via the mobile commerce application program 116(1) or app, financial or payment information associated with a payment method, such as adding a bank account number, payment device number, security code, etc., and, in some instances, the consumer 122(1) can charge, load, or otherwise authorize, via the mobile commerce application program 116(1) or app, a payment account with a pre-paid value for use in purchasing the merchant's goods and/or services. In some embodiments, the consumer 122(1) can create, via the mobile commerce application program 116(1) or app, a personal identification number (PIN) or other code for use in accessing the payment account.

When the consumer 122(1) visits a merchant location, such as 136, utilizing a check in to pay application program, mobile commerce application program, such as 116(1), or app, the consumer's check in to pay application program, mobile commerce application program 116(1) or app, can transmit an indication to the merchant computer system 112, merchant computer device 114 and/or a check in to pay application program or mobile commerce application program, hosted by the merchant such as mobile commerce application program 108, or hosted on a host or server device 106, such as mobile commerce application program 102, that the consumer 122(1) is checking in to the merchant location 136. For example, in certain embodiments, the consumer 122(1) can manually enter his or her location into a mobile device 120(1) or client device, or may manually select from a list of map locations or otherwise indicate on a map output to a mobile device 120(1) or client device. When the consumer 122(1) is ready to make a purchase, the consumer 122(1) can provide his or her name, or a unique code to the merchant or merchant cashier for input to a merchant computer system 112 and/or merchant computer device 114, such as a POS device. In some embodiments, the consumer 122(1) may receive a payment authorization and/or confirmation notification via the consumer's check in to pay application program, mobile commerce application program 116(1) or app. In the manner described above, since consumers 122(1)-122(N) can store certain personal and financial or payment information via the mobile commerce application program 116(1) or app, consumers can readily utilize the check in to pay system and service, and in some instances, check in and/or payment can be accomplished with a single click or authorization from the consumer, such as 122(1).

FIG. 9 illustrates an example method according to embodiments of the disclosure. Various operations of the methods described below can be performed by the system components described above and shown in FIGS. 1 and 2. In FIG. 9, the method 900 can begin in block 902. In block 902, an indication can be received that a consumer has arrived at or will arrive at a predefined merchant location. Block 902 is followed by block 904, in which a respective indication can be transmitted to a point of sale (POS) device associated with a merchant. Block 904 is followed by block 906, in which a consumer's identity, merchant identity and/or a merchant's loyalty/reward program can be determined based at least in part on the received indication. Block 906 is followed by block 908, in which information can be output associated with one or more consumers at the predefined merchant location. Block 908 is followed by block 910, in which a name or unique code can be received with payment information from at least one consumer. Block 910 is followed by block 912, in which the name or unique code is authenticated. Block 912 is followed by block 914, in which payment processing associated with a consumer purchase of a good and/or service from the merchant can be facilitated. Block 914 is followed by block 916, in which a payment authorization request can be received from the consumer. Block 916 is followed by block 918, in which a payment confirmation, offer and/or loyalty/rewards credit confirmation can be transmitted to a POS device and/or mobile device associated with the consumer. The method 900 can end after block 918.

In certain embodiments, a check in to pay application program, mobile commerce application program, such as 108, or app can facilitate issuing and/or redeeming a coupon and/or loyalty/reward credits at a predefined merchant location, such as 136. The check in to pay application program, mobile commerce application program, such as 108, or app can receive an indication that an arriving or waiting consumer, such as 122(1), wants to redeem a previously received coupon and/or loyalty/reward credits with the expected purchase transaction. In certain instances, the check in to pay application program, mobile commerce application program, such as 108, or app can generate and transmit a coupon and/or loyalty/reward credits to an arriving or waiting consumer, such as 122(1), and the check in to pay application program, mobile commerce application program, such as 108, or app can redeem the recently received coupon and/or loyalty/reward credits with an expected purchase transaction when the consumer 122(1) is ready to check out. The information associated with the coupon and/or loyalty/reward credits can be stored on the consumer's mobile device, such as 120(1) and/or client device associated with the consumer or merchant, such as a merchant computer system 112 and/or merchant computer device 114, or may be stored in a device, such as a host or server device 106, accessible via at least one network 126 by a POS device and/or a mobile device 120(1) and/or client device associated with the consumer. In any instance, the check in to pay application program, mobile commerce application program, such as 108, or app can obtain information associated with the coupon or otherwise access a loyalty/reward account associated with the consumer 122(1), merchant and/or merchant loyalty/reward program, and facilitate redemption of the coupon and/or loyalty/reward credits before, during, or after a purchase transaction with the consumer 122(1). In this manner, coupons and/or loyalty/reward credits can be redeemed with a purchase transaction involving a consumer, such as 122(1) using a mobile device, such as 120(1) and/or client device to interact with a check in to pay application program, mobile commerce application program, such as 108, or app.

In certain embodiments, a check in to pay application program, mobile commerce application program, such as 108, or app can facilitate queuing two or more consumers, such as 122(1) and 122(N), who have indicated arrival at or will arrive at a predefined merchant location, such as 136. The check in to pay application program, mobile commerce application program, such as 108, or app can associate each consumer 122(1), 122(N) with a respective name and/or unique code, and maintain the names and/or unique codes in a predefined order based at least in part on some or all of the following information: consumer arrival time, expected service time, expected order completion, expected good and/or service completion, or elapsed consumer wait time. In certain instances, based at least in part on changes to some or all of the information, or newly received information associated with additional consumers, the check in to pay application program, mobile commerce application program, such as 108, or app can change the predefined order for some or all of the names and/or unique codes as well add new names and/or unique codes associated with one or more additional customers. In this manner, checkout information for consumers in line or otherwise waiting for or expecting checkout at a merchant location can be suitably organized at a merchant computer system 112 and/or merchant computer device 114, such as a POS device, for processing each of the consumer's transactions.

In certain embodiments, a check in to pay application program, mobile commerce application program, such as 108, or app can facilitate communications between merchants and consumers. For merchants, a merchant can view a user interface generated by a mobile commerce application program, such as 108, the number of transactions within a predefined time and any relevant details of the transactions, such as purchase price, items purchased, etc. Further, a merchant can generate and send via a mobile commerce application program, such as 108, a query to any number of consumers, such as those that have not visited a merchant location, such as 136, for a predefined time, such as the last 6 months. In some instances, a merchant can generate notifications to consumers via a mobile commerce application program, such as 108, communicating with a mobile commerce application program, such as 116(1), executing on a consumer's mobile device, such as 120(1), to obtain a discount when the consumer 122(1) visits the merchant location, such as 136, and makes a subsequent purchase transaction. Further, notifications to consumers can include messages to consumers who have not visited in awhile, to consumers who are frequent customers, and to visit a merchant location, such as 136, for a special event.

Using some or all of the above systems and processes, a technical solution implementing mobile purchase transaction program, such as a check in to pay application system and service, can be enabled. For example, technical solutions involving transmitting consumer payment information to merchant computer systems and devices, such as POS devices, can be provided. In this manner, technical solutions can be implemented such that merchants can quickly access tools to create a check in to pay application program for consumers, and merchants and consumers can quickly access tools to utilize the merchants′ check in to pay application programs.

Interruptive Alert During Transaction

In some instances, consumers may regret making certain purchases. Certain embodiments of the disclosure can provide systems and processes for interrupting a purchase transaction, such as providing a consumer alert or notification on the consumer's mobile phone and/or a POS device before or during a purchase transaction regarding a factor that could affect the consumer's decision in completing the transaction. For example, if a consumer, such as 122(1) in FIG. 1, is buying movie tickets on or with his or her mobile phone, such as 120(1), the consumer 122(1) can be alerted by a mobile commerce application program, such as 116(1), or app that he or she has exceeded his or her monthly budget for entertainment, and the consumer 122(1) can decide if he or she still wants to complete the purchase transaction. In one instance, the consumer 122(1) may be interacting with a website, such as 134, via the consumer's mobile device 120(1) to browse movie listings. When the consumer 122(1) begins to initiate a purchase transaction via the website 134, the mobile commerce application program 116(1) may be called upon by the website 134 and/or consumer's mobile device 120(1) to provide payment information. In another instance, the consumer 122(1) may be interacting with a website, such as 134, via a mobile commerce application program, such a 116(1), and payment information may be called upon by the website 134. In another instance, the consumer 122(1) may be conducting a purchase transaction at a merchant location 136, and may tap his or her mobile device 120(1) to initiate the purchase transaction. In any instance, the mobile commerce application program 116(1) executing on the consumer's mobile device 120(1) can access a predefined consumer budget and determine whether the proposed purchase transaction is within or otherwise exceeds the budget. If the budget is not exceeded, the transaction is permitted to proceed without having to generate an interruptive alert. If the budget is exceeded, the transaction can be interrupted by the mobile commerce application program 116(1), which can generate an alert or notification to the consumer via the mobile device 120(1) that the budget has been or will be exceeded by completing or otherwise entering into the transaction. The consumer 122(1) can be provided an option by the mobile commerce application program 116(1) to proceed with the transaction or cancel the transaction, in which case the transaction can continue or be canceled depending on the consumer's election. Thus, in certain instances, a two way communication between a consumer 122(1) and a payment application program, mobile commerce application program, such as 116(1), or app can be facilitated, wherein the consumer 122(1) can be prompted by the payment application program, mobile commerce application program, such as 116(1), or app prior to completing a purchase transaction, and complete or cancel the purchase transaction with a better understanding of other information associated with the consumer 122(1) and/or other merchants.

In one embodiment, by way of a mobile device, such as 120(1), or other client device, such as a laptop computer or tablet, a consumer, such as 122(1), can initiate an interrupt transaction notification feature in a payment application program, mobile commerce application program, such as 116(1), or app accessible via the consumer's mobile device 120(1) or other client device. For example, in a payment application program, mobile commerce application program, such as 116(1), or app accessible via the consumer's mobile device 120(1) or other client device, a set of computer-executable instructions can be configured to receive an indication from a consumer 122(1) to initiate an interrupt transaction notification based at least in part on at least one user-defined threshold, predefined action, recent occurrence, or transaction interrupter. The consumer 122(1) may define or otherwise input, via the payment application program, mobile commerce application program, such as 116(1), or app, one or more thresholds, such as, but not limited to, daily, weekly, monthly, or periodic spending limits, categorized budgets (entertainment, food, utilities, clothing, etc.), or bank or financial account withdrawal limits. In some embodiments, the consumer 122(1) may select, via the payment application program, mobile commerce application program, such as 116(1), or app, one or more predefined actions, such as, but not limited to, spending after a certain time and/or date, spending at a certain merchant or location, or spending on a certain good and/or service. In some embodiments, the consumer 122(1) may manually select or elect to receive, via the payment application program, mobile commerce application program, such as 116(1), or app, notifications of recent occurrences or transaction interrupters, such as, but not limited to, a lower price at a different or nearby merchant, offers to purchase other goods and/or services with the present purchase transaction, and switching payment devices to receive or obtain loyalty/reward points and/or monetary discounts. In any instance, the set of computer-executable instructions can be configured to monitor one or more user-defined thresholds and/or predefined actions, and/or for recent occurrences and/or transaction interrupters, and interrupt a purchase transaction when one or more user-defined thresholds, predefined actions, recent occurrences, or transaction interrupters are exceed or otherwise detected.

In one embodiment, a consumer payment application program, mobile commerce application program, such as 116(1), or app accessible via the consumer's mobile device, such as 120(1), or other client device can be configured to interrupt a consumer's purchase transaction with a merchant by outputting a prominent notification to the consumer 122(1) on a user interface with the purchase transaction information. In one instance, the notification can be generated on the consumer's mobile device 120(1) via a mobile commerce application program, such as 116(1), executing on the mobile device 120(1). In any instance, the notification may include an audible, visual, and/or tactile alert generated by the consumer's mobile device or other client device. The user interface may include a command to confirm payment and/or a command to cancel the purchase transaction.

In some embodiments, the consumer payment application program, mobile commerce application program, such as 116(1), or app may communicate via at least one network, such as 126, with a merchant computer system, such as 112, and/or merchant computer device, such as 114, or POS device the merchant is operating to facilitate the purchase transaction. The consumer payment application program, mobile commerce application program, such as 116(1), or app can be configured to interrupt a consumer's purchase transaction with a merchant by outputting a prominent notification, with the purchase transaction information, to the consumer 122(1) and/or merchant on a user interface associated with the merchant computer system, such as 112, and/or merchant computer device, such as 114, or POS device. Similar to the notification on the consumer's mobile device or other client device, the notification may include an audible, visual, and/or tactile alert generated by the POS device. The user interface of the merchant computer system, such as 112, and/or merchant computer device, such as 114, or POS device may include a command to confirm payment and/or a command to cancel the purchase transaction.

In certain embodiments, a consumer payment application program, mobile commerce application program, such as 116(1), or app can generate a notification to the consumer on both the consumer's mobile device, such as 120(1), or other client device, and the merchant computer system, such as 112, and/or merchant computer device, such as 114, or merchant's POS device. If the consumer, such as 122(1), decides to confirm or cancel payment for the purchase transaction, the notification on both the consumer's mobile device 120(1) or other client device, and the merchant computer system, such as 112, and/or merchant computer device, such as 114, or merchant's POS device, can be cleared or otherwise addressed with a single click or authorization from the consumer 122(1) and/or merchant.

In certain embodiments, a financial institution, such as 124, may be in communication with a merchant computer system, such as 112, and/or merchant computer device, such as 114, or merchant's POS device to facilitate an interruptive alert during a purchase transaction. In one instance, a payment processing application program, such as 154, associated with the financial institution 124 can include a hold component and/or module with computer-executable instructions to receive an indication that a user-defined threshold, predefined action, recent occurrence, or transaction interrupter exists. The hold component and/or module can initiate a notification to the merchant computer system, such as 112, and/or merchant computer device, such as 114, or merchant's POS device to prompt the consumer, such as 122(1), to confirm whether to proceed or cancel the transaction. Upon receipt of an input from the consumer 122(1) via the merchant computer system, such as 112, and/or merchant computer device, such as 114, or merchant's POS device, the hold component and/or module can proceed with or cancel the transaction as instructed.

FIG. 10 illustrates an example method according to embodiments of the disclosure. Various operations of the methods described below can be performed by the system components described above and shown in FIGS. 1 and 2. In FIG. 10, the method 1000 can begin in block 1002. In block 1002, one or more consumer preferences can be received for an alert or notification to be sent to a point of sale (POS) device near the consumer or to one more devices associated with the consumer. Block 1002 is followed by block 1004, in which one or more user-defined thresholds, predefined actions, recent occurrences, or transaction interrupters can be determined based at least in part on the one or more received consumer preferences. Block 1004 is followed by block 1006, in which an indication can be received from the consumer to initiate transaction notification based at least in part on the one or more user-defined thresholds, predefined actions, recent occurrences, or transaction interrupters. Block 1006 is followed by block 1008, in which at least one trigger can be configured when one or more user-defined thresholds, predefined actions, recent occurrences, or transaction interrupters are detected and/or received. Block 1008 is followed by block 1010, in which an alert or notification can be transmitted to the point-of-sale device near the consumer and/or to one or more devices associated with the consumer. Block 1010 is followed by block 1012, in which a command is provided to the consumer to confirm payment and/or cancel a purchase transaction. Block 1012 is followed by block 1014, in which command request can be cleared at the point of sale device and/or one or more devices associated with the consumer based at least in part on the receipt of the command from the consumer. The method 1000 can end after block 1014.

Using some or all of the above systems and processes, technical solutions implementing interrupting a purchase transaction can be enabled. For example, technical solutions involving transmitting notifications to a consumer before and/or during a purchase transaction, and before the purchase transaction is complete can be provided. In this manner, technical solutions can be implemented such that certain purchase transactions can be ceased before the purchase transactions are completed, thus permitting consumers to better manage budgets as well as consumer spending, and to be better informed about information that may affect the consumer's decision to complete a purchase transaction.

Share Redeemed Offer

In some instances, consumers desire to share an offer they have received for goods and/or services with others, such as friends and family members. Certain embodiments of the disclosure can provide systems and processes for sharing an offer that has been received by a consumer with others. For example, FIGS. 11-13 illustrate example methods 1100-1300 for sharing a received offer or discount for products or services with selected friends according to certain embodiments of the disclosure. Various operations of the methods described below can be performed by the system components described above and shown in FIGS. 1 and 2. These methods can be implemented, for example, using a mobile commerce application program, such as 116(1), which can execute on a consumer's mobile device, such as 120(1), or other client device. The mobile commerce application program 116(1) can launch, for instance, by the consumer 122(1) manually selecting an icon associated with the share redeemed offer module of the mobile commerce application program 116(1) on the touch-enabled display of the consumer's mobile device 116(1) or other client device. The share redeemed offer module or mobile commerce application program 116(1) can have a set of embedded tools for accessing the consumer's electronic phonebook, contacts list, and/or friends or affiliation listings on one or more social networking websites.

Referring now to FIGS. 11-13, the example method 1100 can begin at block 1102 with the receipt of a request to download the mobile commerce application program that includes the share redeemed offer module. In block 1104, the application program, including the share redeemed offer module, can be transmitted via at least one network 126 from the host or server device 106 to the consumer mobile device, such as 120(1), for download. For example, by way of a consumer's mobile device 120(1) or other client device, such as a laptop computer or tablet, a consumer, such as 122(1), can download a merchant-branded mobile commerce application program 116(1) that includes the share redeemed offer module to the consumer's mobile device 120(1) or other client device.

In block 1106, an input can be received to launch the share redeemed offer module of the mobile commerce application program 116(1) at the consumer's mobile device 120(1). In certain embodiments, the mobile commerce application program 116(1) can launch automatically after completing the downloading process. Alternatively, an icon associated with the mobile commerce application program 116(1) can be displayed and selected by the consumer 122(1) on the consumer's mobile device 116(1). In block 1108, the mobile commerce application program 116(1) can be launched at the consumer's mobile device 120(1). The mobile commerce application program 116(1) can present, generate, and display on the consumer's mobile device 120(1) one or more account set-up prompts in block 1110. For example, the prompts can include one or more fields for receiving personal information, social media account information, passwords, and any other types of information known to the consumer for creating a personalized account for the share redeemed offer module. In block 1112, one or more inputs associated with the set-up prompts can be received at the I/O interface of the consumer's mobile device 120(1). For example, when prompted, the consumer 122(1) can create an account and input certain identification information to the mobile commerce application program 106(1), such as a name, mobile telephone number, email or messaging address, or social media application account name and password. All or a portion of this information may be stored in memory of the consumer's mobile device 120(1) or in the memory, such as 118(1) or a database, such as 151, associated with a host or server device, such as 106, and accessible via an authorization token stored in the memory 118(1) or as part of the share redeemed offer module of the mobile commerce application program 106(1) on the consumer's mobile device 120(1). Optionally, in block 1114, a personal identification number (PIN) code for accessing the consumer account can be received at the consumer's mobile device 120(1). For example, the consumer 122(1) can input a PIN or other code at the display for use in accessing the consumer's account in the share redeemed offer module of the mobile commerce application program 106(1). In this way, access to the consumer's personal information, stored contact information, and access to the consumer's social networking accounts may secured.

Referring now to FIG. 12, the process 1200 begins at block 1202, where an offer can be received and displayed on the consumer's mobile device, such as 120(1) in FIG. 1. In certain embodiments, the offer can be in the form of an email, text message (whether smart messaging service (SMS), extended messaging service (EMS) or multimedia messaging service (MMS)), or an offer that has been received from another mobile commerce application program, such as 116(N), or module and downloaded onto the consumer's mobile device 120(1) or other client device. In some instances, the offer can be a “one-time use” or single use offer, wherein the offer can be used or otherwise redeemed only a single time. In block 1204, an input to launch the application program 106 having the share redeemed offer module can be received at the consumer's mobile device 120(1). For example, the consumer 122(1) can launch the mobile commerce application program 116(1) by, for example, selecting an icon associated with the mobile commerce application program 116(1) on the display of the consumer's mobile device 120(1) or other client device in block 1206.

In block 1208, the offer can be retrieved. For example, the mobile commerce application program 116(1) can retrieve or download the offer either directly or via the server device 106. In block 1210, a listing of names from the contacts list and/or digital phonebook at the consumer's mobile device 116(1) can be retrieved. For example, the share redeemed offer module of the mobile commerce application program 116(1) can download a listing of names from one or more of the digital phonebook or contacts list provided on the consumer's mobile device 120(1) or other client device. Alternatively or in addition, in block 1212, one or more social networking sites, such as website 134, can be accessed and a listing of names of friends or acquaintances can be retrieved from the social networking sites. For example, the share redeemed offer module of the mobile commerce application program 116(1) can access the account information and passwords earlier input into the consumer's mobile device 120(1) (e.g., either stored locally or on the server) and can access the one or more social networking sites, such as website 134, via at least one network, such as 126, to access an additional listing of names or “friends” or other similarly designated contacts to present on the display of the consumer's mobile device 120(1) for optional selection by the consumer 122(1). In addition, the share redeemed offer module of the mobile commerce application program 116(1) may display input fields for names and contact information for one or more persons not identified in the retrieved lists, such that the consumer 122(1) can input that information directly via an I/O interface, such as 142(1) of the consumer's mobile device 120(1).

In block 1216, a request to identify recipients of the offer can be displayed on the consumer's mobile device 120(1). For example, the share redeemed offer module of the mobile commerce application program 116(1) can take the retrieved listing of names in the previous blocks and can display a request as to who the offer should be sent to on the consumer's mobile phone 120(1) or other client device. In addition, the share redeemed offer module of the mobile commerce application program 116(1) may display input fields for names and contact information for one or more persons not identified in the retrieved lists, such that the consumer 122(1) can input that information directly via the I/O interface 142(1) of the consumer's mobile device 120(1). In block 1220, the consumer 122(1) can then select which “friends” to share the offer with by the consumer's mobile device 120(1) receiving a selection of one or more presented names or receiving inputs for one or more names not displayed. In some instances, the offer may be shared or otherwise transferred to only a single person in the retrieved or otherwise accessed listing of names, contacts, and/or contact information.

If the selected friend was identified from the contacts list, the digital phonebook, or any other portion of the memory 118(1) on the consumer's mobile device 120(1), the Mobile Device branch is followed to block 1224, where an email address or mobile phone number can be associated with each selected recipient. For example, for those selected friends from the digital phonebook or contacts list on the consumer's mobile device 120(1), the share redeemed offer module of the mobile commerce application program 116(1) can access the contacts list or digital phonebook and identify an email address or phone number associated with the selected friend in order to forward a copy of the offer to each selected friend. In block 1226, a copy of the offer can be transmitted to the one or more selected recipients via email at an email address identified as being associated with each selected recipient or via text message at a phone number identified as being associated with each selected recipient. For example, the share redeemed offer module of the mobile commerce application program 116(1) can identify the email or mobile phone number associated with each selected friend, and forward a copy of the offer to those selected friends via an email or text message (whether SMS, EMS, or MMS) either directly or via the server.

Returning to block 1222, when recipients were identified from information on a social networking site, the Social Networking Site branch can be followed to block 1230, where a determination is made as to whether to post the offer on the social networking site, such as website 134, or to directly contact the selected recipient based on information retrieved from the social networking site, such as website 134. If the recipients will be directly contacted, the Directly Contact branch can be followed to block 1232, where the share redeemed offer module of the mobile commerce application program 116(1) can access the social networking site, such as website 134. In block 1234, the share redeemed offer module of the mobile commerce application program 116(1) can determine contact information for the selected recipient based on information provided on the social networking site, such as website 134. For example, the share redeemed offer module of the mobile commerce application program 116(1), either directly via the mobile commerce application program 116(1) on the consumer's mobile phone 120(1) or via a host or server device 106, can identify contact information for each of the recipients identified from the one or more social networking websites, such as website 134. The contact information may include an email address and/or mobile phone number. In block 1226, a copy, link, or notification of the offer can be transmitted to the selected recipient via email or text message. For example, the share redeemed offer module at the consumer's mobile device 120(1) or at the server device 106 can then generate and transmit an email or text message (whether SMS, EMS, or MMS) that includes the offer to these recipients, either directly or via the server device 106 using the obtained email address or phone number from the social networking site, such as website 134. Once all the selected recipients have been contacted, the process can continue to the END block.

If the selected recipients will be contacted via the social networking site, the Social Networking Site branch can be followed to block 1236, where a message is generated for posting. For example, the share redeemed offer module of the mobile commerce application program 116(1) can generate the message or provide a user-input field for the consumer 122(1) to input the desired message at the consumer's mobile device 120(1). The message may also include a copy or link to the offer being shared by the consumer 122(1). In block 1238, the social networking site can be accessed. For example, the share redeemed offer module of the mobile commerce application program 116(1) can access, via at least one network 126, the social networking site, such as website 134, using the consumer's user name and/or password. The share redeemed offer module of the mobile commerce application program 116(1) can access the social networking site, such as website 134, via the server device 106 or use an authorization token to retrieve and send the user name and/or password for the consumer to the social networking site, such as website 134, for access.

In block 1240, the page associated with the selected recipient can be accessed at the social networking site. For example, the share redeemed offer module of the mobile commerce application program 116(1) can access the consumer's page or the individual pages of the selected recipients for posting of the offer. In block 1242, the generated message related to the offer can be posted or the offer is linked for each selected recipient. For example, the share redeemed offer module of the mobile commerce application program 116(1) can post a message regarding the offer or attach a copy or link to the offer on each selected recipient's page on the social networking website, such as website 134, and/or on the consumer's page. Once all the selected recipients have been contacted, the process can continue to the END block.

In another embodiment or in addition to the embodiment described above, the user interface generated by the mobile commerce application program 116(1) can include one or more fillable fields that the consumer 122(1) can provide information in to select the friends to which the consumer 122(1) wants to forward the offer. For example, the user interface can display one or more email address fields on the display of the consumer's mobile phone 120(1) or other client device. The consumer 122(1) can use a physical or digital keypad or dynamic linking to fill in the web addresses of those to which the offer will be forwarded. This option may be included even when other information is provided from contact listings or listings from social networking websites, such as website 134, as some friends may not be identified in either of those listings.

In certain embodiments related to a “one-time use” and/or single use offer, such an offer can be associated with an offer identification code and/or number.

The offer identification code and/or number can be generated by a mobile commerce program application, such as 102, 108, or 116(1), associated with the offer, and stored for subsequent processing and retrieval by the mobile commerce program application. When a “one-time use” or single use offer is transmitted or otherwise transferred from one consumer to another consumer, the offer can be redeemed by the receiving consumer by, for example, providing the offer identification code and/or number to a merchant, such as presenting the offer with the offer identification code and/or number. In some instances, a QR code or bar code with an embedded offer identification code and/or number can be presented to the merchant. In any instance, the merchant can obtain and transmit the offer identification code and/or number via an associated merchant computer system 112 and/or merchant computer device 114 to the mobile commerce program application, such as 102 and/or 108, wherein the identification code and/or number can be obtained, compared, and validated for redeeming the offer a single time.

By way of another example, one consumer may transmit or otherwise transfer a “one-time use” or single use offer to another consumer, wherein the particular offer is associated with only a single email address and/or proxy identifier. In this instance, the email address and/or proxy identifier may be associated with an offer identification code and/or number generated and stored by a mobile commerce program application, such as 102, 108, or 116(1). The offer can be redeemed by the receiving consumer by, for example, providing the email address and/or proxy identifier to a merchant. The merchant can obtain and transmit the email address and/or proxy identifier via an associated merchant computer system 112 and/or merchant computer device 114 to the mobile commerce program application, such as 102 and/or 108, wherein the identification code and/or number can be obtained, compared, and validated for redeeming the offer a single time.

In some embodiments, the transmission or transfer of a “one-time use” or single use offer to another consumer may be the sharing of a QR code, bar code, machine-readable code, code, number, or device that is transmitted or transferred from one consumer to the other. Prior to generating the QR code, bar code, machine-readable code, code, number, or device, the QR code, bar code, machine-readable code, code, number, or device may be identified with a “one-time use” or single use offer or otherwise stored for subsequent retrieval by a mobile commerce program application, such as 102, 108, or 116(1). When the QR code, bar code, machine-readable code, code, number, or device is presented to a merchant and/or processed by a host or server device 106, the QR code, bar code, machine-readable code, code, number, or device can be compared with previously stored data and recognized as a QR code, bar code, machine-readable code, code, number, or device, the QR code, bar code, machine-readable code, code, number, or device identified with a “one-time use” or single use offer.

In any instance, when a “one-time use” or single use offer is redeemed by at least one consumer, the offer can no longer be redeemed, and the mobile commerce program application, such as 102, 108, or 116(1), can store or edit information to limit or prevent the particular offer from being redeemed again.

FIG. 13 illustrates an example data flow diagram illustrating an example method and associated user interfaces for sharing an offer that has been received by a consumer with others in accordance with an embodiment of the disclosure. In a first instance, a consumer 1 can receive an offer via a mobile device, such as an offer for “50% off now.” In a second instance, the consumer can interact with the mobile device to “share” the offer using contact information stored on or otherwise accessible via the consumer 1's mobile device, wherein the offer is transmitted to a consumer 2 with an associated mobile device. In a third instance, a consumer 2 can receive the same offer as consumer 1 via a mobile device associated with the consumer 2. In a fourth instance, a consumer 3 can receive the same offer or invitation as consumer 1 to attend a “VIP Event Aug. 5, 2012” via a mobile device associated with the consumer 3, wherein the offer of invitation is transmitted by consumer 1 to consumer 3 with an associated mobile device using contact information stored on or otherwise accessible via the consumer 1's mobile device.

FIGS. 14-35 illustrate example user interfaces for implementing certain systems and methods for facilitating loyalty and reward functionality in mobile commerce according to certain embodiments of the disclosure. For example, some or all of the user interfaces can be used to implement the system and system components shown and described with respect to FIGS. 1 and 2, and the methods shown and described with respect to FIGS. 3-13.

FIGS. 14-18, 20-25, and 27-34 illustrate several example user interfaces displayed by a mobile device in accordance with an embodiment of the disclosure. In particular, these user interfaces can be used for enabling an opt-in mobile loyalty/reward program.

FIGS. 19, 26, and 34 illustrate several example user interfaces displayed by a mobile device in accordance with an embodiment of the disclosure. In particular, these user interfaces can be used for facilitating a mobile purchase transaction, such as using a mobile device or phone to pay (as well as redeem offers, redeem loyalty, earn loyalty, etc) at a physical or virtual store utilizing “check in” type functionality.

FIG. 35 illustrates an example user interface displayed by a mobile device in accordance with an embodiment of the disclosure. In particular, this user interface can be used for interrupting a purchase transaction, such as providing a consumer alert or notification on the consumer's mobile phone and/or a POS device before or during a purchase transaction regarding a factor that could affect the consumer's decision in completing the transaction.

Using some or all of the above systems and processes, technical solutions implementing sharing a redeemed offer can be enabled. For example, technical solutions involving accessing a consumer's address book to facilitate transmitting particular offers from one consumer to another consumer can be provided. In this manner, technical solutions can be implemented such that contact information from a consumer's address book can be used without having one consumer input another consumer's contact information, such as an email address, to transmit an offer from the one consumer to the other consumer.

The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed

The computer-executable program instructions described herein may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or 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 storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer-readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram 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 elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks

Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. A computer-implemented method for providing a loyalty/reward program, the method comprising:

receiving an indication that a consumer has entered a predefined merchant location;

transmitting a notification to a mobile device associated with the consumer;

providing one or more payment tools on a mobile device for the consumer to facilitate a purchase from a merchant associated with the predefined merchant location;

generating a loyalty/reward credit for an account associated with the consumer; and

receiving an instruction from the consumer to redeem loyalty/reward credit for goods and/or service from the merchant.

2. The method of claim 1, further comprising:

providing a network link for the merchant to access a loyalty/reward application program;

receiving an indication that the merchant has opted in to an associated loyalty/rewards program;

receiving one or more merchant parameters for a customized merchant loyalty/rewards program; and

generating a downloadable app or application program for the consumer to access the customized merchant loyalty/rewards program.

3. The method of claim 1, further comprising:

receiving a code from the consumer's mobile device located at a merchant location;

identifying a merchant's loyalty/reward program;

facilitating access to an app or application program associated with the merchant's loyalty/reward program; and

receiving consumer information via the app or application program.

4. The method of claim 1, further comprising:

receiving a merchant loyalty/rewards credit from one merchant loyalty/rewards program;

receiving other merchant loyalty/rewards credit from at least one other merchant loyalty/rewards program;

determining at least one offer or advertisement based at least in part on the one merchant loyalty/rewards program and the at least one other merchant loyalty/rewards program;

outputting the at least one offer or advertisement to the consumer's mobile device;

generating or transmitting a notification to the consumer's mobile device upon receiving an indication of at least one of the following: the consumer's mobile device is in a predefined location, an earned reward, a reward threshold, an expiring reward or offer, or a third party product and/or service review; and

categorizing, organizing, ranking and/or prioritizing two or more merchants and/or associated merchant loyalty/reward programs based at least in part on consumer use, preference, conduct and/or behavior.

5. The method of claim 1, further comprising:

generating a card/loyalty proxy;

linking a merchant and/or affiliate identifier to a payment device via the card/loyalty proxy;

linking multiple merchant and/or affiliate identifiers to the payment device via the card/loyalty proxy;

associating multiple merchant and/or affiliate identifiers with a universal loyalty credential;

receiving an indication that a linked payment device or universal loyalty credential is being used at a point of sale (POS) device, for an online transaction, or via a mobile device transaction;

determining a loyalty/reward activity based at least in part on the card/loyalty proxy; and

transmitting the card/loyalty proxy or universal loyalty credential to an associated merchant facilitating a transaction.

6. The method of claim 1, further comprising:

receiving an indication the consumer has performed a predefined activity;

crediting a consumer's account in a loyalty/rewards program based at least in part on the predefined activity;

outputting an indication of the credit to the consumer's mobile device;

receiving an instruction from the consumer to redeem a loyalty/reward credit on behalf of a third party;

determining a loyalty/reward activity based at least in part on the card/loyalty proxy; and

transmitting the card/loyalty proxy to an associated merchant facilitating a transaction.

7. The method of claim 1, further comprising:

receiving an indication that the consumer has arrived at or will arrive at predefined merchant location;

transmitting a respective notification to a point of sale (POS) device associated with the merchant;

based at least in part on the indication, determining consumer identity, merchant identity and/or merchant's loyalty/reward program;

outputting information associated with one or more consumers at the predefined merchant location;

receiving a name or unique code with payment information from at least one consumer;

authenticating the name or unique code;

facilitating payment processing associated with the consumer purchase of a good and/or service from merchant;

receiving payment authorization request from consumer; and

transmitting payment confirmation, offer and/or loyalty/reward credit confirmation to POS device and/or mobile device associated with consumer.

8. The method of claim 1, further comprising:

providing a network link for the merchant to access a loyalty/reward application program;

receiving an indication that the merchant has opted in to an associated loyalty/rewards program;

receiving one or more merchant parameters for a customized merchant loyalty/rewards program; and

generating a downloadable app or application program for the consumer to access the customized merchant loyalty/rewards program.

9. The method of claim 1, further comprising:

receiving an offer at the consumer's mobile device;

determining a plurality of names in a contacts module of the mobile device;

generating a display of the plurality of names on a user interface of the mobile device;

receiving a selection of at least one of the plurality of names at the mobile device;

determining a contact reference for each of the selected names from the contacts module of the mobile device; and

transmitting the offer to each of the selected names at the respective contact reference.

10. The method of claim 1, further comprising:

receiving an offer at the consumer's mobile device;

receiving access information for at least one social networking website;

accessing the at least one social networking website with the access information;

determining a plurality of names from the social networking website, wherein each name is associated with a person affiliated with the consumer on the social networking website;

generating a display of the plurality of names on a user interface of the mobile device;

receiving a selection of at least one of the plurality of names at the mobile device;

determining a contact reference for each of the selected names from the social networking website; and

transmitting the offer to the person associated with each of the respective selected names at the respective contact reference.

11. The method of claim 1, further comprising:

receiving an offer at the consumer's mobile device;

receiving access information for at least one social networking website;

accessing the at least one social networking website with the access information;

determining a plurality of names from the social networking website, wherein each name is associated with a person affiliated with the consumer on the social networking website;

generating a display of the plurality of names on a user interface of the mobile device;

receiving a selection of at least one of the plurality of names at the mobile device;

accessing a page at the social networking website for each of the respective people associated with the selected names; and

posting information associated with the offer on each of the accessed pages of the social networking website.

12. The method of claim 1, further comprising:

receiving a request from a consumer's mobile device to download an application program;

identifying a share received offer program based at least in part on the request;

facilitating access to an application program associated with the share received offer program;

receiving consumer information via the application program associated with the share received offer program;

receiving access information for at least one social networking website via the application program associated with the share received offer program; and

receiving a personal identification number for accessing the application program associated with the share receive offer program.

13. The method of claim 1, further comprising:

receiving a request from the consumer's mobile device to download an application program;

identifying a share received offer program based at least in part on the request;

facilitating access to an application program associated with the share received offer program;

receiving consumer information via the application program associated with the share received offer program;

receiving access information for at least one social networking website via the application program associated with the share received offer program; and

receiving a personal identification number for accessing the application program associated with the share receive offer program.

14. A system for providing a loyalty/reward program, the system comprising:

at least one processor operable to execute computer-executable instructions; and

at least one memory operable to store computer-executable instructions operable to: receive an indication that a consumer has entered a predefined merchant location; transmit a notification to a mobile device associated with the consumer; provide one or more payment tools on a mobile device for the consumer to facilitate a purchase from a merchant associated with the predefined merchant location; generate a loyalty/reward credit for an account associated with the consumer; and receive an instruction from the consumer to redeem loyalty/reward credit for goods and/or service from the merchant.

15. The system of claim 14, wherein the computer-executable instructions are further operable to:

receive a request from a consumer's mobile device to download an application program;

identify a share received offer program based at least in part on the request;

facilitate access to an application program associated with the share received offer program;

receive consumer information via the application program associated with the share received offer program;

receive access information for at least one social networking website via the application program associated with the share received offer program; and

receive a personal identification number for accessing the application program associated with the share receive offer program.

16. The system of claim 14, wherein the computer-executable instructions are further operable to:

provide a network link for the merchant to access a loyalty/reward application program;

receive an indication that the merchant has opted in to an associated loyalty/rewards program;

receive one or more merchant parameters for a customized merchant loyalty/rewards program; and

generate a downloadable app or application program for the consumer to access the customized merchant loyalty/rewards program.

17. The system of claim 14, wherein the computer-executable instructions are further operable to:

receive a code from the consumer's mobile device located at a merchant location;

identify a merchant's loyalty/reward program;

facilitate access to an app or application program associated with the merchant's loyalty/reward program; and

receive consumer information via the app or application program.

18. The system of claim 14, wherein the computer-executable instructions are further operable to:

receive a merchant loyalty/rewards credit from one merchant loyalty/rewards program;

receive other merchant loyalty/rewards credit from at least one other merchant loyalty/rewards program;

determine at least one offer or advertisement based at least in part on the one merchant loyalty/rewards program and the at least one other merchant loyalty/rewards program;

output the at least one offer or advertisement to the consumer's mobile device;

generate or transmit a notification to the consumer's mobile device upon receiving an indication of at least one of the following: the consumer's mobile device is in a predefined location, an earned reward, a reward threshold, an expiring reward or offer, or a third party product and/or service review; and

categorize, organize, rank and/or prioritize two or more merchants and/or associated merchant loyalty/reward programs based at least in part on consumer use, preference, conduct and/or behavior.

19. The system of claim 14, wherein the computer-executable instructions are further operable to:

generate a card/loyalty proxy;

link a merchant and/or affiliate identifier to a payment device via the card/loyalty proxy;

link multiple merchant and/or affiliate identifiers to the payment device via the card/loyalty proxy;

associate multiple merchant and/or affiliate identifiers with a universal loyalty credential;

receive an indication that a linked payment device or universal loyalty credential is being used at a point of sale (POS) device, for an online transaction, or via a mobile device transaction;

determine a loyalty/reward activity based at least in part on the card/loyalty proxy; and

transmit the card/loyalty proxy or universal loyalty credential to an associated merchant facilitating a transaction.