Messaging Payment Integration via Tokenization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Social networking systems face challenges in integrating secure and simplified payment transaction functions within messaging platforms, requiring a solution that allows users to engage in commercial transactions while maintaining social interactions without compromising security or user experience.

Innovation Solution

The messaging system incorporates external web-based resources and a secured payment processor to manage payment transactions, using tokenization to handle sensitive data securely, allowing users to complete transactions within the messaging interface while ensuring PCI compliance and seamless interaction with external mini-programs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If payment transaction functions are integrated into messaging platforms, then user engagement and comprehensive social solution are improved, but security risks and data breach vulnerabilities increase

Engineering Contradiction:
Improveuser engagementVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary system that acts as a secure bridge between messaging platforms and payment processors. This intermediary handles sensitive payment data through tokenization, replacing actual card information with secure tokens, thereby enabling payment functionality while maintaining security isolation. The intermediary layer prevents direct exposure of sensitive data between the messaging platform and payment processing systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If external web-based resources and mini-programs are integrated, then transaction functionality is enhanced, but system complexity and integration challenges increase

Engineering Contradiction:
Improvetransaction functionalityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal integration framework that allows messaging platforms to interact with multiple external web-based resources and mini-programs through standardized interfaces. This framework provides common authentication, data sharing, and transaction handling mechanisms that work across different external services, reducing the need for separate integration code for each resource and simplifying the overall system architecture.

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

3Ease of operation

If sensitive payment data is processed within messaging systems, then seamless user experience is achieved, but PCI compliance requirements and security obligations increase

Engineering Contradiction:
Improveuser experienceVSAvoidcompliance requirements
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts sensitive payment data processing from the messaging system core and relocates it to specialized secure payment processing environments. By using tokenization, the actual sensitive data is removed from the messaging platform's data stores and replaced with non-sensitive tokens. This extraction maintains seamless user experience within the messaging interface while significantly reducing PCI compliance burden on the messaging system operators.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20240394696A1Cross-platform data management and integration
Publication Date: 2024.11.28 SNAP INC
  • US20240394696A1 patent drawing
  • US20240394696A1 patent drawing
  • US20240394696A1 patent drawing

AI summary

A method and a system include receiving a request to process a transaction, identifying, by the messaging application, transactional data based on the request, the transactional data corresponding to a user profile associated with the client device in an entity graph, determining a first desensitized data item associated with the user profile being included in the transactional data, providing for display a first user interface of the messaging application including a first user-selectable element corresponding to a completion of the transaction, receiving an indication of user selection of the first user-selectable element, and transmitting the transactional data to a secured processor.