A payment method for online transactions that uses a credit card linked to a URL

The credit card linked to a URL method separates payment and user confirmation routes, using URL secret information for verification, addressing leaks and costs, and generating revenue in online transactions.

JP7579261B2Active Publication Date: 2024-11-07キムグムチョル
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2021543149
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-01-26
Filing Date
2020-01-23
Publication Date
2024-11-07
Estimated Expiration
2040-01-23

AI Technical Summary

Technical Problem

In online transactions, credit card information and personal information are transmitted through the same route, leading to potential leaks, increased verification costs, and difficulty in preventing unauthorized use, without generating additional revenue.

Method used

A payment method using a credit card linked to a URL, where CC information is conveyed visually and URLs are conveyed electronically, with separate routes for payment requests and user confirmation, utilizing URL secret information for verification.

Benefits of technology

This approach prevents simultaneous leakage of payment information, reduces verification costs, and generates additional revenue through advertisements, while ensuring secure and efficient transactions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579261000001
    Figure 0007579261000001
  • Figure 0007579261000002
    Figure 0007579261000002
  • Figure 0007579261000003
    Figure 0007579261000003
Patent Text Reader

Abstract

In online payments using URL&CC, the payment request route and user verification route are different, and the procedures for these routes can be interchanged. (Payment Method 1) After requesting payment via a route using the CC information of the URL&CC (payment request route), the user is verified via a route using the URL or URL confidential information (user verification route) and payment is made. (Payment Method 2) After verifying the user via a route using the URL or URL confidential information (user verification route), payment is requested via a route using the CC information of the URL&CC (payment request route) and payment is made.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] Pay with a credit card in an online transaction. [Background technology]

[0002] (CC=Credit Card) CC adheres to credit card standards, stores CC information, and can assist with payments.

[0003] Currently, CC's payment request route and user verification route are the same.

[0004] CCs can include debit cards, prepaid cards, etc. that comply with credit card standards.

[0005] (Credit card standards)Credit card standards include ISO-7810 and EMV.

[0006] Credit card standards are the backbone of the credit card business. CC and merchant equipment (such as credit card terminals and sales servers) and card company equipment (such as CC payment servers) comply with the credit card standards.

[0007] (ISO-7810)ISO-7810 defines the appearance of CC, the method of information exchange, and the specifications for credit card terminals.

[0008] (EMV)EMV (Europay Mastercard Visa) is an international technical standard for IC-type CC.

[0009] (CC information = credit card information) CC information is information stored in the CC.

[0010] Current CC information for online transactions includes main information (card number) and additional information (CVC, expiration date, etc.).

[0011] CC information used in online transactions is visual information.

[0012] In online transactions, CC information is conveyed to CC users in the form of visual information.

[0013] (Card number) The card number is a unique 16-digit number.

[0014] Numbers 1 to 6 (BIN number) specify the issuing country, card company, and card type (general, gold, personal, corporate, etc.). Card companies use numbers 7 to 15 at their discretion. Number 16 is a value that verifies the card number.

[0015] CVC (Card Verification Code) is a security code of CC that verifies the cardholder. CVC, CVV and CID are all security codes.

[0016] Currently, online transactions are only possible when the CVC number (3 digits) and card number (16 digits) match.

[0017] CVC can prevent leaked card numbers from being used fraudulently in online transactions.

[0018] (CC User) A CC User is an entity that uses CC. In online transactions, a CC User provides personal information for identity verification.

[0019] (Personal Information) Personal information is the personal information of a CC user (such as name, SSN, phone number, etc.).

[0020] Personal information is not included in CC information.

[0021] Personal information is used to identify CC users during online transactions.

[0022] (Payment Request) A payment request is a request for payment and may include order details, etc.

[0023] In online transactions, a payment request using CC is used together with personal information and CC information.

[0024] (Order details) The order details may include items, prices, etc.

[0025] (Personal computer) A personal computer is an electronic device with Internet communication and information exchange capabilities.

[0026] Smartphones can also function as computers.

[0027] The PC does not need the ability to communicate with CC.

[0028] (Connection Command) A connection command is an order to connect to a server or website.

[0029] (Merchandise Server) A merchant server is a server that supports online transactions.

[0030] The sales server complies with credit card standards. The sales server transmits personal information to the personal information verification department and receives the results of the personal information verification.

[0031] The sales server transmits the personal information confirmation result, CC information, and payment request to the CC payment server.

