Digital Platform Management With Subordinate IAP Spending Rules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Digital platforms lack the ability to identify and authorize users making in-app purchases (IAPs), allowing unauthorized transactions due to the use of stored payment account information, especially when accessed by non-adult users.

Innovation Solution

A management platform is introduced that creates a master account with associated login credentials, allowing the creation of subordinate accounts with defined funding and spending rules, and provides a dashboard for transaction monitoring and control, including a ledger of transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If stored payment account information is used for in-app purchases, then ease of operation is improved, but security deteriorates due to unauthorized transactions

Engineering Contradiction:
Improveease of operationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments the payment account into a master account (owned by the adult user) and subordinate accounts (owned by non-adult users). This segmentation allows the payment account information to be stored and reused for ease of operation, while simultaneously enabling the master account owner to control and monitor transactions through the management platform, thus resolving the security issue.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The management platform acts as an intermediary between the master account and subordinate accounts. It provides a dashboard and control mechanisms that allow the master account owner to monitor, restrict, and manage transactions made by non-adult users, enabling both ease of operation (through stored payment info) and security (through controlled access).

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If digital platforms allow in-app purchases with stored payment information, then ease of operation is improved, but loss of information increases due to lack of transaction visibility

Engineering Contradiction:
Improveease of operationVSAvoidtransaction visibility
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The management platform implements a feedback mechanism by providing a dashboard that displays transaction information, spending limits, and account status. This feedback loop allows the master account owner to monitor transactions in real-time, maintaining transaction visibility while preserving the ease of operation enabled by stored payment information.

Inventive Principle:
Principle #23Feedback

3Reliability

If a management platform with master and subordinate accounts is implemented, then security is improved, but device complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The management platform is designed as a multi-functional system that handles account creation, transaction monitoring, spending limit enforcement, and payment control through a single integrated dashboard. This universality improves security through comprehensive control while minimizing the increase in device complexity by consolidating multiple functions into one platform.

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

Data Source

PatentUS20250265568A1Systems and methods for providing a management platform for digital platform services
Publication Date: 2025.08.21 WELLS FARGO BANK NA
  • US20250265568A1 patent drawing
  • US20250265568A1 patent drawing
  • US20250265568A1 patent drawing

AI summary

A method, apparatus, and system of providing a management system for digital platforms are disclosed. The method includes creating a master account associated with a first user; providing a management graphical user interface (GUI) to a user device; creating a subordinate account associated with a second user in response to a first user input via the management GUI; establishing one or more spending rules for the subordinate account in response to a second user input via the management GUI; providing a subordinate GUI; generating a subordinate payment token for a payment account associated with the master account; receiving, from a computing system, a request to approve a first in-app purchase (IAP), the request indicating receipt of the subordinate payment token; retrieving the spending rules for the subordinate account; and approving the first IAP from the subordinate account based on the first IAP satisfying the spending rules.