KR102010013B1 - Non-facing transaction and payment method, management server using virtual payment information - Google Patents

Abstract

The present invention relates to a non-face-to-face transaction and settlement method using a virtual payment information, a management server, the method comprising: issuing a payment card for a non-face-to-face transaction at the request of the merchant; Posting the payment card through a service application running in a user terminal; Receiving, by the user terminal, payment request information generated for the payment card when performing a non-face-to-face transaction using the payment card; And processing the payment approval by using the information included in the payment request information.

Description

Non-facing transaction and settlement method using virtual payment information, management server {NON-FACING TRANSACTION AND PAYMENT METHOD, MANAGEMENT SERVER USING VIRTUAL PAYMENT INFORMATION}

The present invention relates to a non-face-to-face transaction and settlement method using a virtual payment information, a management server, and more particularly, to a non-face-to-face transaction using a virtual payment information implemented to improve the existing face-to-face payment method. And a settlement method and a management server.

Recently, mobile payments using mobile terminals have been widely used in the payment market. However, most people think that the physical cards in plastic form are convenient, and the store terminals also support the payment of physical cards. And convenience can not be ignored.

However, in the case of the existing mobile card, there was a hassle to pay directly at the offline merchant. In addition, offline merchants must be equipped with a payment terminal such as a POS terminal or a CAT terminal for payment, so there was a problem in that a terminal installation and maintenance cost must be paid when using a payment service.

As a prior art to solve this problem, there is a method and system for providing a school fee payment service using a wireless message of Korean Patent Publication No. 10-2012-0029305 and a technology related to the recording medium therefor. This is a method in which a user accesses the callback URL through a terminal and performs a payment using an SMS message including a callback URL. However, this payment structure is the same structure as the general online payment, and works in conjunction with a financial institution server (card company or other financial company) via PG company or VAN company. Therefore, compared with the existing online payment, it is impossible to achieve the effect of reducing the fee, and the structure that the merchant and the user must bear the fee. In addition, since the payment request is required to obtain a payment approval through a payment institution, the payment request and approval has a disadvantage in that it takes time.

Korean Unexamined Patent Publication No. 10-2012-0029305 (published Mar. 26, 2012)

The present invention proposes a non-face-to-face transaction and settlement method using virtual payment information in order to solve the problems of the prior art and to perform face-to-face payment of offline merchants.

The present invention relates to a non-face-to-face transaction and settlement method using a virtual payment information, management server, an aspect of the present invention comprises the steps of issuing a payment card for non-face-to-face transactions at the request of the merchant; Posting the payment card through a service application running in a user terminal; Receiving, by the user terminal, payment request information generated for the payment card when performing a non-face-to-face transaction using the payment card; And it proposes a non-face-to-face transaction and settlement method comprising the step of processing the payment approval using the information contained in the payment request information.

Another aspect of the present invention is a non-face-to-face transaction and settlement management server using the virtual payment information, issuing a payment card for non-face-to-face transactions at the request of the merchant, through the service application running on the user terminal, the payment A card issuing unit for posting a card for payment; And a payment processing unit that receives payment request information generated for the payment card when the user terminal performs a non-face-to-face transaction using the payment card, and processes payment approval using information included in the payment request information. It includes.

The management server may further include a settlement processing unit for receiving whether or not to accept or reject the payment approval details from the merchant terminal, the settlement processing unit outputs an electronic receipt issuing menu for the received payment approval details, The electronic receipt issuance request message may be received from the affiliated store terminal, and the electronic receipt may be issued and transmitted to the user terminal with respect to the payment approval details of the received request message.

According to the non-face-to-face transaction and settlement system of the present invention, payment can be made for offline merchants without a separate merchant payment terminal. In particular, in the case of street vendors that are difficult to use the payment terminal, the transaction history can be checked and acquired through the mobile phone possessed by the store owner, so there is no installation and operation cost of the payment terminal. It can contribute to promoting the dissemination of transactional services.

According to the present invention, unlike conventional online payment, by realizing non-face-to-face payment using a prepaid electronic card, payment service can be implemented without the intervention of a payment gateway (PG) company or a value added network (VAN) company. As such, if there is no mediation between the PG company and the VAN company, it may give an opportunity to reduce a large payment fee.

In addition, from the user's point of view, since the non-face-to-face payment is possible without the visit of the offline merchant using the purchased prepaid electronic card, the user convenience is improved. Furthermore, according to the embodiment, payment can be made without a complicated approval process or authentication process at the time of non-face-to-face payment, thereby realizing quick and convenient payment.

