Device, method, and recording medium for processing order information

Abstract

According to an embodiment of the present disclosure, a device for processing order information may be proposed. The device according to the present disclosure may be configured to: transmit store information about a target store to a user terminal of a user who visits the target store; receive, from the user terminal, order information about at least one target item, which is ordered at a target table corresponding to the user terminal in the target store, among at least one item; identify a target payment service for paying a payment amount for the at least one target item; and generate order completion information about the at least one target item on the basis of the order information and the target payment service.

Description

Device, method, and recording medium for processing order information

[0001] The present disclosure relates to a technology for processing order information.

[0002] Due to changes in consumers' shopping and dining habits over the past few years, offline stores have an increasing need to provide more efficient and convenient services. Traditional offline stores could cause inconvenience to customers due to long waiting times and cumbersome ordering procedures. Against this backdrop, table ordering systems have been introduced to enhance operational efficiency. Through these systems, customers can select and order from their tables immediately, providing a convenient and fast shopping experience.

[0003] One embodiment of the present disclosure provides a technology for ordering a desired item through a terminal held by a customer visiting a store.

[0004] One embodiment of the present disclosure provides a technology that allows a customer to select a payment service to pay the payment amount of an item when ordering an item.

[0005] One embodiment of the present disclosure provides a technology for synchronizing the order acceptance and payment status of an item ordered at a table in a store between a terminal held by a customer and a terminal provided in the store.

[0006] In one aspect of the present disclosure, an apparatus for processing order information may be proposed. An apparatus according to the present disclosure comprises one or more processors; and one or more memories in which instructions executed by the one or more processors are stored. When the instructions are executed, the one or more processors may be configured to transmit store information for a target store to a user terminal of a user who has visited the target store—the store information includes information for at least one item sold at the target store—receive order information from the user terminal for at least one target item ordered from a target table corresponding to the user terminal within the target store among the at least one item, identify a target payment service for paying the payment amount of the at least one target item, and generate order completion information for the at least one target item based on the order information and the target payment service.

[0007] According to one embodiment, the one or more processors may be configured to receive a request for store information from the user terminal when transmitting the store information to the user terminal—the request for store information includes a connection address for the store information obtained by the user terminal—identify the store information for the target store based on the connection address, and transmit the identified store information to the user terminal.

[0008] According to one embodiment, the access address may be obtained by the user terminal from at least one of an NFC (near field communication) device or a QR code corresponding to the target table of the target store.

[0009] According to one embodiment, the connection address may correspond to the target store among at least one store and the target table among at least one table within the target store.

[0010] According to one embodiment, the store information may include information about the target table.

[0011] According to one embodiment, information regarding the target table may include at least one of the number of user terminals corresponding to the target table or the identifier of the target table.

[0012] According to one embodiment, if the number of user terminals corresponding to the target table is at least two, the information regarding the target table may further include a notification that at least two users are placing an order together at the target table.

[0013] According to one embodiment, the at least one target item may include at least two items selected by users in the target table.

[0014] According to one embodiment, the order completion information for the at least one target item may include at least one of the order history of the at least one target item or a notification that an order for the at least one target item has been received by the target store.

[0015] According to one embodiment, the one or more processors may be configured to transmit the order completion information for the at least one target item to at least one of the user terminal or the store terminal of the target store.

[0016] According to one embodiment, the one or more processors are configured to identify whether the user’s authentication information for a predetermined application is valid with respect to the first payment service when generating order completion information for the at least one target item based on the target payment service, and the first payment service may be a payment service that pays a payment amount for the at least one target item using a payment method registered in association with the user’s account in the application.

[0017] According to one embodiment, the one or more processors may be further configured to identify the first payment service as the target payment service upon identifying that the user's authentication information for the application is valid, and to generate the order completion information for the at least one target item based on the first payment service.

[0018] According to one embodiment, the one or more processors may be further configured to identify whether there is a history of transmitting promotional information indicating the first payment service as a recommended payment service to the user terminal upon identifying that the user’s authentication information for the application is invalid, and the promotional information includes interface information for requesting information about a payment method registered in the application for the first payment service, and to transmit the promotional information to the user terminal upon identifying that there is no history of transmitting the promotional information to the user terminal.

[0019] According to one embodiment, the one or more processors may be further configured to obtain an authentication result of the user for the application based on the user's input information regarding the interface information, and, as the authentication result of the user for the application indicates that the user's authentication is completed, identify the first payment service as the target payment service and, based on the first payment service, generate order completion information for the at least one target item.

[0020] According to one embodiment, the one or more processors may be configured to generate order completion information for the at least one target item based on the first payment service, by transmitting payment request information for the first payment service to a payment server, wherein the payment request information for the first payment service includes information about the at least one target item, information about the payment amount of the at least one target item, or information about a target payment method for paying the payment amount of the at least one target item among at least one payment method registered in the application for the first payment service, and receiving payment approval information for the first payment service from the payment server, wherein the payment approval information for the first payment service includes payment details of the at least one target item according to the first payment service, and generating order completion information for the at least one target item based on the payment approval information for the first payment service.

[0021] According to one embodiment, the one or more processors are configured to generate order completion information for the at least one target item based on the target payment service by identifying the second payment service as the target payment service, and the second payment service may be a payment service that pays the payment amount of the at least one target item using a payment method selected by the user.

[0022] According to one embodiment, the one or more processors may be configured to generate order completion information for the at least one target item based on the second payment service, by receiving payment approval information for the second payment service from a payment server, wherein the payment approval information for the second payment service includes payment details of the at least one target item according to the second payment service, and generating order completion information for the at least one target item based on the payment approval information for the second payment service.

[0023] According to one embodiment, the one or more processors are configured to generate order completion information for the at least one target item based on the target payment service, by identifying a third payment service as the target payment service, and the third payment service may be a payment service that pays the payment amount of the at least one target item at the counter of the target store.

[0024] In one aspect of the present disclosure, a method for processing order information may be proposed. The method according to the present disclosure may be performed by a device comprising one or more processors and one or more memories in which instructions to be executed by said one or more processors are stored. The method according to the present disclosure may include the step of transmitting store information for a target store to a user terminal of a user who has visited said target store, wherein the store information includes information for at least one item sold at said target store; the step of receiving from said user terminal order information for at least one target item ordered from a target table corresponding to said user terminal within said target store among said at least one item; the step of identifying a target payment service for paying the payment amount of said at least one target item; and the step of generating order completion information for said at least one target item based on said order information and said target payment service.

[0025] In one aspect of the present disclosure, a non-transient computer-readable recording medium may be proposed that records instructions for processing order information. The instructions recorded on the non-transient computer-readable recording medium according to the present disclosure are instructions to be executed by one or more processors, and upon execution by the one or more processors, the one or more processors may be configured to transmit store information regarding a target store to a user terminal of a user who has visited the target store—the store information includes information regarding at least one item sold at the target store—receive order information from the user terminal regarding at least one target item ordered from a target table corresponding to the user terminal within the target store among the at least one item, identify a target payment service for paying the payment amount of the at least one target item, and generate order completion information for the at least one target item based on the order information and the target payment service.

[0026] According to one embodiment of the present disclosure, customers can reduce the time required to order items, and stores can reduce the cost of hiring staff to take orders.

[0027] According to one embodiment of the present disclosure, a customer can conveniently pay a payment amount by selecting a payment service suitable for the situation.

[0028] According to one embodiment of the present disclosure, a customer can conveniently check whether an order has been successfully received, and a store can efficiently manage order reception and payment.

[0029] The effects according to the technical concept of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description in the specification.

[0030] FIG. 1 is a drawing showing a system according to one embodiment of the present disclosure.

[0031] FIG. 2 is a diagram illustrating a process for obtaining a connection address for store information of a target store based on an NFC device according to one embodiment of the present disclosure.

[0032] FIG. 3 is a diagram illustrating a process for obtaining an access address for store information of a target store based on a QR code according to one embodiment of the present disclosure.

[0033] FIG. 4 is a drawing showing store information of a target store according to one embodiment of the present disclosure.

[0034] FIG. 5 is a drawing showing store information of a target store according to one embodiment of the present disclosure.

[0035] FIG. 6 is a drawing showing detailed item information according to one embodiment of the present disclosure.

[0036] FIG. 7 is a drawing showing store information of a target store according to one embodiment of the present disclosure.

[0037] FIG. 8 is a drawing showing recommended item information according to one embodiment of the present disclosure.

[0038] FIG. 9 is a drawing showing order target list information according to one embodiment of the present disclosure.

[0039] FIG. 10 is a drawing showing promotion information according to one embodiment of the present disclosure.

[0040] FIG. 11 is a drawing showing payment service list information according to one embodiment of the present disclosure.

[0041] FIG. 12 is a diagram showing inquiry information regarding whether to run a target application to authenticate a user according to one embodiment of the present disclosure.

[0042] FIG. 13 is a diagram showing execution failure information of a target application according to one embodiment of the present disclosure.

[0043] FIG. 14 is a diagram showing execution failure information of a target application according to one embodiment of the present disclosure.

[0044] FIG. 15 is a diagram showing inquiry information regarding whether to authenticate a user based on a user account registered in a target application according to one embodiment of the present disclosure.

[0045] FIG. 16 is a drawing showing payment schedule information for a first payment service according to one embodiment of the present disclosure.

[0046] FIG. 17 is a diagram illustrating a process in which a user agrees to pay the payment amount of a target item according to a first payment service, according to one embodiment of the present disclosure.

[0047] FIG. 18 is a drawing showing payment service list information according to one embodiment of the present disclosure.

[0048] FIG. 19 is a drawing showing payment means list information for a first payment service according to one embodiment of the present disclosure.

[0049] FIG. 20 is a drawing showing payment means list information for a second payment service according to one embodiment of the present disclosure.

[0050] FIG. 21 is a drawing showing payment schedule information for a second payment service according to one embodiment of the present disclosure.

[0051] FIG. 22 is a drawing showing order completion information for a target item according to one embodiment of the present disclosure.

[0052] FIG. 23 is a drawing showing order completion information for a target item according to one embodiment of the present disclosure.

[0053] FIG. 24 is a drawing showing store situation information according to one embodiment of the present disclosure.

[0054] FIG. 25 is a diagram illustrating a process for processing order information according to one embodiment of the present disclosure.

[0055] FIG. 26 is a diagram illustrating a process for processing order information according to one embodiment of the present disclosure.

[0056] FIG. 27 is a diagram illustrating a process for processing order information according to one embodiment of the present disclosure.

[0057] FIG. 28 is a diagram illustrating a process for processing order information according to one embodiment of the present disclosure.

[0058] FIG. 29 is a diagram illustrating a process for processing order information according to one embodiment of the present disclosure.

[0059] FIG. 30 is a diagram illustrating a process for processing order information according to one embodiment of the present disclosure.

[0060] FIG. 31 is a drawing illustrating a method according to one embodiment of the present disclosure.

[0061] FIG. 32 is a drawing illustrating a method according to one embodiment of the present disclosure.

[0062] FIG. 33 is a drawing illustrating a method according to one embodiment of the present disclosure.

[0063] FIG. 34 is a block diagram of a computing device according to one embodiment of the present disclosure.

[0064] The various embodiments described in this disclosure are illustrative for the purpose of clearly explaining the technical concept of this disclosure and are not intended to limit it to specific embodiments. The technical concept of this disclosure includes various modifications, equivalents, alternatives, and embodiments selectively combined from all or part of each embodiment described in this disclosure. Furthermore, the scope of the technical concept of this disclosure is not limited to the various embodiments presented below or the specific descriptions thereof.

[0065] Terms used in this disclosure, including technical or scientific terms, may have the meaning generally understood by those skilled in the art to which this disclosure pertains, unless otherwise defined.

