WO2020130486A1

WO2020130486A1 - Server and client using main transaction card information to settle payments

Info

Publication number: WO2020130486A1
Application number: PCT/KR2019/017589
Authority: WO
Inventors: 조광현; 최윤정; 유주상
Original assignee: 주식회사 지에스리테일
Priority date: 2018-12-19
Filing date: 2019-12-12
Publication date: 2020-06-25
Also published as: KR102074443B1

Abstract

The present invention relates to a server and a client using main transaction card information to settle payments, and a customer management server according to one embodiment of the present invention comprises: a database unit comprising a user identification table comprising user identification information, a benefits information table including user identification information, and a main transaction card information table comprising user identification numbers and card information; a communication unit for communicating with a payment client and portable terminal; and a centralized control unit which controls the database unit and communication unit, encrypts, by means of a one-way hash function, and stores a portion of a card number, which is among the card information stored in the main transaction card information table, and, when the communication unit receives a card number from the payment client or portable terminal, searches the main transaction card information table, using the portion of the card number that has been encrypted using a one-way hash function, to extract user identification information.

Description

Server and client for payment using main transaction card information

The present invention relates to a server and a client for payment using main transaction card information.

Along with the increase of single-person households, a number of retailers offering various products and services are increasing. In addition, due to the increase in the number of dealerships, competition among dealerships increases, and influx of buyers into the dealership has been attempted in various ways to provide various economic benefits to the buyer.

In addition, with the rapid development of mobile communication technology, popular dissemination of portable terminals such as smart phones has been achieved, and many people have portable terminals. Previous portable terminals were able to simply send voice calls and send text messages, but now they are expanding their functions, such as taking photos and videos, playing music files, and accessing wireless Internet.

Recently, applications that can be installed on smartphones to provide various benefits are being developed, but most of these applications are a method of providing a coupon by accumulating and storing the user's payment characteristics or usage counts numerically. There is a lack of incentives.

Accordingly, it is necessary to provide various payment methods in order to provide buyers with various purchase needs and economic benefits. And, it is necessary for the buyer to have technology to check the purchase result and benefits in real time.

The present invention makes it possible to receive benefit information on payment in the payment process based on the main transaction card.

The present invention is intended to provide stability of payment by sending a notification message when payment store information is sent to the app through a server when payment is made with the registered main transaction card, or when the app is not in the same store.

The present invention seeks to increase the security of personal information by preventing the entire number of main transaction card numbers from being stored when identifying a user using the registered main transaction card.

The problems to be solved by the present invention are not limited to the problems mentioned above, and other problems not mentioned herein will be clearly understood by those skilled in the art from the following description.

The payment client using the main transaction card information according to an embodiment of the present invention is a communication unit communicating with a customer management server and a card company server, an interface unit that outputs information received by the communication unit and receives selection of output information, and card information. After receiving the card reader, the communication unit and the interface unit and the card reader, and after the card reader receives the card information of the first card, the card card information of the first card is transmitted to the customer management server, and the communication unit receives The benefit information and user identification information are output to the interface unit, and the communication unit displays the final payment amount to which the benefit information is applied and the card information of the first card or the card information of the second card received by the card reader according to the selection entered in the interface unit. It includes a payment control unit to control the transmission to the server.

The customer management server using the main transaction card information according to an embodiment of the present invention includes a user information table including user identification information, a benefit information table including user identification information, and a main transaction card information table including user identification number and card information. It controls the database unit, the payment client, the communication unit that communicates with the mobile terminal, and the database unit and the communication unit, and encrypts a part of the card number among the card information stored in the main transaction card information table with a one-way hash function. And a central control unit that retrieves user identification information by searching the main transaction card information table using the result of encrypting a part of the card number with a one-way hash function when the communication unit receives the card number from the payment client or mobile terminal. .

When the embodiment of the present invention is implemented, the payment benefit information may be applied in the payment process based on the main transaction card.

When implementing the embodiment of the present invention, when payment is made with the registered main transaction card, payment store information may be transmitted to a server communicating with the app, or when an app is not in the same store, a notification message may be sent to provide stability of payment.

When implementing the embodiment of the present invention, in identifying a user using the registered main transaction card, it is possible to increase the security of personal information by preventing the entire main transaction card number from being stored.

The effects provided by the present invention are not limited to the above-mentioned effects, and other effects not mentioned herein will be clearly understood by those skilled in the art from the following description.

1 is a view showing a process of storing the main transaction card information in the CRM server using the app according to an embodiment of the present invention.

FIG. 2 is a view showing a process of storing main transaction card information in a server using a client device that performs payment of an offline store according to an embodiment of the present invention.

3 is a diagram showing a database structure of a server according to an embodiment of the present invention.

4 is a view showing a process of payment using a main transaction card according to an embodiment of the present invention.

5 is a diagram showing a processing process when a user registers a plurality of main transaction cards according to an embodiment of the present invention.

6 is a view showing a process of payment using an application according to an embodiment of the present invention.

7 is a diagram showing the configuration of a database in which user benefit information is stored according to an embodiment of the present invention.

8 is a view showing the configuration of a payment client according to an embodiment of the present invention.

