Mobile Device Magnetic Stripe Decoding System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current magnetic stripe card readers are not suitable for conducting financial transactions between individuals on mobile devices, lacking the capability to decode signals from magnetic stripe cards for non-merchant transactions and ensuring secure identity confirmation.

Innovation Solution

A decoding system integrated into a mobile device that includes a miniaturized card reader with a decoding engine and transaction engine, capable of decoding signals from magnetic stripe cards, confirming identities, and facilitating secure financial transactions by communicating with user, product, and transaction databases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional magnetic stripe readers are used, then card reading capability is provided, but portability and ease of operation for individual-to-individual transactions are compromised

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent combines the card reader functionality with a mobile device, merging two separate systems into one integrated unit. The mobile device houses both the decoding engine for processing magnetic stripe signals and the transaction engine for conducting financial transactions, eliminating the need for separate conventional card reading equipment and enabling portable P2P transactions.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The mobile device is designed to perform multiple functions: it serves as both a general-purpose computing device and a specialized card reading/transaction device. The universal design allows the same device to handle various transaction types (merchant transactions and individual-to-individual transactions) without requiring specialized equipment for each use case.

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

2Adaptability or versatility

If conventional card readers are used for merchant transactions, then transaction processing is enabled, but capability for individual-to-individual transactions is lacking

Engineering Contradiction:
ImproveadaptabilityVSAvoidreliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The transaction engine is designed to handle multiple transaction types through a universal interface. It can process both traditional merchant transactions (where a merchant verifies cardholder identity) and individual-to-individual transactions (where the receiving individual directly verifies identity). This multi-functionality enables the system to adapt to different transaction scenarios while maintaining security through consistent verification protocols.

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

Solution Approach 2:

The system dynamically adapts its operation mode based on the transaction type. For merchant transactions, it follows traditional verification flows; for P2P transactions, it switches to a mode where the receiving individual performs verification. This dynamic behavior allows the same hardware to serve multiple purposes reliably.

Inventive Principle:
Principle #15Dynamics

3Loss of information

If magnetic stripe data is read and decoded, then transaction information is obtained, but security against fraud is insufficient without identity confirmation

Engineering Contradiction:
Improvedata accuracyVSAvoiddevice complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system implements feedback loops for identity verification. The transaction engine receives decoded card data, then prompts for additional verification information (such as CVV code, expiration date, or biometric data). This feedback mechanism ensures that only authenticated users can complete transactions, preventing fraud while maintaining data accuracy through multiple verification checkpoints.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary identity verification actions before finalizing the transaction. Before processing the magnetic stripe data, the system requires additional authentication steps (such as entering a PIN, verifying CVV, or biometric confirmation). This preliminary action ensures that even if card data is compromised, unauthorized transactions cannot be completed.

Inventive Principle:
Principle #10Preliminary action

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

Enables secure and convenient financial transactions between individuals using magnetic stripe cards on mobile devices, preventing credit fraud through identity confirmation and efficient data processing.

Implementation Method 1

The magnetic stripe card is capable of storing data by modifying the magnetism of magnetic particles embedded in the stripe. The data stored on the magnetic stripe may be sensed or read by swiping the stripe past a read head.

Methodology Applied
Scientific EffectMagnetic Field: Magnetic Field

Data Source

PatentUS8640953B2Decoding system running on a mobile device and coupled to a payment system that includes at least one of, a user database, a product database and a transaction database
Publication Date: 2014.02.04 BLOCK INC
  • US8640953B2 patent drawing
  • US8640953B2 patent drawing
  • US8640953B2 patent drawing

AI summary

A decoding system runs on a mobile device and is coupled to a payment system. The decoding engine decodes signals produced from a read of a first party's financial transaction card. A transaction engine runs on the mobile device and is coupled to the decoding engine. The transaction engine receives as its input decoded first party's financial transaction card information from the decoding engine. A payment system, in communication with the transaction engine, includes at least one of, a user database, a product database, and transaction database.