WO2023210845A1

WO2023210845A1 - Method and terminal device for providing benefit information by using information about credit card

Info

Publication number: WO2023210845A1
Application number: PCT/KR2022/006186
Authority: WO
Inventors: 푹스파벨; 이나라
Original assignee: 쿠팡 주식회사
Priority date: 2022-04-27
Filing date: 2022-04-29
Publication date: 2023-11-02
Also published as: KR20230152366A; TW202343331A

Abstract

A terminal device according to various embodiments of the present disclosure may include: at least one communication circuit connected for communication with a card reader, a first server device, and a second server device; a memory; and a processor. The processor according to various embodiments may be configured to: receive information about a credit card for payment of a specific amount of money from the card reader; transmit the information about the credit card to the first server device; receive a unique identifier corresponding to the information about the credit card from the first server device; transmit the unique identifier to the second server device; receive benefit information for a customer corresponding to the unique identifier from the second server device; and determine whether or not to apply the benefit information, on the basis of a user input.

Description

Method and terminal device for providing benefit information using credit card information

This disclosure relates to a method and terminal device for providing benefit information using credit card information.

Typically, stores are equipped with point of sale (POS) terminal devices to manage data about sold products and make payments for sold products. The POS terminal device may be equipped with a card reader for payment with a credit card. When a payment is made using a credit card at a POS terminal installed in a store, the store's POS terminal device transmits a card authorization request to the value added network (VAN) server, and the VAN server sends the card to the card company server. The approval information is transmitted, and the ban company server can receive approval or rejection information for the card approval request from the card company server and transmit it to the store's POS terminal device.

In order to provide benefit information (e.g., discount information or loyalty information) to customers who attempt to pay for a specific amount in a store, the customer's personal information has been requested separately from the payment process. As an example, in order to provide benefit information to the customer, separately from the payment process, the customer's QR code that can confirm the customer's personal information is recognized by a separate QR code reader, and based on the recognized customer's personal information This allows benefit information to be provided to customers. As another example, in order to provide benefit information to the customer, the customer may be asked to enter a phone number into the POS terminal device, and benefit information may be provided to the customer based on the phone number entered by the customer. In the above-mentioned examples, it took a lot of time to identify customers and provide benefit information, and cumbersome procedures had to be performed, and there were cases where specific hardware devices were required for this.

A terminal device according to various embodiments of the present disclosure may include at least one communication circuit, a memory, and a processor connected to communication with a card reader, a first server device, and a second server device. The processor according to various embodiments receives credit card information for payment of a specific amount from the card reader, transmits the credit card information to the first server device, and receives the credit card from the first server device. Receive a unique identifier corresponding to information on the card, transmit the unique identifier to the second server device, receive customer benefit information corresponding to the unique identifier from the second server device, and based on user input It may be configured to determine whether to apply the benefit information.

According to various embodiments, the benefit information includes discount information, and the processor, in response to determining to apply the discount information, determines the final amount to which the discount information is applied to the specific amount and the unique identifier. 1 Can be configured to transmit to a server device.

According to various embodiments, the benefit information includes loyalty information, and the processor, in response to determining to apply the loyalty information, transmits the specific amount and the unique identifier to the first server device, and It may be configured to transmit applied royalty information to the second server device.

The credit card information according to various embodiments may include a 16-digit credit card number, and the processor may be configured to encrypt the credit card number and transmit it to the first server device.

The unique identifier according to various embodiments may be data obtained from the credit card information through an encryption algorithm.

The first server device according to various embodiments may include at least one bansa server device.

The processor according to various embodiments may be configured to transmit basic information of the customer holding the credit card to the second server device before receiving the credit card information.

The customer's basic information according to various embodiments may include at least one of the customer's name, phone number, gender, and age.

The processor according to various embodiments may be configured to further receive statistical information about the customer's visit, including at least one of the number of visits, average payment amount, and visit period of the customer, from the second server device.

The processor according to various embodiments may be configured to further receive visitation statistics information about a plurality of customers from the second server device.

