KR20200057672A - Apparatus and method for providing electronic receipt - Google Patents

Abstract

The present invention provides an apparatus and a method for providing an electronic receipt. According to embodiments of the present invention, the apparatus for providing an electronic receipt comprises: a communication unit configured to transceive data; and a processor configured to be electrically connected to the communication unit. The processor receives payment-related information including payment matching information and payment detail information in accordance with payment approval for payment information of a user from a payment terminal when the payment approval is completed by a payment approval server, transfers the received payment matching information to the payment approval server, receives user identification information corresponding to the payment matching information from the payment approval server, checks whether the user agrees or disagrees to electronic receipt issuance based on the received user identification information, generates an electronic receipt based on the payment detail information if the user agrees to the electronic receipt issuance, and transfers the generated electronic receipt to the user terminal.

Description

Apparatus and method for providing electronic receipts {APPARATUS AND METHOD FOR PROVIDING ELECTRONIC RECEIPT}

The present invention provides an apparatus and method for providing electronic receipts.

In general, in order to purchase a desired product at an offline store (eg, an affiliate store), the user may pay the amount of the product using cash or a credit card. When the product payment is completed in this way, the offline store provides the user with a receipt issued in paper or issues an electronic receipt to replace the paper receipt.

In order to issue an electronic receipt as described above, personal information such as a user's resident registration number, telephone number, and mobile phone number is required, or a membership card or number of the affiliated store is presented, and through this, user authentication is performed and the electronic receipt is sent to the user's mobile terminal. This can be provided.

However, in such a case, whenever a user visits various offline stores and purchases a product, there is a inconvenience in that the user must provide the user's personal information for issuing an electronic receipt, or present a membership card or number provided by the store.

