Systems and methods for enhanced shopping using a mobile device

Systems and methods for enhanced shopping using a mobile device are disclosed. In one embodiment, a method for enhanced shopping using a mobile device may include (1) a mobile application executed by a mobile electronic device associating with a merchant system, the mobile electronic device comprising at least one computer processor, a memory, an optical input, and a display; (2) the mobile application receiving an item identifier associated with an item; (3) the mobile application receiving item data for the item from the merchant system based on the item identifier; (4) the mobile application receiving purchase confirmation for the item; and (5) the mobile application communicating payment information for the item to the merchant system.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to payment processing, and, more specifically, to systems and methods for enhanced shopping using a mobile device.

2. Description of the Related Art

Mobile electronic devices are ubiquitous. Today, a mobile electronic device serves as a telephone, camera, calculator, web browser, information source, etc. These device provide the user with the ability to retrieve information at almost any time and in almost any location.

SUMMARY OF THE INVENTION

Systems and methods for enhanced shopping using a mobile device are disclosed. In one embodiment, a method for enhanced shopping using a mobile device, comprising: (1) a mobile application executed by a mobile electronic device associating with a merchant system, the mobile electronic device comprising at least one computer processor, a memory, an optical input, and a display; (2) the mobile application receiving an item identifier associated with an item; (3) the mobile application receiving item data for the item from the merchant system based on the item identifier; (4) the mobile application receiving purchase confirmation for the item; and (5) the mobile application communicating payment information for the item to the merchant system.

In one embodiment, the step of associating with a merchant system may include the mobile application establishing a communication link with the merchant system. In another embodiment, the step of associating with a merchant system may include the mobile application registering with the merchant system. In still another embodiment, the step of associating with a merchant system may include the mobile application logging into an account with the merchant system.

In one embodiment, the step of the mobile application communicating payment information for the item to the merchant system may include the mobile application communicating a payment token to the merchant system. In another embodiment, the step of the mobile application communicating payment information for the item to the merchant system may include the mobile application communicating a payment confirmation to the merchant system.

According to another embodiment, a method for enhanced shopping using a mobile device may include (1) a merchant system comprising at least one computer processor, a memory associating with a mobile application executed by a mobile electronic device; (2) the merchant system receiving, from the mobile application, an identifier for an one item; (3) the merchant system providing item data for the item to the mobile application; (4) the merchant system receiving purchase confirmation for the item from the mobile application; and (5) the merchant system receiving payment information for the item from the mobile application.

In one embodiment, the step of associating with a mobile application may include the merchant establishing a communication link with the mobile application. In another embodiment, the step of associating with a mobile application may include the merchant system receiving a registration request from the mobile application. In still another embodiment, the step of associating with a mobile application may include the merchant system receiving notification that the mobile application has logged into an account with the merchant system.

In one embodiment, the step of the receiving payment information for the item from the mobile application may include the merchant system receiving a payment token from the mobile application. In another embodiment, the step of receiving payment information for the item from the mobile application may include the merchant system receiving a payment confirmation from the mobile application.

In one embodiment, the method may further include the merchant system deactivating a security feature for the item. The security feature may include a RFID tag that is associated with the item.

According to one embodiment, a system enhanced shopping using a mobile device may include a merchant system that includes at least one computer processor, a memory associating with a mobile application executed by a mobile electronic device; an application executed by a mobile electronic device that may include at least one computer processor, a memory, an optical input, and a display; and at least one database comprising item information for a plurality of items offered for sale by the merchant. The mobile application may associate with the merchant system; receive an item identifier associated with an item; receive item data for the item from the merchant system based on the item identifier; receive purchase confirmation for the item; and communicate payment information for the item to the merchant system.

In one embodiment, the association between the mobile application and the merchant system may include a communication link between the mobile application and the merchant system. In another embodiment, the association between the mobile application and the merchant system may be established by the mobile application registering with the merchant system. In still another embodiment, the association between the mobile application and the merchant system may be established by the mobile application logging into an account with the merchant system.

In one embodiment, the payment information may include a payment token. In another embodiment, the payment information may include payment confirmation.

In one embodiment, at least one of plurality of items may include a security feature that is deactivated when the payment information is received. The security feature may include a RF tag. In one embodiment, the merchant may add a RF tag identifier to a list of items that do not trigger a security alert after payment information is received. In another embodiment, the merchant may remove a RF tag identifier to a list of items that trigger a security alert after payment information is received.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Several embodiments of the present invention and their advantages may be understood by referring toFIGS. 1-5.

