Method and device for determining payment device among multiple electronic devices

Abstract

A method and apparatus are disclosed in which an electronic device that does not have a payment function determines an electronic device that best suits the current situation among neighboring electronic devices that have a payment function, and the determined electronic device can be provided to a user. According to various embodiments, the system may include at least two electronic devices, each of which includes: a communication interface including a communication circuit; at least one processor operably connected to the communication interface; and at least one memory electrically connected to the processor, wherein the memory is configured to store instructions that, when executed by the processor, control one of the at least two electronic devices to: receive a first signal including information about a payment request and context information related to the first electronic device from a first electronic device through the communication interface, the first electronic device not having a payment function; in response to receiving the first signal, identify at least one second electronic device that has a payment function and is associated with a user account; send a second signal including information about the at least one second electronic device to the first electronic device through the communication interface; receive a third signal for selecting one of the at least one second electronic device through the communication interface; and send a fourth signal including information related to the payment to the selected second electronic device based at least in part on the third signal.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus capable of determining, among an electronic device without a payment function, a payment electronic device that is most suitable for a current situation among each adjacent electronic device that has a payment function (or is capable of performing payment). Background Art

[0002] With the development of digital technology, various types of electronic devices have been widely used, such as mobile communication terminals, smart phones, tablet personal computers (PCs), laptop computers, personal digital assistants (PDAs), wearable devices, digital cameras, smart speakers or various household appliances (for example, televisions (TVs), refrigerators, washing machines, purifiers, microwave ovens, or air purifiers).

[0003] The electronic device may be implemented in the form of a multifunctional multimedia device (multimedia player). For example, the electronic device may provide a call function such as a voice call or a video call, a message sending / receiving function such as a short message service (SMS) / multimedia message service (MMS) or an email, an electronic notepad function, an image capture function, a broadcast reproduction function, a moving image reproduction function, a music reproduction function, an Internet function, a messenger function, a game function, a social network service (SNS) function, and the like. Recently, the electronic device provides an electronic payment function including mobile payment. According to an embodiment, if a user purchases a product (or item) through online shopping (or Internet shopping) or home shopping, the user can use the electronic device to pay for the product through an electronic card (or application card) registered in an electronic payment service (or payment application).

[0004] However, if a user wishes to purchase a product while using an electronic device (e.g., a TV or tablet PC) that does not have a payment function (e.g., while watching a home shopping program or browsing an online shopping website), the user can use an external electronic device (or another electronic device) that can perform payment. For example, if a user wishes to purchase a product that is currently being sold in a home shopping program being broadcast on a TV, the user can use an electronic device that has a payment application installed. In this example, the user is inconvenienced in that the user needs to use the found electronic device to search for the relevant dealer and product again and continue the purchase. In addition, if there is no electronic device capable of performing payment around the user, the user is inconvenienced in that the user needs to personally move and find the relevant electronic device before using it. In addition, if there are multiple electronic devices capable of performing payment or multiple cards for payment, the user may not be able to easily identify the location of the relevant electronic devices or the various types of cards and easily select the appropriate electronic device or card. Therefore, although the user can make a purchase with a better offer (e.g., discount or points), the user may continue to pay without realizing it.

[0005] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the Invention

[0006] [Technical Issues]

[0007] Embodiments of the present disclosure provide a method and apparatus that allow multiple electronic devices to communicate with each other based on a user purchasing a product, thereby allowing the user to perform electronic payment through the electronic device that is most suitable for purchasing the product.

[0008] Another exemplary aspect of the present disclosure provides a method and apparatus that, if a user issues a payment request using a first electronic device, can select a second electronic device that is more suitable for product payment among adjacent electronic devices that can perform payment, thereby providing relevant information to the user.

[0009] Yet another exemplary aspect of the present disclosure provides a method and apparatus that, if the user purchases a product using an electronic device, enables a user to perform more efficient payment by providing the user with information about neighboring electronic devices that are more suitable for product payment.

[0010] [Technical solution]

[0011] According to an exemplary aspect of the present disclosure, a system may include at least two electronic devices, each electronic device including: a communication interface including a communication circuit; at least one processor operably connected to the communication interface; and at least one memory electrically connected to the processor, wherein the memory is configured to store instructions that, when executed by the processor, control one of the at least two electronic devices to: receive a first signal from a first electronic device through the communication interface, the first signal including information about a payment request and context information related to the first electronic device, the first electronic device not having a payment function; in response to receiving the first signal, identify at least one second electronic device that has a payment function and is associated with a user account; send a second signal including information about the at least one second electronic device to the first electronic device through the communication interface; receive a third signal for selecting one of the at least one second electronic device through the communication interface; and based at least in part on the third signal, send a fourth signal including information related to the payment to the selected second electronic device.

[0012] According to another exemplary aspect of the present disclosure, an electronic device may include: a communication interface including a communication circuit; a display; at least one processor operably connected to the display and the communication interface; and at least one memory electrically connected to the processor, wherein the memory is configured to store instructions that, when executed by the processor, control one of at least two electronic devices to: display content and a user interface on the display, the user interface being configured to receive a payment request related to the content; receive a first input related to the payment request through the user interface; send information related to the first input to an external server through the communication interface; receive a list of at least one external electronic device having a payment function and associated with a user account from the external server; display the list on the display; receive a second input for selecting an external electronic device from at least one external electronic device in the list; and send information about the second input to the external server through the communication interface.

[0013] According to another exemplary aspect of the present disclosure, a method for operating an electronic device may include: receiving a first signal from a first electronic device, the first signal including information about a payment request and context information related to the first electronic device, the first electronic device not having a payment function; in response to receiving the first signal, identifying at least one second electronic device that has a payment function and is related to a user account; sending a second signal including information about the at least one second electronic device to the first electronic device; receiving a third signal for selecting one of the at least one second electronic device through a communication interface; and sending a fourth signal including information related to the payment to the selected second electronic device based at least in part on the third signal.

[0014] In order to solve the above-mentioned technical problems, various exemplary embodiments may provide a computer-readable recording medium having recorded therein a program that, when executed by a processor, causes an electronic device or system to perform the method.

[0015] [Beneficial Effects]

[0016] According to various exemplary embodiments, if a user purchases a product online, the electronic device and its operating method allow multiple electronic devices to communicate with each other, thereby enabling the user to perform electronic payment through an electronic device suitable for purchasing the product. According to various exemplary embodiments, if a user uses one of the multiple electronic devices in a predetermined space to issue a payment request, the electronic device and its operating method can verify the adjacent electronic devices that can perform payment, and can select at least one payment electronic device that is more suitable for product payment among the electronic devices that can perform payment, thereby providing relevant information to the user through the electronic device that the user is using. Through this configuration, the user can easily verify information about the electronic device (or card) that can make product payments, and can select an electronic device that is more suitable for product payment to perform payment. According to various exemplary embodiments, information about the optimal and / or more suitable electronic device for payment can be provided through the electronic device used by the user, thereby solving the inconvenience caused by the user searching for electronic devices or moving. According to various exemplary embodiments, when the user makes an online product payment, the availability, convenience, accessibility and / or reliability of the electronic device can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0018] Figure 1 is a block diagram illustrating an electronic device in a network environment according to various embodiments;

[0019] Figure 2 is a block diagram illustrating an exemplary configuration of an external electronic device according to various embodiments;

[0020] Figure 3A is a diagram illustrating an exemplary network environment for providing payment according to various embodiments;

[0021] Figure 3B is a block diagram illustrating an exemplary configuration of a system for supporting electronic device payment according to various embodiments;

[0022] Figure 4 is a signal flow diagram illustrating exemplary operations for processing payment based on intercommunication between electronic devices according to various embodiments;

[0023] Figure 5 is a flowchart illustrating an exemplary method of operating an electronic device according to various embodiments;

[0024] Figure 6 is a flowchart illustrating an exemplary method of operating an electronic device according to various embodiments;

[0025] Figure 7 is a flowchart illustrating an exemplary method of operating an electronic device according to various embodiments;

[0026] Figure 8 is a system signal flow diagram illustrating exemplary operations for a payment service in a system according to various embodiments;

[0027] Figure 9 is a state transition diagram illustrating an example of determining priority of electronic devices to be used for payment in various embodiments;

[0028] Figure 10 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments;

[0029] Figure 11 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments;

[0030] Figure 12 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments;

[0031] Figure 13 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments; and

[0032] Figure 14 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments. Specific embodiments

[0033] Figure 1 is a block diagram illustrating an electronic device 101 in a network environment 100 according to various embodiments.

[0034] Reference Figure 1, the electronic device 101 in the network environment 100 can communicate with the electronic device 102 via the first network 198 (e.g., a short-range wireless communication network), or communicate with the electronic device 104 or the server 108 via the second network 199 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 101 can communicate with the electronic device 104 via the server 108. According to an embodiment, the electronic device 101 may include a processor 120, a memory 130, an input device 150, a sound output device 155, a display device 160, an audio module 170, a sensor module 176, an interface 177, a haptic module 179, a camera module 180, a power management module 188, a battery 189, a communication module 190, a subscriber identification module (SIM) 196, or an antenna module 197. In some embodiments, at least one of the components (e.g., the display device 160 or the camera module 180) may be omitted from the electronic device 101, or one or more other components may be added to the electronic device 101. In some embodiments, some of the components may be implemented as a single integrated circuit. For example, the sensor module 176 (eg, a fingerprint sensor, an iris sensor, or an illumination sensor) may be implemented as embedded in the display device 160 (eg, a display).

[0035] The processor 120 may run, for example, software (e.g., program 140) to control at least one other component of the electronic device 101 (e.g., a hardware component or a software component) connected to the processor 120, and may perform various data processing or calculations. According to one embodiment, as at least part of the data processing or calculation, the processor 120 may load a command or data received from another component (e.g., the sensor module 176 or the communication module 190) into the volatile memory 132, process the command or data stored in the volatile memory 132, and store the resultant data in the non-volatile memory 134. According to an embodiment, the processor 120 may include a main processor 121 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 123 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operationally independent of or combined with the main processor 121.

[0036] Additionally or alternatively, the auxiliary processor 123 may be adapted to consume less power than the main processor 121, or may be adapted to be specifically used for a designated function. The auxiliary processor 123 may be implemented separately from the main processor 121, or as part of the main processor 121. When the main processor 121 is in an inactive (e.g., sleep) state, the auxiliary processor 123 may control at least some of the functions or states associated with at least one component (e.g., the display device 160, the sensor module 176, or the communication module 190) among the components of the electronic device 101 (other than the main processor 121), or when the main processor 121 is in an active state (e.g., running an application), the auxiliary processor 123 may control at least some of the functions or states associated with at least one component (e.g., the display device 160, the sensor module 176, or the communication module 190) together with the main processor 121. According to an embodiment, the auxiliary processor 123 (eg, an image signal processor or a communication processor) may be implemented as part of another component (eg, the camera module 180 or the communication module 190 ) that is functionally related to the auxiliary processor 123 .

[0037] The memory 130 may store various data used by at least one component of the electronic device 101 (e.g., the processor 120 or the sensor module 176). The various data may include, for example, software (e.g., the program 140) and input data or output data for commands related thereto. The memory 130 may include a volatile memory 132 or a non-volatile memory 134.

[0038] The program 140 may be stored as software in the memory 130 , and may include, for example, an operating system (OS) 142 , middleware 144 , or applications 146 .

[0039] The input device 150 may receive commands or data from outside the electronic device 101 (e.g., a user) to be used by other components of the electronic device 101 (e.g., the processor 120). The input device 150 may include, for example, a microphone, a mouse, a keyboard, or a digital pen (e.g., a stylus).

[0040] The sound output device 155 can output sound signals to the outside of the electronic device 101. The sound output device 155 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as playing multimedia or records, and the receiver can be used for incoming calls. Depending on the embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0041] The display device 160 can visually provide information to the outside of the electronic device 101 (e.g., a user). The display device 160 may include, for example, a display, a holographic device, or a projector, and a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. Depending on the embodiment, the display device 160 may include a touch circuit adapted to detect a touch or a sensor circuit adapted to measure the strength of the force caused by the touch (e.g., a pressure sensor).

[0042] The audio module 170 can convert sound into an electrical signal, and vice versa. According to an embodiment, the audio module 170 can obtain sound via the input device 150, or output sound via the sound output device 155 or an earphone of an external electronic device (e.g., electronic device 102) directly (e.g., wired) or wirelessly connected to the electronic device 101.

[0043] The sensor module 176 can detect an operating state (e.g., power or temperature) of the electronic device 101 or an environmental state (e.g., a user's state) outside the electronic device 101, and then generate an electrical signal or data value corresponding to the detected state. Depending on the embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illumination sensor.

[0044] The interface 177 may support one or more specific protocols to be used to connect the electronic device 101 directly (e.g., wired) or wirelessly to an external electronic device (e.g., the electronic device 102). Depending on the embodiment, the interface 177 may include, for example, a High-Definition Multimedia Interface (HDMI), a Universal Serial Bus (USB) interface, a Secure Digital (SD) card interface, or an audio interface.

[0045] The connection end 178 may include a connector, wherein the electronic device 101 can be physically connected to an external electronic device (e.g., the electronic device 102) via the connector. Depending on the embodiment, the connection end 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0046] The haptic module 179 may convert the electrical signal into mechanical stimulation (eg, vibration or motion) or electrical stimulation that can be recognized by the user via his sense of touch or kinesthetic sense. According to an embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0047] The camera module 180 may capture still images or moving images. Depending on the embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

