PPAN Mapping for Secure Mobile Payment Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Deploying payment account numbers to mobile devices in a timely, efficient, and secure manner is challenging for payment account issuers, especially when implementing proximity payment devices like contactless payment cards or mobile devices.
Innovation Solution
A proximity payment account number (PPAN) mapping mechanism is introduced, where PPANs are pre-personalized and personalized on mobile devices, allowing secure exchange of purchase transaction data without deploying the actual primary account number (PAN), using a PPAN-PAN mapping system that translates PPANs to PANs during authorization processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If payment account numbers are deployed to mobile devices for proximity payment transactions, then payment convenience and security are improved, but deployment complexity and time requirements increase
Solution Approach 1:
The patent introduces a proximity payment account number (PPAN) as an intermediary that maps to the actual payment account number (PAN). The PPAN is deployed to the mobile device instead of the real PAN, acting as a secure proxy that enables transactions without exposing the actual account credentials. This resolves the contradiction by maintaining security while simplifying deployment.
Solution Approach 2:
The patent segments the payment account information into two distinct parts: the PPAN (stored on the mobile device) and the PAN (kept secure on the server). This segmentation allows the mobile device to have payment functionality without containing the full sensitive account information, thereby improving security and reducing deployment complexity.
2Adaptability or versatility
If actual payment account numbers are deployed to mobile devices, then transaction functionality is improved, but security risks increase
Solution Approach 1:
The PPAN serves as an intermediary between the mobile device and the actual payment account. It enables full transaction functionality while preventing direct exposure of the PAN, thus maintaining versatility while reducing security risks.
Solution Approach 2:
The system creates a functional copy (PPAN) that mimics the behavior of the actual account number for transaction purposes, but without containing the sensitive underlying data. This copy enables transactions while eliminating the security risks of storing or transmitting the real PAN.
3Productivity
If payment account numbers are deployed quickly to mobile devices, then user convenience is improved, but security control is worsened
Solution Approach 1:
The PPAN is pre-configured and deployed to the mobile device in advance, enabling rapid deployment. The actual PAN mapping is established beforehand through secure channels, allowing quick provisioning without compromising security control.
Solution Approach 2:
The PPAN intermediary enables rapid deployment of payment functionality while the secure mapping to PAN is maintained separately, allowing speed without sacrificing security control.
Data Source
AI summary
Methods and systems for receiving a proximity payment account number (PPAN) with payment transaction data for a payment transaction from a mobile device, the PPAN selected from at least one PPAN; mapping the received PPAN to a primary account number (PAN); generating an authorization request for the payment transaction based on the PAN and the payment transaction data; receiving an authorization response message; and providing an output including the authorization response message and the PPAN.