1 is a schematic diagram showing a non-face-to-face transaction and settlement system according to an embodiment of the present invention.
2 is a block diagram illustrating a management server of a non-face-to-face transaction and settlement system according to an embodiment of the present invention.
3 is a flowchart illustrating a non-face-to-face transaction and settlement procedure according to an embodiment of the present invention.
4 is a screenshot on a user terminal for explaining a payment processing procedure of a non-face-to-face transaction and settlement system according to an embodiment of the present invention.
5 is a screenshot on an affiliated store terminal for explaining a payment processing procedure of a non-face-to-face transaction and settlement system according to an embodiment of the present invention.
Like reference symbols in the various drawings indicate like elements.

Specific structural or functional descriptions of the embodiments according to the inventive concept disclosed herein are provided only for the purpose of describing the embodiments according to the inventive concept. It may be embodied in various forms and is not limited to the embodiments described herein.

Embodiments according to the inventive concept may be variously modified and have various forms, so embodiments are illustrated in the drawings and described in detail herein. However, this is not intended to limit the embodiments in accordance with the concept of the invention to the specific forms disclosed, it includes all changes, equivalents, or substitutes included in the spirit and scope of the present invention.

Terms such as first or second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another, for example without departing from the scope of the rights according to the inventive concept, and the first component may be called a second component and similarly the second component. The component may also be referred to as the first component.

When a component is said to be "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may exist in the middle. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that no other component exists in the middle. Other expressions describing the relationship between components, such as "between" and "immediately between" or "neighboring to" and "directly neighboring", should be interpreted as well.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, terms such as "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described herein, but one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are not construed in ideal or excessively formal meanings unless expressly defined herein. Do not.

1 is a schematic diagram illustrating a non-face to face transaction and settlement system 100 according to an embodiment of the present invention. The payment system 100 of the present invention includes a user terminal 110, a merchant terminal 120, and a management server 200 of a service provider.

The user may carry the user terminal 110. The user terminal 110 may be a mobile phone, a smart phone, a smart pad, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), navigation, a tablet. Various wearable devices such as PCs and smart watches, smart bands, and the like. However, the present invention is not limited thereto, and may be various types of devices having a communication function capable of wireless communication and a separate application capable of executing a payment service.

The user terminal 110 may install and drive a service application provided by the management server 200. The user terminal 110 may download a service application provided by the management server 200 from an application market (eg, an app store or a Google play market). As an embodiment, a security application for payment may be installed together.

In one embodiment, the affiliated store terminal 120 may be a terminal possessed by the affiliate store owner. Merchant terminals are similar to user terminals, such as mobile phones, smart phones, smart pads, notebook computers, digital broadcasting terminals, PDAs (Personal Digital Assistants), and PMPs. Player), navigation, tablet PCs and smart watches, various wearable devices such as smart bands, and the like. In addition, as a separate terminal installed in the merchant, it includes various types of payment terminals such as a point-of-sale system, a credit authorization terminal (CAT), and a near field communication (NFC) terminal.

For example, the affiliated store terminal 120 may be implemented as a separate terminal (for example, an electronic device having an input device and a display device, such as a scanner), or may be implemented in various forms such as software in a PC or employee mobile terminal owned by a store. It may be an electronic device.

The affiliated store terminal 120 may also install and drive a service application provided by the management server 200, and may check and settle a transaction history and the like during non-face-to-face transactions through the service application.

The management server 200 refers to a service server operated by a service provider, and implements the transaction system of the present invention through a service application to a user and a merchant. The management server 200 may transmit and receive transaction information with the user terminal 110 and the merchant terminal 120, and may operate in conjunction with financial companies such as card companies and banks.

As an embodiment, the management server 200 may perform non-face-to-face transactions and settlement in connection with the user terminal 110 and the affiliated store terminal 120. The management server 200 may issue a payment card at the request of the affiliated store terminal 120. When the user terminal 110 performs a non-face-to-face transaction for a payment card, the management server 200 may receive and analyze payment request information and process payment approval. Thereafter, the management server 200 may notify the affiliated store terminal 120 of the payment approval result, and the affiliated store terminal 120 may perform settlement after checking the payment details.

