Configurable Trigger-Based Event Processing for Revenue Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing approaches for revenue recovery in digital commerce lack the flexibility to address nuanced processes and workflows, making it difficult for merchants to effectively recover lost revenue.

Innovation Solution

A platform that allows merchants to generate customized revenue recovery workflows using a graphical user interface, specifying triggers, conditions, and actions without requiring technical expertise in coding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing approaches for revenue recovery are used, then the process is simplified and standardized, but the flexibility to address nuanced customer scenarios is lost

Engineering Contradiction:
Improveflexibility to address nuanced customer scenariosVSAvoidcomplexity of workflow configuration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the revenue recovery process into discrete, configurable workflow components including trigger events, conditions, and actions. Each component can be independently configured and combined to create customized workflows that address specific customer scenarios while maintaining system manageability through modular structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic workflow configuration that allows merchants to adapt recovery processes in real-time based on customer segments and scenarios. The system transitions from static, one-size-fits-all approaches to dynamic, customizable workflows that can be modified without requiring technical expertise, thereby increasing adaptability while controlling complexity through user-friendly interfaces.

Inventive Principle:
Principle #15Dynamics

2Reliability

If customized revenue recovery workflows are implemented, then the effectiveness for specific customer segments improves, but the computing resources required increase

Engineering Contradiction:
Improveeffectiveness of revenue recoveryVSAvoidcomputing resources consumed
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies preliminary action by pre-configuring workflow templates, trigger events, conditions, and actions that can be selectively activated. This allows the system to prepare recovery strategies in advance for different customer segments, reducing real-time computing requirements while maintaining high effectiveness through pre-processed decision logic and segmented customer targeting.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If technical expertise in coding is required for workflow creation, then the precision and control over recovery processes improve, but the ease of use for merchants deteriorates

Engineering Contradiction:
Improveprecision of workflow configurationVSAvoidease of workflow creation
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent implements self-service capabilities that enable merchants to create and configure precise revenue recovery workflows without requiring external technical expertise. The system provides user-friendly interfaces and automated tools that empower end-users to achieve high-precision workflow configuration independently, thereby improving both ease of operation and maintaining manufacturing precision through intuitive design and automated validation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250173781A1Configurable trigger-based event processing
Publication Date: 2025.05.29 STRIPE LLC
  • US20250173781A1 patent drawing
  • US20250173781A1 patent drawing
  • US20250173781A1 patent drawing

AI summary

Aspects of the subject technology include receiving a selection of a trigger event, a set of workflows associated with the trigger event, wherein each workflow is assigned a respective priority attribute, and a set of custom expressions, wherein each custom expression corresponds to a respective workflow and specifies one or more conditions associated with the trigger event. Aspects also include receiving an occurrence of the trigger event and, in response to a determination that the trigger event matches a custom expression for at least one workflow, performing a workflow of the set of workflows having a greatest priority and for which the associated respective custom expression is satisfied, wherein performing a workflow includes performing a set of recovery actions. Aspects also include, in response to a determination that the trigger event does not match any of the respective sets of custom expressions, performing a default workflow.