[0066] In the present disclosure, expressions such as “comprising,” “may compose,” “possessing,” “possessing,” “having,” “possessing,” etc., mean that the subject feature (e.g., function, operation, or component, etc.) exists and do not exclude the existence of other additional features. That is, such expressions should be understood as open-ended terms implying the possibility of including other embodiments.

[0067] In the present disclosure, singular expressions may include the meaning of the plural form unless otherwise indicated by the context, and this applies likewise to singular expressions described in the claims.

[0068] In the present disclosure, expressions such as "first," "second," or "first," "second," etc., are used to distinguish one object from another when referring to a plurality of objects of the same kind, unless otherwise indicated by the context, and do not limit the order or importance of said objects.

[0069] In the present disclosure, expressions such as “A, B, and C”, “A, B, or C”, “A, B, and / or C”, “at least one of A, B, and C”, “at least one of A, B, or C”, “at least one of A, B, and / or C”, etc., may mean each listed item or all possible combinations of listed items. For example, “at least one of A or B” may refer to (1) at least one A, (2) at least one B, and (3) at least one A and at least one B.

[0070] In the present disclosure, expressions such as "a", "b", "c", etc. may represent any number depending on the context.

[0071] In the present disclosure, the expression “based on” is used to describe one or more factors affecting an act or action of a decision or judgment described in the phrase or sentence containing this expression, and this expression does not exclude additional factors affecting said act or action of a decision or judgment.

[0072] In the present disclosure, the expression that a certain component (e.g., a first component) is "connected" or "connected" to another component (e.g., a second component) may mean that the certain component is not only directly connected or connected to the other component, but is also connected or connected through a new other component (e.g., a third component).

[0073] In the present disclosure, "configured to" may, depending on the context, mean "set to," "capable of," "modified to," "made to," or "capable of." This expression is not limited to the meaning of "specifically designed in hardware." For example, a processor configured to perform a specific operation may mean a generic-purpose processor capable of performing that specific operation by executing software, or a special-purpose computer structured through programming to perform that specific operation.

[0074] In the present disclosure, "item" may mean an object intended for sale. In the present disclosure, "item" may be replaced with "product."

[0075] Hereinafter, various embodiments described in this disclosure will be explained with reference to the attached drawings. In the attached drawings and the description thereof, identical or substantially equivalent components may be given the same reference numerals. Furthermore, in the description of the various embodiments below, the description of identical or corresponding components may be omitted, but this does not mean that such components are not included in the embodiments.

[0076] FIG. 1 is a drawing showing a system (100) according to one embodiment of the present disclosure. According to one embodiment, the system (100) may include at least one of a user terminal (110), a device (120), a store terminal (130), or a payment server (140). Meanwhile, FIG. 1 illustrates an example of a system (100) to which an embodiment of the present disclosure may be applied, and the present disclosure is not limited thereto. For example, other entities not shown in FIG. 1 may be included in the system (100).

[0077] According to one embodiment, the user terminal (110) may be a terminal possessed by a user visiting a store. For example, the user terminal (110) may output information received from a device (120), a store terminal (130), or a payment server (140) on a display. For example, the user terminal (110) may generate a page based on information received from the device (120), the store terminal (130), or the payment server (140), and output the page on a display. In the present disclosure, outputting information on a display may include generating a page containing the information and then outputting the page on a display. For example, the user terminal (110) may obtain user input information regarding the information output on the display and transmit it to the device (120), the store terminal (130), or the payment server (140).

[0078] For example, the user terminal (110) may be implemented as a device capable of transmitting and receiving various information to and from a device (120), a store terminal (130), or a payment server (140) via a network (150). For example, the user terminal (110) may be one of a desktop computer, a laptop computer, a portable communication terminal (smartphone, etc.), a portable multimedia server, a wearable server, or a head-mounted display (HMD). However, the type of user terminal (110) is not limited thereto, and the user terminal (110) may be any computing device capable of receiving information from a user or outputting information to a user, including an input / output interface (e.g., a display), and communicating with a device (120), a store terminal (130), a payment server (140), or other servers via a network (150).

[0079] According to one embodiment, the device (120) may be a device that processes order information for a target item ordered at a table in a store. For example, the device (120) may be a server that manages a predetermined target application. Here, the predetermined target application may be an application that provides a service to order items from an online store.

[0080] For example, the device (120) may be implemented with one or more computing devices. For example, all functions of the device (120) may be implemented in a single computing device. Alternatively, a first function of the device (120) may be implemented in a first computing device and a second function may be implemented in a second computing device. Alternatively, multiple computing devices may be used, each implementing all functions or specific functions of the device (120). For example, a computing device capable of implementing the device (120) may be a desktop computer, a laptop computer, an application server, a proxy server, or a cloud server, but is not limited thereto, and any type of server equipped with computing functions may be a computing device.

[0081] According to one embodiment, the store terminal (130) may be a terminal installed in the store. For example, the store terminal (130) may be a point of sales (POS) terminal located at the counter of the store for managing store information such as order status and sales received at the store, or a terminal equipped with POS software for managing store information. For example, the store terminal (130) may display information received from the user terminal (110), device (120), or payment server (140) on a display. For example, the store terminal (130) may acquire user input information regarding the information displayed on the display and transmit it to the user terminal (110), device (120), or payment server (140).

[0082] For example, the store terminal (130) may be implemented as a device capable of transmitting and receiving various information to and from a user terminal (110), a device (120), or a payment server (140) via a network (150). For example, the store terminal (130) may be one of a desktop computer, a laptop computer, a portable communication terminal (smartphone, etc.), a portable multimedia server, a wearable server, or an HMD. However, the type of store terminal (130) is not limited thereto, and the store terminal (130) may be any computing device capable of receiving information from a user or outputting information to a user, including an input / output interface (display), and communicating with a user terminal (110), a device (120), a payment server (140), or other servers via a network (150).

[0083] According to one embodiment, the payment server (140) may be a device that processes a payment request for the payment amount of a target item ordered at a table in a store. For example, the payment server (140) may receive a payment request from a user terminal (110) or device (120) that includes information regarding the payment amount and information regarding the payment method. The payment server (140) may transmit the information regarding the payment amount and the information regarding the payment method to a financial institution server corresponding to the payment method to request payment of the payment amount using the payment method. For example, the payment method may be card payment or account transfer, etc. For example, if the payment method is card payment, the information regarding the payment method may include the name of the card, the card number, the cardholder, etc. For example, if the payment method is account transfer, the information regarding the payment method may include the name of the account, the account number, the managing bank of the account, the accountholder, etc. For example, the financial institution server may include a card company server, a bank server, etc. corresponding to the payment method. For example, the payment server (140) may receive a payment rejection response or a payment approval response from the financial institution server. For example, upon receiving a payment rejection response, the payment server (140) may transmit payment failure information to the user terminal (110) or device (120) indicating that payment for the payment amount using the payment method has failed. For example, upon receiving a payment approval response, the payment server (140) may transmit payment approval information to the user terminal (110) or device (120) indicating that payment for the payment amount using the payment method has been approved (completed). For example, the payment approval information may include at least one of information regarding the payment amount, information regarding the payment method, or information regarding the payment completion time. For example, based on the payment approval information, the payment server (140) may deposit the payment amount into an account designated by the store.

[0084] For example, the payment server (140) may be implemented with one or more computing devices. For example, all functions of the payment server (140) may be implemented in a single computing device. Alternatively, the first function of the payment server (140) may be implemented in a first computing device and the second function may be implemented in a second computing device. Alternatively, multiple computing devices may be used, each implementing all functions or specific functions of the payment server (140). For example, a computing device capable of implementing the payment server (140) may be a desktop computer, a laptop computer, an application server, a proxy server, or a cloud server, but is not limited thereto, and any type of server equipped with computing functions may be a computing device.

[0085] According to one embodiment, the network (150) may serve to connect a user terminal (110), a device (120), a store terminal (130), a payment server (140), or other external servers. For example, the network (150) may provide a connection path so that the user terminal (110), the device (120), the store terminal (130), or the payment server (140) can be connected to each other to transmit and receive packet data. The network (150) may be implemented as any kind of wired or wireless network, such as, for example, a local area network (LAN), a wide area network (WAN), a mobile radio communication network, or Wibro (wireless broadband internet).

[0086] According to one embodiment, at least some of the user terminal (110), device (120), store terminal (130), and payment server (140) may operate as a single device. For example, the user terminal (110) may be included in the device (120) as all or part of the components of the device (120). For example, various information exchanged between the user terminal (110) and the device (120) via a network (150) may be various information exchanged between each component within a single device. In this case, an operation performed by the user terminal (110) may be expressed as an operation performed by the device (120), and an operation performed by the device (120) may be expressed as an operation performed by the user terminal (110). For example, the store terminal (130) may be included in the device (120) as all or part of the components of the device (120). For example, various information exchanged between a store terminal (130) and a device (120) via a network (150) may be various information exchanged between each component within a single device. In this case, an operation performed by the store terminal (130) may be expressed as an operation performed by the device (120).

[0087] FIG. 2 is a diagram illustrating a process (200) for obtaining a connection address for store information of a target store based on an NFC device (210) according to an embodiment of the present disclosure. According to an embodiment, the connection address for store information of a target store may be a URL (uniform resource locator) for identifying store information. According to an embodiment, the NFC device (210) may be assigned to a table within the store. For example, the NFC device (210) may be attached to a part of the assigned table or to a part of an object placed on the table assigned to the NFC device (210). For example, the NFC device (210) may be attached in the form of a sticker. For example, the connection address for store information of a target store and the identifier of the table assigned to the NFC device (210) may be encoded in the NFC device (210).

[0088] According to one embodiment, a user terminal (110) in NFC mode can generate an electromagnetic field to communicate with an NFC device (210). For example, when the user terminal (110) is brought within a predetermined distance of the NFC device (210), the NFC device (210) can be activated by receiving power through the electromagnetic field generated by the user terminal (110). For example, based on the power received through the electromagnetic field, the NFC device (210) can transmit to the user terminal (110) the access address for the store information of the target store and the identifier of the table assigned to the NFC device (210). Meanwhile, in the present disclosure, the operation of bringing the user terminal (110) within a predetermined distance of the NFC device (210) can be expressed as an operation of tagging the user terminal (110) to the NFC device (210).

[0089] According to one embodiment, the user terminal (110) may output a notification on a display indicating that it has obtained a connection address for store information encoded in the NFC device (210). For example, the notification indicating that it has obtained a connection address for store information may include interface information for requesting store information of a target store.

[0090] According to one embodiment, the user terminal (110) can transmit a request for store information of a target store to the device (120) based on the connection address for the store information of the target store received from the NFC device (210) and the identifier of the table assigned to the NFC device (210), as the user input information for interface information for requesting store information of a target store is obtained. For example, the request for store information of a target store may include the connection address for the store information of the target store received from the NFC device (210) and the identifier of the table assigned to the NFC device (210). In this case, the user terminal (110) may correspond to the table assigned to the NFC device (210). For example, the table corresponding to the user terminal (110) may be represented as a target table.

[0091] FIG. 3 is a diagram illustrating a process (300) for obtaining an access address for store information of a target store based on a QR code (310) according to one embodiment of the present disclosure. According to one embodiment, the QR code (310) may be assigned to a table within the target store. For example, the QR code (310) may be attached to a part of the assigned table or to a part of an object placed on the table assigned to the QR code (310). For example, the QR code (310) may be attached in the form of a sticker. For example, the access address for store information of the target store and the identifier of the table assigned to the QR code (310) may be encoded in the QR code.