In one embodiment, the management server 200 may be a service card based on the host card emulation (HCE). The management server 200 does not store personal information such as card information in a hardware SE such as a universal integrated circuit card (UICC) and an embedded secure element (SEC), but does not store the personal information in an operator server that performs a cloud SE (or cloud platform) function. It can be implemented to store and manage. In addition, in order to solve the security problem when implementing the HCE technology, by adopting tokenization technology (tokenization), issuing a token corresponding to the card information (for example, PAN), the card information or personal information is exposed during the transaction process Can be implemented to prevent this from happening.

In addition, when the management server 200 is an HCE-based server, the management server 200 may be implemented to interwork with a TSP (Token service provider) server. The TSP server issues a token value corresponding to PAN (Primary Account Number) information for the card issuing request received from the user terminal 110. Token value is virtual payment information, and plays the same role as PAN when making a payment, but unlike PAN, it can be changed to a new token value when leaking. The TSP server may store the issued token value and PAN information in a table form. As another embodiment, the TSP server may be implemented to store using a predetermined algorithm capable of inferring a value between the token value and the PAN information, or to store only a path to the mapping table of the token value and the PAN value.

The transaction system 100 according to an embodiment of the present invention may issue a payment card containing merchant information, and the payment card may be issued in the form of an HCE card containing a token value instead of the card information. The user terminal 110 may purchase a card for payment to perform a non-face-to-face transaction, and generate payment request information for a non-face-to-face transaction to request a payment. The management server 200 performs a payment approval process through the information extracted from the received payment request information. Thereafter, the affiliated store terminal 120 may transmit a payment notification and details to the affiliated store terminal 120, and may perform settlement upon request from the affiliated store terminal 120.

In addition, the management server 200 may apply a security function to the service application and the communication section. The management server 200 may secure the service application itself from hacking or rooting by applying a vaccine, an application forgery prevention function, and a security keypad for detecting forgery and alteration in the application itself. The management server 200 may encrypt and manage card information and key values used for payment. For example, card information and key values used for payment may be encrypted with a storage key and stored in a database in the user terminal 110. Also, the key can be embedded in the encryption algorithm itself to prevent leakage of the storage key.

The management server 200 may perform a double encryption process in communication between the service application and the management server 200. The management server 200 generates a new encryption key for every communication, first encrypts all the transmitted data with a one-time mobile session key, and then performs double encryption using a secure communication protocol during communication. By doing so, the confidentiality and integrity of the data can be guaranteed.

In such a transaction system using a mobile card of the present invention, it is possible to support payment using a token value, which is virtual payment information, and there is an advantage that non-face-to-face payment for offline merchants is possible without a separate terminal.

In addition, in the prepaid card payment system, by using non-face-to-face payment, non-face-to-face payment such as online payment is possible by utilizing the information contained in the prepaid card at the time of issuance, thereby maximizing user convenience and practicality.

2 is a block diagram illustrating a management server 200 of a non-face to face transaction and settlement system according to an embodiment of the present invention. In the present specification, a description will be mainly given of a method of performing a payment using a prepaid electronic card in a non-face to face transaction. The management server 200 may include a payment card issuing unit 210, a payment processing unit 220, a settlement processing unit 230, a user DB 240, an affiliated store DB 250, and a settlement history DB 260. . In the present specification, the case where the management server 200 performs a non-face-to-face transaction and settlement is mainly described, but is not limited thereto. The management server 200 may perform a transaction and settlement in connection with a settlement server or another financial company server. have. The management server 200 may be implemented in the form of a platform server for implementing a payment service, and each component 210 to 260 constituting the management server 200 may be implemented in the form of a server.

In addition, the present specification has been described mainly for the school fee payment process, but is not limited thereto, and the present invention may be utilized in various non-face-to-face payment areas such as donation payment and tuition payment.

The card issuer 210 for payment is a component that issues a card at the request of an affiliated store, and may be implemented in a processor or server form. In one embodiment, the payment card issuing unit 210 manages the life cycle of the KOD server, users and services that perform stakeholder management and card service management, and handles the request and push of the service application Mobile Application Platform ) Servers, servers managing prepaid card issuance requests and other service menus, servers processing card issuance requests, servers managing PAN information and key values, creating HCE digital cards, managing card lifecycles and generating digital keys It may include a DCP (Digital Card Platform) server.