A method of providing benefit information to a customer using credit card information of a terminal device according to various embodiments of the present disclosure includes the operations of receiving credit card information for payment of a specific amount from a card reader, An operation of transmitting information to a first server device, an operation of receiving a unique identifier corresponding to the information of the credit card from the first server device, an operation of transmitting the unique identifier to a second server device, the second server device It may include receiving customer benefit information corresponding to the unique identifier from and determining whether to apply the benefit information based on user input.

According to various embodiments, the benefit information includes discount information, and the method includes, in response to determining to apply the discount information, a final amount to which the discount information is applied to the specific amount and the unique identifier. 1 May include the operation of transmitting to a server device.

According to various embodiments, the benefit information includes loyalty information, and the method includes, in response to determining to apply the loyalty information, transmitting the specific amount and the unique identifier to the first server device; It may include transmitting the applied royalty information to the second server device.

According to various embodiments, the credit card information includes a 16-digit credit card number, and the operation of transmitting the credit card information to the first server device includes encrypting the credit card number to the first server device. It may include the action of transmitting to .

According to various embodiments, before the operation of receiving the credit card information, the operation of transmitting basic information of the customer who owns the credit card to the second server device may be included.

According to various embodiments, the method may further include receiving statistical information about the customer's visit including at least one of the number of visits, average payment amount, and visit period of the customer from the second server device.

According to various embodiments, the method may further include receiving visit statistics information about a plurality of customers from the second server device.

According to various embodiments of the present disclosure, a customer who owns a credit card can be identified even if only the process of paying a specific amount using a credit card is performed. Additionally, benefit information can be provided to identified customers.

According to various embodiments of the present disclosure, in order to provide benefit information to customers, a cumbersome personal information identification process that must be performed separately from the payment process can be omitted. Additionally, there is no need to provide a separate hardware device to identify customers' personal information.

1 is a diagram illustrating a system according to various embodiments of the present disclosure.

Figure 2 is a block diagram illustrating a terminal device according to various embodiments of the present disclosure.

3 is an operation flowchart of a system according to various embodiments of the present disclosure.

4 is a flowchart of the operation of a terminal device according to various embodiments of the present disclosure.

5 is a flowchart of the operation of a terminal device according to various embodiments of the present disclosure.

Figure 6 is an operation flowchart of a second server device according to various embodiments of the present disclosure.

Embodiments of the present disclosure are illustrated for the purpose of explaining the technical idea of the present disclosure. The scope of rights according to the present disclosure is not limited to the embodiments presented below or the specific description of these embodiments.

All technical terms and scientific terms used in this disclosure, unless otherwise defined, have meanings commonly understood by those skilled in the art to which this disclosure pertains. All terms used in this disclosure are selected for the purpose of more clearly explaining this disclosure and are not selected to limit the scope of rights according to this disclosure.

Expressions such as “comprising,” “comprising,” “having,” and the like used in the present disclosure are open terms that imply the possibility of including other embodiments, unless otherwise stated in the phrase or sentence containing the expression. It should be understood as (open-ended terms).

The singular forms described in this disclosure may include plural forms unless otherwise stated, and this also applies to the singular forms recited in the claims.

Expressions such as “first” and “second” used in the present disclosure are used to distinguish a plurality of components from each other and do not limit the order or importance of the components.

The term “unit” used in this disclosure refers to software or hardware components such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, “wealth” is not limited to hardware and software. The “copy” may be configured to reside on an addressable storage medium and may be configured to reproduce on one or more processors. Thus, as an example, “part” refers to software components, such as object-oriented software components, class components, and task components, processors, functions, properties, procedures, subroutines, Includes segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within components and “parts” may be combined into smaller numbers of components and “parts” or may be further separated into additional components and “parts”.

As used in this disclosure, the expression "based on" is used to describe one or more factors that influence the act or action of decision, judgment, or action described in the phrase or sentence containing the expression, and this expression It does not exclude additional factors that may influence the decision, act or action of judgment.