[0032] (Merchandise Site) A retail site is a website that sells goods, services, products, etc. A retail server supports the retail site.

[0033] (Personal Information Verification Department) The Personal Information Verification Department can verify personal information.

[0034] Since the sales server cannot verify personal information, the payment processing company (PG) verifies the information and receives the payment.

[0035] (Personal information confirmation result) The personal information confirmation result is the result of verifying personal information.

[0036] (CC payment server) The CC payment server is a server that manages all payments made using CC.

[0037] The CC payment server makes the payment using the information received via the same route (CC information, personal information verification result, and payment request).

[0038] (Payment result) The payment result is the result of payment made in response to a payment request.

[0039] CC payment results are the result of using a single route of information (CC information, personal information verification results, and payment request).

[0040] (CC payment method) CC payment method uses the same information (CC information, personal information and payment request) to identify the CC user and make payment.

[0041] (Payment process) The CC payment process uses CC information, personal information, and payment request on the same route at the same time. The CC payment process uses the personal information verification results of a third party (=personal information verification department).

[0042] The payment request process for CC payment and the CC user verification process are carried out simultaneously through the same path.

[0043] (PG Company = Payment Gateway Company) PG Company is a third party that verifies personal information and receives payments.

[0044] (Problems with a single route) With a single route, CC information and personal information may be leaked at the same time, making it difficult to prevent the leaked information from being used illegally.

[0045] (Regarding route separation: offline example) The payment request route and user confirmation route in Korean Patent No. 10-1751640 and Korean Patent No. 10-1941587 are different, and the order may change.

[0046] (Problems with CC payments in online transactions)

[0047] 1) CC information and personal information may be leaked at the same time.

[0048] 2) There is a cost to verify your personal information.

[0049] 3) It is difficult to prevent the unauthorized use of leaked CC information and personal information.

[0050] 4) The use of auxiliary information is necessary for secure transactions.

[0051] 5) No additional revenue is generated.

[0052] Figures 1 and 2 show a conventional system and flow chart for making payments using CC in online transactions.

[0053] <Existing payment systems that use CC in online transactions, see Figure 1>

[0054] Store CC information and transmit the CC information to CC users CC; The sales site can connect to the sales server in response to a connection command from the CC user, communicate with the sales server and the CC user, receive the CC information, personal information, and payment request from the CC user, transmit the CC information, personal information, and payment request to the sales server, and communicate a payment result with the sales server and the CC user. Personal computer; The computer is connected to the sales site, the sales site communicates with the computer, the CC information, the personal information, and the payment request are received from the computer, the personal information is transmitted to a personal information confirmation unit, a personal information confirmation result is received from the personal information confirmation unit, the CC information, the personal information confirmation result, and the payment request are transmitted to a CC payment server, and the payment result of the CC payment server is transmitted to the computer. Sales server; The personal information can be received from the sales server, and the personal information confirmation result can be transmitted to the sales server. Personal information confirmationand receiving the CC information, the personal information confirmation result, and the payment request from the sales server, and transmitting the payment result to the sales server. CC Payment Server In an online credit card payment system, the payment request process and the user authentication process are carried out simultaneously through the same route.

[0055] <The traditional payment method using CC in online transactions, see Figure 2>

[0056] a) Computer connecting to a sales server in response to a connection command from the CC user, and communicating the sales site with the sales server and the CC user; b) CC transmitting CC information to the CC user; c) The said computer transmitting the CC information, personal information, and a payment request of the CC user to the sales server; d) The sales server transmitting the personal information to a personal information verification department; e) The personal information verification section transmitting a result of the personal information confirmation to the sales server; f) the sales server transmitting the CC information, the personal information confirmation result, and the payment request to a CC payment server; g) The CC payment server transmitting a payment result to the sales server; h) said sales server transmitting the payment result to the personal computer; and i) The computer transmitting the result of the payment to the CC user. In the online credit card payment method, a payment request process and a user verification process are simultaneously performed through the same route. Summary of the Invention [Problem to be solved by the invention]

[0057] In online transactions,

[0058] 1) Provide a way to verify users without using personal information.

[0059] 2) Provide a means to prevent simultaneous leakage of payment information.

[0060] 3) Provide a means to prevent unauthorized use of leaked information.

[0061] 4) Provide a means to reduce user verification costs.

[0062] 5) Provide a means that does not require the use of credit card details (such as CVC).