In one embodiment, the card for payment may be issued in the form of a fixed price ticket or a chargeable form in accordance with the agreement with the merchant. The payment card issuing unit 210 may generate and store token values, card IDs, and PAN information of the new card when issuing a new card. In addition, the payment card issuing unit 210 may issue a payment card containing the token value to the user terminal, and output the card list including the payment card to the user terminal 110 through the service application. The user terminal 110 may use the non-face-to-face payment after purchasing a card to pay. For example, if the merchant A school requested a payment card for payment of school fees in January, the payment card issuing unit 210 may issue a school card payment card for the school A, and the validity period is 2017. Can be specified until January 31st. In addition, if the school fee is a flat fee, the amount can be issued with a flat card.

In one embodiment, the payment card may be a one-time card for non-face-to-face payment. That is, after the user terminal 110 selects the card and pays it, the user terminal 110 may delete the card. In another embodiment, the non-face-to-face payment card may be managed in a separate list.

The card issuer 210 for payment may issue a card in conjunction with a user DB 240 and an affiliated store DB 250. In addition, when the payment card is issued, the token value may be linked with the TSP server for generating and storing the token value, and the TSP server may map and store the token value with the card information.

The payment processor 220 is a processor (or server) that processes payment request information received from the user terminal 110. The payment processor 220 may be implemented as one or more servers for payment processing. For example, when receiving payment request information, the payment processor may include a payment processor (PP) server for processing a payment message and an issuer token adapter (ITA) server for processing cryptographic verification and PAN-token conversion requests. As an embodiment, the ITA server may convert and verify the token value by interworking with a Token Service Provider (TSP) server that stores the PAN value and the token value. In addition, the payment processing unit 220 may include a server that performs the final approval processing, refund processing, balance management. In addition, it may include a server for relaying transaction authentication and information, and a virtual VAN server providing a transaction interface by providing a virtual VAN when there is no VAN.

When the payment processing unit 220 receives payment request information from the user terminal 110, the payment processing unit 220 extracts merchant information and user input information included in the payment request information. Merchant information may be a merchant number or merchant ID. The user's input information includes information selected or directly written by the user through a service application for a predetermined item. For example, in the case of the school fee payment card, the user input information may include a student name, a payment month (for example, a specific month or three months), a trade name, a representative, and other memo items. The user input information 450 may be implemented to directly write or check the output contents, and various items may be set for each payment card according to a merchant request or according to a manager's setting.

The payment request information may include a token value corresponding to the amount of the payment card and the PAN value in addition to the merchant information and the user input information. The payment card according to an embodiment of the present invention is a prepaid card, and since the issuer or affiliate store is specified in the card itself, the card itself includes affiliate store information, an amount, and a token value. Therefore, non-face-to-face payment using a prepaid card is possible without a separate approval process. That is, since the payment and approval through the financial institution in the charging and purchasing process of the payment card, it is possible to pay through the management server 200 in the non-face-to-face payment process without intervention of VAN company or PG company.

The settlement processing unit 230 may process settlement for the non-face-to-face payment details performed on the affiliated store terminal 120. The settlement processor 230 may manage a report for each transaction, and manage a report for each stakeholder (for example, a transaction record for each merchant) and a settlement detail (payment for a merchant, payment for a refund, etc.). In one embodiment, the settlement processing unit 230 may be arranged in a non-face-to-face payment history carried out through the user terminal 110 according to the daily, monthly or a predetermined method so that the merchant terminal 120 can be viewed. In addition, the merchant terminal 120 may check (or approve) or cancel the non-face-to-face payment details received by the merchant terminal 120.

In one embodiment, the settlement processing unit 230 of the management server 200 transmits the payment details to the payment terminal of the merchant (for example, a separate POS terminal or merchant PC other than the merchant owner terminal 120) with respect to the non-face-to-face payment history. Can be. The affiliated store owner can check the non-face-to-face payment details and settlement details and settlement processing results provided by the management server 200 through not only the affiliated store terminal 120 but also other terminals installed in the affiliated store.

As such, the payment card issuing unit 210, the payment processing unit 220, and the settlement processing unit 230 performing non-face-to-face payments include a user DB 240 storing user information and an affiliated store DB 250 storing merchant information. ), Non-face-to-face transactions and settlement can be performed in conjunction with the settlement details DB 260 that manages and stores settlement details.

According to the present invention, unlike conventional online payment, by realizing non-face-to-face payment using a prepaid electronic card, payment service can be implemented without intervention of a payment gateway (PG) company or a value added network (VAN) company. In addition, even in an offline store, when the non-face-to-face payment, there is no need to visit and pay the merchant, there is an advantage that there is no need to install a payment terminal in the merchant. As such, if there is no intermediary between PG and VAN, payment fees can be reduced, and there is no installation and operation cost of payment terminals, thereby maximizing the economic benefits of the merchant.