In this disclosure, when a component is referred to as being “connected” or “connected” to another component, it means that the component can be directly connected or connected to the other component, or as a new component. It should be understood that it can be connected or connected through other components.

Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings. In the accompanying drawings, identical or corresponding components are given the same reference numerals. Additionally, in the description of the following embodiments, overlapping descriptions of identical or corresponding components may be omitted. However, even if descriptions of components are omitted, it is not intended that such components are not included in any embodiment.

1 is a diagram illustrating a system 10 according to various embodiments of the present disclosure. Referring to FIG. 1, a system 10 according to various embodiments includes a terminal device 110, a card reader 120, a first server device 130, and a second server device 150. can do. The terminal device 110 may be wired or wirelessly connected to the card reader 120, the first server device 130, and the second server device 150.

The terminal device 110 according to various embodiments is a POS terminal device 110 (or POS terminal) that can collectively manage sales-related data and collect customer information. The terminal device 110 may be, for example, a POS terminal device 110 that is installed in a store and manages sales of products in the store. A user (e.g., store employee, franchise owner, etc.) may use the terminal device 110 to create and/or manage order information for a specific product. For example, a user may generate order information by entering a customer's order into the terminal device 110. For example, even when there is no user input, the terminal device 110 may generate order information according to remotely received data. The user can check and manage at least one order information generated through the terminal device 110. In this drawing, the terminal device 110 is installed in a store as an example, but of course, in the case of an online store, it does not necessarily need to be installed in the store.

According to various embodiments, the terminal device 110 may be connected to communication with the card reader 120 and may perform credit card payment using the card reader 120. For example, the terminal device 110 may be wired or wirelessly connected to the card reader 120. In this drawing, the terminal device 110 and the card reader 120 are shown as separate devices, but of course, they can also be integrated and implemented as a single device.

When a customer visiting a store makes a card payment for a specific amount using the card reader 120 installed in the store, the terminal device 110 may request card payment approval from the first server device 130. The first server device 130 may be a value added network (VAN) server and may include at least one VAN server device. According to various embodiments of the present disclosure, the system 10 according to various embodiments may identify the customer using credit card information and provide benefit information for the customer before requesting card payment authorization. there is. Afterwards, you can decide whether to apply the benefit information and request card payment approval. A detailed description of the above-mentioned features will be provided later.

The first server device 130 according to various embodiments may receive credit card information from the terminal device 110. For example, when a user (e.g., a customer, an employee) wants to pay a certain amount with a credit card at the card reader 120 (e.g., swipes, inserts, or inserts a credit card into the card reader 120). (or contacting the card reader 120 or placing it near the card reader 120), the card reader 120 can transmit the information of the read credit card to the terminal device 110. The terminal device 110 may transmit credit card information to the first server device 130. According to one embodiment, the terminal device 110 may encrypt credit card information and transmit it to the first server device 130. Credit card information may include, for example, a 16-digit credit card number. The credit card information may further include, for example, the name or phone number of the customer who holds the credit card. According to various embodiments, credit cards include not only physical cards, but also cards implemented in software that can be stored in an electronic device (eg, a smartphone).

The first server device 130 may use the received credit card information to obtain or confirm a unique identifier corresponding to the credit card information. The first server device 130 may obtain a unique identifier by inputting credit card information into an encryption algorithm. For example, the first server device 130 may use a pepper solution to obtain a unique identifier corresponding to credit card information. When using the Pepper solution, it is possible to obtain multiple different unique identifiers corresponding to information on multiple credit cards. That is, in this case, there may be a separate unique identifier for each credit card information. Additionally, if you use the same hash function and the same string when using the Pepper solution, you can obtain the same unique identifier each time you enter the same credit card information. In other words, if the same hash function and the same string are used, only one unique identifier can exist in the information of one credit card. When receiving encrypted credit card information from the terminal device 110, the first server device 130 decrypts the encrypted credit card information and inputs it into the Pepper solution, thereby creating a unique identifier corresponding to the credit card information. You can also obtain it. In addition to the Pepper solution, various encryption algorithms may be used.

