Sender-Configured Security Inputs for Money Transfer Fraud Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing money transfer systems lack effective fraud prevention mechanisms, particularly on the receiver side, due to varying compliance requirements and potential fraudulent activities such as 'grandparent fraud', where agents may deceive senders into sending money to impersonators.

Innovation Solution

A computer system that allows senders to select and require security inputs from receivers for authentication, which are stored and verified by a central server, ensuring only authenticated receivers can access and redeem the funds, thereby minimizing fraud.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If security inputs are required for money transfer redemption, then fraud prevention is improved, but transaction complexity increases

Engineering Contradiction:
Improvefraud preventionVSAvoidtransaction complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by having the sender pre-select and configure security inputs (such as PIN codes or identification requirements) when initiating the money transfer. These security parameters are stored in advance with the transaction details, so that during redemption, the receiver simply needs to provide the pre-configured security input without complex verification procedures. This resolves the contradiction by preparing security measures beforehand, maintaining fraud prevention while simplifying the actual redemption process.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If sender-selected security inputs are implemented, then fraud prevention is improved, but compliance requirement adherence becomes more complex

Engineering Contradiction:
Improvefraud preventionVSAvoidcompliance complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements a universal security input mechanism that can accommodate multiple compliance requirements through a single flexible framework. The sender can select from various types of security inputs (PIN codes, identification verification, biometric authentication) that can satisfy different jurisdictional compliance requirements. The server universally stores and verifies these inputs regardless of the specific compliance regime, thereby maintaining fraud prevention across diverse regulatory environments without requiring separate complex verification systems for each compliance standard.

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

3Reliability

If authentication verification is performed, then fraud prevention is improved, but transaction processing time increases

Engineering Contradiction:
Improvefraud preventionVSAvoidtransaction processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs authentication verification in advance by having the sender pre-configure and select security inputs when initiating the money transfer. The server stores these security parameters with the transaction details before the redemption occurs. During the actual redemption process, the verification simply involves checking whether the receiver provides the pre-configured security input, which is a straightforward comparison rather than a complex real-time authentication process. This preliminary configuration maintains strong fraud prevention while minimizing the time required during the actual transaction completion.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8751395B2Verification methods for fraud prevention in money transfer receive transactions
Publication Date: 2014.06.10 MONEYGRAM INTERNATIONAL INC
  • US8751395B2 patent drawing
  • US8751395B2 patent drawing
  • US8751395B2 patent drawing

AI summary

A computer system is operated to prevent fraud in a money transfer receive transaction. A send transaction request is received from a sender for a money transfer including a send amount. The sender is prompted to select one or more security inputs to be supplied by a receiver for redemption of the money transfer. A send transaction record is stored with the selected one or more security inputs in a server. A receive transaction request is then received from the receiver. The receiver is prompted for the one or more security inputs set for redemption of the money transfer, and the provided one or more security inputs from the receiver are received. The received one or more security inputs are authenticated, and release of funds in the send amount is authorized if the received one or more security inputs are authenticated.