Mobile Credential Conversion via Application Identifier

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The process of updating payment account credentials on mobile devices is often time-consuming and cumbersome for users, as they need to manually provision new credentials for different types of accounts, which can be inconvenient and inefficient.

Innovation Solution

The system utilizes an application identifier (AID) specific to a new account type to automate the provisioning of credentials on mobile devices, allowing issuers to directly convert credentials from one type to another without user involvement, leveraging tokens and a digital platform to facilitate this conversion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual provisioning of credentials is used, then users can update payment account credentials, but the process becomes time-consuming and cumbersome

Engineering Contradiction:
Improveease of credential updateVSAvoidtime for credential update
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by detecting account type changes and automatically provisioning new credentials before the user needs to manually update them. The credential conversion is initiated automatically when an account type change is detected, eliminating the need for users to manually start the update process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by allowing the mobile device to automatically detect account type changes and trigger credential conversion without user intervention. The device autonomously manages the credential update process, including detecting changes, initiating conversion, and provisioning new credentials.

Inventive Principle:
Principle #25Self-service

2Extent of automation

If automated credential conversion is implemented, then user convenience is improved, but system complexity increases

Engineering Contradiction:
Improveautomation of credential conversionVSAvoidcomplexity of credential management system
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system introduces intermediary components including a credential conversion service and account type change detector that mediate between the user's payment account and the credential storage. These intermediaries handle the complex conversion logic and coordinate between different system components, managing complexity through structured intermediary layers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The credential management system is segmented into distinct functional modules: account type change detector, credential conversion service, and token management components. Each module handles a specific aspect of the conversion process, allowing independent development, testing, and maintenance of individual components while reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20240330910A1Systems and methods for use in account credential conversion
Publication Date: 2024.10.03 MASTERCARD INT INC
  • US20240330910A1 patent drawing
  • US20240330910A1 patent drawing
  • US20240330910A1 patent drawing

AI summary

Systems and methods are provided for converting account credentials in mobile devices. An example method includes receiving a request to digitize a second account in a mobile device, in place of a first account, and determining a type of the second account is different than a type of the first account. The method also includes identifying a first application identifier (AID) for the second account and transmitting, to a digital platform computing device, a request to digitize the second account to the mobile device. The method then further includes receiving, from the digital platform computing device, a notice to digitize the second account to an instance of the application for the second account in the mobile device, where the notice includes an AID for the first account, validating the AID for the first account, and generating and transmitting personalization data to the digital platform computing device.