The first server device 130 according to various embodiments may transmit a unique identifier corresponding to credit card information to the terminal device 110. The terminal device 110 may transmit the received unique identifier to the second server device 150. The second server device 150 may check benefit information corresponding to the received unique identifier. The second server device 150 may store various customer information corresponding to each of a plurality of unique identifiers. For example, the second server device 150 may store basic information about customers and benefit information about customers corresponding to each of a plurality of unique identifiers. The second server device 150 may transmit customer benefit information corresponding to the received unique identifier to the terminal device 110. That is, the second server device 150 can identify a customer matching the unique identifier and provide benefit information corresponding to the identified customer to the terminal device 110.

Benefit information may include discount information or loyalty information. Discount information may be, for example, a discount coupon that can be provided by a store to an identified customer. Loyalty information may be, for example, points or coupons that can be accumulated at a store for an identified customer. The customer's personal information is information that needs to be entered only once, and may include at least one of the customer's name, phone number, gender, and age. For example, a customer's personal information may be entered during initial sign-up (registration). For example, the terminal device 110 may receive basic information input from the customer and transmit the basic information input from the customer to the second server device 150. The second server device 150 may store the customer's basic information.

The second server device 150 according to various embodiments may generate and store various statistical information based on the customer's basic information and the customer's credit card usage history. For example, the second server device 150 may generate statistical information about the customer's number of visits to each store, average payment amount, and visit cycle based on the customer's basic information and credit card usage history. The second server device 150 may transmit, to the terminal device 110 installed in the store, customer visit statistical information including at least one of the number of times the customer visits the store, the average payment amount, and the visit cycle. The second server device 150 according to various embodiments may generate visit statistics information about a plurality of customers for each store. The second server device 150 may transmit visit statistics information about a plurality of customers to the store to the terminal device 110 installed in the store.

The second server device 150 according to various embodiments may match and store a plurality of credit card information for a specific customer. For example, when a specific customer uses multiple credit cards, information on the multiple credit cards can be matched to the specific customer and stored. The second server device may use the name or phone number of the customer holding each credit card to identify and store the customer's credit card.

The terminal device 110 according to various embodiments may determine whether to apply customer benefit information received from the second server device 150 based on user input. For example, the terminal device 110 may display customer benefit information received from the second server device 150 through the display 117 and determine whether to apply the benefit information through the input device 119. User input can be received to determine . If the display 117 is a touch display, user input for determining whether to apply the benefit information may be received through the display 117. For example, the terminal device 110 may receive a user input from the customer determining to apply the benefit information, or may receive a user input determining not to apply the benefit information.

The terminal device 110 according to various embodiments may transmit to the first server device 130 an approval request for the final payment amount reflecting whether or not benefit information is applied. If the benefit information is discount information, in response to determining to apply the discount information, a final amount to which the discount information is applied and a unique identifier may be transmitted to the first server device 130 for a specific amount to be calculated. For example, in a case where the amount to be paid by the customer is 10,000 won, a 2,000 won discount coupon is provided, and if the user decides to use this discount coupon, the terminal device 110 sets the final payment amount of 8,000 won. By transmitting the unique identifier corresponding to the won and credit card information to the first server device 130, card payment approval for 8,000 won can be requested.

If the benefit information is loyalty information, in response to determining to apply the loyalty information, a specific amount to be calculated and a unique identifier may be transmitted to the first server device 130. Additionally, the applied royalty information may be transmitted to the second server device 150. For example, in a case where the amount to be paid by the customer is 10,000 won, a 500 won savings coupon is provided, and if it is decided to use this savings coupon, the terminal device 110 stores the amount to be paid, 10,000 won, and the credit By transmitting the unique identifier corresponding to the card information to the first server device 130, card payment approval for 10,000 won can be requested. Additionally, the applied 500 won savings coupon can be transmitted to the second server device 150 so that 500 won can be accumulated for the customer.

