Risk Decision Engine Integration for Client Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing risk management systems require clients to redirect users to a separate risk management system for risk management, leading to a loss of relationship and inconsistent user experience, and lack functionality for monitoring and modifying risk management rules across multiple client systems and jurisdictions.

Innovation Solution

A risk management system that allows clients to interface with a risk decision engine via APIs or user interfaces, enabling continuous monitoring and modification of risk management rules, while maintaining user engagement and managing risk across multiple systems and jurisdictions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users are redirected to a separate risk management system, then risk management functionality is provided, but user relationship is lost and user experience becomes inconsistent

Engineering Contradiction:
Improverisk management functionalityVSAvoiduser experience consistency
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent combines the risk management system with the client system by embedding a risk decision engine within the client system. This allows the client system to directly access risk management capabilities without redirecting users to a separate system, thereby maintaining user experience consistency while providing reliable risk management functionality.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an application program interface (API) as an intermediary that enables the client system to communicate with and leverage the risk management system's capabilities. This API allows seamless integration where the client system can invoke risk management functions locally without requiring user redirection, thus maintaining both functionality and user experience consistency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a separate risk management system is used, then risk assessment capability is provided, but monitoring and modification of risk rules across multiple systems becomes difficult

Engineering Contradiction:
Improverisk assessment capabilityVSAvoidrule monitoring complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal risk decision engine that can be deployed across multiple client systems and jurisdictions. This single engine provides standardized risk assessment capabilities and centralized rule management, allowing monitoring and modification of risk rules across all systems through a unified interface, thereby reducing complexity while maintaining comprehensive risk assessment capability.

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

3Reliability

If risk management is handled externally, then specialized risk expertise is accessed, but integration with client systems becomes complex

Engineering Contradiction:
Improverisk management expertiseVSAvoidsystem integration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent enables the client system to self-serve risk management functions by embedding the risk decision engine directly within the client system. This allows the client system to autonomously perform risk assessments and manage risk rules without requiring complex external integration, while still leveraging specialized risk management expertise through the embedded engine.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11593743B2Risk management system interface
Publication Date: 2023.02.28 PAYPAL INC
  • US11593743B2 patent drawing
  • US11593743B2 patent drawing
  • US11593743B2 patent drawing

AI summary

A method may include generating a user interface (UI) to facilitate interaction with a risk management system. The UI may include a first element indicating a rule used by the risk management system to manage risk for a client, a second element indicating effectiveness of the rule, and a third element invocable to modify the rule. The method may also include monitoring activity of the client to determine whether the activity of the client shifts the client into a different category of client; determining that the client is shifted into the different category; based on the shift, modifying the second element to include a recommended modification to the rule; and in response to receiving an interaction with the second element, applying the recommended modification to the rule.