Accordingly, there is a need for a method for issuing an electronic receipt easily and conveniently without requiring separate user identification information (eg, user's personal information, membership number, barcode number, etc.) for issuing the electronic receipt to the user.

(Patent Document 1) KR1020120049802 A

The problem to be solved by the present invention is to provide an apparatus and method for providing an electronic receipt.

Specifically, a problem to be solved by the present invention is to provide an apparatus and method for providing an electronic receipt without requiring separate information for issuing an electronic receipt to a user.

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

In order to solve the problems as described above, an apparatus and method for providing an electronic receipt according to an embodiment of the present invention are provided. Electronic receipt providing apparatus according to an embodiment of the present invention, a communication unit configured to transmit and receive data; And a processor configured to be electrically connected to the communication unit, wherein the processor receives payment history information and payment matching information according to the payment approval from the payment terminal when payment approval for the user's payment information is completed by the payment approval server. Receives payment-related information including, passes the received payment matching information to the payment approval server, receives user identification information corresponding to the payment matching information from the payment approval server, and receives the received user identification information. Check whether the user has consented to or disagrees with the issuance of the electronic receipt, and if the user agrees to issue the electronic receipt, generates an electronic receipt based on the payment history information, and recalls the generated electronic receipt. It is delivered to the user terminal.

In the electronic receipt providing method performed by the processor of the electronic receipt providing device according to the embodiment of the present invention, when payment approval for the user's payment information is completed by the payment approval server, payment history information according to the payment approval from the payment terminal And receiving payment related information including payment matching information; Transmitting the received payment matching information to the payment approval server; Receiving user identification information corresponding to the payment matching information from the payment approval server; Checking whether the user agrees or disagrees with issuing the electronic receipt based on the received user identification information; Generating an electronic receipt based on the payment history information when the user agrees to issue the electronic receipt; And delivering the generated electronic receipt to the user terminal.

Details of other embodiments are included in the detailed description and drawings.

In the present invention, an electronic receipt can be provided without requiring separate information from a user in order to issue an electronic receipt, so that the user can easily and conveniently receive an electronic receipt.

In addition, the present invention is by checking whether or not the agreement or fine for the electronic receipt issued by the user through the services provided by a third party (3 ^rd party) associated with the settlement approved supplier or service provider using a pay-matching information, services, The provider can confirm whether or not to consent to the issuance of the electronic receipt without additional resource consumption.

The effect according to the present invention is not limited by the contents exemplified above, and more various effects are included in the present invention.

1 is a schematic diagram illustrating a system for providing an electronic receipt according to an embodiment of the present invention.
2 is a schematic diagram illustrating a user terminal according to an embodiment of the present invention.
3 is a schematic diagram illustrating a service providing server according to an embodiment of the present invention.
4 is a schematic flowchart illustrating a method for providing an electronic receipt in a service providing server according to an embodiment of the present invention.
5 is a schematic flowchart illustrating a method for providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention.
6 is a schematic flowchart illustrating a method for providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention.
7 is a schematic flowchart illustrating a method for providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention.
8 and 9 are exemplary views of an interface screen showing an electronic receipt 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.

Although the first, second, etc. are used to describe various components, it goes without saying that these components are not limited by these terms. These terms are only used to distinguish one component from another component. Therefore, it goes without saying that the first component mentioned below may be the second component within the technical spirit of the present invention.

The same reference numerals refer to the same components throughout the specification.

Each of the features of the various embodiments of the present invention may be partially or totally combined or combined with each other, and technically various interlocking and driving may be possible as those skilled in the art can fully understand, and each of the embodiments may be implemented independently of each other. It can also be implemented together in an associative relationship.

Hereinafter, various embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a schematic diagram illustrating a system for providing an electronic receipt according to an embodiment of the present invention.

Referring to FIG. 1, the electronic receipt providing system 10 may be a system for providing an electronic receipt using information related to payment without requiring separate user identification information for issuing the electronic receipt to the user. The electronic receipt providing system 10 is based on payment information provided from the user terminal 100 for purchasing an article or receiving a service, a service providing server 200 for providing an electronic receipt, and a payment terminal 350. It may include a payment terminal (for example, a point of sale (POS) terminal) 350 provided for payment to at least one affiliated store that sells or provides goods, and performs a payment approval server 300 to perform.

First, the user terminal 100 is a user interface device for providing an electronic receipt issued by a user who purchases goods from at least one affiliated store or a user who is provided with a service, and is issued by a user who purchases goods or provides a service. Applications, programs, widgets, or web browsers for providing data are installed, or smart phones, tablets, or wearable devices that provide message services (such as Short Message Service (SMS), Multimedia Message Service (MMS), etc.) can do.

Such applications, programs, widgets, or web browsers are serviced by service providers to provide electronic receipts, payment approval companies such as card companies, mobile payment services, and simple payment services associated with service providers, or messengers, It may be serviced through a third party such as a social network service (SNS) or a portal service, but is not limited thereto, and may be serviced by various service providers or a combination of these for providing electronic receipts.

The user terminal 100 is a payment approval server 300 of a payment approval company such as a service provider server 200, a card company server, a mobile payment server, a simple payment server, etc. of a service provider through a corresponding application, program, widget, or web browser. , A third-party server (not shown) of a third party, such as a messenger server, SNS server, or portal service server.

The user terminal 100 provides an interface screen for agreeing or disagreeing with the issuance of the electronic receipt, and through the interface screen, it is possible to obtain consent / non-agreement information for issuing the electronic receipt indicating consent or disagreement for the issuance of the electronic receipt. . The user terminal 100 may transmit the obtained electronic receipt issuance consent / non-consent information to the service providing server 200, the payment approval server 300, or a third party server. For example, the user terminal 100 may display an interface screen for inputting consent / non-agreement of electronic receipt issuance indicating consent or non-agreement of issuance of the electronic receipt. When the consent / non-agreement information of the electronic receipt issuance is input through the interface screen from the user, the user terminal 100 transmits the information of the consent / non-agreement of the issuance of the electronic receipt to the service providing server 200, the payment approval server 300 or a third party It can be delivered to the server.

In various embodiments, the user terminal 100 obtains user identification information including the user's ID, name, or contact information, and provides the obtained user identification information with the electronic receipt issuance agreement / disagreement information service providing server 200 ), Payment approval server 300 or a third party server. For example, when the user subscribes to the electronic receipt providing service provided by the service provider, the user identification information may include subscription information of the user subscribed to the electronic receipt providing service. In various embodiments, when a user subscribes to a third party service associated with a service provider providing an electronic receipt providing service, the user identification information may include subscription information of a user who subscribes to the third party service. In the presented embodiment, the user identification information is not limited to the above, and various user information for providing an electronic receipt may be included.

When payment is approved by the payment approval server 300, and the user agrees to issue the electronic receipt, the user terminal 100 receives an electronic receipt related to payment approval from the service providing server 200 and receives the received electronic receipt. An interface screen can be provided. In the presented embodiment, the interface screens may be interface screens provided through the above-described application, program, widget, or web browser.

In various embodiments, the user terminal 100 may receive a short message including an electronic receipt, a multimedia message, a messenger message, an SNS message or a portal service message, and provide an interface screen indicating the received message. For example, the electronic receipt may be an image, and a multimedia message, messenger message, SNS message or portal service message including the electronic receipt image may be received.

In various embodiments, the user terminal 100 may receive a text message, a multimedia message, a messenger message, an SNS message or a portal service message including address information related to an electronic receipt, and provide an interface screen indicating the received message. have. For example, when the address information provided through the interface screen is selected by the user, the user terminal 100 receives and provides an electronic receipt corresponding to the corresponding address information from the service providing server 200, or for providing an electronic receipt. An electronic receipt corresponding to the corresponding address information may be provided through the called application, program, widget, or web browser by calling an application, program, widget, or web browser.

Next, the service providing server 200 may include a general-purpose computer, a laptop, a data server, and the like that compute various data for providing an electronic receipt. In various embodiments, the service providing server 200 may provide an application, program, widget, or web browser for providing an electronic receipt to the user terminal 100. Such applications, programs, widgets, or web browsers may be provided through a third party associated with a service provider, payment approval provider, or service provider.

Specifically, the service providing server 200 may receive and store user identification information and electronic receipt issuance consent / non-agreement information through an application, program, widget, or web browser installed in the user terminal 100. In various embodiments, the consent / non-agreement of electronic receipt issuance is collected through the payment approval server 300 and stored in the payment approval server 300, or a third-party third-party server associated with a service provider (eg, a messenger server, SNS server or a portal service server, etc.) may be collected and delivered to the service providing server 200, but is not limited thereto.

When payment is approved by the payment approval server 300, the service providing server 200 may receive payment related information from the payment terminal 350. Here, the payment related information may include payment history information and payment matching information. The payment history information may include at least some of the payment date and time, product name, amount, quantity, product type, merchant name, merchant address, merchant contact information, and payment method. The payment matching information includes a card authorization number used to identify a user who is approved for payment, or an authorization key used to share details of a product in each of various payment services such as a mobile payment service or a simple payment service. May include, but is not limited to.

In order to confirm whether the user who has been approved for payment has consented to or disagrees with the issuance of the electronic receipt, the service providing server 200 delivers payment matching information to the payment approval server 300, and payment matching information from the payment approval server 300 User identification information corresponding to may be received.

The service providing server 200 may determine whether the user corresponding to the issuance of the electronic receipt corresponding to the user identification information agrees or disagrees, based on the received user identification information and the pre-stored electronic receipt issuance consent / non-confirmation information. In this case, the service providing server 200 checks user identification information that matches the received user identification information among the pre-stored user identification information for each of a plurality of users, and the identified user among the pre-stored electronic receipt issuance consent / non-migration information It is possible to check the consent / non-agreement of issuing an electronic receipt corresponding to the identification information.

As a result of the confirmation, when the user agrees to issue the electronic receipt, the service providing server 200 generates an electronic receipt based on the payment history information provided from the payment terminal 350 and delivers the generated electronic receipt to the user terminal 100 Can be. The electronic receipt may be expressed as a graphic object (eg, text and / or image, etc.) to represent at least some of the payment date and time, product name, amount, quantity, product type, merchant name, merchant address, merchant contact information, and payment method. have. In various embodiments, the service providing server 200 may provide the user terminal 100 with address information for providing the generated electronic receipt through an application, program, widget, or web browser.

As a result of the confirmation, if the user does not agree with the issuance of the electronic receipt, the service providing server 200 may delete payment related information provided from the payment terminal 350. In various embodiments, the service providing server 200 deletes payment-related information when the consent / non-consent information for issuing the electronic receipt corresponding to the user identification information does not exist or the user identification information is not received in response to the delivery of payment matching information. Can be.

In various embodiments, when payment related information is received from the payment terminal 350, the service providing server 200 transmits payment matching information to the payment approval server 300 to request payment consent information / consent from the payment approval server 300. 300). When the consent / non-agreement of issuing an electronic receipt is received from the payment approval server 300, the service providing server 200 may generate an electronic receipt or delete payment-related information based on the received consent / non-agreement of the issuance of the electronic receipt. have.

