US20140074605A1 - Systems and methods for facilitating purchases at a gas station via mobile commerce - Google Patents

Abstract

Systems and methods are provided for facilitating purchases at a gas station via mobile commerce. A merchant system can receive an indication that a consumer is at or near the merchant location and can check the consumer into the location. A mobile application can launch and provide the merchant system with consumer identification information. While a consumer makes a purchase at a location, the merchant system can select advertising to provide to the consumer on the consumer mobile device to convince the consumer to make additional purchases at the merchant location. In addition, the consumer can make additional purchases from the merchant system while, for example, pumping gas and can be provided with a code or other identify to provide the consumer with access to those additional products once they have completed the gas purchase.

Description

RELATED APPLICATIONS
• This application claims priority to U.S. Provisional Patent Application No. 61/699,728, titled “Systems and Methods for Implementing Mobile Commerce,” filed on Sep. 11, 2012, and to U.S. Provisional Patent Application No. 61/799,676, titled “Systems and Methods for Implementing Mobile Commerce,” filed on Mar. 15, 2013, the entire contents of both of which are hereby incorporated herein by reference for all purposes.
FIELD OF THE DISCLOSURE
• The disclosure generally relates to mobile commerce, and more particularly, to systems and methods for facilitating purchases at a gas station via mobile commerce.
BACKGROUND
• Commerce related to gas stations has changed significantly over the years. In the past, a typical gas station may have had little to offer customers other than gasoline for purchase. However, conventional gas stations often provide a wide variety of products and services for their customers, including significant food, beverage, and other miscellaneous offerings inside a convenience-style store at the gas station. Additionally, services such as car washes and detailing may be provided by the gas station merchant. Providing this expanded range of goods and services can greatly increase the revenue opportunities for the merchant. Another offering provided by many gas station merchants to provide greater convenience to their customers is the option to pay for gas at the pump, thereby eliminating the need for the customer to actually go inside to pay for their fuel purchase. However, the ability of a customer to pay at the pump reduces the likelihood that the customer will make other purchases at the gas station. These other purchases typically have a higher profit margin for the gas station merchant. Finding ways to entice customers into making additional purchases of goods and services while purchasing gasoline will increase the potential revenue for gas station merchants.
BRIEF DESCRIPTION OF THE DISCLOSURE
• The disclosure relates to systems and methods for facilitating purchases at a gas station via mobile commerce.
• In one embodiment, a method may be provided. The method may include a merchant device including one or more processors transmitting to the consumer mobile device, a request for a selection of a product or service for purchase from the merchant. The merchant device may receive, from the consumer mobile device, a selection of at least one product or service. The merchant device may receive, from the consumer mobile device, a selected payment method for the selected at least one product or service. The merchant device may process a purchase transaction for the selected at least one product or service with the selected payment method. The merchant device may transmit, to the consumer mobile device, a notification of approval of the purchase transaction. The merchant device may facilitate access to the selected at least one product or service in response to the approval of the purchase transaction.
• In one aspect of the embodiment, the merchant device may receive an indication that a consumer is within a predefined distance of a merchant location. The merchant device may receive, from the consumer mobile device, consumer identification information for the consumer.
• In one aspect of the embodiment, the merchant device may determine a purchase history for the consumer based at least in part on the identification information for the consumer. The merchant device may select at least one advertisement based at least in part on the purchase history of the consumer. The merchant device may transmit, to the consumer mobile device, the selected at least one advertisement for display on the consumer mobile device.
• In one aspect of the embodiment, the merchant device may determine demographic information for the consumer based at least in part on the consumer identification information. The merchant device may select at least one advertisement based at least in part on the demographic information for the consumer. The merchant device may transmit, to the consumer mobile device, the selected at least one advertisement for display on the consumer mobile device.
• In one aspect of the embodiment, the request for the selection of the product or service for purchase comprises a request for identification of a pump from which the consumer wants to pump gas, receiving the selection of the at least one product or service comprises an identification of gas pump at the merchant location, and facilitating access to the selected at least one product or service include the merchant device may transmit a signal to the identified gas pump to unlock the gas pump.
• In one aspect of the embodiment, the selected payment method includes payment card transaction information. The merchant device may determine consumer identification information based at least in part on the payment card transaction information. The merchant device may determine contact information for a mobile device of the consumer based at least in part on the determined consumer identification information. The merchant device may transmit a notification to the mobile device of receipt of at least one of a loyalty reward, loyalty points, or a coupon based at least in part on a completion of the purchase transaction.
• In one aspect of the embodiment, the merchant device may receive, from a consumer at an input communicably coupled to the merchant device, a phone number associated with the consumer. The merchant device may determine the consumer mobile device associated with the phone number. The merchant device may transmit a notification to the consumer mobile device of receipt of at least one of a loyalty reward, loyalty points, or a coupon based at least in part on a completion of the purchase transaction.
• In one aspect of the embodiment, a scannable code may be provided at the merchant location. The merchant device may receive the code from a consumer mobile device. The merchant device may identify, a gas station mobile payment application program based at least in part on the received code. The merchant device may facilitate access to the gas station mobile payment application program. The merchant device may receive consumer identification information via the gas station mobile payment application program.
• In one aspect of the embodiment, the merchant device may transmit an access code to the consumer mobile device, the access code providing access to the selected at least one product or service.
• In one aspect of the embodiment, the selected at least one product or service includes a car wash. The merchant device may transmit, to the consumer mobile device, an access code, the access code facilitating the initiation of the car wash. The merchant device may receive, from the consumer mobile device, the access code. The merchant device may be communicably coupled to the car wash. The merchant device may initiate, the car wash in response to receiving the access code at the merchant device.
• In one aspect of the embodiment, the selected payment method includes payment card transaction information. The merchant device may determine consumer identification information for the consumer based at least in part on the payment card transaction information. The merchant device may determine a demographic characteristic for the consumer based at least in part on the consumer identification information. The merchant device may select at least one advertisement based at least in part on the demographic characteristic of the consumer. The merchant device may transmit, to the consumer mobile device, the selected at least one advertisement for display on the consumer mobile device.
• In one aspect of the embodiment, the selected payment method may include payment card transaction information. The merchant device may determine consumer identification information for the consumer based at least in part on the payment card transaction information. The merchant device may determine a purchase history for the consumer at the merchant based at least in part on the consumer identification information. The merchant device may select at least one advertisement based at least in part on the purchase history of the consumer at the merchant. The merchant device may transmit, to the consumer mobile device, the selected at least one advertisement for display on the consumer mobile device.
• In one embodiment, a system may be provided. The system may include at least one memory storing computer-executable instructions and at least one processor, wherein the at least one processor may be configured to access the at least one memory and to execute the computer executable instructions to direct communication of a request for a selection of a product or service for purchase from the merchant to a consumer mobile device; receive, from the consumer mobile device, a selection of at least one product or service; receive, from the consumer mobile device, a selected payment method for the selected at least one product or service; facilitate the processing of a purchase transaction for the selected at least one product or service with the selected payment method; direct communication of a notification of approval of the purchase transaction to the consumer mobile device; and facilitate access to the selected at least one product or service in response to the approval of the purchase transaction.
• In one aspect of the embodiment, the at least one processor may be further configured to execute the computer-executable instructions to receive an indication that a consumer is within a predefined distance of a merchant location; and receive, from the consumer mobile device, consumer identification information for the consumer.
• In one aspect of the embodiment, the at least one processor may be further configured to execute the computer-executable instructions to determine a purchase history for the consumer based at least in part on the identification information for the consumer; select at least one advertisement based at least in part on the purchase history of the consumer; and direct communication of the selected at least one advertisement to the consumer mobile device for display on the consumer mobile device.
• In one aspect of the embodiment, the at least one processor may be further configured to execute the computer-executable instructions to determine demographic information for the consumer based at least in part on the consumer identification information; select at least one advertisement based at least in part on the demographic information for the consumer; and direct communication of the selected at least one advertisement to the consumer mobile device for display on the consumer mobile device.
• In one aspect of the embodiment, the request for the selection of the product or service for purchase includes a request for identification of a pump from which the consumer wants to pump gas, receiving the selection of the at least one product or service includes an identification of gas pump at the merchant location, and facilitating access to the selected at least one product or service includes directing communication of a signal to the identified gas pump to unlock the gas pump.
• In one aspect of the embodiment, the selected payment method includes payment card transaction information. The at least one processor may be further configured to execute the computer-executable instructions to determine consumer identification information based at least in part on the payment card transaction information; determine contact information for a mobile device of the consumer based at least in part on the determined consumer identification information; and direct communication of a notification to the mobile device of receipt of at least one of a loyalty reward, loyalty points, or a coupon based at least in part on a completion of the purchase transaction.
• In one aspect of the embodiment, the at least one processor may be further configured to execute the computer-executable instructions to receive, from a consumer at an input communicably coupled to the merchant device, a phone number associated with the consumer; determine the consumer mobile device associated with the phone number; and direct communication of a notification to the consumer mobile device of receipt of at least one of a loyalty reward, loyalty points, or a coupon based at least in part on a completion of the purchase transaction.
• In one aspect of the embodiment, a scannable code may be provided at a merchant location. The at least one processor may be further configured to execute the computer-executable instructions to receive the code from a consumer mobile device; identify a gas station mobile payment application program based at least in part on the received code; facilitate access to the gas station mobile payment application program; and receive consumer identification information via the gas station mobile payment application program.
• In one aspect of the embodiment, the at least one processor may be further configured to execute the computer-executable instructions to direct communication of an access code to the consumer mobile device, the access code providing access to the selected at least one product or service.
• In one aspect of the embodiment, the at least one processor may be further configured to execute the computer-executable instructions to direct communication of an access code to the consumer mobile device, the access code facilitating the initiation of the car wash; receive, from the consumer mobile device, the access code, wherein the merchant device is communicably coupled to the car wash; and initiate the car wash in response to receiving the access code at the merchant device.
• In one aspect of the embodiment, the selected payment method may include payment card transaction information. The at least one processor may be further configured to execute the computer-executable instructions to determine consumer identification information for the consumer based at least in part on the payment card transaction information; determine a demographic characteristic for the consumer based at least in part on the consumer identification information; select at least one advertisement based at least in part on the demographic characteristic of the consumer; and direct communication of the selected at least one advertisement to the consumer mobile device for display on the consumer mobile device.
• In one aspect of the embodiment, the selected payment method may include payment card transaction information. The at least one processor is further configured to execute the computer-executable instructions to determine consumer identification information for the consumer based at least in part on the payment card transaction information; determine a purchase history for the consumer at the merchant based at least in part on the consumer identification information; select at least one advertisement based at least in part on the purchase history of the consumer at the merchant; and direct communication of the selected at least one advertisement to the consumer mobile device for display on the consumer mobile device.
BRIEF DESCRIPTION OF THE DRAWINGS
• Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
• FIG. 1 illustrates an example system for implementing mobile commerce according to certain example embodiments of the disclosure.
• FIG. 2 illustrates an example mobile commerce program application or module according to certain example embodiments of the disclosure.
• FIG. 3 is a flow chart illustrating an example method for creating a mobile commerce application program according to certain example embodiments of the disclosure.
• FIG. 4 is a flow chart illustrating an example method for setting up a consumer account on a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 5 is a flow chart illustrating an example method for presenting advertising and promotions on a consumer mobile device during a pay at the pump gasoline purchase according to certain example embodiments of the disclosure.
• FIG. 6 is a flow chart illustrating an example method for presenting targeted advertising and promotions on a consumer mobile device during a gasoline purchase according to certain example embodiments of the disclosure.
• FIG. 7 is a flow chart illustrating another example method for presenting targeted advertising and promotions on a consumer mobile device during a gasoline purchase according to certain example embodiments of the disclosure.
• FIGS. 8 and 9 illustrate example displays of a user interface presented on a consumer mobile device to communicate notices of offers or promotions during a gasoline purchase according to certain example embodiments of the disclosure.
• FIG. 10 is a flow chart illustrating another example method for creating a mobile commerce application program according to certain example embodiments of the disclosure.
• FIG. 11 is a flow chart illustrating another example method for setting up a consumer account on a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 12 is a flow chart illustrating an example method for providing information and access to products and services of a merchant at a merchant location via a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 13 illustrate example displays of a user interface presented on a consumer mobile device to communicate information regarding products and services and to provide access to products and services of a merchant at a merchant location according to certain example embodiments of the disclosure.
• FIG. 14 is a flow chart illustrating another example method for creating a mobile commerce application program according to certain example embodiments of the disclosure.
• FIG. 15 is a flow chart illustrating another example method for setting up a consumer account on a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 16 is a flow chart illustrating an example method for providing information and access to products and services of a merchant at a merchant location via a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 17 is a flow chart illustrating an example method for generating and displaying targeted advertising to a consumer associated with a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 18 is a flow chart illustrating another example method for generating and displaying targeted advertising to a consumer associated with a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 19 is a flow chart illustrating yet another example method for generating and displaying targeted advertising to a consumer associated with a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 20 is a flow chart illustrating another example method for generating and displaying targeted advertising to a consumer associated with a consumer mobile device according to certain example embodiments of the disclosure.
• FIG. 21 illustrates an example display of a user interface presented on a consumer mobile device to communicate advertising regarding products and services of a merchant at a merchant location while the consumer is at the merchant location according to certain example embodiments of the disclosure.
DETAILED DESCRIPTION
• The present disclosure is directed to systems and methods facilitating purchases at a gas station via mobile commerce. Certain example embodiments of the disclosure will now be described more fully hereinafter with accompanying drawings and corresponding description inFIGS. 1-21. 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 present disclosure relates to systems and methods for facilitating purchases at a gas station via mobile commerce. In one example implementation, a merchant, such as a gas station merchant, can create a mobile commerce application program, also known as a mobile app, mobile wallet or wallet app. A consumer can download the mobile commerce application program onto the consumer's mobile device and store certain personal and payment method information in association with the mobile commerce application program. When the consumer's mobile device is within the vicinity of the merchant location, the mobile commerce application program can either launch automatically or the consumer can launch the application. The mobile commerce application program can transmit location and personal information about the consumer to a merchant system or server and can “check-in” the consumer at the merchant location. The merchant system can provide a list of goods and services available to the consumer on the consumer's mobile device. The consumer can select the desired goods and/or services and can select a payment method via the mobile commerce application program. The merchant system can authorize the purchase of the selected goods and/or services, can transmit a notification of authorization to the consumer's mobile device via the mobile commerce application program, and can provide the consumer with access to the purchased goods and/or services. The merchant system can identify advertisements and transmit those advertisements to the consumer's mobile device for display via the mobile commerce application program. For example, the advertisements can be presented while the consumer is receiving the requested goods and/or services (e.g., filling up a car with gas). Upon receipt of the goods and services, the merchant system can generate and transmit an electronic receipt to the consumer's mobile device and can transmit notification and/or download to the consumer's mobile device any loyalty rewards, coupons, and/or points earned based on the purchase via the mobile commerce application program.
• In another example implementation, a consumer can select one or more products and/or services for purchase and can present a payment card (e.g., a credit card, debit card, gift card, discount card, or pre-paid card) at a merchant point of sale (POS) device. The consumer's payment card information can be transmitted to a server. The server can determine the consumer associated with the payment card and mobile device associated with the consumer. The merchant system can identify demographic or purchase history information for the consumer and can select one or more advertisements based on the demographic or purchase history. The merchant system can transmit these targeted advertisements to the consumer's mobile device for display via the mobile commerce application program or via email or text message. Upon completion of the purchase, the merchant system can transmit notification and/or download to the consumer's mobile device any loyalty rewards, coupons, and/or points earned based on the purchase via the mobile commerce application program.
• In another example implementation, a consumer can select one or more products and/or services for purchase and can present a payment card (e.g., a credit card, debit card, gift card, discount card, or pre-paid card) or cash to complete the purchase. The consumer can also provide their phone number either to an employee of the merchant or directly into a merchant POS device. The consumer's phone number can be transmitted to a server. The server can determine the consumer associated with the phone number and mobile device associated with the consumer. The merchant system can identify demographic or purchase history information for the consumer and can select one or more advertisements based on the demographic or purchase history. The merchant system can transmit these targeted advertisements to the consumer's mobile device for display via the mobile commerce application program or via email or text message. Upon completion of the purchase, the merchant system can transmit notification and/or download to the consumer's mobile device any loyalty rewards, coupons, and/or points earned based on the purchase via the mobile commerce application program.
• In another example implementation, a merchant, such as a gas station merchant, can create a mobile commerce application program. A consumer can download the mobile commerce application program onto the consumer's mobile device and store certain personal and payment method information in association with the mobile commerce application program. When the consumer's mobile device is within the vicinity of the merchant location, the mobile commerce application program can either launch automatically or the consumer can launch the application. The mobile commerce application program can transmit location and personal information about the consumer to a merchant system or server and can “check-in” the consumer at the merchant location. The merchant system can provide a list of goods and services available to the consumer on the consumer's mobile device. The consumer can select the desired goods and/or services they wish to purchase via the mobile commerce application program. The merchant system can determine pricing based on the selected goods and/or services and can transmit the pricing for display on the consumer's mobile device via the mobile commerce application program. The mobile commerce application program can display the pricing information and retrieve and display one or more payment method options for the consumer on the consumer's mobile device. The consumer can select the desired payment option, which can be transmitted, along with the selected goods and/or services to the merchant system. The merchant system can authorize the purchase and transmit notification of the authorization to the consumer's mobile device via the mobile commerce application program. The merchant system can also provide access to the selected goods and/or services and can transmit advertising, an electronic receipt, and notification of and/or download to the consumer's mobile device any loyalty rewards, coupons, and/or points earned based on the purchase via the mobile commerce application program.
• In another example implementation, a merchant, such as a gas station merchant, can create a mobile commerce application program. A consumer can download the mobile commerce application program onto the consumer's mobile device and store certain personal and payment method information in association with the mobile commerce application program. When the consumer's mobile device is within the vicinity of the merchant location, the mobile commerce application program can either launch automatically or the consumer can launch the application. The mobile commerce application program can transmit location information for the consumer to a merchant system or server and can “check-in” the consumer at the merchant location. The merchant system can provide a list of goods and/or services available to the consumer on the consumer's mobile device via the mobile commerce application program. The consumer can select the desired goods and/or services and can select a payment method via the mobile commerce application program, which can be transmitted along with identifying information of the consumer to the merchant system to complete the purchase. The merchant system can authorize the purchase of the selected goods and/or services, can transmit a notification of authorization to the consumer's mobile device via the mobile commerce application program, and can provide the consumer with access to the purchased goods and/or services. The merchant system can also identify targeted advertisements for the consumer based on the consumer's demographic information or prior purchase history with this or other merchants and can transmit those advertisements to the consumer's mobile device for display via the mobile commerce application program. For example, the targeted advertisements can be presented while the consumer is receiving the requested goods and/or services (e.g., filling up a car with gas). Upon receipt of the goods and services, the merchant system can generate and transmit an electronic receipt to the consumer's mobile device and can transmit notification and/or download to the consumer's mobile device any loyalty rewards, coupons, and/or points earned based on the purchase via the mobile commerce application program.
• In the above implementations and other embodiments described herein, a mobile commerce application program, sometimes referred to as a mobile app or 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 inFIG. 1, and each may have similar or different functionality, such as described inFIG. 2, according to various example embodiments and implementations as described herein.
CERTAIN EXAMPLE IMPLEMENTATIONS AND EMBODIMENTS
• An example architecture or environment for asystem100 according various example embodiments of the disclosure is shown in and described with respect toFIG. 1. A mobile commerce application program or module, such as102, can be stored in memory104 at aserver device106. In certain embodiments, a mobile commerce application program or module, such as108, can be stored inmemory110 at amerchant system computer112 or associatedmerchant device114. In certain embodiments, a mobile commerce application program or module, such as116(1), can be stored in memory118(1) at a mobile device120(1) associated with a consumer122(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 inFIG. 1, thesystem100 may include or otherwise support one or moremerchant system computers112 and/or associatedmerchant devices114, one or more consumer or mobile devices120(1)-120(N), one or more servertransaction processing systems106, and one or more issuer orfinancial institution systems124. A wide variety of different types of consumer or mobile devices120(1)-120(N) may be provided or otherwise supported, such as consumer computers and/or mobile communication devices. As desired, thesystem100 may provide or otherwise support a wide variety of other entities associated with payment transactions, such as one or more servertransaction processing systems106. Any number of suitable networks and/or communication channels, such as the illustratednetworks126, may facilitate communication between various components of thesystem100.
• With reference toFIG. 1, any number ofmerchant system computers112 and/or associatedmerchant devices114 may be provided or otherwise supported. In certain example embodiments, thesemerchant system computers112 and/or associatedmerchant devices114 may include one or more point-of-sale (POS) devices or terminals. As desired, eachmerchant system computer112 and/or associatedmerchant device114 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.
• Amerchant system computer112 and/or associatedmerchant device114 may be any suitable device that facilitates purchase transactions, such as those in retail establishments, e-commerce and/or mobile transactions. In operation, themerchant system computer112 and/or associatedmerchant device114 may utilize one ormore processors128 to execute computer-readable instructions that facilitate the hosting of one or more mobile commerce application program services, the receipt of purchase transaction requests, the processing of payment transactions, and/or the identification and transmission of advertising, such as targeted advertising to a mobile device. As a result of executing these computer-readable instructions, a special purpose computer or particular machine may be formed that facilitates the purchase transactions.
• In addition to having one ormore processors128, themerchant system computer112 and/or associatedmerchant device114 may further include and/or be associated with one ormore memory devices110, input/output (“I/O”) interface(s)130, network interface(s), and/orlocation services132. Thememory110 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. Thememory110 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 mobilecommerce application program108. The data files may include any suitable data that facilitates the operation of themerchant system computer112 and/or associatedmerchant device114, and/or interaction of themerchant system computer112 and/or associated merchant device115 with one or more other components (e.g., one or more one or more consumer or mobile devices120(1)-120(N), one or more servertransaction processing systems106, one or more merchant acquiring platforms, one or more issuer systems, one or morefinancial institution systems124, etc.) of thesystem100. For example, the data files may include information associated with one or more websites134 (hosted by either a third-party and/or merchant), webpages, inventory information associated with available products and/or services, acquiring platform information, service provider information, merchant-specific information (such as the number of fuel dispensing pumps and the products and services offered by the merchant), information associated with the generation of payment transactions, customer information, demographic data, information associated with the identification and transmission of advertising, such as targeted advertising, and/or routing information for payment transactions.
• The OS may be any 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 any currently known or future developed operating system including, but 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 themerchant system computer112 and/or associatedmerchant device114, and one or more external devices, such as the consumer or mobile devices120(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 as134, 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 devices120(1)-120(N).
• The transaction modules or applications, such as the mobilecommerce application program108, 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 device120(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 advertising requests. One example of the operations that may be performed by a transaction module or mobilecommerce application program108 and/or themerchant system computer112 and/or associatedmerchant device114 is described in greater detail below with reference toFIG. 2.
• With continued reference to themerchant system computer112 and/or associatedmerchant device114, the one or more I/O interfaces130 may facilitate communication between themerchant system computer112 and/or associatedmerchant device114 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 themerchant system computer112 and/or associatedmerchant device114. The one or more network interfaces may facilitate connection of themerchant system computer112 and/or associatedmerchant device114 to one or more suitable networks, such as126, and/or communication links. In this regard, themerchant system computer112 and/or associatedmerchant device114 may receive and/or communicate information to other components of thesystem100, such as the consumer or mobile devices, for example120(1)-120(N), the servertransaction processing systems106, and/or the issuer orfinancial institution systems124.
• In certain example embodiments, amerchant system computer112 and/or associatedmerchant device114 can be associated with amerchant location136, such as a retail store (e.g., gas station) or “bricks and mortar”-type establishment. Themerchant location136 may include acode138, such as a QR code, bar code, or other machine readable code, wherein consumers can utilize a respective consumer or mobile device120(1)-120(N) to scan or read the code to check-in to a merchant or to obtain information associated with a merchant, such as product pricing information. Alternatively, themerchant system computer112 and/or the associated merchant device may include or be communicably coupled to geolocation devices that are operatively coupled to one ormore location services132 for sensing and identifying customer mobile devices that are within a predetermined distance of the merchant location.
• Additionally, with continued reference toFIG. 1, any number of consumer or mobile devices120(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, etc.), etc. According to an example aspect of the disclosure, a consumer or mobile device, such as120(1) may be a suitable device that is capable of interaction with other components of thesystem100 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 as134, including those hosted by the merchant system computer, such as112, or themerchant system112 itself and identify products and/or services to be purchased, request a purchase and/or interact with themerchant system computer112,merchant system device114, and/or other components of the system100 (e.g., the servertransaction processing system106, etc.) during the completion of a payment transaction. In one example embodiment, a mobile device, such as120(1), may be utilized to request one or more products and/or services in a payment transaction, provide consumer identification information, and/or to provide validation information during the processing of the payment transaction.
• As desired, a consumer or mobile device, such as120(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 as120(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 device120(1), the mobile device120(1) may utilize one or more processors140(1) to execute computer-readable instructions that facilitate the general operation of the mobile device120(1) (e.g., call functionality, etc.) and/or communication with amerchant system computer112,merchant system device114, and/or other components of the system100 (e.g., the server transaction processing system106) for product selection and payment transaction purposes, for providing access to purchased products, as well as for the receipt of merchant selected advertising, loyalty awards, coupons and promotional information. 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 transactions, provides access to purchased products, and/or provides for the receipt of merchant selected advertising, loyalty awards, coupons and promotional information.
• In addition to having one or more processors, the mobile device, such as120(1)-120(N), may further include and/or be associated with one or more memory devices118(1)-118(N), input/output (“I/O”) interfaces142(1)-142(N), network interfaces, and/or location services144(1)-144(N). The memory118(1)-118(N) may be any computer-readable medium, coupled to the one or more processors140(1)-140(N), such as random access memory (“RAM”), read-only memory (“ROM”), and/or removable storage devices. The memory118(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 program116(1)-116(N). In certain example embodiments, a mobile device, such as120(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 memory118(1) and/or included as a separate component of the mobile device120(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 program116(1), may be stored on a secure element. The transaction modules may be invoked by other components of the mobile device120(1) and/or by one or more other components of thesystem100, such as themerchant system computer112,merchant system device114, and/or the servertransaction processing system106.
• The data files may include any suitable data that facilitates the operation of the mobile device, such as120(1), and/or interaction of the mobile device120(1) with one or more other components (e.g., amerchant system computer112,merchant system device114, a servertransaction processing system106, etc.) of thesystem100. 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 as120(1), as well as the execution of other program modules. For example, the OS may be any currently known or future developed operating system including, but not limited to, a suitable mobile OS or a specially designed operating system. As desired, the mobile device120(1) may also include one or more suitable browser applications that facilitate the access of one or more webpages hosted by themerchant system computer112, and/or third-party or merchant web sites, such as134.
• The transaction modules may include one or more suitable software modules and/or applications configured to facilitate purchase transactions, such as payment transactions, facilitate the receipt and display of advertising, loyalty awards, coupons and/or promotional information, and/or provides access to purchased products on behalf of the mobile device, such as120(1). In certain embodiments, a transaction module or mobile commerce application program, such as116(1), may also facilitate communication with a server transaction processing system, such as106, or a trusted service manager. A wide variety of suitable techniques may be utilized to install a transaction module on the mobile device, such as120(1). For example, a transaction module may be provisioned to the mobile device120(1) by a servertransaction processing system106 and/or by an issuer orfinancial institution system124. 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 as122(1) may be prompted to enter an mPIN, such as a multi-character and/or multi-numeral code, to an associated mobile device, such as120(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 as124, or an issuer system associated with an issuer of a payment account (e.g., a credit account, a debit account, a pre-paid card account, a gift card 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 transaction. For example, the transaction module may be invoked by amerchant system computer112,merchant system device114, or by a servertransaction processing system106 at the request of themerchant system computer112 and/ormerchant system device114. In certain example embodiments, the transaction module may be invoked following a consumer request to conduct a payment transaction and the identification of the mobile device, such as120(1), by themerchant system computer112,merchant system device114, or servertransaction processing system106. Following the invocation of the transaction module, a request for validation data and/or payment 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 as122(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 themerchant system computer112,merchant system device114, or servertransaction processing system106. 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 consumer122(1), an indication that the entered mPIN was authenticated by the mobile device120(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 as124, for authentication and/or risk analysis purposes.
• Examples of the operations of the transaction module and/or the mobile device120(1)-120(N) are described in greater detail below with reference to the other figures.
• The one or more I/O interfaces, such as142(1)-142(N), may facilitate communication between the mobile device, such as120(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 device120(1). Further, the one or more network interfaces may facilitate connection of the mobile device, such as120(1), to one or more suitable networks, for example, the network(s)126 illustrated inFIG. 1. In this regard, the mobile device, such as120(1), may receive and/or communicate information to other components of thesystem100.
• With continued reference toFIG. 1, as desired in various embodiments, any number of server transaction processing systems, such as106, may be provided or otherwise supported. A servertransaction processing system106 may facilitate the backend processing of a purchase transaction, such as a payment transaction, the identification of a consumer's mobile device120(1) based on consumer identification information, demographic and/or purchase history information for the consumer associated with the consumer mobile device120(1) and/or the identification of advertising based on the demographic or purchase history information for the consumer. In certain example embodiments, an issuer system may include similar components as those discussed above for themerchant system computer112 and/ormerchant system device114. For example, servertransaction processing system106 may include any number ofprocessors146, memories, I/O interfaces148, and/or network interfaces. In certain example embodiments, a servertransaction processing system106 can include one or more transaction modules, such as a mobilecommerce application program102 and/or a social networkintegration program application150. In any instance, the transaction modules can facilitate communications and/or interactions with any number of consumer or mobile devices such as120(1)-120(N), merchant computer systems such as112,merchant computer devices114,data stores151, third-party websites such as134, and financial institution systems such as124. In certain embodiments, a service transaction processing system, such as106, can host a social network integration program application, such as150, 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 data152 on a third party or merchant website, such as134.
• Furthermore, as desired, a server transaction processing system, such as106, may provide a wide variety of transaction module provisioning services. Additionally, a server transaction processing system, such as106, may provide a wide variety of transaction-related and/or value added services (“VAS”) in association with transactions, such as targeted advertising services, 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 example embodiments, a server transaction processing system, such as106, may include similar components as those discussed above for the merchant system computer, such as112, and/or merchant system device, such as114. For example, a server transaction processing system, such as106, may include any number of processors, memories, I/O interfaces, and/or network interfaces.
• With continued reference toFIG. 1, as desired in various example embodiments, any number of issuer or financial institution systems, such as124, may be provided or otherwise supported. An issuer or financial institution system, such as124, may facilitate the backend processing of a payment transaction, such as a payment for one or more products and/or services selected by an consumer at a merchant location. For example, an issuer or financial institution system, such as124, may host a payment processing application program, such as154, or module to facilitate the approval, authentication, and/or settlement of a payment transaction. In certain example embodiments, a payment transaction may be routed to an issuer or financial institution system, such as124, via a suitable transaction network (e.g., a debit network, a credit network, etc.), and the issuer or financial institution system, such as124, may evaluate the payment transaction via the payment processing application program, such as154, or module. An approval or rejection of the payment transaction may then be output for communication to a merchant system computer, such as112, and/ormerchant system device114. The issuer or financial institution system, such as124, may then facilitate the settlement of the payment transaction. In certain embodiments, an issuer or financial institution system, such as124, may include similar components as those discussed above for themerchant system computer112 and/ormerchant system device114. For example, an issuer or financial institution system, such as124, may include any number ofprocessors156, memories158, I/O interfaces160, and/or network interfaces. In certain example embodiments of the disclosure, an issuer or financial institution system, such as124, may receive validation information in association with a purchase a transaction.
• A wide variety of suitable networks, individually and/or collectively shown as126 inFIG. 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.
• Thesystem100 shown in and described with respect toFIG. 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 inFIG. 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 mobilecommerce application program200, similar to the mobilecommerce application programs102,108, and116(1)-116(N) inFIG. 1, that can operate with respect to thesystem100 shown inFIG. 1. The mobilecommerce application program200 shown inFIG. 2 can include, for example, a loyalty/rewards module202, a check-in-to-pay module204, aninterruptive alert module206, a share redeemedoffer module208, a notification ormessaging module210, a restaurantmobile payment module212, a check-in-to-pay atQSR module214, a split thebill module216, alifecycle shopping module218, a linkingtransaction module220, a mobiledevice login module222, abill payment module224, a multi-consumerremote payment module226, aninstant issuance module228, a check-in to pumpgas module230, a buycar wash module232, a drive consumer insidemodule234, a tokenization module236, and acode generation module238. Some or all of the modules202-238 are described herein with respect to certain mobile commerce functionality, associated processes, and features.FIGS. 3-21 illustrate certain processes associated with some or all of the modules comprising the example mobilecommerce application program200 inFIG. 2. While the various modules202-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.
Check in to Pump Gas
• In some instances, consumers desire to purchase gas and/or other goods and services using a consumer mobile device, without having to use the merchant's POS device directly. Certain example embodiments of the disclosure can provide systems and processes for facilitating the purchasing of gas and other products from a merchant with a mobile device or other client device. The methods can be implemented by way of a consumer mobile device or other client device. For example,FIGS. 3-9 illustrateexample methods300,400,500,600,700,800, and900 for remotely accessing and paying for products or services from a merchant according to certain example embodiments of the disclosure. The following methods are described with reference to a merchant that is a gas station or similar convenience-type store. However, the example method is not so limited and can be applied to any merchant irrespective of their type of business to provide a way for payment of goods and/or services using a mobile phone or other client device of a consumer.
• FIG. 3 is a flow chart illustrating an example method for creating a mobile commerce application program according to certain example embodiments of the disclosure. Various operations of the methods described below can be performed by the system components described above and shown inFIGS. 1 and 2. With reference now toFIGS. 1-3, theexample method300 can begin atblock305, where a network link is provided for access by a merchant (e.g., via amerchant system112 or device) to a hosted website or payment application program. For example, amerchant system112 may be provided access to a mobilecommerce application program102, which may include abill payment module224. In one example, by way of a client device, such as amerchant system112, a merchant can link via thenetwork126 to thebill payment module224 of the mobilecommerce application program102 on the servertransaction processing system106 to configure a customized payment program.
• Inblock310, one or more templates and/or user interfaces are presented to prompt the merchant for payment parameters. For example, thebill payment module224 may generate or otherwise present to the merchant via thenetwork126 at the merchant system112 a series of templates or predefined user interfaces. Inblock315, merchant parameters for an opt-in mobile payment program are received from the merchant. For instance, a hosted website orbill payment module224 on the servertransaction processing system106 can implement a set of computer-executable instructions to enable an opt-in mobile payment program. When prompted, the merchant, via themerchant system112 can select one or more parameters for a payment program, such as payment methods that can be used, any minimum payment requirements associated with one or more of the payment methods (e.g., minimum amount for use of a credit card, debit card, pre-paid card, gift card, or other stored value card), any additional fees that will be added to a transaction if certain payment methods are used (e.g., additional fees for use of a credit card, debit card, pre-paid card, stored value card, or gift card), and any additional information that will need to be provided by a consumer when using particular payment methods.
• Inblock320, a logo, other trademark, trade name, or other business identifier for the merchant can be received for inclusion in the opt-in mobile payment program. For example, when prompted, the merchant can upload a business logo from themerchant system112 to thebill payment module224 at the servertransaction processing system106 via thenetwork126. Inblock325, a downloadable mobile commerce application program116 for use by a consumer can be generated. For instance, after the merchant inputs the business logo and parameters for a payment program, thebill payment module224 or hostedwebsite134 can execute a set of computer-executable instructions to implement the merchant's payment program, such as offering the program as a consumer downloadable mobile commerce application program116 or app in a mobile application store orwebsite134. In some example embodiments, the mobile commerce application program116 may be branded with the merchant's logo and/or name. In some example embodiments, the mobile commerce application program116 may be the same application program for some or all merchants, or those merchants within a single classification or geographical location. In the manner described above, various merchants, regardless of size, can adopt and implement abill payment module224 as a part of a mobile payment application program116.
• FIG. 4 is a flow chart illustrating an example method for setting up a consumer account on a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2, and4, theexample method400 can begin atblock405 by receiving a request to download a merchant mobile payment program, such as the mobile commerce application program116 that includes a check-in to pumpgas module230. The consumermobile device120 or other client device can communicate, with the servertransaction processing system106 or an app store via thenetwork126, some or all the information associated with a scanned QR code, bar code, any other type of one-dimensional or two-dimensional code, information provided via near-filed communication, or other code or name input from the consumer at the consumermobile device120.
• Inblock410, a mobile commerce application program116, such as a merchant mobile payment program, can be transmitted to and access can be provided to the consumermobile device120. Using the information received in the previous block, the servertransaction processing system106 can identify the merchant's mobile payment program116, and download the consumer downloadable mobile commerce application program116 to the consumermobile device120 or other client device. In one example embodiment, the mobile commerce application program116, including the check-in to pumpgas module230, can be transmitted via thenetwork126 from the mobilecommerce application program102 at the servertransaction processing system106 to the consumermobile device120 for download. For example, by way of a consumermobile device120 or other client device, such as a laptop computer or tablet, a consumer can download a merchant-branded mobile commerce application program116 that includes the check-in to pumpgas module230 to the consumermobile device120 or other client device.
• Inblock415, the mobile commerce application program116 can generate and display on the consumermobile device120 one or more account set-up prompts. For example, the prompts can include one or more fields for receiving consumer identification information and any other types of information known to the consumer for creating a personalized account for the check-in to pumpmodule230. Inblock420, one or more inputs associated with the set-up prompts can be received at the I/O interface142 of the consumermobile device120. For example, when prompted, the consumer can create an account and input certain consumer identification information to the mobile commerce application program116, such as personal information including, but not limited to, the consumer's name, address, social security number, mobile telephone number, email address, and messaging address. Inblock425, consumer payment method information can be received from the consumer at the consumermobile device120. For example, the payment method information may include credit card account information, debit card account information, pre-paid card account information, stored value card account information, gift card account information, checking account information, and/or savings account information. This payment method information may be previously stored or accessible via an authorization token on the consumermobile device120, such as in thebill payment module224. As such, the check-in to pumpgas module230 may retrieve stored payment method information in memory or from theserver102 that is associated with the consumer and can display the payment method information for selection on the display of the consumermobile device120. In certain instances, all or a portion of this consumer identification information and payment method information may be stored inmemory118 of the consumermobile device120 or in the memory104 or a database associated with theserver102 and accessible via an authorization token stored in thememory118 of the consumermobile device120 or as part of the check-in to pumpgas module230 on the consumermobile device120. Optionally, inblock430, a personal identification number (PIN) code for accessing the consumer account can be received at the consumermobile device120. For example, the consumer can input a PIN or other code at the display for use in accessing the consumer's account in the check-in to pumpgas module230. In this way, access to the consumer's personal information and payment method information may be secured within the mobile commerce application program116.
• After the consumer account has been configured, and the mobile payment application program116, such as the check-in to pumpgas module230 has stored information associated with the consumer account, the consumer can utilize the account via a user interface provided by the mobilecommerce application program120 as a digital payment device in the merchant's mobile payment program, such as via the mobilecommerce application program108. The application program116 can provide the consumer with any number of tools to facilitate purchases, such as near-field communication, a QR code scanner, a bar code scanner, a payment button, a keypad, a voice input payment command, etc. In some example embodiments, the consumer can verify a payment command or instruction by entering his or her PIN or other code.
• FIG. 5 is a flow chart illustrating an example method for presenting advertising and promotions on a consumer mobile device during a pay at the pump gasoline purchase according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2, and5, anexample method500 for checking-in to pump gas using the check-in to pumpgas module230 on a consumermobile device120 is shown and described. Theexample method500 begins atblock505, where an indication is received that the consumermobile device120 has entered or is within a predetermined distance of the merchant location. In one example, as a consumer pulls up to a gas pump at the merchant location an alert or notification may be triggered on the consumermobile device120 or other client device when thedevice120 is within a predefined range of the merchant, such as on the merchant's property. The alert can be triggered via a location-basedservice132 on the merchant system identifying or receiving a signal from thelocation service144 on the consumermobile device120. In another example, the consumer can scan a code (e.g., a QR code, bar code or other one-dimensional or two-dimensional code) to indicate that the consumermobile device120 is on the merchant property. In another example, the consumer can check-in to the merchant, such as a gas station, by placing the consumer mobile device adjacent a merchant device for conducting near-field communication. In yet another example embodiment, the consumer can check-in to the merchant location using a third-party application, such as SQUARE or FACEBOOK, or any other location identifying application. In yet another example embodiment, the consumer can check in via biometrics, such as via a fingerprint scanner or eye scanner at the merchant location. In still another example embodiment, the vehicle the consumer is in could provide geolocation information to the mobile commerce application program116 at the consumermobile device120. In yet another example embodiment, the consumer can launch the mobile commerce application program116 and/or specifically the check-in to pumpgas module230 when the consumer arrives at the merchant location. The consumer can input the location information or scan tags or codes at her merchant location to obtain geolocation information for the mobile commerce application program.
• Inblock510, if not already done so, the mobile commerce application program116 is launched on the consumermobile device120. In one example embodiment, the mobile commerce application program116 with the check-in to pumpgas module230 launches automatically in response to the location service determining that the consumermobile device120 has checked in via thelocation service132 of themerchant system112. In another embodiment, the mobile commerce application program116 launches in response to the consumer manually selecting an icon associated with the program app on the touch-enabled display of the consumermobile device120. The consumer can then check-in by manually selecting a radio button or icon on the display of the consumermobile device120. Alternatively, the mobile commerce application program116, once opened, can automatically check the consumer in at the merchant's location. In yet another example embodiment, the mobilecommerce application program106 may be launched in response to scanning the code, such as the QR code or bar code at a merchant location or in response to the near field communication with the merchant system at the merchant. In yet another example embodiment, the mobile commerce application program116 can launch based on information provided by a third-party application, such as SQUARE or FACEBOOK, or any other location identifying application. In still another example embodiment, the mobile commerce application program116 can launch based on location information received from the consumer's vehicle.
• Inblock515, the check-in to pumpgas module230 transmits location information (e.g., via thelocation service144, QR code, or near field communication) and consumer identification information of the consumer to the mobilecommerce application program108 at themerchant system112 via thenetwork126. Inblock520, the mobilecommerce application program108 of themerchant system112 can check the consumermobile device120, and relatedly the consumer, into the merchant location via, for example, the mobilecommerce application program108. Inblock525, a request is transmitted to determine the desired services from themerchant system112 to the consumermobile device120. For example, in the gas station context, the merchant mobilecommerce application program108 sends via thenetwork126, and the check-in to pumpgas module230 on thedevice120 receives and displays a request for the number of the pump that the consumer wishes to receive gas from. In alternative embodiments, the merchant mobilecommerce application program108 can generate and send a request listing one or more products and/or services offered by the merchant for display on the mobile commerce application program116 on the consumermobile device120.
• Inblock530, the consumermobile device120 receives a reply input that identifies the product or service. In one example embodiment, the consumer manually selects the reply to the request displayed by the check-in to pumpmodule230. For example, in the gas station context, using the check-in to pump module's UI on the consumermobile device120 or other client device, the consumer inputs the pump number into a field provided by the check-in to pumpgas module230 on the display of the consumermobile device120. Inblock535, a display of payment options is generated at the consumermobile device120. In one embodiment, the check in to pump gas module's UI can display a payment method request to the consumer and provide a display or listing of payment options for paying for the gas on the display of the consumermobile device120 or other client device. In one example embodiment, the payment options can be retrieved by the mobile commerce application program116 from thebill payment module224 or the check-in to pumpgas module230 based on information previously stored in the mobile commerce application program116. Alternatively, the mobile commerce application program116 can retrieve the payment options for the consumer from the servertransaction processing system106 via thenetwork126.
• Inblock540, an input can be received at the I/O interface142 of the consumermobile device120 that corresponds to a selection of the payment method. In one example embodiment, the consumer can select the payment method, for example one of the payment methods pre-registered by the consumer, by, for example, manually selecting an icon associated with the desired payment method on the touch-enabled display of the consumermobile device120. The consumermobile device120 can transmit the selected service and the selected payment option to themerchant system112 either directly or via the servertransaction processing system106 and thenetwork126. For example, the selected service along with an authorization token for the selected payment option can be transmitted to the servertransaction processing system106 which can provide the selected payment information for processing to themerchant system112 or a third-party payment provider. In one example, the pump number and the payment method are transmitted from the consumermobile device120 to the servertransaction processing system106 and subsequently to themerchant system112, such as to the merchant's POS device or other client device of the merchant for pre-authorization of the gas purchase.
• Inblock550, the purchase is authorized at themerchant system112, such as the merchant POS device. Inblock555, if pre-authorization is granted, a notification or signal is transmitted to the consumermobile device120 and/or themerchant device136. In one example embodiment, the notification is sent from themerchant system112 to the consumermobile device120 either directly or via the servertransaction processing system106 and thenetwork126. In addition, themerchant system112 transmits a signal to the selectedpump136 to “unlock” it and allow the consumer to begin pumping gas. The consumer is provided access to the desired product/service inblock560. In the gas station example, the consumer selects the fuel grade at the unlocked pump, if necessary, and begins fueling a vehicle with gas or another fuel type. In other embodiments, the consumer may be provided access to the selected product or service after receiving notification of authorization.
• Inblock565, advertising may be transmitted to the consumermobile device120 from the servertransaction processing system106 or themerchant system112. In one example embodiment, while pumping gas, offers for additional goods and/or services or advertisements related to the merchant can be transmitted via the servertransaction processing system106 or themerchant system112 to the check-inpump gas module230 of the mobile commerce application program116 for display on the consumermobile device120. The ads can be generally provided to all consumers or ads can be identified based on demographic or other information about the consumer, information about the consumer's purchase history with the merchant and/or other similar merchants, or other information, such as time of day or date. Inblock570, when the purchase is complete, an electronic receipt can be generated and transmitted to the mobile commerce application program116 at the consumer mobile device116. In the gas station example, when the consumer finishes pumping gas and puts the pump back up in the holder, thepump136 can transmit a signal to themerchant system112 notifying themerchant system112 that the consumer is complete and the final transaction cost. The mobilecommerce application program108 at themerchant system112 can then generate the receipt and transmit the receipt either directly or via the servertransaction processing system106 andnetwork126 to the mobile commerce application program116 at the consumermobile device120 for display by the check-in to pumpgas module230. Inblock575, loyalty rewards, points, or coupons related to the purchase can be transmitted to the consumermobile device120. For example, the loyalty rewards, points, or coupons can be sent by either themerchant system112 or the servertransaction processing system106 and can be sent for storage and/or display in the loyalty rewards module202 of the mobile commerce application program116 or can be transmitted to thedevice120 via email or text message. In certain example embodiments, purchase or loyalty rewards can be provided to the consumer by way of the mobilecommerce application program102,108, or116 for certain predefined purchases or purchase levels. In addition, coupons for future purchases can be provided to the consumer via the loyalty rewards module202 of the mobilecommerce application program102,108 or116. The process then continues to the END block.
• In an another embodiment, the consumer desires to make additional purchases from inside the store associated with the merchant and to pay for those items using the consumermobile device120, such as after or during the time the vehicle is being fueled. The user interface for the mobile commerce application program116 displays an option to enter the pump number as described above or to pay inside on the display of the consumermobile device120. The consumer can select to pay inside by manually selecting the icon associated with that request and the information is transmitted from the consumermobile device120 to themerchant system112 and/or the servertransaction processing system106. The check-in to pumpgas module230 user interface can display a payment method request to the consumer and provide a display or listing of payment options for paying for the addition merchant goods and/or services on the display of the consumermobile device120. The consumer can select the payment method, for example one of the payment methods pre-registered by the consumer, by, for example, manually selecting an icon associated with the desired payment method on the touch-enabled display of the consumermobile device120. The payment method selection or an authorization token associated with the selected payment method can be transmitted from the consumermobile device120 to themerchant system112 and/or the servertransaction processing system102 via thenetwork126. The servertransaction processing system106 can determine the information for the selected payment method based on the authorization token and can transmit the information for the payment method to themerchant system112, such as to themerchant POS device112 or other client device at the merchant location for purchase of the additional goods and/or services. Alternatively, the information can be transmitted from the consumermobile device120 the merchant'sPOS device120 via near-field communication by placing the consumermobile device120 or other client device against or in close proximity to a near-field communication device136 of the merchant.
• Another embodiment of a method is presented inFIG. 6.FIG. 6 is a flow chart illustrating an example method for presenting targeted advertising and promotions on a consumer mobile device during a gasoline purchase according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2, and6 themethod600 that begins atblock605, where a consumer selects a product for purchase or prepares to purchase a product. Inblock610, the consumer swipes a payment card (e.g., a credit card, debit card, gift card, discount card, or pre-paid card) at amerchant system112, such as amerchant POS device112. The payment card information is transmitted from themerchant system112 to a thirdparty transaction system124 via thenetwork126 for authorization inblock615. As part ofblock615, the payment card information can also be transmitted to the servertransaction processing system102. Inblock620, the consumer associated with the payment card information is determined. For example, the mobilecommerce application program102 of the servertransaction processing system106 can compare the payment card information to a database of consumer information that includes payment method information for consumers to determine if a match exists. If a match of payment card information is identified, the mobilecommerce application program102 of the servertransaction processing system106 can determine the consumer and information about the consumermobile device120 associated with the consumer.
• Inblock625, the demographic and/or purchase history for the identified consumer is determined. For example, the servertransaction processing system106 can parse a database of consumer information to determine demographic and purchase history information about the consumer. In another example, the servertransaction processing system106 can transmit identifying information about the consumer to themerchant system112 or a third-party system, which can make the demographic and/or purchase history determinations. Inblock630, one or more advertisements can be selected based on the consumer demographic or purchase history and can be transmitted to the consumermobile device120 and displayed by the mobile commerce application program116, such as the check-in thepump gas module230. The advertisements can be general advertisements distributed to all consumers or can be targeted to the consumer based on one or more demographic features and/or the purchase history for the consumer. In one example embodiment, the advertisements are transmitted from themerchant system112 to the consumermobile device120 via thenetwork126. If the purchase is not complete, the NO branch is followed back to block630 where ads may continue to be presented to the consumer on the display of the consumermobile device120.
• If the purchase is complete the process follows the YES branch to block640, where loyalty rewards, points, or coupons related to the purchase can be transmitted to the consumermobile device120. For example, the loyalty rewards, points, or coupons can be sent by either themerchant system112 or the servertransaction processing system106 and can be sent for storage and/or display in the loyalty rewards module202 of the mobile commerce application program116 or can be transmitted to thedevice120 via email or text message. In certain example embodiments, purchase or loyalty rewards can be provided to the consumer by way of the mobilecommerce application program102,108, or116 for certain predefined purchases or purchase levels. In addition, coupons for future purchases can be provided to the consumer via the loyalty rewards module202 of the mobilecommerce application program102,108, or116. The process then continues to the END block.
• Another embodiment of amethod700 is presented inFIG. 7.FIG. 7 is a flow chart illustrating another example method for presenting targeted advertising and promotions on a consumer mobile device during a gasoline purchase according to certain example embodiments of the disclosure. Now referring toFIGS. 1,2, and7, theexample method700 begins atblock705, where a consumer selects a product for purchase or prepares to purchase a product. Inblock710, a determination is made as to whether the consumer will be paying for the purchase using cash or a payment card (e.g., a credit card, debit card, gift card, discount card, or pre-paid card). If the consumer is using a payment card, the Credit branch is followed to block720, where the consumer swipes a payment card at amerchant system112, such as amerchant POS device112. In addition, the consumer inputs the phone number associated with the consumermobile device120 inblock725. If the purchase will be a cash purchase, the Cash branch is followed to the block where the consumer makes a cash payment at themerchant system112, such as themerchant POS device112. In addition, the merchant or consumer inputs the phone number associated with the consumermobile device120.
• Inblock730, the phone number information is transmitted from themerchant system112 to the servertransaction processing system106 via thenetwork126. Inblock735, the consumer associated with the phone number is determined. For example, the mobilecommerce application program102 of the servertransaction processing system106 can compare the phone number provided to a database of consumer information that includes phone numbers for consumer mobile devices associated with the consumers to determine if a match exists. If a match of phone numbers is identified, the mobilecommerce application program102 of the servertransaction processing system106 can determine the consumer and information about the consumermobile device120 associated with the consumer.
• Inblock740, the demographic and/or purchase history for the identified consumer is determined. For example, the mobilecommerce application program102 of the servertransaction processing system106 can parse a database of consumer information to determine demographic and purchase history information about the consumer. In another example, the mobilecommerce application program102 of the servertransaction processing system106 can transmit identifying information about the consumer to the mobilecommerce application program108 of themerchant system112 or a third-party system, which can make the demographic and/or purchase history determination. Inblock745, one or more advertisements can be selected and transmitted to the consumermobile device120 and displayed by the mobile commerce application program116, such as the check-in thepump gas module230. The advertisements can be general advertisements distributed to all consumers or can be targeted to the consumer based on one or more demographic features and/or the purchase history for the consumer. In one example embodiment, the advertisements are transmitted from themerchant system112 to the consumermobile device120 via thenetwork126. If the purchase is not complete, the NO branch is followed back to the prior block where ads may continue to be presented to the consumer on the display of the consumermobile device120.
• If the purchase is complete the process follows the YES branch to block755, where loyalty rewards, points, or coupons related to the purchase can be transmitted to the consumermobile device120. For example, the loyalty rewards, points, or coupons can be sent by either themerchant system112 or the servertransaction processing system106 and can be sent for storage and/or display in the loyalty rewards module202 of the mobile commerce application program116 or can be transmitted to the consumermobile device120 via email or text message. In certain example embodiments, purchase or loyalty rewards can be provided to the consumer by way of the mobilecommerce application program102,108, or116 for certain predefined purchases or purchase levels. In addition, coupons for future purchases can be provided to the consumer via the loyalty rewards module202 of the mobilecommerce application program102,108, or116. The process then continues to the END block.FIGS. 8 and 9 illustrate example displays of a user interface presented on a consumer mobile device to communicate notices of offers or promotions during a gasoline purchase according to certain example embodiments of the disclosure. Any one of these example displays may be used with any one or more of the methods discussed above inFIGS. 3-7.
Buy Car Wash
• In some instances, consumers want to be able to purchase products directly from their phone without going through amerchant POS device112 and at times without having to exit their automobile. As one non-limiting example, consumers sometimes desire to purchase a car wash or similar product at a gas station or similar merchant without having to exit the vehicle and/or speak to an employee of the merchant. Certain embodiments of the disclosure can provide systems and processes for facilitating the purchase of a car wash or other product or service with a mobile device or other client device and automatically receiving a code for operating the car wash or providing access to another product or service at the mobile device or other client device. The methods can be implemented on a consumermobile device120 or other client device. For example,FIGS. 10-13 illustrateexample methods1000,1100,1200, and1300 for remotely accessing an initiating receipt of products and/or services from a merchant at a merchant location according to certain embodiments of the disclosure. The followingmethods1000,1100,1200, and1300 are described with reference to a merchant that is a gas station or similar and provides a car wash that is started with the use of a code. However, the example method is not so limited to this type of merchant or product and can be applied to any merchant irrespective of their type of business if access to certain products or services requires a code or proximity of the consumermobile device120 near the product or service for the product or service to be received.
• FIG. 10 is a flow chart illustrating another example method for creating a mobile commerce application program according to certain example embodiments of the disclosure. With reference now toFIGS. 1,2, and10, theexample methods1000 begins atblock1005, where a network link is provided for access by a merchant (e.g., via amerchant system112 or device) to a hostedwebsite134 or payment application program. For example, amerchant system112 may be provided access to a mobilecommerce application program102 at the servertransaction processing system106, which may include abill payment module224. In one example, by way of a client device, such as amerchant system112, a merchant can link via thenetwork126 to thebill payment module224 of the mobilecommerce application program102 on the servertransaction processing system106 to configure a customized payment program.
• Inblock1010, one or more templates and/or user interfaces are presented to prompt the merchant for payment parameters. For example, thebill payment module224 may generate or otherwise present to the merchant at the merchant system112 a series of templates or predefined user interfaces. Inblock1015, merchant parameters for an opt-in mobile payment program are received from the merchant via themerchant system112 and thenetwork126. For instance, a hostedwebsite134 orbill payment module224 on the servertransaction processing system106 can implement a set of computer-executable instructions to enable an opt-in mobile payment program. When prompted, the merchant can select one or more parameters for a payment program via themerchant system112, such as payment methods that can be used, any minimum payment requirements associated with one or more of the payment methods (e.g. minimum amount for use of a credit card, debit card, pre-paid card, stored value card, or gift card), any additional fees that will be added to a transaction if certain payment methods are used (e.g., additional fees for use of a credit card, debit card, pre-paid card, stored value card, or gift card), and any additional information that will need to be provided by a consumer when using particular payment methods.
• Inblock1020, a logo, other trademark, trade name, or other business identifier for the merchant can be received from themerchant system112 at thebill payment module224 of the mobilecommerce application program102 for inclusion in the opt-in mobile payment program. For example, when prompted, the merchant can upload a business logo from themerchant system112 to thebill payment module224 at the servertransaction processing system106. Inblock1025, a downloadable mobile commerce application program116 for use by a consumer can be generated. For instance, after the merchant inputs the business logo and parameters for a payment program, thebill payment module224 or hostedwebsite134 can execute a set of computer-executable instructions to implement the merchant's payment program, such as offering the program as a consumer downloadable mobile commerce application program116 or app in a mobile application store or website. In some embodiments, the mobile commerce application program116 may be branded with the merchant's logo and/or name and may include a buycar wash module232 or provide access thereto. In some embodiments, the mobilecommerce application program106 may be the same application program for some or all merchants, or those merchants within a single classification or geographical location. In the manner described above, various merchants, regardless of size, can adopt and implement abill payment module224 as a part of a mobile payment application program116.
• FIG. 11 is a flow chart illustrating another example method for setting up a consumer account on a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2, and11, theexample method1100 can begin atblock1105, where the servertransaction processing system106 or themerchant system112 receives a request to download a merchant mobile payment program, such as the mobile commerce application program116 that includes a buycar wash module232 or other module directed towards the merchant or the products/services of the merchant. The consumermobile device120 or other client device can communicate, with the servertransaction processing system106 or themerchant system112 via anetwork126, some or all information associated with a scanned QR code, a bar code, information provided via near-filed communication, or other code or a name input from the consumer at the consumermobile device120.
• Inblock1110, a merchant mobile commerce application program116 can be transmitted to and access can be provided to the consumermobile device120. Using the information received in the previous block, the servertransaction processing system106 can identify the merchant's mobile payment program, and download the consumer downloadable mobile commerce application program116 to the consumermobile device120 via thenetwork126. In one example embodiment, the mobile commerce application program116, including the buycar wash module232, can be transmitted via thenetwork126 from the servertransaction processing system106 to the consumermobile device120 for download. For example, by way of a consumermobile device120, a consumer can download a merchant-branded mobile commerce application program116 that includes the buycar wash module232 to the consumermobile device120.
• Inblock1115, theapplication program106 can generate and display on the consumermobile device120 one or more account set-up prompts. For example, the prompts can include one or more fields for receiving consumer identification information including personal information and any other types of information known to the consumer for creating a personalized account for the buycar wash module232. Inblock1120, one or more inputs associated with the set-up prompts can be received at the I/O interface142 of the consumermobile device120. For example, when prompted, the consumer can create an account and input certain personal information to the mobile commerce application program116, such as the consumer's name, address, mobile telephone number, email, social security number, or messaging address. Inblock1125, consumer payment method information can be received at the consumermobile device120. For example, the payment method information may include payment card account information (e.g., credit card account information, debit card account information, pre-paid card account information, stored value card account information, gift card account information, etc.) checking account information, and/or savings account information. This payment method information may be previously stored or accessible via an authorization token on the consumermobile device120, such as in thebill payment module224. As such, the buycar wash module232 may retrieve stored payment method information inmemory118 or from the servertransaction processing system106 that is associated with the consumer and can display the payment method information for selection on the display of the consumermobile device120. In certain instances, all or a portion of this consumer identification information and payment method information may be stored inmemory118 of the consumermobile device120 or in thememory106 or a database associated with the servertransaction processing system106 and accessible via an authorization token stored in thememory118 of the consumermobile device120 or as part of the buycar wash module232 on the consumermobile device120. Optionally, inblock1130, a PIN code for accessing the consumer account can be received at the consumermobile device120. For example, the consumer can input a PIN or other code at the display for use in accessing the consumer's account in the buycar wash module232. In this way, access to the consumer's personal information and payment method information may be secured.
• After the consumer account has been configured, and the mobile payment application program116, such as the buycar wash module232 has stored information associated with the consumer account, the consumer can utilize the account via a user interface provided by the consumer downloadable mobile commerce application program116 as a digital payment device in the merchant's mobile payment program, such as via the mobilecommerce application program108. The mobile commerce application program116 can provide the consumer with any number of tools to facilitate purchases, such as near-field communication, a QR code scanner, bar code scanner, a payment button, a keypad, a voice input payment command, etc. In some example embodiments, the consumer can verify a payment command or instruction by entering his or her PIN or other code.
• FIG. 12 is a flow chart illustrating an example method for providing information and access to products and services of a merchant at a merchant location via a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure. Now referring theFIGS. 1,2, and12, theexample method1200 begins atblock1205, where an indication is received that the consumermobile device120 has entered or is within a predetermined distance of the merchant location. In one example, as a consumer pulls up to a gas pump at the merchant location an alert or notification may be triggered on the consumermobile device120 or other client device when thedevice120 is within a predefined range of the merchant, such as on the merchant's property. The alert can be triggered via a location-basedservice132 on the merchant system identifying or receiving a signal from thelocation service144 on the consumermobile device120. In another example, the consumer can scan a code (e.g., a QR code, bar code or other one-dimensional or two-dimensional code) to indicate that the consumermobile device120 is on the merchant property. In another example, the consumer can check-in to the merchant, such as a gas station, by placing the consumer mobile device adjacent a merchant device for conducting near-field communication. In yet another example embodiment, the consumer can check-in to the merchant location using a third-party application, such as SQUARE or FACEBOOK, or any other location identifying application. In yet another example embodiment, the consumer can check in via biometrics, such as via a fingerprint scanner or eye scanner at the merchant location. In still another example embodiment, the vehicle the consumer is in could provide geolocation information to the mobile commerce application program116 at the consumermobile device120. In yet another example embodiment, the consumer can launch the mobile commerce application program116 and/or specifically the check-in to pumpgas module230 when the consumer arrives at the merchant location. The consumer can input the location information or scan tags or codes at her merchant location to obtain geolocation information for the mobile commerce application program.
• Inblock1210, if not already done so, the mobile commerce application program116 is launched on the consumermobile device120. In one example embodiment, the mobile commerce application program116 with the check-in to pumpgas module230 launches automatically in response to the location service determining that the consumermobile device120 has checked in via thelocation service132 of themerchant system112. In another embodiment, the mobile commerce application program116 launches in response to the consumer manually selecting an icon associated with the program app on the touch-enabled display of the consumermobile device120. The consumer can then check-in by manually selecting a radio button or icon on the display of the consumermobile device120. Alternatively, the mobile commerce application program116, once opened, can automatically check the consumer in at the merchant's location. In yet another example embodiment, the mobilecommerce application program106 may be launched in response to scanning the code, such as the QR code or bar code at a merchant location or in response to the near field communication with the merchant system at the merchant. In yet another example embodiment, the mobile commerce application program116 can launch based on information provided by a third-party application, such as SQUARE or FACEBOOK, or any other location identifying application. In still another example embodiment, the mobile commerce application program116 can launch based on location information received from the consumer's vehicle.
• Inblock1215, the buycar wash module232 of the mobile commerce application program116 transmits location information (e.g., via thelocation service144, QR code, bar code, or near field communication) and consumer identification information of the consumer to themerchant system112 via thenetwork126. Inblock1220, themerchant system112 can check the consumermobile device120, and relatedly the consumer, into the merchant location via, for example, the mobilecommerce application program108. Inblock1225, a request is transmitted to determine the desired product and/or services (e.g., purchase options) from themerchant system112 to the consumermobile device120 via thenetwork126. For example, in the car wash context at the gas station, the merchant mobilecorner application program108 can send via thenetwork126, and the buycar wash module232 on thedevice120 receives and displays a request for the products and/or services desired by the consumer and/or a listing of the products or services offered by the merchant at the merchant location or any other location. In one example, a listing of products could include gas, car wash, air, water, and/or consumer products available inside of the gas station. In another embodiment outside of the gas station context, it could list parking space and/or meter numbers and the cost for different amounts of time for the meters.
• Inblock1230, the consumermobile device120 receives a reply input that identifies the products and/or services desired by the consumer. In one example embodiment, the consumer manually selects the reply to the request displayed by the buycar wash module232 of the mobile commerce application program116. For example, in the car wash context, using the buy car wash module's user interface on the consumermobile device120, the consumer selects the button on the user interface to purchase a car wash from the merchant in a field provided by the buycar wash module232 mobile commerce application program116 on the display of the consumermobile device120. The selection can then be transmitted from the consumermobile device120 to themerchant system112 either directly or via the servertransaction processing system106. Inblock1235, pricing for the selected products and/or services is determined. In one example embodiment, pricing is determined at themerchant system112 or the servertransaction processing system106 at the mobilecommerce application program102 or108.
• Inblock1240, the pricing is transmitted from themerchant system112, such as aPOS system112, to the consumermobile device120 either directly or via the servertransaction processing system106 and thenetwork126. The pricing is then displayed by the mobile commerce application program116 at the consumermobile device120. For example, the buycar wash module232 of the mobile commerce application program116 can receive and display the pricing on the consumermobile device120. Inblock1245, a display of payment options is generated at the consumermobile device120. For example, the user interface for the buycar wash module232 can display the cost of the car wash (or other selected products and/or services) and the payment options for paying for the car wash on the display of the consumermobile device120. In one example embodiment, the payment options can be retrieved from thebill payment module224 or the buycar wash module232 of the mobile commerce application program116 based on information previously stored in the mobile commerce application program116.
• Inblock1250, an input can be received at the I/O interface142 of the consumermobile device120 that corresponds to a selection of the payment method. In one example embodiment, the consumer can select the payment method, for example one of the payment methods pre-registered by the consumer, by, for example, manually selecting an icon associated with the desired payment method on the touch-enabled display of the consumermobile device120.
• Optionally, inblock1255, coupon or discount information, if any, can be selected for use in the transaction. For example, the coupon or discount can be downloaded or retrieved by the buycar wash module232 or the loyalty/rewards module202 of the mobile commerce application program116 on the consumermobile device120. Inblock1260, the consumermobile device120 can transmit the selected service, the selected payment option, and any coupon or discount information, if any, to themerchant system112 either directly or via the servertransaction processing system106 and thenetwork126. For example, the selected products or services along with an authorization token for the selected payment option and any coupon/discount information can be transmitted to the servertransaction processing system106 which can provide the selected payment information for processing along with the pricing or product selection information and the coupon or discount information to themerchant system112 or a third-party payment provider124. In one example, the selection of a car wash and/or price, an authorization token representing the selected payment method, and an electronic coupon are transmitted from the consumermobile device120 to the servertransaction processing system106. The servertransaction processing system106 then transmits the selection of the car wash and/or price, the selected payment information (based on the received token) and the electronic coupon to themerchant system112, such as to the merchant'sPOS device112 or other client device of the merchant for payment authorization.
• Inblock1265, a determination is made if the purchase will be accepted and if the payment method is accepted. In one example embodiment, the purchase and payment method are authorized at themerchant system112, such as themerchant POS device112. Alternatively, the determination can be made by a third-party processor communicably coupled to the merchant's system112 (e.g., POS device). Inblock1270, if the purchase is authorized, a notification or signal is transmitted to the consumermobile device120 and/or themerchant device136. In one example embodiment, the notification is sent from themerchant system112 to the consumermobile device120 either directly or via the servertransaction processing system106 andnetwork126. The notification or signal is received by the buycar wash module232 of the mobile commerce application program116 and displayed on the consumermobile device120 by themodule232. In certain embodiments, the notification is also transmitted to thecar wash136 orother merchant device136.
• Inblock1275, the consumer is provided access to the desired products and/or services. In certain example embodiments, the notification may include a code (e.g., an alphanumeric code, bar code, QR code, or an ability to transmit start instructions via near-field communication using the consumermobile device120 and the location service144). For example the consumer may be able to read a code displayed by the buycar wash module232 of the mobile commerce application program116 on the display of the consumermobile device120 and input it into a keypad or voice recognition device at the controller for the car wash or other product (e.g., parking meter, air compressor, vending machine) offered by the merchant. Alternatively, the controller for thecar wash136 or other product may include aQR code reader138 orbar code reader138 such that the buycar wash module232 on the consumermobile device120 can display the bar code or QR code, which can activate thecar wash136 or otherwise provide access to the product. In another example embodiment, data is provided to the buycar wash module232, which can transmit that data (e.g., a start code) from the consumermobile device120 to thecontroller138 of thecar wash136 or other product (e.g., parking meter, air compressor, vending machine) via near field communication by, for example, positioning the consumermobile device120 against or adjacent to apad138 or other sensor provided for near-field communication and transmitting the code via near-field communication.
• Inblock1280, advertising may be transmitted to the consumermobile device120 from the servertransaction processing system106 or themerchant system112. In one example embodiment, while in thecar wash136 or receiving other products and/or services from the merchant, or simply while still on the merchant property or within a predetermined distance of the merchant property based on information provided by thelocation service132 and144 on themerchant system112 and the consumermobile device120, offers for additional products and/or services or advertisements related to the merchant can be transmitted via the server to the buycar wash module232 of the mobile commerce application program116 for display on the consumermobile device120. The ads can be generally provided or ads can be identified based on demographic or other information about the consumer, information about the consumer's purchase history with the merchant and/or other similar merchants, or other information, such as time of day or date. Inblock1285, when the purchase is complete and/or receipt of the products and/or service are complete, an electronic receipt can be generated and transmitted to the consumermobile device120. In the car wash example, when the car wash is complete, thecar wash136 or thecontroller138 for the car wash can be communicably coupled to and transmit a signal to themerchant system112 notifying themerchant system112 that the car wash is complete. Themerchant system112 can then generate the receipt and transmit the receipt either directly or via the servertransaction processing system106 to the consumermobile device120 for display by the buycar wash module232 of the mobile commerce application program116.
• Inblock1290, loyalty rewards, points, or coupons related to the purchase can be transmitted to the consumermobile device120. For example, the loyalty rewards, points, or coupons can be sent by either themerchant system112 or the servertransaction processing system106 and can be sent for storage and/or display in the loyalty rewards module202 of the mobile commerce application program116 or can be transmitted to thedevice120 via email or text message. In certain example embodiments, purchase or loyalty rewards can be provided to the consumer by way of the mobilecommerce application program102,108, or116 for certain predefined purchases or purchase levels. In addition, coupons for future purchases can be provided to the consumer via the loyalty rewards module202 of the mobilecommerce application program102,108, or116. The process then continues to the END block.
• FIG. 13 illustrate example displays of a user interface presented on a consumer mobile device to communicate information regarding products and services and to provide access to products and services of a merchant at a merchant location according to certain example embodiments of the disclosure. Any one of these example displays may be used with any one or more of the methods discussed above inFIGS. 10-12.
Drive Consumer at Pump Inside
• In some instances, merchants who offer products and purchasing capabilities at more than one location in a small, defined area desire to attract consumers from one product offering area to another to increase sales. For example many gas station merchants offer consumers the convenience of paying for gas at each pump while also offering other products that are desired by customers inside a store located near the pumps. Certain embodiments of the disclosure can provide systems and processes for enabling a targeted mobile device advertising program offered by each merchant gas stations and similar stores the consumer visits. The methods can be implemented on a consumermobile device120 or other client device. For example,FIGS. 14-21 illustrateexample methods1400,1500,1600,1665, and2000 for facilitating the distribution of merchant-related advertising to a consumermobile device120 at or near a merchant location according to certain embodiments of the disclosure. The following method is described with reference to a merchant that is a gas station or similar convenience type store. However, the example method is not so limited and can be applied to any merchant, irrespective of their type of business, to provide a way for supplying general and/or targeted advertising for display on themobile device120 of a consumer at or near the merchant.
• FIG. 14 is a flow chart illustrating anotherexample method1400 for creating a mobile commerce application program according to certain example embodiments of the disclosure. With reference now toFIGS. 1,2, and14, theexample method1400 begins atblock1405, where a network link is provided for access by a merchant (e.g., via amerchant system112 or device) to a targeted advertising and/orpayment application program102. For example, amerchant system112 may be provided access to a mobilecommerce application program102, which may include abill payment module224 and or a drive consumer insidemodule234. In one example, by way of a client device, such as amerchant system112, a merchant can link via thenetwork126 to thebill payment module234 of the mobilecommerce application program102 on the servertransaction processing system106 to configure a customized target advertising and payment program.
• Inblock1410, one or more templates and/or user interfaces are presented to prompt the merchant for payment parameters at themerchant system112. For example, thebill payment module224 of the mobilecommerce application program102 may generate or otherwise present to the merchant at the merchant system112 a series of templates or predefined user interfaces. Inblock1415, merchant parameters for an opt-in targeted advertising and mobile payment program are received from the merchant at themerchant system112. For instance,bill payment module224 or drive consumer insidemodule234 of the mobilecommerce application program102 on the servertransaction processing system106 can implement a set of computer-executable instructions to enable an opt-in targeted advertising and mobile payment program116. When prompted, the merchant, via themerchant system112, can select one or more parameters for a payment program, such as payment methods that can be used, any minimum payment requirements associated with one or more of the payment methods (e.g., minimum amount for use of a credit card, debit card, pre-paid card, stored value card, gift card, etc.), any additional fees that will be added to a transaction if certain payment methods are used (e.g. additional fees for use of a credit card, debit card, pre-paid card, stored value card, gift card, etc.), and any additional information that will need to be provided by a consumer when using particular payment methods.
• Inblock1420, a logo, other trademark, trade name, or other business identifier for the merchant can be received from themerchant system112 for inclusion in the opt-in targeted advertising and mobile payment program116. For example, when prompted, the merchant can upload, via the merchant system112 a business logo from the merchant system to thebill payment module224 or drive consumer insidemodule234 of the mobilecommerce application program102 at the servertransaction processing system106. Inblock1425, advertisements can be received for inclusion in the merchant advertising program. In one example embodiment, the advertisements can be provided by themerchant system112 and/or stored in themerchant system112 for access by the mobilecommerce application program108 when transmission to a consumermobile device120 will occur. For example, each advertisement can be directed to all or a particular subset of consumers while they are making a purchase or just generally located at the merchant. Alternatively, these advertisements can be modified and uploaded over time and during different times based on changing products and changing purchase patterns of consumers who shop with the merchant. Inblock1430, historical purchase information and/or demographic information can be received for multiple consumers. The historical purchase information may be global, for merchants having more than one store, by individual store, and/or by consumer, based on previous purchases attributed to the consumer. In one embodiment, the purchase history and demographic information is provided by themerchant system112 to thebill payment module224 or drive consumer insidemodule234 of the mobilecommerce application program102 of the servertransaction processing system106. Alternatively, it is provided by a third-party or from personal information sent from the consumermobile device120 when the consumer checks-in to the merchant.
• Inblock1435, a downloadable application116 for use by a consumer can be generated. For instance, after the merchant inputs the business logo, parameters for a payment program, advertisements, and/or historical purchase and demographic information, thebill payment module224 or drive consumer insidemodule234 of the mobilecommerce application program102 of the servertransaction processing system106 can execute a set of computer-executable instructions to implement the merchant's targeted advertising and payment program, such as by offering the program as a consumer downloadable mobile commerce application program116 or app in a mobile application store orwebsite134. In some example embodiments, the mobile commerce application program116 may be branded with the merchant's logo and/or name and may include a drive consumer insidemodule234 or provide access thereto. In some embodiments, the mobile commerce application program116 may be the same application program for some or all merchants, or those merchants within a single classification or geographical location. In the manner described above, various merchants, regardless of size, can adopt and implement a drive consumer insidemodule234 as a part of a targeted advertising and mobile payment application program116.
• FIG. 15 is a flow chart illustrating another example method for setting up a consumer account on a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2, and15, theexample method1500 can begin atblock1505 with receiving a request to download a merchant targeted advertising and mobile payment program, such as the mobile commerce application program116 that includes a drive consumer insidemodule234 or other module directed towards advertising for the merchant or the products/services of the merchant. In one example embodiment, a consumer can use near-field communication, scan a QR code or otherwise input an identifying code or name associated with the merchant's targeted advertising and mobile payment program116 into a mobile application store orwebsite134. The consumermobile device120 can communicate, with the servertransaction processing system106 via anetwork126, some or all information associated with a scanned QR code, bar code, information provided via near-filed communication, or other code or name input from the consumer at the consumermobile device120.
• Inblock1510, a merchant mobile payment program116 can be transmitted to and access can be provided to the consumermobile device120. Using the information received in the previous block, the servertransaction processing system106 can identify the merchant's targeted advertising and mobile payment program, and download the consumer downloadable mobile commerce application program116 to the consumermobile device120. In one embodiment, the mobile commerce application program116, including the drive consumer insidemodule234, can be transmitted via thenetwork126 from the servertransaction processing system106 to the consumermobile device120 for download. For example, by way of a consumermobile device120, a consumer can download a merchant-branded targeted advertising and mobile commerce application program116 that includes the drive consumer insidemodule234 to the consumermobile device120.
• Inblock1515, theapplication program106 can generate and display on the consumermobile device120 one or more account set-up prompts. For example, the prompts can include one or more fields for receiving personal information, demographic information, and any other types of information known to the consumer for creating a personalized account for the drive consumer inside module. Inblock1520, one or more inputs associated with the set-up prompts can be received at the I/O interface of the consumermobile device120. For example, when prompted, the consumer can create an account and input certain consumer identification information, including personal information, and demographic information to the mobile commerce application program116, such as a consumer's name, address, mobile telephone number, email, social security number or messaging address, age, race, marital status, sex, education, salary range, etc.
• Inblock1525, consumer payment method information can be received at the consumermobile device120. For example, the payment method information may include a bank account number, payment device number, security code, payment card number (e.g., credit card number, debit card number, pre-paid card number, gift card number, stored value card number, discount card number) and associated information, debit card number and associated information, loyalty card number and associated information, gift card number and associated information, 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. This payment method information may be previously stored or accessible via an authorization token on the consumermobile device120, such as in thebill payment module224. As such, the drive consumer insidemodule234 may retrieve stored payment method information inmemory118 of the consumermobile device120 or from the servertransaction processing system106 that is associated with the consumer and can display the payment method information for selection on the display of the consumermobile device120. In certain instances, all or a portion of this consumer identification information, demographic information, and payment method information may be stored inmemory118 of the consumermobile device120 or in the memory104 or a database associated with the servertransaction processing system106 and accessible via an authorization token stored in thememory118 of the consumermobile device120 or as part of the drive consumer insidemodule234 on the consumermobile device120. Optionally, inblock1530, a PIN code for accessing the consumer account can be received at the consumermobile device120. For example, the consumer can input a PIN or other code at the display for use in accessing the consumer's account in the drive consumer insidemodule234. In this way, access to the consumer's identification information, demographic information, and payment method information may be secured. In the manner described above, since consumers can store or access certain identification, demographic, and financial information via the mobile commerce application program116, consumers can readily register for multiple merchants′ respective targeted advertising and mobile payment programs116, and in some instances, registration can be accomplished with a single click or authorization from the consumer using the consumermobile device120.
• After the consumer account has been configured, and the targeted advertising and mobile payment application program116, such as the drive consumer insidemodule234 has stored information associated with the consumer account, the consumer can utilize the account via a user interface provided by the consumer downloadable mobile commerce application program116 as a digital payment device in the merchant's mobile payment program, such as via the mobilecommerce application program108. The mobile commerce application program116 can provide the consumer with any number of tools to facilitate purchases, such as near-field communication, a QR code scanner, bar code scanner, a payment button, a keypad, a voice input payment command, etc. In some embodiments, the consumer can verify a payment command or instruction by entering his or her PIN or other code.
• FIG. 16 is a flow chart illustrating an example method for providing information and access to products and services of a merchant at a merchant location via a mobile commerce application program on a consumer mobile device according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2, and16, anexample method1600 for distributing merchant-related advertising to a consumermobile device120 at or near a merchant location is shown and described. In one embodiment, a consumer makes a purchase of gasoline at a gas pump using thePOS device112 provided at the gas pump. Typically, the payment information is requested before the consumer is allowed to begin pumping the gas. While the example embodiment is described with reference to a gas station and the purchase of gas at a gas pump, the example method is not so limited to this type of merchant or product and can be applied to any merchant irrespective of their type of business.
• Theexample method1600 begins atblock1605, where an indication is received that the consumermobile device120 has entered or is within a predetermined distance of the merchant location. In one example, as a consumer pulls up to a gas pump at the merchant location an alert or notification may be triggered on the consumermobile device120 or other client device when thedevice120 is within a predefined range of the merchant, such as on the merchant's property. The alert can be triggered via a location-basedservice132 on the merchant system identifying or receiving a signal from thelocation service144 on the consumermobile device120. In another example, the consumer can scan a code (e.g., a QR code, bar code or other one-dimensional or two-dimensional code) to indicate that the consumermobile device120 is on the merchant property. In another example, the consumer can check-in to the merchant, such as a gas station, by placing the consumer mobile device adjacent a merchant device for conducting near-field communication. In yet another example embodiment, the consumer can check-in to the merchant location using a third-party application, such as SQUARE or FACEBOOK, or any other location identifying application. In yet another example embodiment, the consumer can check in via biometrics, such as via a fingerprint scanner or eye scanner at the merchant location. In still another example embodiment, the vehicle the consumer is in could provide geolocation information to the mobile commerce application program116 at the consumermobile device120. In yet another example embodiment, the consumer can launch the mobile commerce application program116 and/or specifically the check-in to pumpgas module230 when the consumer arrives at the merchant location. The consumer can input the location information or scan tags or codes at her merchant location to obtain geolocation information for the mobile commerce application program.
• Inblock1610, if not already done so, the mobile commerce application program116 is launched on the consumermobile device120. In one example embodiment, the mobile commerce application program116 with the check-in to pumpgas module230 launches automatically in response to the location service determining that the consumermobile device120 has checked in via thelocation service132 of themerchant system112. In another embodiment, the mobile commerce application program116 launches in response to the consumer manually selecting an icon associated with the program app on the touch-enabled display of the consumermobile device120. The consumer can then check-in by manually selecting a radio button or icon on the display of the consumermobile device120. Alternatively, the mobile commerce application program116, once opened, can automatically check the consumer in at the merchant's location. In yet another example embodiment, the mobilecommerce application program106 may be launched in response to scanning the code, such as the QR code or bar code at a merchant location or in response to the near field communication with the merchant system at the merchant. In yet another example embodiment, the mobile commerce application program116 can launch based on information provided by a third-party application, such as SQUARE or FACEBOOK, or any other location identifying application. In still another example embodiment, the mobile commerce application program116 can launch based on location information received from the consumer's vehicle.
• Inblock1615, the buycar wash module232 of the mobile commerce application program116 transmits location information (e.g., via thelocation service144, QR code, bar code, or near field communication) and consumer identification information of the consumer to themerchant system112 via thenetwork126. Inblock1620, themerchant system112 can check the consumermobile device120, and relatedly the consumer, into the merchant location via, for example, the mobilecommerce application program108. Inblock1625, a request is transmitted from themerchant system112 to the mobile commerce application program116 at the consumermobile device120 to determine the desired products and/or services that the consumer wishes to buy. For example, in the gas station context, the merchantmobile application program108 sends via thenetwork126, and the drive consumer insidemodule234 of the mobile commerce application program116 on the consumermobile device120 receives and displays a request for the products and/or services desired by the consumer and/or a listing of the products or services offered by the merchant at the merchant location or any other location. In one example, a listing of product could include gas, pump number, car wash, air, water, and/or consumer products available inside of the gas station.
• Inblock1630, the consumermobile device120 receives a reply input that identifies the products and/or services desired by the consumer. In one embodiment, the consumer manually selects the reply to the request displayed by the drive consumer insidemodule234. For example, in the gas station example, using the drive consumer inside module's user interface on the consumermobile device120, the consumer selects the button on the user interface to purchase gas and/or provides the pump number that the consumer is currently positioned at in a field provided by the drive consumer insidemodule234 on the display of the consumermobile device120.
• Inblock1635, a display of payment options is generated at the consumermobile device120. For example, the user interface for the drive consumer insidemodule234 of the mobile commerce application program116 can display the payment options for use in purchasing the selected products and/or services on the display of the consumermobile device120. In one example embodiment, the payment options can be retrieved from thebill payment module224 or the drive consumer insidemodule234 of the mobile commerce application program116 based on information previously stored in the mobile commerce application program116.
• Inblock1640, an input can be received at the I/O interface142 of the consumermobile device120 that corresponds to a selection of the payment method. In one example embodiment, the consumer can select the payment method, for example one of the payment methods pre-registered by the consumer, by, for example, manually selecting an icon associated with the desired payment method on the touch-enabled display of the consumermobile device120.
• Inblock1645, the consumermobile device120 can transmit the selected products and/or services, the selected payment option, and/or the identity of the consumer and/or personal and/or demographic information of the consumer to themerchant system112, either directly or via the servertransaction processing system106 andnetwork126. For example, the selected products or services along with an authorization token for the selected payment option, and consumer identification and demographic information for the consumer can be transmitted to the servertransaction processing system106, which can provide the selected payment information for processing along with the product selection information and the consumer identification and demographic information to themerchant system112 or a third-party payment provider124. In one example, the selection of a gas purchase, an authorization token representing the selected payment method, and consumer identification and demographic information for the consumer are transmitted from the consumermobile device120 to the servertransaction processing system106. The servertransaction processing system106 then transmits the selection of a gas purchase, the selected payment information (based on the received token) and the consumer identification and demographic information to themerchant system112, such as to the merchant'sPOS device112 or other client device of the merchant for payment authorization.
• Inblock1650, a determination is made if the purchase will be accepted and if the payment method is accepted. In one example embodiment, the purchase and payment method are authorized at themerchant system112, such as themerchant POS device112. Alternatively, the determination can be made by a third-party processor124 communicably coupled to the merchant's system112 (e.g., POS device). Inblock1655, if the purchase is authorized, a notification or signal is transmitted to the consumermobile device120 and/or themerchant device136. In one embodiment, the notification is sent from themerchant system112 to the consumermobile device120 either directly or via the servertransaction processing system106 andnetwork126. The notification or signal is received by the drive consumer insidemodule234 of the mobile commerce application program116 and displayed on the consumermobile device120 by themodule234. In certain example embodiments, the notification is also transmitted to thegas pump136 orother merchant device136. Inblock1660, the consumer is provided access to thedevice136. In one embodiment, the receipt of the notification at thegas pump136 or other merchant device can “unlock” thedevice136 or otherwise provide the consumer access to the product at or in thedevice136. In another embodiment, the notification may include a code (e.g., an alphanumeric code, bar code, QR code, or ability to transmit start instructions via near-field communication using the consumer mobile device120). For example the consumer may be able to read a code displayed by the drive consumer insidemodule234 of the mobile commerce application program116 on the display of the consumermobile device120 and input it into a keypad or voice recognition device at thecontroller138 for thegas pump136 or other merchant device (e.g., car wash, parking meter, air compressor, vending machine) offered by the merchant. Alternatively, the controller for the gas pump or other merchant device may include a QR code reader or bar code reader such that the drive consumer insidemodule234 on the consumermobile device120 can display the bar code or QR code, which can activate or “unlock” thegas pump136 or otherwise provide access to the product. In another example embodiment, data is provided to the drive consumer insidemodule234 of the mobile commerce application program116, which can transmit that data (e.g., a start code) from the consumermobile device120 to thecontroller138 of thegas pump136 or merchant device136 (e.g., car wash, parking meter, air compressor, vending machine) via near field communication by, for example, positioning the consumermobile device120 against or adjacent to a pad orother sensor138 provided for near-field communication and transmitting the code via near-field communication.
• Insubroutine block1665, advertising may be selected for the consumer transmitted to the consumermobile device1 from the server or the merchant system for presentation to the consumer. The details of selecting and presenting the advertising insubroutine block1665 are described in further detail with reference toFIGS. 17-19 below. Inblock1670, when the purchase is complete and/or receipt of the products and/or service are complete, an electronic receipt can be generated and transmitted to the consumermobile device1. In the gas station example, when the consumer is finished pumping gas, the pump or the controller for the pump can transmit a signal to the merchant system notifying the merchant system that the pumping of gas is complete. The merchant system can then generate the receipt and transmit the receipt either directly or via the server to the consumermobile device1 for display by the drive consumer inside module.
• Inblock1675, loyalty rewards, points, or coupons related to the purchase can be transmitted to the consumermobile device120. For example, the loyalty rewards, points, or coupons can be sent by either themerchant system112 or the servertransaction processing system106 and can be sent for storage and/or display in the loyalty rewards module202 of the mobile commerce application program116 or can be transmitted to thedevice120 via email of text message. In certain embodiments, purchase or loyalty rewards can be provided to the consumer by way of the mobilecommerce application program102,108, or116 for certain predefined purchases or purchase levels. In addition, coupons for future purchases can be provided to the consumer via the loyalty rewards module202 of the mobilecommerce application program102,108, or116. The process then continues to the END block.
• FIG. 17 is a flow chart illustrating anexample method1665 for generating and displaying targeted advertising to a consumer associated with a consumer mobile device according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2,16, and17, theexample method1665 begins atblock1705, where consumer information is received at the merchant system112 (e.g., via the merchant POS device). In certain example embodiments, the consumer information is transmitted to themerchant system112 from the consumermobile device120 via the drive consumer insidemodule234 of the mobile commerce application program116. Inblock1710, a determination is made as to the phone number and/or email address of the consumer based on the consumer information. The identification information, personal information and/or demographic information about the consumer can be used by themerchant system112 to determine a phone number associated with the consumer or an email address associated with a consumer by comparing the consumer information to a database of information to determine if a match exists with the received consumer information.
• Inblock1715, a determination is made if the advertising will be targeted advertising or general advertising. For example, targeted advertising involves selecting advertisements based on the consumer's prior purchase history with the merchant or other demographic information associated with the consumer. A general advertisement is one that has been selected for distribution without reference to any particular information about a consumer. If the advertising will be general, the NO branch is followed to block1720 where themerchant system112 selects a general advertisement for the merchant and transmits that advertisement to the consumermobile device120. The general advertisement can be received by the drive consumer insidemodule234 of the mobile commerce application program116 and presented on the display of thedevice120.
• If target advertising will be employed, the YES branch is followed to block1725, where one of themerchant system112, servertransaction processing system106, or drive consumer insidemodule234 of the mobile commerce application program116 determines purchase history or demographic information about the consumer. Inblock1730, one of themerchant system112, servertransaction processing system106, or drive consumer insidemodule234 selects an advertisement for presentation to the consumer based on the purchase history and/or demographic profile of the consumer. In one example embodiment, the advertisements are stored on themerchant system112. Inblock1735, the selected advertisement is transmitted to the consumermobile device120 via email, text message, or otherwise received and displayed by the drive consumer insidemodule234 of the mobile commerce application program116 on the consumermobile device120. Optionally, inblock1740, a coupon associated with the advertisement can be transmitted to the consumermobile device120 via email, text message or the drive consumer insidemodule234. The coupon can be stored inmemory118 or stored with the mobile commerce application program116 in the loyalty/rewards module202.
• FIG. 18 is a flow chart illustrating anotherexample method1665 for generating and displaying targeted advertising to a consumer associated with a consumer mobile device according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2,16, and18, theexample method1665 begins atblock1805, where consumer information is received at the merchant system112 (e.g., via the merchant POS device). In certain embodiments, the consumer information is transmitted to themerchant system112 from the consumermobile device120 via the drive consumer insidemodule232. Inblock1810, the consumer information is used by themerchant system112 to compare it to information in a historical database of purchase information to determine the purchase history for this particular consumer associated with the consumermobile device120. Alternatively, the comparison is made by one of the servertransaction processing system106 and the drive consumer insidemodule232 of the mobile commerce application program116.
• Inblock1815, an advertisement is selected for presentation at the consumermobile device120 based on the identified purchase history of the consumer. In certain embodiments, the advertisement is selected by one of themerchant system112, servertransaction processing system106, and drive consumer insidemodule232 of the mobile commerce application program116. Inblock1820, a determination is made as to whether the advertisement will be presented via the mobile commerce application program116. If not, the NO branch is followed to block1825, where themerchant system112, the servertransaction processing system106, or the drive consumer insidemodule232 determines the phone number and/or email address for the consumer based on the received consumer information. The selected advertisement is then transmitted to the consumermobile device120 by themerchant system112 or servertransaction processing system106 in the form of an email or text message.
• Returning to the application presentation determination, if the advertisement will be presented via the mobile commerce application program116, the YES branch is followed to block1835, where one of themerchant system112 or the servertransaction processing system106 transmits the selected advertisement to the drive consumer insidemodule234 of the mobile commerce application program116 at the consumermobile device120. The drive consumer insidemodule234 receives and displays the advertisement on the display of the consumermobile device120 inblock1840. Optionally, inblock1845, a coupon associated with the advertisement can be transmitted to the consumermobile device120 via email, text message or the drive consumer insidemodule234. The coupon can be stored in memory or stored with the mobile commerce application program116 in the loyalty/rewards module202 or the drive consumer inside module.
• FIG. 18 is a flow chart illustrating anotherexample method1665 for generating and displaying targeted advertising to a consumer associated with a consumermobile device120 according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2,16, and19, theexample method1665 begins atblock1905, where consumer information is received at the merchant system112 (e.g., via the merchant POS device). In certain example embodiments, the consumer information is transmitted to themerchant system112 from the consumermobile device120 via the drive consumer insidemodule234 of the mobile commerce application program116. Inblock1910, the consumer information is used by themerchant system112 to determine demographic characteristics of the consumer. For example, the received consumer information may include the demographic information. In another embodiment, the received information can be compared by themerchant system112 to information in a database of consumer information to determine demographic characteristics for this particular consumer associated with the consumermobile device120. Alternatively, the comparison is made by one of the servertransaction processing system106 and the drive consumer insidemodule234 of the mobile commerce application program116.
• Inblock1915, an advertisement is selected for presentation at the consumermobile device120 based on one or more identified demographic characteristics of the consumer. In certain embodiments, the advertisement is selected by one of themerchant system112, servertransaction processing system106, and drive consumer insidemodule234 of the mobile commerce application program116. Inblock1920, a determination is made as to whether the advertisement will be presented via the mobile commerce application program116. If not, the NO branch is followed to block1925, where themerchant system112, the servertransaction processing system106, or the drive consumer insidemodule234 determines the phone number and/or email address for the consumer based on the received consumer information. The selected advertisement is then transmitted to the consumermobile device120 by themerchant system112 or servertransaction processing system106 in the form of an email or text message.
• Returning to the application presentation determination, if the advertisement will be presented via the mobile commerce application program116, the YES branch is followed to block1935, where one of themerchant system112 or the servertransaction processing system106 transmits the selected advertisement to the drive consumer insidemodule234 of the mobile commerce application program116 at the consumermobile device120. The drive consumer insidemodule234 receives and displays the advertisement on the display of the consumermobile device120 inblock1940. Optionally, inblock1945, a coupon associated with the advertisement can be transmitted to the consumermobile device120 via email, text message or the drive consumer insidemodule234. The coupon can be stored inmemory118 or stored with the mobile commerce application program116 in the loyalty/rewards module202 or the drive consumer insidemodule234.
• Anotheralternative method2000 for distributing merchant related advertising is presented inFIG. 20.FIG. 20 is a flow chart illustrating another example method for generating and displaying targeted advertising to a consumer associated with a consumer mobile device according to certain example embodiments of the disclosure. Referring now toFIGS. 1,2, and20, theexample method2000 begins atblock2005, where a consumer selects a product for purchase or prepares to purchase a product. Inblock2010, the consumer swipes a payment card (e.g., a credit card, debit card, gift card, discount card, or pre-paid card) at amerchant system112, such as amerchant POS device112. The payment card information is transmitted from themerchant system112 to a thirdparty transaction system124 for authorization via thenetwork126 inblock2015. As part ofblock2015, the payment card information can also be transmitted to the servertransaction processing system106. Inblock2020, the consumer associated with the payment card information is determined. For example, the servertransaction processing system106 or themerchant system112 can compare the payment card information to a database of consumer information that includes payment method information for consumers to determine if a match exists. If a match of payment card information is identified, the servertransaction processing system106 ormerchant system112 can determine the consumer and information about the consumermobile device120 associated with the consumer.
• Inblock2025, the consumer identification information, demographic characteristics, and/or purchase history for the identified consumer is determined. For example, the servertransaction processing system106 ormerchant system112 can parse a database of consumer information to determine consumer identification information, demographic, and/or purchase history information about the consumer. In another example, the servertransaction processing system106 can transmit identifying information about the consumer to themerchant system112 or a third-party system, which can make the demographic and/or purchase history determination. Inblock2030, one or more advertisements can be selected for presentation at the consumermobile device120 by themerchant system112 or servertransaction processing system106 based on one or more demographic characteristics and/or the purchase history of the identified consumer. In one embodiment, the selection of the advertisement is made by the servertransaction processing system106 or themerchant system112.
• Inblock2035, a determination is made as to whether the advertisement will be presented via the mobile commerce application program116. If not, the NO branch is followed to block2040, where themerchant system112, the servertransaction processing system106, or the drive consumer insidemodule234 of the mobile commerce application program116 determines the phone number and/or email address for the consumer based on the received consumer information. The selected advertisement is then transmitted to the consumermobile device120 by themerchant system112 or servertransaction processing system106 in the form of an email or text message.
• Returning to the application presentation determination, if the advertisement will be presented via the mobile commerce application program116, the YES branch is followed to block2050, where one of themerchant system112 or the servertransaction processing system106 transmits the selected advertisement to the drive consumer insidemodule234 of the mobile commerce application program116 at the consumermobile device120. The drive consumer insidemodule234 receives and displays the advertisement on the display of the consumermobile device120 inblock2055. Optionally, inblock2060, a notification of receipt of or download of loyalty rewards, points, or a coupon associated with the advertisement can be transmitted to the consumermobile device120 via email, text message or the drive consumer insidemodule234. The loyalty rewards, points, or coupon can be stored inmemory118 or stored with the mobile commerce application program116 in the loyalty/rewards module202 or the drive consumer insidemodule234. The process then continues to the END block.
• FIG. 21 illustrates an example display of auser interface2100 presented on a consumermobile device120 to communicate advertising regarding products and services of a merchant at a merchant location while the consumer is at the merchant location according to certain example embodiments of the disclosure. The example display of an advertisement may be used with any one or more of the methods discussed above inFIGS. 14-20.
• Using some or all of the above systems and processes, functionality for facilitating purchases at a gas station via mobile commerce can be enabled. In this manner, consumers can more easily make purchases and merchants can provide advertisements and promotions to consumers to drive them into the merchant location to make additional purchase, which can increase the revenue opportunities for the merchant while providing the consumer with a more pleasant mobile commerce experience.
• 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.
• Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to example embodiments. It will be understood that one or more blocks of the block diagrams and blocks of the flow diagrams, and combinations of blocks in the block diagrams and blocks of the flow diagrams, respectively, may be implemented by execution of computer-executable program instructions Likewise, some blocks of the block diagrams and blocks of the flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some embodiments. Further, additional components and/or operations beyond those depicted in blocks of the block and/or blocks of the flow diagrams may be present in certain embodiments.
• Accordingly, blocks of the block diagrams and blocks of the flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and block of the flow diagrams, and combinations of blocks in the block diagrams and blocks of the flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.
• 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.
• Additional types of CRSM that may be present in any of the devices described herein may include, but are not limited to, programmable random access memory (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the information and which can be accessed. Combinations of any of the above are also included within the scope of CRSM. Alternatively, computer-readable communication media (CRCM) may include computer-readable instructions, program modules, or other data transmitted within a data signal, such as a carrier wave, or other transmission. However, as used herein, CRSM does not include CRCM.
• 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 (24)

What is claimed is:

1. A computer-implemented method for facilitating a purchase of a product from a merchant from a consumer's mobile device, the method comprising:

transmitting, by a merchant device comprising one or more processors to the consumer mobile device, a request for a selection of a product or service for purchase from the merchant;

receiving, by the merchant device from the consumer mobile device, a selection of at least one product or service;

receiving, by the merchant device from the consumer mobile device, a selected payment method for the selected at least one product or service;

processing, by the merchant device, a purchase transaction for the selected at least one product or service with the selected payment method;

transmitting, by the merchant device to the consumer mobile device, a notification of approval of the purchase transaction; and

facilitating access, by the merchant device, to the selected at least one product or service in response to the approval of the purchase transaction.

2. The computer-implemented method ofclaim 1, further comprising:

receiving, by the merchant device, an indication that a consumer is within a predefined distance of a merchant location; and

receiving, by the merchant device from the consumer mobile device, consumer identification information for the consumer.

3. The computer-implemented method ofclaim 2, further comprising:

determining, by the merchant device, a purchase history for the consumer based at least in part on the identification information for the consumer;

selecting, by the merchant device, at least one advertisement based at least in part on the purchase history of the consumer; and

transmitting, by the merchant device to the consumer mobile device, the selected at least one advertisement for display on the consumer mobile device.

4. The computer-implemented method ofclaim 2, further comprising:

determining, by the merchant device, demographic information for the consumer based at least in part on the consumer identification information;

selecting, by the merchant device, at least one advertisement based at least in part on the demographic information for the consumer; and

transmitting, by the merchant device to the consumer mobile device, the selected at least one advertisement for display on the consumer mobile device.

5. The computer-implemented method ofclaim 1, further comprising:

wherein the request for the selection of the product or service for purchase comprises a request for identification of a pump from which the consumer wants to pump gas,

wherein receiving the selection of the at least one product or service comprises an identification of gas pump at the merchant location, and

wherein facilitating access to the selected at least one product or service comprises transmitting, by the merchant device, a signal to the identified gas pump to unlock the gas pump.

6. The computer-implemented method ofclaim 1, further comprising:

wherein the selected payment method comprises payment card transaction information;

determining, by the merchant device, consumer identification information based at least in part on the payment card transaction information;

determining, by the merchant device, contact information for a mobile device of the consumer based at least in part on the determined consumer identification information; and

transmitting, by the merchant device, a notification to the mobile device of receipt of at least one of a loyalty reward, loyalty points, or a coupon based at least in part on a completion of the purchase transaction.

7. The computer-implemented method ofclaim 1, further comprising:

receiving, by the merchant device from a consumer at an input communicably coupled to the merchant device, a phone number associated with the consumer;

determining, by a merchant device, the consumer mobile device associated with the phone number; and

transmitting, by the merchant device, a notification to the consumer mobile device of receipt of at least one of a loyalty reward, loyalty points, or a coupon based at least in part on a completion of the purchase transaction.

8. The method ofclaim 1, further comprising:

providing a scannable code at a merchant location;

receiving, by merchant device, the code from a consumer mobile device;

identifying, by the merchant device, a gas station mobile payment application program based at least in part on the received code;

facilitating, by the merchant device, access to the gas station mobile payment application program; and

receiving, by the merchant device, consumer identification information via the gas station mobile payment application program.

9. A computer-implemented method ofclaim 1, further comprising:

transmitting, by the merchant device, an access code to the consumer mobile device, the access code providing access to the selected at least one product or service.

10. A computer-implemented method ofclaim 1, wherein the selected at least one product or service comprises a car wash and wherein the method further comprises:

transmitting, by the merchant device to the consumer mobile device, an access code, the access code facilitating the initiation of the car wash;

receiving, by the merchant device from the consumer mobile device, the access code, wherein the merchant device is communicably coupled to the car wash; and

initiating, by the merchant device, the car wash in response to receiving the access code at the merchant device.

11. The computer-implemented method ofclaim 1, wherein the selected payment method comprises payment card transaction information and wherein the method further comprises:

determining, by the merchant device, consumer identification information for the consumer based at least in part on the payment card transaction information;

determining, by the merchant device, a demographic characteristic for the consumer based at least in part on the consumer identification information;

selecting, by the merchant device, at least one advertisement based at least in part on the demographic characteristic of the consumer; and

transmitting, by the merchant device to the consumer mobile device, the selected at least one advertisement for display on the consumer mobile device.

12. The computer-implemented method ofclaim 1, wherein the selected payment method comprises payment card transaction information and wherein the method further comprises:

determining, by the merchant device, consumer identification information for the consumer based at least in part on the payment card transaction information;

determining, by the merchant device, a purchase history for the consumer at the merchant based at least in part on the consumer identification information;

selecting, by the merchant device, at least one advertisement based at least in part on the purchase history of the consumer at the merchant; and

transmitting, by the merchant device to the consumer mobile device, the selected at least one advertisement for display on the consumer mobile device.

13. A system comprising:

at least one memory storing computer-executable instructions; and

at least one processor, wherein the at least one processor is configured to access the at least one memory and to execute the computer-executable instructions to:

direct communication of a request for a selection of a product or service for purchase from the merchant to a consumer mobile device;

receive, from the consumer mobile device, a selection of at least one product or service;

receive, from the consumer mobile device, a selected payment method for the selected at least one product or service;

facilitate the processing of a purchase transaction for the selected at least one product or service with the selected payment method;

direct communication of a notification of approval of the purchase transaction to the consumer mobile device; and

facilitate access to the selected at least one product or service in response to the approval of the purchase transaction.

14. The system ofclaim 13, wherein the at least one processor is further configured to execute the computer-executable instructions to:

receive an indication that a consumer is within a predefined distance of a merchant location; and

receive, from the consumer mobile device, consumer identification information for the consumer.

15. The system ofclaim 14, wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine a purchase history for the consumer based at least in part on the identification information for the consumer;

select at least one advertisement based at least in part on the purchase history of the consumer; and

direct communication of the selected at least one advertisement to the consumer mobile device for display on the consumer mobile device.

16. The system ofclaim 14, wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine demographic information for the consumer based at least in part on the consumer identification information;

select at least one advertisement based at least in part on the demographic information for the consumer; and

direct communication of the selected at least one advertisement to the consumer mobile device for display on the consumer mobile device.

17. The system ofclaim 13, wherein the request for the selection of the product or service for purchase comprises a request for identification of a pump from which the consumer wants to pump gas, wherein receiving the selection of the at least one product or service comprises an identification of gas pump at the merchant location, and wherein facilitating access to the selected at least one product or service comprises directing communication of a signal to the identified gas pump to unlock the gas pump.

18. The system ofclaim 13, wherein the selected payment method comprises payment card transaction information and wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine consumer identification information based at least in part on the payment card transaction information;

determine contact information for a mobile device of the consumer based at least in part on the determined consumer identification information; and

direct communication of a notification to the mobile device of receipt of at least one of a loyalty reward, loyalty points, or a coupon based at least in part on a completion of the purchase transaction.

19. The system ofclaim 13, wherein the at least one processor is further configured to execute the computer-executable instructions to:

receive, from a consumer at an input communicably coupled to the merchant device, a phone number associated with the consumer;

determine the consumer mobile device associated with the phone number; and

direct communication of a notification to the consumer mobile device of receipt of at least one of a loyalty reward, loyalty points, or a coupon based at least in part on a completion of the purchase transaction.

20. The system ofclaim 13, wherein a scannable code is provided at a merchant location and wherein the at least one processor is further configured to execute the computer-executable instructions to:

receive the code from a consumer mobile device;

identify a gas station mobile payment application program based at least in part on the received code;

facilitate access to the gas station mobile payment application program; and

receive consumer identification information via the gas station mobile payment application program.

21. The system ofclaim 13, wherein the at least one processor is further configured to execute the computer-executable instructions to direct communication of an access code to the consumer mobile device, the access code providing access to the selected at least one product or service.

22. The system ofclaim 13, wherein the at least one processor is further configured to execute the computer-executable instructions to:

direct communication of an access code to the consumer mobile device, the access code facilitating the initiation of the car wash;

receive, from the consumer mobile device, the access code, wherein the merchant device is communicably coupled to the car wash; and

initiate the car wash in response to receiving the access code at the merchant device.

23. The system ofclaim 13, wherein the selected payment method comprises payment card transaction information and wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine consumer identification information for the consumer based at least in part on the payment card transaction information;

determine a demographic characteristic for the consumer based at least in part on the consumer identification information;

select at least one advertisement based at least in part on the demographic characteristic of the consumer; and

direct communication of the selected at least one advertisement to the consumer mobile device for display on the consumer mobile device.

24. The system ofclaim 13, wherein the selected payment method comprises payment card transaction information and wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine consumer identification information for the consumer based at least in part on the payment card transaction information;

determine a purchase history for the consumer at the merchant based at least in part on the consumer identification information;

select at least one advertisement based at least in part on the purchase history of the consumer at the merchant; and

direct communication of the selected at least one advertisement to the consumer mobile device for display on the consumer mobile device.

Images