Obviousness

Obviousness Analysis of US Patent 10,643,266 under 35 U.S.C. § 103

Patent: US 10,643,266 B2
Title: System and method for in-app payments
Priority Date: March 31, 2014
Analysis Date: May 31, 2026

This analysis examines whether the independent claims of US Patent 10,643,266 would have been obvious to a person having ordinary skill in the art (PHOSITA) as of the priority date of March 31, 2014, based on the prior art landscape described within the patent itself.

Prior Art Landscape (as of March 31, 2014)

The patent document explicitly identifies several existing technologies, problems, and conceptual solutions that form the basis of the prior art landscape:

• Existing E-commerce and Browser Functionality (Reference A): Online shopping was widespread, featuring merchant-specific shopping carts where users could browse and add products. Web browsers commonly used cookies and local storage for session management, user preferences, and autofill functionalities for forms, including address and basic payment fields [cite: "the system can inspect and use browser cookies from other sites to glean user data, glean search history, or any other information stored in or made available via cookies."].
• Limited "One-Click" Purchasing and Manual Data Entry Problems (Reference B): "One-click" purchasing, notably pioneered by Amazon.com, existed to simplify transactions but was restricted to Amazon's ecosystem [cite: "Some sites like Amazon.com provide a “one-click” purchasing option but those simplifications are only available in the controlled Amazon.com environment."]. For other merchants, the "long-standing problem of requiring users to enter payment data such as credit card information and a user address when making a purchase" was a known issue, often leading to abandoned shopping carts, particularly on mobile devices [cite: "An additional issue relates to the long-standing problem of requiring users to enter payment data such as credit card information and a user address when making a purchase.", "Purchasing concerns can include complicated shopping cart models which require too much data (payment account, address, name, etc.), particularly on a mobile device, causing people to abandon the cart"].
• Multi-site Shopping Cart Concepts and Purchase Management Challenges (Reference C): The concept of a multi-site shopping cart was known to exist, though often undesirable for users due to requirements for separate registration or payment information to the service [cite: "a multi-site shopping cart might exist, it likely requires the user to register or provide payment information to the service, which can be undesirable for the user."]. The proliferation of "buy buttons" on non-merchant sites (e.g., Google, Facebook, Instagram) introduced the challenge of managing purchases spread across "uncoordinated, disparate sites" [cite: "presenting buy options at non-merchant sites to take advantage of such micro-moments introduces the difficulty of managing purchases spread across uncoordinated, disparate sites."].
• Browser Extensions and Payment Service Integration (Reference D): Browser extensions were available to enhance browser functionality, including password managers and form fillers that could store and automatically input user data, including payment and address details, across various websites upon user authorization. External payment services like PayPal and Apple Pay already provided interfaces for easily processing payments by abstracting payment details from merchants [cite: "an interface with PayPal® or Apple Pay is provided such that purchases can be easily processed."].

Core Invention of Independent Claims (1, 11, 14)

The independent claims collectively describe a system and method for a unified, browser-centric shopping experience that integrates products from multiple, distinct merchant sites into a single purchase flow. This includes:

• Receiving and storing product information from a first site (where a purchase was not completed) within or accessible by the browser.
• Initiating a purchase for a second product on a second site.
• Presenting a unified browser payment interface that includes information about both the first and second products.
• Processing the payment for both products through browser-facilitated communication (via APIs) to their respective merchant sites in a streamlined manner, often without manual re-entry of payment or address data.

Obviousness Combination and Motivation

A PHOSITA in March 2014, motivated by the pervasive desire to reduce friction in online purchasing, extend "one-click" convenience beyond single-merchant ecosystems, and simplify the management of cross-site purchases, would have found it obvious to combine the elements described in References A, B, C, and D to arrive at the claimed invention.

Motivation for Combination:
The patent itself clearly articulates the problems that motivated its invention:

