Obviousness

US patent 11004139, titled "System and method for providing simplified in store purchases and in-app purchases using a use-interface-based payment API," aims to simplify the brick-and-mortar shopping experience by enabling users to identify products and complete purchases using their mobile device's web browser and a browser-based payment API, thereby reducing the need for store-specific applications and extensive point-of-sale infrastructure.

Under 35 U.S.C. § 103, a patent claim is obvious if "the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains."

Based on the provided patent text, the following are identified as relevant prior art:

• Amazon Go Store: Described as a system that improves the user shopping experience by allowing users to pick up items and walk out, with purchases automatically charged to their account. However, the patent notes its downsides, including the requirement for users to download a specific Amazon Go app, scan a visual pattern or code upon entry, and the need for an expensive infrastructure of cameras to monitor user activity and product selections. [cite: "Amazon's Go Store provides an improvement of the user experience when shopping but still retains several downsides. The process is as follows. A user must download the Amazon Go app to coordinate with an Amazon payment account (stored credit card) of the user. As the user enters the store, they start the app and scan a visual pattern or code (called a key) that is shown on their phone.", "a very expensive infrastructure is required to monitor the user's selections for identifying what products they are purchasing."]
• Online Payment Services and Browser-based Payment APIs: The patent explicitly mentions "Apple Pay, Google Pay, and the Payment Request API" as existing online payment services and browser-based APIs. [cite: "Online payment services such as Apple Pay, Google Pay, and the Payment Request API or the like are thus applied to the brick-and-mortar purchasing experience."]
• NFC-based Point-of-Sale (POS) Checkout Schemes: The patent refers to "brick-and-mortar point of sale check out schemes like Apple Pay and Google Pay" that utilize NFC technology at checkout points. [cite: "brick-and-mortar point of sale check out schemes like Apple Pay and Google Pay would also be eliminated in favor of the browser-based API model described herein in that no checkout point of sale would be needed."]

The problem US11004139 purports to solve includes the high cost and complexity of existing in-store automated purchasing systems (like Amazon Go), the need for store-specific apps, and the desire to create a consistent purchasing experience across online and physical stores.

Obviousness Combinations and Motivation

A person having ordinary skill in the art (PHOSITA) would have been motivated to combine elements from the identified prior art to arrive at the invention of US11004139.

Combination 1: Amazon Go Store + Online Browser-based Payment APIs

1. Motivation to Combine: The patent itself clearly articulates the motivation to improve upon the Amazon Go model. It states, "This approach also is much more efficient and inexpensive than the Amazon Go store which requires users to download an app, scan a code at an entry location of the store, and which furthermore requires cameras and expensive infrastructure to monitor users as they select items for sale." [cite: "This approach also is much more efficient and inexpensive than the Amazon Go store which requires users to download an app, scan a code at an entry location of the store, and which furthermore requires cameras and expensive infrastructure to monitor users as they select items for sale."] A PHOSITA, observing the convenience of Amazon Go but recognizing its significant infrastructure costs and the friction of requiring a dedicated app, would be motivated to find a more cost-effective and user-friendly solution. Simultaneously, the widespread adoption and simplicity of browser-based online payment APIs (like Apple Pay, Google Pay, and Payment Request API) for online purchases would inspire a PHOSITA to leverage these existing, standardized, and secure payment mechanisms to eliminate the complexities and dedicated infrastructure associated with traditional or even Amazon Go-style in-store payments. The explicit goal is "enabling a consistent purchasing experience both online and in-store." [cite: "Online payment services such as Apple Pay, Google Pay, and the Payment Request API or the like are thus applied to the brick-and-mortar purchasing experience. Thus enabling a consistent purchasing experience both online and in-store."]