9 is a view showing the configuration of the customer management server 300 according to an embodiment of the present invention.

Advantages and features of the present invention, and methods for achieving them will be clarified with reference to embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in various different forms, and only the present embodiments allow the disclosure of the present invention to be complete, and common knowledge in the art to which the present invention pertains. It is provided to completely inform the person having the scope of the invention, and the present invention is only defined by the scope of the claims. The same reference numerals refer to the same components throughout the specification.

In order to clearly describe the present invention, parts irrelevant to the description are omitted, and the same reference numerals are assigned to the same or similar elements throughout the specification. In addition, some embodiments of the present invention will be described in detail with reference to exemplary drawings. In adding reference numerals to the components of each drawing, the same components may have the same reference numerals as possible even though they are displayed on different drawings. In addition, in describing the present invention, when it is determined that detailed descriptions of related well-known structures or functions may obscure the subject matter of the present invention, detailed descriptions thereof may be omitted.

In addition, in describing the components of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are only for distinguishing the component from other components, and the nature, order, order, or number of the component is not limited by the term. When a component is described as being "connected", "coupled" or "connected" to another component, the component may be directly connected to or connected to the other component, but different components between each component It should be understood that the "intervenes" may be, or each component may be "connected", "coupled" or "connected" through other components.

Hereinafter, during the payment process based on the main transaction card, the benefit information in the payment can be applied, and when payment is made with the registered main transaction card, payment store information is sent to the app, or when the app is not in the same store, a notification message is sent to send the payment. Let's take a look at the configuration and operation process of server and payment client that provide stability. In addition, in this specification, in identifying a user by using the registered main transaction card, the entire number of the main transaction card number is not stored, thereby enhancing the security of personal information.

The mobile terminal 100 is capable of communication such as a smart phone and a tablet computer, and includes an interface unit for outputting information, and includes various types of devices that a user can carry.

The mobile terminal 100 may store and execute an application having a function of registering or using the user's main transaction card information or storing and providing user identification information. By executing the application, the mobile terminal 100 receives identification information from the user (S1). Prior to input of the identification information, the mobile terminal 100 may selectively perform the subscription process.

During the sign-up process, the user can enter information such as name and gender, date of birth, mobile phone number, email, address, etc., and the mobile terminal 100 or computer transmits it to the CRM server 300, and as a result of membership registration CRM server 300 transmits that the completion is complete.

The CRM server 300 is a server that stores and manages information about users, and is an acronym for Customer Relationship Management Server or Customer Management Server. Hereinafter, the CRM server is referred to as a customer management server.

In addition, the user can log in to the application using the user identification information set during the sign-up process.

User identification information may include an ID, a user customer number, and the like. Alternatively, the password information input in addition to the user's identification information and the identification information (phone number, etc.) of the mobile terminal may be transmitted together in step S2.

The identification information of the input user is transmitted to the CRM server 300 by the mobile terminal (S2). As a result of the transmission, the CRM server 300 verifies the identification information of the received user, and as a result of verification, if it is a normal user, the CRM server 300 records the registration status information of the registered main transaction card based on the user identification information in the database. Extract (S3).

Then, the CRM server 300 transmits the registration status information of the extracted main transaction card (S4). At this time, the registration status information may include unencrypted card information among card information stored in the database unit.

The application of the mobile terminal 100 outputs the information received in S4 and additionally outputs information for registering the main transaction card (S5). A screen for inputting a card number may be output from the mobile terminal 100. Here, the user inputs the card information and the mobile terminal 100 acquires the card information (S5).

At this time, the input of the card information may be applied to various input methods such as a method in which the user directly enters the serial number of the card on the screen, and a method in which the card's serial number is automatically input into the application by photographing the card with the camera.

The method of photographing the card with the camera is an embodiment in which a serial number of the card is input into the application by recognizing the number written on the card using a technology such as OCR (Optical Character Recognition).

Alternatively, the mobile terminal 100 may automatically receive information of a payment card based on a near field communication or wireless communication method provided by the mobile terminal 100.

The mobile terminal 100 acquires card information in various ways and transmits the acquired card information and user identification information to the CRM server 300 (S6).

The CRM server 300 encrypts the received card information and stores it in a database (S7). At this time, some of the card information may be encrypted and the other may not be encrypted. In one embodiment, configuring card information may be a card number, a card expiration date, etc., among which some of the card numbers may not be encrypted.

The first six of the card numbers are low-priority information to identify an individual, such as information about the country that issued the card, information about the card issuer, or card type. Therefore, the CRM server 300 may store some of the leading digits of the card number in the database.

And the remaining card numbers (for example, 7th to 16th numbers) are encrypted and stored using a one-way encryption algorithm. For example, the CRM server 300 encrypts a part of the card number through a hash function and stores it in a database.

The hash function is one embodiment, and the CRM server 300 may generate one-way data for checking the card number and store it in a database. By using the one-way data generated using a one-way hash function or a one-way encryption function, a card number or a part of the card number is not reversely calculated. Therefore, since the original card number or a part of the card number cannot be restored using the one-way data stored in the main transaction card information table, security of personal information can be enhanced.

