Cross-Device Payment Method Synchronization via ODCDA
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face frustration and inefficiency when replicating data, particularly payment preferences, across multiple devices and applications, leading to increased cognitive burden and fragmented payment options.
Innovation Solution
The implementation of On Device and Cross-device Authentication (ODCDA) technologies, which utilize a hierarchy of tokens and secure token federations to manage user consent and payment methods across multiple applications and devices, enabling a global payment method (GPM) to be automatically applied across trusted devices and applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a user manually replicates data from one device to another device, then data can be transferred between devices, but the process becomes time-consuming and frustrating
Solution Approach 1:
The patent implements automatic copying of user data, preferences, and payment methods from a source device to a target device through cloud synchronization. When a user sets up a new device, the system automatically retrieves and replicates relevant data without requiring manual intervention, thus maintaining data completeness while eliminating time consumption.
Solution Approach 2:
The system performs preliminary synchronization of user data to a cloud service before the user needs it. When a new device is activated, the data is already prepared and ready for automatic transfer, eliminating the need for users to manually copy data at the moment of device transition.
2Adaptability or versatility
If a user manually configures each application on a new device, then application functionality can be restored, but the process becomes increasingly complex with more apps
Solution Approach 1:
The patent creates a universal user profile that encompasses multiple applications and their configurations. This single profile structure can represent settings for numerous applications simultaneously, allowing all app configurations to be managed through one unified mechanism rather than requiring separate configuration steps for each application.
Solution Approach 2:
The system merges individual application configurations into a unified user profile that is stored in the cloud. Instead of treating each application's settings as separate entities requiring individual configuration, the patent combines them into a single replicable unit that transfers together, dramatically reducing the number of configuration steps required.
3Adaptability or versatility
If payment methods are managed separately in each application, then each application can control its own payment options, but users face fragmented payment options across applications
Solution Approach 1:
The patent implements a universal payment method representation that can be used across multiple applications. A single payment method configured in the user profile becomes available to all applications that support it, allowing users to manage payment methods in one place while maintaining broad payment capability across the entire application ecosystem.
4Ease of operation
If user data is synchronized across multiple devices, then seamless experience is achieved, but security risks may increase
Solution Approach 1:
The patent introduces a cloud service as an intermediary between devices and user data. Instead of devices directly sharing sensitive information with each other, all data synchronization goes through the secure cloud infrastructure, which acts as a trusted mediator. This maintains cross-device usability while centralizing security controls and reducing direct exposure of sensitive data.
Data Source
AI summary
Systems and methods for managing user data across multiple applications and devices are disclosed. An example method includes: detecting a user is conducting a transaction using a first application installed on a user device; determining that the user is requesting one or more payment options from a first merchant associated with the first application; determining that a global payment method is selected by the user; determining that the user device is a trusted device associated with the user; and in response to determining that the user device is a trusted device, providing the global payment method to the user in the first application on that same device or a different device.