[0048] The power management module 188 may manage power supply to the electronic device 101. According to an embodiment, the power management module 188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0049] The battery 189 may power at least one component of the electronic device 101. According to an embodiment, the battery 189 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0050] The communication module 190 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (e.g., electronic device 102, electronic device 104, or server 108), and perform communication via the established communication channel. The communication module 190 may include one or more communication processors capable of operating independently from the processor 120 (e.g., an application processor (AP)) and supporting direct (e.g., wired) communication or wireless communication. Depending on the embodiment, the communication module 190 may include a wireless communication module 192 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules can communicate with an external electronic device via a first network 198 (e.g., a short-range communication network such as Bluetooth, Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA)) or a second network 199 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules can be implemented as a single component (e.g., a single chip), or these various types of communication modules can be implemented as multiple components separated from each other (e.g., multiple chips). The wireless communication module 192 can identify and authenticate the electronic device 101 in a communication network (such as the first network 198 or the second network 199) using user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 196.

[0051] Antenna module 197 can transmit or receive signals or power to or from the outside of electronic device 101 (e.g., an external electronic device). Depending on the embodiment, antenna module 197 may include an antenna comprising a radiating element formed of a conductive material or conductive pattern formed in or on a substrate (e.g., a PCB). Depending on the embodiment, antenna module 197 may include multiple antennas. In this case, at least one antenna suitable for the communication scheme used in a communication network (such as first network 198 or second network 199) may be selected from the multiple antennas by, for example, communication module 190 (e.g., wireless communication module 192). Signals or power can then be transmitted or received between communication module 190 and the external electronic device via the selected at least one antenna. Depending on the embodiment, additional components other than the radiating element (e.g., a radio frequency integrated circuit (RFIC)) may also be formed as part of antenna module 197.

[0052] At least some of the above components can be connected to each other via an inter-peripheral communication scheme (e.g., a bus, general-purpose input output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and communicatively transmit signals (e.g., commands or data) therebetween.

[0053] According to an embodiment, commands or data may be transmitted or received between the electronic device 101 and the external electronic device 104 via the server 108 connected to the second network 199. Each of the electronic device 102 and the electronic device 104 may be a device of the same type as the electronic device 101, or a device of a different type than the electronic device 101. According to an embodiment, all or some operations to be executed on the electronic device 101 may be executed on one or more of the external electronic device 102, the external electronic device 104, or the server 108. For example, if the electronic device 101 should automatically execute a function or service or should execute a function or service in response to a request from a user or another device, the electronic device 101 may request the one or more external electronic devices to execute at least part of the function or service instead of executing the function or service, or the electronic device 101 may request the one or more external electronic devices to execute at least part of the function or service in addition to executing the function or service. The one or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or execute another function or service related to the request, and transmit the result of the execution to the electronic device 101. The electronic device 101 may provide the result as at least a partial response to the request, either by further processing the result or without further processing the result. To this end, for example, cloud computing technology, distributed computing technology, or client-server computing technology may be used.

[0054] The electronic device according to various embodiments may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance. According to an embodiment of the present disclosure, the electronic device is not limited to those described above.

[0055] It should be understood that the various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features set forth herein to specific embodiments, but rather include various modifications, equivalents, or alternatives to the corresponding embodiments. For the description of the drawings, similar reference numerals may be used to refer to similar or related elements. It will be understood that a noun in the singular form corresponding to a term may include one or more things, unless the relevant context clearly indicates otherwise.

[0056] As used herein, each of phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B or C” may include any one or all possible combinations of the items listed with the corresponding one of the plurality of phrases. As used herein, terms such as “first” and “second” or “first” and “second” may be used to simply distinguish a corresponding component from another component and do not limit the components in other respects (e.g., importance or order). It will be understood that if an element (e.g., a first element) is referred to as being “combined with another element (e.g., a second element)”, “combined to another element (e.g., a second element)”, “connected with another element (e.g., a second element)”, or “connected to another element (e.g., a second element)”, when the term “operably” or “communicatively” is used or when the term “operably” or “communicatively” is not used, it means that the element can be directly (e.g., wired) connected to the other element, wirelessly connected to the other element, or connected to the other element via a third element.

[0057] As used herein, the term "module" may include units implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "portion," or "circuit"). A module may be a single integrated component adapted to perform one or more functions or the smallest unit or portion of the single integrated component. For example, depending on an embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0058] The various embodiments described herein can be implemented as software (e.g., program 140) comprising one or more instructions stored in a storage medium (e.g., internal memory 136 or external memory 138) that can be read by a machine (e.g., electronic device 101). For example, under the control of a processor, a processor (e.g., processor 120) of the machine (e.g., electronic device 101) can call at least one of the one or more instructions stored in the storage medium and execute the at least one instruction with or without the use of one or more other components. This enables the machine to be operable to perform at least one function according to the called at least one instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The machine-readable storage medium can be provided in the form of a non-transitory storage medium. The term "non-transitory" only means that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between data being semi-permanently stored in the storage medium and data being temporarily stored in the storage medium.

[0059] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be released in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or may be downloaded via an application store (e.g., Play Store). TM ) The computer program product may be published online (e.g., downloaded or uploaded) or may be distributed (e.g., downloaded or uploaded) directly between two user devices (e.g., smartphones). If published online, at least part of the computer program product may be temporarily generated or at least part of the computer program product may be at least temporarily stored in a machine-readable storage medium (such as a memory of a manufacturer's server, an application store's server, or a forwarding server).

[0060] According to various embodiments, each component (for example, module or program) in the above-mentioned components may include a single entity or multiple entities. According to various embodiments, one or more components in the above-mentioned components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (for example, module or program) may be integrated into a single component. In this case, according to various embodiments, the integrated component may still perform the one or more functions of each component in the multiple components in the same or similar manner as a corresponding component in the multiple components before integration. According to various embodiments, the operations performed by module, program or another component may be performed sequentially, in parallel, repeatedly or in a heuristic manner, or one or more operations in the operations may be run or omitted in different orders, or one or more other operations may be added.

[0061] Figure 2 is a block diagram illustrating an exemplary configuration of the external electronic device 201 according to various embodiments.

[0062] For example, Figure 2 It may be a block diagram showing the configuration of an electronic device 201 (eg, a TV, a tablet, or a PC) that does not have a payment function in various embodiments. Figure 2 The example shown in FIG. 1 is a diagram of an electronic device 201, but the electronic device 201 may include Figure 1 All or some of the components of the electronic device 101 shown. For example, the electronic device 201 may be Figure 1 The electronic devices 101 shown are of the same, similar or different types.

[0063] Reference Figure 2, the electronic device 201 may include a processor 210 (eg, including processing circuitry), a memory 220 , a communication interface 230 (eg, including communication circuitry), and a display 240 .

[0064] According to various embodiments, all or some of the operations of the processor 210, memory 220, communication interface 230, and display 240 of the electronic device 201 may correspond to Figure 1 Related components in the electronic device 101 (for example, Figure 1 The operation of the processor 120, memory 130, communication module 190 and display 160).

[0065] According to an embodiment, the processor 210 may be operably connected to the communication interface 230 and the display 240. According to an embodiment, the processor 210 may be electrically connected to the memory 220. According to an embodiment, the processor 210 may run software to control at least one of the other elements of the electronic device 201 connected to the processor 210 (e.g., a hardware element or a software element), and may process various types of data or perform various arithmetic operations. According to an embodiment, as at least some of the data processing operations or arithmetic operations, the processor 210 may load commands or data received from elements other than the processor 210 (e.g., the communication interface 230) into the memory 220, may process commands or data stored in the memory 220, and may store the data generated by the processing in the memory 220. In the following description, the processor is described as controlling various functions, it will be understood that the present disclosure is not limited to the processor directly controlling various functions. For example, the processor may control the electronic device (including its components) to perform various functions, and the present disclosure is not limited to the processor itself performing various functions.

[0066] According to various embodiments, the processor 210 may include various processing circuits and control the following operations: In response to a user's payment request, the processor 210 may obtain information about neighboring electronic devices that have payment functionality (or are capable of performing payment) from an external device (e.g., an external server) and provide (or display) the information. According to an embodiment, the processor 120 may control the electronic device to display a user interface on the display 240, the user interface configured to receive content and a payment request associated with the content. According to an embodiment, the processor 120 may control the electronic device to detect receipt of a first user input associated with the payment request via the user interface displayed on the display 240. According to an embodiment, the processor 120 may control the electronic device to, upon receipt of the first user input, transmit information associated with the first user input to the external server via the communication interface 230. According to an embodiment, the information associated with the first user input may include information regarding the user's payment request and contextual information associated with the electronic device 201. According to an embodiment, the processor 120 may control the electronic device to receive a list of at least one external electronic device associated with the user account and having payment functionality from the external server, and may display the received list on the display 240. According to an embodiment, if the received list is displayed on the display 240, the processor 120 may control the electronic device to: display the received list based on the priority associated with at least one external electronic device. According to an embodiment, the processor 120 may control the electronic device to: detect receipt of a second user input for selecting an external electronic device (e.g., Figure 1 Electronic device 101). According to an embodiment, the processor 120 may control the electronic device to: upon receiving the second user input, transmit information about the second user input to an external server via the communication interface 230. According to an embodiment, the information about the second user input may include information about an external electronic device selected from at least one external electronic device according to the second user input, and information related to payment of the selected external electronic device.