Embodiments disclosed herein facilitate enhanced shopping using a mobile device. Referring toFIG. 1, a system for in-aisle shopping is disclosed according to one embodiment. System100may include mobile device110, merchant location120, back end130, merchant security system140, and network(s)150. In one embodiment, one or more of mobile device110, merchant120, and back end130may communicate via network(s)150. In addition, one or more of mobile device110, merchant location120, back end130, merchant security system140, and network(s)150may communicate directly via any suitable communication channel, such as WiFi, Bluetooth, NFC, IR, etc.

In one embodiment, merchant location120may include a beacon (e.g., for transmitting merchant information to mobile device110), point-of-sale terminals, a web site, etc.

In one embodiment, the customer may desire to purchase item115using mobile device110. In one embodiment, item115may be associated with one or more machine-readable codes (e.g., UPC, QR codes, etc.). In one embodiment, item115may further include a unique identifier tag, such as a RFID tag, that may identify the specific item.

In one embodiment, information regarding the items (e.g., pricing, inventory, unique identifiers, etc.) may be stored in one or more database (not shown) that may be local or remote. The databases may be accessible via back end130.

Referring toFIG. 2, a method for enhanced shopping using a mobile device is disclosed according to one embodiment. In step205, the user may execute a mobile application on the user's mobile electronic device. In one embodiment, the merchant may initiate this association by providing a beacon or other signal to a mobile device when it enters the merchant's location.

The customer may use the merchant's mobile application or website, a financial institution's mobile application or website, or a third party wallet or payment application as part of this process.

In step210, the customer may establish an association with the merchant's physical location. For example, a customer may register or associate a mobile device and/or a mobile application with a merchant when he or she is physically present at a merchant's store. In one embodiment, the customer may use the merchant's mobile application, a financial institution's application, a third party payment application, a third party shopping application, etc. The application may detect the location of the user by GPS, beacons, etc. In another embodiment, the customer may scan a machine-readable code, such as a QR code, using the mobile application or mobile device. In yet another embodiment, the mobile application or mobile device may connect to the merchant's WiFi or other network.

In one embodiment, the customer may associate the mobile device and/or mobile application with a point of sale terminal. An example of such association is provided in U.S. Provisional Patent Application Ser. No. 62/182,155. The disclosure of this document is incorporated, by reference, in its entirety.

After the relationship is established, the customer may use the mobile device as a sort of extension of the point of sale terminal to scan items to be purchased. In on embodiment, a point of sale terminal may be associated with a single mobile device; in another embodiment, it may be associated with more than one device.

In step215, once the association has been established, the customer may shop for desired items. When the customer selects a desired item, the customer may scan one or more machine-readable code, such as a UPC, a QR code, etc. that may be affixed, printed on a item's packaging, otherwise associated with the item, located on a shelf, etc. Any suitable code may be used as is necessary and/or desired.

In another embodiment, the image recognition may be used to identify the item. In still another embodiment, the customer may shop using a catalog. Any suitable method for identifying an item to purchase may be used as is necessary and/or desired.

If the code is not on the item, or the item is stored in a separate location (e.g., a floor model of an appliance is available but the actual item to purchase is in a warehouse, storage area, etc.), the code may be provided on a shelf, product information card, in a catalog, etc.

In one embodiment, the customer may specify a size, color, quantity, or any item information that may be requested/required.

In step220, once the code is received by the mobile application, item data, such as a description, pricing, etc., may be retrieved from local and/or remote databases, the merchant's back end, etc. In one embodiment, the merchant may also check its inventory to make sure that the product is in stock (e.g., if the actual item to purchase is not available for scanning).

In step225, the mobile application may then display the item data to the customer. In one embodiment, the item description, price, and any other details may be provided as is necessary and/or desired.

In one embodiment, additional information, such as unit price information (e.g., price per unit), warranty information, product reviews, alternate products, recommendations of other products, extended warranty offers, rebate information, promotions involving that or a similar item, etc. may be provided as is necessary and/or desired.

In one embodiment, shipping information (e.g., shipping cost, delivery time, etc.), delivery scheduling, etc. may be provided for the items as is necessary and/or desired.

In one embodiment, manufacturer and/or store coupons or other promotions may be presented as necessary and/or desired.

In step230, the customer may then confirm that the item data is correct (e.g., confirm that the item is the proper item, the pricing is correct, etc.). If it is correct, in step235, the customer may then confirm that the item is to be purchased. In one embodiment, the customer may place the item in his or her shopping cart, may request that the item be retrieved from storage, etc.

In step235, the customer may complete the purchase for each item as the item data is confirmed. In another embodiment, the customer may continue shopping and complete the purchase for all items at the conclusion of shopping.

To complete the purchase, the customer may initiate payment through the mobile application by entering payment information, such as entering credit card information, charging an account, executing the payment through a financial institution mobile application or website, a third party payment application, mobile wallet, etc.