[0092] According to one embodiment, the camera of the user terminal (110) can recognize a QR code (310). For example, the camera of the user terminal (110) can obtain an access address for the store information of the target store encoded in the QR code (310) and an identifier of the table assigned to the QR code (310).

[0093] According to one embodiment, the user terminal (110) may output a notification on the display indicating that it has obtained an access address for the store information of the target store through a QR code (310). For example, the notification indicating that it has obtained an access address for the store information of the target store may include interface information for requesting the store information of the target store.

[0094] According to one embodiment, the user terminal (110) can transmit a request for store information of a target store to the device (120) based on the access address for the store information of the target store obtained from the QR code (310) and the identifier of the table assigned to the QR code (310), as the user obtains input information for the interface information for requesting store information of a target store. For example, the request for store information of a target store may include the access address for the store information of the target store obtained from the QR code (310) and the identifier of the table assigned to the QR code (310). In this case, the user terminal (110) may correspond to the table assigned to the QR code (310). For example, the table corresponding to the user terminal (110) may be represented as a target table.

[0095] FIG. 4 is a diagram showing store information (400) of a target store according to one embodiment of the present disclosure. According to one embodiment, the device (120) may transmit the store information (400) to a user terminal (110) upon receiving a request for the store information (400) of the target store. For example, the user terminal (110) may output the store information (400) on a display. Meanwhile, the store information (400) illustrated in FIG. 4 is merely an example for explaining an embodiment of the present disclosure, and the present disclosure is not limited thereto. For example, some components of the store information (400) may be omitted, or other components not illustrated in FIG. 4 may be included in the store information (400).

[0096] According to one embodiment, the store information (400) may include information about the trade name (410) of the target store.

[0097] According to one embodiment, store information (400) may include information about a target table (420) corresponding to a user terminal (110) within the target store. For example, the information about the table (420) may include an identifier of the target table (420). For example, the identifier of the table (420) may be a number assigned to the target table (420). Based on the identifier of the table (420), the target table (420) may be distinguished from other tables within the store.

[0098] According to one embodiment, the store information (400) may include information regarding the notice (430) of the target store. For example, the notice (430) of the target store may indicate the store's operating hours, level of congestion, etc.

[0099] According to one embodiment, store information (400) may include information about at least one item (440) sold at a target store. For example, information about the item (440) may include at least one of the item category to which the item (440) belongs, the name of the item (440), the price of the item (440), or an image of the item (440).

[0100] For example, at least one item (440) sold at the target store may include recommended items recommended to the user by the target store. For example, the recommended items may be determined based on the user's item order history for at least one item (440) sold at the target store. For example, the user's item order history may include at least one of the total number of orders per item, the total payment amount, or the order frequency. For example, the recommended items may be determined based on the user's discount coupon issuance history. For example, the recommended items may include items to which discount coupons issued or that may be issued to the user are applicable among at least one item (440) sold at the target store. For example, the recommended items may be determined based on the user's membership history. For example, if the user is subscribed to a membership, the recommended items may include items to which membership benefits are applicable among at least one item (440) sold at the target store. For example, membership benefits may include discount benefits, cash accumulation benefits on payment amounts, etc. Here, Cash can be a virtual currency that can be used to pay the payment amount when ordering items.

[0101] For example, at least one item (440) sold at the target store may include a popular item with a number of orders greater than a predetermined number.

[0102] According to one embodiment, store information (400) may include interface information (450) for calling an employee of a target store. For example, as the user terminal (110) obtains user input information regarding the interface information (450), it transmits a call request for an employee of a target store to the device (120), and the device (120) may transmit the call request for an employee of a target store to the store terminal (130). Alternatively, as the user terminal (110) obtains user input information regarding the interface information (450), it may transmit a call request for an employee of a target store to the store terminal (130). For example, the call request for an employee of a target store may include information regarding a target table (420). For example, the store terminal (130) may output the call request for an employee of a target store on a display. Through this, the manager or employee of the target store can confirm that there is a call from the target table (420).

[0103] FIG. 5 is a diagram showing store information (400) of a target store according to one embodiment of the present disclosure. For example, if the number of user terminals requesting store information (400) based on the access address for the store information (400) of the target store is at least two, the information for the target table (420) may further include information for the number of user terminals (510) corresponding to the target table (420). For example, if the number of user terminals requesting store information (400) based on the access address for the store information (400) of the target store is at least two, the store information (400) may include a notification (520) indicating that at least two users are placing an order together at the target table (420).

[0104] FIG. 6 is a diagram showing item detail information (600) according to an embodiment of the present disclosure. According to an embodiment, a user terminal (110) may transmit a request for item detail information (600) for a target item (610, 620) selected by the user to a device (120) by obtaining input information from a user who selects one item among at least one item (440) displayed on a display. For example, the user terminal (110) may receive item detail information (600) from the device (120) and display it on a display. Meanwhile, the item detail information (600) illustrated in FIG. 6 is merely an example for explaining an embodiment of the present disclosure, and the present disclosure is not limited thereto. For example, some components of the item detail information (600) may be omitted, or other components not illustrated in FIG. 6 may be included in the item detail information (600).

[0105] For example, the item details (600) may include information about the target item (610, 620). For example, the information about the target item (610, 620) may include at least one of the name of the target item (610, 620) or the price of the target item (610, 620). For example, the item details (600) may include interface information (611) for changing the quantity of the target item (610, 620).

[0106] According to one embodiment, the item details (600) may include information about additional items that can be ordered together with the target items (610, 620). For example, the additional items may belong to a different item category than the target items. For example, if the target items are "pasta," the additional items may be "drinks." If the user selects the additional items, the target items (610, 620) may include the items selected by the user from at least one item (440) and the additional items.

[0107] According to one embodiment, the item detail information (600) may include interface information (630) for adding target items (610, 620) to the order target list information of the target table (420). For example, the interface information (630) may indicate the price of the target items (610, 620). As the user terminal (110) obtains user input information regarding the interface information (630), it may transmit a request to add target items (610, 620) to the order target list information of the target table (420) to the device (120). As the device (120) receives the request to add target items (610, 620) to the order target list information of the target table (420), it may add target items (610, 620) to the order target list information of the target table (420).

[0108] According to one embodiment, the item detail information (600) may include interface information (640) for calling an employee of a target store. For example, the user terminal (110) may transmit a call request for an employee of a target store to the device (120) upon obtaining user input information regarding the interface information (640), and the device (120) may transmit the call request for an employee of a target store to the store terminal (130). Alternatively, the user terminal (110) may transmit a call request for an employee of a target store to the store terminal (130) upon obtaining user input information regarding the interface information (640). For example, the call request for an employee of a target store may include information regarding the target table (420). For example, the store terminal (130) may output the call request for an employee of a target store on the display. Through this, the manager or employee of the store can confirm that there is a call from the target table (420).

[0109] FIG. 7 is a diagram showing store information (400) of a target store according to one embodiment of the present disclosure. According to one embodiment, the device (120) can transmit store information (400) to the user terminal (110) by adding target items (610, 620) to the order target list information of the target table (420) corresponding to the user terminal (110). In this case, the store information (400) may include a notification (710) indicating that target items (610, 620) have been added to the order target list information of the target table (420), or interface information (720) for requesting the order target list information of the target table (420). For example, the user terminal (110) may output the store information (400) on a display. Meanwhile, the store information (400) illustrated in FIG. 7 is merely an example for explaining an embodiment of the present disclosure, and the present disclosure is not limited thereto. For example, some components may be omitted, or other components not shown in FIG. 7 may be included in the store information (400).

[0110] According to one embodiment, the interface information (720) may indicate an amount obtained by summing the prices of at least one target item included in the order target list information. For example, the user terminal (110) may transmit a request for order target list information to the device (120) upon obtaining user input information regarding the interface information (720). For example, the device (120) may transmit order target list information to the user terminal (110) upon receiving a request for order target list information.

[0111] FIG. 8 is a diagram showing recommended item information (800) according to one embodiment of the present disclosure. According to one embodiment, the device (120) can transmit recommended item information (800) to a user terminal (110) for a recommended item (810) that has been ordered at least once with a target item included in the order target list information among at least one item (440) sold at a target store, and the number of times it has been ordered is greater than or equal to a predetermined number. For example, the user terminal (110) can output the recommended item information (800) on a display. For example, the user terminal (110) can output the recommended item information (800) on at least a part of the area where store information (400) is displayed on the display. That is, the recommended item information (800) can be output on the display of the user terminal (110) in a form that is at least partially overlaid on the store information (400). Meanwhile, the recommended item information (800) illustrated in FIG. 8 is merely an example for explaining an embodiment of the present disclosure, and the present disclosure is not limited thereto. For example, some components of the recommended item information (800) may be omitted, or other components not shown in FIG. 8 may be included in the recommended item information (800).

[0112] According to one embodiment, the recommended item information (800) may include information about a recommended item (810) that has been ordered together with a target item included in the order target list information among at least one item (440) sold at a target store, and that the number of times it has been ordered is greater than or equal to a predetermined number. For example, the information about the recommended item (810) may include at least one of an image of the recommended item (810), a name of the recommended item (810), or a price of the recommended item (810).

[0113] According to one embodiment, the recommended item information (800) may include interface information (820) for preventing the recommended item information (800) from being displayed on the display of the user terminal (110). For example, the user terminal (110) may control the display so that the recommended item information (800) is not displayed on the display by obtaining user input information regarding the interface information (820).

[0114] FIG. 9 is a diagram showing order target list information (900) according to one embodiment of the present disclosure. According to one embodiment, the device (120) may transmit the order target list information (900) to the user terminal (110) upon receiving a request for the order target list information (900) of the target table (420) from the user terminal (110). For example, the user terminal (110) may receive the order target list information (900) and output it on a display. Meanwhile, the order target list information (900) illustrated in FIG. 9 is merely an example for explaining an embodiment of the present disclosure, and the present disclosure is not limited thereto. For example, some components of the order target list information (900) may be omitted, or other components not illustrated in FIG. 9 may be included in the order target list information (900).

[0115] According to one embodiment, the order target list information (900) may include interface information (910) for inputting requests for an order target item (920). For example, the user terminal (110) may output requests for an order target item (920) on a display as it obtains user input information regarding the interface information (910). For example, the user input information regarding the interface information (910) may include a string representing the user's request for an order target item (920).

[0116] According to one embodiment, the order target list information (900) may include information about the order target item (920). For example, the information about the order target item (920) may include at least one of the name of the order target item (920), the price of the order target item (920), or the order quantity of the order target item (920).

[0117] According to one embodiment, the order target list information (900) may include information regarding the payment amount (930). For example, the payment amount (930) may be the sum of the prices of the order target items (920) included in the order target list information (900), and may be the amount expected to be paid when ordering the order target items (920).

[0118] According to one embodiment, the order target list information (900) may include interface information (940) for requesting payment of a payment amount (930) for an order target item (920). For example, the user terminal (110) can identify whether the user's authentication information for a predetermined target application is valid by obtaining user input information regarding the interface information (940). For example, the user terminal (110) can identify that the user's authentication information for the target application is valid by identifying that the user's account registered in the target application is in a logged-in state in the target application. For example, the user terminal (110) can identify that the user's authentication information for the target application is invalid by identifying that the user's account registered in the target application is in a logged-out state in the target application. For example, the user terminal (110) can generate order information for the order target item (920) based on the result of identifying whether the user's authentication information for the target application is valid. For example, order information for an item to be ordered (920) may include information about the item to be ordered (920), information about the payment amount (930) of the item to be ordered (920), and information indicating whether the user's authentication information for the target application is valid. Additionally, order information for the item to be ordered (920) may include information about requests for the item to be ordered (920). Meanwhile, a payment service for paying the payment amount (930) of the item to be ordered (920) may be one of a first payment service, a second payment service, and a third payment service. For example, the first payment service may be a payment service that pays the payment amount (930) of the item to be ordered (920) using a payment method registered in association with the user's account in the target application.For example, the second payment service may be a payment service that pays the payment amount (930) of the target item (920) using a payment method selected by the user. For example, the third payment service may be a payment service that pays the payment amount (930) of the target item (920) at the counter of the target store. In the present disclosure, the first payment service may be expressed as a simple payment service, the second payment service as a general payment service, and the third payment service as an on-site payment service. For example, when the user terminal (110) first obtains user input information regarding interface information (940), the target payment service for paying the payment amount of the target item (920) may be predetermined as the first payment service.

