API Gateway Policy Engine for Privacy-Safe Fraud Screening
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Financial institutions are vulnerable to fraud when new account holders provide inaccurate information, leading to unpaid debts, and existing systems lack efficient methods to assess the risk of new participants using information from wireless communication service providers without compromising subscriber confidentiality.
Innovation Solution
A system and method that enables institutions to access non-confidential, obfuscated information about potential new customers through a single API gateway, allowing risk assessments while protecting subscriber privacy, and includes asynchronous logging and policy-based record processing to manage transactions efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If financial institutions access detailed subscriber information to assess risk, then fraud prevention capability is improved, but subscriber confidentiality is compromised
Solution Approach 1:
The patent introduces an intermediary system that sits between the subscriber data source and the financial institution. This intermediary retrieves detailed subscriber information, applies obfuscation rules to protect confidentiality, and returns sanitized risk assessment data to institutions. The intermediary acts as a mediator that enables fraud prevention while preserving subscriber privacy through controlled information disclosure.
Solution Approach 2:
The system extracts only the necessary risk assessment information from complete subscriber records, separating useful risk indicators from confidential personal data. By taking out only the essential elements needed for fraud prevention (such as verification status without personal identifiers), the system enables risk assessment while removing information that would compromise subscriber confidentiality.
2Adaptability or versatility
If the system provides customized information bundles to different institutions, then adaptability is improved, but device complexity increases
Solution Approach 1:
The patent segments the information delivery system into modular components: a configuration module that defines information bundles, a retrieval module that fetches data, and a delivery module that sends customized responses to different institutions. This segmentation allows each component to handle specific tasks independently, enabling customized information bundles for different institutions while managing system complexity through clear separation of concerns.
Solution Approach 2:
The system implements a universal gateway interface that handles multiple types of information requests from different financial institutions through a single unified entry point. This universal interface can deliver customized information bundles to various institutions without requiring separate systems, achieving adaptability while reducing overall complexity through consolidation.
3Reliability
If the system logs all transactions for audit purposes, then accountability is improved, but processing time increases
Solution Approach 1:
The system performs preliminary logging actions during the transaction processing itself, capturing essential audit information in real-time without requiring separate post-processing steps. By recording transaction data as it occurs rather than after completion, the system maintains accountability while avoiding additional processing delays.
Solution Approach 2:
The patent implements asynchronous logging where transaction recording occurs in the background without blocking the main processing flow. Critical transaction data is quickly captured and logged without waiting for complete processing, allowing the system to rush through essential logging actions to maintain accountability while minimizing impact on processing time.
Data Source
AI summary
A method of providing information on subscribers by a telecommunication service provider based on subscriber accounts. The method comprises receiving a plurality of requests for subscriber information by an application programming interface (API) of a gateway application; sending responses to the requests comprising filtered information about subscribers by the API; sending a log about each of the responses by the gateway application to a transaction recording application; processing the logs by the transaction recording application to produce transaction records based on a plurality of policies, wherein the policies define how records on requests from different partner institutions are to be recorded and wherein the transaction records are stored in a transaction records data store table; and processing the transaction records stored in the transaction records data store table by the transaction recording application to generate a summarized transaction records data store table that comprises transactions summaries.