If the customer decides not to apply the benefit information, the terminal device 110 may transmit the initial payment amount along with a unique identifier to the first server device 130. That is, in this case, the terminal device 1110 may request credit card payment approval for a specific amount to be initially paid from the first server device 130. Additionally, the first server device 130 may store data indicating that the customer did not use the benefit information.

The first server device 130 according to various embodiments may request card payment approval from the card company server device 140 in response to receiving a card payment approval request from the terminal device 110. The second server device 150 may be a server device operated by a credit card company. The card company server device 140 may determine whether to approve a card payment approval request.

Accordingly, in order to receive benefit information when a customer wants to pay a specific amount, there is no need to enter separate personal information other than paying with a credit card, and the store also installs a separate hardware device for this purpose. There is no need to have it.

Figure 2 is a block diagram of a terminal device 110 according to various embodiments of the present disclosure. Referring to FIG. 2, a terminal device 110 according to various embodiments may include a processor 111, a memory 113, at least one communication circuit 115, a display 117, and an input device 119. there is. Even if some of the components shown in FIG. 2 are omitted or replaced, there will be no problem in implementing the various embodiments disclosed in this document.

According to various embodiments, the processor 111 may be a component capable of performing operations or data processing related to control and/or communication of each component of the terminal device 110. The processor 111 may be operatively connected to components of the terminal device 110, for example. The processor 111 may load commands or data received from other components of the terminal device 110 into the memory 113, process the commands or data stored in the memory 113, and store the resulting data. there is. The memory 113 according to various embodiments may store instructions for the operation of the processor 111 described above.

According to various embodiments, at least one communication circuit 115 may establish a communication channel with an external electronic device and transmit and receive various data with the external device. According to various embodiments, at least one communication circuit 115 may include a cellular communication module and be configured to be connected to a cellular network (eg, 3G, LTE, 5G, Wibro, or Wimax). According to various embodiments, at least one communication circuit 115 includes a short-range communication module and uses short-range communication (e.g., Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), UWB) to communicate with external electronic devices and data. Sending and receiving is possible, but is not limited to this. In this document, for convenience of explanation, “at least one communication circuit” is described as “communication circuit,” but the communication circuit described in this document means at least one communication circuit.

According to various embodiments, the display 117 may display various screens based on control of the processor 111. The display 117 may be implemented in the form of a touch sensor panel (TSP) that can recognize contact or proximity (eg, hovering) of various external objects. The display 117 may include a capacitance sensor to recognize contact or proximity of various external objects. A capacitance sensor may be composed of a plurality of capacitors, and the capacitance sensor may apply an electrical signal to the capacitor. A capacitor can charge and discharge charge in response to the application of an electrical signal. When an electrical signal is applied to a capacitor, the capacitor may be charged depending on the magnitude of the voltage of the electrical signal. The display 117 may receive a touch input based on signals collected from the capacitive sensor.

The input device 119 according to various embodiments may receive commands or data to be used for components of the terminal device 110 from outside the terminal device 110 (eg, a user). Input device 119 may include, for example, a microphone, mouse, or keyboard.

3 is a flowchart of the operation of system 10 according to various embodiments of the present disclosure. Referring to the operation flowchart 300, the card reader 120 according to various embodiments may transmit credit card information to the terminal device 110 in operation 301. For example, when a user (eg, a customer or a store employee) pays a certain amount of money to the card reader 120 with a credit card, the card reader 120 can read the information of the credit card. The card reader 120 may transmit the read credit card information to the communication-connected terminal device 110. The terminal device 110 and the card reader 120 may be wired or wirelessly connected for communication and may be implemented as a single device.

The terminal device 110 according to various embodiments may transmit credit card information to the first server device 130 in operation 303. For example, the terminal device 110 may transmit credit card information to the first server device 130 to check benefit information before transmitting a card payment approval request. According to one embodiment, the terminal device 110 may encrypt credit card information and transmit it to the first server device 130. The credit card information may include a 16-digit credit card number. In this case, the terminal device 110 may encrypt the credit card number and transmit it to the first server device 130. The credit card information may further include, for example, the name or phone number of the customer who holds the credit card. The first server device 130 may be, for example, a server device from a ban company.

