Iframe Domain Validation for Payment Form Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Online merchants face security vulnerabilities in payment processing due to malicious actors bypassing security measures through fake iframe injection in payment forms, leading to potential theft of customer financial information.

Innovation Solution

A system and method that detects payment forms on online merchant websites, identifies iframes, and determines their association with trusted domains, performing security actions to prevent malware attacks by alerting users and preventing transaction completion if the iframe is unassociated with a trusted domain.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If PSP hosted iframe forms are used for payment processing, then security protection through Same Origin Policy is improved, but vulnerability to fake iframe injection attacks worsens

Engineering Contradiction:
Improvesecurity protectionVSAvoidfake iframe injection vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary validation by checking whether the iframe's domain matches the expected payment gateway domain before allowing the payment form to be displayed or submitted. This proactive domain verification prevents fake iframes from processing payments, addressing the security vulnerability while maintaining the benefits of hosted iframe forms

Inventive Principle:
Principle #10Preliminary action

2Reliability

If domain validation is performed on iframes, then protection against malware attacks is improved, but transaction processing time worsens

Engineering Contradiction:
Improvemalware attack protectionVSAvoidtransaction processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The domain validation is performed preliminarily during the iframe loading or form initialization phase, rather than during the actual payment submission. This timing strategy ensures that the validation overhead does not significantly impact the core transaction processing time, as the check is completed before the user initiates the payment

Inventive Principle:
Principle #10Preliminary action

3Reliability

If security validation of iframe domains is implemented, then customer payment data protection is improved, but ease of operation worsens

Engineering Contradiction:
Improvepayment data protectionVSAvoidtransaction completion ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs automatic domain validation without requiring user intervention. The validation logic independently checks the iframe domain against the trusted domain list and either permits or blocks the transaction automatically, maintaining ease of operation for legitimate transactions while providing robust protection

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11810117B1Systems and methods for protecting customer payment data against malware attacks on inline frame payment forms
Publication Date: 2023.11.07 GEN DIGITAL INC
  • US11810117B1 patent drawing
  • US11810117B1 patent drawing
  • US11810117B1 patent drawing

AI summary

The disclosed computer-implemented method for protecting customer payment data against malware attacks on inline frame payment forms may include (i) detecting a payment form in a payment page on an online merchant website (e.g., by monitoring the website for a user entry of payment information during a customer transaction session or by analyzing, in hypertext markup language associated with an inline frame (iframe), a document object model (DOM)) to identify the payment form, (ii) identifying the iframe on the online merchant website, (iii) determining whether the iframe is associated with a trusted domain utilized for processing the payment information to complete the customer transaction session, and (iv) performing a security action that protects against a potential malware attack by preventing completion of the customer transaction upon determining that the iframe is unassociated with the trusted domain. Various other methods, systems, and computer-readable media are also disclosed.