API Gateway Multi-Level Authentication for Payment Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Payment networks face challenges in ensuring the security and authenticity of messages transmitted across their systems, particularly in protecting sensitive data and maintaining continuous authentication to prevent unauthorized access.

Innovation Solution

The implementation of a multi-level authentication system where client and computing device certificates are appended to messages, validated through a local repository and a global access manager, generating a security token for access to backend servers, enhancing security by ensuring only recognized devices and clients can access sensitive information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multi-level authentication with certificate appending is implemented, then security and authenticity of messages is improved, but device complexity and processing overhead increase

Engineering Contradiction:
Improvemessage authenticityVSAvoidauthentication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication system is segmented into multiple independent components: client certificate validation, device certificate validation, and security token generation. Each component operates independently but contributes to the overall authentication process, allowing the system to maintain high security while managing complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Certificates are appended to messages in advance during the message creation process, and validation is performed proactively before granting access to backend services. This preliminary authentication prevents unauthorized access without requiring complex real-time verification mechanisms during critical transaction processing.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If certificate validation is performed at multiple levels, then unauthorized access prevention is improved, but message processing time increases

Engineering Contradiction:
Improveaccess control securityVSAvoidmessage processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs certificate validation and security token generation in advance, before the actual message processing begins. By completing the authentication checks preliminarily, the system ensures that only authorized messages proceed to processing, thereby preventing unauthorized access without significantly delaying legitimate message handling.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A security token acts as an intermediary credential that bridges the gap between certificate validation and message processing. Once certificates are validated, the generated security token serves as a streamlined proof of authentication, allowing subsequent message processing to proceed efficiently without repeatedly verifying the original certificates.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If security tokens are generated for authenticated clients, then backend service protection is improved, but system processing overhead increases

Engineering Contradiction:
Improvebackend service securityVSAvoidmessage processing throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of performing full certificate validation for every backend service request, the system creates a simplified security token copy that represents the authenticated client's credentials. This token can be efficiently verified by backend services without requiring the computationally intensive operations of full certificate chain validation, thus maintaining security while improving processing throughput.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3378213B1Systems and methods for authenticating network messages
Publication Date: 2019.12.25 MASTERCARD INT INC
  • EP3378213B1 patent drawingFigure 1
  • EP3378213B1 patent drawingFigure 2
  • EP3378213B1 patent drawingFigure 3

AI summary

Networks and methods for use in authenticating messages, based on the clients and the computing devices, are provided. One exemplary method generally includes performing, by an API gateway, validation of a computing device based on a certificate identifying the computing device as one of the recognized computing devices, via the repository, and performing, by the API gateway, validation of the client based on the client certificate via a global access manager, separate from the repository. The exemplary method further includes causing a security token indicative of the client to be generated, when the computing device and the client are validated, whereby the security token is indicative of the client and permits the message, from the client, to be delivered to one or more backend services.