WO2021049897A1 - Dispositif et procédé de fourniture de reçu électronique - Google Patents

Dispositif et procédé de fourniture de reçu électronique Download PDF

Info

Publication number
WO2021049897A1
WO2021049897A1 PCT/KR2020/012274 KR2020012274W WO2021049897A1 WO 2021049897 A1 WO2021049897 A1 WO 2021049897A1 KR 2020012274 W KR2020012274 W KR 2020012274W WO 2021049897 A1 WO2021049897 A1 WO 2021049897A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
electronic receipt
data
user
server
Prior art date
Application number
PCT/KR2020/012274
Other languages
English (en)
Korean (ko)
Inventor
손종희
김재명
Original Assignee
주식회사 더리얼마케팅
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020200116368A external-priority patent/KR20210031410A/ko
Application filed by 주식회사 더리얼마케팅 filed Critical 주식회사 더리얼마케팅
Publication of WO2021049897A1 publication Critical patent/WO2021049897A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment

Definitions

  • the present invention relates to a technology for providing an electronic receipt, and more particularly, to a device and method for providing an electronic receipt that can easily and conveniently issue and provide an electronic receipt without requiring separate user identification information for issuing an electronic receipt to the user. About.
  • a user in order to purchase a desired product at an offline store (eg, affiliated store), a user can pay for the product by using cash or a credit card.
  • the offline store provides the user with a paper-issued receipt or issues an electronic receipt that can replace the paper receipt.
  • Korean Patent Registration No. 10-1255142 (2013.04.10) relates to a method of issuing an electronic receipt, and after purchasing goods or providing services, an electronic receipt containing payment details or a key corresponding to the electronic receipt information on the customer's mobile terminal It is possible to provide a method of issuing electronic receipts that prevents the use of paper receipts by transferring values.
  • Korean Patent Registration No. 10-1625916 (2016.05.25) relates to a method and apparatus for issuing an electronic receipt, an application mounted on a dedicated smartphone for issuing an electronic receipt, software (SW) provided to a merchant terminal, and an electronic receipt.
  • SW software
  • an electronic receipt By building a separate server that handles related functions and providing an API (Application Programming Interface) using a separate standardized communication protocol to the operator, the e-receipt issuer system, receiver's receiving module, and other related systems can be transferred regardless of the solution.
  • API Application Programming Interface
  • An embodiment of the present invention is to provide an electronic receipt providing apparatus and method capable of easily and conveniently issuing and providing an electronic receipt without requiring separate user identification information for issuing an electronic receipt to a user.
  • An embodiment of the present invention is to provide an electronic receipt providing apparatus and method capable of issuing and providing an electronic receipt to a user by receiving user identification information for issuing an electronic receipt from a payment approval server after payment approval.
  • An embodiment of the present invention is to provide an electronic receipt providing apparatus and method capable of generating an electronic receipt based on payment details information and providing notification of the electronic receipt to a user through an app push.
  • an apparatus and method for providing an electronic receipt are provided.
  • An electronic receipt providing apparatus includes: a communication unit configured to transmit and receive data; And a control unit operably connected to the communication unit, wherein the control unit performs payment approval for payment data received from the payment terminal through the communication unit, and whether the user agrees to issue an electronic receipt from the service providing server through the communication unit Receiving payment matching data used to confirm the payment, determining issuance of an electronic receipt for the user based on the payment matching data, requesting payment details data used for issuing the electronic receipt to the service providing server, and When the payment details data is received from the service providing server, the electronic receipt is generated using the received payment details data, and the generated electronic receipt is transmitted to a user terminal.
  • An electronic receipt providing method performed by an electronic receipt providing apparatus includes: performing payment approval for payment data received from a payment terminal; Receiving payment matching data used to confirm whether the user agrees to issue an electronic receipt from the service providing server; Determining issuance of an electronic receipt for the user based on the payment matching data; Requesting payment detail data used for issuing the electronic receipt to the service providing server; Generating the electronic receipt using the received payment detail data when the payment detail data is received from the service providing server; And transmitting the generated electronic receipt to the user terminal.
  • the disclosed technology can have the following effects. However, since it does not mean that a specific embodiment should include all of the following effects or only the following effects, it should not be understood that the scope of the rights of the disclosed technology is limited thereby.
  • the apparatus and method for providing an electronic receipt according to an embodiment of the present invention can provide an electronic receipt without requiring separate information from the user in order to issue an electronic receipt, so that the user can easily and conveniently obtain the electronic receipt. .
  • the electronic receipt providing apparatus and method receive user identification information from a payment approval server using payment matching information corresponding to a payment identification code generated after payment is completed, and identify a user for issuing an electronic receipt. Because it can, it is possible to easily and conveniently provide an electronic receipt to the user.
  • FIG. 1 is a diagram illustrating a system for providing an electronic receipt according to an embodiment of the present invention.
  • FIG. 2 is a block diagram illustrating a physical configuration of the apparatus for providing an electronic receipt in FIG. 1.
  • FIG. 3 is a block diagram showing functional elements of the processor in FIG. 2.
  • FIG. 4 is a flowchart illustrating a process of providing an electronic receipt performed by the processor in FIG. 2.
  • FIG. 5 is a diagram illustrating an embodiment of a process of providing an electronic receipt performed through the apparatus for providing an electronic receipt in FIG. 1.
  • FIG. 6 is an exemplary screen showing the form of an electronic receipt provided to the user terminal in FIG. 1.
  • FIGS. 7A and 7B are schematic diagrams of a system for providing an electronic receipt according to various embodiments of the present disclosure.
  • FIG. 8 is a schematic diagram illustrating a user terminal according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram illustrating a service providing server according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram illustrating a payment approval server according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram illustrating a communication service provider server according to an embodiment of the present invention.
  • FIG. 12 is a flowchart illustrating a method of providing an electronic receipt in a payment approval server according to an embodiment of the present invention.
  • FIG. 13 is a flowchart illustrating a method of providing an electronic receipt in a communication service provider server according to an embodiment of the present invention.
  • FIG. 14 is a flowchart illustrating a method of providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention.
  • 15 is a flowchart illustrating a method of providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention.
  • the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, and the identification code does not describe the order of each step, and each step has a specific sequence clearly in the context. Unless otherwise stated, it may occur differently from the stated order. That is, each of the steps may occur in the same order as the specified order, may be performed substantially simultaneously, or may be performed in the reverse order.
  • the present invention can be implemented as computer-readable code on a computer-readable recording medium, and the computer-readable recording medium includes all types of recording devices storing data that can be read by a computer system. do.
  • Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tapes, floppy disks, and optical data storage devices.
  • the computer-readable recording medium is distributed over a computer system connected by a network, so that computer-readable codes can be stored and executed in a distributed manner.
  • FIG. 1 is a diagram illustrating a system for providing an electronic receipt according to an embodiment of the present invention.
  • the electronic receipt providing system 100 may include a user terminal 110, a payment terminal 130, a payment approval server 150, and an electronic receipt providing device 170.
  • the user terminal 110 may correspond to a computing device capable of receiving an electronic receipt related to payment of a user who has purchased an item or provided a service at at least one affiliated store, and may be implemented as a smartphone, a laptop, or a computer, It is not necessarily limited thereto, and may be implemented in various devices such as a tablet PC.
  • the user terminal 110 may be connected to the payment terminal 130, the payment approval server 150, and the electronic receipt providing device 170 through a network.
  • the user terminal 110 may be installed with an application, a program, a widget, or a web browser for providing an electronic receipt.
  • the e-receipt providing application, program, widget, or web browser is provided by the e-receipt providing device 170 according to an embodiment or linked to the e-receipt providing device 170, mobile payment, simple payment, etc. It may be provided through the same payment approval server 150, but is not limited thereto, and may be provided through a third party such as a messenger, a social network service (SNS), a portal service, and the like.
  • SNS social network service
  • the user terminal 110 may determine whether to consent to issuance of an electronic receipt, and may receive an electronic receipt when consent to issuance of an electronic receipt is made. After payment is approved, the user terminal 110 may receive an electronic receipt related to payment approval from the electronic receipt providing device 170. In one embodiment, the user terminal 110 may receive an electronic receipt related person including address information related to the electronic receipt from the electronic receipt providing device 170, and when the electronic receipt related person is selected by the user, the electronic receipt providing device ( 170) can receive an electronic receipt corresponding to the address information.
  • the user terminal 110 may be connected to the payment approval server 150 through a network, and may receive an electronic receipt through the payment approval server 150.
  • the user terminal 110 may receive a short message including an electronic receipt, a multimedia message, a messenger message, an SNS message, or a portal service message, and may provide the received message on an interface screen indicating the received message.
  • the user terminal 110 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 may provide an interface screen indicating the received message.
  • the payment terminal 130 may correspond to a point of sale (POS) provided for payment at an affiliate store that sells goods or provides services, and is not limited thereto, such as cash payment, card payment, simple payment, or mobile payment. It may be implemented as a computing device capable of performing payment using a payment method presented by the user.
  • the payment terminal 130 requests payment approval according to the user's payment information to the payment approval server 150, and when information indicating that payment approval has been completed is received from the payment approval server 150, the payment terminal 130 transmits payment related information. It can be delivered to the electronic receipt providing device 170.
  • the payment terminal 130 provides an electronic receipt of payment details information including at least the user's purchase amount and payment matching information uniquely issued by the payment approval server 150 when payment is approved. It can be transmitted to the providing device 170.
  • the payment approval server 150 may include a general-purpose computer, a laptop, a data server, etc. that calculate various data to perform payment approval for the user's payment information.
  • the payment approval server 150 may include a card company server, a mobile payment server, or a simple payment server, but is not limited thereto, and a value added network (VAN) company server or a payment gateway (PG) for electronic payment. ), etc. may be included.
  • VAN value added network
  • PG payment gateway
  • the payment approval server 150 completes payment approval and transmits information indicating that payment approval is completed to the payment terminal 130 when approval for payment information according to the user's product payment or service provision is requested from the payment server 130.
  • the payment information may include product information, service information, or amount, etc. input or selected in the payment terminal 130 in relation to a product purchased by the user or a service provided to the user.
  • the payment approval server 150 may issue payment matching information to the payment terminal 130 after payment approval.
  • the payment matching information may include an authorization number or an authorization key.
  • the payment approval server 150 may check user identification information corresponding to the payment matching information and provide the verified user identification information to the electronic receipt providing device 170. have.
  • the payment approval server 150 includes the affiliate store name, affiliate store address, affiliate store contact information, payment time, payment amount, payment matching information (eg, approval number, approval key, etc.), and user identification information (eg, user ID, name, contact information, etc.). ) Can be stored in the payment approval history information.
  • the payment approval server 150 checks user identification information related to payment matching information based on a previously stored payment approval history, and provides an electronic receipt with the verified user identification information. It can be delivered to the device 170. In one embodiment, the payment approval server 150 may request an electronic receipt to the electronic receipt providing device 170 and provide the electronic receipt to the user terminal 110.
  • the electronic receipt providing device 170 may be implemented as a server corresponding to a computer or program capable of providing an electronic receipt to the user terminal 110.
  • the electronic receipt providing device 170 may be connected to the user terminal 110, the payment terminal 130, and the payment approval server 150 through a network, and may exchange information.
  • the electronic receipt providing device 170 may receive payment-related information from the payment terminal 130, and for issuing an electronic receipt from the payment approval server 150 through payment matching information included in the payment-related information.
  • User identification information can be provided. That is, the electronic receipt providing device 170 provides user identification information (user phone number) through a query to the payment approval server 150 without requesting separate information (user personal information, membership number, barcode, etc.) from the user. I can receive it.
  • the electronic receipt providing device 170 may generate an electronic receipt based on the payment history information included in the payment related information and provide the generated electronic receipt to the payment approval server 150 or the user terminal 110. have.
  • the electronic receipt providing device 170 may store the electronic receipt by linking with a database to connect the electronic receipt with a person associated with the electronic receipt.
  • the electronic receipt providing device 170 may be implemented by including a database therein, if necessary.
  • the electronic receipt providing apparatus 170 may be implemented including a processor, a memory, a user input/output unit, and a communication interface, which will be described in more detail with reference to FIG. 2.
  • FIG. 2 is a block diagram illustrating a physical configuration of the apparatus for providing an electronic receipt in FIG. 1.
  • the electronic receipt providing apparatus 170 may include a processor 210, a memory 230, a user input/output unit 250, and a communication interface 270.
  • the processor 210 may receive payment-related information from the payment terminal 130 and execute each procedure for generating an electronic receipt, and manage the memory 230 that is read or written throughout the process, and the memory It is possible to schedule a synchronization time between the volatile memory and the non-volatile memory in 230.
  • the processor 210 can control the overall operation of the electronic receipt providing device 170, and is electrically connected to the memory 230, the user input/output unit 250, and the communication interface 270 to control the data flow between them. I can.
  • the processor 210 may be implemented as a CPU (Central Processing Unit) of the electronic receipt providing apparatus 170.
  • CPU Central Processing Unit
  • the memory 230 is implemented as a nonvolatile memory such as a solid state disk (SSD) or a hard disk drive (HDD), and may include an auxiliary storage device used to store all data required for the electronic receipt providing device 170, and , A main memory device implemented as a volatile memory such as random access memory (RAM).
  • SSD solid state disk
  • HDD hard disk drive
  • main memory device implemented as a volatile memory such as random access memory (RAM).
  • the user input/output unit 250 may include an environment for receiving a user input and an environment for outputting specific information to a user.
  • the user input/output unit 250 may include an input device including an adapter such as a touch pad, a touch screen, an on-screen keyboard, or a pointing device, and an output device including an adapter such as a monitor or a touch screen.
  • the user input/output unit 250 may correspond to a computing device connected through a remote connection, and in such a case, the electronic receipt providing device 170 may be performed as a server.
  • the communication interface 270 includes an environment for connecting to an external device or system through a network, for example, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), and a value Added Network) may include an adapter for communication.
  • a local area network LAN
  • MAN metropolitan area network
  • WAN wide area network
  • a value Added Network may include an adapter for communication.
  • FIG. 3 is a block diagram showing functional elements of the processor in FIG. 2.
  • the processor 210 may include an information receiving unit 310, an electronic receipt generating unit 330, an electronic receipt processing unit 350, an electronic receipt providing unit 370 and a control unit 390. .
  • the information receiving unit 310 may receive payment-related information from the payment terminal 130 when payment performed between the payment terminal 130 and the payment approval server 150 is approved.
  • Payment related information may include payment details information and payment matching information.
  • the payment details information may include at least the user's purchase amount.
  • the payment detail information may further include at least one of payment date and time, product name, quantity, product type, affiliate store name, affiliate store address, affiliate store contact information, and payment method.
  • the payment matching information may correspond to a payment identification code uniquely issued by the payment approval server 150 after payment is completed.
  • the payment matching information may include an authorization number used to identify a payment approved user or an authorization key used to share detailed product details in a payment service.
  • the information receiving unit 310 may query the payment approval server 150 for payment matching information to receive user identification information.
  • the payment approval server 150 may identify a user based on payment matching information and may transmit the user identification information to the electronic receipt providing device 170.
  • the user identification information may include a card number or phone number of a user registered in the payment approval server 150.
  • the e-receipt providing device 170 may check the e-receipt issuance address of the user through the user identification information.
  • the electronic receipt providing device 170 may check the user's electronic receipt receiving method through user identification information.
  • Users can register a method for receiving electronic receipts, such as receiving via e-mail or text message, or via a chat app or a credit card company's exclusive app, and can receive the electronic receipt through the registered method.
  • the electronic receipt providing device 170 performs user identification by the payment approval server 150, so that a separate procedure for requesting user-related information for issuing an electronic receipt to the user is not required.
  • the electronic receipt generator 330 may generate an electronic receipt based on payment detail information included in payment related information.
  • the e-receipt generation unit 330 may generate an e-receipt according to a standardized e-receipt format, and the e-receipt may include details of the same item as the paper receipt.
  • the electronic receipt generation unit 330 may check whether the user is subject to issuance of an electronic receipt based on the user identification information, and in the case of issuance of the electronic receipt, it may generate an electronic receipt based on the payment details information. If the receipt is not subject to issuance, payment details can be deleted.
  • the electronic receipt processing unit 350 may determine whether to request an electronic receipt from the payment approval server 150 and provide the generated electronic receipt to the payment approval server 150 when there is a request for an electronic receipt from the payment approval server 150 Before doing so, it can be processed into an electronic receipt form required by the payment approval server 150.
  • the payment approval server 150 is a card company server
  • an electronic receipt form uniquely designed for each card company may be designated, and an electronic receipt form uniquely designed for each affiliated store (business operator) may be designated.
  • the electronic receipt processing unit 350 may process the electronic receipt into an electronic receipt form designated by the payment approval server 150 at the request of the payment approval server 150.
  • the electronic receipt processing unit 350 may process the electronic receipt into an electronic receipt form designated by the affiliated store (company) when there is no request from the payment approval server 150.
  • the electronic receipt providing unit 370 transmits the electronic receipt to the payment approval server 150 and provides it to the user terminal 110 through the payment approval server 150. I can. At this time, the electronic receipt providing unit 370 provides an image of the electronic receipt processed according to the form of the payment authorization server 150 according to the request of the payment authorization server 150 or provides detailed information corresponding to the unprocessed electronic receipt item. It can be transmitted to the payment approval server 150. When the payment approval server 150 receives the processed electronic receipt image from the electronic receipt providing unit 370, it can be provided to the user terminal 110 as it is. The image may be processed in the form of a receipt and provided to the user terminal 110.
  • the payment approval server 150 may provide an electronic receipt to the user terminal 110 through the push method of the own app. If there is no request for the electronic receipt from the payment approval server 150, the electronic receipt providing unit 370 may store the electronic receipt in connection with the electronic receipt associate, and transmit the electronic receipt associate to the user terminal 110. The user terminal 110 may receive an electronic receipt stored in a location connected to the electronic receipt associate through the electronic receipt associate.
  • the control unit 390 controls the overall operation of the processor 210, and control flow or data between the information receiving unit 310, the electronic receipt generating unit 330, the electronic receipt processing unit 350, and the electronic receipt providing unit 370 You can manage the flow.
  • FIG. 4 is a flowchart illustrating a process of providing an electronic receipt performed by the processor in FIG. 2.
  • the processor 210 approves payment details and payment information including at least a user's purchase amount from the payment terminal 130. Payment related information including payment matching information uniquely issued by the server 150 may be received (step S410).
  • the processor 210 may query the payment approval server 150 for payment matching information to receive user identification information (step S430).
  • the processor 210 may generate an electronic receipt based on the payment details information (step S450).
  • the processor 210 determines whether or not to request an electronic receipt from the payment approval server 150, and when there is no request for an electronic receipt from the payment approval server 150, the generated electronic receipt is connected and stored with the associated electronic receipt, and the electronic receipt The associated person may be transmitted to the user terminal 110 (step S470).
  • FIG. 5 is a diagram illustrating an embodiment of a process of providing an electronic receipt performed through the apparatus for providing an electronic receipt in FIG. 1.
  • a user may request a payment by presenting a payment method for payment of a purchase amount to a seller, and may convey an intention to consent to issuance of an electronic receipt.
  • the payment terminal 130 may request payment approval from the payment approval server 150 for the user's purchase amount and payment method-related information, and the payment approval server 150 may perform payment approval processing.
  • the payment approval server 150 may transmit an approval number for identifying payment approval details to the payment terminal 130 after approving the payment of the purchase amount using the user's payment method.
  • the payment terminal 130 may determine whether or not the user agrees to issue an electronic receipt, and if there is no consent, output a paper receipt and provide it to the user.
  • the payment terminal 130 may process a request for issuing an electronic receipt when the user agrees to issue an electronic receipt. That is, the payment terminal 130 provides electronic receipt providing device 170 with payment details information including at least a user's purchase amount and payment related information including payment matching information uniquely issued by the payment approval server 150 It can be forwarded to to process the request for issuance of an electronic receipt.
  • the payment matching information may include a payment approval number.
  • the electronic receipt providing device 170 transmits the payment matching information included in the payment-related information to the payment approval server 150 to perform user verification for issuing an electronic receipt. I can.
  • the payment approval server 150 may check user identification information corresponding to the payment matching information and transmit the user identification information to the electronic receipt providing device 170.
  • the user identification information may include the phone number of the user to whom the electronic receipt is issued.
  • the electronic receipt providing device 170 may generate an electronic receipt based on payment detail information included in the payment related information.
  • the electronic receipt may be generated in the same form as the paper receipt including the user's purchase details.
  • the electronic receipt providing device 170 may provide the generated electronic receipt to the user terminal 110 through the payment approval server 150 or directly to the user terminal 110.
  • the electronic receipt providing device 170 can deliver the electronic receipt to the payment approval server 150 when there is a request for an electronic receipt from the payment approval server 150, and if there is no request, the electronic receipt is connected with an associated electronic receipt. After storing and storing, the electronic receipt related person can be delivered to the user terminal 110.
  • the e-receipt providing device 170 may issue an e-receipt through a chat app, e-mail, messenger, etc. without installing a separate e-receipt application on the user terminal 110.
  • the person associated with the e-receipt may include address information stored in the e-receipt.
  • the electronic receipt providing device 170 may also allow the electronic receipt to be provided to the user terminal 110 through applications such as Toss and Bill Letter.
  • the electronic receipt providing device 170 may provide the electronic receipt according to a provision method designated by the user.
  • the user terminal 110 selects an e-receipt related person delivered through a push notification of a chat app, e-mail, messenger, etc.
  • the e-receipt connected to the e-receipt can be searched and stored.
  • FIG. 6 is an exemplary screen showing the form of an electronic receipt provided to the user terminal in FIG. 1.
  • the user terminal 110 may receive a short message including an e-receipt related person from the electronic receipt providing device 170 and display the received short message on the screen 610.
  • a guide phrase 620 for an electronic receipt is displayed, and the electronic receipt guide phrase 620 includes an electronic device connected to the electronic receipt.
  • Receipt related person 630 may be displayed.
  • the person associated with the e-receipt may correspond to a hyperlink, which is address information indicating the storage location of the e-receipt.
  • the user terminal 110 can receive the electronic receipt from the electronic receipt providing device 170, and the details are as shown in (b) of FIG.
  • the included electronic receipt 640 may be displayed.
  • the electronic receipt 640 displayed on the screen 610 of the user terminal 110 includes the member store's representative name, contact information, business number, address, payment date and time, product name, unit price, quantity, amount, taxable goods price, additional amount, and total. Details such as amount and refund amount may be included.
  • FIGS. 7A and 7B an electronic receipt providing system according to various embodiments will be described with reference to FIGS. 7A and 7B.
  • a case of issuing an electronic receipt from a payment approval server will be described with reference to FIG. 7A
  • a case of issuing an electronic receipt at will be described with reference to FIG. 7B.
  • FIGS. 7A and 7B are schematic diagrams of a system for providing an electronic receipt according to various embodiments of the present disclosure.
  • the electronic receipt providing system 10 includes a user terminal 710 that provides a user interface for an electronic receipt, a payment terminal provided for payment at at least one affiliated store that sells goods or provides services ( 720), a service providing server 730 that provides payment-related data used to generate an electronic receipt, and a payment authorization that performs payment approval based on the payment data provided from the payment terminal 720, and provides an electronic receipt It includes a server 740.
  • the payment data may include item information, service information, or amount, etc. input or selected in the payment terminal 720 in relation to an item purchased by the user or a service provided to the user.
  • the user terminal 710 is a user interface device for providing an electronic receipt that is owned by a user who has purchased a product or provided a service at at least one affiliated store, and is issued by a user's product purchase or service provision, and is an electronic receipt.
  • An application, a program, a widget, a web browser, or the like may be installed, or a smartphone, tablet, or wearable device that provides a message service (eg, SMS, MMS, etc.) may be included.
  • a service provider for providing electronic receipts, or payment approval companies such as card companies, mobile payment services, and simple payment services, or messengers, linked to the service provider SNS (Social Network service) or portal (portal service) can be served by a third party (3 rd party) as such, this is not limited, and various service providers or services by a combination of these to provide an electronic receipt Can be.
  • SNS Social Network service
  • portal portal service
  • the user terminal 710 is a payment approval server 740 of a payment approval company such as a service providing server 730 of a service provider, a card company server, a mobile payment server, a simple payment server, etc. through a corresponding application, program, widget, or web browser.
  • a third party server (not shown) of a third party such as a messenger server, an SNS server, or a portal service server.
  • the user terminal 710 provides an interface screen for consenting or disagreeing with the issuance of an electronic receipt, and through the interface screen, data of consent/not consent to issue an electronic receipt indicating consent or disagreement for issuance of an electronic receipt may be obtained. .
  • the user terminal 710 may transmit the obtained electronic receipt issuance consent/non-consent data to the payment approval server 740 or a third party server.
  • the user terminal 710 may display an interface screen for inputting consent/non-consent to electronic receipt issuance data indicating consent or non-agreement to issuance of an electronic receipt.
  • the user terminal 710 may transmit the input data of the consent/not consent for issuance of the electronic receipt to the payment approval server 740 or a third party server.
  • the user terminal 710 When payment is approved by the payment approval server 740 and the user agrees to issue an electronic receipt, the user terminal 710 receives an electronic receipt related to payment approval from the payment approval server 740, and receives the received electronic receipt. It is possible to provide a display interface screen.
  • the interface screens may be interface screens provided through the above-described application, program, widget, or web browser.
  • the user terminal 710 may receive a short message including an electronic receipt, a multimedia message, a messenger message, an SNS message or a portal service message, and may provide an interface screen indicating the received message.
  • an electronic receipt may be a part of a web page obtained through an image or a URL, and a multimedia message, a messenger message, an SNS message, an app push alarm, and an app alarm including the electronic receipt image or web page or their URL.
  • An app message or a portal service message may be received.
  • the user terminal 710 may receive a text message, a multimedia message, a messenger message, an SNS message, or a portal service message including address data related to an electronic receipt, and provide an interface screen indicating the received message. have.
  • the payment terminal 720 may be a POS terminal provided for payment at at least one affiliate store that sells goods or provides services, but is not limited thereto, and cash payment, card payment, simple payment or mobile payment, etc. It may be a computing device capable of performing payment using a payment method presented by a user of.
  • the payment terminal 720 transmits a payment approval request according to the user's payment data to the payment approval server 740, and when payment approval from the payment approval server 740 is completed, includes payment matching data, indicating that payment approval is completed. Indicative payment approval response may be received.
  • the payment matching data may be, for example, a card authorization number when the payment authorization server 740 is a card company, but is not limited thereto, and is the business registration number and payment time of the affiliate store where payment was made, or the phone number of the affiliate store and May include payment time.
  • the payment terminal 720 may transmit payment-related data including payment matching data and payment detail data used for issuing an electronic receipt to the service providing server 730.
  • the payment detail data may include at least some of the payment date, product name, amount, quantity, product type, affiliate store name, affiliate store identification number, affiliate store address, affiliate store contact information, payment method, and the like.
  • the payment terminal 720 may further include a conversion module for converting payment-related data into data in a common format.
  • a conversion module for converting payment-related data into data in a common format.
  • the payment terminal 720 may convert payment-related data of different data formats into a common data format through the conversion module, and transfer payment-related data in a common data format to the service providing server 730.
  • the conversion module may be provided in the service providing server 730 to convert and store payment-related data including payment detail data received from the payment terminal into a common data format.
  • the service providing server 730 may include a general-purpose computer, a laptop, a cloud server, etc. that calculate various data for providing payment-related data used to generate an electronic receipt.
  • the service providing server 730 may receive and store payment related data from the payment terminal 720.
  • the payment-related data may be data converted into a common data format by the payment terminal 720.
  • the service providing server 730 further includes a conversion module for converting payment-related data in various data formats into a common data format, and includes received payment details data when payment-related data in various data formats is received. Payment-related data can be converted and stored in a common data format.
  • the service providing server 730 may transmit payment matching data used for issuing (or generating) an electronic receipt to the payment approval server 740 according to the request of the payment approval server 740.
  • the payment matching data may be at least one of a'payment approval number','affiliate unique number and payment date', and'affiliate contact information and payment date' used to identify a payment approved user.
  • the payment authorization number may be a card authorization number of a card company, an authorization key used to share detailed product details in a mobile payment service or a simple payment service.
  • the affiliate store identification number may be a business registration number. The payment authorization number may be used solely for user identification, but other affiliated store identification numbers and payment date and time or affiliated store contact information and payment date and time may be used for user identification through a combination.
  • the service providing server 730 may transmit payment-related data received from the payment terminal 720 to the payment approval server 740.
  • the payment approval server 740 may include a general-purpose computer, a laptop, a cloud server, etc. that perform payment approval for the user's payment data and calculate various data for issuing an electronic receipt.
  • the payment approval server 740 includes, but is not limited to, a card company server, a mobile payment server, or a simple payment server, and a VAN (Value Added Network) company server or a PG (Payment Gateway) company for electronic payment. And the like may be further included.
  • the payment approval server 740 completes the payment approval and transmits payment approval completion data indicating that the payment approval is completed. 720).
  • the payment approval completion data may include payment matching data.
  • the payment approval server 740 may receive payment matching data from the service providing server 730 and determine whether to issue an electronic receipt by the user based on the received payment matching data.
  • the payment approval server 740 checks the user identification data corresponding to the payment matching data, and whether the user agrees to issue an electronic receipt according to the previously stored electronic receipt issuance consent/non-consent data corresponding to the confirmed user identification data. Can be determined. To this end, the payment approval server 740 may store user identification data previously stored for each of the plurality of users and data of consent/not consent for issuance of an electronic receipt corresponding to each user identification data. Electronic receipt issuance consent/non-consent data corresponding to the user identification data may be received from the user terminal 710.
  • the payment approval server 740 requests payment details data to the service providing server 730, and when payment details data is received from the service providing server 730, the payment details data is used to electronically After generating the receipt, the generated electronic receipt may be delivered to the user device 710.
  • the payment approval server 740 may delete the payment matching data.
  • the payment approval server 740 may receive payment-related data from the service providing server 730 and determine whether to issue an electronic receipt by the user based on payment matching data among payment-related data.
  • the payment approval server 740 checks the user identification data corresponding to the payment matching data, and whether the user agrees to issue an electronic receipt according to the previously stored electronic receipt issuance consent/non-consent data corresponding to the confirmed user identification data. Can be determined.
  • the payment approval server 740 may generate an electronic receipt using payment detail data among payment-related data, and then transmit the generated electronic receipt to the user device 710.
  • the electronic receipt providing system 10 includes a user terminal 710 that provides a user interface for an electronic receipt, a payment terminal provided for payment at at least one affiliated store that sells goods or provides services ( 720), a service providing server 730 that provides payment-related data used to generate an electronic receipt, a payment approval server 740 that performs payment approval based on payment data provided from the payment terminal 720, and a communication company It includes a server 750.
  • the user terminal 710 may be a user interface device owned by a user who has purchased an item or provided a service at at least one affiliated store, and provides an electronic receipt issued by the user's purchase of an item or provision of a service.
  • the user terminal 710 may perform at least the same operation as the user terminal 710 described above with reference to FIG. 7A.
  • the user terminal 710 may obtain data of consent/not consent for issuance of electronic receipts, and transmit the data of consent/not consent for issuance of electronic receipts to the communication company server 750.
  • the user terminal 710 When payment is approved by the payment approval server 740 and the user agrees to issue an electronic receipt, the user terminal 710 receives an electronic receipt related to payment approval from the communication company server 750, and indicates the received electronic receipt. Interface screen can be provided.
  • the payment terminal 720 is a POS terminal provided for payment at at least one affiliate store that sells goods or provides services, or a payment method presented by the user such as cash payment, card payment, simple payment or mobile payment. It may be a computing device capable of performing payment using.
  • the payment terminal 720 may perform at least the same operation as the payment terminal 720 described above with reference to FIG. 7A.
  • the payment terminal 720 transmits a payment approval request according to the user's payment data to the payment approval server 740, and when payment approval from the payment approval server 740 is completed, includes payment matching data, indicating that payment approval is completed. Indicative payment approval response may be received.
  • the payment terminal 720 may transmit payment-related data including payment matching data and payment detail data used for issuing an electronic receipt to the service providing server 730.
  • the service providing server 730 may include a general-purpose computer, a laptop, a cloud server, etc. that calculate various data for providing payment-related data used to generate an electronic receipt.
  • the service providing server 730 may perform at least the same operation as the service providing server 730 described above with reference to FIG. 7A.
  • the service providing server 730 may receive and store payment related data from the payment terminal 720.
  • the service providing server 730 may transmit payment matching data among payment related data to the payment approval server 740 or may transmit payment matching data (eg, second payment matching data) to the communication company server 750.
  • the service providing server 730 may transmit payment details data to the payment approval server 740 or the communication company server 750 according to the request of the payment approval server 740 or the communication company server 750.
  • the service providing server 730 may transmit the payment-related data received from the payment terminal 720 to the payment approval server 740 or the communication company server 750. have.
  • the payment approval server 740 may include a general-purpose computer, a laptop, a cloud server, etc. that perform payment approval for the user's payment data and calculate various data for issuing an electronic receipt.
  • the payment approval server 740 may perform at least the same operation as the payment approval server 740 described above with reference to FIG. 7A.
  • the payment approval server 740 When approval for payment information according to the user's product payment or service provision is requested from the payment terminal 720, the payment approval server 740 completes the payment approval and transmits information indicating that the payment approval is completed to the payment terminal 720. I can deliver.
  • the payment approval server 740 may receive payment matching data from the service providing server 730 and determine whether to issue an electronic receipt by the user based on the received payment matching data. An operation of determining whether to issue an electronic receipt based on payment matching data may be the same as the operation described above in FIG. 7A.
  • the payment approval server 740 may transmit user identification data of the user who has agreed to issue the electronic receipt to the payment approval server 740.
  • the payment approval server 740 may delete the payment matching data.
  • the payment approval server 740 may receive payment-related data from the service providing server 730 and determine whether to issue an electronic receipt by the user based on payment matching data among payment-related data.
  • the payment approval server 740 may transmit the user identification data of the user who has agreed to issue the electronic receipt to the communication company server 750, as described above, depending on whether or not the electronic receipt is issued, at this time, the payment detail data together with the communication company server 750 Can be delivered to.
  • the payment approval server 740 may transmit payment matching data (eg, first payment matching data) and user identification data used to determine whether to issue an electronic receipt by the user to the communication company server 750.
  • payment matching data eg, first payment matching data
  • user identification data used to determine whether to issue an electronic receipt by the user to the communication company server 750.
  • the payment approval server 740 may transmit at least one of payment matching data and user identification data to the communication company server 750 in the form of a message such as a short message or a multimedia message.
  • payment matching data may be included in the full text of the message.
  • the communication company server 750 provides a communication service, and includes a general-purpose computer, a laptop, a cloud server, etc. that calculate various data for issuing an electronic receipt to the user terminal 710 of a user subscribed to the communication service. I can.
  • the communication company server 750 When payment is approved by the payment approval server 740 and user identification data of a user who has agreed to issue an electronic receipt from the payment approval server 740 is received, the communication company server 750 sends the payment details data to the service providing server 730 Can be requested. In order to request payment details data, the communication company server 750 may transmit user identification data to the service providing server 730.
  • the communication company server 750 may generate an electronic receipt using the received payment details data and transmit the generated electronic receipt to the user terminal 710.
  • the communication company server 750 when payment is approved by the payment approval server 740, the communication company server 750 receives the first payment matching data and user identification data from the payment approval server 740, and provides the first payment matching data and user identification data from the service providing server 730. 2 Can receive payment matching data.
  • the communication company server 750 may determine whether the first and second payment matching data match, and if the first and second payment matching data match, determine whether to issue an electronic receipt based on the user identification data.
  • the communication company server 750 may delete the received first and second payment matching data and user identification data.
  • the communication company server 750 may check the data of consent/not consent to issuing an electronic receipt previously stored based on user identification data. To this end, the communication service provider server 750 may store consent/non-consent data for issuing an electronic receipt in response to user identification data of a plurality of users subscribed to the service provider.
  • the communication company server 750 may request payment details data from the service providing server 730. In order to request payment details data, the communication company server 750 may transmit user identification data. When the payment details data is received, the communication company server 750 may generate an electronic receipt using the received payment details data, and transmit the generated electronic receipt to the user terminal 710.
  • the communication company server 750 may delete the first and second payment matching data and the user identification data.
  • the communication company server 750 when payment is approved by the payment approval server 740, the communication company server 750 receives the first payment matching data and user identification data from the payment approval server 740, and provides the first payment matching data and user identification data from the service providing server 730. 2 Can receive payment matching data and payment details data.
  • the communication company server 750 may determine whether the first and second payment matching data match, and if the first and second payment matching data match, determine whether to issue an electronic receipt based on the user identification data.
  • the operation for determining whether to issue an electronic receipt may be the same as the operation of the communication company server 750 described above.
  • the communication company server 750 may generate an electronic receipt using payment details data, and transmit the generated electronic receipt to the user terminal 710.
  • the communication company server 750 may delete the first and second payment matching data, user identification data, and payment details data.
  • the communication company server 750 may receive at least one of payment matching data and user identification data from the payment approval server 740 in the form of a message such as a short message or a multimedia message.
  • the communication company server 750 may generate an electronic receipt using the received payment matching data and/or user identification data, and transmit the generated electronic receipt to the user device 710 in the form of a short message or an app push.
  • the electronic receipt provided in this form may replace the payment approval notification message previously provided in the form of a short message from the telecommunication company server to notify the payment approval upon payment approval.
  • the present invention can provide an electronic receipt without requiring separate information from the user to issue an electronic receipt, so that the user can easily and conveniently receive the electronic receipt.
  • FIG. 8 is a schematic diagram illustrating a user terminal according to an embodiment of the present invention.
  • the user terminal 800 may include a communication unit 810, a display unit 820, a storage unit 830, and a control unit 840.
  • the communication unit 810 connects the user terminal 800 to enable communication with an external device.
  • the communication unit 810 may be connected to the payment approval server 740 through wired/wireless communication to transmit and receive various data. Specifically, the communication unit 810 may transmit user identification data and data of consent/not consent to issue an electronic receipt to the payment approval server 740 or the communication company server 750.
  • the communication unit 810 may receive an electronic receipt from the payment approval server 740 or the communication company server 750.
  • the display unit 820 may display various types of content (eg, text, images, videos, icons, banners, symbols, etc.) to the user. Specifically, the display unit 820 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 company, or a third party.
  • the display unit 820 may include a touch screen, for example, a touch, gesture, proximity, drag, and swipe using an electronic pen or a part of the user's body. (swipe) or hovering (hovering) input, etc. can be received.
  • a touch screen for example, a touch, gesture, proximity, drag, and swipe using an electronic pen or a part of the user's body. (swipe) or hovering (hovering) input, etc. can be received.
  • the storage unit 830 may store various data used to provide an electronic receipt.
  • the storage unit 830 stores user identification data acquired by a user through a user interface, stores an electronic receipt received from the payment approval server 740 or the communication company server 750, or stores an electronic receipt.
  • the storage unit 830 may store various graphic objects used to configure an interface screen.
  • the storage unit 830 is 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 magnetic memory, a magnetic disk, and an optical disk.
  • the user terminal 800 may operate in connection with a web storage that performs a storage function of the storage unit 830 over the Internet.
  • the control unit 840 is operably connected to the communication unit 810, the display unit 820, and the storage unit 830, and may execute various commands for providing an electronic receipt.
  • control unit 840 displays an interface screen for acquiring user identification data or data of consent/not consent to issue an electronic receipt through the display unit 820, and consent to issuance of user identification data or electronic receipt obtained through the interface screen. /Unconfirmed data may be transferred to the payment approval server 740 or the communication company server 750.
  • control unit 840 When payment is approved by the payment approval server 740 and the user agrees to issue an electronic receipt, the control unit 840 receives an electronic receipt from the payment approval server 740 or the communication company server 750, and the received electronic receipt You can display an interface screen indicating
  • control unit 840 transmits a short message including an electronic receipt, a multimedia message, a messenger message, an app push, an app message, an SNS message, or a portal service message from the payment approval server 740 or the communication company server 750. It is also possible to receive and provide an interface screen indicating the received message.
  • control unit 840 receives a text message, a multimedia message, a messenger message, an SNS message, or a portal service message including address data related to an electronic receipt from the payment approval server 740 or the communication company server 750 , An interface screen indicating the received message may be provided.
  • FIG. 9 is a schematic diagram illustrating a service providing server according to an embodiment of the present invention.
  • the service providing server 900 may include a communication unit 910, a storage unit 920, and a control unit 930.
  • the communication unit 910 connects the service providing server 900 to enable communication with an external device.
  • the communication unit 910 may be connected to the payment terminal 720 and the payment approval server 740 to transmit and receive various data. Specifically, the communication unit 910 receives payment-related data from the payment terminal 720, and transmits any one of payment matching data, payment detail data, and payment-related data to the payment approval server 740 or the communication company server 750. I can.
  • the storage unit 920 may store various data for providing payment related data.
  • the storage unit 920 may store payment related data received from the payment terminal 720.
  • the storage unit 920 is 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 of.
  • the service providing server 900 may operate in connection with a web storage that performs a storage function of the storage unit 920 on the Internet.
  • the control unit 930 is operatively connected to the communication unit 910 and the storage unit 920 and may perform various commands for providing payment related data.
  • the controller 930 may receive payment-related data from the payment terminal 720 and store the received payment-related data in the storage unit 920.
  • the control unit 930 transmits the payment matching data to the payment approval server 740 or the communication company server 750, and transmits payment related data to the payment approval server 740 at the request of the payment approval server 740 or the communication company server 750. ) Or it can be delivered to the communication company server 750.
  • the controller 930 may transmit payment-related data to the payment approval server 740 or the communication company server 750.
  • FIG. 10 is a schematic diagram illustrating a payment approval server according to an embodiment of the present invention.
  • the payment approval server 1000 may include a communication unit 1010, a storage unit 1020, and a control unit 1030.
  • the communication unit 1010 connects the payment approval server 1000 to enable communication with an external device.
  • the communication unit 1010 may be connected to the user terminal 710, the payment terminal 720, and the service providing server 730 to transmit and receive various data.
  • the communication unit 1010 may be further connected to the communication company server 750.
  • the communication unit 1010 may receive payment data from the payment terminal 720 and transmit payment approval completion data to the payment terminal 720.
  • the communication unit 1010 may receive user identification data and consent/non-consent data for issuing an electronic receipt from the user terminal 710.
  • the communication unit 1010 may receive any one of payment matching data, payment detail data, and payment-related data from the service providing server 730, and transmit an electronic receipt to the user terminal 710. In various embodiments, the communication unit 1010 may transmit a request for payment detail data to the service providing server 730.
  • the communication unit 1010 may transmit payment matching data to the communication company server 750, or may transmit first payment matching data and user identification data to the communication company server 750.
  • the storage unit 1020 may store various data for performing payment approval according to a request of the payment terminal 720 and issuing an electronic receipt upon completion of the payment approval.
  • the storage unit 1020 may store payment matching data generated when payment is approved, user identification data of a plurality of users, and data of consent/not consent to issuance of an electronic receipt set in correspondence with each user identification data.
  • the storage unit 1020 is 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 of.
  • the payment approval server 1000 may operate in connection with web storage that performs a storage function of the storage unit 1020 on the Internet.
  • the control unit 1030 is operably connected to the communication unit 1010 and the storage unit 1020, and may perform various commands for approving payment and issuing an electronic receipt.
  • the controller 1030 may perform payment approval for payment data received from the payment terminal 720 and transmit payment approval completion data including payment matching data to the payment terminal 720.
  • the control unit 1030 receives payment matching data from the service providing server 730, checks pre-stored user identification data corresponding to the received payment matching data, and agrees to issue a pre-stored electronic receipt in response to the confirmed user identification data. You can decide whether to issue an e-receipt based on the unconsent data.
  • the controller 1030 may request payment details data from the service providing server 730 and receive payment details data from the service providing server 730.
  • the controller 1030 may generate an electronic receipt using the received payment details data, and transmit the generated electronic receipt to the user terminal 710.
  • control unit 1030 may delete the payment matching data received from the service providing server 730.
  • the controller 1030 may receive payment related data from the service providing server 730.
  • the control unit 1030 checks pre-stored user identification data in response to payment matching data among payment-related data, and issues an electronic receipt based on the previously stored electronic receipt issuance consent/non-consent data in response to the confirmed user identification data. You can decide whether or not.
  • control unit 1030 may generate an electronic receipt using payment detail data among payment-related data, and transmit the generated electronic receipt to the user terminal 710.
  • the controller 1030 determines whether to issue an electronic receipt based on the payment matching data received from the service providing server 730, and the user issues the electronic receipt. If agreed, the user identification data may be transmitted to the communication company server 750, or user identification data and payment details data may be transmitted to the communication company server 750.
  • FIG. 11 is a schematic diagram illustrating a communication service provider server according to an embodiment of the present invention.
  • the communication company server 1100 may include a communication unit 1110, a storage unit 1120, and a control unit 1130.
  • the communication unit 1110 connects the communication company server 1100 to enable communication with an external device.
  • the communication unit 1110 may be connected to the user terminal 710, the payment terminal 720, the service providing server 730, and the payment approval server 740 to transmit and receive various data.
  • the communication unit 1110 may receive user identification data from the payment approval server 740, request payment details data from the service providing server 730, and receive payment details data from the service providing server 730. have.
  • the communication unit 1110 may receive first payment approval data and user identification data from the payment approval server 740, and receive second payment approval data from the service providing server 730.
  • the communication unit 1110 may receive second payment approval data and payment detail data from the service providing server 730.
  • the communication unit 1110 may receive user identification data and data of consent/not consent for issuance of an electronic receipt from the user terminal 710 and transmit the electronic receipt to the user terminal 710.
  • the storage unit 1120 may store various data for issuing an electronic receipt upon completion of payment approval.
  • the storage unit 1120 may store user identification data of a plurality of users who have subscribed to a communication service provider, and data of consent/not consent to issuance of an electronic receipt set in correspondence with each user identification data.
  • the storage unit 1120 is 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 of.
  • the communication service provider server 1100 may operate in connection with a web storage that performs a storage function of the storage unit 1120 on the Internet.
  • the control unit 1130 is operably connected to the communication unit 1110 and the storage unit 1120 and may execute various commands for issuing an electronic receipt.
  • the control unit 1130 receives the user identification data from the payment approval server 740. You can receive it.
  • the controller 1130 may request payment detail data from the service providing server 730 to issue an electronic receipt. In order to request payment details data, the controller 1130 may transmit user identification data to the service providing server 730.
  • control unit 1130 may generate an electronic receipt using the received payment details data and transmit the generated electronic receipt to the user device 710.
  • the controller 1130 may use user identification data to deliver the electronic receipt to the user device 710.
  • the controller 1130 may receive user identification data and payment detail data from the payment approval server 740.
  • the controller 1130 may generate an electronic receipt using the received payment detail data, and transmit the generated electronic receipt to the user terminal 710 corresponding to the user identification data.
  • control unit 1130 may receive first payment matching data and user identification data from the payment approval server 740, and receive second payment matching data from the service providing server 730. have.
  • the controller 1130 may determine whether to issue an electronic receipt by the user based on the user identification data according to whether the first and second payment matching data match. Specifically, if the first and second payment data match, the control unit 1130 checks the data of consent/not consent for issuance of the electronic receipt in response to the user identification data, and based on the data of consent/not consent for issuance of the electronic receipt. Thus, you can decide whether to issue an electronic receipt.
  • the controller 1130 When the user agrees to issue an electronic receipt, the controller 1130 requests payment details data to the service providing server 730, and when the payment details data is received from the service providing server 730, the electronic receipt is sent using the payment details data. After generating, the generated electronic receipt may be delivered to the user terminal 710.
  • the controller 1130 may delete the first and second payment matching data and user identification data.
  • control unit 1130 receives the first payment matching data and user identification data from the payment approval server 740, and the second payment matching data and payment details data from the service providing server 730 Can be received.
  • the controller 1130 may determine whether to issue an electronic receipt by the user based on the user identification data according to whether the first and second payment matching data match. Specifically, if the first and second payment data match, the control unit 1130 checks the data of consent/not consent for issuance of the electronic receipt in response to the user identification data, and based on the data of consent/not consent for issuance of the electronic receipt. Thus, you can decide whether to issue an electronic receipt.
  • the controller 1130 When the user agrees to issue an electronic receipt, the controller 1130 requests payment details data to the service providing server 730, and when the payment details data is received from the service providing server 730, the electronic receipt is sent using the payment details data. After generating, the generated electronic receipt may be delivered to the user terminal 710.
  • the controller 1130 may delete the first and second payment matching data and user identification data.
  • the present invention does not require separate user identification information from the user for issuing an electronic receipt by confirming the user's consent/non-consent to the issuance of an electronic receipt using the user identification information. Users can easily and conveniently obtain electronic receipts.
  • FIG. 12 is a flowchart illustrating a method of providing an electronic receipt in a payment approval server according to an embodiment of the present invention.
  • the payment approval server 740 performs payment approval for the user's payment data received from the payment terminal 720 (S1200 ).
  • the payment approval server 740 may transmit payment matching data generated according to payment approval to the payment terminal 720.
  • the payment approval server 740 receives payment matching data used for user identification or electronic receipt issuance confirmation from the service providing server 730 (S1210).
  • the payment approval server 740 determines issuance of an electronic receipt to the user based on the payment matching data (S1220). Specifically, the payment approval server 740 may check pre-stored user identification data corresponding to the payment matching data, and determine whether to issue an electronic receipt in response to the confirmed user identification data.
  • the payment approval server 740 requests payment details data from the service providing server 730 (S1230), and receives payment details data from the service providing server 730 (S1240).
  • the payment approval server 740 generates an electronic receipt using the received payment detail data and then transmits the generated electronic receipt to the user device 710 (S1250).
  • FIG. 13 is a flowchart illustrating a method of providing an electronic receipt in a communication service provider server according to an embodiment of the present invention.
  • the telecommunication company server 750 is the first payment generated according to payment approval from the payment approval server 740 Matching data and user identification data are received (S1305).
  • the communication company server 750 receives the second payment matching data used for issuing an electronic receipt from the service providing server 730 (S1310), determines whether the first and second payment matching data match (S1320), In response to the user identification data, the previously stored electronic receipt issuance consent or non-consent data is checked (S1325). If the first and second payment matching data do not match, the communication company server 750 deletes the first and second payment matching data and user identification data (S1330).
  • the communication company server 750 determines whether an electronic receipt is issued or not issued to the user (S1335), and in the case of issuing an electronic receipt, requests payment details data to the service providing server 730 (S1340), and from the service providing server 730 When payment details data is received, an electronic receipt is generated using the received payment details data and then transmitted to the user device 710 (S1345).
  • the communication company server 750 deletes the first and second payment matching data and user identification data (S1350).
  • FIG. 14 is a flowchart illustrating a method of providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention.
  • the payment approval server 740 provides an electronic receipt will be described.
  • the payment terminal 720 transmits a payment approval request to the payment approval server 740 (S1400), and the payment approval server 740 processes payment approval according to the payment approval request (S1405), Payment matching data is generated (S1410).
  • the payment approval server 740 transmits a payment approval response to the payment terminal 720 (S1415).
  • the payment approval response may include payment matching data.
  • the payment terminal 720 transmits payment-related data to the service providing server 730 (S1420), and the service providing server 730 transmits the payment-related data to the payment approval server 740 (S1425). ).
  • the payment approval server 740 determines issuance of an electronic receipt by the user based on payment matching data among payment-related data (S1430), and generates an electronic receipt by using payment detail data among payment-related data (S1435).
  • the payment approval server 740 transmits the generated electronic receipt to the user terminal 710 (S1440).
  • 15 is a flowchart illustrating a method of providing an electronic receipt in an electronic receipt providing system according to an embodiment of the present invention.
  • a case where an electronic receipt is provided by the communication company server 750 is described.
  • the payment terminal 720 transmits a payment approval request to the payment approval server 740 (S1500), and the payment approval server 740 processes payment approval according to the payment approval request (S1505), First payment matching data is generated (S1510).
  • the payment approval server 740 transmits a payment approval response to the payment terminal 720 (S1515).
  • the payment approval response may include first payment matching data.
  • the payment approval server 740 transmits the first payment matching data and user identification data to the communication company server 750 (S1520), and the payment terminal 720 transmits the second payment matching data and payment details data. It is transmitted to the service providing server 730 (S1525), and the service providing server 730 transmits the second payment matching data and payment details data to the communication company server 750 (S1530).
  • the communication company server 750 determines issuance of the user's electronic receipt based on the first and second payment matching data (S1535), and generates an electronic receipt using the payment detail data (S1540).
  • the communication company server 750 determines whether the first and second payment matching data match, and if they match, checks the previously stored electronic receipt issuance consent/non-consent data in response to the user identification data, and consents to the issuance of the confirmed electronic receipt. / Can decide whether to issue an electronic receipt based on the unconsent data.
  • the communication service provider server 750 may delete the first and second payment matching data and payment detail data.
  • the communication company server 750 When the issuance of the electronic receipt is determined, the communication company server 750 generates an electronic receipt using the payment details data, and when it is determined that the electronic receipt is not issued, the first and second payment matching data and the payment detail data may be deleted.
  • the communication company server 750 delivers the generated electronic receipt to the user terminal 710 (S1545).
  • the present invention does not require separate user identification information from the user in order to issue an electronic receipt, and provides an electronic receipt, so that the user can easily and conveniently receive the electronic receipt.
  • the apparatus and method according to an embodiment of the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium.
  • the computer-readable medium may include program instructions, data files, data structures, and the like alone or in combination.
  • Program instructions recorded on a computer-readable medium may be specially designed and configured for the present invention, or may be known and usable to 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 and DVDs, and magnetic media such as floptical disks.
  • Examples of program instructions include not only machine language codes such as those produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like.
  • the above-described hardware device may be configured to operate as one or more software modules to perform the operation of the present invention, and vice versa.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Security & Cryptography (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Cash Registers Or Receiving Machines (AREA)

Abstract

La présente invention concerne, selon un mode de réalisation, un dispositif et un procédé de fourniture de reçu électronique. Un dispositif de fourniture de reçu électronique selon un mode de réalisation de la présente invention comprend : une unité de communication configurée pour émettre ou recevoir des données ; et une unité de commande connectée fonctionnellement à l'unité de communication, l'unité de commande étant configurée pour : délivrer une autorisation de paiement concernant des données de paiement provenant d'un terminal de paiement par l'intermédiaire de l'unité de communication ; recevoir des données de correspondance de paiement utilisées pour vérifier s'il existe un accord de l'utilisateur concernant l'émission de reçus électroniques, en provenance d'un serveur de fourniture de service par l'intermédiaire de l'unité de communication ; décider de délivrer un reçu électronique à l'utilisateur sur la base des données de correspondance de paiement ; demander au serveur de fourniture de service des données d'historique de paiement utilisées pour émettre le reçu électronique ; lorsque les données d'historique de paiement sont reçues en provenance du serveur de fourniture de service, générer le reçu électronique à l'aide des données d'historique de paiement reçues ; et transférer le reçu électronique généré à un terminal utilisateur.
PCT/KR2020/012274 2019-09-11 2020-09-11 Dispositif et procédé de fourniture de reçu électronique WO2021049897A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2019-0112745 2019-09-11
KR20190112745 2019-09-11
KR1020200116368A KR20210031410A (ko) 2019-09-11 2020-09-10 전자영수증 제공 장치 및 방법
KR10-2020-0116368 2020-09-10

Publications (1)

Publication Number Publication Date
WO2021049897A1 true WO2021049897A1 (fr) 2021-03-18

Family

ID=74866749

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/012274 WO2021049897A1 (fr) 2019-09-11 2020-09-11 Dispositif et procédé de fourniture de reçu électronique

Country Status (1)

Country Link
WO (1) WO2021049897A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20150049299A (ko) * 2013-10-30 2015-05-08 삼성에스디에스 주식회사 전자영수증 관리 장치 및 방법
KR101538745B1 (ko) * 2015-01-02 2015-07-24 디에이치이노시스 주식회사 전자영수증 발행 시스템
JP2015232826A (ja) * 2014-06-10 2015-12-24 東芝テック株式会社 情報処理装置、携帯端末装置およびプログラム
KR20180045486A (ko) * 2016-10-26 2018-05-04 주식회사 이엔티 전자 영수증 발급 방법 및 이의 시스템
KR20190021811A (ko) * 2017-08-24 2019-03-06 주식회사 케이티 전자영수증 발행 방법, 장치 및 시스템

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20150049299A (ko) * 2013-10-30 2015-05-08 삼성에스디에스 주식회사 전자영수증 관리 장치 및 방법
JP2015232826A (ja) * 2014-06-10 2015-12-24 東芝テック株式会社 情報処理装置、携帯端末装置およびプログラム
KR101538745B1 (ko) * 2015-01-02 2015-07-24 디에이치이노시스 주식회사 전자영수증 발행 시스템
KR20180045486A (ko) * 2016-10-26 2018-05-04 주식회사 이엔티 전자 영수증 발급 방법 및 이의 시스템
KR20190021811A (ko) * 2017-08-24 2019-03-06 주식회사 케이티 전자영수증 발행 방법, 장치 및 시스템

Similar Documents

Publication Publication Date Title
WO2015111950A1 (fr) Procédé d'intermédiation de messages, procédé de traitement de messages, procédé de gestion de service et dispositif de mise en œuvre ceux-ci
WO2014030959A1 (fr) Procédé pour fournir des informations, terminal mobile et dispositif d'affichage correspondants
WO2014025186A1 (fr) Procédé de fourniture de fonction de messagerie et dispositif électronique associé
WO2014030876A1 (fr) Procédé et appareil pour déterminer un objet approprié sur la base d'un environnement d'interaction
WO2017135777A1 (fr) Dispositif électronique mobile et procédé de paiement électronique
WO2014046440A1 (fr) Dispositif terminal utilisateur et appareil de serveur de réseau pour la fourniture d'informations d'évaluation et de procédés associés
WO2018166091A1 (fr) Procédé, système et terminal de signature de prêt en face à face, et support d'enregistrement lisible par ordinateur
WO2017039341A1 (fr) Dispositif d'affichage et procédé de commande correspondant
WO2018155846A1 (fr) Système de paiement d'agence, serveur et son procédé de commande
WO2017204507A1 (fr) Appareil électronique et son procédé de commande
WO2019104876A1 (fr) Procédé et système de poussée de produit d'assurance, terminal, terminal client et support d'informations
WO2016199994A1 (fr) Dispositif et procédé de fourniture de service de livraison préalable d'un produit d'intérêt au moyen d'une boîte de courrier sans opérateur, et support d'enregistrement sur lequel est enregistré un programme informatique
WO2021025387A1 (fr) Procédé de commerce électronique capable de commande intégrée et de distribution intégrée, et serveur associé
WO2015122601A1 (fr) Terminal, appareil de fourniture de service, et serveur de coupons, système de porte-monnaie électronique doté de ce dernier, son procédé de commande, et support d'enregistrement sur lequel un programme informatique est enregistré
WO2022060149A1 (fr) Dispositif électronique de gestion de droit à l'aide d'un réseau décentralisé et son procédé de fonctionnement
WO2017069503A1 (fr) Appareil électronique et son procédé de commande
WO2021049897A1 (fr) Dispositif et procédé de fourniture de reçu électronique
WO2012064026A2 (fr) Procédé permettant de délivrer un reçu électronique
WO2018030827A1 (fr) Système et procédé d'émission et de gestion d'un bordereau d'expédition sécurisé à l'aide d'informations personnelles virtuelles
WO2017026651A1 (fr) Procédé de commerce électronique
WO2017043847A1 (fr) Système de réduction de frais de gestion et serveur de plateforme interagissant avec un procédé de service de paiement en nuage
WO2018043860A1 (fr) Dispositif de recommandation d'article de location au moyen d'un groupe de propension similaire et procédé d'utilisation associé
WO2018056691A1 (fr) Procédé de demande de négociation en temps réel, dispositif de gestion, et système, utilisant une application mobile
WO2023068417A1 (fr) Dispositif électronique pour fournir des informations d'article, et procédé associé
WO2015147409A1 (fr) Système et procédé d'authentification d'utilisateur lors de l'utilisation d'un service web

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20862605

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 06.05.2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20862605

Country of ref document: EP

Kind code of ref document: A1