Credential Manager Receipts for Secure Aggregated Transaction Details
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to provide detailed transaction information to customers when multiple service transactions are aggregated, as the credential manager only receives limited information about the aggregated transaction, making it difficult for customers to understand the individual transactions.
Innovation Solution
A method is implemented where the service provider subsystem facilitates service transactions, aggregates them, and provides detailed transaction descriptors to the funding subsystem, which then generates a customer receipt with individual transaction details upon authentication, ensuring the credential manager can present these details securely to the customer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple service transactions are aggregated into a single transaction, then processing efficiency is improved, but transaction detail visibility deteriorates
Solution Approach 1:
The patent segments the aggregated transaction information by maintaining separate transaction detail records for each individual transaction within the aggregation. The service provider subsystem stores and transmits detailed information for each constituent transaction (e.g., individual purchase amounts, descriptors, and identifiers) separately, allowing the credential manager to reconstruct and display complete transaction breakdowns to customers while the funding subsystem processes the aggregate transaction efficiently.
2Loss of information
If detailed transaction information is provided to the credential manager, then customer transparency is improved, but security risk increases
Solution Approach 1:
The service provider subsystem acts as an intermediary between the funding subsystem and the credential manager. It receives detailed transaction information from the funding subsystem, validates and processes this information, then transmits only the necessary detailed descriptors to the credential manager. This intermediary role enables the credential manager to display transparent transaction details to customers without directly accessing sensitive financial data, thereby maintaining security while improving transparency.
3Loss of time
If aggregated transaction data is transmitted to the funding subsystem, then communication efficiency is improved, but transaction traceability deteriorates
Solution Approach 1:
The service provider subsystem performs preliminary action by pre-processing and organizing detailed transaction information before transmitting it to the funding subsystem. It prepares comprehensive transaction detail data structures that include individual transaction identifiers, amounts, and descriptors in advance, so that when the funding subsystem needs traceability information, the data is already structured and ready for efficient retrieval and transmission, eliminating the need for repeated queries.
Data Source
AI summary
A customer interfacing with a credential manager may be enabled to request and obtain securely from the credential manager additional details related to a service transaction previously effected between the customer and a service provider using a customer transaction credential managed by the credential manager. To obtain such a detailed customer receipt for presentation to a customer, the credential manager may provide an authenticatable customer receipt request to the service provider that may include certain information indicative of an active session between the credential manager and an authenticated customer and/or certain information indicative of a trusted relationship between the credential manager and service provider. When a request is authenticated, the service provider may provide a detailed customer receipt to the credential manager in a format that may be presented to the customer but that may not be used by the credential manager to easily access details conveyed by the receipt.