Thereafter, the CRM server 300 extracts the registration status information of the main transaction card including the added main transaction card from the database (S8) and transmits it to the mobile terminal 100 (S9). As a result of the transmission, the mobile terminal 100 displays the registered main transaction card on the screen (S10).

The main transaction card can be registered through the process shown in FIG. 1. In addition, the user can check the registered main transaction card information based on the process of S1, S2, S8, S9, S10 through the mobile terminal 100.

Alternatively, once the main transaction card is registered, the mobile terminal 100 stores information about the main transaction card in the application of the portable terminal 100 so that the user can check the main transaction card without accessing the CRM server 300. That is, when the information on the main transaction card is registered in the storage space in the mobile terminal 100, the application of the mobile terminal 100 checks the information stored in the mobile terminal 100 without accessing the CRM server 300, and performs the main transaction. You can check the information on the card.

In addition, the user can set a name for the main transaction card in the process of storing the main transaction card. This makes it easier to check the card if the user has registered a number of main transaction cards. The set name may be stored in the database of the server 100.

FIG. 2 is a view showing a process of storing main transaction card information in a server using a client device that performs payment of an offline store according to an embodiment of the present invention. This shows the process of the user visiting the offline store and registering the main transaction card to the CRM server 300 using the payment client 200 installed in the store.

The user identification information is input to the payment client 200 disposed in the offline store (S12), and information for registering the main transaction card and card information are input (S13).

When the user has the mobile terminal 100 and the application is installed, S12 may proceed after the process (S11) of providing the user identification information to the payment client 200 through the user's application. When the user identification information is displayed on the mobile terminal 100 using a barcode or a QR code, the barcode reader or QR code reader of the payment client 200 can read the displayed code.

S13 may be performed through a card reader of the payment client 200. In particular, the card reader may be applied in addition to a magnetic card reading method, an IC card reading method, a card reading method through NFC or wireless communication, or a reading method using a cyber card stored in the mobile terminal 100.

The payment client 200 transmits the information input in S12 / S13 to the CRM server 300. The server encrypts and stores the card information using the transmitted information (S15). This process may be performed in the same manner as in the S7 process.

CRM server 300 transmits the processing result to payment client 200 (S16). In addition, the processing result is also transmitted to the user's mobile terminal 100 (S17), so that the user can confirm the final processing result of the main transaction card registration.

The database includes a user information table 301 and a main transaction card information table 302. The database of FIG. 3 may constitute an integrated member information system for users of multiple stores.

The user information table 301 is information generated when a user registers as a member. User identification information (UID), name (NAME), date of birth (BIRTHDAY), phone number (PHONE), gender (GENDER), and email Information such as (EMAIL) is stored for each user.

The main transaction card information table 302 stores one or more main transaction card information for each user.

It consists of unencrypted card number (CARD_NUMBER), encrypted card number (CARD_ENCR_NUMBER), and card name (CARD_NAME) based on user identification information (UID).

The unencrypted card number (CARD_NUMBER) means card information stored without encryption. In an embodiment, a part of the leading digit (for example, 6 digits) of the card number is a number allocated for each card (or for each country or member type) rather than personal information, and thus the number is stored without encryption. Some card numbers that are stored without encryption are called Isiner Identification Number (IIN) or Bank Identification (BIN). When using such an IIN or BIN, the search speed can be increased. In addition, this information does not need to be encrypted because it is a known number. Therefore, the known or publicly used card number is not encrypted, and the security of the card number can be increased while increasing the convenience of user identification.

On the other hand, the encrypted card number (CARD_ENCR_NUMBER) means information encrypted in one direction. You can use a hash function. In one embodiment, a part of the back digit of the card number (for example, numbers after the 7th) is encrypted and stored to protect personal information.

The hash function, which is an embodiment of the one-way encryption algorithm, cannot infer the original information through the encrypted information, but means that when the original information is encrypted, the same encrypted result is obtained. Instead, since the original information cannot be extracted from the encrypted information, the card number itself is not stored.

For example, it is assumed that the "GSR H card" number of the user whose UID is abcd1234 is "0123 2531 1234 1234". The first 6 digits "0123 25" of the card are not encrypted and stored as they are. The information "31 1234 1234" after the seventh of the card stores "fjkfsdjlgsls23sdfs243lfdsal" which is the result of inputting to the hash function. This result is stored separately from the unencrypted card number (CARD_NUMBER).

In addition, the information "31 1234 1234" after the seventh of the cards input to the hash card is not stored in the database.

As a result, if there is a card number transmitted in the payment process, the CRM server 300 searches for the first six digits of the card number as it is, and the last digit is put in a hash function to retrieve the result, so it stores only a part of the card number, but it is the main transaction card You can check That is, it is possible to check whether or not the user's main transaction card is paid while the user's main transaction card information is protected.

In addition, as shown in the main transaction card information table 302, a plurality of main transaction cards may be registered in response to user identification information. The CRM server 300 may limit the number of main transaction cards that can be registered (for example, 3 or 5, etc.). Alternatively, the CRM server 300 may not limit the number of main transaction cards that can be registered.

