Mobile Payment Permission Control for Frictionless Checkout

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional online checkout processes for new and returning customers require multiple steps, including account setup and payment information entry, which discourages purchases, especially on mobile devices with limited input/output capabilities, leading to lower conversion rates.

Innovation Solution

A friction-less purchasing technology that populates a payment field with a payment request using a payment proxy, allowing seamless transactions without account registration or sign-in, by integrating a mobile payment application that stores financial information and credentials, and optionally verifying transactions through biometric or security measures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional checkout processes require account registration and payment information entry, then security and payment verification are improved, but checkout time and customer friction increase

Engineering Contradiction:
Improvepayment verification securityVSAvoidcheckout time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-registering customers through mobile device identification (device ID, IMEI, or mobile number) and pre-storing payment information in the payment gateway database. When a customer makes a purchase, the system automatically retrieves the stored payment information using the device identifier, eliminating the need for customers to manually enter payment details during checkout. This preliminary setup reduces checkout time while maintaining security through pre-verified payment methods.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically identifying customers through their mobile device identifiers and autonomously retrieving their stored payment information without requiring manual account login or payment detail entry. The payment gateway system automatically matches the device ID with the registered customer profile and processes the payment using pre-stored information, allowing customers to complete purchases with minimal interaction while the system handles verification independently.

Inventive Principle:
Principle #25Self-service

2Reliability

If multiple checkout steps are required including account setup and payment entry, then payment security is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvepayment securityVSAvoidcheckout simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system extracts the complex account login and payment information entry steps from the checkout process by using mobile device identifiers as automatic authentication keys. Instead of requiring customers to navigate through account setup forms and manually input payment details, the system extracts this information beforehand and retrieves it automatically using the device ID, significantly simplifying the checkout operation while maintaining security through the extracted and stored payment profiles.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements universality by using a single mobile device identifier (device ID, IMEI, or mobile number) to perform multiple functions: customer identification, authentication, and payment information retrieval. This single identifier replaces the need for separate account credentials, login processes, and payment detail entries, making the checkout process universally simple across different devices and customers while maintaining secure access to stored payment information.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Measurement precision

If customers must manually enter payment information each time, then data accuracy is improved, but productivity and conversion rate worsen

Engineering Contradiction:
Improvepayment information accuracyVSAvoidpurchase conversion rate
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system performs preliminary action by pre-collecting and storing accurate payment information during the initial mobile device registration process. The payment information is securely stored in the payment gateway database associated with the customer's device identifier. During subsequent purchases, the system automatically retrieves this pre-verified accurate information, eliminating transcription errors from manual entry while maintaining data accuracy through the pre-stored profiles.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically retrieving and using the customer's pre-stored payment information without requiring manual re-entry. The payment gateway system autonomously matches the device identifier with the registered profile and processes the payment using the stored accurate information, eliminating human error from manual input while maintaining productivity through automated retrieval and processing of payment details.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12572919B2Permission management via mobile payment application
Publication Date: 2026.03.10 BLOCK INC
  • US12572919B2 patent drawing
  • US12572919B2 patent drawing
  • US12572919B2 patent drawing

AI summary

Permission management via a mobile payment application is described. A first request to authorize an account of a customer for payment a transaction between the customer and a third-party merchant can be received from a third-party application. Based on the first request indicating that the third-party merchant is permitted to store payment data associated with the account of the customer for processing payment(s) for future transaction(s), a token can be sent to the third-party merchant to be stored for processing the payment(s) for the future transaction(s). A user interface presented via an instance of a mobile payment application, associated with the payment service, on a computing device of the customer, can enable the customer to manage permission(s) associated with the token. A permission associated with the token can be modified based at least in part on receiving a second request via the mobile payment application.