Subsequently, the payment approval server 300 may include a general-purpose computer, laptop, data server, etc. that calculates various data to perform payment approval for the user's payment information. For example, the payment approval server 300 includes, but is not limited to, a card company server, a mobile payment server, or a simple payment server, and is not limited thereto, a value added network (VAN) server for electronic payment, or a payment gateway (PG) company. And the like.

When approval for payment information according to payment of a user's goods or service is requested from the payment terminal 350, the payment approval server 300 completes the payment approval and sends information indicating that payment approval is completed to the payment terminal 350. Can deliver. For example, the payment information may include item information, service information or amount of money input or selected in the payment terminal 350 in relation to the goods purchased by the user or services provided to the user.

When payment matching information is received from the service providing server 200, the payment approval server 300 may check user identification information corresponding to the payment matching information and provide the identified user identification information to the service providing server 200. .

Specifically, the payment approval server 300 includes the merchant name, merchant address, merchant contact, payment time, payment amount, payment matching information (eg, approval number, approval key, etc.) and user identification information (eg, user ID, name) , Contact information, etc.). When payment matching information is received from the service providing server 200, the payment approval server 300 checks user identification information related to payment matching information based on the pre-stored payment approval history, and checks the identified user identification information from the service providing server ( 200). If the user identification information related to the payment matching information does not exist, the payment approval server 300 may not deliver a response to the payment matching information.

In various embodiments, the payment approval server 300 may obtain and store information of the user's electronic receipt issuance consent / non-consent from the user terminal 100. For example, the payment approval server 300 receives the user's user identification information and electronic receipt issuance consent / non-consent information through an application, program, widget, or web browser provided by the payment approval company installed on the user terminal 100. It can be received and stored. According to a payment approval request from the payment terminal 350, the payment approval server 300 may perform payment approval for the user's payment information and store payment approval history information. When payment matching information is received from the service providing server 200, the payment approval server 300 checks user identification information corresponding to the payment matching information based on the payment approval history information, and issues an electronic receipt related to the verified user identification information. You can check the consent / non-consent information The payment approval server 300 may transmit the confirmed electronic receipt issuance agreement / unsent information to the service providing server 200. In various embodiments, as a result of checking the consent / non-agreement of electronic receipt issuance, the payment approval server 300 may not transmit a response to the payment matching information when the user does not agree to the issuance of the electronic receipt.

