KR20180106456A - Payment system and method using mobile terminal - Google Patents

Abstract

The present invention proposes a payment method using a mobile terminal and a payment method using a first mobile terminal held by a customer and a second mobile terminal held by a payer through a service application provided by a management server. The payment method includes the steps of: a first mobile terminal selecting a payment card through the service application; Receiving a payment information from a second mobile terminal and generating a payment code using the payment information; The second mobile terminal outputting the payment code for a predefined valid time; Recognizing the billing code output to the second mobile terminal using the first mobile terminal; And transmitting, at the first mobile terminal, the payment request information included in the payment code to the management server to request payment approval.

Description

TECHNICAL FIELD [0001] The present invention relates to a payment system and a payment method using a mobile terminal,

The present invention relates to a payment system and method using a mobile terminal. More particularly, the present invention proposes a payment system and a method for implementing a payment using a payer or a mobile terminal owned by the user as a payment terminal.

Recently, various payment methods using mobile terminals have been developed. A settlement may be carried out using an authentication code such as a bar code or a QR code at a store, or a settlement may be performed using short-range wireless communication (for example, NFC).

However, all of these payment methods perform payment using a dedicated payment terminal such as a POS terminal or a CAT terminal, and all the merchants need to have one or more payment terminals. In addition, there has been a problem in that a high commission is paid at the time of settlement, as payment is performed through an intermediary company (for example, VAN company) that manages the payment terminal.

As a part of these various payment methods, the payment service method and system of Korean Laid-Open Patent Application No. 2012-00130023 proposes a method in which a user makes a payment directly using the billing statement output from the merchant selling system. However, since such a payment method can be utilized in a case where a merchant selling system or a module capable of outputting a statement is provided in a store, the payment terminal itself is merely suggested as a payment method of the user, and the mobility of the payment terminal is not guaranteed.

Korean Patent Laid-Open No. 10-2012-0130023 (disclosed on Nov. 28, 2012)

The present invention proposes a settlement method and system that solves the problems of the prior art and implements settlement using a mobile terminal held by a user and a payer without a separate settlement-only terminal.

The present invention proposes a payment method using a mobile terminal and a payment method using a first mobile terminal held by a customer and a second mobile terminal held by a payer through a service application provided by a management server. The payment method includes the steps of: a first mobile terminal selecting a payment card through the service application; Receiving a payment information from a second mobile terminal and generating a payment code using the payment information; The second mobile terminal outputting the payment code for a predefined valid time; Recognizing the billing code output to the second mobile terminal using the first mobile terminal; And transmitting, at the first mobile terminal, the payment request information included in the payment code to the management server to request payment approval.

According to another aspect of the present invention, there is provided a payment system using a mobile terminal, the method comprising: issuing a settlement card for on-site settlement in response to a request from an affiliated store; receiving, via a service application running on a first mobile terminal, And a second mobile terminal for receiving the payment request information generated for the payment card when the first mobile terminal performs the field settlement using the payment card, And a payment processing unit for processing the payment approval using the received information; A second mobile terminal for inputting payment information through a service application provided by the service server and generating and outputting a payment code using the payment information; And the first mobile terminal selecting the payment card through the service application, recognizing the payment code output to the second mobile terminal, and transmitting the payment request information to the management server.

According to the settlement system and method of the present invention, it is possible to settle an offline merchant without a separate settlement-only terminal. Particularly, in the case of a street vendor which is difficult to use a payment terminal, it is possible to make payment through a mobile phone owned by a shop owner, and there is no installation and operation cost of the payment terminal, thereby maximizing the economic benefit of the merchant, And the like.

According to the present invention, a payment service can be implemented without the involvement of a payment gateway (PG) or a value added network (VAN) company by realizing a non-face-to-face payment using a prepaid electronic card unlike the existing payment. In this way, if there is no intermediary between PG and VAN, it is possible to give an opportunity to save a large payment commission.

Also, since the user performs settlement using a mobile phone (smart phone) possessed by the user without using a separate settlement means, user convenience is improved. Furthermore, it is possible to make payments without complicated approval procedures or authentication procedures, thereby realizing prompt and convenient settlement.

1 is a schematic diagram showing a payment system according to an embodiment of the present invention.
2 is a block diagram illustrating a management server of a billing system according to an embodiment of the present invention.
3 is a flowchart illustrating a settlement procedure of the settlement system according to an embodiment of the present invention.
4 is a screen shot on the payer's terminal for explaining the procedure of the payment method according to an embodiment of the present invention.
5 is a screen shot on a user terminal for explaining a procedure of a payment method according to an embodiment of the present invention.
Like reference numbers in the several drawings indicate like elements.