[0119] FIG. 10 is a diagram showing promotion information (1000) according to one embodiment of the present disclosure. According to one embodiment, the device (120) can identify whether the user authentication information of the user terminal (110) for the target application is valid upon receiving order information for a target item (920) from the user terminal (110). For example, the device (120) can identify that the user needs to select a target payment service to pay the payment amount of the target item upon identifying that the user needs to select a target payment service to pay the payment amount of the target item. For example, the device (120) can identify whether there is a history of transmitting promotion information (1000) to the user terminal (110) indicating the first payment service as a recommended payment service upon identifying that the user needs to select a target payment service to pay the payment amount of the target item. That is, the device (120) can identify whether the user of the user terminal (110) has seen the promotion information (1000). For example, the device (120) can transmit the promotion information (1000) to the user terminal (110) by identifying that there is no history of transmitting the promotion information (1000) to the user terminal (110). For example, the user terminal (110) can receive the promotion information (1000) and output it on a display. For example, the user terminal (110) can output the promotion information (1000) on at least a part of the area where the order target list information (900) is displayed on the display. That is, the promotion information (1000) can be output on the display of the user terminal (110) in a form that is at least partially overlaid on the order target list information (900).

[0120] According to one embodiment, the promotion information (1000) may include interface information (1010) for preventing the promotion information (1000) from being displayed on the display of the user terminal (110). For example, the user terminal (110) may control the display so that the promotion information (1000) is not displayed on the display by acquiring user input information regarding the interface information (1010). For example, the user terminal (110) may transmit information indicating that user input information regarding the interface information (1010) has been acquired to the device (120).

[0121] According to one embodiment, the promotion information (1000) may include descriptive information (1020) for a first payment service. For example, the descriptive information (1020) for a first payment service may include an image or text describing the first payment service. For example, the image or text describing the first payment service may refer to FIG. 10.

[0122] According to one embodiment, the promotion information (1000) may include interface information (1030) for requesting information about a payment method registered in a target application for a first payment service. For example, a user terminal (110) may initiate a user authentication procedure for a target application by obtaining user input information regarding the interface information (1030).

[0123] FIG. 11 is a diagram showing payment service list information (1100) according to one embodiment of the present disclosure. According to one embodiment, the device (120) can transmit payment service list information (1100) for at least one payment service to the user terminal (110) by identifying that there is a history of transmitting promotion information (10000) to the user terminal (110). According to one embodiment, the device (120) can transmit payment service list information (1100) to the user terminal (110) by receiving information indicating that user input information regarding interface information (1010) included in the promotion information (1000) has been obtained from the user terminal (110). For example, the user terminal (110) can receive payment service list information (1100) and output it on a display.

[0124] According to one embodiment, the payment service list information (1100) may include option information (1110) for the first payment service. For example, the option information (1110) for the first payment service may include interface information (1111) for selecting the first payment service as the target payment service and interface information (1112) for requesting information about a payment method registered in the target application for the first payment service. For example, the user terminal (110) may identify that the user has selected the first payment service as the target payment service by obtaining user input information regarding the interface information (1111). For example, the user terminal (110) may initiate a user authentication procedure for the target application by obtaining user input information regarding the interface information (1112).

[0125] According to one embodiment, the payment service list information (1100) may include option information (1120) for a second payment service. For example, the option information (1120) for a second payment service may include interface information (1121) for selecting the second payment service as a target payment service. For example, the user terminal (110) may identify that the user has selected the second payment service as a target payment service by obtaining user input information regarding the interface information (1121).

[0126] According to one embodiment, the payment service list information (1100) may include option information (1130) for a third payment service. For example, the option information (1130) for a third payment service may include interface information (1131) for selecting the third payment service as a target payment service. For example, the user terminal (110) may identify that the user has selected the third payment service as a target payment service by obtaining user input information regarding the interface information (1131).

[0127] According to one embodiment, the payment service list information (1100) may include interface information (1140) for requesting the continuation of a procedure to pay the payment amount of a target item according to the target payment service. For example, if the target payment service is a first payment service, the user terminal (110) may initiate a user authentication procedure for the target application by obtaining user input information regarding the interface information (1140). For example, if the target payment service is a second payment service, the user terminal (110) may initiate a procedure to pay the payment amount of a target item according to the second payment service by obtaining user input information regarding the interface information (1140). For example, if the target payment service is a third payment service, the user terminal (110) may initiate a procedure to pay the payment amount of a target item according to the third payment service by obtaining user input information regarding the interface information (1140).

[0128] FIG. 12 is a diagram showing inquiry information (1200) regarding whether to execute a target application to authenticate a user according to one embodiment of the present disclosure. According to one embodiment, as the user terminal (110) initiates a user authentication procedure for a target application, inquiry information (1200) regarding whether to execute a target application can be displayed on a display.

[0129] According to one embodiment, inquiry information (1200) may include interface information (1210) for canceling (stopping) the execution of a target application for authenticating a user. For example, when a user authentication procedure for a target application is initiated from promotion information (1000), the user terminal (110) may output the promotion information (1010) received from the device (120) on the display again as it obtains user input information regarding the interface information (1210). For example, when a user authentication procedure for a target application is initiated from payment service list information (1100), the user terminal (110) may output the payment service list information (1100) received from the device (120) on the display again as it obtains user input information regarding the interface information (1100).

[0130] According to one embodiment, inquiry information (1200) may include interface information (1220) for approving the execution of a target application to authenticate a user. For example, a user terminal (110) may execute a target application by obtaining user input information regarding the interface information (1220).

[0131] FIG. 13 is a diagram showing execution failure information (1300) of a target application according to one embodiment of the present disclosure. According to one embodiment, as the user terminal (110) identifies that the target application is not installed on the user terminal (110), execution failure information (1300) indicating that the execution of the target application has failed because the target application is not installed on the user terminal (110) can be displayed on a display. For example, when a user authentication procedure for the target application is initiated from promotion information (1000), the user terminal (110) identifies that the target application is not installed on the user terminal (110) and can transmit a request for payment service list information (1100) to the device (120). For example, the user terminal (110) receives payment service list information (1100) from the device (120) and can display the payment service list information (1100) and execution failure information (1300) on a display. For example, when a user authentication procedure for a target application is initiated from the payment service list information (1100), the user terminal (110) may output the payment service list information (1100) and execution failure information (1300) received from the device (120) on the display as the user terminal (110) identifies that the target application is not installed on the user terminal (110). For example, the execution failure information (1300) may be output on the display of the user terminal (110) in a form that is at least partially overlaid on the payment service list information (1100).

[0132] FIG. 14 is a diagram showing execution failure information (1400) of a target application according to one embodiment of the present disclosure. According to one embodiment, as the user terminal (110) identifies that the latest version of the target application is not installed on the user terminal (110), execution failure information (1400) indicating that the execution of the target application has failed because the latest version of the target application is not installed on the user terminal (110) can be displayed on a display. For example, when a user authentication procedure for the target application is initiated from promotion information (1000), the user terminal (110) identifies that the latest version of the target application is not installed on the user terminal (110) and can transmit a request for payment service list information (1100) to the device (120). For example, a user terminal (110) may receive payment service list information (1100) from a device (120) and output the payment service list information (1100) and execution failure information (1400) on a display. For example, when a user authentication procedure for a target application is initiated from the payment service list information (1100), the user terminal (110) may output the payment service list information (1100) and execution failure information (1400) received from the device (120) on a display as it identifies that the latest version of the target application is not installed on the user terminal (110). For example, the execution failure information (1400) may be output on the display of the user terminal (110) in a form that is at least partially overlaid on the payment service list information (1100).

[0133] FIG. 15 is a diagram showing inquiry information (1500) regarding whether to authenticate a user based on a user account registered in a target application according to one embodiment of the present disclosure. According to one embodiment, as the user terminal (110) executes a target application for authenticating a user, the inquiry information (1500) can be displayed on a display.

[0134] According to one embodiment, the inquiry information (1500) may include interface information (1510) for canceling (stopping) user authentication based on the user account registered in the target application. For example, when a user authentication procedure for the target application is initiated from the promotion information (1000), the user terminal (110) may output the promotion information (1000) received from the device (120) on the display again as it obtains user input information regarding the interface information (1510). For example, when a user authentication procedure for the target application is initiated from the payment service list information (1100), the user terminal (110) may output the payment service list information (1100) received from the device (120) on the display again as it obtains user input information regarding the interface information (1510).

[0135] According to one embodiment, inquiry information (1500) may include interface information (1520) for allowing (accepting) user authentication based on the user's account registered in the target application. For example, the user terminal (110) can identify whether the user's account registered in the target application is in a logged-in state in the target application by obtaining user input information regarding the interface information (1520). For example, the user terminal (110) can identify whether the user's account is in a logged-in state or a logged-out state in the target application based on a local cache indicating the login history for the user's account stored in the storage space allocated to the target application in memory. For example, the user terminal (110) identifies that the user's account is in a logged-in state in the target application, identifies that user authentication is complete, and can identify a payment method registered in association with the user's account in the target application as a payment method for the first payment service. For example, as the user terminal (110) identifies that the user's account is in a logged-out state in the target application, it may output interface information on the display to switch the user's account to a logged-in state in the target application. For example, as the user terminal (110) identifies that the user's account has switched to a logged-in state in the target application, it may identify that the user's authentication is complete and identify a payment method registered in association with the user's account in the target application as a payment method for the first payment service.

[0136] FIG. 16 is a diagram illustrating payment schedule information (1600) for a first payment service according to one embodiment of the present disclosure. According to one embodiment, when a user authentication procedure for a target application is initiated from promotion information (1000) and user authentication is completed based on the user's account registered in the target application, the device (120) may transmit payment schedule information (1600) for the first payment service to the user terminal (110). For example, the device (120) may receive the user authentication result for the target application from the user terminal (110). For example, the device (120) may transmit payment schedule information (1600) for the first payment service to the user terminal (110) as the user authentication result for the target application indicates that user authentication is completed. For example, the user authentication result for the target application may include information regarding a payment method registered in association with the user's account in the target application. For example, the user terminal (110) may receive payment schedule information (1600) for the first payment service and output order target list information (900) and payment schedule information (1600) on a display. For example, the user terminal (110) may output payment schedule information (1600) on at least a portion of the area where order target list information (900) is output on the display. That is, payment schedule information (1600) may be output on the display of the user terminal (110) in a form that is at least partially overlaid on the order target list information (900).

[0137] According to one embodiment, the payment schedule information (1600) may include information about the target item (1610). For example, the information about the target item (1610) may include at least one of the name of the target item (1610), the quantity of the target item (1610), or the payment amount of the target item (1610).

[0138] According to one embodiment, payment schedule information (1600) may include information regarding a payment method (1620) for a first payment service. For example, the information regarding the payment method (1620) may include at least one of the name of a payment method registered in association with a user's account in a target application or an installment period for the payment amount of a target item.