In step240, after payment, the merchant may update its inventory for the product. In one embodiment, items that were in storage may be readied for the customer to pick up. For example, they may be delivered to the front of the store, may be made available at a loading dock, may be otherwise delivered, etc.

In step245, the merchant may deactivate a security feature (e.g., an anti-theft feature) associated with the purchased items. For example, each item may be associated with a unique identifier, such as a RFID tag, that may be affixed to, or otherwise secured to, the item. This identifier may be scanned when the item is scanned, for example, in step215. Once the items is purchased, the merchant may take an action, such as removing the unique identifier for the item from a list that may trigger an alarm or other notification. Alternately, the merchant may add the unique identifier to a list of purchased items. Other actions may be taken as are necessary and/or desired.

As the items are removed from the merchant's store, each item's unique identifier may be read. If the unique identifier is determined to be associated with an item that was not purchased, the merchant and/or customer may be so informed. For example, an alarm may sound, a notification may be sent to the merchant and/or customer, etc.

In one embodiment, a corrective action, such as verifying that the item was paid for, paying for the item, etc., may be taken.

Other embodiments disclosed herein may facilitate cloud-based payments. Referring toFIG. 3, a system for cloud-based payments is disclosed according to one embodiment. System300may include mobile device310, merchant320, financial institution330, and cloud processing350. In one embodiment, one or more of mobile device310, merchant320, financial institution330, and cloud340may communicate via any suitable communication network. In addition, one or more of mobile device310, merchant320, financial institution330, and cloud processing350may communicate directly via one or more suitable communication channel, such as WiFi, Bluetooth, NFC, IR, etc.

In one embodiment, cloud processing350may include processing and/or storage that may be separate from any processing performed by any of mobile device310, merchant320, and/or financial institution330.

In one embodiment, the customer may desire to purchase and/or pay for an item (not shown) using mobile device310. In one embodiment, the customer may shop using mobile device310by, for example, entering data for the item (e.g., UPC code, QR code, selecting from a menu, etc.) into a mobile application that is executed by mobile device310. In another embodiment, the customer may receive item data from merchant320, such as merchant320's point-of-sale device, merchant320's website, or any other suitable interface. Customer310may authorize financial institution330to make a payment for the item to merchant320using the mobile application.

Referring toFIG. 4, a method for cloud-based payment using a mobile device is disclosed according to one embodiment. In step405, a customer may select one or more item for purchase from a merchant. In one embodiment, the customer may select the item(s) in person at a merchant location; in another embodiment, the customer may select the items on-line using the merchant's website, the merchant's application, etc. In another embodiment, the customer may select the items using an application that is provided by a financial institution. The financial institution's application may provide a portal to a merchant's website, may be associated with the merchant's point-of-sale device or other interface, etc.

In step410, the customer may present the item(s) for purchase. In one embodiment, the customer may have the items scanned at a point-of-sale device. In another embodiment, the customer may add the items to an electronic shopping cart and select “checkout.” Any suitable way of selecting items to purchase may be used as is necessary and/or desired.

In step415, the customer may initiate a mobile payment application and may be authenticated by the mobile payment application. It should be noted that the execution of the mobile payment application may occur at any suitable point of the process.

The customer may use the merchant's mobile application or website, a financial institution's mobile application or website, or a third party wallet or payment application, a kiosk, etc. as part of this process.

In step420, the customer may establish an association between the mobile payment application and the merchant. For example, a customer may register or associate a mobile device and/or a mobile application with a merchant when he or she is physically present at a merchant's store. In one embodiment, the customer may use the merchant's mobile application, a financial institution's application, a third party payment application, a third party shopping application, etc. The application may automatically detect the location of the user by GPS, beacons, WiFi networks, etc.

In one embodiment, the customer may associate, or pair, the mobile device and/or mobile application with a point of sale terminal. An example of such association is provided in U.S. Provisional Patent Application Ser. No. 62/182,155. The disclosure of this document is incorporated, by reference, in its entirety.

In step425, the mobile payment application may receive transaction information. In one embodiment, the transaction information may be received from the merchant's point-of-sale device. In another embodiment, transaction information may be received from the merchant's website. In another embodiment, the transaction information may be received as items are identified and entered into the mobile application.

In another embodiment, the mobile payment application may receive the information in bulk, e.g., after information on all products that are part of the transaction are received.

In one embodiment, transaction information may include item information (e.g., description, quantity, price, etc.), merchant identification, a point-of-sale or other terminal identifier, a transaction identifier, etc. Other or additional information may be provided as is necessary and/or desired.

In step430, the customer may authorize payment to the merchant using the mobile payment application. In one embodiment, the customer may select a payment account (e.g., credit card, debit card, checking, line of credit), may apply for a new financial instrument with a new credit line to use for the transaction, etc. Non-traditional transaction accounts, such as rewards accounts, home equity lines of credit, etc. may be used to conduct the transaction as is necessary and/or desired.

