Tokenization Request Throttling for Issuer-Compatible Payment Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Payment networks face significant processing loads and inefficiencies due to the large number of tokenization requests from merchants, necessitating throttling to manage system capabilities and issuer limitations, which complicates transaction processing and exposes vulnerabilities.
Innovation Solution
A computerized method and system that buffers and throttles tokenization requests through a request stream layer, using tokenization stream brokers, a request data store, and a request processing service to manage processing rates, ensuring compatibility with issuer capabilities, thereby optimizing resource use and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If payment networks accept a high volume of tokenization requests from merchants, then the productivity and service coverage are improved, but the processing load on the system increases and issuer capabilities are overwhelmed
Solution Approach 1:
The patent implements preliminary action by pre-fetching tokenization requests from the request stream and storing them in a request data store before issuers are ready to process them. This allows the system to prepare requests in advance and batch them appropriately, ensuring that issuers receive requests at manageable rates while maintaining high overall processing volume. The request handler continuously consumes requests from the stream and stores them, preparing the workload before issuer processing capacity is needed.
Solution Approach 2:
The patent applies dynamics by implementing a request handler that dynamically adjusts the rate at which tokenization requests are consumed from the stream and provided to issuers. The system monitors issuer processing capabilities and request queue depths, dynamically balancing the flow of requests to prevent overwhelming issuers while maximizing throughput. This dynamic rate adjustment allows the system to adapt to varying issuer capacities and maintain reliability under different load conditions.
2Speed
If the payment network processes all tokenization requests immediately, then the speed of processing is improved, but the system complexity increases due to the need to manage throttling and rate limiting
Solution Approach 1:
The patent applies segmentation by dividing the tokenization request processing system into distinct functional layers: a request stream layer that receives and buffers incoming requests, a request data store that holds requests for processing, and a request processing service that interacts with issuers. This segmentation allows each component to operate independently at its optimal speed without requiring complex coordination mechanisms, as the layered architecture naturally handles rate management through the buffer between request intake and issuer processing.
3Reliability
If tokenization requests are buffered and throttled through a request stream layer, then the reliability and issuer compatibility are improved, but the processing time for individual requests increases
Solution Approach 1:
The patent implements continuity of useful action by having the request handler continuously consume tokenization requests from the request stream and store them in the request data store without interruption. This continuous operation eliminates idle time and ensures that requests are prepared as soon as they arrive. The system maintains this continuous request intake and preparation process while throttling the output to issuers, thereby minimizing the time requests spend in the system while ensuring issuer compatibility through controlled release rates.
Data Source
AI summary
The disclosure herein describes handling tokenization requests associated with electronic transactions at a payment network at a throttled processing rate. Tokenization requests are received by tokenization stream brokers from request sources. The tokenization requests include primary account numbers (PANs) to be tokenized. The tokenization requests are then consumed from the tokenization stream brokers, at a request storage rate, for storage in a request data store. Tokenization operations are then performed, at a request processing rate, based on the tokenization requests stored in the request data store. The tokenization operations include providing at least the primary account numbers to be tokenized to issuers associated with the tokenization requests at issuer tokenization rates associated with the issuers, whereby the request processing rate is throttled for compatibility with capabilities of the system and the issuers without unnecessary limitations placed on request sources.