In-App Payment Software Module for One-Click Purchasing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current online and in-app payment systems require users to manually enter payment and address data, which is cumbersome and reduces the number of conversions, especially on mobile devices, and there is no effective mechanism to manage purchases across multiple sites or platforms.

Innovation Solution

A software module and browser-based solution that uses application programming interfaces (APIs) to manage payment data and facilitate one-click purchasing by receiving and transmitting authorized payment information, allowing users to make purchases without manual data entry and enabling unified management of purchases across multiple sites.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users manually enter payment and address data for each transaction, then payment security and accuracy are maintained, but the complexity of operation increases and conversion rates decrease

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

Solution Approach 1:

The system performs preliminary actions by automatically storing payment and address data in the browser's local storage during the first transaction. This pre-stored data is then automatically retrieved and transmitted for subsequent transactions, eliminating the need for repeated manual data entry and significantly reducing the time required for future payments.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service by automatically managing the retrieval, transmission, and updating of payment and address data without requiring user intervention. The browser's local storage mechanism autonomously handles data persistence across sessions, and the system automatically detects when to use stored data versus when to request new data, making the payment process seamless and self-serveing.

Inventive Principle:
Principle #25Self-service

2Productivity

If payment data is automatically transmitted without user confirmation, then transaction speed increases, but security and user control are compromised

Engineering Contradiction:
Improvetransaction processing speedVSAvoidpayment security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system incorporates feedback mechanisms where the user interface displays confirmation of stored payment data before transmission. The system provides visual feedback to users about what data will be transmitted and allows users to review and confirm or modify the data before final submission, ensuring both speed and security are maintained through informed user approval.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If payment data is stored in browser local storage, then ease of access across multiple sites is improved, but data security and privacy risks increase

Engineering Contradiction:
Improvecross-platform payment capabilityVSAvoiddata exposure risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system uses the browser's local storage as an intermediary mechanism that enables cross-platform payment capability while maintaining security boundaries. The stored data remains isolated within the browser's secure storage environment and is only transmitted when explicitly triggered by user action and confirmed through the interface, preventing unauthorized access while enabling versatile payment access across multiple platforms and sites.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10643266B2System and method for in-app payments
Publication Date: 2020.05.05 MONTICELLO ENTERPRISES LLC
  • US10643266B2 patent drawing
  • US10643266B2 patent drawing
  • US10643266B2 patent drawing

AI summary

Disclosed is a device including a processor, a computer-readable storage device and a software module stored on the computer-readable storage device, the software module configured with a software module application programming interface programmed that defines a protocol for communicating data between an application on the device and the software module. The module receives, from the application operating on the device, a request associated with a purchase from the application, wherein the request comprises information about the purchase, receives the authorized payment data and transmits, via the software module application programming interface and to the application, the authorized payment data.