[0139] According to one embodiment, payment schedule information (1600) may include interface information (1630) for changing a payment method (1620). For example, the user terminal (110) may transmit a request to change a payment method to the device (120) upon obtaining user input information regarding the interface information (1630). For example, upon receiving a request to change a payment method, the device (120) may transmit payment service list information (1100) to the user terminal (110). For example, the payment service list information (1100) may include information regarding at least one payment method registered in association with the user's account in the target application for the first payment service. For example, the user terminal (110) may receive the payment service list information (1100) and output it on a display.

[0140] According to one embodiment, payment scheduled information (1600) may include interface information (1640) for accepting (approving) the payment amount of a target item (1610) according to a first payment service. For example, as the user terminal (110) obtains user input information regarding the interface information (1640), it may transmit information to the device (120) indicating that the user has accepted the payment amount of the target item (1610) according to the first payment service. For example, as the device (120) receives information indicating that the user has accepted the payment amount of the target item (1610) according to the first payment service, it may initiate a procedure for paying the payment amount of the target item (1610) according to the first payment service.

[0141] FIG. 17 is a diagram illustrating a process (1700) in which a user consents to pay the payment amount of a target item according to a first payment service according to an embodiment of the present disclosure. According to an embodiment, the user may consent to pay the payment amount of a target item (1610) according to the first payment service by sliding touch the interface information (1640) displayed on the display of the user terminal (110) in a predetermined direction for a predetermined length. Meanwhile, FIG. 17 is merely an example of a method in which the user consents to pay the payment amount of a target item according to the first payment service, and the present disclosure is not limited thereto. For example, the user may consent to pay the payment amount of a target item (1610) according to the first payment service based on pre-registered biometric information. For example, the biometric information may include fingerprint information, iris information, facial information, vein information, etc. For example, the user terminal (110) may output information requesting the input of biometric information to approve the payment of the target item (1610) according to the first payment service on the display. For example, the user may approve the payment of the target item (1610) according to the first payment service by inputting biometric information into the user terminal (110). For example, the user may approve the payment of the target item (1610) according to the first payment service based on a payment password registered in association with the user's account in the target application. For example, the user terminal (110) may output information requesting the input of a payment password to approve the payment of the target item (1610) according to the first payment service on the display. For example, the user may approve the payment of the target item (1610) according to the first payment service by inputting a payment password into the user terminal (110).

[0142] FIG. 18 is a diagram showing payment service list information (1100) according to one embodiment of the present disclosure. According to one embodiment, a user authentication procedure for a target application is initiated from the payment service list information (1100), and when the user authentication for the target application is completed, the device (120) may transmit the payment service list information (1100) to a user terminal (110). In this case, the payment service list information (1100) may include interface information (1810) for changing a payment method for a first payment service and interface information (1820) for approving payment of a target item amount according to the target payment service. For example, the user terminal (110) may receive the payment service list information (1100) and output it on a display.

[0143] According to one embodiment, when the device (120) receives a request from the user terminal (110) to change a payment method based on user input information regarding interface information (1630), the device (120) may transmit payment service list information (1100) to the user terminal (110). In this case, the payment service list information (1100) may include interface information (1810) for changing a payment method for a first payment service and interface information (1820) for approving payment of a target item's payment amount according to the target payment service. For example, the user terminal (110) may receive the payment service list information (1100) and output it on a display.

[0144] According to one embodiment, when the target payment service is a first payment service, the user terminal (110) may transmit information to the device (120) indicating that the user has agreed to pay the payment amount of the target item according to the first payment service, upon obtaining user input information regarding interface information (1820). For example, upon receiving information indicating that the user has agreed to pay the payment amount of the target item according to the first payment service, the device (120) may initiate a procedure to pay the payment amount of the target item according to the first payment service. For example, when the target payment service is a second payment service, the user terminal (110) may initiate a procedure to pay the payment amount of the target item according to the second payment service upon obtaining user input information regarding interface information (1820). For example, when the target payment service is a third payment service, the user terminal (110) may initiate a procedure to pay the payment amount of the target item according to the third payment service upon obtaining user input information regarding interface information (1820).

[0145] FIG. 19 is a diagram showing payment means list information (1900) for a first payment service according to one embodiment of the present disclosure. According to one embodiment, a user terminal (110) can transmit payment means list information (1900) for a first payment service to the user terminal (110) upon obtaining user input information regarding interface information (1810). For example, the user terminal (110) can output the payment means list information (1900) on at least a part of the area where the payment service list information (1100) is output on the display. That is, the payment means list information (1900) can be output on the display of the user terminal (110) in a form where at least a part of the payment service list information (1100) is overlaid.

[0146] According to one embodiment, the payment method list information (1900) may include interface information for selecting a specific payment method registered in association with a user's account in a target application as a target payment method for a first payment service. For example, upon obtaining user input information regarding the interface information for selecting a specific payment method, the user terminal (110) may identify that an existing payment method for the first payment service has been changed to a specific payment method selected by the user, and transmit information indicating that an existing payment method for the first payment service has been changed to a specific payment method selected by the user to the device (120). For example, upon receiving information indicating that an existing payment method for the first payment service has been changed to a specific payment method selected by the user, the device (120) may transmit payment service list information (1100) indicating a specific payment method selected by the user to the user terminal (110). For example, the user terminal (110) may receive payment service list information (1100) indicating a payment method selected by the user and output it on a display.

[0147] FIG. 20 is a diagram showing payment means list information (2000) for a second payment service according to an embodiment of the present disclosure. According to an embodiment, as a user terminal (110) initiates a procedure to pay the payment amount of a target item according to the second payment service, a request for payment means list information (2000) for the second payment service may be transmitted to a payment server (140). For example, upon receiving a request for payment means list information (2000), the payment server (140) may transmit the payment means list information (2000) to the user terminal (110). For example, the user terminal (110) may receive the payment means list information (2000) and output it on a display.

[0148] According to one embodiment, the payment method information (2000) may include interface information (2010) for selecting a payment method for a second payment service. For example, as the user terminal (110) obtains user input information regarding the interface information (2010), it may transmit information about a target payment method selected by the user to a payment server (140).

[0149] FIG. 21 is a diagram showing payment schedule information (2100) for a second payment service according to one embodiment of the present disclosure. According to one embodiment, a payment server (140) can transmit payment schedule information (2100) to a user terminal (110) upon receiving information regarding a target payment method selected by a user based on user input information regarding interface information (2010) from a user terminal (110). For example, the user terminal (110) can receive payment schedule information (2100) and output it on a display.

[0150] According to one embodiment, payment scheduled information (2100) may include information about a target item (2110). For example, the information about the target item (2110) may include at least one of the name of the target item (2110) or the price of the target item (2110).

[0151] According to one embodiment, the payment schedule information (2100) may include information regarding a target payment method (2120) selected by the user. For example, the information regarding the target payment method (2120) may indicate at least one of the name of the target payment method (2120) or the installment period for the payment amount of the target item (2110).

[0152] According to one embodiment, payment scheduled information (2100) may include interface information (2130) for approving payment of the payment amount of a target item (2110) according to a second payment service. For example, the user terminal (110) may transmit payment request information for the second payment service to the payment server (140) upon obtaining user input information regarding the interface information (2130). For example, the payment request information for the second payment service may include information regarding the payment amount of the target item (2110) and information regarding the target payment method (2120). For example, upon receiving the payment request information for the second payment service, the payment server (140) may transmit information regarding the payment amount of the target item (2110) and information regarding the target payment method (2120) to a financial institution server corresponding to the target payment method (2120). For example, the payment server (140) may transmit payment approval information for the second payment service to the user terminal (110) upon receiving a payment approval response from the financial institution server. For example, the payment approval information for the second payment service may include payment details of the target item (2110) according to the target payment method (2120). For example, the payment details of the target item (2110) may include at least one of the payment amount or the payment completion time. For example, the user terminal (110) may transmit the payment details of the target item (2110) to the device (120).

[0153] FIG. 22 is a diagram showing order completion information (2200) for a target item according to one embodiment of the present disclosure. According to one embodiment, when the target payment service is a first payment service or a second payment service, the device (120) can transmit order completion information (2200) for the target item to a user terminal (110). For example, the user terminal (110) can receive the order completion information (2200) and output it on a display. For example, the order completion information (2200) may include a notification (2210) indicating that the order and payment of the target item have been completed. For example, the order completion information (2200) may include payment details (2220) of the target item according to the first payment service or the second payment service. For example, the order completion information (2200) may include a notification (2230) indicating that the order of the target item has been received by the store. Meanwhile, if the payment amount of the target item is 0 and the user's authentication information for the target application is valid, the device (120) can transmit order completion information (2200) to the user terminal (110) as it identifies that the user has requested payment of the payment amount for the target item. In this case, the user terminal (110) can output order completion information (2200) including payment details indicating that the payment amount of the target item is 0 on the display.

[0154] FIG. 23 is a diagram showing order completion information (2300) for a target item according to one embodiment of the present disclosure. According to one embodiment, when the target payment service is a third payment service, the device (120) can transmit order completion information (2300) for the target item to a user terminal (110). For example, the user terminal (110) can receive the order completion information (2300) and output it on a display. For example, the order completion information (2300) may include a notification (2310) indicating that the order for the target item has been completed and instructing the payment amount for the target item to be paid at the counter of the target store. For example, the order completion information (2300) may include the order details (2320) for the target item according to the third payment service. For example, the order completion information (2300) may include a notification (2330) indicating that the order for the target item has been received by the target store.

[0155] FIG. 24 is a drawing showing store situation information (2400) according to one embodiment of the present disclosure. According to one embodiment, a store terminal (130) can output store situation information (2400) on a display.

[0156] According to one embodiment, the store status information (2400) may include information for each of at least one table within the target store. For example, the information for each table may include at least one of the identifier of each table, the location of each table within the store, or the number of user terminals corresponding to each table. For example, the information for each table may include order completion information for each table. For example, the order completion information for each table may include at least one of the target item ordered at each table, the target payment service for paying the payment amount of the target item, or the estimated time required to serve the target item to the table.

[0157] According to one embodiment, a store terminal (130) may receive order completion information (2410) for at least one target item ordered from a target table within a target store from a device (120). For example, the store terminal (130) may output the order completion information (2410) on a display. For example, upon receiving the order completion information (2410), the store terminal (130) may output a notification (2420) on a display indicating that an order for at least one target item has been received from a target table within a target store.

[0158] FIG. 25 is a diagram illustrating a process (2500) for processing order information according to one embodiment of the present disclosure. At least some of the operations of the process (2500) may be omitted.

[0159] In S2501, the user terminal (110) can obtain an access address for store information (400) of the target store. According to one embodiment, the user terminal (110) can obtain an access address for store information (400) based on an NFC device or QR code located on a target table within the target store.

[0160] In S2502, the user terminal (110) can transmit a request for the store information (400) of the target store to the device (120) based on the access address for the store information (400) of the target store. According to one embodiment, the request for the store information (400) of the target store may include the access address for the store information (400) of the target store.

[0161] In S2503, the device (120) can transmit store information (400) of a target store to a user terminal (110). According to one embodiment, the store information (400) of a target store may include information about at least one item (440) sold at the target store.

[0162] In S2504, the user terminal (110) can transmit a request for item detail information (600) for a target item selected by the user among at least the items (440) sold at the target store to the device (120).

[0163] In S2505, the device (120) can transmit item detail information (600) for the target item to the user terminal (110).

[0164] In S2506, the user terminal (110) can transmit information to the device (120) requesting to add a target item to the order target list information (900).

[0165] In S2507, the device (120) can add a target item to the order target list information (900) and transmit the target store information (400) to the user terminal (110). According to one embodiment, the target store information (400) may include a notification indicating that a target item has been added to the order target list information (900).

[0166] In S2508, the user terminal (110) can transmit a request for order target list information (900) to the device (120).