In this case, when a user has a card with a higher payment benefit through the payment client when the card is paid, the user may select the card and perform payment again.

Various information related to payment may be additionally stored in the main transaction card information table 302. At the time of payment, benefit information, discount information, and the like may be stored for each card, or may be separately stored in the CRM server 300.

In addition, the user information table 301 may store information to be applied at the time of payment, such as discounts, ratings, points, discounts of mobile operators, and mobile discounts, together with user information.

In particular, if a user's payment card is easily registered based on OCR, card information is safely stored in the system. Particularly, since some of the card information is encrypted and the result of the hash function is stored, user information can be identified at the time of payment by the card without storing the entire card number.

In addition, the user information table 301 of FIG. 3 may store some kind of membership account information, especially when a number of stores, such as a franchise, convenience store, or large discount store, provide points to one membership account, or through partnership with a card company The present invention can be applied even when a selection is given for each card.

The payment client 200 receives card information through a card reader (S21). Then, the received card information is transmitted to the CRM server 300 (S22). In S22, not only the card number, but also information about the product to be paid, information such as the amount to be paid, and information about the payment store may be transmitted together with the card information. Of course, the information on the payment store may be transmitted by a payment client 200 in a different process from S22.

The CRM server 300 receiving the card information including the card number generates a hash result by applying a hash function to the encryption portion of the received card information (S23). In addition, the CRM server 300 extracts user identification information from the information on the non-encrypted portion of the card information and the hash result calculated in S23 (S24). For example, the CRM server 300 receiving the card information including the card number "0123 2531 1234 1234" is a hash result calculated by applying a hash function to the information "31 1234 1234" after the 7th of the cards. The "fjkfsdjlgsls23sdfs243lfdsal" and the first six digits "0123 25" of the card are searched in the main transaction card information table 302 of Fig. 3 to confirm that the UID is "abcd1234".

CRM server 300 extracts the UID "abcd1234" as the user identification information and extracts the benefit information corresponding thereto (S25). The benefit information may be variously configured as an example.

First, the benefit information includes information on whether coupons or points allocated to the UID "abcd1234" can be used. Includes exclusive benefit information provided directly to the user. Also, product information already stored by the user (for example, product information previously purchased or stored as exchangeable as a gift) is also included in the benefit information.

In addition, the benefit information includes additional points or cyber money at the corresponding store. In addition, the benefit information includes additional points, cyber money, or a discount amount according to purchase of a specific product.

Next, the benefit information includes information on affiliate discounts. It includes discount information for carrier membership or discount information for card partners.

Next, benefit information specific to the store is also included in the embodiment of the present invention. For example, the benefit information includes information on discounts or extended products that can be used in a store to be paid.

The CRM server 300 extracts the benefit information based on the corresponding user identification information or the identification information of the store to perform payment, and then transmits the user identification information and the benefit information to the payment client 200 (S26).

The payment client 200 outputs the received information on the interface window. For example, sales price, benefit information (amount, coupon, point application, etc.), final payment planned amount, and the like may be output. Here, the user identification information may or may not be partially output for security purposes.

The benefit information outputs information such as discounts and coupons available at the time of payment. Then, the payment client 200 calculates the final payment amount by reflecting the benefit information selected by the user or automatically the benefit information, and transmits the final payment amount and card information to the card company server 500 (S32). The final payment amount may be an amount subtracted from the original payment amount by applying the benefit.

The card company server 500 performs payment based on the received information and transmits payment completion information to the payment client 200 (S33). The payment client 200 confirming that payment is completed transmits payment completion information, applied benefit information, and user identification information to the CRM server 300 (S36).

The CRM server 300 updates the user information table 301 by reflecting the payment result in response to the user identification information (S37). When a coupon is used, the used coupon is deleted in response to user identification information. When an accumulation point occurs, a reserve is added in response to user identification information.

In addition, the CRM server 300 transmits payment completion information, applied benefit information, and updated benefit information to the user's mobile terminal 100 (S38). CRM server 300 may be sent to the mobile terminal 100 by text. Alternatively, the CRM server 300 transmits a push message to an application installed in the mobile terminal 100 to display information received by the application installed in the mobile terminal 100 in a pop-up on a screen.

When the embodiment of FIG. 4 is applied, when the payment client 200 of the store receives the card information of the card owned by the user and transmits it to the CRM server 300, matching is performed through a hash process on some of the transmitted card information To identify individuals. In addition, when the user information of the card to be paid is identified, the CRM server 300 automatically provides benefit information such as coupons, points, and gift products to the payment client 200.

The payment client 200 may output the benefit information through a screen so that the user can check it, and when the user selects specific benefit information or automatically deducts the payment without selecting it, the benefit information can be applied to the payment. The benefit information includes coupons, point application, and the like.

In addition, the CRM server 300 transmits the benefit information applied in the payment process to the user's mobile terminal 100 so that the user can immediately check it. That is, even after paying only with the card, the payment result, benefit information such as points and reward accumulation, etc. are displayed on the app.

