Mobile Device Risk Management via Transaction Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current payment systems using mobile devices face challenges in managing risk associated with fraud and unauthorized transactions, particularly in balancing convenience with security measures, especially for contactless payment transactions.

Innovation Solution

The integration of risk management techniques into payment-enabled mobile devices, which require users to acknowledge transactions or enter a PIN depending on the transaction amount, and utilize transaction counters and accumulators to enforce security protocols, ensuring secure and convenient contactless payments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If contactless payment transactions are processed without real-time authorization for small amounts, then transaction speed and convenience are improved, but security risk and potential fraud increase

Engineering Contradiction:
Improvetransaction speedVSAvoidfraud risk
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The system changes the authorization parameter based on transaction amount thresholds. Transactions below a predetermined threshold are processed offline without real-time authorization, while transactions above the threshold require online authorization. This parameter-based differentiation resolves the contradiction by enabling fast processing for low-risk transactions while maintaining security for high-risk ones.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The payment system is segmented into different processing modes: offline processing for small transactions and online processing for large transactions. This segmentation allows the system to optimize for speed for small amounts while optimizing for security for large amounts, effectively resolving the contradiction between transaction speed and fraud prevention.

Inventive Principle:
Principle #1Segmentation

2Object-affected harmful factors

If security measures such as PIN entry and transaction acknowledgment are required for all transactions, then fraud prevention is improved, but user convenience and transaction speed deteriorate

Engineering Contradiction:
Improvefraud preventionVSAvoiduser convenience
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The system dynamically changes security requirements based on transaction parameters, specifically the amount. Small transactions proceed without PIN entry or acknowledgment, while large transactions trigger security measures. This parameter-based adaptive security resolves the contradiction by applying minimal friction for low-risk transactions while maintaining strong security for high-risk transactions.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

Instead of applying full security measures to all transactions, the system applies partial security measures only when necessary. This partial action principle allows the system to maintain user convenience for most transactions while providing enhanced security only when the transaction amount warrants it, thus resolving the contradiction between security and convenience.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If transaction counters and accumulators are implemented to track spending patterns, then risk management and fraud detection are improved, but device complexity increases

Engineering Contradiction:
Improverisk managementVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The mobile device autonomously performs risk management by maintaining and evaluating transaction counters and accumulators locally. The device self-determines whether to proceed with offline or online processing based on its own tracking data, eliminating the need for complex centralized risk management systems. This self-service approach improves reliability while keeping device complexity manageable.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The risk management functionality is extracted from the centralized server and embedded within the mobile device itself. By taking out the risk management logic and placing it in the device, the system achieves better real-time risk assessment without requiring complex communication infrastructure or centralized processing, thus improving reliability with acceptable complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Applied Scientific Principles

This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.

Function Achieved in This Case

Enhances security by requiring user verification for higher-value transactions and managing risk through transaction categorization, thereby reducing fraud while maintaining convenience for low-value transactions.

Implementation Method 1

In other IC payment card systems, the exchange of information between the card and the POS terminal proceeds via wireless RF (radio frequency) communications

Methodology Applied
Scientific EffectRF (radio frequency) communications: Electromagnetic Induction

Implementation Method 2

It has also been proposed to use wireless exchanges of information via NFC (Near Field Communication) for payment applications

Methodology Applied
Scientific EffectNFC (Near Field Communication): Electromagnetic Induction

Data Source

PatentUS9947006B2Methods for risk management in payment-enabled mobile device
Publication Date: 2018.04.17 MASTERCARD INT INC
  • US9947006B2 patent drawing
  • US9947006B2 patent drawing
  • US9947006B2 patent drawing

AI summary

A payment-enabled mobile device receives, during a first tap of the mobile device on a proximity reader component of a point of sale (POS) terminal, first transaction context data for a current transaction, and receives during a second tap of the mobile device on the proximity reader component, second transaction context data for the current transaction. When the mobile device determines that the second tap is for the same transaction as the first tap, and that one of a customer verification method (CVM) status or a user acknowledgment status flag has been set, then it transmits a payment card account number to the POS terminal to consummate the transaction.