In step435, the mobile payment application may provide the transaction information to the issuer of the financial instrument or the financial institution that hosts the selected payment account.

In step440, the issuer/financial may approve the transaction. In one embodiment, the issuer/financial institution may require additional authentication from the customer. For example, if the transaction is above a certain amount, with a certain type of merchant, for a particular product, appears fraudulent, etc., the issuer/financial institution may require additional authentication.

In step445, the issuer/financial institution may provide payment confirmation to the merchant and/or the mobile device. In one embodiment, payment confirmation may not include information regarding the financial instrument or account that was used to complete the payment. Rather, it provides the merchant and/or mobile device with confirmation that the issuer/financial institution has approved the transaction, and the merchant will receive funds for the transaction.

In one embodiment, the confirmation may be provided directly to the merchant. For example, the merchant point-of-sale device, terminal, etc. that is involved in the transaction may receive the payment confirmation, directly or indirectly, from the merchant.

In another embodiment, the payment confirmation may be provided to a trusted site, to a secure location in the cloud, etc. For example, the issuer may host a payment confirmation site that the merchant may access and pull payment confirmation from.

In still another embodiment, the issuer/financial institution may provide the mobile payment application with confirmation of the transaction, and the mobile payment application may provide the confirmation to the merchant. For example, the confirmation may be in the form of a machine-readable code (e.g., a QR code), a RF transmission, etc. that my provide a link to a payment confirmation, etc.

In one embodiment, payment confirmation may be provided to both the merchant and the mobile payment application.

In step450, the transaction may be complete. In one embodiment, the customer may be provided with a receipt (paper, electronic, etc.). For example, an electronic receipt may be provided to the mobile payment application.

In one embodiment, the receipt may include an identifier for the account that was used in the transaction, such as the last four digits of the account number, etc.

Referring toFIG. 5, a method for conducting a cloud-based transaction is provided.

In step505, the customer may initiate a mobile payment application and may be authenticated by the mobile payment application. In one embodiment, the mobile application may be provided by, or associated with, a financial institution.

In one embodiment, the mobile payment application may provide closed-loop payment functionality (e.g., no third party acquirer may be used). Examples of such payment mechanisms are provided in U.S. patent application Ser. Nos. 14/699,511, 14/744,608, and 15/131,979, the disclosures of which are hereby incorporated, by reference, in their entireties.

In step510, the customer may select an item for purchase. In one embodiment, the customer may enter a code that is associated with an item, such as a QR code, that may be provided in marking material, circulars, mailings, on-line, billboards, magazines, etc. to the financial institution's application. In one embodiment, the code may include a product code for the item, a merchant identifier, a manufacturer identifier (if the item is to be purchased directly from the manufacturer), etc. If necessary, the customer may enter size information, color information, quantity information, etc. as necessary and/or desired.

In one embodiment, the financial institution may confirm product availability, pricing, etc. based on the merchant identifier. In one embodiment, the financial institution may determine if the same item may be procured from a different merchant for a lower price, less expensive/quicker shipping, etc.

In one embodiment, the communication with the merchant(s) or manufacturers may be performed without the customer realizing this is happening.

In step515, the customer may authorize payment using the mobile application.

In step520, the financial may approve the transaction. In one embodiment, the customer may submit the transaction to the financial institution using the financial institution's mobile application or website, and may receive approval from the same.

In one embodiment, the financial institution may require additional authentication from the customer. For example, if the transaction is above a certain amount, with a certain type of merchant, for a particular product, appears fraudulent, etc., the financial institution may require additional authentication from the customer.

In step525, the financial institution may transmit the order details and payment confirmation to the merchant that will provide the product, such as the merchant identified in the code.

In step530, the financial institution may provide the mobile application with a receipt for the transaction. Additional information, such as tracking information, etc. may be provided as is necessary and/or desired.

The disclosure of U.S. patent application Ser. Nos. 15/088,437 and 15/069,418 are hereby incorporated, by reference, in their entireties.

It should be recognized that although several embodiments have been disclosed, these embodiments are not exclusive and aspects of one embodiment may be applicable to other embodiments.

The processing machine used to implement the invention may utilize a suitable operating system. Thus, embodiments of the invention may include a processing machine running the iOS operating system, the OS X operating system, the Android operating system, the Microsoft Windows™ operating systems, the Unix operating system, the Linux operating system, the Xenix operating system, the IBM AIX™ operating system, the Hewlett-Packard UX™ operating system, the Novell Netware™ operating system, the Sun Microsystems Solaris™ operating system, the OS/2™ operating system, the BeOS™ operating system, the Macintosh operating system, the Apache operating system, an OpenStep™ operating system or another operating system or platform.