It is to be understood that the specific structural or functional description of embodiments of the present invention disclosed herein is for illustrative purposes only and is not intended to limit the scope of the inventive concept But may be embodied in many different forms and is not limited to the embodiments set forth herein.

The embodiments according to the concept of the present invention can make various changes and can take various forms, so that the embodiments are illustrated in the drawings and described in detail herein. It should be understood, however, that it is not intended to limit the embodiments according to the concepts of the present invention to the particular forms disclosed, but includes all modifications, equivalents, or alternatives falling within the spirit and scope of the invention.

The terms first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The terms may be named for the purpose of distinguishing one element from another, for example, without departing from the scope of the right according to the concept of the present invention, the first element may be referred to as a second element, The component may also be referred to as a first component.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that no other element exists in between. Other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent to" should be interpreted as well.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprises" or "having" and the like are used to specify that there are features, numbers, steps, operations, elements, parts or combinations thereof described herein, But do not preclude the presence or addition of one or more other features, integers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the meaning of the context in the relevant art and, unless explicitly defined herein, are to be interpreted as ideal or overly formal Do not.

1 is a schematic diagram showing a payment system 100 according to an embodiment of the present invention. The payment system 100 of the present invention includes a user terminal 110, an affiliate terminal 120, a payer terminal 130 and a management server 200 of a service provider.