[0167] In S2509, the device (120) can transmit order target list information (900) to the user terminal (110).

[0168] In S2510, the user terminal (110) can identify whether the user's authentication information for the target application is valid as it identifies that the user has requested payment of the payment amount for the order target item.

[0169] In S2511, the user terminal (110) can generate order information for a target item based on the result of identifying whether the user's authentication information for the target application is valid. According to one embodiment, if the user's authentication information for the target application is valid, the order information for the target item may include at least one of information about the target item, information about the payment amount of the target item, information indicating that the user's authentication information for the target application is valid, or information indicating a first payment service as a target payment service for paying the payment amount of the target item. According to one embodiment, if the user's authentication information for the target application is invalid, the order information for the target item may include at least one of information about the target item, information about the payment amount of the target item, information indicating that the user's authentication information for the target application is valid, or information indicating that there is a need to select a target payment service for paying the payment amount of the target item.

[0170] In S2512, the user terminal (110) can transmit order information for the target item to the device (120).

[0171] FIG. 26 is a diagram illustrating a process (2600) for processing order information according to one embodiment of the present disclosure. At least some of the operations of the process (2600) may be omitted.

[0172] In S2601, the device (120) can identify that the user's authentication information for the target application is valid based on the order information for the target item received from the user terminal (110).

[0173] In S2602, the device (120) can identify the first payment service as the target payment service for paying the payment amount of the target item as it identifies that the user's authentication information for the target application is valid. According to one embodiment, the device (120) can identify the first payment service as the target payment service based on order information for the target item received from the user terminal (110).

[0174] In S2603, as the device (120) identifies the first payment service as the target payment service, it can transmit payment scheduled information (1600) for the first payment service to the user terminal (110). According to one embodiment, the device (120) can generate payment scheduled information (1600) for the first payment service by identifying at least one payment method registered in association with the user's account in the target application for the first payment service.

[0175] In S2604, the user terminal (110) can transmit information to the device (120) indicating that the user has agreed to pay the payment amount of the target item according to the first payment service.

[0176] In S2605, the device (120) may transmit payment request information for the first payment service to the payment server (140) upon receiving information indicating that the user has agreed to pay the payment amount of the target item according to the first payment service. According to one embodiment, the payment request information for the first payment service may include at least one of information about the target item, information about the payment amount of the target item, or information about a payment means for the first payment service.

[0177] In S2606, the payment server (140) may perform a procedure to pay the payment amount of a target item using a payment means for the first payment service based on payment request information for the first payment service, and as a result of the procedure, transmit payment approval information for the first payment service to the device (120). According to one embodiment, the payment approval information for the first payment service may include payment details of the target item according to the first payment service.

[0178] In S2607, the device (120) can generate order completion information (2200) for the first payment service based on payment approval information for the first payment service. According to one embodiment, the order completion information (2200) for the first payment service may include payment details of a target item according to the first payment service.

[0179] In S2608, the device (120) can transmit order completion information (2200) for the first payment service to the user terminal (110).

[0180] In S2609, the device (120) can transmit order completion information (2200) for the first payment service to the store terminal (130).

[0181] According to the process (2600), the order acceptance and payment status for the target item can be synchronized between the user terminal (110), the device (120), and the store terminal (130).

[0182] FIG. 27 is a diagram illustrating a process (2700) for processing order information according to one embodiment of the present disclosure. At least some of the operations of the process (2700) may be omitted.

[0183] In S2701, the device (120) can identify that the user's authentication information for the target application is invalid based on the order information for the target item received from the user terminal (110).

[0184] In S2702, the device (120) may identify that the user needs to select a target payment service as it identifies that the user's authentication information for the target application is invalid. According to one embodiment, the device (120) may identify that the user needs to select a target payment service based on order information for a target item received from the user terminal (110). According to one embodiment, the device (120) may identify whether there is a history of transmitting promotion information (1000) to the user terminal (110) as it identifies that the user needs to select a target payment service.

[0185] In S2703, the device (120) can transmit the promotion information (1000) to the user terminal (110) as it identifies that there is no history of transmitting the promotion information (1000) to the user terminal (110).

[0186] In S2704, the user terminal (110) identifies that the user has requested information regarding a payment method registered in the target application for the first payment service, and can perform an authentication procedure for the user regarding the target application. According to one embodiment, the user terminal (110) can transmit the user's authentication result regarding the target application to the device (120).

[0187] In S2705, the device (120) can identify the first payment service as the target payment service as it identifies that the user's authentication for the target application has been completed.

[0188] In S2706, the device (120) can transmit payment scheduled information (1600) for the first payment service to the user terminal (110) as the device identifies the first payment service as the target payment service. According to one embodiment, the device (120) can generate payment scheduled information (1600) for the first payment service by identifying at least one payment method registered in association with the user's account in the target application for the first payment service.

[0189] In S2707, the user terminal (110) can transmit information to the device (120) indicating that the user has agreed to pay the payment amount of the target item according to the first payment service.

[0190] In S2708, the device (120) may transmit payment request information for the first payment service to the payment server (140) upon receiving information indicating that the user has agreed to pay the payment amount of the target item according to the first payment service. According to one embodiment, the payment request information for the first payment service may include at least one of information about the target item, information about the payment amount of the target item, or information about a payment means for the first payment service.

[0191] In S2709, the payment server (140) may perform a procedure to pay the payment amount of a target item using a payment means for the first payment service based on payment request information for the first payment service, and as a result of the procedure, transmit payment approval information for the first payment service to the device (120). According to one embodiment, the payment approval information for the first payment service may include payment details of the target item according to the first payment service.

[0192] In S2710, the device (120) can generate order completion information (2200) for the first payment service based on payment approval information for the first payment service. According to one embodiment, the order completion information (2200) for the first payment service may include payment details of a target item according to the first payment service.

[0193] In S2711, the device (120) can transmit order completion information (2200) for the first payment service to the user terminal (110).

[0194] In S2712, the device (120) can transmit order completion information (2200) for the first payment service to the store terminal (130).

[0195] According to the process (2700), the order acceptance and payment status for the target item can be synchronized between the user terminal (110), the device (120), and the store terminal (130).

[0196] FIG. 28 is a diagram illustrating a process (2800) for processing order information according to one embodiment of the present disclosure. At least some of the operations of the process (2800) may be omitted.

[0197] In S2801, the device (120) can identify that the user's authentication information for the target application is invalid based on the order information for the target item received from the user terminal (110).

[0198] In S2802, the device (120) may identify that the user needs to select a target payment service as it identifies that the user's authentication information for the target application is invalid. According to one embodiment, the device (120) may identify that the user needs to select a target payment service based on order information for a target item received from the user terminal (110). According to one embodiment, the device (120) may identify whether there is a history of transmitting promotion information (1000) to the user terminal (110) as it identifies that the user needs to select a target payment service.

[0199] In S2803, the device (120) can transmit payment service list information (1100) to the user terminal (110) as it identifies that there is a history of transmitting promotion information (1000) to the user terminal (110).

[0200] In S2804, the user terminal (110) can identify that the user has selected the first payment service as the target payment service.

[0201] In S2805, the user terminal (110) can perform a user authentication procedure for the target application as it identifies that the user has selected the first payment service as the target payment service. According to one embodiment, the user terminal (110) can transmit the user authentication result for the target application to the device (120).

[0202] In S2806, the device (120) can identify the first payment service as the target payment service as it identifies that the user's authentication for the target application has been completed.

[0203] In S2807, the device (120) can transmit payment scheduled information (1600) for the first payment service to the user terminal (110) as the device identifies the first payment service as the target payment service. According to one embodiment, the device (120) can generate payment scheduled information (1600) for the first payment service by identifying at least one payment method registered in association with the user's account in the target application for the first payment service.

[0204] In S2808, the user terminal (110) can transmit information to the device (120) indicating that the user has agreed to pay the payment amount of the target item according to the first payment service.

[0205] In S2809, the device (120) may transmit payment request information for the first payment service to the payment server (140) upon receiving information indicating that the user has agreed to pay the payment amount of the target item according to the first payment service. According to one embodiment, the payment request information for the first payment service may include at least one of information about the target item, information about the payment amount of the target item, or information about a payment means for the first payment service.

[0206] In S2811, the payment server (140) may perform a procedure to pay the payment amount of a target item using a payment means for the first payment service based on payment request information for the first payment service, and as a result of the procedure, transmit payment approval information for the first payment service to the device (120). According to one embodiment, the payment approval information for the first payment service may include payment details of the target item according to the first payment service.

[0207] In S2812, the device (120) can generate order completion information (2200) for the first payment service based on payment approval information for the first payment service. According to one embodiment, the order completion information (2200) for the first payment service may include payment details of a target item according to the first payment service.

[0208] In S2813, the device (120) can transmit order completion information (2200) for the first payment service to the user terminal (110).

[0209] In S2814, the device (120) can transmit order completion information (2200) for the first payment service to the store terminal (130).

[0210] According to the process (2800), the order acceptance and payment status for the target item can be synchronized between the user terminal (110), the device (120), and the store terminal (130).

[0211] FIG. 29 is a diagram illustrating a process (2900) for processing order information according to one embodiment of the present disclosure. At least some of the operations of the process (2900) may be omitted.

[0212] In S2901, the device (120) can identify that the user's authentication information for the target application is invalid based on the order information for the target item received from the user terminal (110).

[0213] In S2902, the device (120) may identify that the user needs to select a target payment service as it identifies that the user's authentication information for the target application is invalid. According to one embodiment, the device (120) may identify that the user needs to select a target payment service based on order information for a target item received from the user terminal (110). According to one embodiment, the device (120) may identify whether there is a history of transmitting promotion information (1000) to the user terminal (110) as it identifies that the user needs to select a target payment service.

[0214] In S2903, the device (120) can transmit payment service list information (1100) to the user terminal (110) as it identifies that there is a history of transmitting promotion information (1000) to the user terminal (110).

[0215] In S2904, the user terminal (110) can identify that the user has selected the second payment service as the target payment service.

[0216] In S2905, the user terminal (110) can transmit payment scheduled information for the second payment service to the device (120) as it identifies that the user has selected the second payment service as the target payment service. According to one embodiment, the payment scheduled information for the second payment service may include at least one of information about the target item, information about the payment amount of the target item, or information indicating that the user has selected the second payment service as the target payment service.

[0217] In S2906, the device (120) can identify the second payment service as the target payment service based on payment schedule information for the second payment service.

[0218] In S2907, the user terminal (110) can transmit payment request information for the second payment service to the payment server (140). According to one embodiment, the payment request information for the second payment service may include at least one of information about a target item, information about the payment amount of the target item, or information about a payment means for the second payment service.

[0219] In S2908, the payment server (140) may perform a procedure to pay the payment amount of a target item using a payment method for the second payment service based on payment request information for the second payment service, and as a result of the procedure, transmit payment approval information for the second payment service to the user terminal (110). According to one embodiment, the payment approval information for the second payment service may include payment details of the target item according to the second payment service.

[0220] In S2909, the user terminal (110) can transmit the payment details of the target item according to the second payment service to the device (120).

[0221] In S2910, the device (120) may generate order completion information (2200) for the second payment service based on the payment history of the target item according to the second payment service. According to one embodiment, the second order completion information (2200) may include the payment history of the target item according to the second payment service.

[0222] In S2911, the device (120) can transmit order completion information (2200) for the second payment service to the user terminal (110).

[0223] In S2912, the device (120) can transmit order completion information (2200) for the second payment service to the store terminal (130).

[0224] According to the process (2900), the order acceptance and payment status for the target item can be synchronized between the user terminal (110), the device (120), and the store terminal (130).