5 is a diagram showing a processing process when a user registers a plurality of main transaction cards according to an embodiment of the present invention. In the case of the same indication number as in FIG. 4, it operates in the same manner as in FIG. 4, and is replaced with the description of FIG.

In the flow of Fig. 5, the payment client 200 receives card information (S21), and the payment client 200 transmits information to the CRM server 300 (S22). The CRM server 300 extracts user identification information as card information in step S23/S24. As a result of extracting the user identification information, the CRM server 300 extracts other main transaction card information and benefit information registered in response to the user identification information (S25a).

For example, referring to 302 of FIG. 3, when the “GSR H card” information of the user abcd1234 is transmitted, the CRM server 300 confirms that the “AMEX card” of the same user is also registered as the main transaction card. In addition, the benefit information of the "AMEX card" and the benefit information of the "GSR H card" may be different depending on the promotion of the card affiliate.

The CRM server 300 transmits each extracted main transaction card information, benefit information, and user identification information to the payment client 200 (S26a). At this time, in order to protect the user's personal information, only the part of the name of the card (CARD_NAME) set by the user may be transmitted to the main transaction card information. For example, "AMEX card" can be transferred to "A**** card".

The payment client 200 outputs other main transaction card information and benefit information in the interface window (S31a). The user determines whether to change the payment card by confirming the case where more benefits are provided or other types of benefits are provided (S31b). If the payment card is changed to an "AMEX card", the user can provide the "AMEX card" to the store again. The payment client 200 of the store starts the step of S21 again. However, since the main transaction card has been received and payment has been attempted with the changed card, steps S21 to S38 of FIG. 4 may be performed as it is.

That is, if the information of the main transaction card is input more than once within a certain time in the same payment client 200, the CRM server 300 provides the information of the other main transaction card even if there is another main transaction card of the user identified as the corresponding main transaction card You may not. This is due to the quick payment and the user's willingness to use the card.

Next, if the payment card is not changed in S31b, the payment client 200 calculates the final payment amount by reflecting the benefit information when selecting payment with the main transaction card in S21 (S31c), and the steps of S32 to S38 described in FIG. 4 are performed. To proceed.

When the embodiment of FIG. 5 is applied, the payment client 200 such as POS may provide the user with the information of another main transaction card of the user who is provided with a higher benefit to the user while the card payment is in progress. .

4 and 5, the main transaction card set by the user can be used for online/offline payment, and particularly, offline payment can automatically apply benefit information according to membership.

If there is no matching user identification information in the process of paying the card in FIGS. 4 and 5, the payment client 200 may output a guide message for card registration or user identification information registration as a voice message/video message. . For example, if there is no matched user identification information in the CRM server 300 in S24, the payment client 200 may output a message inducing registration with the main transaction card using the interface unit.

When the above-described embodiment is applied, in order to increase the convenience of payment, a credit card, a check card, a prepaid card, etc. are easily recognized on/offline, encrypted, and stored in the CRM server 300. After that, when you pay with the card, you can automatically provide membership benefits to users.

In particular, by using the main transaction card registered by the user, the user can automatically reflect the benefits (discount/accumulate) in the payment process without having to run the app separately when submitting the payment or submit user identification information to the store, thereby increasing convenience.

In addition, in the embodiment of FIG. 5, when a plurality of main transaction cards are identified through user identification information, the CRM server 300 may selectively provide other main transaction card information. For example, the user (USER1) who has registered the main transaction cards A and B can pay with the "A" card. At this time, the CRM server 300 also confirmed the “B” card as the main transaction card of USER1 through the card “A”. However, if the benefit of the "A" card is higher, the CRM server 300 does not provide the payment client 200 with information that the "B" card is the main transaction card.

Conversely, if the card company of the "B" card has a discount event, or if the benefit of the "B" card is overdue (for example, one week or shorter than the benefit of the "A" card), then "A In order to induce payment of the "B" card instead of the "card, the CRM server 300 provides the payment client 200 with information that the "B" card is the main transaction card.

6 is a view showing a process of payment using an application according to an embodiment of the present invention. In the app of the mobile terminal 100, select a product to be purchased and input card information for payment (S21c). After input, the user identification information and the card information by the application are transmitted from the mobile terminal 100 to the CRM server 300 (S22c). Afterwards, S23, S24, and S25 processes operating in the CRM server 300 are as described in FIG. 4 above. The CRM server 300 extracts the benefit information and transmits user identification information and benefit information to the mobile terminal 100 (S26c).

Here, S23 and S24 may be omitted, because the user identification information is transmitted from the mobile terminal 100. However, in order to confirm whether the user identification information is transmitted and the transmitted card information is the main transaction card of the corresponding user, the CRM server 300 may perform steps S23 and S24.

The benefit information is output on the interface window of the mobile terminal 100, and the final payment amount is calculated by reflecting the benefit information according to the user's selection (S31c). And for payment, the final payment amount and card information are transmitted to the CRM server 300 (S32c), and the CRM server 300 again transmits the final payment amount and card information to the card company server 500 (S32d).

When the card company server 500 transmits the payment completion information (S33c), the CRM server 300 updates the user information table by reflecting the payment result in response to the user identification information (S37). Then, the payment completion information and the applied benefit information are transmitted to the mobile terminal 100 (S38c), and the user can confirm this.

