URL Medium Payment System Using Vault Server Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current payment and charging systems face challenges in providing a simpler, more economical, and secure means of transaction that can support various types of transactions, including face-to-face and non-face-to-face transactions, while preventing hacking and reducing fees.
Innovation Solution
A payment and charging system that utilizes a URL medium to store and deliver a vault URL, allowing for transactions to be processed through an external device connected to the Internet, using a VS to manage payments and charging requests, and supporting additional services like provisional payments and coupon charging.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a URL medium is used to store and deliver vault URLs for internet-based transactions, then transaction simplicity and economy are improved, but security vulnerability to hacking increases
Solution Approach 1:
The patent introduces a VS (Vault Server) as an intermediary between the URL medium and the actual money storage. The VS manages the vault accounts and processes payment commands, acting as a secure mediator that handles sensitive financial operations while the URL medium only stores and transmits the vault URL, not the money itself. This separation reduces security risks associated with direct access to funds.
Solution Approach 2:
The system segments the payment function into distinct components: the URL medium stores only the vault URL (access information), the VS manages the vault account and processes transactions, and the money remains stored in the vault account. This segmentation ensures that no single component holds all sensitive elements, reducing the impact of potential hacking at any individual point.
2Adaptability or versatility
If multiple payment systems (RF card, URL-NFC CC, App&SP) are used to support various transactions, then transaction versatility is improved, but system complexity and fees increase
Solution Approach 1:
The patent creates a universal payment system where a single URL medium can be used for multiple types of transactions (face-to-face, non-face-to-face, provisional payments, coupon charging) through a common VS platform. The VS handles different transaction types using the same basic architecture of URL storage, vault account management, and payment command processing, eliminating the need for separate systems for each transaction type.
3Reliability
If user confirmation is required for face-to-face transactions, then transaction security is improved, but transaction speed and convenience deteriorate
Solution Approach 1:
The system performs user verification in advance through TD (Terminal Device) that confirms user identity before the actual payment transaction. The VS receives verified user information and transaction details beforehand, so when the payment command is executed using the URL medium, the transaction can be processed quickly without requiring additional real-time user confirmation steps.
Data Source
AI summary
Not using any app, a URL medium including a vault URL containing a property of an ID of a user is used during a user confirmation process and a transaction request process (a payment request process or a charging request process), and transaction (a payment or a charging) is made using money from an external device (a URL vault account), not the URL medium. A URL medium can support a way of requesting a transaction (a payment or a charging) after checking a user, or can support a way of confirming a user after requesting a transaction (a payment or a charging). A URL medium can support offline transactions and online transactions, and two URL medium (a URL medium-B of a buyer and a URL medium-S of a seller) can support offline transactions that do not use a POS (a URL POS). A URL medium can also support transactions that temporarily approve a payment.


