API Account Capabilities Framework for Onboarding Bottlenecks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing onboarding process for merchants and agents in commerce systems is burdensome due to the requirement for extensive and irrelevant account data, leading to inefficient resource utilization, prolonged onboarding times, and potential barriers to user onboarding.
Innovation Solution
The implementation of an API-based account capabilities framework that allows merchants and agents to specify requested capabilities, reducing the need for irrelevant data collection by mapping each capability to a compliance plan that defines the minimum required data for activation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If extensive account data is collected from all account types, then compliance requirements are met, but onboarding complexity and time increase significantly
Solution Approach 1:
The patent segments account data requirements by account type and capability. Different account types (merchant, agent, consumer) have different data collection requirements based on their specific capabilities. This segmentation allows the system to collect only necessary data for each account type while maintaining compliance, thereby reducing onboarding time and complexity.
Solution Approach 2:
The patent implements partial data collection by mapping capabilities to minimum required data sets. Instead of collecting all possible account data for every account type, the system collects only the partial data necessary for the specific capabilities that account will use, reducing onboarding burden while meeting compliance requirements.
2Reliability
If comprehensive account information is required for all users, then system security and compliance are ensured, but resource utilization deteriorates
Solution Approach 1:
The system segments data storage and processing by account type and capability. Different account types store different subsets of account information based on their capabilities. This segmentation reduces overall computing resource utilization by avoiding storage and processing of irrelevant data for each account type, while maintaining security through appropriate data protection for each segment.
Solution Approach 2:
The patent applies local quality by tailoring data collection and storage to specific account types and their capabilities. Each account type has customized data requirements matched to its local needs and capabilities, rather than applying a uniform comprehensive data collection approach across all accounts, optimizing resource utilization while maintaining security.
3Device complexity
If uniform account creation process is used for all account types, then system simplicity is maintained, but adaptability to different roles decreases
Solution Approach 1:
The patent implements a dynamic account creation process that adapts to different account types and capabilities. The system dynamically determines which data to collect based on the account type selected and the capabilities requested, rather than using a static uniform process. This dynamic approach maintains relative simplicity while providing high adaptability to different roles.
Solution Approach 2:
The system changes parameters of the account creation process based on account type and capability selections. By dynamically adjusting data collection requirements, validation rules, and processing steps according to the specific account type and requested capabilities, the system maintains process simplicity while achieving high adaptability to different roles.
Data Source
AI summary
A method and apparatus for managing capabilities of an account of a user system at a commerce platform are described. The method includes receiving a request for a desired functionality of the account from a user system. The method may also include mapping the requested capability to a compliance plan that defines a set of account data to be collected before activation of the capability for the account. The method may also include transmitting a message that includes a list of additional data to be provided by the user system before activation of the capability for the account. The method may further include receiving a response from the user system that includes the additional data for activating the capability for the account.