IN ONLINE TRANSACTIONS A PAYMENT SYSTEM OR A PAYMENT METHOD USING A CREDIT CARD THAT CAN LINK WITH A URL

Abstract

In online payment using the URL&CC, the routes of the payment request process and the user confirmation process are different and the order of these can be changed. (Payment method 1) Payment method 1 first requests payment by using the URL&CC's CCI path, and confirms the user by using the URL&CC's URL path and the user's URL PWD path. (Payment method 2) Payment method 2 confirms the user by using the URL&CC's URL path and the user's URL PWD path, and requests the payment by using the URL&CC's CCI path.

Claims

1. An online payment system, comprising: a URL&CC that can store CCI and a URL, deliver the CCI to a user, and deliver the URL to a SD; the SD that can connect to a URL&SS in response to the user's access order, communicate a sales site, etc. with the URL&SS or the user, receive the CCI and a payment request including order details from the user, deliver the CCI and the payment request to the URL&SS, receive the URL from the URL&CC, connect to a URL&CCWS in response to the URL, communicate SD information, etc. with the URL&CCWS, communicate a URL&CC site, etc. with the URL&CCWS or the user, receive a URL PWD from the user, deliver the URL PWD to the URL&CCWS, receive a URL PWD check result, the order details, etc. from the URL&CCWS, deliver the URL PWD check result, the order details, etc. to the user, deliver the user's an order confirmation to the URL&CCWS, and deliver a payment result of the URL&SS or the URL&CCWS to the user; the URL&SS that can connect to the SD, communicate the sales site, etc. with the SD, receive the CCI and the payment request from the SD, deliver the CCI, the payment request, etc. to a URL&CCPS, and deliver the URL&CCPS's the payment result to the SD; the URL&CCWS that can receive the order details, etc. from the URL&CCPS, connect to the SD, communicate the SD information, the URL&CC site, etc. with the SD, receive the URL PWD from the SD, deliver the URL PWD check result, the order details, etc. to the SD, receive the order confirmation from the SD, deliver the order confirmation to the URL&CCPS, and deliver the URL&CCPS's the payment result to the SD; and the URL&CCPS that can receive the CCI, the payment request, etc. from the URL&SS, deliver the order details, etc. to the URL&CCWS, receive the order confirmation from the URL&CCWS, and deliver the payment result to the URL&SS or the URL&CCWS in response to the payment request, the order confirmation, etc.

2. An online payment method, comprising: step a) in which a SD connects to a URL&SS in response to a user's access order, and communicates a sales site, etc. with the URL&SS or the user; step b) in which a URL&CC delivers CCI to the user; step c) in which the SD receives the CCI and a payment request including order details from the user, and delivers the CCI and the payment request to the URL&SS; step d) the URL&SS delivers the CCI, the payment request, etc. to the URL&CCPS; step e) the URL&CCPS delivers the order details, etc. to a URL&CCWS; step f) the URL&CCWS manages the order details, etc.; step g) the SD receives a URL from the URL&CC, connects to the URL&CCWS in response to the URL, communicates SD information, etc. with the URL&CCWS, communicates a URL&CC site, etc. with the URL&CCWS or the user, receives a URL PWD from the user, delivers the URL PWD to the URL&CCWS, receives a URL PWD check result, the order details, etc. from the URL&CCWS, delivers the URL PWD check result, the order details, etc. to the user, receives an order confirmation from the user, and delivers the order confirmation to the URL&CCWS; step h) in which the URL&CCWS delivers the order confirmation to the URL&CCPS; step i) in which the URL&CCPS delivers the payment result to the URL&SS or the URL&CCWS in response to the payment request, the order confirmation, etc.; and step j) in which the URL&SS or the URL&CCWS delivers the payment result to the SD; and the SD delivers the payment result to the user.

