Browser Payment Request API for One-Click Purchase Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current payment processes on the web and mobile devices require users to manually enter payment and address data, making purchases cumbersome and inefficient, especially when transitioning between non-commerce sites and commerce sites.

Innovation Solution

A browser payment request application programming interface (API) that facilitates the communication of payment data between a browser and a site, allowing for prepopulation of payment fields and enabling one-click purchases by analyzing user input for purchase intent and integrating payment processing within social networking sites.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users manually enter payment and address data on each website, then payment security and accuracy are maintained, but the payment process becomes cumbersome and time-consuming

Engineering Contradiction:
Improvepayment process convenienceVSAvoidtime required for data entry
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The browser stores payment and address data in advance during user setup. When a purchase is initiated, the pre-stored data is automatically retrieved and populated into the payment form, eliminating the need for users to re-enter information manually at the time of purchase.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The browser automatically manages the payment data population process without requiring user intervention. The system self-service by detecting the purchase intent, retrieving stored payment information, and filling the form fields automatically, reducing manual data entry to a single confirmation action.

Inventive Principle:
Principle #25Self-service

2Productivity

If users navigate to separate commerce sites to make purchases, then site-specific payment processing accuracy is ensured, but the number of navigation steps and user interactions increases

Engineering Contradiction:
Improvepurchase completion speedVSAvoidnumber of navigation steps
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The invention merges the payment initiation process with the browser's native interface by adding a purchase button to non-commerce sites. This allows users to initiate purchases directly from the content site without navigating away, while the browser handles the payment processing seamlessly in the background.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The browser acts as an intermediary between non-commerce sites and commerce sites. It detects purchase intent on the content site, retrieves stored payment data, and automatically navigates to the appropriate commerce site with pre-filled information, then returns to the original site upon completion, abstracting away the complex navigation steps from the user.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If payment fields are prepopulated with stored data, then the number of user interactions is reduced, but data security and user consent management become more complex

Engineering Contradiction:
Improvenumber of user interactionsVSAvoiddata security management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system implements feedback by presenting the pre-populated payment form to the user for review before submission. The user can verify that the correct payment and address data are selected and has the opportunity to modify or cancel the transaction, ensuring informed consent while maintaining the convenience of pre-filled fields.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The browser establishes security protocols and user consent mechanisms in advance during the initial data storage phase. Users explicitly authorize the browser to store and use their payment information, and this authorization is managed and can be revoked beforehand, simplifying the actual purchase process while maintaining security.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10366429B2Browser payment request API
Publication Date: 2019.07.30 MONTICELLO ENTERPRISES LLC
  • US10366429B2 patent drawing
  • US10366429B2 patent drawing
  • US10366429B2 patent drawing

AI summary

Disclosed herein are methods for providing browser payment request application programming interface for simplifying a payment process on a site. The method includes presenting, on a graphical user interface managed by a browser, a presentation, the presentation being received from a site over a network, receiving, via the user interface and from a user, an interaction with the presentation, receiving, at the browser and via a browser payment request application programming interface that manages communication of data between the site and the browser for processing a payment, a request from the site for payment data for the user and transmitting, to the site and via the browser payment request application programming interface, the payment data, wherein the payment data can be used to process a payment.