Blockchain Entity Name Mapping for Authorization Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Authorization systems face challenges in securely matching alternate entity names with legal names, leading to potential misrouting of transactions, especially in distributed blockchain networks where accurate record-keeping of entity names is crucial.
Innovation Solution
A blockchain network system that records payment end points associated with both legal and alternate names, allowing for identification and adjustment of transaction requests to ensure funds are directed to the correct legal entity, even if alternate names are used, by maintaining a ledger that maps alternate names to their corresponding legal names.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If alternate entity names are used in authorization requests instead of legal names, then the ease of operation is improved, but the reliability of accurate matching and routing deteriorates
Solution Approach 1:
The patent introduces an intermediary component (authorization system with blockchain integration) that mediates between the alternate entity names provided by users and the legal names required for accurate routing. This intermediary resolves the contradiction by accepting flexible user input while ensuring reliable matching through blockchain-verified entity name mappings.
Solution Approach 2:
The system performs preliminary actions by pre-establishing and storing the relationships between alternate entity names and legal names in a blockchain ledger before authorization requests are processed. This allows the system to quickly and reliably match alternate names to legal names during transaction processing, maintaining both ease of operation and reliability.
2Device complexity
If traditional authorization systems are used without blockchain, then the device complexity is reduced, but the measurement precision of entity name matching deteriorates
Solution Approach 1:
The patent replaces traditional mechanical/database-based entity name matching systems with a blockchain-based system. This substitution provides immutable, distributed verification of entity name relationships, significantly improving measurement precision of matching while the modular integration keeps added complexity manageable.
Solution Approach 2:
The blockchain ledger serves multiple functions: it stores entity name mappings, provides verification of matching accuracy, and enables secure routing decisions. This multi-functionality justifies the added complexity by delivering superior measurement precision across multiple operational dimensions simultaneously.
3Reliability
If blockchain network is implemented for recording entity names, then the reliability of record-keeping is improved, but the device complexity increases
Solution Approach 1:
The patent segments the blockchain implementation into specific functional components within the authorization system, rather than requiring a complete blockchain overhaul. This selective integration maintains reliability benefits while limiting complexity increase to only the portions of the system where blockchain provides value.
Solution Approach 2:
The system utilizes the blockchain ledger as a copied, distributed record-keeping mechanism that replicates entity name mappings across multiple nodes. This copying approach enhances reliability through redundancy and distributed verification while the copying infrastructure is leveraged from existing blockchain implementations, moderating the complexity increase.
Data Source
AI summary
Embodiments of the present invention are directed to routing process authorizations to determine an appropriate legal entity name when an alternate entity name is provided. The system stores alternate entity names in a private or semi-private block chain distributed network, where a block chain ledger keeps an ongoing record of the alternate entity names and their associated legal entity name. When an authorization request is received that does not include a known legal entity name, the system will match the listed entity name with one of the stored alternate entity names, and thereby determine the legal entity name that should be associated with the authorization request.