3. An online payment system, comprising: a URL&CC that can store CCI and a URL, deliver the CCI to a user, and deliver the URL to a SD; the SD that can receive the URL from the URL&CC, connect to a URL&CCWS in response to the URL, communicate SD information, etc. with the URL&CCWS, communicate a URL&CC site, etc. with the URL&CCWS or the user, receive a URL PWD from the user, deliver the URL PWD to the URL&CCWS, receive a URL PWD check result, etc. from the URL&CCWS, deliver the URL PWD check result, etc. to the user, receive a payment reservations from the user, deliver the payment reservation to the URL&CCWS, connect to a URL&SS in response to the user's access order, communicate a sales site, etc. with the URL&SS or the user, receive the CCI and a payment request from the user, deliver the CCI and the payment request to the URL&SS, receive a payment result from the URL&CCWS or the URL&SS, and deliver the payment result to the user; the URL&CCWS that can connect to the SD, communicate the SD information, the URL&CC site, etc. with the SD, receive the URL PWD from the SD, deliver the URL PWD check result, etc. to the SD, receive the payment reservation from the SD, deliver the payment reservation, etc. to URL&CCPS, and deliver the URL&CCPS's the payment result to the SD; the URL&SS that can connect to the SD, communicate the sales site, etc. with the SD, receive the CCI and the payment request from the SD, deliver the CCI, the payment request, etc. to the URL&CCPS, and deliver the URL&CCPS's the payment result to the SD; and the URL&CCPS that can receive the payment reservation, etc. from the URL&CCWS, receive the CCI, the payment request, etc. from the URL&SS, and deliver the payment result to the URL&CCWS or the URL&SS in response to the payment reservation, the payment request, etc.

4. An online payment system, comprising: step a) in which a URL&CC delivers a URL to a SD; step b) in which the SD connects to a URL&CCWS in response to the URL, communicates SD information, etc. with the URL&CCWS, communicates a URL&CC site, etc. with the URL&CCWS or the user, receives a URL PWD from the user, delivers the URL PWD to the URL&CCWS, receive a URL PWD check result, etc. from the URL&CCWS, deliver the URL PWD check result, etc. to the user, receive a payment reservation from the user, and deliver the payment reservation to the URL&CCWS; step c) in which the URL&CCWS delivers the payment reservation, etc. to a URL&CCPS; step d) in which the SD connects to a URL&SS in response to the user's access order, and communicates a sales site, etc. with the URL&SS or the user; step e) in which the URL&CC delivers CCI to the user; step f) in which the SD receives the CCI and a payment request from the user, and delivers the CCI and the payment request to the URL&SS; step g) in which the URL&SS delivers the CCI, the payment request, etc. to the URL&CCPS; step h) in which the URL&CCPS delivers a payment result to the URL&CCWS or the URL&SS in response to the payment reservation, the payment request, etc.; and step i) in which the URL&CCWS or the URL&SS delivers the payment result to the SD; and the SD delivers the payment result to the user.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0075] FIG. 1 is an existing payment system that uses an existing credit card and uses CCI (=credit card information), PI (=personal information), and a payment request through one path.

[0076] FIG. 2 is a flow chart of FIG. 1.

[0077] FIG. 3 is a payment system that checks a user through the other path supporting a URL, URL PWD, or others, after requesting a payment through one path supporting CCI, etc.

[0078] FIG. 4 is a flow chart of FIG. 3.

[0079] FIG. 5 is a payment system that requests a payment through the other path supporting CCI, etc., after checking a user through one path supporting a URL, a URL PWD, or others.

[0080] FIG. 6 is a flow chart of FIG. 5.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

[0081] Hereinafter, preferred embodiments of the present invention are described in detail with reference to the accompanying drawings. The terms used herein should be interpreted not in typical or dictionary definitions but to comply in concept with the technical matters of the present invention.

[0082] The configurations disclosed in the specification and the drawings are mere examples and do not overall represent the technical spirit of the present invention. Therefore, various changes may be made thereto, and equivalents thereof also belong to the scope of the present invention.

[0083] URL (Uniform Resource Locator) is the location of a web document or a file in a web server that provides various services.

[0084] <An Online Payment System that Confirms a User after Requesting Payment, See FIG. 3>