In the embodiment of FIG. 6, when the user registers the main transaction card, the CRM server 300 provides the appropriate benefit information to the user even if the user does not check the benefit information of each main transaction card, so that the use of a specific main transaction card provides benefits You can confirm that you can. And, depending on the user's choice, payment can be made using a main transaction card with high benefits.

As an example, the benefits include membership discounts provided in response to the main transaction card, carrier discounts, sales discounts, and point accumulation.

In addition, after payment of the card company server 500 is completed, the CRM server 300 transmits the applied benefit information to the mobile terminal 100 by reflecting the payment result, so that the user can check the payment benefit in real time.

In addition, when the user's information is confirmed using the main transaction card, the product benefits assigned to the user can also be checked in an offline store or an online channel. For example, as a benefit provided to a user, a voucher for a product received from another user or a voucher for a product previously purchased by the user may be provided as benefit information.

In this case, when the user information is confirmed by the main transaction card, the payment client 200 or the mobile terminal 100 of the offline store may provide a notification message to the user that the user has a voucher that can be received free of charge.

7 is a diagram showing the configuration of a database in which user benefit information is stored according to an embodiment of the present invention. The benefit information table 305 in which the benefit information is stored includes a type of benefits and details provided for each user. The type consists of card benefit information (CARD_ADV), points (POINT), exchange vouchers (EXCHANGE), and carrier discounts (TELECOM), and the types of benefit information can be variously added.

The details may consist of a card name set by the user and a discount rate (%) or points earned. Or, in the case of discounts for mobile carriers, the discount rate (10%) at the mobile carriers is included. In the case of a voucher, it means a product that the user can acquire without payment. For example, the serial "0003" indicates benefit information for a voucher that allows a user with a UID of "abcd1234" to acquire a hamburger without payment. The serial "0004" indicates benefit information for a voucher for a bottled water received by a user with a UID of "abcd1234". The user presented here has a UID of "gsr7890".

Therefore, as shown in Figure 7, the benefit information for each user is stored in the database of the CRM server 300, when the user attempts to pay with the main transaction card, through the application of the payment client 200 or mobile terminal 100 of the offline store Benefit information extracted as user information corresponding to the main transaction card, such as S26 or S26a or S26c, is provided. This allows the user to always check available benefit information when attempting to pay with the main transaction card, without having to remember the benefits available to the user each time.

In addition, when the user makes a payment using the main transaction card, an additional new benefit may be presented to other users. For example, there is a benefit information that is additionally provided to the user due to purchase of the product, and the benefit information may be held by the user at the user's option or presented to other users.

The payment client 200 includes a communication unit 210, an interface unit 220, a card reader 230, and a payment control unit 250.

The communication unit 210 communicates with the customer management server 300 and the card company server 500. Then, the interface unit 220 outputs the information received by the communication unit 210 and receives a selection of the output information. A display screen capable of a touch screen or a display screen combined with keyboard input is an embodiment of the interface unit 220.

The card reader 230 receives card information such as a magnetic card and an IC card. There are various methods for receiving card information, and the present invention is not limited thereto.

The payment control unit 250 controls the communication unit 210, the interface unit 220, and the card reader 230. In addition, the payment control unit 250 controls the card reader 230 to receive the card information of the first card, and then transmit the card information of the first card to the communication unit 210 to the customer management server 300.

In addition, the payment control unit 250 outputs the benefit information and the user identification information received by the communication unit 210 to the interface unit 220.

Also, the payment control unit 250 communicates the final payment amount to which the benefit information is applied according to the selection input to the interface unit 220 and the card information of the first card or the card information of the second card received by the card reader 230 ( 210) is controlled to transmit to the card company server 500.

Here, the first card is the main transaction card presented by the user for the first time, and the second card is a card provided for the user to check the benefit information output from the interface unit 220 and calculate it as a new main transaction card.

And when the communication unit 210 receives payment completion information of the first card or the second card from the card company server 500, the payment control unit 250 receives the benefit information according to the input selection and the first card or the second applied to the payment. The card information of the card is transmitted to the customer management server 300. Thereafter, the process of the customer management server 300 updating the user information table and notifying the mobile terminal 100 of payment information is as described in FIGS. 4 and 5.

9 is a view showing the configuration of the customer management server 300 according to an embodiment of the present invention. The customer management server 300 is composed of a database unit 310, a communication unit 320, and a central control unit 350. Tables constituting the database unit 310 have been described in FIGS. 3 and 7.

The database unit 310 includes a user information table 301 including user identification information, a benefit information table 305 including user identification information, and a main transaction card information table 302 including user identification number and card information. do.

The communication unit 320 communicates with the payment client 200 and the mobile terminal 100.

The central control unit 350 controls the database unit 310 and the communication unit 320. In addition, the central control unit 350 encrypts a part of the card number among the card information stored in the main transaction card information table 302 with a one-way hash function and stores it in the main transaction card information table. It can be confirmed that the card number itself is not stored, such as "CARD_ENCR_NUMBER" in 302 of FIG. 3.