[0067] According to an embodiment, the memory 220 may store various data used by at least one element (eg, the processor 210) of the electronic device 201. The data may include, for example, software (eg, Figure 1 The memory 220 may include a volatile memory and / or a non-volatile memory. Depending on the embodiment, the memory 220 may store modules (e.g., processes or functions) configured to perform functions according to various embodiments, and the modules stored in the memory 220 may be executed by the processor 220.

[0068] According to an embodiment, the communication interface 230 may include various communication circuits and establish a wireless communication channel between the electronic device 201 and an external device (eg, an external server, an external electronic device, or a remote control device), and may perform wireless communication through the established communication channel.

[0069] According to an embodiment, the display 240 may visually provide (or display) information to an external portion (e.g., a user) of the electronic device 201. According to an embodiment, the display 240 may further include a touch circuit configured to detect a touch, or a sensor circuit configured to measure the magnitude of a force generated by a touch (e.g., a pressure sensor).

[0070] Figure 3A is a diagram illustrating an exemplary network environment for providing payment according to various embodiments.

[0071] exist Figure 3A In the embodiment, for the convenience of description, a floor plan (or structure) of a house interior is shown as an example, and a predetermined space in the house is shown as an example, and a plurality of electronic devices are placed at different locations (or positions) in the predetermined space. Figure 3A An example is shown, in which: a first electronic device 310 (eg, Figure 2 The electronic device 201 shown does not have a payment function, such as a TV, and the second electronic device 320 (eg, Figure 1 The electronic device 101 with a payment function shown, such as a smart phone, a wearable device or a tablet PC) is placed in a first space 301 (e.g., a living room); a third electronic device 330 (e.g., a smart phone, a wearable device or a tablet PC) is placed in a second space 302 (e.g., room 1); a fourth electronic device 340 (e.g., a smart phone, a wearable device or a tablet PC) is placed in a third space 303 (e.g., room 2); and a user 300 is in the first space 301.

[0072] According to an embodiment, Figure 3A In the embodiment, each of the first electronic device 310, the second electronic device 320, the third electronic device 330, and the fourth electronic device 340 can be owned and used by one user. The first electronic device 310, the second electronic device 320, the third electronic device 330, and the fourth electronic device 340 can be owned and used by at least two different users. One electronic device (for example, the first electronic device 310) among the various electronic devices can be used by multiple users. Figure 3A In the example, the first electronic device 310 may be shown as a device without a payment function (eg, Figure 2The second electronic device 201 of FIG. 20 is a first electronic device, and the second electronic device 320, the third electronic device 330 and / or the fourth electronic device 340 may be shown as devices with a payment function (eg, Figure 1 electronic device 101).

[0073] Figure 3A The following state may be shown, in which: in an environment where multiple electronic devices 310, 320, 330, and 340 are placed in a predetermined space, the first electronic device 310 provides (e.g., displays) content (e.g., home shopping broadcast content or online shopping network content) that allows the user 300 to purchase a product (e.g., an item); and the user 300 desires to purchase the product while using (e.g., watching) the first electronic device 310 (e.g., a TV).

[0074] According to various embodiments, as in the example of the first electronic device 310, if the user 300 pays via an electronic device that does not have a payment function (e.g., Figure 2 If the electronic device 201 shown in the figure, such as a payment request device, issues a payment request, an electronic device that can easily replace the above electronic device to perform payment (for example, a target electronic device for payment or a payment electronic device) can be determined among the multiple electronic devices 320, 330 and 340 with payment functions, and the payment can be completed through the determined electronic device (for example, Figure 1 The first electronic device 101) performs payment.

[0075] According to an embodiment, each user (e.g., user 300) may own multiple electronic devices (e.g., a smartphone and a tablet PC), and may register a card (e.g., a mobile card, an electronic card, or an application card, hereinafter referred to as an "electronic card") corresponding to a real payment card (e.g., a credit card or a physical card), or card information related to the real card (e.g., card company information, card name, card number, expiration date, authentication information (e.g., authentication number and fingerprint information), etc.) in at least one of the electronic devices owned by the user. According to an embodiment, the user 300 may register a card on an electronic device (e.g., Figure 1 A mobile payment application (or electronic payment application) is run in the electronic device 101), and payment can be performed by selecting an electronic card capable of performing payment based on the run application.

[0076] According to various embodiments, while using a first electronic device 310 that does not have a payment function (e.g., watching a shopping home program), in order to purchase a specific product, the user 300 may select (or input) to purchase a product provided (or displayed) by the first electronic device 310. For example, the user 300 may request product payment by, for example but not limited to, operating a remote controller (not shown) wirelessly connected to the first electronic device 310, or request product payment by performing a touch input on a payment button displayed by the first electronic device 310. According to an embodiment, the electronic device 101 (e.g., Figure 3A The second electronic device 320 shown, such as a smartphone or tablet PC, can be used to act as a remote control configured to remotely control the first electronic device 310. For example, the electronic device 101 can include an application (or function) capable of controlling the first electronic device 310, as in the case of a remote control. As an example, the user 300 can use the electronic device 101 to select (or touch) to purchase a product provided by the first electronic device 310.

[0077] According to various embodiments, if the first electronic device 310 receives (or detects) a payment request from a user, the first electronic device 310 allows payment to proceed through one of the plurality of adjacent electronic devices 320, 330, and 340 that have a payment function (or are capable of performing payment), instead of the first electronic device 310 itself. According to embodiments, in response to the user's payment request, the first electronic device 310 may transmit a signal (or message) to a server (not shown) requesting verification of at least one electronic device capable of performing payment (or having a payment function) (hereinafter referred to as a "payment-capable device"). According to embodiments, the signal (or message) requesting verification of the payment-capable device may include, for example, but not limited to, the user's input information for the payment request and contextual information related to the first electronic device 310. According to embodiments, the contextual information may include, for example, but not limited to, at least one of the following: information about the product to be paid (e.g., product code, product type, product amount, and product distributor), information about the payment amount, information about the user account registered with the first electronic device 310, information about the location (or position) of the first electronic device 310 in space, and the like.

[0078] According to various embodiments, the server may configure a candidate group of payment electronic devices for payment among the plurality of electronic devices 320, 330, and 340, or may indicate a device from which a payment electronic device may be selected (or determined) among the plurality of electronic devices. According to an embodiment, the server may identify an electronic device capable of performing payment (or having a payment function) among the plurality of electronic devices 320, 330, and 340, may generate a list of the identified electronic devices, and may transfer the generated list to the first electronic device 310. According to an embodiment, the server may select a payment electronic device from the identified candidate group of payment electronic devices, and may transfer information about the selected electronic device to the first electronic device 310.

[0079] In various exemplary embodiments, the server may include a device such as, but not limited to, a central control device, a hub, an artificial intelligence (AI) device (e.g., an AI speaker), a cloud server (or account server), etc., which may function to collect information related to payment (e.g., whether payment can be performed, card information, and user account information) from multiple adjacent electronic devices to generate a candidate group of payment electronic devices or determine the role (or function) of the payment electronic device. According to an embodiment, the server may include an internal server placed in the same space as the electronic devices 310, 32, 330, 340 (hereinafter referred to as electronic devices 310 to 340) are placed, or an external server placed outside the space where the electronic devices 310 to 340 are placed. According to an embodiment, the internal server may use, for example, a separate central control device or one electronic device as the central server. According to an embodiment, the external server is a server located anywhere externally (e.g., on the Internet), and may include, for example, but not limited to, a cloud server, an account server, a service server, a network server, etc. In various embodiments, one of the electronic devices 310 to 340 in the same space may be implemented to act as a server, an electronic device (e.g., the first electronic device 310) that detects a payment request from a user among the various electronic devices may be implemented to act as a server, or a separate server may be implemented to act as a server.

[0080] According to various embodiments, among multiple electronic devices capable of performing payment, the server may determine the priority of the payment electronic device based on various conditions (for example, the location of the electronic device, its status, the discount rate of the registered card, etc.), may generate a list including at least one payment electronic device based on the priority, and may provide the generated list to the first electronic device 310.

[0081] According to various embodiments, the first electronic device 310 may receive a list from the server and may display the received list on a display. According to an embodiment, if a user selects (or designates) a payment electronic device from the list displayed on the display, the first electronic device 310 may transmit a signal (or message) to the server requesting payment to be performed by the selected electronic device.

[0082] According to various embodiments, in response to receiving a signal requesting payment from the first electronic device 310, the server allows the corresponding payment electronic device to continue (execute) the payment. For example, the server may send various pieces of information related to the product payment (e.g., product information, payment amount, and mutual information) and a signal including a command for controlling the payment execution to the payment electronic device.

[0083] In various embodiments, one of the electronic devices 310 to 340 in the same space (e.g., the first electronic device 310 that receives a payment request from the user, or an external electronic device (or other electronic devices 320, 330, and 340)) may be implemented to act as a server.

[0084] According to an embodiment, in an example where the payment electronic device is a third electronic device 330 placed in the second space 302, in response to receiving a command for controlling payment execution from the server, the third electronic device 330 may run an electronic payment application (or mobile payment application, hereinafter referred to as the "payment application") and may perform a payment procedure based on the running payment application. According to an embodiment, the user 300 may perform payment by selecting an electronic card capable of performing payment based on the payment application run by the third electronic device 330.

[0085] According to various embodiments, an operation of determining a payment electronic device among a plurality of electronic devices to perform payment will be described in more detail below with reference to the following drawings.

[0086] Figure 3B is a block diagram illustrating an exemplary configuration of a system for making payments by an electronic device according to various embodiments.

[0087] Reference Figure 3B In various exemplary embodiments, a system for making payments by an electronic device may include, for example, a first electronic device 310, a second electronic device 320, a server (e.g., a cloud server) 350, a payment agent server 360, a payment server 370 (e.g., including a card company server 380 and an authentication server 390), and the like.

[0088] According to an embodiment, Figure 3B, the first electronic device 310 may be shown as an electronic device that does not have a payment function (or in which no payment application is installed, or in which information about available payment cards is not registered), for example, Figure 2 electronic device 201 or Figure 3A The first electronic device 310.

[0089] According to an embodiment, Figure 3B Examples of the second electronic device 320 may include, for example but not limited to, a device that can run an electronic payment application (e.g., Samsung HPay TM According to an embodiment, the second electronic device 320 may refer to, for example, all kinds of devices (e.g., Figure 1 The electronic device 101 of the second electronic device 320 may include information about a card company that has issued a physical card and an electronic card (or an application card, etc.), and / or information about a financial company that has issued a physical card and an electronic card (or an application card, etc.). According to an embodiment, the second electronic device 320 may be functionally connected to the server 350 via an application installed therein. For example, the second electronic device 320 may send payment-related information to / receive payment-related information from the server 350 via a payment application running thereon. According to an embodiment, the server 350 may send payment-related information to / receive payment-related information from the payment agent server 360 that is functionally connected to the server 350.

[0090] In various embodiments, the first electronic device 310 and the second electronic device 320 may be devices managed by a user account.

[0091] According to an embodiment, the payment application executed by the second electronic device 320 may provide a user interface (UI) and user experience (UX) corresponding to electronic payment. For example, a user may register one or more electronic cards through the payment application, and the second electronic device 320 may provide information about the registered cards and / or various user interfaces related to proceeding with payment using the cards.

[0092] According to an embodiment, the server 350 may determine a payment-capable device that can perform payment among a plurality of electronic devices, and may provide information about the determined payment-capable device, or a list including information about the determined payment-capable device, to the first electronic device 310 that has issued a payment request. According to an embodiment, if the first electronic device 310 selects an electronic device (e.g., a payment electronic device selected from payment-capable devices), the server 350 may determine the selected payment-capable device as a payment electronic device (e.g., the second electronic device 320), and may control the relevant payment electronic device (e.g., the second electronic device 320) to continue payment-related procedures. In various embodiments, the server 350 may refer to, for example, a device that can be connected to an adjacent electronic device and can communicate with and control the connected adjacent electronic device, such as, for example, but not limited to, a central control device, a hub, an artificial intelligence device, a cloud server, etc.

[0093] In various embodiments, the server 350 may store a unique identifier of the second electronic device 320 and information about the user account, and may pre-register and manage card information (e.g., card name, card number, expiration date, and card usage information) corresponding to at least one card used by the user (or registered in the second electronic device 320). According to various embodiments, the server 350 may store and manage information about other accounts associated with the user (e.g., family accounts and group accounts), and may store and manage related payment data. According to an embodiment, the server 350 may relay card information for payment between the second electronic device 320 and the payment proxy server 360. According to an embodiment, the server 350 may communicate with the payment proxy server 360 via a wireless communication channel, and may communicate with the first electronic device 310 and the second electronic device 320 via a direct (e.g., wired) communication channel or a wireless communication channel.

[0094] According to an embodiment, the payment proxy server 360 may be, for example, a device configured to perform payment on behalf of (or in a manner related to) the second electronic device 320 based on at least the payment information regarding the second electronic device 320 received from the server 350. According to an embodiment, if the payment proxy server 360 performs payment on behalf of the second electronic device 320, the payment proxy server 360 may communicate with the server 350 and may thus send or receive an authentication request and an authentication response related to the second electronic device 320 to or from the server 350, or may send or receive payment-related information to or from the server 350.

[0095] According to an embodiment, the external server 370 may include, for example, a card company server 380 and an authentication server 390 (eg, a Fast Identity Online (FIDO) server).

[0096] According to an embodiment, the card company server 380 may be, for example, a server actually operated by the card company, and may store and manage each user's personal card information. According to an embodiment, the card company server 380 may issue a card to the user (or the second electronic device 320) and may manage the issued card. According to an embodiment, the card company server 380 may be connected to another server (e.g., a financial server (not shown), a purchase server (not shown) or a token server) in a wired or wireless manner. According to an embodiment, the card company server 380 may issue (e.g., a one-time issue or when registering a card) and manage tokens for electronic payment services. In an embodiment, the token may replace unique card information (primary account number (PAN)). In one embodiment, the token may be generated using bank identification information (bank identification number (BIN)). According to an embodiment, the token server (not shown) may send a token used for authentication related to the user's (or the second electronic device 320) payment to the card company server 380 and / or the payment proxy server 360.

[0097] According to an embodiment, the authentication server 390 may, for example, be a server associated with user authentication. According to an embodiment, if the authentication server 390 proceeds with a payment associated with the second electronic device 320, the authentication server 390 may process user authentication based on biometric information (e.g., registered fingerprint information, registered iris information, etc.) (or based on biometric authentication). According to an embodiment, the authentication server 390 may perform user authentication based on at least one authentication scheme, such as, but not limited to, a PIN-based authentication scheme, an online authentication scheme (e.g., a scheme such as a carrier authentication scheme), an online biometric authentication scheme (e.g., Fast Identity Online (FIDO)), etc. According to an embodiment, the authentication server 390 may transmit the authentication result related to the user (or second electronic device 320)'s payment to the card company server 380 and / or the payment proxy server 360. According to an embodiment, the authentication server 390 may be connected to a financial server (not shown) or a purchase server (not shown) in a wired or wireless manner. According to various embodiments, the card company server 380 and the authentication server 390 may be implemented as an integrated server 370 or may be implemented separately.

[0098] As described above, the system according to various exemplary embodiments (e.g., Figure 1 electronic device 101, Figure 3B Server 350, and Figure 4 The server 420 may include at least one electronic device and at least one server, each of the electronic device and the server including: a communication interface including a communication circuit (eg, Figure 1 communication module 190); at least one processor (e.g., Figure 1 processor 120), operatively connected to the communication interface; and at least one memory electrically connected to the processor 120 (e.g., Figure 1 130), wherein the memory 130 is configured to store instructions that, when executed by the processor 120, control the electronic device or server to: receive a first signal from the first electronic device through the communication interface, the first signal including information about the user's payment request and a signal corresponding to a first electronic device that does not have a payment function (e.g., Figure 2 electronic device 201, or Figure 4 In response to receiving the first signal, identifying at least one second electronic device (e.g., Figure 1 electronic device 101, or Figure 3A or Figure 4 the second electronic device 430); transmitting a second signal including information about at least one second electronic device to the first electronic device 410 through the communication interface; receiving a third signal for selecting one of the at least one second electronic device through the communication interface; and transmitting a fourth signal including payment-related information to the selected second electronic device (e.g., Figure 4 a second electronic device 430).

[0099] According to various exemplary embodiments, when the instructions are executed by the processor 120, they may control the electronic device or server to: identify at least one second electronic device having a payment function and associated with a user account among a plurality of adjacent electronic devices based on at least one second electronic device being identified, at least in part based on contextual information associated with the first electronic device.

[0100] According to various exemplary embodiments, when the instructions are executed by the processor 120, they may control the electronic device or server to: identify at least one second electronic device having a payment function among a plurality of adjacent electronic devices based on at least one second electronic device being identified, at least in part based on contextual information associated with the at least one second electronic device.

[0101] According to various exemplary embodiments, the context information related to the at least one second electronic device may include at least one of the following information: information about a device location of the at least one second electronic device; information about a device status thereof; and card information about a registered card.

[0102] According to various exemplary embodiments, the context information related to the first electronic device may include: information about a device location of the first electronic device; and information about an account of a user registered in the first electronic device.

[0103] According to various exemplary embodiments, when the instructions are executed by the processor 120, they may control the electronic device or server to: send at least one request related to determining a payment device to at least one second electronic device based on receiving a first signal from the first electronic device; and receive a response corresponding to the request.

[0104] According to various exemplary embodiments, when the instructions are executed by the processor 120 , they may control the electronic device or the server to identify at least one second electronic device based on whether a response corresponding to the request has been received.

[0105] According to various exemplary embodiments, the instructions, when executed by the processor 120 , may control the electronic device or the server to determine a priority of the at least one second electronic device based at least in part on a response corresponding to the request.

[0106] According to various exemplary embodiments, when the instructions are executed by the processor 120 , they may control the electronic device or the server to generate a list including information about payment-capable devices based on the determined priorities.

[0107] According to various exemplary embodiments, the third signal may include: information about a final payment electronic device selected by the user through the first electronic device among at least one second electronic device; and information related to payment by the final payment electronic device.

[0108] As described above, the electronic device 201 (eg, Figure 2 electronic device 201 or Figure 4 The first electronic device 410 may include: a communication interface including a communication circuit (eg, Figure 2 communication interface 230); a display (eg, Figure 2 display 240); at least one processor (e.g., Figure 2 processor 210), operatively connected to the display and the communication interface; and at least one memory (e.g., Figure 2 ), electrically connected to the processor 210, wherein the memory 220 is configured to store instructions that, when executed by the processor 210, control the electronic device to: display content and a user interface configured to receive a payment request related to the content on a display; receive a first input related to the payment request through the user interface; send information related to the first input to an external server through a communication interface; receive a list of at least one external electronic device that has a payment function and is related to a user account from the external server; display the list on the display; receive a second input for selecting an external electronic device from at least one external electronic device on the list; and send information about the second input to the external server through the communication interface.

[0109] According to various exemplary embodiments, the instructions, when executed by the processor 210, may control the electronic device to: send information about the second input to an external server based on information about the second input, send information about the second input, the information about the second input including information about an external electronic device selected based on the second input from at least one external electronic device and information related to payment of the external electronic device.

[0110] According to various exemplary embodiments, the instructions, when executed by the processor 210 , may control the electronic device to display the list based on a priority associated with at least one external electronic device based on the list being displayed.

[0111] According to various exemplary embodiments, the instructions, when executed by the processor 210, may control the electronic device to: send information related to the first input based on information related to the first input being sent, the information related to the first input including information related to the payment request and context information related to the electronic device.

[0112] Figure 4 is a signal flow diagram illustrating exemplary operations for processing payment based on intercommunication between electronic devices according to various embodiments.

[0113] Figure 4 An exemplary configuration may be shown in which a user is using a first electronic device 410 (eg, Figure 2 The electronic device 210 such as a TV shown in FIG. 210 is used to watch (or use) content related to product sales (eg, home shopping or Internet shopping). Figure 4 In the example, the first electronic device 410 may be an electronic device (eg, TV) that does not have a payment function (eg, a payment application (or cannot perform payment)). Figure 4 An example is shown in which, among a plurality of electronic devices having a payment function (or capable of performing payment), a second electronic device 430 (eg Figure 1 The electronic device 101) is used as the payment electronic device for product payment, so the second electronic device 430 continues to make payment.

[0114] Reference Figure 4In operation 401, the first electronic device 410 may verify whether to execute payment. According to an embodiment, a user using content related to purchasing a product using the first electronic device 410 may request the first electronic device 410 to make a product payment in order to purchase the related product. For example, the user may make a payment request by, for example, but not limited to, manipulating and selecting a payment button displayed on the first electronic device 410 via an external electronic device (e.g., a remote control or electronic device that connects to the first electronic device 410 and operates as a remote control according to a specific scheme); selecting a physical / software payment button provided on the external electronic device; directly touching the payment button displayed on the first electronic device 410; etc. According to an embodiment, as in the above example, the first electronic device 410 may detect the payment request in response to user input for selecting a predetermined payment button. According to an embodiment, if the first electronic device 410 is connected to an artificial intelligence (AI) service, the user may input a voice command (e.g., "Buy the product currently being reproduced (or currently being displayed)"), and the first electronic device 410 may detect the payment request by performing voice recognition of the user's voice command.

[0115] In operation 403, if the first electronic device 410 detects an input, for example, from a user requesting payment for a product in the content, the first electronic device 410 may transmit a request for verifying an electronic device capable of performing payment (hereinafter referred to as a "payment-capable device") to the server 420. According to an embodiment, in order to proceed with the payment, the first electronic device 410 may transmit information about at least one user account through which the user is currently logged into the first electronic device 410 (or at least one user account pre-registered in the first electronic device 410) together with the payment request.

[0116] In operation 405, if server 420 receives a request from first electronic device 410 to verify a payment-capable device, server 420 may verify the payment-capable device based on the received information about the user account. According to embodiments, the information used by server 420 to verify the payment-capable device may include, for example, but not limited to: information about electronic devices registered in the user account that are capable of performing payments (or have payment functions); information about registered cards; information about the current status of the electronic device (e.g., the current status of the device, whether the device is powered on or off, or whether the device is currently in use); information about the current location of the electronic device (e.g., the current device location); and the like. According to embodiments, in operation 407, server 420 may verify the device status information of second electronic device 430 based on a device status request and a device status response associated with second electronic device 430. According to embodiments, to determine the current device status, server 420 may send a device status request to a payment-capable device (e.g., second electronic device 430) determined (or identified) based on the user account of the user of first electronic device 410, and may receive a response corresponding to the request. According to various embodiments, the server 420 may expand the payment-capable devices to be verified even to payment-capable devices registered in another account (e.g., a family account or a group account) associated with the user account of the user of the first electronic device 410. According to another embodiment, the server 420 may send a request for information for verifying the device status to other adjacent payment-capable devices, and may receive a response corresponding to the request, if necessary.

[0117] In operation 409, the server 420 may generate a list of electronic devices capable of performing payment. According to an embodiment, the server 420 may verify at least one electronic device capable of performing payment based on at least information for verifying a payment-capable device, and may generate a list of verified electronic devices (e.g., payment-capable devices). According to an embodiment, the list may be generated with information about the priority of the payment-capable devices and / or card information, or in an order according to the priority. According to an embodiment, if there is one payment-capable device, the list may notify the first electronic device 410 that the relevant electronic device can perform payment, and the relevant payment-capable device may immediately generate a notification to allow the user to immediately proceed with payment.

[0118] In operation 411 , the server 420 may transmit the generated list to the first electronic device 410 .

[0119] In operation 413, if the first electronic device 410 receives the list from the server 420, the first electronic device 410 may display the list on a display so that the user can verify the payment-capable device. According to an embodiment, if the list is displayed, the first electronic device 410 may display the payment-capable device and / or card information according to the configured priority.

[0120] In operation 415, in response to a user input selecting (or specifying) a payment-capable device (e.g., a target electronic device for payment), the first electronic device 410 may select (or determine) a final electronic device (e.g., a payment electronic device) to be used for payment in place of the first electronic device 410. In some embodiments, the user may select one of the payment-capable devices provided in a list. For example, the list displayed by the first electronic device 410 may include information regarding the payment-capable devices. For example, the list may display information regarding the payment-capable devices, such as, but not limited to: the type of electronic device (or owner of the payment-capable device); the location of the payment-capable device; the cards registered with the payment-capable device; and the applicable discount rate for the card. In some embodiments, the user may determine the payment electronic device to be used for payment based on the information regarding the payment-capable devices in the list. The user may then select the determined payment electronic device using the first electronic device 410 or a remote controller connected to the first electronic device 410. In some embodiments, if the list is provided based on card information, the user may also select a payment electronic device in the card section.

[0121] In operation 417, the first electronic device 410 may request the server 420 to make a payment based on the information of the selected electronic device. According to an embodiment, the first electronic device 410 may transmit information corresponding to the payment electronic device selected by the user or card information selected by the user to the server 420, and may request payment to be made by an electronic device matching the corresponding information.

[0122] In operation 419, if the server 420 receives information about the payment electronic device from the first electronic device 410, the server 420 may determine the electronic device corresponding to the received information (e.g., the second electronic device 430) as the payment electronic device, and may request the determined electronic device (e.g., the second electronic device 430) to proceed with the payment.

[0123] In operation 421, the second electronic device 430 may display a payment processing screen on a display in response to receiving a payment request from the server 420. According to an embodiment, the second electronic device 430 may run a mobile payment application (or electronic payment application) and may display a screen related to payment processing (or user interface) based on the run mobile payment application.

[0124] In operation 423, the second electronic device 430 may continue the payment process in response to the user input (or operation) on the screen related to payment processing. According to an embodiment, the second electronic device 430 may continue the payment process related to payment, including, for example but not limited to: displaying the payment screen for the product selected by the first electronic device 410; displaying various pieces of information related to the user's payment input on the payment screen; and executing authentication related to payment based on the various pieces of input information.

[0125] According to various embodiments, the server 420 may provide the list to the first electronic device 410 and simultaneously may pre-send a payment request to all payment-capable devices included in the list. In this example, the user may verify which electronic device in the list is to be used to perform the payment and may immediately proceed with the prepared payment processing procedure simply by using user authentication (e.g., fingerprint authentication or iris authentication) of the corresponding electronic device.

[0126] Figure 5 is a flowchart 500 illustrating an exemplary method of operating an electronic device according to various embodiments.

[0127] According to an embodiment, Figure 5 An example is shown in which the electronic device 101 acts as a device (e.g., a server or system) configured to: receive a payment request from an external electronic device; and select a payment electronic device to provide relevant information to the external electronic device in response to the payment request.

[0128] Reference Figure 5 In operation 501, the processor 120 (eg, at least one processor including a processing circuit and / or an operation memory (eg, Figure 1 The memory 130) enables the processor 120 to operate the instructions) to control the electronic device to receive a first signal from the first electronic device, the first signal including information about the user (for example, Figure 1 The first electronic device may be an electronic device that does not have a payment function (e.g., Figure 2 electronic device 201, or Figure 3A The first electronic device 310, or Figure 4 According to an embodiment, through a communication interface (eg, Figure 1The communication module 190 of the first electronic device 101 is used, the processor 120 can control the electronic device to receive a first signal from the first electronic device, the first signal including, for example, but not limited to: an input (for example, a first input) for requesting verification of a payment electronic device, the payment electronic device being used for payment related to content displayed on a display of the first electronic device that does not have a payment function; and first context information related to the first electronic device. According to an embodiment, the first context information related to the first electronic device may include, for example, but not limited to, at least one of the following information: information about a product to be paid for; information about a payment amount; information about a user account registered in the first electronic device; information about a location (or position) of the first electronic device in space, etc. According to an embodiment, the communication interface may be provided in the housing of the electronic device 101, and may be configured to be electrically connected to an antenna of the electronic device 101 to support a communication protocol.

[0129] In operation 503, the processor 120 may control the electronic device to identify at least one second electronic device (e.g., a payment electronic device) having a payment function. According to an embodiment, if a first signal is received, the processor 120 may identify that the first electronic device has requested verification of the payment electronic device based on the first input of the first signal, and may identify at least one second electronic device based on the first context information. According to an embodiment, if a first signal is received from a first electronic device, the processor 120 may control the electronic device to verify a user account based on the first context information associated with the first electronic device, and may identify at least one second electronic device associated with the user account and having a payment function from among a plurality of adjacent electronic devices. According to an embodiment, if at least one second electronic device is identified, the processor 120 may control the electronic device to identify at least one second electronic device having a payment function from among a plurality of adjacent electronic devices based at least in part on the context information associated with the at least one second electronic device (hereinafter referred to as "second context information"). According to an embodiment, the second context information associated with the at least one second electronic device may include, for example, but not limited to, at least one piece of information selected from device status information, device location information, registration card information, and the like.

[0130] In operation 505, the processor 120 may control the electronic device to transmit a second signal including information about at least one second electronic device (e.g., information about a payment electronic device) to the first electronic device. Depending on an embodiment, the processor 120 may control the electronic device to generate a list including information about the at least one identified second electronic device and may transmit the generated list to the first electronic device. Depending on an embodiment, if one second electronic device has been identified, the processor 120 may control the electronic device to immediately transmit information about the relevant second electronic device to the first electronic device. Depending on an embodiment, if multiple second electronic devices have been identified, the processor 120 may control the electronic device to generate a list based on information about at least two second electronic devices and may transmit the list to the first electronic device. Depending on an embodiment, if a list is generated, the processor 120 may control the electronic device to generate the same list so that the at least two second electronic devices are arranged (or placed) according to their priority order. Depending on an embodiment, the information about the payment electronic device may include, for example, but not limited to, at least one of the following: identification information of the relevant electronic device (e.g., user name, device name, and phone number), card information registered in the relevant electronic device, discount information based on the card information, and points (or accumulation) information based on the card information.

[0131] In operation 507, the processor 120 may control the electronic device to receive a third signal from the first electronic device for selecting one of the at least one second electronic devices. Depending on an embodiment, the processor 120 may control the electronic device to receive, via a communication interface, a third signal sent by the first electronic device in response to user input, the third signal being used by the user to select a second electronic device (e.g., a final payment electronic device) from the at least one second electronic device. Depending on an embodiment, the third signal may include, for example, but not limited to, information regarding the final payment electronic device used for payment (e.g., the second electronic device selected by the user via the first electronic device) and information requesting the selected second electronic device to execute the payment. Depending on an embodiment, the third signal may also include, for example, but not limited to, payment information related to the payment. Depending on an embodiment, the payment information related to the payment may not be included in the third signal, but may instead be configured by the electronic device 101 (or processor 120) based on at least a portion of the previously received first context information. For example, the processor 120 may control the electronic device to configure payment information including information about the product to be paid (e.g., product code, product type, product amount, and product distributor), as well as the payment amount from the first context information.

[0132] In operation 509, the processor 120 may control the electronic device to transmit a fourth signal including payment-related information to the selected second electronic device based at least in part on the third signal. According to an embodiment, if the third signal including information regarding payment by the selected second electronic device is received from the first electronic device, the processor 120 may control the electronic device to transmit a fourth signal including payment request information and payment information to the second electronic device via the communication interface.

[0133] Figure 6 is a flowchart 600 illustrating an exemplary method of operating an electronic device according to various embodiments.

[0134] According to an embodiment, Figure 6 An example is shown in which the electronic device 101 is a device (e.g., a server or system) configured to: receive a payment request from an external electronic device; and select a payment electronic device in response to the payment request to provide relevant information to the external electronic device. According to an embodiment, Figure 6 An example of the operation of the electronic device 101 for selecting a payment electronic device and generating a list is shown.

[0135] Reference Figure 6 In operation 601, the processor 120 (eg, at least one processor including a processing circuit and / or an operation memory (eg, Figure 1 The memory 130) and the instructions for the processor 120 to operate may control the electronic device to receive a first signal from the first external electronic device for requesting an electronic device capable of performing payment. According to an embodiment, the first external electronic device may refer to an electronic device that does not have a payment function (e.g., Figure 2 electronic device 201, or Figure 3A The first electronic device 310, or Figure 4 According to an embodiment, through a communication interface (eg, Figure 1 The processor 120 may control the electronic device to receive a signal from the first external electronic device, including, for example, but not limited to, an input requesting verification of a payment electronic device for payment related to content displayed on a display of the first external electronic device that does not have a payment function; and contextual information related to the first external electronic device. According to an embodiment, the contextual information related to the first external electronic device may include, for example, but not limited to, at least one of the following: information about a product to be paid; information about a payment amount; information about a user account registered with the first external electronic device; information about the location (or position) of the first external electronic device in space; and the like.

[0136] In operation 603, the processor 120 may control the electronic device to determine a second external electronic device capable of performing payment. According to an embodiment, the processor 120 may control the electronic device to determine at least one second external electronic device (e.g., Figure 3A According to an embodiment, the processor 120 may control the electronic device to determine an electronic device that is associated with the user account and can perform payment. According to an embodiment, the processor 120 may control the electronic device to verify the electronic device capable of performing payment based on at least the following information, such as but not limited to: information about the electronic device that can perform payment and is registered in the user account; information about the card registered therein; information about the current state of the external electronic device (for example, whether the external device is turned on or off, or whether the external electronic device is currently in use); information about the current location of the external electronic device, etc.

[0137] In operation 605, the processor 120 may determine a configured priority criterion. Depending on the embodiment, the priority criterion may be configured to be, for example, but not limited to, one or a combination of at least two of the following: device status; card payment benefits (e.g., discount rate and cumulative amount); device location; user preferences (e.g., frequently used cards or electronic devices for payment); etc.

[0138] In operation 607, the processor 120 may determine a candidate electronic device capable of performing payment from the second external electronic device based on a priority criterion. According to an embodiment, the processor 120 may control the electronic device to determine at least one second external electronic device that meets the priority criterion as a candidate group (or candidate electronic device) of payment electronic devices from the second external electronic devices.

[0139] In operation 609, the processor 120 may control the electronic device to determine information about the candidate electronic device. According to an embodiment, information about the second external electronic device capable of performing payment may be pre-registered in the electronic device 101. According to an embodiment, information about the second external electronic device may be registered separately for each user account. According to an embodiment, information about the second external electronic device may not be pre-registered in the electronic device 101, and the electronic device 101 (or the processor 120) may collect (or obtain) information about the second external electronic device in the operation of determining the second external electronic device. For example, the processor 120 may control the electronic device to request the second external electronic device to provide information about the second external electronic device, and may obtain information from the second external electronic device in response to the information provision request. According to an embodiment, the information about the candidate electronic device may include, for example, at least one of the following information: identification information of the relevant electronic device (e.g., user name, device name, and phone number), card information registered in the relevant electronic device, discount information based on the card information, and points (or accumulation) information based on the card information.

[0140] In operation 611, the processor 120 may control the electronic device to generate a list of electronic devices capable of performing payment based on the information about the candidate electronic devices. According to an embodiment, if the list is generated, the processor 120 may include multiple pieces of information about the candidate electronic devices in the list, and the information about the candidate electronic devices may be arranged (or placed) in order of their priority.

[0141] In operation 613 , the processor 120 may control the electronic device to transmit a second signal related to the list to the first external electronic device.

[0142] Figure 7 is a flowchart 700 illustrating an exemplary method of operating an electronic device according to various embodiments.

[0143] According to an embodiment, Figure 7 An example is shown in which the electronic device 201 is a device configured to perform the following operations (eg, Figure 2 electronic device 201 or Figure 3A The first electronic device 310 or Figure 4 The first electronic device 410 of the embodiment of the present invention comprises: sending a payment request to a first external electronic device (e.g., a server or a system); receiving information about at least one second external electronic device (e.g., a payment electronic device) capable of performing payment from the external electronic device; and displaying the payment request on a display (e.g., Figure 2 The received information is displayed on the display 240).

[0144] Reference Figure 7In operation 701, the processor 210 of the electronic device 201 (eg, at least one processor including a processing circuit, or an operating memory (eg, Figure 2 The memory 220) enables the processor 210 to operate the instructions) to control the electronic device to display ( Figure 2 The user interface of the electronic device 201 displayed on the display 240 and configured to receive a payment request related to the content is displayed on the display 240. According to an embodiment, the user interface displayed by the electronic device 201 on the display 240 will be described in more detail with reference to the accompanying drawings.

[0145] In operation 703, the processor 210 may control the electronic device to receive a first user input related to a payment request through the user interface. According to an embodiment, the first user input may include allowing the user (e.g., Figure 3A The first user input may include an input that allows the user (e.g., a user 300) to select a payment key provided (or displayed) on the display 240 of the electronic device 201 by manipulating an external electronic device (e.g., a remote controller) connected to the electronic device 201. Figure 3A The user 300) directly selects (eg, touches) an input of a payment button provided (or displayed) on the display 240 of the electronic device 201.

[0146] In operation 705, the processor 210 may control the electronic device to communicate with the user through a communication interface (eg, Figure 2 The communication module 230 of the electronic device 201 transmits information related to the first user input to an external server. Depending on an embodiment, the information related to the first user input may include information about the user's payment request and contextual information related to the electronic device 201. Depending on an embodiment, the contextual information related to the electronic device 201 may include at least one of the following: information about the product to be paid (e.g., product code, product type, product price, and product distributor); information about the payment amount; information about the user account registered with the electronic device 201; information about the location (or position) of the electronic device 201 in space, etc.

[0147] In operation 707, the processor 210 may control the electronic device to receive a list of at least one external electronic device with a payment function from an external server. Depending on an embodiment, the at least one external electronic device with a payment function may be an electronic device associated with a user account. Depending on an embodiment, the external server may determine the user account based at least in part on the context information transmitted by the electronic device 201, and may transmit a list of external electronic devices associated with the user account that can perform payment.

[0148] In operation 709, the processor 210 may control the electronic device to display a list on the display 240. According to an embodiment, the processor 210 may display the list received from the external server on at least a partial area of the display 240 (for example, a partial area or an edge area of the screen) or the entire area of the screen. According to an embodiment, if the list is displayed, the processor 210 may control the electronic device to display information about at least one external electronic device arranged in an order according to priority. According to an embodiment, the processor 210 may control the electronic device to display the list to cover the content (or user interface) displayed on the display 240 by the electronic device 201, may display the list to cover with the content (or user interface) being displayed, or may display the list and the content on separate split screens.

[0149] In operation 711, the processor 210 may control the electronic device to receive a second user input for selecting an electronic device from the list. According to an embodiment, the second user input may include allowing the user (eg, Figure 3A The user 300) selects an input of information about an external electronic device (or an item (or object) including information) of the list by manipulating an external electronic device (e.g., a remote controller) connected to the electronic device 201. According to an embodiment, the second user input may include an input that allows the user (e.g., Figure 3A An input of information of an external electronic device (or an item (or object) including information) of a list provided (or displayed) on the display 240 of the electronic device 201) is directly selected (eg, touched).

[0150] In operation 713, the processor 210 may control the electronic device to send the information about the second user input to the external server through the communication interface. According to an embodiment, the information about the second user input may include information about the final payment electronic device used for payment (e.g., an external electronic device selected by the user), and information for requesting the selected external electronic device to perform the payment. According to an embodiment, the information about the second user input may also include payment information related to the payment. According to an embodiment, the payment information related to the payment may not be included in the information about the second user input, but may be configured by the external server based at least in part on context information related to the electronic device 201. For example, the external server may configure payment information in the context information, the payment information including information about the product to be paid (e.g., product code, product type, product amount, and product dealer) and the payment amount.

[0151] Figure 8 is a system signal flow diagram 800 illustrating exemplary operations for a payment service in a system according to various embodiments.

[0152] According to an embodiment, Figure 8An example of an operation scenario for providing a payment service based on intercommunication between electronic devices is shown.

[0153] like Figure 8 As shown, the system according to various embodiments may include a first electronic device 810, a payment server 820, a payment proxy server 830, a server 840, a second electronic device 850, and a card company server 860. According to an embodiment, the first electronic device 810 may be a device without a payment function (e.g., Figure 2 The electronic device 201), and the second electronic device 850 may refer to, for example, at least one device having a payment function (or capable of performing payment), for example, Figure 1 electronic device 101. According to an embodiment, the server 840 may include an internal server placed in the same space as the electronic devices 810 and 850, or an external server placed outside the space where the electronic devices 810 and 850 are placed. For example, the server 840 may include devices such as, but not limited to, a central control device, a hub, an AI device (e.g., an AI speaker), a cloud server (or an account server), etc., which may serve to collect payment-related information (e.g., whether payment can be performed, card information, and user account information) from multiple electronic devices to generate a candidate group of payment electronic devices or determine the role (or function) of the payment electronic device. According to an embodiment, one of the electronic devices 810 and 850 in the same space (e.g., a device configured to receive a payment request from a user, or the first electronic device 810) may be implemented to act as the server 840.

[0154] Reference Figure 8 In operation 801, the first electronic device 810 may determine whether to make a payment. According to an embodiment, it can be assumed that the first electronic device 810 may be, for example, a TV, and a user desires to purchase a specific product while viewing content related to product sales (e.g., home shopping) through the first electronic device 810. According to an embodiment, while viewing the content, the user may input on a payment screen provided on the display of the first electronic device 810, or may touch a payment button assigned to a remote controller, etc., thereby transmitting a payment request to the first electronic device 810 to purchase the product.

[0155] In operation 803, if the first electronic device 810 detects a user input requesting payment related to a product in the content currently being displayed (or reproduced), the first electronic device 810 may send a request to the server 840 to verify an electronic device capable of performing payment (hereinafter referred to as a "payment-capable device"). Depending on an embodiment, the first electronic device 810 may transmit information (e.g., a user key or a globally unique identifier (GUID)) related to the user account through which the user is currently logged into the first electronic device 810 (or a user account pre-stored in the first electronic device 810). With this configuration, the server 840 can verify the payment-capable device and / or card information associated with the user account. Depending on an embodiment, the GUID may be an identifier that can be used alone to identify a specific object (e.g., an electronic device). Depending on an embodiment, the server 840 may search for a payment-capable device that has payment functionality and is associated with the user account based on the GUID. Depending on an embodiment, the server 840 may manage electronic devices for each user account. This configuration is shown as an example in Table 1 below.

[0156] [Table 1]

[0157]

[0158]

[0159] In an embodiment, Table 1 may refer to an example of information managed by the server 840. As shown in Table 1, Table 1 shows an example of registering three accounts in the server 840. For example, the server 840 may store account information related to a first user account (e.g., test1@samsung.com), a second user account (e.g., son1@sam.com), and a third user account (e.g., wife@sung.com).

[0160] According to an embodiment, at least one payment-capable device with a payment function may be registered for each account. For example, a first device and a second device may be registered in a first user account, a third device may be registered in a second user account, and a fourth device and a fifth device may be registered in a third user account. For example, the at least one payment-capable device with a payment function may be managed based on the user account.

[0161] According to an embodiment, a user account-specific payment device may be managed based on a device identifier (device ID) uniquely assigned to the corresponding payment device, and a GUID may be assigned to each user account. In various embodiments, the GUID may represent information about the user key assigned to each user account.

[0162] According to an embodiment, the registration card may include card information about the card registered in each payment-capable device. According to an embodiment, the card information may include a single unique number (or code) such as a device ID, and may also include the card type, card name, etc. According to an embodiment, the card information may also include information about card-specific discount rates and / or points accumulation, etc., and these pieces of information may be obtained from the card company server 860 for updating. According to an embodiment, a payment-capable device may have one or more pieces of card information registered therein.

[0163] According to an embodiment, the server 840 may store account information related to a group account (e.g., a family account). According to an embodiment, the server 840 may verify the card information registered in the payment-enabled device of the account associated with the GUID and the account of a group member (e.g., another user), thereby providing the payment-enabled device and card information that allow the user to perform payment.

[0164] In various embodiments, the information managed by the server 840 based on the account is not limited to the example in Table 1, and may also include various additional information, or some information may be omitted. For example, the information managed by the server 840 may include location information (or position information) of each device.

[0165] In operation 805, the server 840 may determine the device status of an electronic device that is capable of performing payment and is associated with a user account based on a request for the device status (e.g., whether the device is powered on or off, whether the device is currently being used, or the current location (or place) of the device) and a response thereto. According to an embodiment, in order to determine the current device status of a payment-capable device determined (or identified) based on the user account of the first electronic device 810, where the current device status may be, for example, whether the device is powered on or off, whether the device is currently being used, or the current location (or place) of the device, the server 840 may request the determined device status of the payment-capable device. According to an embodiment, the server 840 may periodically verify the device status of the electronic device. For example, the electronic device may provide information about the device status to the server 840 at each set period, and the server 840 may periodically obtain (or collect) the device status of the electronic device without separately requesting an operation.

[0166] In operation 807, the server 840 may verify the payment-capable device (or recommended electronic device) for payment. According to an embodiment, if the server 840 receives a response in response to the device status request from each electronic device, the server 840 may determine the relevant electronic device as a payment-capable device. According to an embodiment, if the server 840 receives a response in response to the device status request from each electronic device, the server 840 may also verify the payment-capable device based on the response result (e.g., device status information and / or device location information) of the electronic device from which the response has been received. According to an embodiment, if the server 840 does not receive a response in response to the device status request from the relevant electronic device (e.g., if no response is obtained from the relevant electronic device), the server 840 may exclude the relevant electronic device from the payment-capable devices recommended to the user.

[0167] In operation 809, the server 840 may send information about the verified payment-capable device to the first electronic device 810. According to an embodiment, the server 840 may generate a list including information about at least one payment-capable device, and may send the generated list to the first electronic device 810. According to an embodiment, the server 840 may determine the priority of the payment-capable device and / or the card information about the card. According to an embodiment, the server 840 may determine the priority based on at least the following: the place (or position) where the payment-capable device is currently located; the discount rate at the time of card payment; the card with the recent payment history, etc. According to an embodiment, if the server 840 provides the information about the payment-capable device (or a list including information about the payment-capable device) to the first electronic device 810, the server 840 may provide information about the priority of the payment-capable device and / or the card information, or a list with an order according to the priority.

[0168] In operation 811, the first electronic device 810 may receive a list from the server 840 and may display the list including at least one payment-capable device (or information about a payment-capable device) on a display. According to an embodiment, if the list is displayed, the first electronic device 810 may display at least one payment-capable device and / or card information according to priority.

[0169] In operation 812 , the user may identify payment-capable devices based on the list displayed by the first electronic device 810 , and may select one payment-capable device as a payment electronic device (or target payment device) through which payment is to be performed according to user requirements.

[0170] In operation 813, if the user selects a payment electronic device, the first electronic device 810 may pass the order information to the payment server 820 (or billing server). According to an embodiment, the order information may include information related to the product that the user desires to purchase in the content displayed (or reproduced) by the first electronic device 810. According to an embodiment, the order information may include at least one of a product dealer, a product type, a product name, a product amount, or a payment amount. According to an embodiment, the first electronic device 810 may pass information (e.g., a user key or a GUID) related to the user account currently logged into the first electronic device 810 (or a user account pre-registered in the first electronic device 810). For example, the first electronic device 810 may provide the payment server 820 with information about which electronic device is to be used to perform the payment based on the GUID passed to the server 840 in operation 803.

[0171] In operation 815, the payment server 820 may transmit the payment information to the payment proxy server 830. According to an embodiment, the payment server 820 may transmit the payment information (e.g., the payment amount) regarding the order received from the first electronic device 810 to the payment proxy server 830. According to an embodiment, the payment proxy server 830 may be a server configured to operate an electronic payment settlement proxy service.

[0172] In operation 817, the payment proxy server 830 may transmit an authentication request for payment requested by the first electronic device 810 to the server 840 based on at least the payment information. According to an embodiment, the payment proxy server 830 may transmit the authentication request to the server 840 to obtain a unique ID for authenticating the payment request of the first electronic device 810.

[0173] In operations 819 and 821, the server 840 may send an authentication response to the payment proxy server 830 in response to the authentication request of the payment proxy server 830, and may call (e.g., push call) the second electronic device 850 so that the second electronic device 850 can perform payment. According to an embodiment, the server 840 may send a unique identifier for authenticating the payment request to the payment proxy server 830 as an authentication response corresponding to the authentication request of the payment proxy server 830. According to an embodiment, the server 840 may manage the electronic payment service executed by the second electronic device 850 (e.g., the payment application of the second electronic device 850).

[0174] Depending on the embodiment, the server 840 may transmit the payment-related information received from the payment proxy server 830 to the second electronic device 850, or may directly process the payment-related information. Depending on the embodiment, the server 840 may relay the payment authentication information included in the payment-related information. Depending on the embodiment, the server 840 may manage an electronic payment service account (e.g., a user account or a Samsung account); a unique ID of the second electronic device 850 (e.g., a device unique identifier (DUID)); or card information corresponding to a user using one or more cards in the electronic payment service account (e.g., card name, card number, expiration date, and information about the card used).

[0175] In operation 823, a user verification procedure may be performed. Depending on the embodiment, the user verification procedure may be performed based on at least one of the following authentication schemes: for example, a PIN-based authentication scheme, a biometric authentication scheme, an online authentication scheme (e.g., a scheme such as a carrier authentication scheme), and an online biometric authentication scheme (e.g., FIDO). Depending on the embodiment, the second electronic device 850 may perform biometric authentication using a biometric signal detected from the user. For example, the second electronic device 850 may scan the user's biometric information (e.g., fingerprint, iris, or face) using a biometric sensor (e.g., a fingerprint recognition sensor, an iris recognition sensor, or a facial recognition sensor) of the second electronic device 850, and may perform user authentication based on the scanned biometric information (e.g., an image). Depending on the embodiment, the second electronic device 850 may perform online biometric authentication (e.g., FIDO) together with the card company server 860 (or an authentication server, such as a FIDO server (not shown)). Depending on the embodiment, as a result of the biometric authentication, the authentication server (e.g., a FIDO server) may send random data to the second electronic device 850. In an embodiment, in order to perform authentication between the second electronic device 850, the server 840, and the card company server 860 (or an authentication server, such as a FIDO server), the random data may include data (e.g., a random number or a challenge) randomly generated by the card company server 840 (or the authentication server). For example, the second electronic device 850 and the authentication server (e.g., a FIDO server) may register a pre-agreed encryption key between them.

[0176] According to an embodiment, in operation 825, the second electronic device 850 may transmit a payment authentication request to the server 840 in response to a call from the server 840. According to an embodiment, the second electronic device 850 may receive random data as a result of online biometric authentication between itself and the authentication server, and may provide the received random data to the server 840. According to an embodiment, if the user authentication is completed (for example, if the user authentication is valid), the second electronic device 850 may transmit a payment authentication request including the authentication result (for example, signature data and random data) to the server 840.

[0177] According to an embodiment, in operation 827, the server 840 may transmit an authentication request of the user (or the second electronic device 850) related to the payment of the second electronic device 850 to the card company server 860. According to an embodiment, the server 840 may transmit the authentication request including the authentication result (e.g., random data) obtained from the second electronic device 850 to the card company server 860.

[0178] According to an embodiment, in operation 829, if the card company server 860 completes approval of the user's authentication request for payment through a predetermined authentication procedure, the card company server 860 may send a response to the authentication result (hereinafter referred to as an "authentication result response") to the server 840. According to an embodiment, in response to the authentication request from the server 850, the card company server 860 may send the random data obtained from the server 840 to the authentication server (e.g., a FIDO server) to verify the random data (or verify whether the random data is valid). If the authentication server determines that the random data is valid (e.g., the relevant random data is consistent with the random data provided to the second electronic device 850), the card company server 860 may send the authentication result response to the server 840. According to an embodiment, if the card company server 860 sends the authentication result response to the server 840, the card company server 860 may only send encrypted data that the card company server 860 can decrypt. According to an embodiment, the encrypted data may include, for example, a one-time card number (OTC), and the OTC may include a code whose validity can be verified by the card company server 860.

[0179] According to an embodiment, in operation 831, the server 840 may transmit the authentication result response received from the card company server 860 to the payment proxy server 830. According to an embodiment, if the server 840 transmits the authentication result response, the server 840 may transmit the authentication result response to the payment proxy server 830, the authentication result response including the unique ID of the second electronic device 850 and the encrypted data received from the card company server 860.

[0180] According to an embodiment, in operation 833, the payment proxy server 830 may verify the second electronic device 850 based on the unique ID and transmit an approval request (e.g., the unique ID) for payment by the second electronic device 850 to the card company server 860. According to an embodiment, if the payment proxy server 830 transmits the approval request, the payment proxy server 830 may transmit payment information and encrypted data to the card company server 860. According to an embodiment, a specific card company server may transmit an OTC (e.g., encrypted data) to the payment proxy server 830, and if the payment proxy server 830 requests approval of payment, the payment proxy server 830 may also transmit the OTC received from the specific card company server to the corresponding card company server.

[0181] According to an embodiment, in operation 835, if the card company server 860 completes the approval of the payment approval request through a predetermined authentication procedure, the card company server 860 may send a response to the payment (e.g., an approval response corresponding to the payment approval request, or an approval completion message indicating completion of the card approval) to the payment proxy server 830. According to an embodiment, the card company server 860 may decrypt the encrypted data received from the payment proxy server 830 and thereby determine whether the received encrypted data is valid. According to an embodiment, if the encrypted data that passes the decryption and validity determination procedures is valid, the card company server 860 may send a response to the approval result (e.g., payment approval) to the payment proxy server 830.

[0182] According to an embodiment, in operation 837 , the payment proxy server 830 may transmit a response to the approval result to the payment server 820 .

[0183] According to an embodiment, in operation 839, the payment server 820 may send a response to the approval result to the first electronic device 810. According to an embodiment, although Figure 8 Not shown, but if the first electronic device 810 receives a response to the approval result from the payment server 820, the first electronic device 810 can display the approval result on the display (for example, an approval completion message indicating that the card approval is completed, and card-related messages).

[0184] In various embodiments, Figure 8 An example of an operation scenario for a payment service system is shown, but the present disclosure is not limited thereto. Figure 8 In the embodiment, the payment server 820 may be included in the first electronic device 810 in the form of a software development kit (SDK), or may be implemented as follows: Figure 8In the example of FIG, the system may be configured as a separate element external to the first electronic device 810. According to an embodiment, the system may be configured such that the payment server 820 is omitted and the payment proxy server 830 communicates directly with the first electronic device 810. According to an embodiment, the system may be configured such that the card company server 860 includes the functionality of the payment proxy server 830, and the card company server 860 acts as the payment proxy server 830 to communicate directly with the first electronic device 810.

[0185] Figure 9 is a state transition diagram illustrating an example of prioritizing electronic devices to be used for payment in various embodiments.

[0186] like Figure 9 As shown, in various embodiments, the priority 900 of payment-capable devices having payment functionality and associated with a user account may be determined based on a combination of one or at least two of a device status basis 910, a device location basis 920, a preference basis 930, or a card information basis 940.

[0187] According to embodiments, the method for selecting payment-capable devices 900 may utilize, for example, the device status 910 of the payment-capable devices. For example, even if a card capable of making payments is registered with the payment-capable device, if the payment-capable device is powered off, payment cannot actually be made using the payment-capable device. According to various embodiments, if a server receives a request to verify a payment-capable device, the server may identify payment-capable devices capable of making payments in a user's account and verify the device status of the identified payment-capable devices. According to embodiments, the server may send a request for the current device status to at least one of the identified payment-capable devices and determine the device status of each payment-capable device based on whether a response has been received from each payment-capable device. According to embodiments, the server may determine that payment-capable devices from which no response has been received within a predetermined period of time (e.g., in a network unavailable state or powered off state) are payment-incapable devices and may exclude them from the payment-capable devices recommended to the user. According to embodiments, the device status of a payment-capable device may include, for example, whether the associated electronic device is currently in use (e.g., being used by another user or being busy). According to an embodiment, the server may determine that a payment-capable device that has sent a busy status is a device that cannot perform payment and may exclude it from the payment-capable devices recommended to the user. According to an embodiment, if one of the payment-capable devices acts as a remote control device (e.g., a remote controller) that is connected in a specific manner to an electronic device that reproduces content that can purchase products to control the relevant electronic device, the corresponding payment-capable device is likely to be near the user and has a high probability of being used by the user. In this example, the server may assign a higher priority to the corresponding payment-capable device than to other payment-capable devices.

[0188] According to an embodiment, the method for selecting a priority 900 for payment-capable devices may use, for example, the device location 920 of the payment-capable device. According to an embodiment, if a server receives a request to verify a payment-capable device, the server may identify a payment-capable device capable of performing payments in a user's account and verify the device location of the identified payment-capable device. According to an embodiment, the server may send a request for the current device location to at least one identified payment-capable device and determine the device location of each payment-capable device based on the response from each payment-capable device. According to an embodiment, if the server receives location information from a payment-capable device, the server may determine whether the corresponding payment-capable device is located indoors or outdoors. According to an embodiment, if the payment-capable device is located indoors, the server may verify the location or position of the corresponding payment-capable device (e.g., a living room, bedroom, or kitchen). If the corresponding payment-capable device is near (or around) the user (or the electronic device that has requested verification of the payment-capable device), the server may assign a higher priority to the corresponding payment-capable device.

[0189] According to an embodiment, the method for selecting the priority 900 of a payment-capable device may use, for example, a user preference 930 for a payment-capable device (or a user's usage history). According to an embodiment, the server may include information about payment-capable devices (e.g., preference information) pre-configured according to the user's preference level, and may assign a higher priority to an identified payment-capable device with a higher preference level based on the user's preference level. According to an embodiment, information about a user's usage history of an electronic device (or a usage history of a payment-capable device for payment) may be stored in the server and may be managed by the server. Based on the usage history, a higher priority may be assigned to an identified payment-capable device with a history of higher frequency of use.

[0190] According to an embodiment, the method for selecting the priority 900 of payment-capable devices may use, for example, card information 940. According to an embodiment, the server may determine a discount rate, accumulated points, card usage benefits, etc. based on the registered card information 940. According to an embodiment, the server may assign the highest priority to the card (or the electronic device in which the card is registered) that provides the highest benefits to the user based on the determination result.

[0191] In various embodiments, the method for selecting the priority of payment capable devices 900 is not limited to Figure 9, and various priority selection methods may be adopted based on at least the configuration of the electronic device 101 or the configuration of the user. According to various embodiments, if priority is selected, multiple selection methods may be adopted in a complex manner. For example, the server may configure the priority in consideration of a combination of one or at least two of the device status 910, the device location 920, the preference 930, and the card information 940. As an example, the server may select a payment device that can actually be used to perform payment among payment devices based on the device status 910, may determine the device location 920 of the selected payment device, and if the selected payment device is closer to the user, may configure a higher priority for the selected payment device. As another example, the server may configure a higher priority for a payment device that includes card information 940 about a card that provides the highest discount to the user when paying for a product among payment devices that can actually be used to perform payment, regardless of whether the payment device is near the user or the payment device is close to the user.

[0192] Figure 10 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments. Figure 11 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments.

[0193] According to an embodiment, Figure 10 An example of determining priority based on the device status of a payment capable device is shown. Figure 11 Shown based on Figure 10 An example of a list of related payment-capable devices is provided based on the priority determined in the example.

[0194] exist Figure 10 In the example, for ease of description, a floor plan (or structure) of a house is shown as an example, and a predetermined space inside the house is shown as an example, multiple electronic devices (1010, 1020, 1030, and 1040) are placed at various locations (or positions) in the predetermined space, and multiple users (e.g., a first user 1000A and a second user 1000B) are present. According to an embodiment, Figure 10 In the example shown, a first electronic device 1010 (e.g., a TV), a second electronic device 1020 (e.g., a smart phone, a wearable device, or a tablet PC), and a third electronic device 1030 (e.g., a smart phone, a wearable device, or a tablet PC) are placed in a first space 1001 (e.g., a living room); a fourth electronic device 1040 (e.g., a smart phone, a wearable device, or a tablet PC) is placed in a second space 1002 (e.g., a room); and a first user 1000A and a second user 1000B are in the first space 1001.

[0195] According to an embodiment, Figure 10 , each of the first electronic device 1010, the second electronic device 1020, the third electronic device 1030, and the fourth electronic device 1040 may be owned and used by one user. Alternatively, the first electronic device 1010, the second electronic device 1020, the third electronic device 1030, and the fourth electronic device 1040 may be owned and used by at least two different users, respectively. One of the electronic devices (e.g., the first electronic device 1010) may be used in common by multiple users. According to an embodiment, Figure 10 An example is shown, in which: the first electronic device 1010 refers to a device without a payment function; the second electronic device 1020, the third electronic device 1030 or the fourth electronic device 1040 refers to a device with a payment function; and the second electronic device is used by the second user 1000B (e.g., busy state).

[0196] Reference Figure 10 , while using content displayed by the first electronic device 1010 (for example, watching a home shopping program), the first user 1000A desires to purchase a specific product, and may send a payment request to the first electronic device 1010 based on at least one of the above-mentioned schemes for requesting payment. According to an embodiment, the first electronic device 1010 may request the server to verify the payment device based on the payment request of the first user 1000A. According to an embodiment, if the server receives a request for verifying the payment device from the first electronic device 1010, the server may identify at least one electronic device (for example, a payment-capable device) that can perform payment and is included in the account of the user (for example, the first user 1000A). According to an embodiment, in Figure 10 In the example of the payment-capable device, examples may include the second electronic device 1020, the third electronic device 1030, and the fourth electronic device 1040. According to an embodiment, if a payment-capable device is identified, the server may request the current device status of each of the identified payment-capable devices 1020, 1030, and 1040. In various embodiments, the device status may include, for example, the on / off status of the electronic device, the location of the relevant electronic device, whether the relevant electronic device is in use, etc.

[0197] According to various embodiments, if each of the capable payment devices 1020, 1030, and 1040 receives a device status verification request from the server, then in response to the device status verification request, each of the capable payment devices 1020, 1030, and 1040 may determine the current status information of the corresponding capable payment device, and may provide a response including the determination result to the server. For example, if each of the capable payment devices 1020, 1030, and 1040 is in a powered-on state, the corresponding capable payment device may send a response including its location information, busy information, and the like to the server. According to an embodiment, if a capable payment device in a powered-on state receives a device status verification request from the server, the relevant capable payment device may transmit to the server the current process usage of the relevant capable payment device, its memory occupancy, its application running status, and the like. If the server determines that the usage status of the corresponding capable payment device is greater than or equal to a predetermined usage status value based on the information received from each capable payment device, the server may determine that the corresponding capable payment device is in a busy state. According to an embodiment, in Figure 10 In the example, it may be assumed that the second electronic device 1020 is used by the second user 1000B, and the second electronic device 1020 may provide busy information to the server.

[0198] According to various embodiments, if the server does not receive a response to the device status request within a predetermined time period, the server may determine that the relevant payment-capable device is in a state where payment cannot be performed (for example, a network unavailable state or a shutdown state of the electronic device). According to an embodiment, if the server receives a response from the payment-capable device, the server may select the priority of the relevant payment-capable device based on the received response. According to an embodiment, the server may verify that the second electronic device 1020 includes busy information, may not consider the second electronic device 1020 as the electronic device to be assigned the highest priority (or may assign the lowest priority to the second electronic device 1020, or may exclude it from the payment-capable devices), and may determine the electronic device to be assigned the highest priority among other payment-capable devices (for example, the third electronic device 1030 and the fourth electronic device 1040). According to an embodiment, in Figure 10 In the example, the server may select the third electronic device 1030 closest to the first user 1000A as the payment-capable device with the highest priority.

[0199] According to various embodiments, the server may generate a list including priorities configured based on device states related to payment-capable devices, and may transmit the list to the first electronic device 1010. According to various embodiments, if the first electronic device 1010 receives the list from the server, the first electronic device 1010 may display the list of payment-capable devices on an area of the display. An example of such a configuration is shown in FIG. Figure 11 Shown in.

[0200] like Figure 11 As shown, if the first electronic device 1010 receives a list from the server, the first electronic device 1010 may display the received list 1120 on the content 1110 being displayed (or reproduced). According to an embodiment, the first electronic device 1010 may display the payment-capable devices (e.g., the third electronic device 1030 (e.g., device 3), the fourth electronic device 1040 (e.g., device 4), and the second electronic device 1020 (e.g., device 2)) in the list 1120 according to the order of priority configured by the server.

[0201] According to various embodiments, Figure 10 and Figure 11 As shown, if it is assumed that the first user 1000A is currently watching content displayed by the first electronic device 1010 (e.g., TV), then with reference to the first electronic device 1010, the second electronic device 1020 and the third electronic device 1030 may be located around the first electronic device 1010, and the fourth electronic device 1040 may be located in another place (e.g., another room). Figure 10 In the example of , the second electronic device 1020 may be used by the second user 1000B (for example, a family member of the first user 1000A). In this environment, assuming that the first user 1000A views content displayed by the first electronic device 1010, if the first user 1000A chooses to pay for a specific product in the content displayed by the first electronic device 1010, the server (or the first electronic device 1010) may verify the device status of each payment-capable device, as well as the location of the first user 1000A (or the first electronic device 1010) and the location of each payment-capable device, and may determine the priority based on the location and current device status of each payment-capable device. According to an embodiment, the device status of the payment-capable device may be information such as the processor operating rate of the payment-capable device, its memory occupancy, or whether an application is currently running, and the server (for example, the first electronic device 1010) may collect this information to determine the priority. According to an embodiment, as Figure 10 As shown, although the current location of the second electronic device 1020 is similar to that of the third electronic device 1030 , the second electronic device 1020 is used by the second user 1000B, and thus it may be determined that the third electronic device 1030 is to be assigned a higher priority.

[0202] Figure 12 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments. Figure 13 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments.

[0203] According to an embodiment, Figure 12An example of determining priority based on the device location of a payment device is shown. According to an embodiment, Figure 13 Shown based on Figure 12 An example of a list of related payment-capable devices is provided based on the priority determined in the example.

[0204] exist Figure 12 In the example, for ease of description, a floor plan (or structure) of a house interior is shown as an example, and in the example: a plurality of electronic devices (1210, 1220, 1240, and 1250) are placed at various locations (or positions) in a predetermined space inside the house; and one electronic device (for example, a third electronic device 1230) is placed outside the predetermined space (or outside the room). According to an embodiment, Figure 12 An example is shown in which: a first electronic device 1210 (e.g., a TV) and a second electronic device 1220 (e.g., a smart phone, a wearable device, or a tablet PC) are placed in a first space 1201 (e.g., a living room); a fourth electronic device 1240 (e.g., a smart phone, a wearable device, or a tablet PC) is placed in a second space 1202 (e.g., a room); a fifth electronic device 1250 (e.g., a smart phone, a wearable device, or a tablet PC) is placed in a third space 1203 (e.g., a bedroom); a third electronic device 1230 (e.g., a smart phone, a wearable device, or a tablet PC) is placed outside the space (e.g., a house); and a user 1200 is in the first space 1201.

[0205] According to an embodiment, Figure 12 An example is shown, in which: the first electronic device 1210 refers to a device without a payment function; the second electronic device 1220, the third electronic device 1230, the fourth electronic device 1240 or the fifth electronic device 1250 refers to a device with a payment function; and the third electronic device 1230 is placed outside the house.

[0206] Reference Figure 12 , while using content displayed by the first electronic device 1210 (for example, watching a home shopping program), the user 1200 desires to purchase a specific product, and may send a payment request to the first electronic device 1210 based on at least one of the above-mentioned schemes for requesting payment. According to an embodiment, the first electronic device 1210 may request the server to verify the payment device based on the payment request of the user 1200. According to an embodiment, if the server receives a request for verifying the payment device from the first electronic device 1210, the server may identify at least one electronic device (for example, a payment-capable device) that can perform payment and is included in the account of the user (for example, the user 1200). According to an embodiment, in Figure 12, examples of payment-capable devices may include a second electronic device 1220, a third electronic device 1230, a fourth electronic device 1240, and a fifth electronic device 1250. According to an embodiment, if a payment-capable device is identified, the server may request each of the identified payment-capable devices 1220, 1230, 1240, and 1250 for its current device location.

[0207] According to various embodiments, if each of the payment-capable devices 1220, 1230, 1240, and 1250 receives a device location verification request from the server, each of the payment-capable devices 1220, 1230, and 1240 may determine the current location information of the corresponding payment-capable device in response to the device location verification request, and may provide a response including the determination result to the server. Figure 12 In the same predetermined space as the space where the first electronic device 1210 (or user 1200) is located, each of the second electronic device 1220, the fourth electronic device 1240 and the fifth electronic device 1250 can provide location information of a relevant place (or position), and the third electronic device 1230 can provide location information outside the predetermined space.

[0208] According to various embodiments, if the server does not receive a response to the device location request within a predetermined time period, the server may determine that the relevant payment-capable device is in a state that cannot perform payment. According to an embodiment, if the server receives a response from the payment-capable device, the server may determine the location of the payment-capable device based on the received response, and may select the priority of the relevant payment-capable device based on the location. According to an embodiment, the server may verify that the third electronic device 1230 is outside the house, and may not consider the third electronic device 1230 as the electronic device to be assigned the highest priority (or may assign the lowest priority to the third electronic device 1230, or may exclude it from the payment-capable devices), and may determine the electronic device to be assigned the highest priority among other payment-capable devices (for example, the second electronic device 1220, the fourth electronic device 1240, and the fifth electronic device 1250). According to an embodiment, in Figure 12 In the example, the server may select the second electronic device 1220 closest to the user 1200 as the payment-capable device with the highest priority.

[0209] According to various embodiments, the server may generate a list including priorities configured based on device locations related to payment-capable devices, and may transmit the list to the first electronic device 1210. According to various embodiments, if the first electronic device 1210 receives the list from the server, the first electronic device 1210 may display the list of payment-capable devices on one area of the display. An example of such a configuration is shown in FIG. Figure 13 Shown in.

[0210] like Figure 13 As shown, if the first electronic device 1210 receives a list from the server, the first electronic device 1210 may display the received list 1320 on the content 1310 being displayed (or reproduced). According to an embodiment, the first electronic device 1210 may display payment-capable devices (e.g., the second electronic device 1220 (e.g., device 2), the fifth electronic device 1250 (e.g., device 5), and the fourth electronic device 1240 (e.g., device 4)) in the list 1320 according to the order of priority configured by the server.

[0211] According to various embodiments, Figure 12 and Figure 13 As shown, assuming that a user 1200 is currently viewing content displayed by a first electronic device 1210 (e.g., a TV), with reference to the first electronic device 1210, a second electronic device 1220 may be located around the first electronic device 1210, a third electronic device 1230 may be located outside a space (e.g., a house), and each of the fourth electronic device 1240 and the fifth electronic device 1250 may be located in another location (e.g., another room). In this environment, assuming that the user 1200 is viewing content displayed by the first electronic device 1210, if the user 1200 selects to pay for a specific product in the content displayed by the first electronic device 1210, the server may verify the location of the user 1200 (or the first electronic device 1210) and the locations of payment-capable devices (e.g., the second electronic device 1220, the third electronic device 1230, the fourth electronic device 1240, and the fifth electronic device 1250). According to an embodiment, assuming that the user 1200 views content displayed by the first electronic device 1210 , the server may verify the locations of the payment-enabled devices 1220 , 1230 , 1240 , and 1250 , and may configure the highest priority for the payment-enabled device closest to the first electronic device 1210 .

[0212] According to an embodiment, as an example of obtaining the location of an electronic device, each electronic device may perform indoor positioning and transmit the results of the operation. The first electronic device 1210 may broadcast a specific signal so that adjacent electronic devices can receive the signal, and the locations of the adjacent electronic devices may be measured based on the order in which the adjacent electronic devices transmit responses to the received signals. According to another embodiment, regarding the location of the electronic devices, the electronic device most recently used by the user 1200 may be determined as the electronic device currently closest to the user 1200, and thus the electronic device may be configured to have the highest priority.

[0213] Figure 14 is a diagram illustrating an example of determining an electronic device to be used for payment according to configured priorities in various embodiments.

[0214] According to an embodiment, Figure 14 The following example illustrates configuring priorities based on card payment benefits based on card information registered with payment-capable devices, and providing a list of relevant card information and payment-capable devices based on the configured priorities. For example, according to various embodiments, the benefits associated with actual card payments may be reflected in determining the priorities of payment-capable devices. According to embodiments, a user may log in to (or access) electronic device 1401 using a user account, and may associate a family account with the user account, allowing the user to control multiple external electronic devices together with family members.

[0215] Figure 14 An example of a list 1420 reflecting priorities according to payment offers is shown. According to an embodiment, if the electronic device 1401 receives the list 1420 from the server, the electronic device 1401 may display the received list 1420 on an area of the screen where the content 1410 is being displayed (or reproduced). Figure 14 In the shown list 1420, if there is also a card registered in another account related to the user account (for example, a family account), the electronic device of the related account may be included in the payment-capable devices, and a list 1420 including card information of the related payment-capable devices may be provided. According to various embodiments, if there are multiple pieces of card information in multiple payment-capable devices, information such as the relationship between each card and the product (for example, a discount rate) may be included in the list 1420, so that the user can easily select a card for payment.

[0216] According to various embodiments, Figure 14 As shown, based on the card information associated with multiple cards, priority can be determined based on product payment offers. According to an embodiment, as described above, priority can be determined based on the payment-enabled devices associated with the user account and another user (e.g., a family member) associated with the user account. For example, a user may use different types of cards, and the offers of the cards associated with the product currently desired to be purchased may vary. In addition, each card may or may not offer specific offers based on its usage history. Therefore, in various embodiments, the final priority can be determined based on both a first priority of payment-enabled devices (e.g., device location and device status) and a second priority based on card-specific offers.

[0217] According to an embodiment, if the final priority is displayed, such as Figure 14As shown, the following information may be provided, such as: the owner of each card (e.g., ID, user prefix (e.g., name and phone number)); what type of electronic device the payment-enabled device is (e.g., device name, device type, or alias); or card-provided benefits. According to various embodiments, the user can easily determine which payment-enabled device to use for payment based on the above information, and can immediately proceed with payment through the determined payment-enabled device.

[0218] As described above, the electronic device 101 (eg, Figure 1 electronic device 101, Figure 3B Server 350, or Figure 4 The operating method of the server 420 may include: receiving a first signal from a first electronic device, the first signal including information about the user's payment request and information related to the first electronic device (e.g., Figure 2 electronic device 201 or Figure 4 receiving contextual information related to a first electronic device 410) that does not have a payment function; after receiving the first signal, identifying at least one second electronic device that has a payment function and is associated with a user account; sending a second signal including information about the at least one second electronic device to the first electronic device; receiving a third signal for selecting one of the at least one second electronic devices; and sending a fourth signal including information related to payment to the selected second electronic device based at least in part on the third signal.

[0219] According to various exemplary embodiments, identifying the at least one second electronic device may include identifying at least one second electronic device having a payment function and associated with a user account among a plurality of neighboring electronic devices based at least in part on context information associated with the first electronic device.

[0220] According to various exemplary embodiments, identifying the at least one second electronic device may include identifying the at least one second electronic device having a payment function among a plurality of neighboring electronic devices based at least in part on context information related to the at least one second electronic device.

[0221] According to various exemplary embodiments, the context information related to the first electronic device may include: information about the device location of the first electronic device, and information about an account of a user registered in the first electronic device; and the context information related to at least one second electronic device may include at least one of the following information: information about the device location of at least one second electronic device, information about its device status, and card information about a registered card.

[0222] According to various exemplary embodiments, identifying at least one second electronic device may include: sending at least one request related to determining a payment device to at least one second electronic device based on receiving a first signal from a first electronic device; receiving a response corresponding to the request; and identifying at least one second electronic device based on whether a response corresponding to the request has been received.

[0223] According to various exemplary embodiments, sending the second signal may include: determining a priority of at least one second electronic device based at least in part on a response corresponding to the request; and generating a list including information about payment-capable devices based on the determined priority.

[0224] The various exemplary embodiments shown and described in the present disclosure and the accompanying drawings are provided only to easily describe the technical problems of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. Therefore, it should be understood that in addition to the embodiments disclosed herein, all modifications and changes or modified and changed forms based on the technical ideas of the present disclosure fall within the scope of the present disclosure.

Claims

1. A server configured to communicate with a plurality of electronic devices, the server comprising: a communication interface, including a communication circuit; at least one processor operatively connected to the communication interface; as well as at least one memory electrically connected to the processor, The memory of the server is configured to store instructions that, when executed by the processor of the server, control the server to: receiving a first signal from a first electronic device through the communication interface, the first signal including information about a payment request and context information related to the first electronic device, the first electronic device not having a payment function; sending, based on receiving the first signal from the first electronic device, at least one request related to determining a payment-capable device to a plurality of second electronic devices associated with user accounts associated with the first electronic device; generating, based on receiving responses corresponding to the at least one request from the plurality of second electronic devices, a list including information related to payment-capable devices among the plurality of second electronic devices based on priorities of the plurality of second electronic devices, wherein the priorities are determined based on a combination of at least two of states of the plurality of second electronic devices, locations of the plurality of second electronic devices, payment information registered in the plurality of second electronic devices, and payment preferences of a user; sending a second signal including the list to the first electronic device through the communication interface; receiving, from the first electronic device via the communication interface, a third signal for selecting one of the payment-capable devices included in the list; and Based at least in part on the third signal, a fourth signal including payment-related information is sent to the selected payment-capable device.

2. The server according to claim 1, wherein The instructions, when executed by the processor, control the server to: Based at least in part on the context information associated with the first electronic device, the plurality of second electronic devices having payment functionality and associated with the user's account are identified among a plurality of neighboring electronic devices.

3. The server according to claim 1, wherein The instructions, when executed by the processor, control the server to: identifying the plurality of second electronic devices having payment functionality based at least in part on contextual information associated with the plurality of second electronic devices, The context information related to the first electronic device includes: information about the device location of the first electronic device, and information about the user's account registered in the first electronic device, and Among them, the context information related to the multiple second electronic devices with payment functions includes at least one of the following information: information about the device locations of the multiple second electronic devices, information about the device status of the multiple second electronic devices, and card information about the registered card.

4. The server system according to claim 1, wherein: The instructions, when executed by the processor, control the server to: The priorities of the plurality of second electronic devices are determined based at least in part on the responses corresponding to the at least one request.

5. The server according to claim 1, wherein The third signal includes: information about a selected payment-capable device selected from the list by the first electronic device; and Information related to payment for the selected payment-capable device.

6. An electronic device comprising: a communication interface, including a communication circuit; monitor; at least one processor operatively connected to the display and the communication interface; as well as at least one memory electrically connected to the processor, The memory is configured to store instructions that, when executed by the processor, control the electronic device to: displaying content on the display and a user interface configured to receive a payment request associated with the content; receiving, through the user interface, a first user input related to the payment request; sending information related to the first user input to an external server via the communication interface; receiving, from the external server, a list of a plurality of external electronic devices having a payment function and associated with a user account associated with the electronic device; displaying the list on the display based on priorities associated with the plurality of external electronic devices, wherein the priorities are determined based on a combination of at least two of states of the plurality of second electronic devices, locations of the plurality of second electronic devices, payment information registered in the plurality of second electronic devices, and payment preferences of a user; receiving a second user input for selecting an external electronic device among the plurality of external electronic devices in the displayed list; and Information about the second user input is sent to the external server through the communication interface.

7. The electronic device according to claim 6, wherein: The instructions, when executed by the processor, control the electronic device to: Based on the information about the second user input being sent to the external server, Information regarding the second user input including information regarding the external electronic device selected based on the second user input among the plurality of external electronic devices and information related to payment of the selected external electronic device is transmitted.

8. The electronic device according to claim 6, wherein: The instructions, when executed by the processor, control the electronic device to: Based on information associated with the first user input being sent, Information related to the first user input is sent, including information about the user's payment request and context information related to the electronic device.

9. A method performed by a server configured to communicate with a plurality of electronic devices, the method comprising: receiving a first signal from a first electronic device, the first signal including information about a payment request and context information related to the first electronic device, the first electronic device not having a payment function; sending, based on receiving the first signal from the first electronic device, at least one request related to determining a payment-capable device to a plurality of second electronic devices associated with user accounts associated with the first electronic device; generating, based on receiving responses corresponding to the at least one request from the plurality of second electronic devices, a list including information related to payment-capable devices among the plurality of second electronic devices based on priorities of the plurality of second electronic devices, wherein the priorities are determined based on a combination of at least two of states of the plurality of second electronic devices, locations of the plurality of second electronic devices, payment information registered in the plurality of second electronic devices, and payment preferences of a user; sending a second signal including the list to the first electronic device; receiving, from the first electronic device via the communication interface, a third signal for selecting one of the payment-capable devices included in the list; and Based at least in part on the third signal, a fourth signal including payment-related information is sent to the selected payment-capable device.

10. The method according to claim 9, further comprising: Based at least in part on the context information associated with the first electronic device, the plurality of second electronic devices having payment functionality and associated with the user's account are identified among a plurality of neighboring electronic devices.

11. The method according to claim 9 further comprising: identifying the plurality of second electronic devices having payment functionality among a plurality of adjacent electronic devices based at least in part on contextual information associated with the plurality of second electronic devices, The context information related to the first electronic device includes: information about the device location of the first electronic device, and information about the user's account registered in the first electronic device, and The context information related to the plurality of second electronic devices includes at least one of the following information: information about device locations of the plurality of second electronic devices, information about device states of the plurality of second electronic devices, and card information about a registration card.

12. The method according to claim 9, further comprising: Priorities of the plurality of second electronic devices are determined based at least in part on the responses corresponding to the at least one request.

13. The method according to claim 9, wherein: The third signal includes: information about a selected payment-capable device selected from the list by the first electronic device; and Information related to payment for the selected payment-capable device.

Images