[0085] An online payment system, comprising: a URL&CC that can store CCI, a URL, etc., deliver CCI to a user, or deliver a URL to a SD; a SD that can connect to a URL&SS in response to a user's access order, communicate a sales site, etc. with a URL&SS or a user, receive CCI, a payment request including order details, or others from a user, deliver CCI, a payment request, or others to a URL&SS, receive an order #, etc. from the URL&SS, deliver an order #, etc. to a user, receive a URL from a URL&CC, connect to a URL&CCWS in response to a URL, communicate SD information, etc. with a URL&CCWS, communicate a URL&CC site, etc. with a URL&CCWS or a user, receive a URL PWD, etc. from a user, deliver a URL PWD, etc. to a URL&CCWS, receive a URL PWD check result, an order details, or others from a URL&CCWS, deliver a URL PWD check result, an order details, or others to a user, deliver a user's an order confirmation, etc. to a URL&CCWS, or deliver a payment result of a URL&SS or URL&CCWS to a user; a URL&SS that can connect to a SD, communicate a sales site, etc. with a SD, receive CCI, a payment request, or others from a SD, deliver an order #, etc. to a SD, deliver URL&SS information, CCI, a payment request, or others to a URL&CCPS, or deliver a URL&CCPS's payment result, etc. to a SD; a URL&CCWS that can receive an order details, etc. from a URL&CCPS, connect to a SD, communicate SD information, a URL&CC site, or others with a SD, receive a URL PWD, etc. from a SD, deliver a URL PWD check result, an order details, or others to a SD, receive an order confirmation, etc. from a SD, deliver an order confirmation, etc. to a URL&CCPS, or deliver a URL&CCPS's payment result, etc. to a SD; or a URL&CCPS that can receive URL&SS information, CCI, a payment request, or others from a URL&SS, deliver an order details, etc. to a URL&CCWS, receive an order confirmation, etc. from a URL&CCWS, or deliver a payment result, etc. to a URL&SS or a URL&CCWS in response to a payment request, an order confirmation, or others. An online payment system confirms a user using a URL&CC's URL, a user's URL PWD, or others after requesting payment using a URL&CC's CCI, etc.

[0086] An Online Payment Method that Confirms a User after Requesting Payment, See FIG. 4>

[0087] An online payment method, comprising: step a) in which a SD connects to a URL&SS in response to a user's access order, or communicates a sales site, etc. with a URL&SS or a user; step b) in which a URL&CC delivers CCI to a user; step c) in which a SD receives CCI, a payment request including order details, or others from a user, delivers CCI, a payment request, or others to a URL&SS, receive an order #, etc. from a URL&SS, or deliver an order #, etc. to a user; step d) in which a URL&SS delivers URL&SS information, CCI, a payment request, or others to a URL&CCPS; step e) in which a URL&CCPS delivers an order details, etc. to a URL&CCWS; step f) in which a URL&CCWS manages an order details, etc.; step g) in which a SD receives a URL from a URL&CC, connects to a URL&CCWS in response to a URL, communicates SD information, etc. with a URL&CCWS, communicates a URL&CC site, etc. with a URL&CCWS or a user, receives a URL PWD, etc. from a user, delivers a URL PWD, etc. to a URL&CCWS, receives a URL PWD check result, an order details, or others from a URL&CCWS, delivers a URL PWD check result, an order details, or others to a user, receives an order confirmation, etc. from a user, or delivers an order confirmation, etc. to a URL&CCWS; step h) in which a URL&CCWS delivers an order details, etc. to a URL&CCPS; step i) in which a URL&CCPS delivers a payment result, etc. to a URL&SS or a URL&CCWS in response to a payment request, an order confirmation, or others; or step j) in which a URL&SS or a URL&CCWS delivers a payment result, etc. to a SD; or a SD delivers a payment result, etc. to a user. An online payment method confirms a user using a URL&CC's URL, a user's URL PWD, or others after requesting payment using a URL&CC's CCI, etc.

[0088] <An Online Payment System that Requests Payment after Confirming a User, See FIG. 5>