In addition, when the communication unit 320 receives the card number from the payment client 200 or the mobile terminal 100, the central control unit 350 uses the result of encrypting a part of the card number with a one-way hash function to display the main transaction card information table ( 302) to extract user identification information.

A case in which the customer management server 300 according to an embodiment receives information of the main transaction card from the payment client 200 will be described.

The communication unit 320 receives product information and card information from the payment client 200. The central control unit 350 searches the main transaction card information table 302 using the received card information to extract user identification information. In addition, the central control unit 350 searches and extracts one or more benefit information from the benefit information table 305 using the extracted user identification information.

Then, the communication unit 320 transmits the benefit information to the payment client 200 together with the user identification information. This process was examined in S23 to S26 of FIG. 4.

Meanwhile, as shown in FIG. 5, the central control unit 350 may confirm that the main transaction card information included in the extracted one or more benefit information is different from the received card information.

In this case, the communication unit 320 transmits the benefit information including the new main transaction card information to the payment client 200 together with the user identification information.

In addition, the customer management server 300 may recommend a voucher or a special discount product in the case of a product in which the extracted benefit information is an exchange ticket or a special discount.

For example, the central control unit 350 identifies a case where the similarity between product information included in the extracted one or more benefit information and product information transmitted for payment is high. For example, if there is a "hamburger exchange ticket" in the user's benefit information, and the product transmitted for payment is also a "hamburger" or "sandwich", it is confirmed that the degree of similarity of the product is high.

The similarity of the above-mentioned product information can be confirmed as follows. First, product information may include group information that designates a product type or classification. The "WATER" group for bottled water, the "MILK" group for milk, and the "COOKIE" group for confectionery can be set. Or, it can be confirmed by the similarity of the product name. The similarity of the product may be determined using words included in the product name, such as "eating spring water", "drinking spring water", and "living water". That is, the degree of similarity of product information refers to an example in which a group to which a product belongs is identical, a part of product names overlap, or mutual products are set as similar products.

Further, the similarity of product information may be calculated as the similarity of the number of products. If the number of benefits of the same product is N, if the number of products to be paid is 1, it is determined that the similarity is high. Accordingly, a product having a high degree of similarity includes information stored and stored by a seller in a product when the sales quantity is different in the same product.

Or, if the product information transmitted for payment is "1 500ml bottled water", and the user's benefit information includes "30% discount for 2 500ml bottled water", it is confirmed that the degree of similarity of the product is high.

The central control unit 350 transmits the benefit information including the product information to the payment client 200 together with the user identification information so that the user can select it.

In addition, when information on the main transaction card is received, the customer management server 300 may check whether the card is stolen or misused by extracting user identification information and confirming the user's location. For example, the central control unit 350 may calculate the location of the mobile terminal where the logged-in application is installed with the extracted user identification information.

Then, the location of the payment client 200 (the location of the store) is compared to determine whether it is different. If different, the central control unit 350 may determine that payment is in progress at a location where the main transaction card is different from the user's location.

In this case, the communication unit 320 may transmit product information and card information to the mobile terminal 100 so that the user can check the card theft status.

4 and 5 have been described an embodiment in which the mobile terminal 100 checks the benefit information after payment. To this end, the communication unit 320 receives a payment completion message applying the benefit information previously transmitted from the payment client 200. The communication unit 320 transmits the benefit information applied in the payment process to the mobile terminal in which the application logged in with the user identification information is installed using the user identification information under the control of the central control unit 350. S38 and S38c.

Meanwhile, as illustrated in FIG. 6, payment may be performed on the mobile terminal. The communication unit 320 receives user identification information, product information, and card information from the first mobile terminal (S22c).

The central control unit 350 searches for and extracts one or more benefit information from the benefit information table using the transmitted user identification information (S25 of FIG. 6 ). In addition, the communication unit 320 may transmit the benefit information to the first mobile terminal 100 together with the user identification information or without the user identification information.

In the embodiment of Fig. 6, card theft can be confirmed. The user identification information retrieved from the main transaction card information table 305 using the card information received from the central control unit 350 may be different from the user identification information received from the first mobile terminal. For example, the user identification information received from the first mobile terminal has a UID of "abcd1234", and the result of applying the hash function to the received card information is" Jkcva03klsj23980fkl". "Gsr7890" may be searched as identification information.

In this case, the communication unit 320 may transmit product information and card information to the second mobile terminal where the logged-in application is installed with the searched user identification information (“gsr7890”).

In the offline service environment, in order to receive a discount, the user had to present a physical card or app that can apply for membership or membership benefits of the carrier, and then purchase it with a payment card. Alternatively, even if the membership discount is applied through the simple payment app and the card payment is made, it takes a long time to find the app and execute it and recognize it on the card terminal. Suddenly, there is a problem that cannot be used when the communication environment is difficult.

However, in the case of applying the embodiment of the present invention, the customer can simply apply a variety of benefit information such as carrier and brand membership benefits, use of an exchange ticket, etc. even if the customer simply presents the card and pays as usual.