In addition, from the user's point of view, since the non-face-to-face payment is possible without the visit of the offline merchant using the purchased prepaid electronic card, the user convenience is improved. In addition, according to the embodiment, payment can be made without a complicated approval process or authentication process when face-to-face payment, it is possible to realize a quick and convenient payment.

3 is a flowchart illustrating a non-face-to-face transaction and settlement procedure according to an embodiment of the present invention. The management server 200 may issue a payment card according to a contract or a request with an affiliated store (step 310). As described above, the payment card may be issued in the form of a flat card or a prepaid card. In addition, the payment card may include information on the expiration date (designated time limit), and may be issued for a single use or for a month (eg, for payment in January 2017).

In one embodiment, the payment card includes card information for payment. If the payment card is a flat pass, it includes a fixed amount. In addition, the card for payment may include at least one of a merchant name, a number, an identifier (ID), or a merchant phone number as merchant information. User information, such as user nickname or name, may also be included, depending on whether it is named or anonymous. In addition, the management server of the present invention can issue card information in the form of a token value according to the implementation of HCE-based mobile payment. That is, the payment card may be issued including card information (token value), merchant information, amount information, and the like.

As payment cards used in a plurality of affiliates are issued, the management server 200 may transmit the payment cards in a list form (step 320). For example, the management server 200 may output a list of purchaseable payment cards through a service application running on the user terminal 110.

As another example, the management server 200 may analyze a user's purchase tendency or location and provide a customized list. In another embodiment, when the merchant terminal 120 requests a specific payment card to be issued, the user terminal 110 pops up, links to the top of the list, or links the payment card of the requested merchant in the form of push notification or SMS. Can be implemented to be deployed.

The user terminal 110 may select a payment card to purchase and purchase a payment card within a charged amount. As an example, when the charged amount is less than the payment card amount, the user may be guided to perform the charging process on the service application. After the payment card is purchased using the charged amount, the payment card may be displayed in the user's holding card list (see FIG. 4A). The user may confirm that the purchased card is stored in the list, and perform a non-face-to-face transaction using the card. For example, in the case of a non-face-to-face transaction-only card, other menus (eg, offline payments, gifts, etc.) except for the non-face-to-face transaction may be displayed in an inactive state.

The user terminal 110 may input necessary user information according to the guidance of the service application (step 340, see FIG. 4 (b)). As shown in FIG. 4B, in the input menu 450, necessary items may be input or selected, and the input information may be confirmed in the following process. Information to be input by the user may be specified at the request of the affiliated store or may be specified by the management server according to the type of payment card. For example, in the case of a card for payment of school expenses, it may be implemented to input a payer name (or nickname), a student name, a payment month, a discount code, and other memos.

When the user's input is completed, the input information may be confirmed, and the user may input authentication information (eg, a PIN) after verification (step 350). As one embodiment, when the authentication information is a PIN, the user may implement a payment password set through the service application as a PIN or input a PIN set for non-face-to-face payment only. In another embodiment, the authentication information may include biometric authentication information and may include fingerprint information, face recognition information, iris recognition information, and the like. The authentication information may be implemented to perform one-time authentication or to perform additional authentication by combining PIN and biometric authentication.

When the user completes input of the authentication information, the user terminal 110 generates payment request information to be transmitted to the management server 200 (step 360). The payment request information may include at least one of a token value of a payment card included in issuing a payment card, a token validity period, a token ID generated each time a token transaction is made, amount information, and merchant information (eg, merchant number). In addition, when the payment request information has a field describing a payment terminal ID (Terminal ID) value, the management server may be assigned or replaced with an affiliate store number. In addition, the payment request information may include a token value and a cryptogram. A cryptogram is a value generated using a payment key for payment data used for payment, and the verification of the cryptogram is performed by the management server 200. At this time, the payment key is stored in a secure area that cannot be hacked, thereby preventing misuse through hacking or duplication. As an embodiment, the payment key may be implemented to be automatically discarded after a certain number of times of use. In addition, the payment request information may include user input information. The user input information may be included in the full text of the payment request or transmitted together as additional information.

In one embodiment, the payment request information may be configured according to the ISO8583 message standard of the payment message, the configuration values included in the message may be defined by the management server 200.

