Headless Browser Virtual API Mobile Banking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices face challenges in accessing secured data due to security considerations and the complexity of integrating with existing back-end systems, particularly in developing mobile banking applications that require read and write access, while providing a secure and user-friendly experience.

Innovation Solution

A system utilizing a native mobile application combined with a headless browser, which enables read and write access to secured data by emulating a computer login and using a virtual API to interact with internet banking websites, allowing for secure and efficient data access without requiring dedicated back-end integrations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If account aggregation is used to access bank data via intermediary server, then mobile banking functionality can be provided, but security is compromised and read-write access is limited

Engineering Contradiction:
Improvemobile banking functionalityVSAvoidsecurity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent uses a headless browser as an intermediary component that runs locally on the mobile device, acting as a mediator between the native app and the bank's website. This local intermediary eliminates the need for cloud-based credential storage while still enabling access to bank accounts through the website interface, thus maintaining security while providing full functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If custom mobile banking application is developed with full-featured functionality, then complete read and write access is achieved, but development cost and complexity increase

Engineering Contradiction:
Improveread and write access capabilityVSAvoidback-end integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes the headless browser a universal component that can interact with any bank's website through standard web protocols. This multi-functional approach allows a single native app with embedded headless browser to work with multiple banks without requiring custom integrations for each, significantly reducing development complexity while maintaining full read-write access capabilities.

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

Solution Approach 2:

The headless browser essentially copies the functionality of a traditional web browser, allowing it to render and interact with bank websites exactly as a desktop browser would. This copying approach enables the mobile app to access any bank website without requiring custom integration code for each bank, reducing development complexity.

Inventive Principle:
Principle #26Copying

3Reliability

If desktop-formatted websites are accessed via mobile web browser, then access to bank data is enabled, but user experience deteriorates

Engineering Contradiction:
Improvedata access capabilityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent separates the user interface rendering function from the data access function. The native app provides the mobile-optimized user interface, while the headless browser handles the data access tasks in the background. This segmentation allows the UI to be device-optimized while the backend data access can use any format, resolving the conflict between accessibility and user experience.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20240314108A1Headless browser system with virtual api
Publication Date: 2024.09.19 APPBRILLIANCE INC
  • US20240314108A1 patent drawing
  • US20240314108A1 patent drawing
  • US20240314108A1 patent drawing

AI summary

Systems, methods, and computer-readable storage devices to enable virtual API technology embodied in an SDK for use within a mobile application, a mobile payment wallet, or a mobile operating system.