When applying the present invention, payment by the registered main transaction card can provide payment stability by sending a notification message when payment store information is transmitted to the app or when the app is not in the same store.

In addition, if the pre-purchased product is stored with the registered main transaction card, or when a product is gifted from another person, it may be stored in the benefit information table 305 as benefit information of the exchange ticket. And, when the user pays with the main transaction card, the user can receive the product without paying the amount using the exchange voucher.

Of course, it is possible to present the benefit information (for example, points, discount vouchers, exchange vouchers, etc.) provided in the process of purchasing a product with the corresponding main transaction card to other users. This may be performed in the payment client 200 or the mobile terminal 100.

When implementing the embodiment of the present invention, payment by the registered main transaction card may provide payment stability by sending a notification message when payment store information is transmitted to the app or when the app is not in the same store. Payment store information is information that can identify a convenience store, store, mart, etc. where payment has been performed, and includes code information and location information assigned to each store. This can confirm the location information of the payment client. Of course, the information (identification information) unique to the payment client may also be stored in the customer management server, and the customer management server may check the location of the user by using the payment client information instead of the payment store information.

Methods according to an embodiment of the present invention may be implemented in the form of program instructions that can be executed through various computer means and may be recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, or the like alone or in combination. The program instructions recorded on the medium may be specially designed and configured for the present invention, or may be known and usable by those skilled in computer software.

As described above, although the present invention has been described with limited embodiments and drawings, the present invention is not limited to the above embodiments, and various modifications and variations from these descriptions will be made by those skilled in the art to which the present invention pertains. This is possible. It should be understood that the above-described embodiments are illustrative and non-limiting in all respects, and the scope of the present invention will be indicated by the following claims rather than the detailed description above. And it should be interpreted that the meaning and scope of the claims, as well as all alterable and deformable forms derived from the equivalent concept, are included in the scope of the present invention.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined by the following claims and equivalents to the claims.

Claims

A communication unit communicating with the customer management server and the card company server;

An interface unit that outputs the information received by the communication unit and receives a selection of the output information;

A card reader that receives card information;

After controlling the communication unit, the interface unit and the card reader, and after the card reader receives the card information of the first card, the card information of the first card is transmitted to the customer management server after the communication unit transmits the card information to the customer management server. The benefit information and user identification information received by the communication unit is output to the interface unit,

A payment control unit that controls the communication unit to transmit the final payment amount to which the benefit information is applied according to the selection input to the interface unit and the card information of the first card or the card information of the second card received by the card reader to the card company server. Including, payment client using the main transaction card information.
According to claim 1,

When the communication unit receives payment completion information of the first card or the second card from the card company server,

The payment control unit transmits the benefit information according to the input selection and the card information of the first card or the second card applied to the payment to the customer management server, a payment client using the main transaction card information.
A database unit including a user information table including user identification information, a benefit information table including user identification information, and a main transaction card information table including user identification number and card information;

Payment client, a communication unit to communicate with the mobile terminal; And

The database unit and the communication unit are controlled, and a part of the card number stored in the main transaction card information table is encrypted with a one-way hash function and stored in the main transaction card information table, and the communication unit is the payment client or mobile terminal When receiving the card number from the central management unit for extracting user identification information by retrieving from the main transaction card information table using the result of encrypting a part of the card number with a one-way hash function, customer management server using the main transaction card information .
According to claim 3,

The communication unit receives product information and card information from the payment client,

The central control unit searches the main transaction card information table using the card information to extract user identification information, searches for and extracts one or more benefit information from the benefit information table using the user identification information,

The communication unit transmits the benefit information together with the user identification information to the payment client, customer management server using the main transaction card information.
According to claim 4,

When the main transaction card information included in the extracted one or more benefit information is different from the received card information, the central control unit transmits the benefit information including the main transaction card information to the payment client along with the user identification information. The customer management server using the main transaction card information to be transmitted.
According to claim 4,

When the similarity between the product information included in the extracted one or more benefit information and the received product information is high, the central control unit displays the benefit information including the product information together with the user identification information and the payment client. To the customer management server using the main transaction card information.
According to claim 4,

If the central control unit is different by comparing the location of the payment terminal and the location of the mobile terminal where the logged-in application is installed with the extracted user identification information,

The communication unit transmits the product information and card information to the mobile terminal, a customer management server using the main transaction card information.
According to claim 3,

When the communication unit receives a payment completion message applying the transmitted benefit information from the payment client,

The communication unit transmits the applied benefit information to a mobile terminal having an application logged in with the user identification information using the user identification information under the control of the central control unit, a customer management server using main transaction card information.
According to claim 3,

The communication unit receives user identification information, product information and card information from the first mobile terminal,

The central control unit searches and extracts one or more benefit information from the benefit information table using the transmitted user identification information,

The communication unit transmits the benefit information together with the user identification information to the first mobile terminal, a customer management server using the main transaction card information.
The method of claim 9,

When the user identification information retrieved from the main transaction card information table using the received card information by the central control unit is different from the user identification information received from the first mobile terminal,

The communication unit transmits the product information and card information to a second mobile terminal on which an application logged in with the searched user identification information is installed, a customer management server using main transaction card information.