In addition, the payment terminal 350 requests payment approval according to the user's payment information to the payment approval server 300 and provides payment related information service when information indicating that payment approval is completed is received from the payment approval server 300 It can be delivered to the server 200. For example, the payment terminal 350 includes a POS terminal capable of cash payment, card payment, simple payment, or mobile payment, but is not limited thereto, and is separate for performing card payment, simple payment, or mobile payment. It may further include a terminal.

Through this, the present invention can provide an electronic receipt without requiring separate information from the user in order to issue the electronic receipt, so that the user can easily and conveniently receive the electronic receipt.

Hereinafter, the user terminal 100 will be described in more detail with reference to FIG. 2.

2 is a schematic diagram illustrating a user terminal according to an embodiment of the present invention. 1 and 2, the user terminal 100 may include a communication unit 110, a display unit 120, a storage unit 130, and a processor 140.

The communication unit 110 connects the user terminal 110 to communicate with an external device. The communication unit 110 may be connected to the service providing server 200 through wired / wireless communication to transmit and receive various data. Specifically, the communication unit 110 may transmit user identification information and electronic receipt issuance agreement / unidentified information to the service providing server 200 or the payment approval server 300. In various embodiments, the communication unit 110 may transmit user identification information and electronic receipt issuance consent / non-consent information to a third party server. The communication unit 110 may receive an electronic receipt from the service providing server 200, the payment approval server 300, or a third party server.

The display unit 120 may display various contents (eg, text, images, videos, icons, banners or symbols, etc.) to the user. Specifically, the display unit 120 may display an interface screen such as an application, program, widget, or web browser that provides an electronic receipt. Such applications, programs, widgets or web browsers may be provided by a service provider, payment approval provider, or third party.

In various embodiments, the display unit 120 may include a touch screen, for example, a touch, gesture, proximity, drag, and swipe using an electronic pen or a user's body part. (swipe) or hovering (hovering) input.

The storage unit 130 may store various data used to provide an electronic receipt. For example, the storage unit 130 stores the user identification information obtained by the user through the user interface and the electronic receipt received from the service providing server 200 or a graphic object used to represent the electronic receipt. Can be. In various embodiments, the storage unit 130 may store graphic objects used to configure an interface screen.

In various embodiments, the storage unit 130 may be a flash memory type, a hard disk type, a multimedia card micro type, or a card type memory (for example, SD or XD) Memory, etc.), RAM (Random Access Memory, RAM), SRAM (Static Random Access Memory), ROM (Read-Only Memory, ROM), EEPROM (Electrically Erasable Programmable Read-Only Memory), PROM (Programmable Read-Only Memory) , A storage medium of at least one type of a magnetic memory, a magnetic disk, or an optical disk. The user terminal 100 may operate in connection with a web storage that performs a storage function of the storage unit 130 on the Internet.

The processor 140 is operably connected to the communication unit 110, the display unit 120, and the storage unit 130, and can perform various commands for providing an electronic receipt.

Specifically, the processor 140 obtains user identification information and electronic receipt consent / non-agreement information through an application, program, widget, or web browser for providing an electronic receipt, and the obtained user identification information and electronic receipt agreement / The unidentified information may be transmitted to the service providing server 200, the payment approval server 300, or a third party server through the communication unit 110. For example, the processor 140 displays an interface screen through which the user identification information or electronic receipt issuance agreement / non-consent information is input through the display unit 120, and issues the user identification information or electronic receipt input through the interface screen. You can obtain consent / non-agreement information. Here, the interface screen may be an interface screen related to an application, program, widget, or website provided by a service provider, payment approval provider, or third party.

When the payment approval of the payment approval server 300 by the payment approval request of the payment terminal 350 is completed, and the user of the user terminal 100 agrees to issue an electronic receipt, the processor 140 may communicate through the communication unit 110. An electronic receipt may be received from the service providing server 200 and an interface screen indicating the received electronic receipt may be displayed through the display 120. In various embodiments, the processor 140 receives a short message including an electronic receipt, a multimedia message, an SNS message, or a portal service message, and displays a received short message, multimedia message, SNS message, or portal service message, etc. You can also display the interface screen.

In various embodiments, the processor 140 may receive a text message, a multimedia message, a messenger message, an SNS message or a portal service message including address information related to an electronic receipt, and provide an interface screen indicating each message received. have. For example, when the address information included in the interface screen is selected, the processor 140 receives and provides an electronic receipt corresponding to the address information from the service providing server 200, or an application, program for providing an electronic receipt, An electronic receipt corresponding to the corresponding address information may be provided through an application, program, widget, or web browser called by calling a widget or a web browser.

Hereinafter, the service providing server 200 will be described in more detail with reference to FIG. 3.

3 is a schematic diagram illustrating a service providing server according to an embodiment of the present invention. 1 and 3, the service providing server 200 may include a communication unit 210, a storage unit 220, and a processor 230.