[0063] 6) To provide an economical and efficient payment system.

[0064] 7) Provide a means to generate additional revenue. [Means for solving the problem]

[0065] In online transactions, payment is made by organically operating URL&CC, smart device, smart device information, URL sales server, URL sales server information, sales site, URL&CC payment server, URL&CC web server, URL&CC site, CC information, payment request, order number, order details, URL, URL confidential information, URL confidential information confirmation result, order confirmation, payment result, etc. This payment method requests payment using a route such as CC information, and then confirms the user using a route such as URL or URL confidential information.

[0066] In online transactions, payment is made by organically operating URL&CC, smart device, smart device information, URL&CC web server, URL&CC site, URL sales server, URL sales server information, sales site, URL&CC payment server, URL, URL confidential information, URL confidential information confirmation result, payment schedule, CC information, payment request, payment result, etc. This payment method confirms the user through a route using URL or URL confidential information, etc., and then requests payment through a route using CC information, etc. Effect of the Invention

[0067] In online transactions,

[0068] 1) Since users are identified using the URL and URL confidential information, personal information or additional information (such as CVC) cannot be used.

[0069] 2) The payment request route and user confirmation route are separate, which prevents payment information from being leaked at the same time.

[0070] 3) It is possible to prevent unauthorized use of leaked information by separating the route and identifying the method of use.

[0071] 4) Since the card company's equipment uses the URL and URL confidential information to verify the user, the cost of verifying the user can be reduced.

[0072] 5) Since the user is identified using the URL or URL confidential information, it is not possible to use auxiliary information (such as CVC).

[0073] 6) It is possible to separate routes and identify their usage to ensure structural payment security.

[0074] 7) Additional revenue can be generated by using advertisements during the payment process. [Brief description of the drawings]

[0075] [Figure 1] Figure 1 shows a conventional online payment system using a credit card (where the payment request route and user verification route are the same). [Diagram 2] FIG. 2 is a flow chart of FIG. [Diagram 3] Figure 3 shows a payment system in which, in online transactions, after requesting payment via a route that uses CC information, etc. (payment request route), the user is verified via a route that uses a URL or URL confidential information, etc. (user verification route). [Figure 4] FIG. 4 is a flow chart of FIG. [Diagram 5]Figure 5 shows a payment system for online transactions in which a user is verified via a route (user verification route) that uses a URL or URL confidential information, etc., and then payment is requested via a route (payment request route) that uses CC information, etc. [Figure 6] FIG. 6 is a flow chart of FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0076] Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the attached drawings. Terms used in this specification and claims should not be interpreted as being limited to their ordinary or dictionary meanings, but should be interpreted as meanings and concepts that are consistent with the technical matters of the present invention.

[0077] The embodiments described in this specification and the configurations illustrated in the drawings are preferred embodiments of the present invention and do not represent all of the technical ideas of the present invention. There may be various equivalents and modifications that can replace them at the time of this application.

[0078] A URL (Uniform Resource Locator) refers to the location of a file on a web server that provides web documents and various services.

[0079] <An online payment system that verifies the user after a payment request, see Figure 3>

[0080] It is possible to include CC information and URLs, transmit CC information to users, and transmit URLs to smart devices. URL&CC;It is possible to connect to a URL sales server in response to a user's connection command, communicate the sales site with the URL sales server and the user, receive a payment request and CC information including order details from the user, transmit the payment request and CC information to the URL sales server, receive a URL from URL&CC, connect to the URL&CC web server in response to the URL, communicate smart device information with the URL&CC web server, communicate the URL&CC site with the URL&CC web server and the user, receive URL confidential information from the user, transmit the URL confidential information to the URL&CC web server, receive the URL confidential information confirmation result and order details from the URL&CC web server, transmit the URL confidential information confirmation result and order details to the user, transmit the user's order confirmation to the URL&CC web server, and transmit the payment result of the URL sales server or the URL&CC web server to the user. Smart devices; It is possible to connect to smart devices, communicate with sales sites and smart devices, receive CC information and payment requests from smart devices, transmit URL sales server information, CC information and payment requests to the URL & CC payment server, and transmit payment results of the URL & CC payment server to smart devices. URL sales server; It is possible to receive order details and the like from the URL & CC payment server, connect to a smart device, communicate smart device information and URL & CC sites with the smart device, receive URL confidential information and the like from a smart device, transmit URL confidential information confirmation results and order details and the like to a smart device, receive order confirmation and the like from a smart device, transmit order confirmation and the like to the URL & CC payment server, and transmit payment results of the URL & CC payment server and the like to a smart device. URL & CC Web Server It is possible to receive URL sales server information, CC information, and payment requests from the URL sales server, transmit order details to the URL&CC web server, receive order confirmations from the URL&CC web server, and transmit payment results to the URL sales server or URL&CC web server in response to payment requests and order confirmations. URL & CC payment server;An online payment system comprising:

