Third-Party Wallet FPAN Provisioning With Encrypted Card Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack secure methods for provisioning funding card numbers to third-party wallets while ensuring data privacy and security, particularly in e-commerce transactions.
Innovation Solution
Implementing systems and methods that utilize Public Key Infrastructure (PKI) for field-level encryption and symmetric keys to securely transport funding card numbers between issuers and merchants, with authentication and validation processes to ensure data protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If funding card numbers are provisioned to third-party wallets without encryption, then transaction processing is simplified and faster, but data security and privacy are compromised
Solution Approach 1:
The patent introduces an intermediary authentication and authorization server that mediates between the payment processor and third-party wallets. This server handles the complex encryption and validation operations, allowing the payment processor to maintain simple interfaces while achieving secure data provisioning through the intermediary's security mechanisms
Solution Approach 2:
The provisioning system is segmented into distinct functional components: authentication module, authorization module, encryption module, and validation module. Each component handles specific security tasks independently, allowing the system to achieve comprehensive security without requiring a single complex monolithic system
2Loss of information
If funding card numbers are encrypted during transmission, then data privacy is enhanced, but transmission time and processing complexity increase
Solution Approach 1:
The system performs preliminary authentication and authorization actions before the actual funding card number provisioning. By validating credentials and establishing security contexts in advance, the system minimizes the time required for the main encryption and transmission operations, as the preparatory work is already complete
Solution Approach 2:
The patent employs different encryption parameters and algorithms based on the specific provisioning scenario. The system adjusts encryption strength, key types, and transmission protocols dynamically to match the risk level and requirements of each transaction, optimizing the balance between security and processing speed
3Reliability
If multiple authentication and validation steps are implemented, then security against unauthorized access is improved, but the number of processing steps and system complexity increases
Solution Approach 1:
The authentication and authorization server is designed as a universal platform that performs multiple security functions through a single integrated system. It handles authentication, authorization, encryption key management, and validation all through one server infrastructure, reducing overall system complexity compared to having separate dedicated systems for each function
4Ease of manufacture
If funding card numbers are provided to merchants without encryption, then system operation is simpler, but security against data breaches and unauthorized use deteriorates
Solution Approach 1:
The intermediary authentication and authorization server acts as a secure mediator that protects funding card numbers during the provisioning process. It encrypts data before transmission to merchants and validates authentication credentials, thereby reducing data breach risks without requiring fundamental changes to the overall system architecture or implementation processes
Data Source
AI summary
Systems, methods, and devices for provisioning funding card numbers to merchant wallets are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for provisioning funding card numbers to third party wallets may include: (1) authenticating a customer using an electronic device; (2) redirecting the customer to a third-party website; (3) receiving, from the third-party website and via a first API, a request for funding primary account numbers (FPANs) associated with the customer; (4) providing the third-party website with a plurality of FPAN identifiers for FPANs associated with the customer; (5) receiving, from the third-party website and via a second API, a request for a FPAN associated with a selected FPAN identifier; (6) encrypting the FPAN associated with the selected FPAN identifier; and (7) communicating the encrypted FPAN to the third-party website.