A user may have a 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 PDA (Personal Digital Assistants), a PMP (Portable Multimedia Player), a navigation device, PCs, and various wearable devices such as smart watches, smart bands, and the like. However, the present invention is not limited to this, 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 operate a service application provided by the management server 200. [ The user terminal 110 can download a service application provided by the management server 200 in an application market (for example, an application store or a Google Play market). In one embodiment, a secure application for payment may be installed together.

In an embodiment, the merchant terminal 120 may be a settlement-only terminal installed at an affiliated store or a settlement terminal paid by an affiliate shop. The payment-only terminal may include various types of payment terminals, such as a point-of-sale (POS) system, a credit authorization terminal (CAT), and a near field communication (NFC) terminal. When the merchant terminal 120 is the settlement terminal of the merchant store, the merchant terminal 120 may be a mobile phone of a merchant store, a smart phone, a smart pad, a notebook computer, a digital broadcast terminal, a PDA Personal digital assistants (PMPs), portable multimedia players (PMPs), navigation, tablet PCs, smart watches, and smart bands. In this specification, the merchant terminal 120 is a settlement terminal for distinguishing from the payer terminal 130, and may be a settlement terminal disposed at a representative terminal or an affiliated store, 120 < / RTI >

In one embodiment, the merchant terminal 120 may be implemented in a separate terminal (e.g., an electronic device having an input device and a display device such as a scanner) or implemented in software in a PC or employee mobile terminal Lt; / RTI >

The merchant terminal 120 can also install and operate the service application provided by the management server 200, and can confirm transaction details and settle the transaction when the transaction is generated through the service application.

In one embodiment, the merchant terminal 120 may be implemented to be interlocked with the payer terminal 130. For example, when an order is received through the merchant terminal 120, the merchant can transmit the order details to the payer terminal 130 owned by any employee via wired / wireless communication, and the payer terminal 130 And can perform payment with the customer using the received order history.

The payer terminal 130 is a portable terminal carried by a mobile employee such as an employee of a franchisee, a visiting salesperson, a salesperson or a delivery person, and can implement a self-payment function using a service application provided by the management server 200 Device. Mobile phones, smart phones, smart pads, notebook computers, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigation, tablet PCs, And various wearable devices such as bands. For example, if the employee is an employee in the store, the payment terminal 130 can be implemented to perform settlement in the customer table, and if the employee is a delivery employee, the settlement can be implemented together with the customer at the place of visit .

The management server 200 refers to a service server operated by a service provider, and implements the payment system of the present invention through a service application to a user and an affiliate shop. The management server 200 can transmit and receive transaction information to and from the user terminal 110, the merchant terminal 120 and the payer terminal 130 and operates in cooperation with financial companies such as card companies and banks can do.

In one embodiment, the management server 200 can perform on-site payment in conjunction with the user terminal 110 and the payer terminal 130. The management server 200 can issue a payment card in response to a request from the merchant terminal 120 or the payer terminal 130. [ When the user terminal 110 performs on-site payment for the payment card, the management server 200 can receive and analyze the payment request information and process payment approval. Thereafter, the management server 200 can notify the merchant terminal 120 and / or the payer terminal 130 of the payment approval result, and the merchant terminal 120 or the payer terminal 130 confirms the payment Can be performed.

In one embodiment, the management server 200 may be a HCE (Host Card Emulation) based service server. The management server 200 does not store personal information such as card information in a hardware SE such as a UICC (Universal Integrated Circuit Card) and an embedded SE (Secure Element), but instead stores it in a business server that performs a cloud SE (or a cloud platform) Stored, and managed. In order to solve the security problem in implementing the HCE technology, a tokenization technique is employed to issue a token corresponding to card information (for example, PAN), and card information or personal information is exposed .

In addition, when the management server 200 is an HCE-based server, it can be implemented to operate in conjunction with a TSP (Token service provider) server. The TSP server issues a token value corresponding to the primary account number (PAN) information of the card to the card issuance request requested from the user terminal 110. [ The token value is the virtual payment information and plays the same role as the PAN at the payment, but unlike the PAN, it can be changed to a new token value at the time of leak. The TSP server can map the issued token value and the PAN information and store it in the form of a table. In another embodiment, the TSP server may be configured to use a predetermined algorithm that can infer a value between the token value and the PAN information, or to store only the path to the token value and PAN value mapping table.

The billing system 100 according to an embodiment of the present invention can issue a payment card containing merchant information and the payment card can be issued in the form of an HCE card containing a token value instead of the card information. The user terminal 110 can purchase a payment card to perform non-face-to-face transactions, and can generate payment request information for non-face-to-face transactions and request payment. The management server 200 performs payment approval processing through the information extracted from the received payment request information. The merchant terminal 120 or the payer terminal 130 may transmit the settlement notice and the details to the merchant terminal 120 and perform settlement upon request from the merchant terminal 120. [

In addition, the management server 200 may apply a security function to a service application and a communication section. The management server 200 can safely protect the service application itself from hacking or rooting by applying a vaccine, an app forgery prevention function, and a security keypad to detect forgery and falsification of the application itself. The management server 200 can encrypt and manage the card information and the key value used for settlement for data security. For example, the card information and the key value used for settlement may be encrypted with a storage key and stored in a database in the user terminal 110. [ In addition, a key can be embedded in the encryption algorithm itself to prevent leakage of the storage key.

The management server 200 can perform a dual encryption process when communicating between the service application and the management server 200. [ The management server 200 newly generates an encryption key for each communication, first encrypts all data to be transmitted with a one-time mobile session key, performs secondary encryption using a secure communication protocol during communication, The confidentiality and integrity of the data can be ensured.

In the transaction system using the mobile card of the present invention, it is possible to perform settlement using the token value which is the virtual settlement information, and it is possible to perform non-face settlement for the offline merchant without using a separate terminal.

Also, in the prepaid card payment system, by using the non-face settlement, it is possible to implement non-face settlement such as online settlement by utilizing the information stored in the prepaid card at the time of issuance, thereby maximizing the convenience and practicality of the user.

As another embodiment, the payment system of the present invention can be applied to various payment means such as a credit card and a check card in addition to the prepaid card. For example, a user can perform settlement using a credit card stored in a mobile terminal, but can implement transactions using a settlement code proposed in the present invention.

2 is a block diagram illustrating a management server 200 of a payment system according to an embodiment of the present invention. In this specification, a method of making a payment using a prepaid electronic card at the time of transaction is mainly described. 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, a merchant DB 250 and a settlement history DB 260 . In this specification, the case where the management server 200 performs non-face-to-face transaction and settlement has been mainly described, but the present invention is not limited thereto. The management server 200 can perform transaction and settlement in cooperation with a settlement server or another financial company server have. The management server 200 may be implemented as a platform server that implements a payment service, and each of the components 210 to 260 that constitute the platform 200 may be implemented as a server.

The payment card issuing unit 210 is a component for issuing a card at the request of the merchant, and may be implemented as a processor or a server. In one embodiment, the payment card issuing unit 210 includes an operation desk server for performing stakeholder management and card service management, a management server for managing lifecycles of users and services, A MAP (Mobile Application Platform) server, a server for managing prepaid card issuance requests and other service menus, a server for processing card issuance requests, a server for managing PAN information and key values, and a HCE digital card, And a Digital Card Platform (DCP) server for generating a digital key.

In one embodiment, the payment card can be issued in a fixed form and / or in a rechargeable form in consultation with the merchant. In the case of a flat-rate payment card, a user or a payer can select a fixed-price card when making a payment, and if the balance occurs, the user or the payer can accumulate or redeem the fixed-rate card. In the case of a rechargeable card for payment, the customer or the payer can freely input the amount of payment and can freely charge the card within a predetermined limit. As another example, the payment card may be set to be associated with a predetermined account or card, and may be configured to be automatically charged if the balance remains on a regular basis or below a predetermined amount.

The payment card issuing unit 210 can generate and store the token value, the card ID, and the PAN information of the new card when issuing a new card. 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 can use the card for settlement after purchasing the card to be paid.

In one embodiment, the payment card may be a one-time card for on-site payment. That is, after the user terminal 110 selects the corresponding card and makes a payment, the user terminal 110 can be deleted from the held card list of the user. As another example, the non-face-to-face payment card may be managed as a separate list.

As another embodiment, the payer terminal 130 may issue a payment card according to the order details and transmit it to the user terminal 110. [ For example, when the payer terminal 130 receives an order of 10,000 yuan and wants to make a payment, the billing terminal generates a payment card according to the details and transmits (issues) the payment card to the user terminal 110 through wire / wireless communication . At this time, the payer terminal 130 can transmit the payment card to the user through the function in the service application, such as issuing a card to the user terminal 110 through the NFC, or issuing a card for gift or on-site payment have. As another embodiment, the merchant terminal 120 may transmit a payment card to the user terminal 110 in the form of a post-order service application or a push message, and the user terminal 110 may use the received payment card To perform settlement.

The payment card issuing unit 210 can issue a card in cooperation with the user DB 240 and the merchant DB 250. [ Also, the TSP server can interwork with the TSP server to generate and store a token value when issuing a payment card, and the TSP server can map and store the token value with the card information.

The payment processing unit 220 is a processor (or server) that processes the payment request information received from the user terminal 110 or the payer terminal 130. The payment processing unit 220 may be implemented as one or more servers for payment processing. For example, upon receipt of the payment request information, it may include a payment processor (PP) server for processing payment specialties and an issuer token adapter (ITA) server for processing the cryptogram verification and PAN token conversion requests. In one embodiment, the ITA server may interoperate with a TSP (Token Service Provider) server that stores the PAN value and the token value to convert and verify the token value. The settlement processing unit 220 may include a server for performing final approval processing, refund processing, and balance management. In addition, it may include a server for relaying transaction authentication and information, and a virtual VAN server for providing a virtual VAN when there is no VAN and providing a transaction interface.

Upon receiving the payment request information from the payer terminal 130, the payment processing unit 220 extracts the merchant information, purchase information, and input information of the user included in the payment request information. The merchant information may be the merchant number or the merchant ID. The input information of the user includes information (for example, money or coupon) that the user selects or directly describes through the service application for the predetermined item. The user input information can be directly written or the output contents can be confirmed, and the necessary items can be set variously according to the payment card according to the request of the merchant or the setting of the manager.

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 input information of the user. The PAN value is a fixed value for the card, while the token value is a changeable value and has the advantage of issuing a new one if it is leaked. Since the payment card according to the embodiment of the present invention is a prepaid card and the issuer or merchant is specified in the card itself, the card itself includes merchant information (e.g., Merchant ID), merchandise information do. Therefore, it is possible to pay using a prepaid card without a separate approval process. In other words, payment and approval are made through a financial institution in the charging and purchasing procedure of the payment card, so payment through the management server 200 is possible without involvement of the VAN company or the PG company in the field settlement process according to the present invention.

In one embodiment, the payment request information may include security information. In order to prevent the forgery and falsification of the payment data, the payment request information may include security information (e.g., a cryptogram) for the payment data with the payment key at the time of payment and may include the payment information in the payment request information. At this time, the payment key may be stored in the secure area, and the payment information may be encrypted by the payment key at the time of each payment. Also, the payment key can be rounded down automatically after a certain number of uses.

The settlement processing unit 230 can process the settlement of accounts performed on the merchant 120. The settlement processing unit 230 manages reports for each transaction, and can manage details of the interested parties (for example, transaction records for each merchant), settlement details (payment of merchant payment, refund payment, etc.). In one embodiment, the settlement processing unit 230 may arrange the non-face-to-face settlement details performed through the user terminal 110 according to a daily, monthly, or predetermined method so that the settlement can be viewed at the merchant terminal 120. Also, the merchant terminal 120 can be implemented to automatically receive the details of settlement made at the payer terminal 130 from the management server 200, so that even if payment is made by various settlement terminals, the entire merchant can be collected . Also, the merchant terminal 120 or the payer terminal 130 may be implemented so that the merchant terminal 120 confirms (or approves) or cancels the received payment details.

In one embodiment, the settlement processing unit 230 of the management server 200 may transmit the payment details to the payment terminal of the merchant (for example, a separate POS terminal or merchant PC other than the merchant paying attention terminal 120) . The non-face-to-face settlement details, the settlement details, and the settlement processing result provided by the management server 200 can be confirmed through the merchant terminal 120 as well as other terminals installed at the merchant's terminal.

As described above, the payment system according to the present invention includes a settlement card issuing unit 210, a settlement processing unit 220, and a settlement processing unit 230, which constitute a management server, 240, a merchant DB 250 storing merchant information, and a settlement history DB 260 for managing and storing settlement details.

According to the present invention, settlement can be realized using a prepaid electronic card, unlike existing online settlement, so that a payment service can be implemented without involvement of a payment gateway (PG) or a value added network (VAN) company. In addition, even in the case of an off-line store, there is no need to install a payment terminal at an affiliate shop, and there is no need to provide a separate payment module at the time of visit payment. In this way, the settlement commission can be reduced when there is no intermediary between PG and VAN, and since there is no installation and operation cost of the payment terminal, the economic benefit of the merchant can be maximized.

In addition, since the user can use the purchased prepaid electronic card to settle the payment without using the dedicated terminal, there is no need to receive the physical card payment and the paper receipt, and the convenience of the user is improved through the electronic payment means. Further, according to the embodiment, it is possible to make settlement without complicated approval procedure or authentication procedure at the time of settlement, and quick and convenient settlement can be realized.

3 is a flowchart illustrating a settlement procedure of the settlement system according to an embodiment of the present invention. The management server 200 can issue a payment card in accordance with a contract or a request with an affiliate shop. As described above, the payment card can be issued in the form of a flat-type prepaid card or a rechargeable prepaid card. In addition, the payment card may contain information about the expiration date (the due date) and may specify a time period, such as one-time or one-month (for example, for payment in January 2017) have.

In one embodiment, the payment card includes card information for payment. If the payment card is a fixed amount, it includes the fixed amount. Further, the payment card 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, ID or name may also be included, depending on whether it is an original name or a bearer name. In addition, the management server 200 of the present invention can issue card information of a payment card in the form of a token value by implementing HCE-based mobile settlement. That is, the payment card can be issued including card information (token value), merchant information, amount information, and the like.

In another embodiment, when the payment card is a card issued by a financial institution such as a credit card or a check card, after the card is selected, the merchant information and the merchandise information are specified, and payment is requested. Also, in this embodiment, the management server 200 can process settlement and settlement in cooperation with a financial company server as a card issuer.

As a payment card used by a plurality of merchants is issued, the management server 200 can transmit the payment card in the form of a list. For example, the management server 200 can output a list of payment cards that can be purchased through a service application driven by the user terminal 110. [ In another embodiment, the management server 200 may provide a customized list by analyzing the purchasing propensity or position of the user. As another embodiment, when requesting to issue a specific payment card from the merchant terminal 120, a payment card of a merchant requesting the user terminal 110 in the form of a push notification or SMS is popped up or linked to the user terminal 110, As shown in FIG. In this case, the merchant terminal 120 or the payer terminal 130 requests the management server 200 to issue a payment card in response to an order request, and the management server 200 issues a payment card to the user terminal 110 (A message or a notification).

The user terminal 110 may select a payment card to be purchased and purchase a payment card within the charged amount (step 330). The service application may be provided with a basic card issued at the time of user subscription, and may be implemented by charging another payment card within the charged amount of the basic card. In one embodiment, if the charged amount is less than the payment card amount, the charging application can guide the charging application to perform the charging process. After purchasing the payment card using the charge amount, the payment card may be displayed on the user's card list. The user confirms that the purchased card is stored in the list, and performs on-site payment using the card (step 340). As an embodiment, when the card is a field-only payment card, other menus (e.g., off-line payment, gift, etc.) other than the field payment may be displayed in a deactivated state.

The biller terminal 130 is a terminal for recognizing the settlement code presented by the user and performing settlement, and includes various types of pagers of a payer operating a service application. For example, when the payer is a visiting salesman, a delivery agent, or a salesperson, the payer terminal 130 may be used to perform settlement at a place other than the merchant. The biller terminal 130 executes the service application (mobile payment application) and selects the on-site settlement menu (step 310, step 320) when the payment terminal 130 faces the user.

The biller terminal 130 can input necessary payment information according to the guidance of the service application (step 350; see FIG. 4 (a)). For example, as shown in FIG. 4A, when an amount to be paid is directly input, a necessary item can be inputted or selected in the input menu 430, and the inputted information can be confirmed in the following process . The information to be input by the payer can be specified at the request of the merchant, or the management server 200 can designate the information according to the type of the payment card. As another example, in the case of a card for a specific merchandise or a coupon, it is possible to omit the input step and perform payment immediately. As another example, the payment information including the amount may be implemented such that the user terminal 110 inputs the payment information.

When the user completes the input of the authentication information, the payer terminal 130 generates a payment code (step 360). The billing code includes a two-dimensional code such as a bar code or a QR code. The payment code may include payment request information to be transmitted to the user terminal 110. [ The payment request information includes at least one of a token value of the payment card included in the payment card issuance, a token validity period, a token ID generated at each transaction of the token, money information, and merchant information (e.g., Merchant ID or merchant number) One can be included. Also, if the payment request information has a field for recording a terminal ID value, the corresponding field may be replaced with a number assigned by the management server or merchant information.

The payment request information may also include a token value and a cryptogram. A Cryptogram is a value generated by using a payment key for settlement data used at the time of payment, and the management server 200 performs verification of the cryptogram. At this time, the settlement key is stored in a security area where hacking is not possible, thereby preventing misuse by hacking or copying. In an embodiment, the payment key may be automatically discarded after a certain number of uses. In addition, the payment request information may include user input information. The user input information may be included in the payment request specialist or may be transmitted together with additional information.

In one embodiment, the payment request information may be configured according to the ISO 8583 message specification of the payment message, and 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 pre-stored encryption key or an encryption key issued in real time from the management server, and may transmit the encrypted payment request information to the management server 200. [

The biller terminal 130 can display the settlement code on the display unit after generating the settlement code (step 360, see Fig. 4 (b)). The biller terminal 130 may display a payment code so that the user terminal 110 can recognize it, and may display the additional information (valid time, coupon use, etc.) together.

When the user terminal 110 selects the on-site settlement menu, the camera module of the user terminal 110 may be driven (step 370). The user terminal 110 recognizes the payment code output to the payer terminal 130 as a camera and receives the payment request information (steps 370 to 380). In one embodiment, the user terminal 110 recognizes the settlement code and can transmit the settlement request information included in the settlement code to the management server 200 as it is. In another embodiment, the payer terminal 130 extracts the first payment request information recognized by the user terminal 110 and then adds or encrypts the payer information (e.g., user authentication, payment date and time) to the payment request information And may generate and transmit second payment request information to the management server 200. [ The payer terminal 130 transmits the payment request information to the management server 200 and transmits a payment approval request (step 390).

In one embodiment, the user terminal 110 may further input authentication information (e.g., a PIN) before or after the billing code recognition step. For example, when the authentication information is a PIN, the user can implement the PIN for settlement set through the service application as a PIN or the PIN set for on-site settlement only. In another embodiment, the authentication information may include biometric authentication information, fingerprint information, facial recognition information, or iris recognition information. The authentication information may be implemented to perform one authentication using PIN or biometric information, or to perform additional authentication by combining PIN and biometric authentication.

Next, the management server 200 receives the settlement request information and can process whether or not to approve the payment (step 392). The management server 200 may decrypt the settlement request information when encrypted. The management server 200 can extract the merchant information and user input information included in the payment request information. Since the management server 200 is an approval for a card that has already been purchased, it can process the approval of the payment request without approval or purchase of another financial institution. Further, in order to confirm whether or not the payment is truly made by the user, the authentication information stored in the management server 200 may be matched with the authentication information input at the time of transaction.

When the authentication information is confirmed, the management server 200 transmits the payment approval information to the user terminal 110 or the payer terminal 130, and the user terminal 110 or the payer terminal 130 receives the payment approval information (Steps 394 and 396).

On the other hand, the management server 200 may transmit a notification message to the merchant terminal 120 to notify the occurrence of the field transaction at the time of payment approval, or may additionally store the notification message in the transaction history. In one embodiment, the notification message may be transmitted in the form of SMS or in the form of a pop-up message upon execution of a service application. According to another embodiment, the franchisee terminal 120 may be configured to receive notifications and confirm details on a regular basis, such as daily, monthly, etc., without receiving a separate notification message.

The merchant terminal 120 can confirm the payment approval information and browse the payment approval details. As described above, the management server 200 can be configured to transmit the collected payment details to the merchant terminal 120 or to transfer the collected payment details to another payment terminal (for example, the POS terminal of the merchant or the merchant PC).

In one embodiment, the merchant can confirm transaction details through the payer terminal 130 or the merchant terminal 120 and determine whether to accept the transaction. The merchant terminal 120 can confirm the settlement approval details and select the acceptance or rejection. For example, if the amount or user information is erroneously settled or duplicated, the transaction can be canceled by refusing the purchase of the franchisee's stock price. As another example, the payer terminal 130 may determine the first-order acquisition in real time, and the merchant terminal 120 may view, correct, or cancel the transaction confirmation.

As another embodiment, the merchant terminal 120 or the payer terminal 130 may be configured to perform the additional authentication procedure when a transaction is confirmed (acquired). For example, when the payment approval information is notified, the management server 200 may transmit an approval message to the terminal of the merchant, and the approval message may include a one-time number or an authentication number. The merchant can implement the authentication number included in the approval message to process the argument for the payment. When the additional authentication is performed, the merchant's stock is subjected to the authentication process for the specific payment, so that the risk of the acquisition by the other person can be reduced.

After completing the transaction approval, the payer terminal 130 or the merchant terminal 120 may request the user terminal 110 to issue an electronic receipt to the acquired transaction details. The management server 200 may receive the 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 the form of an SMS.

According to the payment system of the present invention, payment can be made using a plurality of payer terminals without a separate merchant payment terminal. Particularly, when a street vendor and a plurality of delivery agents, which are difficult to use a payment terminal, are required to make on-site payment, payment can be made through a mobile phone possessed by each payer, thereby contributing to promoting the spread of electronic transaction services.

4 is a screen shot on the payer terminal 130 for explaining the settlement process of the settlement system according to the embodiment of the present invention. 4 (a) shows a screen for outputting a payment card purchased through a service application.

When the payer selects the on-site settlement menu 420, the on-site settlement procedure is started through data transmission / reception with the management server 200 (Fig. 4 (a)). The management server 200 may output the payment information input field on the guidance page 410 when the payment information is required according to the on-site payment request. The payer can confirm the payment information including the amount information displayed on the terminal 130 and input the information. The settlement person input information 430 may be directly written or may be implemented by selecting the item. As another example, when the user does not need to input information (for example, in the case of a flat-type card, when a money is set as a card for a specific commodity, etc.), the payment information input step is omitted and the billing code is immediately generated .

In one embodiment, the billing code may include merchant information (e.g., Merchant ID), payee input information (e.g., merchandise or amount information), and may be generated to include encryption information via an encryption process.

The management server 200 switches to the payment code output page 440 (FIG. 4B) when the user presses the OK button after completing the input. Screen 440 may include a prompt to present the billing code to the user and a validity time. As an embodiment, the biller authentication information (PIN) may be further input before the billing code is output.

5 is a screen shot on the user terminal 110 for explaining the settlement process of the settlement system according to the embodiment of the present invention. 4 (b)), the user can recognize the settlement code through the user terminal 110. In this case, As described with reference to FIG. 3, the user terminal 110 may drive the service application to select the on-site settlement menu and operate the camera. The service application may have a separate menu or account for the user, or may be provided as a separate application.

In one embodiment, a payment approval notification message may be received on the user terminal 110 or the payer terminal 130 when the on-site payment is completed. However, the present invention is not limited to this, and it is possible to notify a transaction approval in various forms such as a push message or an application icon notification.

The payer can confirm the approval details of the field settlement transaction through the payer terminal (130). In addition, the user can confirm transaction details approved on the user terminal 110 ((b) of FIG. 5). As an embodiment, the non-face-to-face transaction history can be viewed only through a terminal owned by a member having a merchant account or a payer account, and the transaction history can be read through a separate authentication procedure (PIN or biometric authentication) .

In one embodiment, the payer can confirm the transaction approval list via the payer terminal 130, and the transaction approval list includes the details of the settlement (acquisition), the details of the pending settlement, the details of the cancellation can do. The payer can check the details of the on-the-spot transaction and select whether to accept the transaction for the subject of the transaction. In one embodiment, when the transaction is taken, it can be indicated that the settlement has been completed and an electronic receipt is sent. For example, the electronic receipt can be automatically transmitted to the user terminal 110 via the management server 200 upon confirmation of the acceptance.

As described above, since the payer and the user's mobile terminal replace the dedicated payment terminal and function as a mobile payment terminal, it is possible to lower the troubles in the existing offline transaction and provide convenience to the merchant business operator and the user . In particular, since the merchant does not need to install or purchase a payment terminal and does not need a purchase transaction procedure, it does not need to go through a VAN company or a PG company, thereby significantly reducing the transaction fee.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

100: Payment system 110: User terminal
120: Merchant terminal 130: Payer terminal (payer's mobile terminal)
200: management server 210: payment card issuing unit
220: payment processor 230: settlement processor
240: User DB 250: Merchant DB
260: Settlement record DB

Claims (12)

A payment method using a first mobile terminal held by a customer and a second mobile terminal held by a payer via a service application provided by a management server,
The first mobile terminal selecting a payment card through the service application;
Receiving the payment information from the second mobile terminal and generating a payment code using the payment information;
The second mobile terminal outputting the payment code for a predefined valid time;
Recognizing the billing code output to the second mobile terminal using the first mobile terminal; And
And transmitting, at the first mobile terminal, the payment request information included in the payment code to the management server to request payment approval. The method according to claim 1,
Wherein the payment card is issued from the management server to store information including at least one of a token value, merchant information, a card amount, and an expiration date at the time of issuance of the payment card,
Wherein the token value is virtual payment information corresponding to a PAN (Primary Account Number) value of each of the payment cards. The method according to claim 1,
And the second mobile terminal generates the payment code including at least one of the payment information and the merchant information. The method according to claim 1,
Wherein the first mobile terminal further comprises an authentication step of inputting user authentication information according to a guidance of the service application upon on-site payment. The method according to claim 1,
The payment request information includes at least one of payment card information, user input information, authentication information, and information received from the payment code. The payment request information includes a cryptogram value And generating the payment information. The method according to claim 1,
Transmitting settlement approval details to the second mobile terminal or the first terminal after the settlement approval processing through the management server; And
Further comprising the step of the management server receiving, from the second mobile terminal, whether to accept or reject the payment approval history. The method according to claim 6,
Outputting an electronic receipt issuing menu for the received payment approval details; And
Wherein the second mobile terminal requests the issuance of an electronic receipt to the management server by selecting the menu for issuing the electronic receipt, and the management server issues an electronic receipt to the first mobile terminal. The method according to claim 1,
Transmitting the settlement approval details to the merchant terminal installed in the merchant; And
Further comprising the step of the management server receiving from the merchant terminal an acceptance or rejection of the payment approval history. 9. The method of claim 8,
Wherein the merchant terminal comprises a merchant PC, a POS (Point of Sale) terminal or a CAT (Credit Authorization Terminal) terminal. A billing system using a mobile terminal,
A payment card issuing unit for issuing a payment card for on-site payment in response to a request from an affiliate store and for publishing the payment card through a service application driven by a first mobile terminal carried by the user, And a settlement processor for receiving the settlement request information generated for the settlement card when the terminal performs on-site settlement using the settlement card and processing the settlement approval using the information included in the settlement request information server;
A second mobile terminal for inputting payment information through a service application provided by the management server and generating and outputting a payment code using the payment information; And
The first mobile terminal selecting the payment card through the service application, recognizing the payment code output to the second mobile terminal, and transmitting the payment request information to the management server. 11. The method of claim 10,
Wherein the payment card is issued from the management server to include at least one of a token value, merchant information, a card amount, and an expiration date at the time of issuance of the payment card,
Wherein the token value is virtual payment information corresponding to a PAN (Primary Account Number) value of each of the payment cards. 11. The method of claim 10,
The payment request information includes at least one of payment card information, user input information, authentication information, and information received from the payment code. The payment request information includes a cryptogram value To generate a payment transaction.

Images