The first server device 130 according to various embodiments may obtain a unique identifier corresponding to credit card information in operation 305. The first server device 130 may obtain a unique identifier by inputting credit card information into an encryption algorithm. The encryption algorithm may be, for example, a pepper solution. If encrypted credit card information is received from the terminal device 110, the first server device 130 decrypts the encrypted credit card information, obtains the credit card information, and encrypts the credit card information. It can be input into the algorithm. According to one embodiment, the first server device 130 may store information on the received credit card.

The first server device 130 according to various embodiments may transmit a unique identifier to the terminal device 110 in operation 307. The terminal device 110 according to various embodiments may transmit the unique identifier received from the first server device 130 to the second server device 150 in operation 309.

The second server device 150 according to various embodiments may identify customer information corresponding to the received unique identifier in operation 311. The second server device 150 may store information on a plurality of customers and benefit information corresponding to each of the plurality of customer information. The second server device 150 may store a unique identifier corresponding to each piece of information on a plurality of customers. Accordingly, the second server device 150 can identify the corresponding customer using only the unique identifier information corresponding to the credit card information.

The second server device 150 according to various embodiments may check customer benefit information corresponding to the identified customer information in operation 313. Benefit information may include, for example, discount information or loyalty information.

The second server device 150 according to various embodiments may transmit the confirmed benefit information to the terminal device 110 in operation 315. The terminal device 110 according to various embodiments may determine whether to apply benefit information based on user input in operation 317. The user can select whether to apply benefit information through the display 117 or input device 119 of the terminal device 110. For example, the user may decide to apply benefit information or not. For example, if the benefit information is discount information (eg, discount coupon), the user may decide to apply the discount information.

The terminal device 110 according to various embodiments may transmit the final payment amount and a unique identifier to the first server device 130 in operation 319. The terminal device 110 may request credit card payment approval for the final payment amount reflecting whether or not benefit information is applied to the first server device 130. The terminal device 110 may transmit a unique identifier corresponding to the final payment amount reflecting the discount information and credit card information to the first server device 130 .

The first server device 130 according to various embodiments may transmit a credit card approval request to the card company server device 140. The first server device 130 may request credit card payment approval for the final payment amount reflecting whether or not benefit information is applied to the card company server device 140.

FIG. 4 is a flowchart of the operation of the terminal device 110 according to various embodiments of the present disclosure. Referring to the operation flowchart 400, in operation 410, the processor 111 of the terminal device 110 according to various embodiments receives a credit card for payment of a specific amount from the card reader 120 communicated with the terminal device 110. information can be received.

The processor 111 according to various embodiments may transmit credit card information to the first server device 130 in operation 420. For example, the processor 111 may encrypt a 16-digit credit card number and transmit it to the first server device 130.

The processor 111 according to various embodiments may receive a unique identifier corresponding to credit card information from the first server device 130 in operation 430. The unique identifier may be a hash value obtained by inputting credit card information into an encryption algorithm.

The processor 111 according to various embodiments may transmit the received unique identifier to the second server device 150 in operation 440. The processor 111 according to various embodiments may receive customer benefit information corresponding to the unique identifier from the second server device 150 in operation 450. The second server device 150 may identify customer information matching the unique identifier, confirm benefit information corresponding to the identified customer information, and transmit it to the terminal device 110 .

The processor 111 according to various embodiments may determine whether to apply benefit information based on user input in operation 460. The processor 111 may receive a user input for selecting whether to apply benefit information through the display 117 or the input device 119. Processor 111 may determine whether to apply benefit information based on the user input.

FIG. 5 is a flowchart of the operation of the terminal device 110 according to various embodiments of the present disclosure. Content that overlaps with the content described in FIG. 4 will be omitted. Referring to operation flowchart 500, the processor 111 of the terminal device 110 according to various embodiments may receive credit card information for paying a specific amount from the card reader 120 in operation 510.