[0089] An online payment system, comprising: a URL&CC that can store CCI, a URL, etc., deliver CCI to a user, or deliver a URL to a SD; a SD that can receive a URL from a URL&CC, connect to a URL&CCWS in response to a URL, communicate SD information, etc. with a URL&CCWS, communicate a URL&CC site, etc. with a URL&CCWS or a user, receive a URL PWD, etc. from a user, deliver a URL PWD, etc. to a URL&CCWS, receive a URL PWD check result, etc. from a URL&CCWS, deliver a URL PWD check result, etc. to a user, receive a payment reservations, etc. from a user, deliver a payment reservation, etc. to a URL&CCWS, connect to a URL&SS in response to a user's access order, communicate a sales site, etc. with a URL&SS or a user, receive CCI, a payment request, or others from a user, deliver CCI, a payment request, or others to a URL&SS, receive a payment result, etc. from a URL&CCWS or a URL&SS, or deliver a payment result, etc. to a user; a URL&CCWS that can connect to a SD, communicate SD information, a URL&CC site, or others with a SD, receive a URL PWD, etc. from a SD, deliver a URL PWD check result, etc. to a SD, receive a payment reservation, etc. from a SD, deliver a payment reservation, etc. to URL&CCPS, or deliver a URL&CCPS's a payment result, etc. to a SD; a URL&SS that can connect to a SD, communicate a sales site, etc. with a SD, receive CCI, a payment request, or others from a SD, deliver URL&SS information, CCI, a payment request, or others to a URL&CCPS, or deliver a URL&CCPS's payment result, etc. to a SD; or a URL&CCPS that can receive a payment reservation, etc. from a URL&CCWS, receive URL&SS information, CCI, a payment request, or others from a URL&SS, or deliver a payment result, etc. to a URL&CCWS or a URL&SS in response to a payment reservation, a payment request, or others. An online payment system confirms a user using a URL&CC's URL, a user's URL PWD, or others and then requests payment using a URL&CC's CCI, etc.

[0090] <An Online Payment Method that Requests Payment after Confirming a User, See FIG. 6>

[0091] An online payment system, comprising: step a) in which a URL&CC delivers a URL to a SD; step b) in which a SD connects to a URL&CCWS in response to a URL, communicates SD information, etc. with a URL&CCWS, communicates a URL&CC site, etc. with a URL&CCWS or a user, receives a URL PWD, etc. from a user, delivers a URL PWD, etc. to a URL&CCWS, receive a URL PWD check result, etc. from a URL&CCWS, deliver a URL PWD check result, etc. to a user, receive a payment reservation, etc. from a user, or deliver a payment reservation, etc. to a URL&CCWS; step c) in which a URL&CCWS delivers a payment reservation, etc. to a URL&CCPS; step d) in which a SD connects to a URL&SS in response to a user's access order, or communicates a sales site, etc. with a URL&SS or a user; step e) in which a URL&CC delivers CCI to a user; step f) in which a SD receives CCI, a payment request, or others from a user, or delivers CCI, a payment request, or others to a URL&SS; step g) in which a URL&SS delivers URL&SS information, CCI, a payment request, or others to a URL&CCPS; step h) in which a URL&CCPS delivers a payment result, etc. to a URL&CCWS or a URL&SS in response to a payment reservation, a payment request, or others; or step i) in which a URL&CCWS or a URL&SS delivers a payment result, etc. to a SD; or a SD delivers a payment result, etc. to a user. An online payment system confirms a user using a URL&CC's URL, a user's URL PWD, or others and then requests payment using a URL&CC's CCI, etc.

Definition and Explanation of Terms

[0092] (URL&CC) A URL&CC is a credit card that includes a URL.

[0093] A URL&CC can store CCI, a URL, etc.

[0094] CCI is visual information and can be delivery to a user. And a URL is electronic information, image information, or other information and can be delivery to a SD, etc.

[0095] A URL&CC does not store a URL PWD.

[0096] A URL&CC can help identity a user without using a user's PI (personal information).

[0097] A URL&CC can separate a payment request path and a user confirmation path.

[0098] A URL&CC complies with credit card standards and stores CCI, a URL, etc. A URL&CC can include URL&debitcards (a kind of debit card), URL&prepaidcards (a kind of prepaid card), or others.

[0099] CCI or a URL can be stored in one or more URL&CC.

[0100] A URL&CC can help connect to a URL&CCWS, etc. while using a URL as an ID.

[0101] A URL&CC can prevent an illegal connection by using access methods, usage methods, access paths, SD's information, or others.

[0102] Because URL&CCs do not store URL PWDs, them cannot deliver passwords (=URL PWDs) to URL&CCWSs or URL&CC sites. Since a URL&CC is a card, a loss of the URL&CC(=a loss of an ID) can be easily recognized.