[0081] <Online payment method that confirms the user after payment request, see Figure 4>

[0082] a) The smart device connects to the URL sales server in response to the user's connection command, and communicates with the sales site, the URL sales server, and the user. step; b) URL&CC conveys CC information to users step; c) The smart device receives a payment request including order details and CC information from the user, and transmits the payment request and CC information to the URL sales server. step; d) The URL sales server transmits the URL sales server information, CC information, and payment request to the URL & CC payment server. step; e) The URL&CC payment server transmits the order details to the URL&CC web server. step; f) URL & CC web server manages order details, etc. step; g) The smart device receives a URL from the URL&CC, connects to the URL&CC web server in response to the URL, communicates smart device information, etc. with the URL&CC web server, communicates the URL&CC site with the URL&CC web server and a user, receives URL confidential information, etc. from a user, transmits URL confidential information, etc. to the URL&CC web server, receives URL confidential information confirmation results and order details, etc. from the URL&CC web server, transmits URL confidential information confirmation results and order details, etc. to the user, receives order confirmation, etc. from the user, and transmits order confirmation, etc. to the URL&CC web server. step; h) The URL&CC web server transmits the order confirmation, etc. to the URL&CC payment server. step; i) The URL&CC payment server responds to payment requests and order confirmations and transmits payment results to the URL sales server and the URL&CC web server. step; j) The URL sales server or the URL&CC web server transmits the payment results to the smart device; or the smart device transmits the payment results to the user. step; An online payment method comprising the steps of:

[0083] <An online payment system that requests payment after verifying the user, see Figure 5>

[0084] It is possible to include CC information and URLs, transmit CC information to users, and transmit URLs to smart devices. URL&CC; It is possible to receive a URL from URL&CC, connect to a URL&CC web server in response to the URL, communicate smart device information, etc. with the URL&CC web server, communicate a URL&CC site with the URL&CC web server or a user, receive URL confidential information, etc. from a user, transmit URL confidential information, etc. to the URL&CC web server, receive URL confidential information confirmation results, etc. from the URL&CC web server, transmit URL confidential information confirmation results, etc. to a user, receive payment plans, etc. from a user, transmit payment plans, etc. to the URL&CC web server, connect to a URL sales server in response to a user's connection command, communicate a sales site with the URL sales server or a user, receive CC information and payment requests, etc. from a user, transmit CC information and payment requests, etc. to the URL sales server, receive payment results, etc. from the URL&CC web server or the URL sales server, and transmit payment results, etc. to a user. Smart devices; It is possible to connect to smart devices, communicate smart device information and URL & CC sites with smart devices, receive URL confidential information from smart devices, transmit URL confidential information confirmation results to smart devices, receive payment schedules from smart devices, transmit payment schedules to the URL & CC payment server, and transmit payment results from the URL & CC payment server to smart devices. URL&CC Web Server; It is possible to connect to smart devices, communicate with sales sites and smart devices, receive CC information and payment requests from smart devices, transmit URL sales server information, CC information and payment requests to the URL & CC payment server, and transmit payment results of the URL & CC payment server to smart devices. URL sales server; It is possible to receive payment schedules, etc. from the URL&CC web server, receive URL sales server information, CC information, payment requests, etc. from the URL sales server, and transmit payment results, etc. to the URL&CC web server and URL sales server in response to payment schedules and payment requests. URL & CC payment server ;An online payment system comprising:

[0085] <Online payment method that requests payment after verifying the user, see Figure 6>

