IP Library Granted Patent US 11,210,661
Granted Patent B2
US 11,210,661 · App. 16/508,090 · Granted Dec 28, 2021

Method for providing payment gateway service using UTXO-based protocol and server using same

Inventors: Jay Wu Hong (Seoul, KR); Moon Gju Suh (Seoul, KR)
Assignee: COINPLUG, INC.
G06Q20/3821G06Q20/027G06Q20/3227G06Q20/3829G06Q20/4012H04L9/0637
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,210,661
App. No.
16/508,090
Granted
Dec 28, 2021
Kind
B2
Abstract

The present disclosure relates to a method for providing a payment agency service and a server using same, and a method for registering an authentication certificate, a method for providing a payment agency service, a card company server, and a payment agency server. The method comprises steps of a payment agency server: (a) delivering identity authentication information and a first push token ID delivered from a user terminal to a card company server; (b) delivering a successful authentication result to the user terminal to support generating and saving a public key and a private key of the user; and (c) managing the first push token ID or a second push token ID as an integrated push token ID when the first push token ID and the second push token ID match, and saving registration information including the integrated push token ID and the public key.

Claims (15)

1. A method for registering an authentication certificate for a payment gateway service, comprising:

receiving from a user device, by a payment gateway server, identity authentication information and a unique 1-st push token ID, wherein the unique 1-st push token ID is associated with a push service to the user device;

transmitting, by the payment gateway server, the identity authentication information and the 1-st push token ID to a card service providing server;

receiving, by the payment gateway server, an authentication result from the card service providing server;

transmitting, by the payment gateway server, the authentication result to the user device;

receiving, at the user device, biometric information input into the user device;

in response to receiving the biometric information at the user device, generating, by the user device, a public/private key pair for the user, wherein the public/private key pair for the user corresponds to the biometric information;

receiving from the user device, by the payment gateway server (i) a public key of the public/private key pair for the user of the user device and (ii) a 2-nd push token ID corresponding to the 1-st push token ID;

storing in a private blockchain database, by the payment gateway server, registration information including an identifier of a push token and the public key, wherein the identifier of a push token is one of the 1-st push token ID or the 2-nd push token ID;

determining whether an anchoring condition is satisfied, wherein the anchoring condition is one of (i) acquiring a certain number of a specific hash value and a neighboring hash value, (ii) determining whether a certain amount of time has elapsed, (iii) generating a block in the private blockchain database, and (iv) a condition including one or more characteristics of services;

in response to the anchoring condition being satisfied, generating, by a card service providing server, from transactions stored in the private blockchain database, a representative hash value, where the representative hash value is generated by a hashing calculation using both (i) a specific hash value which is a hash value of the registration information and (ii) its corresponding at least one neighboring hash value which is one of (ii-1) a hash value of a specific registering transaction which is specific registration information including a specific push token ID and a public key of a specific user and (ii-2) a hash value of a specific payment-proving transaction which is transaction information including at least part of a specific hash value of a device identification information, the specific push token ID, and specific payment subject information;

storing in a public blockchain database, by the card service providing server, the representative hash value generated from transactions stored in the private blockchain database;

verifying, by the card service providing server, an integrity of the private blockchain database, wherein the verification includes comparing (i) the representative hash value and (ii) the corresponding representative hash value stored in the public blockchain database by the card service providing server.

2. The method of claim 1 , further comprising: transmitting to the user device, by the payment gateway server, a completion of registration of a certificate message.

3. The method of claim 1 , wherein the identity authentication information includes at least one of a name of the user, a phone number of the user, a number of a credit card of the user, and a CVC (Card Verification Value) of the credit card of the user.

Assignments (2)
CHANGE OF NAME Recorded Nov 20, 2023
From: COINPLUG, INC.
To: CPLABS, INC.
Reel/Frame 065628/0785 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 10, 2019
From: HONG, JAY WU; SUH, MOON GJU
To: COINPLUG, INC.
Reel/Frame 049720/0805 →
Priority Claims (1)
KR 10-2017-0004421 · Jan 11, 2017 · national
Continuity (2)
Continuation PCTKR2018000475 · Jan 10, 2018
Related Publication 20190333058A1 · Oct 31, 2019
Cited By (1)
US 12,388,822