1. Reducing Purchase Friction: The "long-standing problem of requiring users to enter payment data" [cite: "An additional issue relates to the long-standing problem of requiring users to enter payment data such as credit card information and a user address when making a purchase."] and the high abandonment rates for complicated shopping carts, particularly on mobile devices [cite: "Purchasing concerns can include complicated shopping cart models which require too much data (payment account, address, name, etc.), particularly on a mobile device, causing people to abandon the cart"], created a strong motivation to simplify the payment process. The success of Amazon's one-click purchasing (Reference B) demonstrated the user demand for such convenience.
2. Harmonizing Disparate Shopping Experiences: The emergence of "buy buttons" on non-merchant sites presented a new challenge: "there is no existing mechanism of harmonizing or organizing purchases such that users can easily manage purchases" [cite: "buy buttons are expanding, there is no existing mechanism of harmonizing or organizing purchases such that users can easily manage purchases."]. This motivated the need for a unified approach to track and purchase items from various sources.
3. Improving Cross-Site Shopping: While "a multi-site shopping cart might exist" [cite: "a multi-site shopping cart might exist, it likely requires the user to register or provide payment information to the service, which can be undesirable for the user."], the existing solutions were cumbersome. A PHOSITA would be motivated to improve upon these by leveraging existing browser capabilities to avoid separate registrations and simplify data entry.

Combination Steps and Rationale Leading to Claims 1, 11, and 14:

1. Browser-Managed Product Interest Tracking (References A, C): Given that browsers already stored user data (Reference A) and extensions could manage cross-site data for autofill (Reference D), it would have been obvious for a PHOSITA to extend a browser's capabilities (either natively or via an extension) to record user interest in a product on a first site (even without purchase). This could be initiated by a user interaction (e.g., dwelling on a product page, adding to a browser-managed "wishlist" or "potential purchase" list) or triggered by a simple "add to cart" action on the merchant's site that the browser's enhanced functionality intercepts and stores. This directly addresses the problem of losing information about items not purchased immediately.
2. Unified Browser Interface for Multi-Merchant Checkout (References A, B, C): Building on the known concept of multi-site shopping carts (Reference C) and the desire for streamlined purchasing (Reference B), it would be an obvious next step to present a browser-controlled interface that aggregates items of interest from various sites. When a user initiates a purchase on a second site, this browser interface would display both the current item and the previously stored item(s) from other sites, allowing for a consolidated view of potential purchases. This leverages the browser's role as a central point of user interaction (Reference A).
3. Browser-Facilitated Payment and Delivery (References B, D): To address the "long-standing problem of requiring users to enter payment data" (Reference B) and extend the "one-click" experience, a PHOSITA would logically integrate the browser's existing autofill capabilities (Reference D) with this unified checkout. Upon user confirmation within the browser's payment interface, the browser (or its extension/module) would securely transmit the stored payment and address data to each relevant merchant site. This could be achieved through a standardized Application Programming Interface (API), which is a common and obvious method for inter-system communication, or by programmatically simulating form submissions. This effectively allows the user to make a single "click" (or minimal interaction) to complete multiple purchases across different merchants, with the browser orchestrating the individual transactions and providing the necessary payment and shipping information. The "browser payment request application programming interface" and "browser shopping cart application programming interface" are thus obvious means to formalize and standardize these interactions given the existing technologies and user needs.

Conclusion

The independent claims of US Patent 10,643,266, encompassing a browser-centric system for aggregating items from multiple sites and facilitating their purchase through a unified interface using browser-stored payment and address data, would have been obvious to a PHOSITA as of the priority date. The motivation stemmed from clear and well-understood problems in online commerce, including the tediousness of manual data entry, the limitations of single-merchant "one-click" solutions, and the challenges of managing purchases across a fragmented online landscape. The combination of existing browser capabilities (data storage, autofill), conceptual multi-site shopping solutions, and established payment service integrations would have led a PHOSITA to develop the claimed invention with a reasonable expectation of success.