In one embodiment, the payment request information may be encrypted through an encryption process. The payment request information may be encrypted using a previously stored encryption key or an encryption key issued in real time from the management server, and the encrypted payment request information may be transmitted to the management server 200.

The management server 200 may receive payment request information and, if encrypted, decrypt the payment request information (step 370). The management server 200 may extract affiliate store information and user input information included in the payment request information (380). Since the management server 200 is an approval for the card already purchased, the management server 200 may process the approval of the payment request without the approval and purchase procedure of a separate financial institution (step 390). However, in order to confirm whether the payment is made by the real user, the authentication information stored in the management server 200 and the authentication information input during the transaction may be matched and checked.

When the authentication information is confirmed, the management server 200 may transmit payment approval information to the user terminal 110, and the user terminal may receive and confirm payment approval information (steps 392 and 398).

On the other hand, the management server 200 may transmit a notification message notifying the occurrence of the non-face-to-face transaction to the merchant terminal 120 when the payment is approved (step 394). In one embodiment, the notification message may be transmitted in the form of an SMS or may be implemented in the form of a pop-up message when the service application is executed. As another embodiment, the mobile terminal 120 may be configured to receive a notification or check the details on a regular basis such as daily or monthly, without receiving a separate notification message according to the setting of the affiliated store terminal 120.

The affiliated store terminal 120 may check payment approval information and view payment approval details. As described above, the management server 200 may be implemented to transmit the collected payment details to the merchant terminal 120, or to another payment terminal (eg, POS terminal or merchant PC of the merchant).

In one embodiment, the affiliated store owner may check the non-face-to-face transaction details through the affiliated store terminal 120, and may determine whether to take over (step 396). Merchant terminal 120 may check the payment approval history and select the acceptance or rejection. For example, when the amount or the user information is incorrectly settled or duplicated settled, the merchant may refuse to take over the stock price and execute the cancellation transaction.

As another embodiment, the merchant terminal 120 may be implemented to perform an additional authentication procedure upon acquisition. For example, the management server 200 may transmit an approval message to the affiliated owner's terminal when the payment approval information is notified, and the approval message may include a one-time number or an authentication number. Merchant can enter the authentication number included in the approval message to implement the payment for the payment. When performing this additional certification, the merchant's stock goes through the verification process for certain payments, thereby reducing the risk of acquisition by others.

The affiliated store terminal 120 may request issuance of an electronic receipt to the user terminal 110 for the transaction details acquired, and the management server 200 may receive a issuance request and issue a receipt to the user terminal 110. . The receipt may be issued through a service application provided by the management server 200 or may be issued in an SMS form.

According to the non-face-to-face transaction and settlement system of the present invention, payment is possible at an offline merchant without a separate merchant payment terminal. In particular, in the case of a street vendor that is difficult to use the payment terminal, it is possible to contribute to the promotion of the electronic transaction service as the transaction history can be confirmed and acquired through the mobile phone possessed by the store owner.

4 is a screenshot on a user terminal 110 for explaining a payment processing procedure of a non-face-to-face transaction and settlement system according to an embodiment of the present invention. 4 (a) shows a screen outputting a payment card purchased through the service application. For example, in the case of purchasing a 300,000 won flat card issued by a picture and a child art academy (member), the picture and child art academy card 420 can be displayed on the screen 410 of the user terminal 110. have. The list of remaining cards owned by the user can also be displayed at the bottom. As an example, the present, charge, and non-face-to-face transaction (payment) menus may be displayed for a picture and a child art school card. In this case, when the picture and the child art school card is a non-face-to-face transaction-only card, the remaining menus (gift and charge) may be displayed in a deactivated state, and the non-face-to-face transaction menu 430 may be displayed in an activated form.

When the user selects the non-face-to-face transaction menu 430, a non-face-to-face transaction (payment) procedure is started through data transmission and reception with the management server 200 (Fig. 4 (b)). The management server 200 may output the guide page 440 according to the non-face-to-face transaction request. The user may check card information displayed on the user terminal 110 and a description of information to be input, and input information. The user input information 450 may be directly described or implemented in a form of selecting a corresponding item.