The processor 111 according to various embodiments transmits credit card information to the first server device 130 and receives a unique identifier corresponding to the credit card information from the first server device 130 in operation 520. can do.

The processor 111 according to various embodiments may transmit a unique identifier to the second server device 150 and receive customer benefit information corresponding to the unique identifier from the second server device 150 in operation 530. there is.

The processor 111 according to various embodiments may determine whether to apply the received benefit information based on the user input in operation 540.

If it is determined that the benefit information is not applied, branching to operation 580 (540-NO), the processor 111 may request card payment approval for a specific amount. That is, the processor 111 may request card payment approval for a specific amount to be initially paid. To this end, the processor 111 may transmit a unique identifier corresponding to a specific amount of money and credit card information to the first server device 130. For example, if the initial payment amount is 10,000 won, in response to the decision not to apply the benefit information, card payment approval for 10,000 won may be requested.

If it is determined to apply the benefit information, the process may branch to operation 550 (540-YES). In operation 550, the processor 111 may check what type of benefit information is.

If the benefit information is discount information, the processor 111 may branch to operation 560 (550 - discount information) and request card payment approval for the final payment amount with the discount information applied to the specific amount. To this end, the processor 111 may transmit to the first server device 130 a unique identifier corresponding to the final payment amount with discount information applied to the specific amount and credit card information. For example, if the initial payment amount is 10,000 won and the discount information is a coupon for a 2,000 won discount, the processor 111 may request card payment approval for 8,000 won.

If the benefit information is royalty information, the processor 111 branches to operation 570 (550 - royalty information) and transmits the applied royalty information to the second server device 150. The processor 111 may request card payment approval for a specific amount in operation 580. The processor 111 may transmit a unique identifier corresponding to a specific amount and credit card information to the first server device 130. For example, if the initial payment amount is 10,000 won and the loyalty information is a coupon that accumulates 1,000 won, you can request card payment approval for 10,000 won, and send the accumulated loyalty information of 1,000 won to the second server device ( 150). In this case, the second server device 150 may store the fact that the amount accumulated for the customer is 2,000 won.

Figure 6 is an operation flowchart of the second server device 150 according to various embodiments of the present disclosure. Referring to the operation flowchart 600, the second server device 150 according to various embodiments may receive a unique identifier from the terminal device 110 in operation 610.

The second server device 150 according to various embodiments may identify customer information corresponding to the unique identifier in operation 620. The second server device 150 can store information on a plurality of customers. The second server device 150 may store a unique identifier corresponding to each piece of information on a plurality of customers. Accordingly, the second server device 150 can identify the corresponding customer using only the unique identifier information corresponding to the credit card information.

The second server device 150 according to various embodiments may check customer benefit information corresponding to the identified customer information in operation 630. The second server device 150 may store benefit information corresponding to each of a plurality of customer information. Accordingly, the second server device 150 may check the customer benefit information corresponding to the customer information identified based on the unique identifier.

The second server device 150 according to various embodiments may transmit the confirmed benefit information to the terminal device 110 in operation 640. Although not shown, the second server device 150 may further transmit statistical information about customers' visits to the store. The customer's visit statistics information may include, for example, at least one of the customer's number of visits, average payment amount, and visit cycle. The second server device 150 may further transmit visit statistics information regarding a plurality of customers.

Although the process steps, method steps, algorithms, etc. are described in a sequential order in the flow diagrams shown in FIGS. 3-6, such processes, methods, and algorithms may be configured to operate in any suitable order. In other words, the steps of the processes, methods and algorithms described in various embodiments of this disclosure do not need to be performed in the order described in this disclosure. Additionally, although some steps are described as being performed asynchronously, in other embodiments, some such steps may be performed concurrently. Additionally, illustration of a process by depiction in the drawings does not mean that the illustrated process excludes other variations and modifications thereto, and that any of the illustrated process or steps thereof may be used in various embodiments of the present disclosure. It does not imply that more than one is required, nor does it imply that the illustrated process is preferred.