2. How the Combination Renders Claims Obvious:

   • Browser-based Store Interaction and Product Identification: Given the goal of reducing app clutter and infrastructure (from Amazon Go), a PHOSITA would naturally consider replacing Amazon Go's proprietary app and camera system with ubiquitous mobile web browsers and the native capabilities of mobile devices. Web browsers are well-known for accessing online store sites. Mobile devices commonly have cameras (for scanning barcodes/QR codes or general image recognition) and communication modules (NFC, RFID readers, Bluetooth) that can be integrated with browser functionality (e.g., via web APIs or JavaScript). Thus, enabling a mobile device's browser to access a store's website and use its camera or NFC for product identification (instead of Amazon Go's dedicated cameras) would be an obvious step for a PHOSITA. [cite: "the user device 204 can have a code reader/camera or other communication component and as they look at products they like, they can scan a code, or the product could be automatically identified through near field communication or some other wireless protocol."]
   • Virtual Shopping Cart: Once products are identified via the mobile device and communicated to the store's server (accessible via the browser), adding them to a virtual shopping cart is a standard and well-understood e-commerce feature.
   • Browser-based Payment API for In-Store Purchases: Applying existing browser-based payment APIs (Apple Pay, Google Pay, Payment Request API), which were already simplifying online transactions, to finalize purchases within this browser-driven in-store environment would be a logical and obvious extension. The PHOSITA would see this as a way to "simplify for them the ability to finalize the purchase" [cite: "the system will simplify for them the ability to finalize the purchase"] and eliminate the need for any separate POS system, including those using NFC. [cite: "brick-and-mortar check out schemes like NFC-based Apple Pay and Google Pay would also be eliminated in favor of the browser-based API model described herein in that no checkout point of sale would be needed including no need for the expensive NFC equipment."]
   • Automated Browser Launch/URL Population: To further streamline the process and overcome the manual URL entry, a PHOSITA would readily integrate known technologies like NFC tags, QR codes, or Bluetooth beacons at store entrances or on products to automatically launch the browser and navigate to the store's specific URL. This is a common application of short-range wireless communication to provide context-aware actions on mobile devices. [cite: "as a user enters the store, there could be a wireless communication through an NFC station, Wi-Fi, Bluetooth, code scan, geofence, or any other protocol 220 which provides an instruction to the device to launch a browser and auto populate the appropriate URL and hit “enter” to navigate to that server."]

Combination 2: NFC-based Point-of-Sale (POS) Payments + Mobile Browsing for Product Information + Mobile Device Scanning

1. Motivation to Combine: A PHOSITA would be familiar with NFC-based mobile payment systems (like Apple Pay and Google Pay) already used at traditional brick-and-mortar POS terminals. While these systems simplified payment at the checkout, they still required a dedicated checkout process and potentially expensive NFC hardware at each POS. Simultaneously, mobile web browsers were commonly used to look up product information (reviews, prices) while in a physical store, often by scanning barcodes with the phone's camera to identify products. The motivation would be to integrate the convenience of mobile product identification and browser-based payment directly, eliminating the need for any dedicated point-of-sale infrastructure whatsoever, including the NFC readers at POS. The patent explicitly states this goal: "The effort made by the individual is minimal in this process and completely eliminates point-of-sale devices and infrastructure." [cite: "The effort made by the individual is minimal in this process and completely eliminates point-of-sale devices and infrastructure."]

2. How the Combination Renders Claims Obvious:

   • Product Identification (Camera/NFC/RFID) and Virtual Cart via Browser: A PHOSITA would extend the existing practice of using a mobile device's camera to scan barcodes for product information lookup to actively select items for purchase within a browser interface. Similarly, NFC/RFID tags, already used for inventory management and short-range data transfer, could be easily adapted to convey product identification data to a mobile browser. This data would then be sent to a store server to populate a virtual shopping cart, mimicking online shopping behavior in a physical store. [cite: "the user device 204 can have a code reader/camera or other communication component and as they look at products they like, they can scan a code, or the product could be automatically identified through near field communication or some other wireless protocol."]
   • Browser-based Payment API for In-Store: Having moved product identification and cart management into the browser, the final logical step is to leverage the already established and user-friendly browser-based payment APIs (which are standard for online purchases and conceptually known even for in-store payments via NFC at POS) to complete the transaction directly from the browser, bypassing any physical POS equipment entirely. This integrates the "simplified payment" aspect of existing mobile payment solutions with the browser-centric product identification to achieve a truly checkout-free experience.

In summary, the claims of US11004139 appear obvious because they represent a combination of existing technologies—the checkout-free store concept (Amazon Go), mobile device capabilities (cameras, NFC, browsers), and standardized online payment APIs (Apple Pay, Google Pay, Payment Request API)—driven by clear motivations to reduce costs, enhance user convenience, and unify the online and offline shopping experiences. The patent itself highlights these problems and provides the motivations for combining these known elements.