Cloud Wallet Third-Party Check-In Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic wallet systems require users to check-in using a dedicated application for point-of-sale transactions, limiting flexibility and convenience as they cannot process transactions with third-party check-in applications.

Innovation Solution

A cloud wallet system that interfaces with multiple third-party check-in applications, allowing users to conduct point-of-sale transactions using any affiliated check-in application, eliminating the need for a dedicated check-in application and enabling seamless integration with social network systems like Facebook and Foursquare.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a dedicated check-in application is used for electronic wallet transactions, then transaction security and reliability are improved, but user convenience and system adaptability deteriorate because users must use a specific application rather than their preferred third-party check-in application

Engineering Contradiction:
Improvetransaction securityVSAvoiduser convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The electronic wallet service acts as an intermediary between third-party check-in applications and the payment processing system. It receives check-in data from various third-party applications, validates the information, and processes transactions securely without requiring users to download or switch to a dedicated wallet application. This mediator approach maintains security while preserving user convenience.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The electronic wallet service is designed to accept check-in data from multiple different third-party applications rather than being dedicated to a single application. It performs multiple functions including receiving check-in data, validating merchant information, processing payments, and supporting various data formats from different sources, thereby achieving universality and multi-functionality.

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

2Reliability

If a dedicated check-in application is required, then transaction processing reliability is improved, but device complexity and system integration requirements worsen because merchants must implement separate wallet systems

Engineering Contradiction:
Improvetransaction processing reliabilityVSAvoidsystem integration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The electronic wallet service is designed to accept check-in data from multiple different third-party applications rather than being dedicated to a single application. It performs multiple functions including receiving check-in data, validating merchant information, processing payments, and supporting various data formats from different sources, thereby achieving universality and multi-functionality.

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

Solution Approach 2:

The check-in functionality is extracted from the payment processing system and separated into independent third-party applications. The electronic wallet service only needs to receive and validate check-in data without implementing the entire check-in workflow, thereby reducing device complexity while maintaining transaction reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If multiple third-party check-in applications are supported, then user convenience and system adaptability are improved, but data validation complexity and processing time worsen

Engineering Contradiction:
Improvesystem adaptabilityVSAvoiddata validation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The electronic wallet service establishes homogeneous validation rules and data format requirements that all third-party check-in applications must follow. By standardizing the expected data structure and validation criteria across different applications, it reduces validation complexity while maintaining support for multiple applications and achieving adaptability.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS10853776B1Third party check-in associations with cloud wallet
Publication Date: 2020.12.01 AMAZON TECH INC
  • US10853776B1 patent drawing
  • US10853776B1 patent drawing
  • US10853776B1 patent drawing

AI summary

A cloud wallet system may receive an indication from a third party system that a user has checked-in at a merchant. The cloud wallet system then determines whether the merchant has an account with the cloud wallet system so that a point-of-sale (POS) purchase can be processed via the user check-in. If the merchant has an account with the cloud wallet system, a user profile corresponding to the user is sent to the merchant and a point-of-sale transaction based on a third party user check-in may be processed by the merchant through the cloud wallet system.