The communication unit 210 connects the service providing server 200 to communicate with an external device. The communication unit 210 may be connected to the user terminal 100, the payment approval server 300, and the payment terminal 350 to transmit and receive various data. Specifically, the communication unit 210 may receive the user identification information and the consent / non-agreement information of issuing the electronic receipt from the user terminal 100, and transmit the electronic receipt to the user terminal 100. The communication unit 210 may receive payment-related information from the payment terminal 350 and deliver payment matching information to the payment approval server 300. The communication unit 210 may receive user identification information or electronic receipt issuance consent / non-agreement information from the payment approval server 300.

The storage unit 220 may store various data for providing an electronic receipt. For example, the storage unit 220 may store user identification information for each of a plurality of users and electronic consent issuance / non-agreement information corresponding to the user identification information. In various embodiments, the storage unit 220 may store various data used to generate an electronic receipt.

In various embodiments, the storage unit 220 may include at least one type of flash memory type, hard disk type, multimedia card micro type, card type memory, RAM, SRAM, ROM, EEPROM, PROM, magnetic memory, magnetic disk, and optical disk. It may include a storage medium. The service providing server 200 may operate in connection with web storage that performs a storage function of the storage unit 220 on the Internet.

The processor 230 is operably connected to the communication unit 210 and the storage unit 220 and can perform various commands for providing an electronic receipt. Specifically, the processor 230 receives the user identification information and the electronic receipt issuance consent / non-confirmation information from the user terminal 100 through the communication unit 210, and the received user identification information and the electronic receipt issuance consent / non-consent information Can be stored in the storage unit 220.

When payment approval for the user's payment information is completed by the payment approval server 300 and payment related information is received from the payment terminal 350, the processor 230 pays payment matching information among payment related information to issue an electronic receipt. It can be delivered to the approval server 300. Here, the payment matching information may include the above-mentioned card approval number or an approval key used to share product details.

When the user identification information corresponding to the payment matching information is received from the payment approval server 300, the processor 230 may check the user identification information that matches the received user identification information among pre-stored user identification information for each of a plurality of users. have. The processor 230 corresponds to the received user identification information based on the electronic receipt issuance consent / non-agreement information corresponding to the identified user identification information among the stored electronic receipt issuance consent / non-agreement information corresponding to the previously stored user identification information. It is possible to confirm whether the user has consented to the issuance of the electronic receipt or not.

When the user agrees to issue the electronic receipt, the processor 230 generates an electronic receipt based on payment history information among payment-related information received from the payment terminal 350 and delivers the generated electronic receipt to the user terminal 100 Can be.

If the user does not agree with the issuance of the electronic receipt, the processor 230 may delete payment related information.

In various embodiments, if user identification information is not received from the payment approval server 300, the processor 230 may decide to issue the electronic receipt of the user without consent, and delete payment related information.

In various embodiments, when the user identification information for each of the plurality of users and the electronic receipt issuance consent / non-agreement information corresponding to the user identification information are stored in the payment approval server 300, the processor 230 may check the payment matching information with the payment approval server. Delivered to (300), it is possible to receive the electronic receipt issuance / non-issuance information corresponding to the payment matching information from the payment approval server (300). The processor 230 may check whether the user agrees or disagrees with the issue of the electronic receipt based on the received electronic receipt issuance / non-issuance information.

In various embodiments, the processor 230 may obtain user identification information and electronic receipt issuance consent / non-agreement information from the user terminal 100 through a third party server associated with a service provider. Here, the user identification information and the consent / non-agreement of the electronic receipt issuance may be obtained through an application, program, widget, or website provided by a third party. User identification information obtained through an application, a program, a widget or a website, etc., and consent / non-agreement information of the electronic receipt issuance may be provided to the service providing server 200 through a third party server.

The processor 230 may store the user identification information received through the third party server and the consent / non-agreement of the electronic receipt issuance in the storage unit 220.

When payment approval is completed, the processor 230 may receive payment-related information from the payment terminal 350 and deliver payment matching information among the received payment-related information to the payment approval server 300. When the user identification information corresponding to the payment matching information is received from the payment approval server 300, the processor 230 checks the user identification information matching the received user identification information among the user identification information stored in the storage unit, and the verified user It is possible to check the consent / non-agreement of issuing an electronic receipt corresponding to the identification information.

When the user agrees to issue the electronic receipt, the processor 230 may generate an electronic receipt based on payment history information among payment related information, and transmit the generated electronic receipt to the user terminal 100 through a third party server. In this case, the electronic receipt may be provided to a user through a third-party application, program, widget, or website installed on the terminal.

In various embodiments, the processor 230 may generate address information related to an electronic receipt and provide the generated address information to the user terminal 100. The address information may be provided to the user terminal 100 through a text message, or may be provided to the user terminal 100 through an application, program, widget, or the like provided by a service provider or a third party. For example, the address information may be hyperlink information for executing an application, program, widget, etc. that provides an electronic receipt, or to go to a website that provides an electronic receipt. Such address information may also be provided to the user terminal 100 through a third party server.