[0086] a) URL&CC transmits the URL via smart device step; b) The smart device connects to the URL&CC web server in response to the URL, communicates smart device information, etc. with the URL&CC web server, communicates the URL&CC site with the URL&CC web server and a user, receives URL confidential information, etc. from a user, transmits URL confidential information, etc. to the URL&CC web server, receives URL confidential information confirmation results, etc. from the URL&CC web server, transmits URL confidential information confirmation results, etc. to a user, receives payment schedules, etc. from a user, and transmits payment schedules, etc. to the URL&CC web server. step; c) The URL&CC web server transmits the payment schedule to the URL&CC payment server. step; d) The smart device connects to the URL sales server in response to the user's connection command, and communicates with the sales site, the URL sales server, and the user. step; e) URL&CC conveys CC information to users step; f) The smart device receives CC information, payment requests, etc. from the user, and transmits CC information, payment requests, etc. to the URL sales server. step; g) The URL sales server transmits the URL sales server information, CC information, payment request, etc. to the URL & CC payment server. step; h) The URL&CC payment server responds to payment schedules and payment requests and transmits payment results to the URL&CC web server and URL sales server. step;i) The URL&CC web server or URL sales server transmits the payment result to the smart device; or the smart device transmits the payment result to the user. step; An online payment method comprising the steps of:

[0087] <Terminology definitions and explanations>

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

[0089] URL&CC can save CC information and URLs, etc.

[0090] In online transactions, the CC information can be transmitted to the user as visual information, and the URL can be transmitted to the smart device in the form of electronic information, image information, etc.

[0091] URL&CC does not store any confidential URL information.

[0092] URL&CC payments do not use user personal information.

[0093] URL&CC payment can separate the payment request route and the user confirmation route.

[0094] URL&CC complies with credit card standards and stores CC information and URLs, etc. URL&CC can include URL&debit card (a kind of debit card) and URL&prepaid card (a kind of prepaid card), etc.

[0095] CC information and URLs can be stored in one or more URL&CCs.

[0096] URL&CC can support connecting to URL&CC web servers etc. using the URL as an ID.

[0097] URL&CC can help prevent unauthorized connections by identifying connection methods, connection paths, and smart device characteristics.

[0098] Because URL&CC does not store URL confidential information, the password for logging cannot be transmitted to the URL&CC web server or URL&CC site. And because URL&CC is a card, loss of URL&CC (= loss of ID) is easily recognized.

[0099] (CC information) The CC information in URL&CC may not include additional information (such as CVC or expiration date).

[0100] CC information comes in the form of electronic information and image information.

[0101] The CC information in URL&CC does not include URLs or URL confidential information.

[0102] (Card Number) The card number in the URL&CC corresponds to the card number of an existing credit card.

[0103] The card number is the main information of the URL&CC.

[0104] (User) A user is an entity that can use a URL&CC.

[0105] Users do not use personal information to identify themselves, and users can transmit secret URLs, payment schedules, order confirmations, etc.

[0106] (URL) A URL can assist in connecting to a URL&CC web server or a URL&CC site.

[0107] The URL can be used as the URL&CC or as a user ID.

[0108] URLs can be stored in URL&CC in the form of electronic information, image information, etc.

[0109] The URL can be transmitted to the outside via NFC communication or image communication.

[0110] The URL&CC web server does not support the connection method of entering a URL from a browser.

[0111] URLs can be used to prevent unauthorized connections by utilizing the method of use, connection route, device characteristics, etc.

[0112] Because the URL is transmitted to the smart device via electronic communication, it cannot be leaked through malicious code, phishing or other hacking.

[0113] In online payments, the use of URLs can provide the following means: 1) a means to identify users without using personal information, 2) a means to separate the payment request path from the user identification path, 3) a means to prevent simultaneous leakage of payment information, 4) a means to avoid using additional information (CVC, etc.), and 5) a means to generate additional revenue from advertisements, etc.

[0114] (URL confidential information) URL confidential information is a password set for a URL, URL&CC, URL&CC site, etc.

[0115] The URL secret information can be used as user authentication information or information for logging into URL&CC sites.

[0116] The URL secret information is memorized by the user, so it will not be leaked even if the URL&CC is lost.

[0117] There can be multiple URL secrets.

[0118] (URL confidential information confirmation result) The URL confidential information confirmation result is the result of checking the URL confidential information, URL, smart device information, etc. The URL confidential information confirmation result may include user confirmation results, log results, etc.

[0119] (Order Number) The order number is a number that represents an order and can be used to specify an order or to search for an order.

[0120] The order number can be used as information to identify the user, etc.

[0121] (Payment Request) The payment request may include order details, etc.

[0122] (Payment Schedule) A payment schedule is advance notice of a payment request.

[0123] The payment schedule may include facts that identify the user.

[0124] Payment schedules do not exist for payments made using traditional credit cards.