Although the method has been described through specific embodiments, the method can also be implemented as computer-readable code on a computer-readable recording medium. Computer-readable recording media include all types of recording devices that store data that can be read by a computer system. Examples of computer-readable recording media may include ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage devices. Additionally, computer-readable recording media can be distributed across computer systems connected to a network, so that computer-readable code can be stored and executed in a distributed manner. And, functional programs, codes, and code segments for implementing the above embodiments can be easily deduced by programmers in the technical field to which this disclosure pertains.

Claims

In the terminal device,

at least one communication circuit connected in communication with the card reader, the first server device, and the second server device;

Memory; and

Includes a processor,

The processor,

Receive credit card information for paying a specific amount from the card reader,

transmitting the credit card information to the first server device,

Receive a unique identifier corresponding to the credit card information from the first server device,

transmitting the unique identifier to the second server device,

Receive customer benefit information corresponding to the unique identifier from the second server device,

A terminal device, configured to determine whether to apply the benefit information based on user input.
According to paragraph 1,

The benefit information includes discount information,

The processor,

In response to determining to apply the discount information, the terminal device is configured to transmit, to the first server device, a final payment amount with the discount information applied to the specific amount and the unique identifier.
According to paragraph 1,

The benefit information includes loyalty information,

The processor,

In response to determining to apply the loyalty information, transmitting the specific amount and the unique identifier to the first server device;

A terminal device, configured to transmit the applied royalty information to the second server device.
According to paragraph 1,

The credit card information includes a 16-digit credit card number,

and the processor is configured to encrypt the credit card number and transmit it to the first server device.
According to paragraph 1,

The unique identifier is data obtained from the credit card information through an encryption algorithm.
According to paragraph 1,

A terminal device, wherein the first server device includes at least one bansa server device.
According to paragraph 1,

The processor,

A terminal device, configured to transmit basic information of the customer holding the credit card to the second server device before receiving the information of the credit card.
In clause 7,

The basic information of the customer includes at least one of the customer's name, phone number, gender, and age.
In clause 7,

The processor,

The terminal device is further configured to receive, from the second server device, statistical information about the customer's visit, including at least one of the customer's number of visits, average payment amount, and visit period.
According to clause 9,

The processor,

The terminal device is configured to further receive, from the second server device, visitation statistics information about a plurality of customers.
In a method of providing benefit information to a customer using credit card information of a terminal device,

An operation of receiving credit card information for payment of a specific amount from a card reader;

transmitting the credit card information to a first server device;

Receiving a unique identifier corresponding to the credit card information from the first server device;

transmitting the unique identifier to a second server device;

Receiving customer benefit information corresponding to the unique identifier from the second server device; and

A method comprising determining whether to apply the benefit information based on user input.
According to clause 11,

The benefit information includes discount information,

The above method is,

In response to determining to apply the discount information, transmitting a final payment amount with the discount information applied to the specific amount and the unique identifier to the first server device.
According to clause 11,

The benefit information includes loyalty information,

The above method is,

In response to determining to apply the loyalty information, transmitting the specific amount and the unique identifier to the first server device; and

A method comprising transmitting the applied royalty information to the second server device.
According to clause 11,

The credit card information includes a 16-digit credit card number,

The operation of transmitting the credit card information to the first server device is an operation of encrypting the credit card number and transmitting it to the first server device.
According to clause 11,

The method wherein the unique identifier is data obtained through an encryption algorithm of the credit card information.
According to clause 11,

The method of claim 1, wherein the first server device includes at least one bansa server device.
According to clause 11,

A method comprising transmitting basic information of the customer holding the credit card to the second server device before receiving the credit card information.
According to clause 17,

The basic information of the customer includes at least one of the customer's name, phone number, gender, and age.
According to clause 17,

The method further includes receiving, from the second server device, statistical information about the customer's visit including at least one of the number of visits, average payment amount, and visit period of the customer.
According to clause 19,

The method further comprising receiving, from the second server device, visitation statistics information regarding a plurality of customers.