Federated Identifier Registry for Cross-Platform Payment Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing payment systems face challenges in interoperability due to differing technical specifications, communication protocols, and payment rails, leading to issues such as namespace collisions and misdirected payments, especially with the proliferation of various payment services.
Innovation Solution
Implementing federated identifiers that are unique across multiple services, utilizing centralized or decentralized control systems, with collision resolution protocols and security measures to ensure seamless cross-platform transactions and secure user identification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different payment services use their own unique identifiers and technical specifications, then each service can maintain its own security and control, but cross-platform interoperability is limited and transaction complexity increases
Solution Approach 1:
The patent introduces a federated identifier system that acts as an intermediary layer between different payment services. This system includes a federated identifier registry that issues and manages unique identifiers (e.g., did:payment:service:identifier) that can be recognized across multiple payment platforms. The registry mediates between the sender's payment service and the recipient's payment service, enabling seamless cross-platform transactions without requiring each service to directly integrate with every other service.
2Adaptability or versatility
If payment services use centralized identifier management, then cross-platform compatibility improves, but system security and decentralization benefits are reduced
Solution Approach 1:
The federated identifier system segments identifier management into two independent layers: a decentralized issuance layer where multiple trusted payment services can independently issue identifiers using cryptographic key pairs, and a centralized resolution layer where the federated registry resolves identifiers to actual payment accounts. This segmentation allows both decentralization (for security and trust) and centralization (for compatibility and resolution) to coexist.
Solution Approach 2:
The system dynamically adapts to different payment services and platforms by allowing the federated registry to learn and accommodate various identifier formats, payment rails, and technical specifications from different services. The registry can dynamically route transactions through appropriate payment services based on the identifier type and target account, making the system flexible and adaptable to new services without requiring rigid pre-integration.
3Reliability
If federated identifier technology is implemented, then transaction accuracy and security improve, but system complexity and implementation difficulty increase
Solution Approach 1:
The federated identifier system provides universal functionality that works across all participating payment services through a common identifier format and resolution protocol. The did:payment:service:identifier structure and the federated registry's resolution capabilities serve multiple purposes: identifying recipients, routing transactions, verifying authenticity through cryptographic signatures, and enabling cross-platform interoperability. This multi-functionality reduces the need for service-specific identifier systems and simplifies overall implementation.
Data Source
AI summary
In one embodiment, techniques include storing indications of unique identifiers used by users of service providers that are part of a federated system. Each of the unique identifiers is associated with only one user. A computing system of a first service provider receives an intent to register a unique identifier with the first service provider. The computing system determines availability of the unique identifier based on determining whether the unique identifier is associated with another user in the data store. Based at least in part on the determination that the unique identifier is available, the computing system maps, in the data store, the unique identifier with an account of the user associated with each service provider that is part of the federated system. Subsequent to the mapping, the unique identifier is usable as a proxy in lieu of personal data associated with the user on each service provider.