Secure Data Forwarding Server with Tokenized Dual-Key Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional data processing systems lack robust security measures to manage and transmit secure data efficiently, failing to authenticate requests at both ends of data forwarding and exposing systems to unnecessary risks.

Innovation Solution

A data processing system that generates unique digital tokens for secure data, uses dual API keys for authentication, and segregates services handling secure and unsecure data, ensuring secure data is not transmitted directly and allowing independent updates of system components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If secure data is transmitted directly over the network, then data transmission efficiency is improved, but security is compromised

Engineering Contradiction:
Improvedata transmission efficiencyVSAvoidsecurity risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a forwarding server as an intermediary between the source and destination systems. The secure data never travels directly over the network; instead, the forwarding server receives the data in a private channel, stores it temporarily, and forwards it to the destination. This mediator approach eliminates direct network exposure of secure data while maintaining transmission efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the secure data from the public network transmission path and places it in a private, secure storage environment on the forwarding server. By taking the secure data out of the direct transmission path and storing it in a protected location, the system maintains security while allowing efficient access through the forwarding server.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If dual API key authentication is implemented, then security is improved, but system complexity increases

Engineering Contradiction:
Improveauthentication securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication process is segmented into two distinct phases: first API key validation for initial request authentication, and second API key validation for data forwarding authentication. This segmentation allows each API key to have a specific, limited purpose, making the complex dual-key system more manageable and secure by reducing the attack surface for each key.

Inventive Principle:
Principle #1Segmentation

3Reliability

If services handling secure and unsecure data are segregated, then security is improved, but device complexity increases

Engineering Contradiction:
Improvedata protectionVSAvoidservice architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The forwarding server is divided into distinct services: one service handles secure data storage and management, while another service handles unsecure network communications and forwarding. This segmentation ensures that even if the unsecure service is compromised, the secure data service remains protected. The clear separation of duties makes the complex architecture more maintainable and secure.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12547746B2Secure data storage and forwarding server
Publication Date: 2026.02.10 STRIPE LLC
  • US12547746B2 patent drawing
  • US12547746B2 patent drawing
  • US12547746B2 patent drawing

AI summary

A server computer system is configured to forward secure data. The system stores secure data in a database. Each unit of secure data for which the system supports forwarding is associated with a respective token. The system receives from a first server, a request comprising at least: an indicator associated with a secure data, a destination indicator, a first API key, a second API key, and a body having a predefined data format. The system validates the request based on the first API key, references the database to obtain the secure data based on the indicator and the respective token, and populates the body with the secure data. Once populated, the system transmits a second request comprising the second API key and the populated body to a second server, based on the destination indicator.