As described above, the present invention does not require separate user identification information from the user to issue the electronic receipt by confirming the consent / non-agreement of the user's electronic receipt issuance using the user identification information obtained from the payment approval server 300. Therefore, the user can easily and conveniently receive an electronic receipt.

4 is a schematic flowchart illustrating a method for providing an electronic receipt in a service providing server according to an embodiment of the present invention.

1 and 4, when the payment approval for the payment information of the user is completed by the payment approval server 300 (S400), the service providing server 200 pays the payment according to the payment approval from the payment terminal 350 Payment related information including information and payment matching information is received (S410).

The service providing server 200 transmits the received payment matching information to the payment approval server 300 (S420), and receives user identification information corresponding to payment matching information from the payment approval server 300 (S430).

The service providing server 200 confirms whether the user corresponding to the received user identification information agrees or disagrees with the issuance of the electronic receipt (S440). Specifically, the service providing server 200 may correspond to the electronic receipt issuance consent / non-agreement information corresponding to the received user identification information among the electronic receipt issuance consent / non-agreement information stored in correspondence with the user identification information for each of a plurality of users. Based on this, it is possible to confirm whether the user has agreed or is not in agreement with the issuance of the electronic receipt.

In the case of the consent to issue the electronic receipt, the service providing server 200 generates an electronic receipt based on the payment history information and transmits it to the user terminal (S450), and if the electronic receipt is not agreed, deletes the payment related information (S460).

5 is a schematic flowchart illustrating a method for providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention. The electronic receipt providing system 10 according to the presented embodiment includes a user terminal 100, a service providing server 200, a payment approval server 300, and a payment terminal 350 as described above with reference to FIG. 1. Hereinafter, an embodiment in which the service providing server 200 obtains consent / non-agreement information for issuing an electronic receipt corresponding to user identification information from the user terminal 100 will be described.

1 and 5, the user terminal 100 transmits the electronic receipt issuance agreement or non-agreement information to the service providing server 200 (S500). In this case, the user terminal 100 may transmit the electronic receipt issuance agreement or non-agreement information corresponding to the user identification information to the service providing server 200.

When payment approval is completed (S502), the payment terminal 350 delivers the payment related information to the service providing server 200 (S504), and the service providing server 200 delivers the payment matching information to the payment approval server 300 (S506). Specifically, when payment approval of the payment approval server 300 is completed by the payment approval request of the payment terminal 350, the payment terminal 350 provides payment related information including payment history information and payment matching information to the service providing server ( 200). The service providing server 200 may transmit payment matching information to the payment approval server 300 in order to confirm whether the user consents or fails to issue the electronic receipt.

The payment approval server 300 confirms the user identification information in response to the payment matching information (S508), and transmits the identified user identification information to the service providing server 200 (S510). The service providing server 200 confirms whether the user corresponding to the user identification information agrees or disagrees with the issuance of the electronic receipt (S512). Specifically, the service providing server 200 confirms the consent / non-agreement information of the electronic receipt issuance corresponding to the received user identification information among the consent / non-agreement information stored in response to the user identification information for each of the plurality of users. Can be.

When the user agrees to issue the electronic receipt, the service providing server 200 generates an electronic receipt based on the payment history information (S514) and delivers the generated electronic receipt to the user terminal 100 (S516).

If the user does not agree to the issuance of the electronic receipt, the service providing server 200 deletes payment-related information (S518).

Through this, the present invention allows the user to easily and conveniently obtain an electronic receipt by confirming whether the user agrees or disagrees with the issue of the electronic receipt using payment matching information without requiring additional information from the user.

6 is a schematic flowchart illustrating a method for providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention. The electronic receipt providing system 10 according to the presented embodiment includes a user terminal 100, a service providing server 200, a payment approval server 300, and a payment terminal 350 as described above with reference to FIG. 1. Hereinafter, an embodiment in which the payment approval server 300 obtains consent / non-agreement information for issuing an electronic receipt corresponding to user identification information from the user terminal 100 will be described.

1 and 6, the user terminal 100 transmits the electronic receipt issuance agreement or non-agreement information to the payment approval server 300 (S500). In this case, the user terminal 100 may transmit the electronic receipt issuance agreement or non-agreement information corresponding to the user identification information to the payment approval server 200. In this case, the user terminal 100 obtains the consent or issuance of the electronic receipt corresponding to the user identification information and the user identification information through an application, program, widget, or web page provided by the payment approval company, and the obtained user identification The electronic receipt issuance agreement or unidentified information corresponding to the information and the user identification information may be transmitted to the payment approval server 300.

When payment approval is completed (S602), the payment terminal 350 delivers the payment related information to the service providing server 200 (S604), and the service providing server 200 delivers the payment matching information to the payment approval server 300 (S606).

The payment approval server 300 checks the user identification information corresponding to the payment matching information (S608), and confirms the consent or non-agreement of the electronic receipt issuance corresponding to the identified user identification information (S610). Specifically, the payment approval server 300 confirms the electronic receipt issuance agreement or non-agreement information corresponding to the identified user identification information among the electronic receipt issuance agreement or non-agreement information stored in correspondence with the user identification information of each of a plurality of users. Can be.