[0125] (Order details) The order details may include items, prices, etc.

[0126] The order details may be included in the payment request.

[0127] The URL&CC payment server can communicate order details and other information with the URL&CC web server.

[0128] (Order Confirmation) The order confirmation confirms the contents of the order.

[0129] The order confirmation may include the fact that the user has been confirmed and the meaning of requesting payment again.

[0130] Order confirmation is not included in traditional credit card payments.

[0131] (Smart Device) A smart device is an electronic device that has Internet communication functions, functions to exchange information with users, and functions to communicate with URLs and CCs.

[0132] A typical example of a smart device is a smartphone.

[0133] Computers that further have the function of communicating with URL&CC can also be included in smart devices.

[0134] Smart devices can communicate with URLs and CCs via NFC communication and image communication (such as taking photos with a camera).

[0135] Smart devices can communicate with URLs and CCs, but traditional computers cannot communicate with credit cards.

[0136] One or more smart devices can connect to a merchant site or URL&CC site to facilitate payment.

[0137] (Smart device information) Smart device information is information held by smart devices (such as the smart device's IP address, OS serial number, MAC address, IMEI (International Mobile Equipment Identity), etc.) Smart device information can also be used to identify smart devices and their users.

[0138] (Connection Command) A connection command is an order to connect to a server or website.

[0139] (URL & Sales Server) The URL & Sales Server is a server that supports online sales.

[0140] The URL & merchant server may include devices (eg, merchant servers and merchant sites) that support credit cards and URLs & CCs in online transactions.

[0141] The URL & sales server does not communicate with the traditional personal information verification unit.

[0142] (URL & sales server information) URL & sales server information is information on the URL & sales server (IP, OS serial number, MAC address, etc.). URL & sales server information can be used to identify the URL & sales server and the operator of the URL & sales server.

[0143] (Sales Site) A sales site is a website that sells goods, services, products, etc.

[0144] (URL&CC payment server) The URL&CC payment server is a server that manages all payments using URL&CC.

[0145] The URL & CC payment server can determine payment based on information (CC information, payment request, order confirmation, payment schedule, etc.) received through separate routes (payment request route and user confirmation route).

[0146] The URL & CC payment server can communicate CC information, payment requests, payment results, etc. with the URL & sales server.

[0147] The URL&CC payment server can communicate with the URL&CC web server, etc., regarding order details, order confirmation, payment schedule, and payment results.

[0148] The URL&CC payment server cannot use the URL or URL secrets.

[0149] The URL&CC payment server can separate payment paths, use order confirmations and payment schedules, and communicate with the URL&CC web server.

[0150] (URL&CC Web Server) The URL&CC Web Server is a web server that can support payment.

[0151] The URL&CC web server can manage URL&CC sites and support payments using URLs and URL secret information.

[0152] The URL&CC web server can manage URLs, URL confidential information, etc., and can verify users with URLs, URL confidential information, smart device information, etc. The URL&CC web server can determine login to the URL&CC site, and communicate with the URL&CC payment server, etc., for order details, order confirmation, payment schedule, payment results, etc.

[0153] The URL&CC web server does not exist in traditional credit card payments.

[0154] (URL&CC Site) The URL&CC Site is a website that can assist with URL&CC payments.

[0155] The URL&CC site can assist with payment using the URL&CC, URL, or URL confidential information.

[0156] The URL&CC site can transmit information about the payment process (order details, order confirmation, payment schedule, payment result, etc.) and can include advertisements.

[0157] URL&CC sites are not available for payments using traditional credit cards.

[0158] (Payment Result) The payment result is the result of supporting the payment.

[0159] The URL & CC payment result may be generated using information (CC information, payment request, order confirmation, payment schedule, etc.) from separate paths (payment request path and user confirmation path).

[0160] Traditional credit card payments do not use order confirmations or payment schedules.

[0161] (URL & CC payment method 1: see Figure 3 and Figure 4) After requesting payment via a route using CC information, etc., the user is verified via a route using URL or URL confidential information, etc.

[0162] (URL & CC payment method 2: see Figure 5 and Figure 6) After verifying the user through a route using the URL or URL secret information, payment is requested through a route using CC information, etc.

[0163] Payments using URL&CC have different payment request routes and user confirmation routes, and the information used is also different.

[0164] (Advantages of using URL&CC for online transactions)

[0165] 1) Since users can be identified using the URL and URL confidential information, personal information or additional information (such as CVC) cannot be used.