When the user presses the OK button after completing the input, the management server 200 guides a page 460 for inputting authentication information (FIG. 4C). As an example, before the authentication information is input, the details of the non-face-to-face payment 470 may be checked, and the user may input the authentication information PIN 480 after checking the contents. When the user inputs the authentication information, the user terminal 110 generates payment request information using information and input information of the payment card. As one embodiment, the user terminal 110 may be implemented to perform the payment request information generation procedure in a separate security application to enhance security, or may be implemented to encrypt the generated payment request information.

5 is a screenshot on an affiliated store terminal for explaining a payment processing procedure of a non-face-to-face transaction and settlement system according to an embodiment of the present invention. As an embodiment, when the non-face-to-face payment is completed, the payment approval notification message may be received on the affiliated store terminal 120. For example, as shown in (a) of FIG. 5, it may be received in the form of an SMS message 510. However, the present invention is not limited thereto, and the transaction approval may be notified in various forms such as a push message or an application icon notification.

In another embodiment, the transaction notification after the transaction approval may be transmitted to the affiliated store terminal 120 in the form of a barcode or QR code. If the management server 200 is non-face-to-face transaction approval can transmit the transaction information to the merchant terminal in the form of a two-dimensional code, the merchant owner receives it, merchant terminal 120 or a separate payment terminal (POS terminal, merchant PC or The code scanner may be used to recognize a code and retrieve payment details.

When the affiliated store owner executes the service application through the affiliated store terminal 120, the approval details of the non-face-to-face transaction may be confirmed (FIG. 5B). In one embodiment, the non-face-to-face transaction can be viewed only through a terminal possessed by a person having a merchant main account or a manager account, and the transaction history is read through a separate authentication procedure (PIN or biometric authentication). It can also be implemented.

The affiliated store owner may check the transaction approval list 530 through the affiliated store terminal 120, and may check details of settlement (acquisition), details pending payment, cancellation (rejection), and the like. It is possible to select whether to accept a transaction with respect to the details of the acquisition target 530. As an example, when the transaction is acquired, the settlement may be marked as completed and the electronic receipt sending menu 540 may be output ((c) of FIG. 5).

The merchant may select the electronic receipt issuing 550 to request management of the electronic receipt from the management server 200, and output the electronic receipt to the user terminal 110 through the management server or a separate receipt issuing server.

By implementing such a non-face-to-face transaction service, the hassle of existing online and offline transactions can be reduced, and convenience can be provided to merchants and users. In particular, merchants do not need to install a payment terminal, and the transaction purchase process is unnecessary, so there is no need to go through a VAN company or a PG company, thereby significantly reducing the transaction fee.

Although the present invention has been described with reference to one embodiment shown in the drawings, this is merely exemplary, and those skilled in the art will understand that various modifications and equivalent other embodiments are possible therefrom. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

100: non-face-to-face transaction system 110: user terminal
120: merchant terminal 200: management server
210: payment card issuing unit 220: payment processing unit
230: settlement processing unit 240: user DB
250: Merchant DB 260: Settlement history DB

Claims (20)

A non-face-to-face transaction and settlement method using virtual payment information performed by a management server that provides a non-face-to-face transaction service,
Receiving a request for issuing a payment card for a non-face-to-face transaction at the affiliated store together with designation of user input information to be provided at the affiliated store after a non-face-to-face transaction from a plurality of affiliated stores;
Issuing a payment card for a non-face-to-face transaction at the specified affiliated store by specifying the requested affiliated store information according to requests from the plurality of affiliated stores;
Displaying a screen for posting the payment card and inputting the designated user input information to the payment card through a service application running in a user terminal;
Receiving authentication information of the payment card after the user input information is input;
When the user terminal performs a non-face-to-face transaction using a payment card including the merchant information, the specific merchant information read from the issued payment card is input through a screen for inputting the designated item. Receiving, by the management server, payment request information generated including user input information and the authentication information;
Confirming, by the management server, matching stored authentication information and authentication information input during the transaction;
Processing a payment approval for the affiliated store by using the affiliated store information included in the payment request information;
Transmitting non-face-to-face payment details to the terminal of the affiliated store; And
Non-face-to-face transaction and settlement method comprising the step of allowing the merchant terminal to check the user input information based on the non-face-to-face payment history. The method of claim 1,
The issuing of the payment card may include generating and storing a token value, which is virtual payment information corresponding to a primary account number (PAN) value of the payment card,
The payment card is issued to further include at least one of the token value, the card amount and the expiration date, non-face to face transaction and settlement method. The method of claim 1,
The payment card is a prepaid card, characterized in that it is issued in a flat form or rechargeable, non-face-to-face transaction and settlement method. The method of claim 1,
The posting may include posting one or more cards issued for each affiliate in the form of a list or recommendation according to predetermined criteria. The method of claim 1,
The user input information,
A non-face-to-face transaction and settlement method comprising at least one of a payer name, a payee beneficiary name, and a discount code. The method of claim 1,
The payment request information is generated further including at least one of payment amount information, expiration date, and a token value of a payment card, and generates a cryptogram value by using a payment key generated for each transaction. A non-face-to-face transaction and settlement method comprising the. The method of claim 1,
Processing the payment approval,
The information stored in the management server and the information included in the payment request information is compared, and if all the information is matched, characterized in that the payment is approved, non-face to face transaction and settlement method. The method of claim 1,
After the payment approval processing, transmitting the payment approval details to the merchant terminal; And
The non-face-to-face transaction and settlement method further comprising the step of receiving whether to accept or decline the payment approval history from the merchant terminal. The method of claim 8,
Outputting an electronic receipt issuance menu for the received payment approval details;
Receiving an electronic receipt issuance request message from the affiliated store terminal; And
The non-face-to-face transaction and settlement method further comprising the step of issuing and transmitting an electronic receipt to the user terminal with respect to the payment approval history received the request message. The method of claim 8,
The step of transmitting the payment approval history,
Transfer to a payment terminal or merchant computer (PC) installed in the merchant,
The payment terminal includes a point of sales (POS) terminal or a credit authorization terminal (CAT) terminal. As a non-face-to-face transaction and settlement management server using virtual payment information,
After a non-face-to-face transaction from a plurality of merchants, a request for issuance of a card for payment for non-face-to-face transaction at the affiliated store is issued along with designation of user input information to be provided at the affiliated store, and the user for the payment card Issuing a payment card for posting the payment card and displaying the screen for inputting the user input information through a service application driven by the user terminal to receive input information, and receiving the authentication information of the payment card part;
When the user terminal performs a non-face-to-face transaction using a payment card including the affiliated store information, the user terminal is input through a screen for inputting the corresponding affiliated store information read from the issued payment card and the user input information. Received payment request information including user input information and the authentication information, and processes payment approval for the affiliated store by using the affiliated store information and authentication information included in the payment request information, and performs non-face-to-face payment. A non-face-to-face transaction and settlement management server including a payment processing unit that allows the affiliated store to check the user input information as the details are transmitted to the affiliated store. The method of claim 11,
The payment card issuing unit generates and stores a token value, which is virtual payment information corresponding to the PAN value of the payment card,
The payment card is issued to further include at least one of the token value, the card amount and the expiration date, non-face to face transaction and settlement management server. The method of claim 11,
The payment card is a prepaid card, characterized in that it is issued in a flat or rechargeable, non-face to face transaction and settlement management server. The method of claim 11,
The payment card issuing unit,
A non-face-to-face transaction and settlement management server, characterized by posting one or more cards issued for each merchant in a list or recommendation form according to predetermined criteria. The method of claim 11,
The user input information,
A non-face-to-face transaction and settlement management server, characterized in that it comprises at least one of a payer name, payment beneficiary name, and a discount code. The method of claim 11,
The payment request information further includes at least one of payment amount information, an expiration date, and a token value of a payment card, and further includes generating and generating a cryptogram value by using a payment key generated for each transaction. Non-face-to-face transaction and settlement management server, characterized in that. The method of claim 11,
The payment processing unit,
And the information stored in the management server and the information included in the payment request information, and approving the payment if all the information is matched. The method of claim 11,
The payment processing unit transmits a payment approval history to the merchant terminal after payment approval processing,
The non-face-to-face transaction and settlement management server further comprises a settlement processing unit for receiving whether or not to accept or reject the payment approval details from the merchant terminal. The method of claim 18,
The settlement processing unit,
Outputting an electronic receipt issuance menu for the received payment approval details, receiving an electronic receipt issuance request message from the merchant terminal, issuing and transmitting an electronic receipt to the user terminal with respect to the payment approval details that have received the request message; Non-face-to-face transaction and settlement management server, characterized in that. The method of claim 18,
The payment processing unit transmits to the payment terminal or merchant computer (PC) installed in the merchant at the time of payment approval history transmission,
The payment terminal is a non-face-to-face transaction and settlement management server comprising a point of sales (POS) terminal or a credit authorization terminal (CAT) terminal.

Images