Multi-mode Digital Wallet for NFC and QR Code POS Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital wallet systems are limited in their ability to facilitate transactions at point of sale (POS) terminals that either support or do not support near field communication (NFC) transactions, and users with non-NFC-enabled mobile devices face difficulties in conducting payments using these systems.

Innovation Solution

A digital wallet system that allows users to register payment card information for access across various POS terminals, including NFC and QR code-enabled devices, enabling transactions through a mobile device that may or may not support NFC, by utilizing a remote wallet platform, tokenization service, and merchant acquirer systems to process payments using either NFC or QR code methods.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a digital wallet system is designed to support NFC transactions only, then transaction speed and convenience are improved at NFC-enabled POS terminals, but compatibility with non-NFC POS terminals deteriorates

Engineering Contradiction:
Improvetransaction convenienceVSAvoidPOS terminal compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The digital wallet system is designed to perform multiple payment functions by supporting both NFC and QR code transaction modes. The system automatically detects the POS terminal type and switches between NFC mode for contactless payments and QR code mode for non-NFC terminals, making the wallet universally compatible with different POS terminal types while maintaining transaction convenience

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If the system supports multiple payment modes (NFC and QR code), then adaptability to different POS terminals is improved, but system complexity increases

Engineering Contradiction:
ImprovePOS terminal compatibilityVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A server acts as an intermediary between the mobile device and various POS terminals. The server receives transaction requests from the mobile device, determines the appropriate payment mode based on POS terminal capabilities, and facilitates the transaction accordingly. This intermediary approach simplifies the mobile device architecture while maintaining multi-mode payment capability through centralized intelligence

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If NFC functionality is required for optimal performance, then transaction efficiency is improved, but accessibility for users with non-NFC devices deteriorates

Engineering Contradiction:
Improvetransaction efficiencyVSAvoiddevice compatibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

Instead of requiring the mobile device to have NFC capability, the system inverts the approach by using QR code technology that can be displayed on any mobile device screen. Non-NFC devices display QR codes that NFC-enabled POS terminals can read, while NFC devices can use either mode. This inversion allows users with non-NFC devices to access efficient payment transactions through QR code display and scanning

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS10664821B2Multi-mode payment systems and methods
Publication Date: 2020.05.26 MASTERCARD INT INC
  • US10664821B2 patent drawing
  • US10664821B2 patent drawing
  • US10664821B2 patent drawing

AI summary

Systems, methods, apparatus and computer program code are provided to receive payment card and mobile identity information from a mobile device associated with a user, determine account and mobile device eligibility and capability and in the case where the mobile device is NFC capable, triggering a tokenization process to generate a tokenization record associated with the payment card, storing the payment card information associated with the user securely, and transmitting card reference information associated with at least one of (i) the tokenization record, and (ii) the stored payment card information to the mobile device for use in transactions.