[0103] (CCI) CCI of a URL&CC follows credit card standards, but cannot include additional information (CVC, expiration date, etc.).

[0104] CCI can be in the form of electronic information, image information, or other information.

[0105] CCI of a URL&CC does not include a URL or a URL PWD.

[0106] (Card number) A card number of URL&CC can correspond to a card number of existing credit card.

[0107] Card number is main information of URL&CC.

[0108] (User) A user is a subject that can use a URL&CC.

[0109] A user does not use PI (=personal information) to confirm a user's identity. A user can provide a URL PWD, a payment reservation, an order confirmation, or others.

[0110] (URL) A URL can support connect to a URL&CCWS or a URL&CC Site.

[0111] A URL can be used as an ID of URL&CC or user.

[0112] A URL may be stored in a URL&CC in the form of electronic information, image information, or other information.

[0113] A URL can be transmitted to an outside through a NFC communication, an image communication, or other communications.

[0114] A URL&CCWS does not support an access using a browser.

[0115] A URL can prevent an illegal access by using usage methods, access paths, SD's features, or other methods.

[0116] Since a URL is transmitted to a SD in electronic communication it cannot be leaked through malicious code, phishing, or other hacking.

[0117] URLs can support following means. 1) Means to identify a user without using a user's PI (=personal information) 2) Means to use separate paths (a payment request path and a user confirmation path) 3) Means to prevent the simultaneous leakage of payment information 4) Means not to use additional information (CVC, etc.) 5) Means to make an additional income (advertisement income, etc.), etc.

[0118] (URL PWD) A URL PWD is a password that is set in a URL, a URL&CC, a URL&CC Site, or others.

[0119] A URL PWD can help confirm users or log in to a URL&CCWS.

[0120] Since a URL PWD is not stored in URL&CC it is not leaked even if the URL&CC is lost.

[0121] The URL PWD can be multiple.

[0122] (URL PWD check result) A URL PWD check result is a result of checking a URL PWD, a URL, SD information, or others. A URL PWD check result can include user check results, log results, or others.

[0123] (Order #) Order # is a number representing the order and can designate the order.

[0124] Order # can be used as information to identify users, etc.

[0125] (Payment request) A payment request can include order details, etc.

[0126] (Payment reservation) A payment reservation is a notice in advance that a payment will be requested.

[0127] A payment reservation can include results of confirming users, etc.

[0128] Payment reservations do not exist in existing payments using existing credit cards.

[0129] (Order Details) Order details are the details of order and can include items, prices, or others.

[0130] Order details can be included in payment requests.

[0131] A URL&CCPS can communicate order details, etc. with a URL&CCWS, etc.

[0132] (Order confirmation) Order confirmation is to confirm order details.

[0133] Order confirmation can include user confirmations or payment request confirmations or others.

[0134] Order confirmation is not available for existing payments using existing credit cards.

[0135] (SD=Smart Device) A SD is an electronic device that has an internet communication function, an information exchange function, a function of communication with a URL&CC, etc.

[0136] A smart-phone is a typical SD.

[0137] A SD can include a computer having a function capable of communicating with a URL&CC, etc.

[0138] SD can communicate with a URL&CC by using NFC communication, image communication (camera filming, etc.), or others.

[0139] A SD can communicate with a URL&CC, but an existing computer cannot communicate with an existing credit card.

[0140] More than one SD can connect to sales sites or URL&CC sites to support payments.

[0141] (SD information) SD information is SD's information (a SD's IP, an OS serial number, a MAC address, an IMEI (International Mobile Equipment Identity), etc.). SD information can be used as information that identifies SDs, users, or others.

[0142] (Access order) Access order is a command to connect to servers or websites.

[0143] (URL&SS) A URL&SS is a sales server of an online store that supports a URL&CC.

[0144] A URL&SS can include devices (such as sales sites, etc.) that support transactions using URL&CCs.

[0145] A URL&SS does not include a function to communicate with a PICD (Personal Information Confirmation Department).

[0146] (URL&SS information) URL&SS information is URL&SS's information (an IP, an OS serial number, a MAC address, etc.). URL&SS information can be used as information to check URL&SSs, operators of URL&SS, or others.

