Stand-In Liquidity Repository for Payment Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Downtime in liquidity management systems during online transactions leads to delays and inefficiencies, particularly for real-time payment requests, as they are typically queued until the system becomes available again.

Innovation Solution

Implementing a stand-in liquidity management system that automatically activates when the primary system is down, allowing real-time payments to be processed using previous liquidity data, and queues or denies requests based on context, with updates to the primary system's ledger upon recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the liquidity management system is used to process payment requests, then measurement precision of liquidity data is improved, but reliability of payment processing deteriorates when the system experiences downtime

Engineering Contradiction:
Improveliquidity data accuracyVSAvoidpayment processing availability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The stand-in liquidity management repository pre-stores historical liquidity data before the primary system goes down. This preliminary preparation allows the payment processing system to continue operations using previously cached data when the primary system becomes unavailable, thus maintaining reliability without sacrificing measurement precision when the primary system is operational.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The stand-in liquidity management repository acts as an intermediary between the primary liquidity management system and the payment processing system. When the primary system is down, the stand-in repository mediates by providing fallback liquidity data, ensuring continuous payment processing while maintaining data accuracy through its pre-stored information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If real-time payment processing is enabled during system downtime using stand-in data, then productivity is improved, but measurement precision of current liquidity status deteriorates

Engineering Contradiction:
Improvepayment processing throughputVSAvoidcurrent liquidity data accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The system applies partial action by using stand-in liquidity data only for the specific purpose of maintaining payment processing throughput during downtime. The stand-in repository provides sufficient historical data to enable transactions to continue, accepting that the data represents a slightly stale view of liquidity status rather than real-time precision, thus prioritizing productivity over perfect measurement accuracy when necessary.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If a stand-in liquidity management repository is implemented, then reliability of payment processing is improved during downtime, but device complexity increases

Engineering Contradiction:
Improvesystem availabilityVSAvoidrepository architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The stand-in liquidity management repository is essentially a copy of the primary repository's data structure and interface, designed to be as simple as possible while providing the necessary fallback functionality. By copying only the essential data storage and retrieval mechanisms rather than implementing a completely new system, the solution improves reliability during downtime while minimizing the increase in device complexity.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250328910A1Liquidity assessment
Publication Date: 2025.10.23 WELLS FARGO BANK NA
  • US20250328910A1 patent drawing
  • US20250328910A1 patent drawing
  • US20250328910A1 patent drawing

AI summary

Managing payment requests. When a liquidity manager goes down, last-known liquidity data can be obtained from a stand-in liquidity manager to execute requested payments even while the liquidity manager is down. Based on a context of a requested payment, execution of the payment can be either performed in real-time using the stand-in liquidity manager or queued until a later time when the liquidity manager is back up.