[0225] FIG. 30 is a diagram illustrating a process (3000) for processing order information according to one embodiment of the present disclosure. At least some of the operations of the process (3000) may be omitted.

[0226] In S3001, the device (120) can identify that the user's authentication information for the target application is invalid based on the order information for the target item received from the user terminal (110).

[0227] In S3002, the device (120) may identify that the user needs to select a target payment service as it identifies that the user's authentication information for the target application is invalid. According to one embodiment, the device (120) may identify that the user needs to select a target payment service based on order information for a target item received from the user terminal (110). According to one embodiment, the device (120) may identify whether there is a history of transmitting promotion information (1000) to the user terminal (110) as it identifies that the user needs to select a target payment service.

[0228] In S3003, the device (120) can transmit payment service list information (1100) to the user terminal (110) as it identifies that there is a history of transmitting promotion information (1000) to the user terminal (110).

[0229] In S3004, the user terminal (110) can identify that the user has selected a third payment service as the target payment service.

[0230] In S3005, the user terminal (110) can transmit payment schedule information for the third payment service to the device (120) as it identifies that the user has selected the third payment service as the target payment service. According to one embodiment, the payment schedule information for the third payment service may include at least one of information about the target item, information about the payment amount of the target item, or information indicating that the user has selected the third payment service as the target payment service.

[0231] In S3006, the device (120) can identify the third payment service as the target payment service based on payment schedule information for the third payment service.

[0232] In S3007, as the device (120) identifies the third payment service as the target payment service, it can generate order completion information (2300) for the third payment service.

[0233] In S3008, the device (120) can transmit order completion information (2300) for the third payment service to the user terminal (110).

[0234] In S3009, the device (120) can transmit order completion information (2300) for the third payment service to the store terminal (130).

[0235] In S3010, the store terminal (130) can identify the payment method used by the user of the user terminal (110) to pay the payment amount of the target item at the counter of the target store according to the third payment service. According to one embodiment, the store terminal (130) can transmit the payment details of the target item according to the third payment service to the device (120) as the payment method used by the user of the user terminal (110) to pay the payment amount of the target item at the counter of the target store is identified as cash. For example, the device (120) can transmit the payment details of the target item according to the third payment service to the user terminal (110).

[0236] In S3011, the store terminal (130) can transmit payment request information for a third payment service to the payment server (140) as the payment method used by the user of the user terminal (110) to pay the payment amount of a target item at the counter of the target store is identified as a debit card or a deferred payment card. According to one embodiment, the payment request information for the third payment service may include at least one of information about the target item, information about the payment amount of the target item, or information about the payment method for the third payment service.

[0237] In S3012, the payment server (140) may perform a procedure to pay the payment amount of a target item using a payment method for the third payment service based on payment request information for the third payment service, and as a result of the procedure, transmit payment approval information for the third payment service to the store terminal (130). According to one embodiment, the payment approval information for the third payment service may include payment details of the target item according to the third payment service.

[0238] In S3013, the store terminal (130) can transmit the payment details of the target item according to the third payment service to the device (120).

[0239] According to the process (3000), the order acceptance and payment status for the target item can be synchronized between the user terminal (110), the device (120), and the store terminal (130).

[0240] FIG. 31 is a drawing illustrating a method (3100) according to one embodiment of the present disclosure. According to one embodiment, the method (3100) may be performed by a user terminal (110). At least some of the operations of the method (3100) may be omitted.

[0241] In S3110, the user terminal (110) can obtain a connection address for store information (400) that includes information about at least one item (440) sold at the target store.

[0242] In S3120, the user terminal (110) can identify whether the user's authentication information for the target application is valid by identifying a target item selected from a target table corresponding to the user terminal (110) within the target store among at least one item (440) sold at the target store.

[0243] In S3130, the user terminal (110) can generate order information for a target item based on the result of identifying whether the user's authentication information for the target application is valid.

[0244] In S3140, the user terminal (110) can transmit order information for the target item to the device (120).

[0245] FIG. 32 is a drawing illustrating a method (3200) according to one embodiment of the present disclosure. According to one embodiment, the method (3200) may be performed by a device (120). At least some of the operations of the method (3200) may be omitted.

[0246] In S3210, the device (120) can transmit store information (400) about the target store to the user terminal (110) of the user who visited the target store.

[0247] According to one embodiment, the store information (400) may include information about at least one item (440) sold at the target store.

[0248] According to one embodiment, the device (120) may receive a request for store information (400) from the user terminal (110) when transmitting store information (400) to the user terminal (110). For example, the request for store information (400) may include an access address for store information (400) obtained by the user terminal (110). For example, upon receiving the request for store information (400), the device (120) may identify the store information (400) based on the access address for store information (400). For example, the device (120) may transmit the identified store information (400) to the user terminal (110).

[0249] According to one embodiment, the access address for store information (400) may be encoded in at least one of an NFC device or a QR code located at a target table within a target store. For example, the access address for store information (400) may be obtained by a user terminal (110) from at least one of an NFC device or a QR code corresponding to a target table in a target store.

[0250] According to one embodiment, the access address for store information (400) may correspond to a target store visited by the user of the user terminal (110) among at least one store, and a target table where the user is located among at least one table within the target store. That is, the access address for store information (400) may be a URL uniquely generated for the target store and the target table.

[0251] According to one embodiment, store information (400) may include information about a target table. For example, information about a target table may include at least one of the number of user terminals corresponding to the target table or an identifier of the target table. For example, if the number of user terminals corresponding to the target table is at least two, information about the target table may further include a notification that at least two users are ordering together at the target table. For example, at least one item ordered at the target table may include an item selected by at least two users at the target table.

[0252] In S3220, the device (120) can receive order information for at least one target item ordered from a target table corresponding to a user terminal (110) within the target store among at least one item sold at the target store.

[0253] According to one embodiment, order information for at least one target item may include at least one of information for at least one target item, information for the payment amount of at least one target item, or information indicating whether the user's authentication information for the target application is valid. For example, if the user's authentication information for the target application is valid, the order information for at least one target item may further include information indicating the first payment service as the target payment service for paying the payment amount of at least one target item. For example, if the user's authentication information for the target application is invalid, the order information for at least one target item may further include information indicating that the user needs to select the target payment service.

[0254] In S3230, the device (120) can identify a target payment service for paying the payment amount of at least one target item.

[0255] In S3240, the device (120) can generate order completion information for at least one target item based on order information for at least one target item and a target payment service.

[0256] According to one embodiment, order completion information for at least one target item may include the order history of at least one target item and a notification that an order for at least one target item has been received at a target store.

[0257] According to one embodiment, the device (120) can transmit order completion information for at least one target item to at least one of a user terminal (110) or a store terminal (130).

[0258] According to one embodiment, the device (120) can identify whether user authentication information for a predetermined target application is valid for the first payment service when generating order completion information for at least one target item based on the target payment service.

[0259] For example, the device (120) may identify a first payment service as a target payment service as it identifies that the user's authentication information for the target application is valid. For example, the device (120) may generate order completion information (2200) for at least one target item based on the first payment service.

[0260] For example, the device (120) can identify whether there is a history of transmitting promotion information (1000) to the user terminal (110) that directs the first payment service as a recommended payment service, as it identifies that the user's authentication information for the target application is invalid. For example, the promotion information (1000) may include interface information (1013) for requesting information about a payment method registered in the target application for the first payment service. As the device (120) identifies that there is no history of transmitting the promotion information (1000) to the user terminal (110), it can transmit the promotion information (1000) to the user terminal (110). For example, the device (120) can obtain the user's authentication result for the target application based on the user's input information for the interface information (1013). For example, the device (120) can receive the user's authentication result for the target application based on the user's input information for the interface information (1013) from the user terminal (110). For example, the device (120) may identify a first payment service as a target payment service as the result of user authentication for a target application indicates that user authentication is complete. For example, as the device (120) identifies the first payment service as a target payment service, it may generate order completion information (2200) for at least one target item based on the first payment service.

[0261] For example, the device (120) may transmit payment request information for the first payment service to the payment server (140) in generating order completion information (2200) for at least one target item based on the first payment service. For example, the payment request information for the first payment service may include at least one of information about at least one target item, information about the payment amount of at least one target item, or information about a target payment method for paying the payment amount of at least one target item among at least one payment method registered in association with the user's account in the target application for the first payment service. For example, the device (120) may receive payment approval information for the first payment service from the payment server (140). For example, the payment approval information for the first payment service may include payment details of at least one target item according to the first payment service. Here, the payment details of at least one target item according to the first payment service may be the result of paying the payment amount of at least one target item using a target payment method according to the first payment service. For example, the device (120) can generate order completion information (2200) for at least one target item based on payment approval information for the first payment service.

[0262] According to one embodiment, the device (120) may generate order completion information (2200) for at least one target item based on a target payment service by identifying a second payment service as the target payment service when generating order completion information (2200) for at least one target item based on a target payment service. For example, when generating order completion information (2200) for at least one target item based on a second payment service, the device (120) may receive payment approval information for the second payment service from a payment server (140). For example, the payment approval information for the second payment service may include payment details for at least one target item according to the second payment service. For example, the device (120) may receive payment details for at least one target item according to the second payment service from a payment server (140). Here, the payment details for at least one target item according to the second payment service may be the result of paying the payment amount of at least one target item using a payment method selected by the user according to the second payment service. For example, the device (120) can generate order completion information (2200) for at least one target item based on payment approval information for the second payment service. For example, the device (120) can generate order completion information (2200) for at least one target item based on payment history of at least one target item according to the second payment service.

[0263] According to one embodiment, the device (120) can generate order completion information (2300) for at least one target item based on a target payment service by identifying a third payment service as the target payment service when generating order completion information for at least one target item based on a target payment service.

[0264] FIG. 33 is a drawing illustrating a method (3300) according to one embodiment of the present disclosure. According to one embodiment, the method (3300) may be performed by a store terminal (130). At least some of the operations of the method (3300) may be omitted.

[0265] In S3310, the store terminal (130) can receive order completion information for at least one target item ordered from a target table within the target store from the device (120).

[0266] According to one embodiment, if the target payment service for paying the payment amount of at least one target item is the first payment service, the order completion information for at least one target item may include the payment history of at least one target item according to the first payment service.

[0267] According to one embodiment, if the target payment service for paying the payment amount of at least one target item is a second payment service, the order completion information for at least one target item may include the payment history of at least one target item according to the second payment service.

[0268] According to one embodiment, if the target payment service for paying the payment amount of at least one target item is a third payment service, the order completion information for at least one target item may include the order details of at least one target item according to the third payment service.

[0269] In S3320, the store terminal (130) can output order completion information for at least one target item on the display.

[0270] FIG. 34 is a block diagram of a computing device (3400) according to one embodiment of the present disclosure. According to one embodiment, each of the user terminal (110), device (120), store terminal (130), and payment server (140) may be implemented as one or more computing devices (3400). For example, the computing device (3400) may be implemented as a computer, a laptop, a portable communication terminal (smartphone, etc.), a portable multimedia device, a wearable device, or an HMD, etc. For convenience of explanation, the description below will focus on one computing device (3400).

[0271] According to one embodiment, the computing device (3400) may include one or more processors (3410), one or more memories (3420), or a communication interface (3430). Meanwhile, some components may be removed from the computing device (3400), or other components (such as a display or input device) may be added to the computing device (3400). Additionally, some components may be implemented by being integrated or by being implemented as a single or multiple entity. In the present disclosure, one or more processors (3410) may be referred to as processors (3410). Unless the context clearly indicates otherwise, the term processors (3410) may mean a set of one or more processors. Also, in the present disclosure, one or more memories (3420) may be referred to as memories (3420). Unless the context clearly indicates otherwise, the term memories (3420) may mean a set of one or more memories. Alternatively, in the present disclosure, the term communication interface (3430) may mean a set of one or more communication circuits unless the context clearly indicates otherwise. At least some of the components inside and outside the computing device (3400) may be connected to each other via a bus, GPIO (general purpose input / output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface), etc., to exchange information (data, signals, etc.).

