Payment Card Signing via Cloud POS for Document Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack an efficient and cost-effective method for electronically signing and authenticating documents using payment cards, requiring separate infrastructure and resources for document signing and authentication.

Innovation Solution

A cloud point of sale (POS) server leverages the encryption capabilities of payment cards, such as EMV cards, to generate and store document hashes using private keys, creating a unique signature identifier (ID) for authentication, eliminating the need for a separate electronic signature infrastructure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a separate electronic signature infrastructure is established, then document signing and authentication capability is provided, but system complexity and resource costs increase

Engineering Contradiction:
Improvedocument signing capabilityVSAvoidinfrastructure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by enabling payment cards to serve dual purposes: their original payment function and a new document signing function. The payment card's existing cryptographic infrastructure (private key stored in secure element) is repurposed to generate digital signatures for documents, eliminating the need for dedicated signature devices or infrastructure.

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

Solution Approach 2:

The patent merges the document signing functionality with the existing payment card infrastructure. Instead of maintaining separate systems for payments and digital signatures, the solution combines these functions by using the payment card's secure element and cryptographic capabilities to perform both payment authentication and document signing operations through a unified interface.

Inventive Principle:
Principle #5Merging (Combining)

2Device complexity

If payment card infrastructure is used for document signing, then resource costs and system complexity are reduced, but authentication capability must be verified

Engineering Contradiction:
Improveinfrastructure complexityVSAvoidauthentication reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent introduces a server as an intermediary that facilitates the authentication process. The server receives the document hash and signature ID from the user, retrieves the corresponding public key from its stored records, performs the cryptographic verification, and returns the authentication result. This intermediary layer ensures reliable verification while keeping the user's payment card infrastructure simple.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The authentication system implements feedback by providing clear authentication results (valid/invalid) to the user through the server. The server compares the provided signature ID against stored records, verifies the cryptographic signature using the associated public key, and returns a definitive authentication outcome, enabling users to understand whether their document signing is verified.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12536546B2Electronically signing a document using a payment card
Publication Date: 2026.01.27 MASTERCARD INT INC
  • US12536546B2 patent drawing
  • US12536546B2 patent drawing
  • US12536546B2 patent drawing

AI summary

A computerized method electronically signs and authenticates documents using cards with associated private keys. A hash of a document is obtained from a user by a cloud point of sale (POS) server and a document signing request to sign the obtained hash with a card is received. The document signing request is received via the presentation of the card. The server causes the obtained hash to be signed using the private key of the card and an associated signature ID is generated. The signed hash and generated signature ID are stored, and the generated signature ID is provided to the user for use in future authentication of the document. Later, a document authentication request is received that includes the generated signature ID and a hash of a target document to be authenticated. The signed hash is decrypted and compared to the hash of the target document to determine its authenticity.