[0147] (Sales site) Sales sites are websites that sell goods, services, products, or others.

[0148] (URL&CCPS) A URL&CCPS is a server that supports payments using URL&CCs.

[0149] A URL&CCPS can determine a payment using information (CCI, payment requests, order confirmations, payment reservations, or others) received through separate paths (a payment request path and a user confirmation path).

[0150] A URL&CCPS can communicate CCI, payment requests, payment results, or others with URL&SSs, etc.

[0151] A URL&CCPS can communicate information (order details, order confirmations, payment reservations, payment results, or others) with URL&CCWSs, etc.

[0152] A URL&CCPS cannot use a URL or a URL PWD.

[0153] A URL&CCPS can separate payment paths, use order confirmations or payment reservations or others, or communicate with URL&CCWSs.

[0154] (URL&CCWS) A URL&CCWS is a web server that can support payments using URL&CCs.

[0155] A URL&CCWS can manage URL&CC Sites, etc., or support payments using a URL, a URL PWD, or others.

[0156] A URL&CCWS can manage a URL, a URL PWD, or others, and can identify users using a URL, a URL PWD, SD information, or others. A URL&CCWS can determine to log in to URL&CC sites or communicate information (order details, order confirmations, payment reservations, payment results, or others) with URL&CCPSs, etc.

[0157] A URL&CCWS is not available for existing payments using existing credit cards.

[0158] (URL&CC Site) URL&CC Sites are websites that can support payments using URL&CCs.

[0159] URL&CC Sites can support payments using URL&CCs, URLs, URL PWDs, or others.

[0160] URL&CC sites can deliver payment process's information (order details, order confirmations, payment reservations, payment results, or others) or include advertisements, etc.

[0161] A URL&CC Site is not available for existing payments using existing credit cards.

[0162] (Payment Result) Payment result is a result of performing payments.

[0163] Payment results of URL&CC can be generated using a payment request path's information (CCI, payment request, etc.) and a user confirmation path's information (order confirmation, payment reservation, etc.).

[0164] Order confirmations or payment reservations do not exist in existing payments using existing credit cards.

[0165] (A payment Method 1 using URL&CCs: See FIGS. 3 and 4) After requesting a payment through a path using CCI, etc., a user is identified through a path using a URL, a URL PWD, or others.

[0166] (A payment method 2 using URL&CCs: see FIGS. 5 and 6) After confirming users through a path using a URL, a URL PWD, or others a payment is requested through a path using CCI, etc.

[0167] A URL&CC's payment request process and user confirmation process have the different path and information.

[0168] (Advantages of Payments Using URL&CCs)

[0169] 1) Since users can be identified with URLs, URL PWDs, etc., PI (=personal information) does not be used.

[0170] 2) Because CCI uses a payment request path and a URL or a URL PWD uses a user confirmation path, payment information cannot be leaked at the same time.

[0171] 3) Since a URL of URL&CC can specify an access method, an access path or others, an illegal access to a URL&CCWS can be prevented.

[0172] 4) Since a card company's server identifies users by using URLs, URL PWDs, or others it is possible to reduce costs of user confirmations.

[0173] 5) Different information for each route and route separation can provide economical security of payments.

[0174] 6) In payment processes, additional incomes can be generated by using advertisements, etc.

EXPLANATION OF THE SIGN

[0175] <Existing Credit Card Payment System and Flow Chart> [0176] 110, 210: CC(=Credit Card) [0177] 120, 220: CC User (=Credit Card User) [0178] 130, 230: SS(=Sales Server) [0179] 140, 240: Computer [0180] 150, 250: CCPS(=Credit Card payment Server) [0181] 160, 260: PICD (=Personal Information Confirmation Department) [0182] <Invention's URL&CC payment system and flow chart> [0183] 310, 410, 510, 610: URL&CC(=URL & Credit Card) [0184] 320, 420, 520, 620: User [0185] 330, 430, 530, 630: URL&SS(=URL & Sales Server) [0186] 340, 440, 540, 640: SD (=Smart Device) [0187] 350, 450, 550, 650: URL&CCPS(=URL & Credit Card Payment Server) [0188] 390, 490, 590, 690: URL&CCWS(=URL & Credit Card Web Server)