The payment approval server 300 transmits the confirmed electronic receipt issuance agreement or unsent information to the service providing server 200 (S612).

The service providing server 200 checks whether the user consents to or is not in agreement with the issuance of the electronic receipt (S614), and when the user's electronic receipt is consent, generates the electronic receipt based on the payment history information (S616). The received electronic receipt is delivered to the user terminal (S618). If the user's electronic receipt is not agreed, the service providing server 200 deletes payment-related information (S620).

Through this, the present invention can confirm whether the user consents or is not consent to the issuance of the electronic receipt by using the payment matching information. Therefore, the user is required to separately request information for the issuance of the electronic receipt, or the consent or issue of the issuance of the electronic receipt for each user is not met. It is possible to issue an electronic receipt without consuming additional resources for storing the information of.

7 is a schematic flowchart illustrating a method for providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention. The electronic receipt providing system 10 according to the presented embodiment includes a user terminal 100, a service providing server 200, a payment approval server 300, a payment terminal 350, and a third party server 400. In the following, the payment approval server 300 obtains the consent / non-agreement of issuing the electronic receipt corresponding to the user identification information from the user terminal 100 through the third party server 400, and the user through the third party server 400 An embodiment of transmitting an electronic receipt to the terminal 100 will be described.

1 and 7, the user terminal 100 transmits an electronic receipt issuance agreement or unidentified information to the third party server 400 (S700), and the third party server 400 agrees to issue the received electronic receipt. Alternatively, the unidentified information is transmitted to the service providing server 200 (S702). For example, the user terminal 100 may provide an interface screen such as an application, program, widget, or web page provided by a third party to input user identification information and electronic receipt issuance agreement or non-consent information. The user of the user terminal 100 inputs the user identification information and the consent or issuance of the electronic receipt through the interface screen, and the user terminal 100 receives the input user identification information and the consent or issuance of the electronic receipt issuance. It may be delivered to the service providing server 200 through the third party server 400.

When payment approval is completed (S602), the payment terminal 350 delivers the payment related information to the service providing server 200 (S604), and the service providing server 200 delivers the payment matching information to the payment approval server 300 (S606).

The payment approval information 300 checks user identification information corresponding to the received payment matching information (S712), and transmits the identified user identification information to the service providing server 200 (S714).

The service providing server 200 checks whether the user's electronic receipt corresponding to the user identification information agrees or disagrees (S714), and when the user's electronic receipt is consent, generates an electronic receipt based on the payment history information (S716), and transmits the generated electronic receipt to the user terminal through the sub-party server (S718, S720). In this case, the electronic receipt may be provided to the user terminal 100 through an application, program, widget, or web page provided by a third party.

If the user's electronic receipt is not agreed, the service providing server 200 deletes payment-related information (S722).

Through this, the present invention confirms whether or not the user consents to the issuance of the electronic receipt through the service provided by the third party linked with the service provider, or the service provider consents to or disagrees with the issuance of the electronic receipt without additional resource consumption. Can be checked.

8 and 9 are exemplary views of an interface screen showing an electronic receipt according to an embodiment of the present invention. In the presented embodiment, a case in which a short message including address information related to an electronic receipt is provided will be described.

Referring to FIG. 8, the user terminal 100 receives a short message including address information related to an electronic receipt from the service providing server 200 and displays an interface screen 800 for displaying the received short message ( 120).