[0166] 2) CC information, URL, URL confidential information, etc. are used via separate routes, so payment information cannot be leaked at the same time.

[0167] 3) The URL is saved in URL&CC, and the connection method and route can be identified to prevent unauthorized use.

[0168] 4) User authentication costs can be reduced because the card company's equipment authenticates users using the URL and confidential URL information.

[0169] 5) The security of payments can be economically ensured by methods such as separating routes and using different information for each route.

[0170] 6) Additional revenue can be generated by using advertisements during the payment process.

[0171] * Explanation of symbols *

[0172] <Conventional credit card payment system and flow chart>

[0173] 110, 210: CC (= credit card)

[0174] 120, 220: CC users (= credit card users)

[0175] 130, 230: Sales server

[0176] 140, 240: PC

[0177] 150, 250: CC payment server (= credit card payment server)

[0178] 160, 260: Personal Information Verification Department

[0179] <Invention URL & CC payment system and flow chart>

[0180] 310, 410, 510, 610: URL&CC (=URL&credit card)

[0181] 320, 420, 520, 620: User

[0182] 330, 430, 530, 630: URL sales server

[0183] 340, 440, 540, 640: Smart devices

[0184] 350, 450, 550, 650: URL & CC payment server (= URL & credit card payment server)

[0185] 390, 490, 590, 690: URL&CC web server (=URL&Credit card web server)

Claims

1. a) a step in which the smart device connects to a URL sales server supporting a sales site in response to a connection command from a user and communicates with the URL sales server; b) transmitting the URL & CC (credit card information) stored in the CC (credit card) to the user; c) the smart device receiving a payment request including order details and the CC information from the user, and transmitting the payment request and the CC information to the URL sales server; d) the URL sales server transmitting the payment request and the CC information to a URL&CC payment server; e) the URL&CC payment server transmits the order details to the URL&CC web server; f) the URL&CC web server manages the order contents; g) the smart device receives a URL from the URL&CC where the URL is stored, connects to the URL&CC web server in response to the URL, communicates smart device information with the URL&CC web server, communicates with the URL&CC web server managing the URL&CC site and the user, receives URL secret information (password) input from the user, transmits the URL secret information to the URL&CC web server, receives a URL secret information confirmation result and the order contents from the URL&CC web server, transmits the URL secret information confirmation result and the order contents to the user, receives an order confirmation input from the user, and transmits the order confirmation to the URL&CC web server; h) the URL&CC web server transmitting the order confirmation to the URL&CC payment server; i) the URL&CC payment server transmits a payment result to the URL sales server or the URL&CC web server in response to the payment request and the order confirmation; and j) the URL sales server or the URL&CC web server transmitting the payment result to the smart device; and the smart device transmitting the payment result to the user.

2. a) transmitting the URL to be stored in the URL&CC (credit card) to the smart device; b) the smart device connects to a URL&CC web server that manages a URL&CC site corresponding to the URL, communicates with the URL&CC web server, receives URL secret information (password) input from a user, transmits the URL secret information (password) to the URL&CC web server, receives a URL secret information confirmation result from the URL&CC web server, transmits the URL secret information confirmation result to the user, receives a payment plan input from the user, and transmits the payment plan to the URL&CC web server; c) the URL&CC web server transmits the payment plan to the URL&CC payment server; d) the smart device accessing a URL sales server supporting a sales site in response to a connection command from the user and communicating with the URL sales server; e) transmitting the URL & CC (credit card information) stored in the CC (credit card) to the user; f) the smart device receives the CC information (credit card information) and the payment request as input from the user, and transmits the CC information (credit card information) and the payment request to the URL sales server; g) the URL sales server transmits the CC information (credit card information) and the payment request to the URL & CC payment server; h) the URL&CC payment server transmits a payment result to the URL&CC web server or the URL sales server in response to the payment schedule and the payment request; and i) the URL&CC web server or the URL sales server transmitting the payment result to the smart device; and the smart device transmitting the payment result to the user.

Citation Information

Patent Citations

  • Method and device for vicarious charging, and method and device for settlement confirmation

    JP2002334291A

  • Payment control server, payment control method and payment control program

    JP2003242423A

  • Prepaid type electronic money settlement system

    JP2010033546A

  • Settlement intermediation system, settlement system, program and method

    JP2015056044A

  • Settlement method, server, and application using instant message

    JP2016024831A