Secure Token Conditional Routing of Payment Proceeds

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current payment systems lack flexibility and control for merchants, particularly in handling secure transactions at an enterprise level, leading to poor user experiences and increased costs due to reliance on third-party processors, which restricts the ability to create payment tokens with incomplete information and split or redirect proceeds.

Innovation Solution

Implementing secure token-driven conditional routing of proceeds, allowing merchants to generate and manage payment tokens within a cloud-based environment, enabling the creation of transaction-ready tokens that can be updated and enforced according to specific payment conditions, thereby facilitating flexible and secure transactions without relying on third-party processors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If merchants rely on third-party processors to handle payments, then transaction security is improved, but control over user experience and payment flow is lost

Engineering Contradiction:
Improvetransaction securityVSAvoidcontrol over user experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a payment token as an intermediary that enables merchants to maintain control over payment flows while using third-party processors. The token contains encrypted payment information and routing instructions, allowing the merchant's system to directly manage the payment process without redirecting users to third-party sites, thus preserving user experience control while maintaining security through the use of established payment processors.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If merchants build their own payment infrastructure to maintain control, then control over payment flow is improved, but investment in computing infrastructure and customized software increases

Engineering Contradiction:
Improvecontrol over payment flowVSAvoidinvestment in computing infrastructure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent uses payment tokens that contain encrypted copies of payment information and routing instructions. Instead of building complex payment infrastructure, merchants can implement a relatively simple system that generates, manages, and processes these tokens. The token itself carries all necessary payment data and logic, allowing merchants to control payment flows without investing in extensive computing infrastructure or customized software.

Inventive Principle:
Principle #26Copying

3Ease of manufacture

If conventional payment systems are used, then transaction processing is simplified, but flexibility to create tokens with incomplete information and redirect proceeds is lost

Engineering Contradiction:
Improvetransaction processing simplicityVSAvoidflexibility to create and update payment tokens
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic payment tokens that can be created with incomplete information and updated subsequently. The token structure allows for conditional routing of proceeds and can be modified based on changing payment conditions. This dynamic capability enables merchants to create flexible payment arrangements that can adapt to different scenarios, such as split payments, conditional routing, and updates to payment terms, while maintaining relatively simple transaction processing.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20240348598A1Secure token driven conditional routing of proceeds
Publication Date: 2024.10.17 STRIPE INC
  • US20240348598A1 patent drawing
  • US20240348598A1 patent drawing
  • US20240348598A1 patent drawing

AI summary

Methods and systems for secure token driven conditional routing of proceeds are described. A request to initiate routing of data between remote systems is received by a server computer system, where the request includes an incomplete set of parameters. A validation challenge and a challenge response defined by a first remote computing system are received, and a token that references the first remote computing system and the incomplete parameter set is generated. A validation may then be performed for a second remote computing system using the validation challenge and the challenge response defined by the first remote computing system. The incomplete set of parameters may then be completed by the second remote computing system when the challenge is validated to enable the routing of data according to the complete set of parameters referenced by the token.