The corresponding interface screen 800 is a graphic that includes information on an electronic receipt (eg, [The Real Electronic Receipt] KB Kookmin Card 9 ** approval, 12,000 won lump sum, 3/24 20:30, Fatskin Fat Beans) It may include an object 810. The graphic object 810 may further include address information (eg, http://thereal.co.kr/20190324_203040_1) for outputting an electronic receipt image. For example, the address information may be hyperlink information indicating a specific location of the electronic receipt image.

If there is a selection of the corresponding address information by the user, the user terminal 100 may display an interface screen 900 for displaying an electronic receipt image corresponding to the address information as shown in FIG. 9.

Referring to FIG. 9, the interface screen 900 is a merchant's name, contact information, business number, address, payment date, product name, unit price, quantity, amount, taxable product value, value added, and total amount corresponding to payment history information , May include a graphic object (eg, text) representing the return amount.

As described above, according to the present invention, an electronic receipt can be easily and conveniently issued to a user by providing an electronic receipt without requiring separate user identification information from a user in order to issue an electronic receipt.

The apparatus and method according to an embodiment of the present invention may be implemented in a form of program instructions that can be executed through various computer means and recorded in a computer readable medium. Computer-readable media may include program instructions, data files, data structures, or the like alone or in combination.

The program instructions recorded on the computer-readable medium may be specially designed and configured for the present invention or may be known and usable by those skilled in the computer software field. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs, DVDs, and magnetic media such as floptical disks. Includes hardware devices specifically configured to store and execute program instructions such as magneto-optical media and ROM, RAM, flash memory, and the like. Examples of program instructions include high-level language codes that can be executed by a computer using an interpreter, etc., as well as machine language codes produced by a compiler.

The hardware device described above may be configured to operate as one or more software modules to perform the operation of the present invention, and vice versa.

The embodiments of the present invention have been described in more detail with reference to the accompanying drawings, but the present invention is not necessarily limited to these embodiments, and may be variously modified without departing from the technical spirit of the present invention. . Therefore, the embodiments disclosed in the present invention are not intended to limit the technical spirit of the present invention, but to explain, and the scope of the technical spirit of the present invention is not limited by these embodiments. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. The scope of protection of the present invention should be interpreted by the claims below, and all technical spirits within the equivalent range should be interpreted as being included in the scope of the present invention.

100: user terminal
110: communication department
120: display unit
130: storage unit
140: processor
200: service providing server
210: communication unit
220: storage
230: processor
300: payment approval server
350: payment terminal
400 third-party server

Claims (14)

An electronic receipt providing device for providing an electronic receipt to a user without requiring user identification information,
A communication unit configured to transmit and receive data; And
And a processor configured to be electrically connected to the communication unit,
The processor,
When payment approval for the user's payment information is completed by the payment approval server, payment related information including payment matching information according to the payment approval and user identification information provided from the user is received from the payment terminal. and,
Deliver the received payment matching information to the payment approval server,
Receiving user identification information corresponding to the payment matching information from the payment approval server,
Check the issuance of the electronic receipt of the user based on the received user identification information,
Create an electronic receipt based on the payment history information,
Delivering the generated electronic receipt to the user terminal,
The payment matching information is an electronic receipt providing device, which is an approval number of a payment method generated when a payment is approved. The method of claim 1, wherein the processor,
An electronic receipt providing device for deleting the payment related information when the user does not agree to issue the electronic receipt. According to claim 1, The payment history information,
Electronic receipt providing device, including at least a part of the payment date and time, product name, amount, quantity, product type, merchant name, merchant address, merchant contact information, and payment method. According to claim 1, The payment matching information,
An electronic receipt providing device comprising a card authorization number used to identify a user who is authorized to pay or an authorization key used to share details of a product in a payment service. According to claim 1,
Further comprising a storage unit for storing the user identification information for each of the plurality of users and the electronic receipt issuance agreement or non-agreement information corresponding to the user identification information,
The processor,
Among the user identification information stored in the storage unit, it is checked whether user identification information matching the received user identification information exists,
If there is user identification information that matches the received user identification information, the electronic receipt providing device confirms the consent or non-agreement of the electronic receipt issuance corresponding to the user identification information. The method of claim 5, wherein the processor,
If there is no user identification information matching the received user identification information, the electronic payment providing device for deleting the payment-related information. The method of claim 1, wherein the processor,
If the user identification information corresponding to the payment matching information is not received from the payment approval server, the user determines that the electronic receipt is not agreed, and deletes the payment related information. An electronic receipt providing method performed by a processor of an electronic receipt providing device for providing an electronic receipt to a user without requiring user identification information, comprising:
When payment approval for the user's payment information is completed by the payment approval server, payment related information including payment matching information according to the payment approval and user identification information provided from the user is received from the payment terminal. To do;
Transmitting the received payment matching information to the payment approval server;
Receiving user identification information corresponding to the payment matching information from the payment approval server;
Confirming the issuance of the electronic receipt of the user based on the received user identification information;
Generating an electronic receipt based on the payment history information; And
And transmitting the generated electronic receipt to a user terminal.
The payment matching information is an approval number of a payment method generated when a payment is approved, and an electronic receipt providing method. The method of claim 8,
And if the user does not agree to the issuance of the electronic receipt, deleting the payment related information. The method of claim 8, wherein the payment history information,
A method of providing an electronic receipt, including at least some of the payment date and time, product name, amount, quantity, product type, merchant name, merchant address, merchant contact information, and payment method. The method of claim 8, wherein the payment matching information,
A method of providing an electronic receipt, comprising a card authorization number used to identify a user who has been approved for payment or an authorization key used to share details of a product in a payment service. The method of claim 8,
Further comprising the step of storing the user identification information for each of the plurality of users and the electronic receipt issuance agreement or non-agreement information corresponding to the user identification information in the storage unit,
The step of confirming the issuance of the electronic receipt of the user based on the received user identification information,
Checking whether user identification information matching the received user identification information among the user identification information stored in the storage unit exists; And
And if there is user identification information matching the received user identification information, confirming the consent or issuance of electronic receipt issuance corresponding to the user identification information. The method of claim 12, wherein checking the issuance of the electronic receipt of the user based on the received user identification information comprises:
And if there is no user identification information matching the received user identification information, deleting the payment history information. The method of claim 8, wherein the step of confirming the issuance of the electronic receipt of the user based on the received user identification information,
Determining that the user does not consent to the issuance of the electronic receipt when user identification information corresponding to the payment matching information is not received from the payment approval server; And
And deleting the payment-related information.

Images