Credit Card Tokenization for Secure Payment Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current online payment systems risk customer data security as they store credit card information, leading to potential hacking and compliance issues with the Payment Card Industry Data Security Standard (PCI-DSS).

Innovation Solution

Implementing a secure credit card payment system where a merchant server only receives customer data related to a credit card, with the credit card data being sent to a separate token server that generates a token representing the credit card information, which is then stored and used for future payments, keeping the credit card data outside the merchant server's scope and reducing PCI-DSS compliance requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If credit card information is stored on the merchant server for future payments, then payment processing convenience is improved, but security risk and PCI-DSS compliance burden increase

Engineering Contradiction:
Improvepayment processing convenienceVSAvoidsecurity risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the sensitive credit card data from the merchant server environment by implementing a separate tokenization service. The credit card information is captured and replaced with tokens that are stored on the merchant server, while the actual sensitive data is held in a PCI-DSS compliant environment outside the merchant's control, thus eliminating the security risk while preserving payment convenience

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a tokenization service as an intermediary between the payment system and the merchant server. This intermediary captures credit card data, generates tokens, and manages the mapping between tokens and actual card information, allowing the merchant to process payments conveniently without directly handling or storing sensitive credit card data

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If credit card data is stored on the merchant server, then future payment processing is simplified, but PCI-DSS compliance requirements and costs increase

Engineering Contradiction:
Improvepayment processing efficiencyVSAvoidPCI-DSS compliance burden
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent removes the storage of sensitive credit card data from the merchant server infrastructure and places it in a separate, dedicated tokenization service environment that is already PCI-DSS compliant. This extraction eliminates the need for the merchant to implement and maintain complex PCI-DSS security measures while preserving the ability to process payments efficiently using stored tokens

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates token representations (copies) of credit card data that can be stored and processed on the merchant server without containing the actual sensitive information. These tokens function as substitutes that maintain payment processing efficiency while eliminating PCI-DSS compliance requirements for the merchant's systems

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20240303646A1System and Method for Secure Acceptance of Customer Credit Card Numbers
Publication Date: 2024.09.12 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US20240303646A1 patent drawing
  • US20240303646A1 patent drawing
  • US20240303646A1 patent drawing

AI summary

A method and system may provide a secure credit card payment service which allows a merchant to store credit cards without storing credit card data on merchant servers. The customer, via a web-enabled device, transmits a request to register a credit card and receives from the merchant server, a credit card registration webpage where the customer may provide credit card data and customer data. In response to receiving the credit card data and the customer data, the web-enabled device transmits the credit card data to a token server that stores the credit card data and receives a token from the token server. In response to receiving the token, the web-enabled device transmits the token and the customer data to the merchant server for storage and processing subsequent credit card payment transactions.