[0272] According to one embodiment, the processor (3410) may perform operations or information processing regarding the control or communication of each component of the computing device (3400). Specifically, the processor (3410) may control at least one component of the computing device (3400) connected to the processor (3410) by running software (or computer program) received from another component. As an example, the processor (3410) may load instructions (e.g., instructions, code, or code segments) or information into memory (3420), process instructions or information stored in memory (3420), and store result information resulting from the processing in memory (3420). Additionally, the processor (3410) may be operatively connected to the components of the computing device (3400) to perform various operations such as operations, processing, generation, or processing related to the present disclosure.

[0273] According to one embodiment, the memory (3420) may store various information. The information stored in the memory (3420) may include software, which is information acquired, processed, or used by at least one component of the computing device (3400). The software may include one or more instructions that cause the processor (3410) to perform operations according to various embodiments of the present disclosure when loaded into the memory (3420). That is, the processor (3410) may perform operations according to various embodiments of the present disclosure by executing the one or more of the aforementioned instructions. The memory (3420) may include, for example, volatile or non-volatile memory.

[0274] According to one embodiment, the program is software stored in memory (3420) and may include an operating system for controlling the resources of a computing device (3400), an application, or middleware that provides various functions to the application so that the application can utilize the resources of the computing device (3400).

[0275] According to one embodiment, the communication interface (3430) can establish a wired or wireless communication channel with another device and transmit and receive various information with the other device.

[0276] According to one embodiment, the communication interface (3430) may include at least one port for connecting to another device via a wired cable in order to communicate with another device via a wired cable. In this case, the communication interface (3430) may perform communication with another device connected via a wired cable through at least one port. According to one embodiment, the communication interface (3430) may include a cellular communication module and be configured to be connected to a cellular network (e.g., 3G, LTE, 5G, Wibro, or Wimax). According to one embodiment, the communication interface (3430) may include a short-range communication module and be able to transmit and receive information with another device using short-range communication (e.g., Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), UWB).

[0277] According to one embodiment, the communication interface (3430) may include a contactless communication module for contactless communication. Contactless communication may include at least one contactless proximity communication technology, such as, for example, NFC communication, RFID (Radio Frequency Identification) communication, or MST (Magnetic Secure Transmission) communication. In addition to the various examples described above, the computing device (3400) may be implemented in various known ways for communicating with other devices, and the scope of the present disclosure is not limited by the examples described above.

[0278] According to one embodiment, the computing device (3400) may include a display. The display may output a screen based on store information (400), item details (600), order target list information (900), promotion information (1000), payment service list information (1100), etc., based on the control of the processor (3410). For example, when the computing device (3400) receives information to output a specific screen, the processor (3410) may control the display to output the specific screen. In addition, to output a screen with various interfaces applied to the display, for example, a web browser or a dedicated application may be installed on the computing device (3400). Furthermore, the display may be configured to interact with a user and may receive user input from the user. Such a display may be implemented in the form of a touch sensor panel (TSP) capable of recognizing contact or proximity of various external objects (e.g., a user's finger or stylus).

[0279] According to one embodiment, the computing device (3400) may include an input device (e.g., a mouse or a keyboard). The input device may receive information to be used in a component of the computing device (3400) from outside the computing device (3400) (e.g., a user).

[0280] According to one embodiment, the computing device (3400) may include a camera. The camera can recognize a QR code and obtain information encoded in the QR code. For example, if an access address for the store information (400) of a target store is encoded in the QR code, the camera can obtain the access address for the store information (400) of the target store from the QR code.

[0281] The methods according to the present disclosure may be methods implemented by a computing device (3400) having a computer or a processor. In the present disclosure, each step of the methods is illustrated and described in a predetermined order, but the steps may be performed in an order that can be arbitrarily combined according to the present disclosure, in addition to being performed sequentially. According to one embodiment, at least some of the steps may be performed in parallel, iteratively, or heuristically. The present disclosure does not exclude changes or modifications to the methods. According to one embodiment, at least some of the steps may be omitted or other steps may be added.

[0282] Various embodiments of the present disclosure may be implemented as software recorded on a machine-readable recording medium. The software may be software for implementing the various embodiments of the present disclosure described above. The software may be inferred from the various embodiments of the present disclosure by programmers skilled in the art to which the present disclosure pertains. For example, the software may be a machine-readable instruction (e.g., code or code segment) or a program. The machine may be a device capable of operating according to instructions called from the recording medium, for example, a computer. According to one embodiment, the machine may be a computing device (3400) according to the embodiments of the present disclosure. According to one embodiment, the processor of the machine may execute the called instruction to cause the components of the machine to perform a function corresponding to the instruction. According to one embodiment, the processor may be a processor (3410) according to the embodiments of the present disclosure. The recording medium may mean a recording medium in which data is stored that can be read by the machine. The recording medium may include, for example, ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc. According to one embodiment, the recording medium may be a memory (3420). According to one embodiment, the recording medium may be implemented in a distributed form in a computer system connected by a network, etc. Software may be stored and executed in a distributed manner in a computer system, etc. The recording medium may be a non-transitory recording medium. A non-transitory recording medium refers to a tangible medium that exists regardless of whether data is stored semi-permanently or temporarily, and does not include a signal that is transmitted transitory.

[0283] Although the technical concept of the present disclosure has been described by various embodiments above, the technical concept of the present disclosure includes various substitutions, modifications, and alterations that can be made within the scope of understanding of those skilled in the art to which the present disclosure pertains. Furthermore, it should be understood that such substitutions, modifications, and alterations may be included within the scope of the appended claims. Embodiments according to the present disclosure may be combined with one another. Each embodiment may be combined in various ways depending on the circumstances, and embodiments created by combining also fall within the scope of the present disclosure.

Claims

1. One or more processors; and It includes one or more memories in which instructions executed by the above one or more processors are stored, and When executing the above instructions, the one or more processors, Store information regarding a target store is transmitted to a user terminal of a user who has visited the target store, and the store information includes information regarding at least one item sold at the target store. From the above user terminal, order information for at least one target item ordered from a target table corresponding to the user terminal within the target store among the at least one item is received, and Identifying a target payment service for paying the payment amount of at least one target item, and A device configured to generate order completion information for at least one target item based on the above order information and the above target payment service.

2. In Paragraph 1, The above one or more processors, in transmitting the store information to the user terminal, Receiving a request for the above store information from the above user terminal - the request for the above store information includes an access address for the above store information obtained by the above user terminal -, Based on the above access address, the store information for the above target store is identified, and A device configured to transmit the identified store information to the user terminal.

3. In Paragraph 2, The above access address is a device obtained by the user terminal from at least one of an NFC (near field communication) device or a QR code corresponding to the target table of the target store.

4. In Paragraph 3, The above connection address is a device corresponding to the target store among at least one store and the target table among at least one table within the target store.

5. In Paragraph 4, A device comprising the above store information, which includes information about the above target table.

6. In Paragraph 5, A device comprising information about the above target table including at least one of the number of user terminals corresponding to the above target table or the identifier of the above target table.

7. In Paragraph 6, A device in which, when the number of user terminals corresponding to the above target table is at least two, the information regarding the above target table further includes a notification that at least two users are placing an order together at the above target table.

8. In Paragraph 7, A device wherein the above at least one target item includes the above at least two user-selected items in the target table.

9. In Paragraph 1, A device comprising at least one of the order completion information for at least one target item, the order history of the at least one target item, or a notification that an order for the at least one target item has been received at the target store.

10. In Paragraph 1, The above one or more processors, A device configured to transmit order completion information for at least one target item to at least one of the user terminal or the store terminal of the target store.

11. In Paragraph 1, The above one or more processors, in generating the order completion information for the at least one target item based on the target payment service, With respect to the first payment service, it is configured to identify whether the user's authentication information for a predetermined application is valid, and The device, wherein the first payment service is a payment service that pays a payment amount for at least one target item using a payment method registered in association with the user's account in the application.

12. In Paragraph 11, The above one or more processors, As it is identified that the authentication information of the user for the above application is valid, the first payment service is identified as the target payment service, and A device further configured to generate order completion information for at least one target item based on the above-mentioned first payment service.

13. In Paragraph 11, The above one or more processors, Identifying whether there is a history of transmitting promotional information to the user terminal indicating the first payment service as a recommended payment service upon identifying that the user's authentication information for the application is invalid, and - the promotional information includes interface information for requesting information regarding a payment method registered in the application for the first payment service -, A device further configured to transmit the promotion information to the user terminal upon identifying that there is no history of transmitting the promotion information to the user terminal.

14. In Paragraph 13, The above one or more processors, Obtaining the user's authentication result for the application based on the user's input information regarding the interface information, and As the authentication result of the user for the above application indicates that the user's authentication is complete, the first payment service is identified as the target payment service, and A device further configured to generate order completion information for at least one target item based on the above-mentioned first payment service.

15. In Paragraph 14, The above one or more processors, in generating the order completion information for the at least one target item based on the first payment service, Transmitting payment request information for the first payment service to a payment server - the payment request information for the first payment service includes information about the at least one target item, information about the payment amount of the at least one target item, or information about a target payment method for paying the payment amount of the at least one target item among at least one payment method registered in the application for the first payment service -, Receiving payment approval information for the first payment service from the payment server, wherein the payment approval information for the first payment service includes payment details of at least one target item according to the first payment service, A device configured to generate order completion information for at least one target item based on payment approval information for the first payment service.

16. In Paragraph 1, The above one or more processors, in generating the order completion information for the at least one target item based on the target payment service, As the second payment service is identified as the target payment service, the system is configured to generate the order completion information for the at least one target item based on the second payment service, and The device, wherein the second payment service is a payment service that pays the payment amount of at least one target item using a payment method selected by the user.

17. In Paragraph 16, The above one or more processors, in generating the order completion information for the at least one target item based on the second payment service, Receiving payment approval information for the second payment service from the payment server - the payment approval information for the second payment service includes payment details of at least one target item according to the second payment service -, A device configured to generate order completion information for at least one target item based on payment approval information for the second payment service.

18. In Paragraph 1, The above one or more processors, in generating the order completion information for the at least one target item based on the target payment service, As the third payment service is identified as the target payment service, the system is configured to generate the order completion information for the at least one target item based on the third payment service, and The above third payment service is a payment service that pays the payment amount of at least one target item at the counter of the target store.

19. A method performed in a device comprising one or more processors and one or more memories storing instructions to be executed by said one or more processors, wherein One or more of the above processors, A step of transmitting store information regarding a target store to a user terminal of a user who has visited the target store - the store information includes information regarding at least one item sold at the target store -; A step of receiving order information from the user terminal regarding at least one target item ordered from a target table corresponding to the user terminal within the target store among the at least one item; A step of identifying a target payment service for paying the payment amount of at least one target item; and A method comprising the step of generating order completion information for at least one target item based on the above order information and the above target payment service.

20. A non-transient computer-readable recording medium having recorded instructions that cause one or more processors to perform an operation when executed by one or more processors, The above instructions cause the above one or more processors, Store information regarding a target store is transmitted to a user terminal of a user who has visited the target store, and the store information includes information regarding at least one item sold at the target store. From the above user terminal, order information for at least one target item ordered from a target table corresponding to the user terminal within the target store among the at least one item is received, and Identifying a target payment service for paying the payment amount of at least one target item, and A non-transient computer-readable recording medium that generates order completion information for at least one target item based on the above order information and the above target payment service.

Images