State-Machine Event Workflows for No-Code Billing Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital commerce billing systems face limitations in flexibility and customization due to vendor-specific APIs, requiring complex developmental interventions and technical expertise for workflow tailoring.

Innovation Solution

Implementing customizable state-machine-based event processing that allows merchants to create and modify workflows without coding, using modular state machines and graphical user interfaces to dynamically adapt to new use cases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vendor-specific APIs and pre-defined integrations are used, then system reliability is maintained, but customization flexibility deteriorates

Engineering Contradiction:
Improveworkflow customization flexibilityVSAvoiddevelopmental intervention complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the workflow customization process into modular state machines that can be independently configured and combined. Each state machine represents a discrete unit of business logic that can be assembled like building blocks to create customized workflows without requiring complex developmental interventions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal state machine framework that can serve multiple customization needs. The same state machine infrastructure supports various workflow types and integrations, allowing a single platform to handle diverse customization requirements without vendor-specific development for each case.

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

2Adaptability or versatility

If pre-defined integrations are used, then ease of operation is improved, but adaptability to new use cases deteriorates

Engineering Contradiction:
Improveadaptability to new use casesVSAvoidworkflow creation ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent prepares state machines in advance with pre-configured structures, transitions, and integrations. These pre-defined components can be readily deployed and modified when new use cases arise, eliminating the need for complex developmental work while maintaining ease of operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables dynamic configuration of state machines where merchants can modify transitions, states, and integrations based on evolving business needs. The system adapts to new use cases by allowing runtime configuration changes without requiring system redesign or complex development interventions.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If vendor developmental efforts are required, then customization capability is improved, but loss of time and resources deteriorates

Engineering Contradiction:
Improveworkflow customization capabilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent empowers merchants to perform workflow customization themselves through the state machine interface without requiring vendor developmental efforts. The system provides self-service capabilities where business users can configure custom workflows using drag-and-drop state machine assembly, eliminating time-consuming vendor development cycles.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If technical expertise is required for programming, then customization precision is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveworkflow customization precisionVSAvoiduser accessibility
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces state machines as an intermediary layer between the user and the complex programming requirements. This abstraction layer translates high-level business logic definitions into executable workflows, allowing users without programming expertise to achieve precise customization by configuring state machine parameters rather than writing code.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12632812B2Customizable state-machine-based event processing
Publication Date: 2026.05.19 STRIPE LLC
  • US12632812B2 patent drawing
  • US12632812B2 patent drawing
  • US12632812B2 patent drawing

AI summary

Aspects of the subject technology include receiving a request to generate an event-based workflow associated with a first event type, which includes a state machine that includes at least a state and an associated transition and receiving an event including a second event type and an event attribute. Aspects also include determining whether the event attribute satisfies the triggering condition of the transition associated with the state, in response to determining that the second event type corresponds to the first event type, and when a current state of the event-based workflow corresponds to the state. Aspects also include performing the transition action of the transition and updating the current state based at least in part on the performed transition action, in response to determining that the event attribute satisfies the triggering condition of the transition associated with the state.