CN105894268B

CN105894268B - Payment processing method and electronic equipment paying for same

Info

Publication number: CN105894268B
Application number: CN201610084771.2A
Authority: CN
Inventors: 吴世娥; H.N.金; 朴美妍; 朴容万; 徐瑜枇; 徐和延; 俞炳仁; 卢炳卓; 尹硕铉; 李曜汉; 诸成民
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2015-02-12
Filing date: 2016-02-14
Publication date: 2020-02-21
Anticipated expiration: 2036-02-14
Also published as: AU2016216833B2; KR102461042B1; AU2016216833A1; KR20160099464A; CN105894268A

Abstract

An electronic device and a method of processing payment at an electronic device are provided. The electronic device includes a secure memory configured to store payment information of a Near Field Communication (NFC) method, payment information of a Magnetic Secure Transmission (MST) method, and fingerprint information, and a processor configured to control a multi-payment operation of the NFC method and the MST method when the fingerprint information obtained through fingerprint detection is valid. The processor is further configured to control signal processing information operating according to the NFC method and signal processing information operating according to the MST method to be output as one screen interface.

Description

Payment processing method and electronic equipment paying for same

Cross Reference to Related Applications

This application claims the benefit of us provisional patent application having an assigned serial number of 62/126,121 filed at us patent and trademark office on day 27 of year 2015 and korean patent application having an assigned serial number of 10-2015-0021808 filed at korean intellectual property office on day 12 of year 2015 and korean patent application having an assigned serial number of 10-2015-0179430 filed on day 15 of year 2015, the entire disclosure of each of these applications being incorporated herein by reference.

Technical Field

The present disclosure relates to payment processing. More particularly, the present disclosure relates to a payment processing method for more easily and conveniently processing payment of a fee by using an electronic device and an electronic device supporting the same.

Background

Generally, electronic devices support various functions. For example, the electronic device supports a corresponding function by displaying content or executing an application having a specific function.

The above-described electronic devices of the related art provide screens provided from websites selling various commodities.

The above information is presented merely as background information to aid in understanding the present disclosure. No determination is made as to whether any of the above applies as prior art to the present disclosure, nor is an assertion made.

Disclosure of Invention

Aspects of the present disclosure are to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present disclosure is to provide a payment processing method for more easily and conveniently processing payment of a fee by using an electronic device and an electronic device supporting the same.

According to an aspect of the present disclosure, an electronic device is provided. The electronic device includes a secure memory configured to store payment information of a Near Field Communication (NFC) method, payment information of a Magnetic Secure Transmission (MST) method, and fingerprint information, and a processor (or a control module) configured to control a multi-payment operation of the NFC method and the MST method when the fingerprint information obtained through fingerprint detection is valid.

The control module controls a signal processing screen (or signal processing information) operating according to the NFC method and a signal processing screen (or signal processing information) operating according to the MST method to be output as one screen interface.

According to another aspect of the present disclosure, a payment processing method of an electronic device is provided. The payment processing method includes performing fingerprint detection, and outputting signal processing information operating according to an NFC method and signal processing information operating according to an MST method, which are output as one screen interface, when fingerprint information obtained through the fingerprint detection is valid.

Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

Drawings

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

FIG. 1 illustrates a payment processing environment, according to various embodiments of the present disclosure;

FIG. 2 illustrates a control module according to various embodiments of the present disclosure;

fig. 3A is a flow diagram illustrating a Near Field Communication (NFC) payment processing method of an electronic device, according to various embodiments of the present disclosure;

fig. 3B is a flow diagram illustrating a Magnetic Security Transmission (MST) type payment processing method of an electronic device, according to various embodiments of the disclosure;

fig. 3C is a flow diagram illustrating a barcode-type payment processing method of an electronic device, according to various embodiments of the present disclosure;

fig. 4 is a flow diagram illustrating a handoff function in a payment processing method according to various embodiments of the present disclosure;

FIG. 5 illustrates a payment application execution screen of an electronic device, in accordance with various embodiments of the present disclosure;

6A, 6B, 6C, and 6D illustrate card search screen interfaces of electronic devices according to various embodiments of the present disclosure;

7A, 7B, 7C, and 7D illustrate a payment completion screen interface of an electronic device, according to various embodiments of the present disclosure;

fig. 8A illustrates an NFC method and MST method support screen of an electronic device, in accordance with various embodiments of the disclosure;

FIG. 8B illustrates a barcode method operational screen of an electronic device, in accordance with various embodiments of the present disclosure;

FIG. 9 illustrates a multiple payment operations re-execution screen of an electronic device, in accordance with various embodiments of the present disclosure;

fig. 10A and 10B illustrate a handover function execution screen according to various embodiments of the present disclosure;

11A, 11B, 11C, 11D, and 11E illustrate payment execution-related screen interfaces in accordance with various embodiments of the present disclosure;

FIG. 12 illustrates a token validity related screen interface in accordance with various embodiments of the present disclosure;

FIG. 13 illustrates a token validity related screen interface in accordance with various embodiments of the present disclosure;

14A and 14B illustrate MST signal processing operations according to various embodiments of the present disclosure;

fig. 15 illustrates a battery remaining related payment processing screen, in accordance with various embodiments of the present disclosure;

16A, 16B, and 16C illustrate card selection related screens according to various embodiments of the present disclosure;

17A, 17B, and 17C illustrate card selection related screens according to various embodiments of the present disclosure;

FIG. 18 is a block diagram illustrating a network environment, according to various embodiments of the present disclosure;

FIG. 19 is a block diagram of an electronic device according to various embodiments of the present disclosure;

FIG. 20 is a block diagram of program modules according to various embodiments of the present disclosure;

FIG. 21 is a block diagram illustrating a Rich Execution Environment (REE) and a Trusted Execution Environment (TEE) operating in an electronic device, according to various embodiments of the present disclosure;

22A, 22B, and 22C are block diagrams illustrating the hardware structure of a TEE according to various embodiments of the present disclosure;

fig. 23 illustrates a payment system in accordance with various embodiments of the present disclosure;

fig. 24 is a block diagram illustrating a payment system for performing payments, in accordance with various embodiments of the present disclosure;

fig. 25 is a block diagram illustrating a hardware structure of an electronic device for performing payment functions, according to various embodiments of the present disclosure;

fig. 26A is a hardware (H/W) block diagram illustrating the interior of an electronic device using wireless short-range communication with at least one of a plurality of MST modules, according to various embodiments of the disclosure;

fig. 26B is an H/W block diagram illustrating the interior of an electronic device using wireless short-range communication with at least one of a plurality of MST modules, according to various embodiments of the disclosure;

fig. 26C is an H/W block diagram illustrating the interior of an electronic device using wireless short-range communication with at least one of a plurality of MST modules, according to various embodiments of the disclosure;

FIG. 27 is a block diagram illustrating program modules executed in an execution environment of an electronic device for performing payment functions, in accordance with various embodiments of the present disclosure;

28A, 28B, 28C, 28D, 28E, 28F, 28G, 28H, 28I, and 28J illustrate a payment user interface of an electronic device, according to various embodiments of the present disclosure;

FIG. 29 illustrates a token password generation method, in accordance with various embodiments of the present disclosure;

FIG. 30 illustrates a payment system in accordance with various embodiments of the present disclosure;

FIG. 31 is a flow diagram of token payment (token payment) according to various embodiments of the present disclosure;

FIG. 32 illustrates operation of payment system components in accordance with various embodiments of the present disclosure;

FIG. 33A illustrates a flow diagram of a first token issuance operation of an electronic device, in accordance with various embodiments of the present disclosure;

FIG. 33B illustrates a flow diagram of a second token issuance operation by an electronic device, in accordance with various embodiments of the present disclosure; and is

Fig. 33C illustrates a flow diagram of a third token issuance operation by an electronic device, in accordance with various embodiments of the present disclosure.

Like reference numerals will be understood to refer to like parts, components and structures throughout the various views.

Detailed Description

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. The description includes various specific details to aid understanding, but such details are to be regarded as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Moreover, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to the literal meanings, but are used by the inventors to enable a clear and consistent understanding of the disclosure. Accordingly, it will be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

The term "substantially" is used to mean that the recited characteristic, parameter, or value need not be achieved exactly, but may vary in amount, including, for example, tolerances, measurement error, measurement accuracy limitations and other factors known to those skilled in the art, without such deviation or variation interfering with the intended result of the characteristic.

The terms "comprising," "including," and "having," or "may include" and "may have," as used herein, indicate the presence of the disclosed functions, operations, or elements, but do not exclude other functions, operations, or elements.

For example, the expression "a or B" or "at least one of a or/and B" may indicate that A, B or both a and B are included. For example, the expression "a or B" or "at least one of a or/and B" may indicate (1) at least one a, (2) at least one B, or (3) both at least one a and at least one B.

Terms such as "1 st," "2 nd," "first," "second," and the like, as used herein, may refer to, but do not limit, various elements that modify various embodiments of the disclosure. These expressions may be used to distinguish one element from another. For example, "first user equipment" and "second user equipment" may indicate different users, regardless of order or importance. For example, a first component may be termed a second component, and vice-versa, without departing from the scope of the present disclosure.

In various embodiments of the present disclosure, it will be understood that when a component (e.g., a first component) is referred to as being "operatively or communicatively coupled"/"(operatively or communicatively) to" or "connected to" another component, the component may be directly connected to the other component or connected through yet another component (e.g., a third component). In various embodiments of the present disclosure, it will be understood that when a component (e.g., a first component) is referred to as being "directly connected to" or "directly accessing" another component (e.g., a second component), there is no further component (e.g., a third component) between the component (e.g., the first component) and the other component (e.g., the second component).

The expression "configured to" as used in various embodiments of the present disclosure may be used interchangeably with "adapted to", "having … … capabilities", "designed to", "adapted to", "enabled", or "capable", for example, depending on the situation. The term "configured to" may not necessarily mean "specifically designed" in terms of hardware. Instead, the expression "a device configured as … …" may mean in some cases that the device and another device or component are "capable … …". For example, the phrase "a processor configured to perform A, B and C" may mean a dedicated processor (e.g., an embedded processor) for performing the respective operations or a general-purpose processor (e.g., a Central Processing Unit (CPU) or an Application Processor (AP)) for performing the respective operations by executing at least one software program stored in a memory device.

Unless otherwise indicated herein, all terms, including technical or scientific terms, used herein may have the same meaning as commonly understood by one of ordinary skill in the art. In general, terms defined in dictionaries should be considered to have the same meaning as the context of the related art and should not be understood abnormally or to have an excessively formal meaning unless explicitly defined herein. In any case, even the terms defined in the present specification should not be construed as excluding the embodiments of the present disclosure.

According to various embodiments of the present disclosure, an electronic device may include at least one of: smart phones, tablet Personal Computers (PCs), mobile phones, video phones, electronic book (e-book) readers, desktop PCs, laptop PCs, netbook computers, workstation servers, Personal Digital Assistants (PDAs), Portable Multimedia Players (PMPs), moving picture experts group phase 1or phase 2(moving picture experts group phase 1or phase 2, MPEG _1or MPEG _2) audio layer 3(MPEG _1 MPEG or 2audio layer 3, MP3) players, mobile medical devices, cameras and wearable devices (e.g., smart glasses, head-mounted devices (HMDs), electronic clothing, electronic necklaces, electronic accessories, electronic tattoos, smart mirrors, and smart watches).

According to some embodiments of the present disclosureThe electronic device may be an intelligent household appliance. The smart home appliance may include, for example, at least one of: television (TV), Digital Versatile Disc (DVD) player, stereo, refrigerator, air conditioner, cleaner, oven, microwave oven, washing machine, air purifier, set-top box, home automation control panel, security control panel, TV box (e.g., Samsung HomeSync)^TM、Apple TV^TMOr GoogleTV^TM) Game machine (e.g., Xbox)^TMAnd PlayStation^TM) An electronic dictionary, an electronic key, a camcorder and an electronic photo frame.

According to some embodiments of the disclosure, an electronic device may include at least one of: various medical devices that support call forwarding services (e.g., various portable measurement devices (e.g., blood glucose meters, heart rate meters, blood pressure meters, thermometers, etc.), Magnetic Resonance Angiography (MRA) devices, Magnetic Resonance Imaging (MRI) devices, Computed Tomography (CT) devices, medical imaging devices, ultrasound devices, etc.), navigation devices, Global Positioning System (GPS) receivers, Event Data Recorders (EDRs), Flight Data Recorders (FDRs), vehicle infotainment devices, marine electronic devices (e.g., marine navigation systems, gyros, etc.), avionic devices, security devices, head units, industrial or home robots, automated teller machines (ATMs 'of financial institutions) or point of sale (ATM's), POS) or the internet of things (e.g., light bulbs, various sensors, electricity or gas meters, sprinkler systems, fire alarms, thermostats, street lights, toasters, exercise equipment, hot water tanks, heaters, boilers, etc.).

In various embodiments of the present disclosure, the electronic device may include at least one of: a part of furniture or a building/structure supporting a call forwarding service, an electronic board, an electronic signature receiving device, a projector, and various measuring instruments (e.g., water, electric, gas, or radio signal measuring instruments). The electronic device according to various embodiments of the present disclosure may be one of the various devices described above, or a combination thereof. Furthermore, the electronic device according to embodiments of the present disclosure may be a flexible electronic device. Furthermore, the electronic device according to the embodiment of the present disclosure is not limited to the above-described devices, but may include a new kind of electronic device according to technical development.

Hereinafter, electronic devices according to various embodiments of the present disclosure will be described with reference to the accompanying drawings. The term "user" in this disclosure may refer to a person using an electronic device or a device using an electronic device (e.g., an artificial intelligence electronic device).

Fig. 1 illustrates a payment processing environment, according to various embodiments of the present disclosure.

Referring to FIG. 1, a payment processing environment 10 may include an electronic device 100 and a payment processing device 200.

In the payment processing environment 10, the electronic device 100 (e.g., a payment information providing device) may deliver payment information to the payment processing device 200 by combining operations of a Magnetic Security Transmission (MST) method and a Near Field Communication (NFC) method or a barcode method, regardless of a payment processing method of the payment processing device 200. According to an embodiment of the present disclosure, the electronic device 100 may provide payment information to the payment processing device by alternately processing signal transmission necessary for the MST method and the NFC method, regardless of whether the payment processing device supports the MST receiving method or the payment processing device supports the NFC communication method. For example, the electronic device 100 may transmit the MST signal after an NFC method operation based on an NFC polling cycle (polling cycle). Alternatively, the electronic device 100 may utilize sensors to determine MST signal timing.

According to various embodiments of the present disclosure, the electronic device may output barcode information to the display on a screen interface (or user interface) for alternately handling signal transmission necessary for the MST method and the NFC method. Alternatively, the electronic device may temporarily stop the operation of the MST method and the NFC method, and output a screen interface (or user interface) including barcode information to the display in correspondence with the user input. According to various embodiments of the present disclosure, the electronic apparatus 100 may provide a handover function (or a function for suppressing switching to another function of the electronic apparatus) corresponding to a screen lock state during a payment information providing operation. Based on this, even if the electronic apparatus 100 is handed over to another user, access to another function (e.g., an album function, a call function, etc.) of the electronic apparatus by the other user may be prevented.

The payment processing device 200 may be, for example, a device including an NFC communication module for establishing an NFC communication channel with the electronic device 100. Alternatively, the payment processing device 200 may be, for example, a device including an MST receiving module for receiving an MST signal transmitted from the electronic device 100. Alternatively, the payment processing device 200 may be a device that includes a scanner for identifying a barcode output to a display of the electronic device 100. The payment processing apparatus 200 may transmit payment information delivered by the electronic apparatus 100 through one of the MST method, the NFC method, and the barcode method to a designated server apparatus.

The payment processing apparatus 200 may receive approval (approval) information about corresponding payment information from a designated server apparatus. When the approval information is received, the payment-processing apparatus 200 may process the approval information differently according to the communication method. For example, if the payment processing apparatus 200 is an apparatus for operating the NFC method, the payment processing apparatus 200 may transmit approval information to the electronic apparatus 100. If the payment processing apparatus 200 is an apparatus for operating the MST method or the barcode method, the payment processing apparatus 200 may output at least one of video data, audio data (e.g., payment completion notification sound), vibration, and lamp blinking, which are designated to guide payment completion. According to various embodiments of the present disclosure, the designated server device may directly provide the payment approval information to the electronic device 100.

The payment processing apparatus 200 may include at least one of the NFC communication module, MST receiving module, and barcode scanner mentioned above in connection with payment processing. Further, the payment processing apparatus 200 may include a display apparatus for outputting payment processing-related information. Further, the payment processing device 200 may include a communication module for communicating with a designated server device. The payment processing arrangement 200 may include at least one processor that is involved in the processing of payment processing related information.

Electronic device 100 may include bus 110, control module 120, memory 130, input/output interface 140, display 150, NFC chip 161, MST coil 163, secure memory 165, communication interface 170, sensor unit 190, and camera 180.

Bus 110 may include, for example, circuitry for connecting components 120-190 to each other and for delivering communications (e.g., control messages and/or data) between components 120-190. For example, the bus 110 may receive payment-related input events from the input/output interface 140 or a touch screen of the display 150. The bus 110 may deliver the received payment-related input event to the control module 120. The bus 110 may deliver a signal for activating components related to payment processing or execution of functions related to payment processing.

The control module 120 may perform control to deliver and process signals related to the operation of the electronic device 100, or read and store data. The control module 120 may include at least one processor. The processor may include at least one or more of a CPU, an AP, and a Communication Processor (CP). The processor may, for example, perform calculations or data processing for control and/or communication of at least one further component of the electronic device 100.

According to an embodiment of the present disclosure, the processor may execute the payment application according to the payment application execution request. The processor may prepare for multi-payment method operation of the NFC method and the MST method in relation to execution of the payment application. In addition, the processor may prepare the barcode method operation in response to an input event or a specified event occurrence. The operation preparation may include, for example, a state for receiving an NFC detection signal from the outside by activating the NFC chip 161. The operation preparation may include, for example, determining whether the operation is a state for transmitting the MST signal by operating the sensor unit 190. The operation preparation may include determining, with the camera 180, whether the operation is a situation for outputting a barcode to the display 150 based on the approach of the specified object.

The memory 130 may include volatile and/or nonvolatile memory. Memory 130 may, for example, store instructions or data related to at least one additional component of electronic device 100. Memory 130 may store software and/or programs in accordance with embodiments of the present disclosure. Programs may include kernels, middleware, application programming interfaces, and applications. At least a portion of the kernel, middleware, or application interface may be referred to as an Operating System (OS).

The kernel, for example, may control or manage system resources (e.g., bus 110, processors, memory 130, etc.) for performing operations or functions implemented in other programs (e.g., middleware, application interfaces, or applications). Further, the kernel may provide an interface for controlling or managing system resources from middleware, an application interface, or an application by accessing individual components of the electronic device 100.

Middleware may act as an intermediary for exchanging data, for example, when an application interface or application communicates with a kernel. Further, with respect to job requests received from the applications, the middleware may perform control (e.g., scheduling or load balancing) on the job requests, for example, by using a method of assigning a priority of using system resources (e.g., the bus 110, the processor (or the control module 120), the memory 130, and the like) of the electronic device 100 to at least one application among the applications.

The application interface, which is an interface for allowing an application to control functions provided from a kernel or middleware, may include at least one interface or function (e.g., an instruction) for file control, window control, image processing, or character control.

The application may be a program related to at least one function provided to the user through the operation of the electronic apparatus 100. According to embodiments of the present disclosure, the application may comprise a payment application. The payment application may be executed according to a designated icon or menu item selection. Alternatively, the payment application may be activated corresponding to a payment execution request received from the outside. The payment application may request operations of a payment processing-related screen interface process, a fingerprint authentication-related interface process, an NFC method according to fingerprint authentication, an MST method, and a barcode method. When a request to pay for an application occurs, the necessary processing of the application interface, middleware, and kernel may be accomplished by the processor (or control module 120).

Input/output interface 140 may, for example, serve as an interface for delivering instructions or data input from a user or another external device to additional component(s) of electronic device 100. Further, input/output interface 140 may output instructions or data received from additional component(s) of electronic device 100 to a user or another external device. The input/output interface 140 may include, for example, at least one physical button, touch pad, or touch screen. Further, the input/output interface 140 may include an input unit (or an input device) using an electronic pen.

Further, the input/output interface 140 may include an audio device for processing audio signals. A speaker included in the audio device may perform output of a designated high frequency signal. A microphone included in the audio collecting apparatus may perform collection of a designated high-frequency signal. The high frequency signal output function and the high frequency signal collection function of the audio device may be used to determine whether there is a peripheral magnetic reader associated with the MST method operation.

The display 150 may include, for example, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, an Organic LED (OLED) display, a Micro Electro Mechanical System (MEMS) display, or an electronic paper display. Display 150 may display various content (e.g., text, images, videos, icons, symbols, etc.) to a user. The display 150 may include a touch screen, and may receive touch, gesture, proximity, or hover input using an electronic pen or a body part of a user, for example.

The display 150 may output a payment application execution screen related to payment processing. According to an embodiment of the present disclosure, the display 150 may output one multi-payment screen interface including a signal processing screen (or signal processing information) related to the NFC method operation and a signal processing screen (or signal processing information) related to the MST method operation. The screen interface may include an object for performing barcode switching. When an object for performing barcode switching is selected, the display 150 may output a barcode screen interface in which a barcode object is displayed. The barcode screen interface may include an object for performing a multi-payment screen interface switch.

The display 150 may output a screen including at least one virtual card object when the payment application is executed. Display 150 may output information for guiding fingerprint authentication. The display 150 may output visual guide information necessary for the operation of the NFC method or the MST method. The display 150 may output information regarding errors occurring during the payment processing process. The display 150 may output various information according to the completion of payment. According to various embodiments of the present disclosure, the electronic apparatus 100 may output at least one of video data designated to guide payment completion and a guide sound for guiding payment completion. Further, the electronic apparatus 100 may output a vibration pattern or a lamp blinking pattern indicating at least one of a payment progress status, a payment completion status, and a payment failure.

The NFC chip 161 may be a chip for supporting an NFC communication function. The NFC chip 161 may be activated, for example, corresponding to control of the control module 120. When receiving a specified signal from the outside, the NFC chip 161 may transmit a specified signal corresponding to the received signal to the outside. During this operation, the NFC chip 161 may transmit payment information stored in the secure memory 165 to an external device corresponding to the control of the control module 120. After the payment information is transmitted, the NFC chip 161 may receive a message about the completion of payment from an external device (e.g., the payment processing device 200).

MST coil 163 may be a coil for MST signal transmission. According to an embodiment of the present disclosure, the MST coil 163 may be disposed on at least one side of the housing of the electronic device 100 (e.g., a certain (or particular) location inside the housing). For example, the MST coil 163 may be disposed at a battery cover of the electronic device 100. Alternatively, MST coil 163 may be patterned and disposed at a back cover or back cover of electronic device 100. When the MST coil 163 is disposed at a housing, for example, a case, a contact point connected to the control module 120 may be disposed at one side of the housing. The MST coil 163 may output the designated safety information stored in the safety memory 165 according to the control of the control module 120.

Secure memory 165 may store information related to payment processing by electronic device 100. The secure memory 165 may include various forms, such as at least one of an embedded universal integrated circuit card (eUICC) and an embedded secure element (eSE), for example. Secure memory 165 may include payment information sent through NFC chip 161 or payment information sent through MST coil 163. In addition, the secure memory 165 may include barcode information. The payment information transmitted through the NFC chip 161 and the payment information transmitted through the MST coil 163 may be the same information. For example, the payment information may include credit information (e.g., Identification (ID) information of the payment user, virtual card information, contact information of the electronic device 100, address information of the user, etc.) recorded on the virtual card.

The payment information may include, for example, token (token) information. The token information may include validity determination-related time information or count information. The token information including the time information may lose validity when the corresponding time information elapses. Token information including count information may lose validity when corresponding count information is exceeded. Token information that loses validity is not further operable and the electronic device 100 may require updating when the token information loses validity. Further, the electronic device 100 may require new token information replacement.

Payment completion information collected according to payment completion may be received from a designated server device. Payment completion information may be stored in the secure memory 165 according to the settings. Alternatively, the payment completion information may be stored in the memory 130 according to user settings. The payment completion information stored in the secure memory 165 or the memory 130 may be output to the display 150 according to the search request.

The communication interface 170 may set communication between the electronic apparatus 100 and an external apparatus (e.g., a designated server apparatus), for example. For example, the communication interface 170 may communicate with an external device through a wireless communication or wired communication contact network. As the cellular communication protocol, for example, Long Term Evolution (LTE), LTE-advanced (LTE-a), Code Division Multiple Access (CDMA), wideband CDMA (wideband CDMA, WCDMA), Universal Mobile Telecommunications System (UMTS), wireless broadband (WiBro), or global system for mobile communications (GSM) may be used for wireless communication. The wired communication may include, for example, at least one of: universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), recommended standard 232 (RS-232), and Plain Old Telephone Service (POTS). The network may include at least one of a telecommunications network, such as at least one of a computer network (e.g., a Local Area Network (LAN) or a Wide Area Network (WAN)), the internet, and a telephone network. The communication interface 170 may, for example, receive payment completion information (or a message including payment completion content (e.g., Short Messaging Service (SMS), Multimedia Messaging Service (MMS)), etc.) from a designated server device.

The sensor unit 190 may collect at least one sensor information related to determining a motion of the electronic apparatus 100, determining an object near the electronic apparatus 100, and determining whether there is an object around the electronic apparatus 100. The sensor unit 190 may include, for example, a high frequency sensor, an acceleration sensor, a gyro sensor, an illumination sensor, a proximity sensor, and a heart rate sensor. The sensor information of the high frequency sensor, the acceleration sensor, the gyro sensor, the illumination sensor, the proximity sensor, and the heart rate sensor collected by the sensor unit 190 may be provided to the control module 120. The delivered sensor information may be analyzed for location, angle of rotation, surrounding situation recognition of the electronic device.

According to various embodiments of the present disclosure, the speaker and microphone included in the input/output interface 140 may act as sensors configured to transmit and receive high frequency signals during payment processing operations. Further, the speaker may output a specified guidance message related to the payment process to the user. Further, a microphone may be used to detect ambient sounds.

The camera 180 may be disposed at a side of the housing of the electronic device 100 to collect images. For example, the camera 180 may include a first camera 181 disposed at a front surface of the electronic device 100 and a second camera 182 disposed at a rear surface. The electronic device 100 may include one of a front camera and a rear camera.

According to various embodiments of the present disclosure, the images collected by the camera 180 may be used to identify the type, location, and motion of the payment processing device 200 (e.g., POS) through analysis. In connection with this, the camera 180 may be activated when the payment processing function is performed, corresponding to the control of the control module 120. Images collected by the camera 180 may be provided to the control module 120 and used to determine that a subject in a specified pattern is approaching. In relation to the subject proximity analysis, the memory 130 may store texture images. The texture image may comprise a texture in the form of a barcode scanner, for example. According to various embodiments of the present disclosure, the camera 180 may collect infrared information emitted from a barcode scanner. The collected infrared information may be provided to the control module 120 and used to determine whether the barcode scanner is approaching or receding. According to various embodiments of the present disclosure, the texture image may include a texture (texture) in the form of a magnetic card reader, for example.

According to various embodiments of the present disclosure, images collected by the camera 180 may be provided to the control module 120 and used to determine a specified form of subject motion (e.g., withdrawal from a specified location). In connection with this, the camera 180 may support functionality for tracking an object (e.g., a barcode scanner or a magnetic card reader) by providing preview images or capturing video.

As described above, the payment processing environment 10 can support the prompt completion of payment with minimal operations in a manner most similar to the method of making payment by taking out a plastic card. The payment processing environment 10 minimizes user operations related to payments and intuitively guides actions to be taken so that the payment processing environment 10 supports easy and simple payments. The electronic device 100 may be, for example, one of a smart device and a wearable device.

Fig. 2 illustrates a control module according to various embodiments of the present disclosure.

Referring to fig. 2, the control module 120 according to various embodiments of the present disclosure may include a payment screen processing module 121, a multi-payment processing module 123, and a handover processing module 125.

The payment screen processing module 121 may perform at least one state control related to the payment application execution of the electronic device 100. For example, when the display 150 is turned off, the payment screen processing module 121 may determine whether a touch gesture related to the payment application execution occurs by operating a driving frequency of the touch panel as a first frequency. When a touch gesture related to the payment application execution occurs, the payment screen processing module 121 may perform control to output a designated payment application execution screen (e.g., a screen including at least one virtual card object) to the display 150.

According to various embodiments of the present disclosure, when the display 150 is turned on, the payment screen processing module 121 may perform control to output an icon or menu item related to the execution of the payment application. Alternatively, the payment screen processing module 121 may assign the payment application execution to a designated input button or a designated sensor (e.g., fingerprint sensor). Accordingly, when at least one of an icon or menu selection signal related to the payment application execution, an input button selection signal, and fingerprint recognition occurs, the payment screen processing module 121 may output a screen according to the payment application execution. For example, the payment screen processing module 121 may perform control to output the virtual card object on the background screen. During this operation, the payment screen processing module 121 may perform control to convert the background screen into a designated screen and output the virtual card object.

The payment screen processing module 121 may request a specified authentication information input during the execution of the payment application. For example, the payment screen processing module 121 may output an input window related to the input of the specified authentication information. Alternatively, the payment screen processing module 121 may output a guidance message for requesting fingerprint detection. In connection with this, the payment screen processing module 121 may perform a control to activate the fingerprint sensor during execution of the payment application. The payment screen processing module 121 may determine whether the fingerprint information collected by the fingerprint sensor corresponds to the fingerprint information stored in the secure memory 165.

According to various embodiments of the present disclosure, when the fingerprint information matches, the payment screen processing module 121 may output a write window related to the user signature writing. When a touch event occurs on the write window, the payment screen processing module 121 may collect signature information according to the touch event and deliver it to the multi-payment processing module 123. The write window output may be performed in conjunction with fingerprint sensor activation.

The multi payment processing module 123 may perform control to operate the NFC method and the MST method in combination corresponding to fingerprint information matching. For example, the multi payment processing module 123 may activate the NFC chip 161 with respect to the NFC method operation. The multi-payment processing module 123 may determine whether or not a specified NFC signal is received through the NFC chip 161 at each period. The multi-payment processing module 123 may transmit the payment information stored in the secure memory 165 to the external device when receiving the designated NFC signal.

The multi-payment processing module 123 may perform payment processing with NFC at or after the designated gesture operation to prevent undesirable payment processing during NFC method operation. For example, the multi-payment processing module 123 may support payment execution by activating the NFC chip 161 upon sensor information according to a specified motion of the wearable device (e.g., sensor information according to an operation for moving the device worn on the wrist to a specified location).

The multi payment processing module 123 may transmit an MST signal for operation of the MST method at every period (e.g., an idle period considering an NFC polling period) during operation of the NFC method. In connection with this, the multi-payment processing module 123 may perform control to transmit the payment information stored in the secure memory 165 through the MST coil 163. The multi-payment processing module 123 may maintain the MST signal transmission for a certain period of time or a certain time, and process the MST signal transmission completion after a specified number of times ends or a specified time elapses. The multi payment processing module 123 may operate the NFC method again. Further, the multi payment processing module 123 may output a virtual key button for performing MST signal transmission again to the display 150. When the virtual key button is selected, the multi payment processing module 123 may perform MST signaling again.

According to various embodiments of the present disclosure, the multi-payment processing module 123 may utilize at least one of the sensor unit 190 and the camera 180 to determine whether a magnetic card reader is nearby during the NFC method operation. The multi-payment processing module 123 may stop the NFC method operation and operate the MST method if it is determined through the sensor information analysis that there is a magnetic card reader in the vicinity. For example, the multi-payment processing module 123 may perform control to transmit the MST signal when it is determined that the distance between the magnetic card reader and the electronic device 100 is within a certain distance. During this operation, the multi-payment processing module 123 may perform control to repeatedly output the MST signal a designated number of times or for a designated time. After the completion of the MST signal transmission, the multi-payment processing module 123 may perform control to output a payment completion screen according to whether a specified condition is satisfied.

Regarding payment completion recognition, the multi-payment processing module 123 may determine whether the magnetic card reader is left using high-frequency transmission through the sensor unit 190 (e.g., a proximity sensor and a heart rate sensor), the camera 180, or a speaker and high-frequency reception through a microphone. When the magnetic card reader located within a certain distance is separated by more than a specified distance, the multi-payment processing module 123 may determine that the payment is completed.

According to various embodiments of the present disclosure, the multi-payment processing module 123 may determine whether the payment processing device 200 receives the notification sound. In connection with this, the multi-payment processing module 123 may determine whether a specified notification sound is received by activating a microphone during the MST method operation. The memory 130 may store at least one notification sound sample output by the payment processing apparatus 200 with respect to payment completion. After comparing the received notification sound with the stored notification sound, the multi-payment processing module 123 may determine that the payment is completed when the similarity therebetween is greater than a specified value.

According to various embodiments of the present disclosure, the multi-payment processing module 123 may determine whether a message completed according to the payment is received. In connection with this, the multi-payment processing module 123 may determine whether a word related to payment completion is included by parsing a message received within a specified time after the MST signal is transmitted. When receiving the message including the payment completion contents, the multi-payment processing module 123 may determine that the payment is completed.

According to various embodiments of the present disclosure, the multi-payment processing module 123 may operate a payment completion processing interface (e.g., a payment completion virtual key button, a back key, etc.) through which payment completion is processed upon user manipulation. When an input signal indicating completion of payment is received through the payment completion processing interface, the multi-payment processing module 123 may determine that it is payment completion.

The multi-payment processing module 123 may provide a barcode operation related interface. For example, the multi-payment processing module 123 may perform control to output a virtual key button for selecting a barcode method operation to the payment application execution screen. Alternatively, in connection therewith, the multi-payment processing module 123 may activate the camera 180 during execution of the payment application. The multi-payment processing module 123 may determine whether a designated subject (e.g., a scanner or infrared information) is detected by operating the camera 180. When the designated subject is detected, the multi-payment processing module 123 may perform control to automatically output the barcode information stored in the secure memory 165 to the display 150. During the time the bar code is output to the display 150, the multi-payment processing module 123 may perform processing to allow the brightness of the display 150 to be a specified value (e.g., a maximum value or a value greater than a specified illumination). The multi-payment processing module 123 may output the barcode to the display 150 for a specified time, and may perform barcode output termination and payment completion processing when specified conditions are satisfied.

With respect to the satisfaction of the specified condition, the multi-payment processing module 123 may determine that the payment is completed based on the obtained size change or distance change of the specified subject. For example, when the size of the body changes from greater than a certain size to less than a specified size, the multi-payment processing module 123 may determine that the payment is completed. Further, the multi-payment processing module 123 may determine payment completion based on at least one of whether a specified notification sound is received with the microphone, whether a message including payment completion content is received, and whether an input signal indicating payment completion occurs.

The handover processing module 125 may block access to another function of the electronic device 100 corresponding to a specified event occurring during the operation of the payment application. For example, the handover processing module 125 may perform control to output a handover execution related virtual key button to the display 150 during the execution of the payment application. Alternatively, the handover processing module 125 may identify the face of the user of the current electronic device 100 during execution of the payment application by automatically activating the camera 180. The handover function may be automatically performed if the user face is not the designated user face or there is no face. During this operation, the handover processing module 125 may collect the subject using the camera 180 at a certain time or in real time and determine whether a designated user face is recognized. When the designated user face is recognized, the handover processing module 125 may perform control to terminate the handover function.

According to various embodiments of the present disclosure, the handover processing module 125 may activate a fingerprint sensor and determine whether specified fingerprint information is input. When the designated fingerprint information is input, the handover processing module 125 may perform control to terminate the handover function. When the handover function is terminated, the handover processing module 125 may perform control to output a payment completion screen.

The handover processing module 125 may perform processing to allow the brightness of the display 150 to be a designated value (e.g., maximum brightness) during the execution of the handover function. The handover processing module 125 may readjust a turn-off timing of the display 150 (e.g., a time set for sleep entry) during the execution of the handover function. For example, in the case where the sleep entry state is set to a first time, when the handover function is performed, the handover processing module 125 may set a second time (e.g., a time longer than the first time) different from the first time as the sleep entry time. Alternatively, the handover processing module 125 may set a third time shorter than the first time as the sleep entry time according to a user setting. After the sleep entry, the handover processing module 125 may maintain the handover function even if an input of a designated key (e.g., a home key or a power key) occurs.

When the electronic device changes from a specified state (e.g., the front side where the display 150 is arranged is facing upward) to another state (e.g., the front side where the display 150 is arranged is facing downward), at least one of the multi-payment processing module 123 or the handover processing module 125 may output specified guidance information (e.g., guidance sound, guidance vibration, lamp blinking, etc.). The guidance information may include, for example, information for guiding to make the display 150 with the electronic device face up for the status of the payment process.

As described above, according to various embodiments of the present disclosure, an electronic device includes a first memory (e.g., a secure memory) configured to store payment information of an NFC method, payment information of an MST method, and fingerprint information, and a control module configured to control a multi-payment operation of the NFC method and the MST method when the fingerprint information obtained through fingerprint detection is valid. The control module controls signal processing information operated according to the NFC method and signal processing information operated according to the MST method to be output as one screen interface.

According to various embodiments of the present disclosure, the control module may display a signal transmission object for indicating a signal transmission start guidance for payment processing, a signal transmission direction operating according to the NFC method, or a signal transmission direction operating according to the MST method. After the fingerprint recognition is completed, a signal may be output to transmit the object.

According to various embodiments of the present disclosure, the control module may alternately operate the NFC method operation and the MST method operation, and differently display the signal transmission object during the payment operation of the NFC method and the signal transmission object during the payment operation of the MST method.

According to various embodiments of the present disclosure, the control module may determine whether or not the approach of a specified object (e.g., a magnetic card reader) is located within a specified distance through sensor operation during a payment operation of the NFC method, and transmit an MST signal according to an MST method operation when the object is located within the specified distance.

According to various embodiments of the present disclosure, the control module may activate the camera during multiple payment operations and automatically display the barcode object when an image including an object related to barcode recognition (e.g., a barcode scanner or infrared information) is captured.

According to various embodiments of the present disclosure, when it is determined that an object associated with barcode recognition is separated by more than a specified distance or disappears from the image, the control module may determine that payment is complete.

According to various embodiments of the present disclosure, the control module may display on the screen interface at least one of: a handover function object for maintaining a display state of at least a part of objects included in a current screen interface and limiting an operation to only a prohibition of switching to another function or to a barcode method, an object including operation guidance information related to payment execution, a signature object related to signature input, and a barcode method switching object for outputting a barcode.

According to various embodiments of the present disclosure, the control module may control a screen interface display including at least one of a barcode object and an object for switching to a multi-payment operation screen according to a barcode method switching object selection.

According to various embodiments of the present disclosure, the control module may output fingerprint detection guidance information related to handover function release during handover function execution according to the handover function object selection.

According to various embodiments of the present disclosure, the control module may perform a handover function for maintaining a display state of at least a part of an object included in a current screen interface and prohibiting switching to another function when a designated user face is not recognized after the camera is activated.

According to various embodiments of the present disclosure, the control module may perform control to automatically release a handover function in execution when a designated user face is recognized.

During the operation of the MST method or the barcode method, the control module may automatically perform the payment completion process corresponding to satisfaction of a specified condition (e.g., specifying at least one of notification sound reception, movement or disappearance of a specified object through image analysis, and reception of a message including the payment completion contents), or support a manual payment completion process by displaying a payment completion process-related object.

Fig. 3A is a flow diagram illustrating a method of NFC payment processing by an electronic device, according to various embodiments of the present disclosure.

Referring to fig. 3A, regarding a payment processing method of an electronic device according to various embodiments of the present disclosure, in operation 301, the control module 120 may execute a payment application according to a user input or information reception from the outside. In connection with this, the control module 120 may perform input setting related to the execution of the payment application (e.g., physical keys or virtual keys allocated for touch screen operation or the execution of the payment application). When the payment application is executed, the control module 120 may perform a control to activate the fingerprint sensor. The control module 120 may output guidance information for guiding fingerprint detection to the display 150 upon fingerprint sensor activation.

According to various embodiments of the present disclosure, when the payment application execution condition is a fingerprint recognition in a designated state of the electronic device (e.g., an off state of the display 150), the control module 120 may activate the fingerprint sensor before the payment application is executed. Alternatively, the control module 120 may activate the fingerprint sensor when a specified touch event occurs through a touch screen that is intermittently activated for a specified period of time in the off state of the display 150. Accordingly, the control module 120 may perform

operations

301 and 303 substantially simultaneously.

According to various embodiments of the present disclosure, when a designated touch event occurs from a touch screen activated in a designated period in an off state of the display 150, the control module 120 may perform control to output an object related to the execution of the payment application. When a second touch event (e.g., a swipe or drag event that is continuous with the first touch event) occurs, the control module 120 may perform control to execute the payment application. When the payment application is executed, the control module 120 may automatically activate the fingerprint sensor.

In operation 303, the control module 120 may determine whether the fingerprint authentication is successful. In this regard, the control module 120 may determine a similarity between the collected fingerprint authentication information and the fingerprint authentication information stored in the memory 165. If the fingerprint authentication fails because the similarity is less than the specified value or the fingerprint authentication is not performed within the specified time, the control module 120 may perform control to output the specified guide information related to the fingerprint authentication in operation 305. For example, the control module 120 may perform control to output guidance information for fingerprint authentication to the display 150. Alternatively, the control module 120 may perform control to output a warning message for notifying an erroneous fingerprint input.

If the fingerprint authentication is successful, the control module 120 may determine whether the token is valid in operation 307. In connection with this, the control module 120 may determine time information or usage count information of the token stored in the secure memory 165. If the token is valid, the control module 120 may perform the NFC method and the MST method in operation 309. For example, the control module 120 may alternately operate the NFC method and the MST method at a certain period. Alternatively, while supporting the NFC method, the control module 120 may determine the MST method according to whether a specified condition is satisfied by activating the sensor unit 190.

If the token is not valid, the control module 120 may perform control to terminate the payment application in operation 311. When the screen is terminated, the control module 120 may output guidance information for the reason of the termination of the screen (e.g., loss of token validity). Alternatively, the control module 120 may control the token-related designated boot information output in operation 311. For example, the control module 120 may perform control to output a message for requesting a token update. Alternatively, the control module 120 may perform control to output server device address information for token update to the display 150.

In operation 313, the control module 120 may determine whether an NFC device is detected. If an NFC device is detected within a specified period of time, the control module 120 may determine whether the NFC method payment is complete in operation 315. When the NFC-method payment is completed, the control module 120 may output payment completion guide information in operation 317. When the NFC method payment is not completed, the control module 120 may perform error processing in operation 319. For example, the control module 120 may control a warning message output for abnormal operation.

In operation 313, when the NFC device is not detected, the control module 120 may determine whether a designated time has elapsed while operating the MST method in operation 321. If the designated time elapses, the electronic apparatus 100 may output a retry screen in operation 323. For example, the electronic device 100 may output to the display 150 a virtual key button prepared for re-executing the MST method.

In operation 325, the control module 120 may determine whether an event related to barcode method switching occurs. In connection with this, the control module 120 may switch the relevant virtual key button to the retry screen output barcode method. According to various embodiments of the present disclosure, the control module 120 may output a barcode method switching-related virtual key button in operations 309 and 313. When a barcode method switching related event occurs, the control module 120 may provide a barcode method operation screen in operation 327. For example, the control module 120 may output barcode information stored in the secure memory 165 to the display 150. During this operation, the control module 120 may increase the barcode recognition rate by adjusting the brightness of the display 150 to a specified value. The control module 120 may restore the brightness of the display 150 to the original setting after the specified time elapses.

If the time specified in operation 321 has not elapsed or an event related to the barcode method switching has not occurred in operation 325, the control module 120 may branch to operation 313 and perform the subsequent operation again. In operation 327, after providing the barcode method operation screen, the control module 120 may determine whether an event related to function termination occurs. If no function termination related event occurs, the control module 120 may branch into operation 313 and perform the subsequent operation again. After operation 305, operation 311, operation 317, and operation 319, the control module 120 may branch into operation 329 and perform the branching according to whether termination is performed, according to various embodiments of the present disclosure.

According to various embodiments of the present disclosure, after providing the barcode method operation screen or transmitting the MST signal, the control module 120 may determine whether the payment completion condition is satisfied. When the payment completion condition is satisfied, the control module 120 may perform control to terminate application execution.

Fig. 3B is a flow diagram illustrating a MST-type payment processing method of an electronic device, according to various embodiments of the disclosure.

Referring to fig. 3B, with respect to the MST type payment processing method, in operation 331, the control module 120 may receive MST method operation-related events. With respect to MST method operations, in operation 333, the control module 120 may perform sensor operations. For example, the control module 120 may collect sensor information using at least one of a high frequency sensor, an acceleration sensor, a gyro sensor, a lighting sensor, a proximity sensor, and a heart rate sensor included in the sensor unit 190.

In operation 335, the control module 120 may determine whether a magnetic card reader is found. For example, the control module 120 may transmit a designated high frequency signal using the collected high frequency sensors and receive a high frequency signal corresponding thereto, thereby determining whether the magnetic card reader is within a designated distance. Alternatively, the control module 120 may utilize a proximity sensor or an illumination sensor to determine whether a particular object (e.g., an object intended to be a magnetic card reader) is nearby. Alternatively, the control module 120 may determine whether the user performs a designated gesture operation (e.g., an operation in which the user takes an electronic device (e.g., a smart phone or a wearable device) to a magnetic card reader) using sensor information of the acceleration sensor, the gyro sensor, and the heart rate sensor. According to various embodiments of the present disclosure, the control module 120 may collect surrounding images by operating the camera 180 and determine whether an object corresponding to the magnetic card reader is detected.

When the card reader is found, the control module 120 may send an MST signal in operation 337. For example, the control module 120 may send an MST signal stored in the secure memory 165. During this operation, the control module 120 may output to the display 150 which direction to send the MST signal. By this, the control module 120 may direct the user to allow the electronic device to be in a particular state.

In operation 339, the control module 120 may determine whether the payment completion condition is satisfied. For example, when a subject is captured by activating the camera 180 and the subject's size changes from greater than a certain size to less than a specified size or the subject disappears, the control module 120 may determine this as payment completion. Further, the control module 120 may determine that the payment is complete when a specified notification sound is received through the microphone within a specified time frame (e.g., during transmission of the MST signal). Alternatively, the control module 120 may determine the content of a message received during a specified time (e.g., during the MST signaling time or within a specified time after the MST signaling). When the payment completion content is included in the content, the control module 120 may determine this as payment completion.

When the payment completion condition is satisfied, the control module 120 may perform automatic payment completion in operation 341. For example, the control module 120 may perform control to output guidance information for guiding payment completion. When the payment completion condition is not satisfied, the control module 120 may determine that an event for payment termination occurs and process the payment termination in operation 343. For example, the control module 120 may process the payment termination in response to an input signal occurrence according to a hardware back key selection. Alternatively, in operation 343, if the payment termination-related event does not occur, the control module 120 may branch to operation 333 and perform the subsequent operation again.

Fig. 3C is a flow diagram illustrating a barcode-type payment processing method of an electronic device, according to various embodiments of the present disclosure.

Referring to fig. 3C, with respect to the barcode-type payment processing method, the control module 120 may receive an event for requesting a barcode method operation in operation 351. For example, the control module 120 may receive an event according to a virtual key button selection for a barcode method operation. Alternatively, the control module may perform control to operate the barcode method in addition to the NFC method and the MST method according to a specified schedule.

In operation 353, the control module 120 may activate the camera 180. For example, the control module 120 may activate the first camera 181 disposed at the front surface and analyze the obtained image. In operation 355, the control module 120 may perform scanner detection based on the analyzed image. For example, the control module 120 may determine whether a specified subject corresponding to a scanner or barcode recognition device is in the analyzed image. Further, the control module 120 may determine whether the size of the specified subject is the specified size or whether the specified subject is detected within a specified distance.

When the designated subject is detected, the control module 120 may perform control to output the barcode to the display 150 in operation 357. In operation 359, the control module 120 may determine whether a payment completion condition is satisfied. For example, the control module 120 may determine whether a specified time elapses after the barcode is output, whether the size of the specified subject changes from being larger than a certain size to being smaller than the specified size or whether the specified subject disappears, whether a specified notification sound is collected using a microphone, whether payment is completed, and whether a message including content is received.

When at least one of the above-described payment completion conditions is satisfied, the control module 120 may process this as automatic payment completion in operation 361. For example, the control module 120 may perform control to output the specified payment completion information to the display 150. Alternatively, when a payment completion message is received, the control module 120 may perform control to automatically output a corresponding payment completion message to the display 150. When the payment completion condition is not satisfied, the control module 120 may determine whether a manual input (e.g., a hardware back key input) for payment termination occurs in operation 363. If no function termination related event has occurred, the main control module 120 may return to operation 353 and perform the subsequent operations again.

Fig. 4 is a flow diagram illustrating a handover function in a payment processing method according to various embodiments of the present disclosure.

Referring to fig. 4, with respect to the handover function, the control module 120 may execute a payment application in operation 401. The control module 120 may activate the fingerprint sensor corresponding to the payment application execution. When the fingerprint sensor initialization is completed, the control module 120 may output an object or guide information for guiding fingerprint detection.

In operation 403, the control module 120 may determine whether the fingerprint authentication is successful. When the fingerprint authentication fails, the control module 120 may output fingerprint-related guide information in operation 405. For example, the control module 120 may perform a process for performing fingerprint authentication again when the fingerprint authentication fails.

When the fingerprint authentication is successful, the control module 120 may prepare for a multi payment operation in operation 407. For example, the control module 120 may prepare for multi payment operations of the NFC method and the MST method. During this operation, the control module 120 may activate the NFC chip 161 and operate the sensor unit 190 to determine the MST signal transmission time point. Meanwhile, the control module 120 may perform input setting related to the handover function execution (e.g., output of a virtual key button related to the handover function execution).

In operation 409, the control module 120 may determine whether a handover function execution request occurs. For example, the control module 120 may determine whether a virtual key button selection signal for handover function execution occurs. When the virtual key button selection signal occurs, the control module 120 may determine that a handover function execution request occurs. According to various embodiments of the present disclosure, during preparation for multi-payment operations, the control module 120 may recognize the face of the current user by activating the camera 180. When the face of the designated user is not recognized from the image obtained by the camera 180, the control module 120 may determine this as a handover function execution request.

When the handover function execution request occurs, the control module 120 may lock the current screen in operation 411. During this operation, the control module 120 may perform control to continuously output the current screen. In addition, the control module 120 may perform processing to allow the brightness of the display 150 to be a designated value. Further, the control module 120 may perform a process to allow the sleep state of the display 150 to enter a designated value.

In operation 413, the control module 120 may determine whether a specified condition is satisfied. If the specified condition is not satisfied, the control module 120 may branch to operation 411 and maintain the screen lock state. The specified condition may be, for example, a condition in which the user fingerprint is to be recognized again. The specified condition may include at least one of a specified pattern lock release condition, a specified number lock release condition, and a specified voice lock release condition. Alternatively, the specified condition may be a collection of sensor information corresponding to the specified gesture. Alternatively, the specified condition may be a specified time elapsed condition after completion of the payment.

According to various embodiments of the present disclosure, the control module 120 may maintain the screen lock state, but turn off the display 150 when a designated time elapses. When a designated input event occurs after the display 150 is turned off, the control module 120 may output a previous screen lock state screen. The control module 120 may continuously maintain the screen lock state until a specified condition is satisfied.

If the specified condition is satisfied, the control module 120 may release the handover function in operation 415. For example, the control module 120 may release the screen lock state and perform control to return to the payment application execution screen. In a state of being completed according to a specified condition of payment completion, if the handover function is released (e.g., screen lock release performed according to authentication after payment completion), the control module 120 may output guidance information according to payment completion to the display 150. When a specified condition is satisfied in a state where payment completion is not formed, the control module 120 may output a screen corresponding to the payment incomplete state. Alternatively, the control module 120 may output a screen corresponding to the payment error processing status.

In operation 417, the control module 120 may determine whether an event related to termination of the function occurred. If a function termination related event occurs, the control module 120 may terminate the payment application execution and turn off the display 150. If no function termination related event occurs, the control module 120 may branch to operation 407 and perform the subsequent operation again.

According to various embodiments of the present disclosure, a payment processing method of an electronic device may include performing fingerprint detection, and outputting signal processing information operating according to an NFC method and signal processing information operating according to an MST method as one screen interface when fingerprint information obtained through the fingerprint detection is valid.

Fig. 5 illustrates a payment application execution screen of an electronic device, in accordance with various embodiments of the present disclosure.

Referring to fig. 5, the display 150 of the electronic device 100 may output a payment application execution screen 500. The payment application execution screen 500 may include, for example, a menu object 510, a first virtual card object 521, a second virtual card object 522, a first total card (total card) information object 513, and scan guidance information 514.

The menu object 510 may include an application name, an addition item "ADD (ADD)" for adding a virtual card, and an item "MORE (MORE)" related to application settings. When the add item "add" is selected, the control module 120 may provide a screen interface related to virtual card addition. When the item "more" is selected, the control module 120 may provide a screen interface related to the total virtual card setting or the virtual card operation method setting.

The first virtual card object 521 may be, for example, a designated virtual card. For example, the first virtual card object 521 may be an object corresponding to a most recently used virtual card. Alternatively, the first virtual card object 521 may be a newly registered virtual card object. Alternatively, the first virtual card object 521 may be a virtual card object that is most frequently used during a specified period.

The first virtual card object 521 may be provided as an initial screen when the payment application is executed. The first virtual card object 521 may be output in a certain size at the center of the screen as shown.

The second virtual card object 522 may be the next most recently used virtual card object. Alternatively, the second virtual card object 522 may be a next-recently-registered virtual card object or a next-frequently-used virtual card object. Alternatively, the second virtual card object 522 may be an object related to the first virtual card object 521. For example, the second virtual card object 522 may be a loyalty or discount card associated with the first virtual card object 521. As shown, a partial image of the second virtual card object 522 may be output. When a swipe touch event or a flick touch event or a drag event occurs, or an event for touching the second virtual card object 522 occurs, the second virtual card object 522 may be output at the position of the first virtual card object 521.

The first bus card information object 513 may have a number corresponding to the number of virtual card objects. As shown, the first total card information object 513 may represent, for example, a state in which three virtual card objects are registered in the payment application. The first bus card information object 513 may indicate an order of the virtual objects currently displayed. For example, the first total card information object 513 may visually display position information regarding which number in the order in which the currently displayed virtual card object corresponds to the total virtual card object by displaying the color of a specific point of the object to be different from the surroundings.

The scan guide information 514 may include information for guiding fingerprint detection necessary for operating the currently displayed virtual card object. When the currently displayed virtual card object (e.g., first virtual card object 521) does not require scanning (e.g., fingerprint detection), the scan guide information 514 may not be displayed. For example, when the displayed virtual card object (e.g., the virtual card object displayed larger than a specified area) is a loyalty card or a discount card, the scan guidance information 514 may not be displayed or additional guidance information (e.g., discount information, loyalty scraping guidance information, etc.) may be displayed. The scan guide information 514 may include at least one of text for guiding that fingerprint detection is required and an image (e.g., a partial image of a fingerprint) corresponding to a position for fingerprint detection.

6A, 6B, 6C, and 6D illustrate card search screen interfaces of electronic devices according to various embodiments of the present disclosure.

Referring to fig. 6A, 6B, 6C, and 6D, the control module 120 of the electronic device 100 may output a payment application execution screen to the display 150 as shown in fig. 6A. The payment application execution screen may include a first virtual card object 521, a second virtual card object 522, a second total card information object 603, and scan guide information 514 as described with reference to fig. 5. The second total card information object 603 may correspond to the number of virtual card objects registered in the payment application. For example, the second total card information object 603 may include images corresponding to the number of six registered virtual card objects.

When the specified event occurs, the control module 120 may output a card thumbnail list 610 as shown in fig. 6B. For example, the control module 120 may output the card thumbnail list 610 when an event for selecting the first bus card information object 513 occurs or a designated gesture event (e.g., a long tap touch event occurring at a designated location) occurs. Although it is shown in the drawing that the card thumbnail list 610 is disposed at the lower end of the screen, various embodiments of the present disclosure are not limited thereto. For example, the card thumbnail list 610 may be output full screen. Further, with respect to the card thumbnail list 610, the card thumbnail objects may be arranged in a matrix and displayed.

The card thumbnail list 610 may include, for example, a first card thumbnail object 611, a second card thumbnail object 612, a third card thumbnail object 613, a fourth card thumbnail object 614, a fifth card thumbnail object 615, and a sixth card thumbnail object 616. The first card thumbnail object 611 may include, for example, a thumbnail image of the first virtual card object 521. Similarly, the Nth card thumbnail object may include a thumbnail image of the Nth card thumbnail object. The card thumbnail list 610 may display a card thumbnail object corresponding to a virtual card image arranged at the center of the current screen differently from other card thumbnail objects. For example, the first card thumbnail object 611 corresponding to the first virtual card object 521 displayed full screen on the display 150 may be displayed with a highlight effect.

Further, the card thumbnail object displayed in the card thumbnail list 610 may be selected by the user. For example, the third card thumbnail object 613 may be selected by a touch event. When an input signal for selecting the third card thumbnail object 613 occurs, the control module 120 may display a third virtual card object 523 corresponding to the selected third card thumbnail object 613 in the center of the screen as shown in fig. 6C. During this operation, the control module 120 may remove the card thumbnail list 610 from the display 150 and output the second total card information object 603 and the scan guide information 514. Here, when the third virtual card object 523 is a card necessary for additional scanning, the output of the scanning guide information 514 may be omitted.

The second total card information object 603 may have a different display form according to the display of the third virtual card object 523. For example, with respect to the second total card information object 603, points corresponding to the order of the third virtual card object 523 may be displayed differently from the surrounding area. Since the third virtual card object 523 is disposed at the center of the screen, the control module 120 may perform control to display a partial image of the second virtual card object 522 at the left edge and a partial image of the fourth virtual card object 524 at the right edge. When the left swipe touch event (or flick event or drag event) occurs, the control module 120 may perform control to arrange the fourth virtual card object 524 in the center of the screen. Further, when the right swipe touch event (or flick event or drag event) occurs, the control module 120 may perform control to arrange the second virtual card object 522 in the center of the screen.

According to various embodiments of the present disclosure, when the third virtual card object 523 is disposed at the center of the screen, the control module 120 may dispose the card object related to the third virtual card object 523 at the position of the second virtual card object 522 and the position of the fourth virtual card object 524. The associated card object may include, for example, a credit or rebate card associated with the third virtual card object 523, or a card including the same card name greater than a specified length. The loyalty card or rebate card may be registered as a related card, for example, according to user settings during a third virtual card registration process. Cards having the same card name greater than a specified length may be automatically registered as related cards according to the control of the control module 120. If there is no related card object, the control module 120 may arrange the virtual card objects according to the order of the card thumbnail list 610.

According to various embodiments of the present disclosure, as shown in fig. 6D, the control module 120 may support order conversion in the card thumbnail list 610. For example, when an event related to the movement of the first card thumbnail object 611 occurs (e.g., an event of long-pressing the first card thumbnail object 611), the control module 120 may display the first card thumbnail object 611 in a state of being in the order in the conversion card thumbnail list 610. For example, the control module 120 may display the first card thumbnail object 611 using a different layer than the additional card thumbnail objects. When an event (e.g., a drag event) for moving the first card thumbnail object 611 occurs, the control module 120 may move the first card thumbnail object 611 according to the corresponding event. The control module 120 may change the positions of the other card thumbnail objects according to the movement of the first card thumbnail object 611. For example, when the first card thumbnail object 611 is moved and overlaps more than the middle of the second card thumbnail object 612, the second card thumbnail object 612 may be automatically moved to the position where the first card thumbnail object 611 was previously located. When the event of selecting the first card thumbnail object 611 is released, the first card thumbnail object 611 may be disposed at the event release position.

According to various embodiments of the present disclosure, when the first card thumbnail object 611 is moved and arranged at a designated position, the first card thumbnail object 611 may be replaced with a card thumbnail object arranged at a corresponding position. For example, when the touch event is released in a state where the first card thumbnail object 611 overlaps the sixth card thumbnail object 616 by more than a designated size, the first card thumbnail object 611 is moved to a place where the sixth card thumbnail object 616 was previously located and the sixth card thumbnail object 616 is moved to a place where the first card thumbnail object 611 was previously located.

According to various embodiments of the present disclosure, although it is exemplarily described above that the thumbnail object is arranged with respect to the virtual card, various embodiments of the present disclosure are not limited thereto. For example, the card thumbnail object may be in the form of a list of card objects using each card name as a list.

Although the display of all virtual card objects in the card thumbnail list 610 is exemplarily described above according to various embodiments of the present disclosure, various embodiments of the present disclosure are not limited thereto. For example, the card object list may include a scroll bar or scroll control virtual keys for displaying only some of the entire virtual card objects and later displaying the remaining objects.

7A, 7B, 7C, and 7D illustrate payment completion screen interfaces of an electronic device according to various embodiments of the present disclosure.

Referring to fig. 7A, 7B, 7C, and 7D, as shown in fig. 7A, the control module 120 may output a payment completion message 710 when the payment is completed. For example, in the case where payment is completed through the NFC chip, the control module 120 may output the payment completion message 710 when a specified condition corresponding to payment completion is satisfied during the operation of the MST method or the barcode method. During this operation, if the brightness of the display 150 is adjusted during the payment process, the control module 120 may restore the brightness of the display 150 to a previous value. Further, in the case where the lamp blinks to guide payment during the payment processing procedure, the control module 120 may turn off the lamp according to payment completion. Alternatively, the control module 120 may perform control to output a designated vibration pattern corresponding to payment completion.

As shown in fig. 7B, an event related to a shortcut panel call disposed at a certain position of the display 150, for example, at the top of the display 150 may occur. For example, when a shortcut panel call touch event 730 that moves from a specified location (e.g., outside of the display area) at the upper end of the display 150 to the inside of the display 150 (e.g., inside of the display area) occurs, the control module 120 may dim a certain area of the display 150 (e.g., display the certain area at a lower than specified illuminance).

When the shortcut panel call touch event 730 occurs, the control module 120 may output a shortcut panel (quick panel)750 to the display 150 as shown in FIG. 7C. The shortcut panel 750 may include, for example, a payment completion item 751. When the event of selecting the payment completion item 751 occurs, the control module 120 may output a payment completion information screen as shown in fig. 7D. The payment completion information screen may include, for example, a message provided from a server device that performs payment processing or information processed based on the corresponding message (for example, information obtained by extracting specified information such as payment card information, payment location information, payment amount information, and the like).

Fig. 8A illustrates an NFC method and MST method support screen of an electronic device, according to various embodiments of the disclosure.

Referring to fig. 8A, if fingerprint authentication is completed after the payment application is executed, the control module 120 may perform control to output a multi-payment operation screen to the display 150. The multi-payment operation screen may include, for example, a signal transmission object 810, a first visual guidance information object 820 for describing a payment method, a signature object 830, a first handover function execution object 841, a gesture (position) guidance object 850, and a barcode switching object 860.

The signaling object 810 may be output after fingerprinting is complete. The signaling object 810 may be output in the form of wave animation (wave animation), for example. Signaling object 810 may guide the user in bringing electronic device 100 to payment processing device 200 by providing feedback to the user that the signal began to be transmitted. The location of the signaling object 810 may have a screen configuration as follows: wherein the signal transmitting object 810 is arranged on top of the MST coil to naturally guide the electronic device 100 to the corresponding location.

According to various embodiments of the present disclosure, the signal transmission object 810 may be information for guiding an NFC signal transmission direction or an MST signal transmission direction. According to an embodiment of the present disclosure, the signal transmission object 810 may be set to indicate a direction of a signal transmitted through the NFC antenna or the MST coil. The signal transmission object 810 may be displayed during transmission of an NFC signal or transmission of an MST signal. Regarding the signal transmission object 810, the color of the signal transmission object corresponding to NFC signal transmission may be different from the color of the signal transmission object corresponding to MST signal transmission. Alternatively, the signal transmission object 810 may include a character indicating NFC displayed at a fixed position during NFC signal transmission or a character indicating NFC moving in a specified direction (e.g., a direction in which a signal is transmitted). Similarly, signal transmitting object 810 may include characters indicating an MST displayed at a fixed location during MST signal transmission or characters indicating an MST moving in a specified direction (e.g., the direction in which the signal is transmitted). According to various embodiments of the present disclosure, when the NFC method and the MST method are alternately operated, the electronic device 100 may intuitively indicate which type of signal is currently being transmitted through a change of characters.

The first visual guidance information object 820 may include a video image or a slide image. For example, the first visual guidance information object 820 may include information representing how to operate the electronic device 100 with respect to a multi payment method and in which state the electronic device 100 is currently in.

The signature object 830 may be an object for receiving a signature of a user. The signature object 830 may be displayed with an empty region, for example, and output signature information corresponding to a touch gesture of a user. The signature object 830 may not be output according to the type of the virtual card. For example, when a loyalty card or rebate card operates, signature object 830 may not be output.

The first handover function execution object 841 may be a virtual key button for switching to a handover function. When the first handover function execution object 841 is selected, the control module 120 may enter a current screen lock state according to the handover function execution. When the handover function is performed, the control module 120 may output guidance information related to fingerprint detection for fingerprint sensor activation and handover function release. Alternatively, the control module 120 may output guidance information for activating the camera and requesting to capture a designated user face. During this operation, the screen lock screen may output a thumbnail preview region related to the user's face capture. The thumbnail preview area may be, for example, a display area in which a capture state is determined during the front camera capturing an image. The user may move corresponding to the focus position of the front camera by determining the thumbnail preview area.

Gesture guidance object 850 may include textual information for guiding in which form electronic device 100 is to be positioned.

The barcode switch object 860 may be a virtual key button for switching to a barcode method. When the barcode switch object 860 is selected, a barcode method operation screen as shown in fig. 8B may be output to the display 150.

When a screen (e.g., a display) of the electronic apparatus 100 is in a specified posture (e.g., face down), the electronic apparatus 100 may output specified guidance information (e.g., information for guiding the display of the electronic apparatus to face up).

Fig. 8B illustrates a barcode method operational screen of an electronic device, according to various embodiments of the present disclosure.

Referring to fig. 8B, when the barcode switch object 860 described with reference to fig. 8A is selected, the control module 120 may perform control to output a barcode method operation screen to the display 150 as shown. The barcode method operation screen may include, for example, a barcode object 870, a second handover function execution object 842, a multi-payment method switching object 880, barcode usage guidance information 890, and a signature object 830.

Barcode object 870 may include, for example, a barcode image and barcode digital information. When the barcode object 870 is output, the control module 120 may perform a process to display the barcode image brighter than the surroundings. Based on this, the electronic device 100 may reduce scanning errors during barcode image scanning. Alternatively, the control module 120 may perform control to make the illuminance of the display 150 greater than a specified value during the barcode image output.

The second handover function execution object 842 may be a virtual key button substantially the same as the first handover function execution object 841 described with reference to fig. 8A. The second handover function execution object 842 output from the barcode method operation screen may be output to a designated area not overlapping with the barcode image. Alternatively, the size of the second handover function execution object 842 may be adjusted based on the size of the barcode object 870.

The multi payment method switching object 880 may be an object related to switching to the multi payment method (e.g., a method of operating the NFC method and the MST method in combination) described with reference to fig. 8A. The multi payment method switching object 880 may be in the form of a virtual key button. The multi payment method switching object 880 may be output to, for example, a point similar to the point where the barcode switching object 860 of the screen described with reference to fig. 8A is disposed.

Barcode usage guidance information 890 may include, for example, textual information describing the operation of electronic device 100 with respect to barcode method operations. Further, the barcode usage guidance information 890 may further include information for guiding execution of the handover function with respect to security during a process of handing over the electronic apparatus 100 to another person.

The signature object 830 may be the same as the signature object described with reference to fig. 8A. For example, the signature object 830 may support user signature input.

According to various embodiments of the present disclosure, when the barcode method operation screen is output to the display 150, the second handover function execution object 842 is not output, and the camera may be automatically activated. The control module 120 may perform a process to automatically perform a handover function if the designated user face recognition is not performed through the camera. The control module 120 may automatically release the handover function if the execution of the payment application is terminated or payment completion information is displayed according to the user input. With regard to the handover function being automatically deactivated, the control module 120 may automatically deactivate the activated camera.

Fig. 9 illustrates a multiple payment operation re-execution screen of an electronic device, in accordance with various embodiments of the present disclosure.

Referring to fig. 9, when a designated time elapses after the MST signal is transmitted, the control module 120 may output a multi payment operation re-execution screen to the display 150 as shown. The multi payment operation re-execution screen may include, for example, a second visual guidance information object 920 and a re-execution object 930.

The second visual guidance information object 920 may include a video, a slide image, or a still image related to an operation for re-performing a plurality of payment operations. The second visual guidance information object 920 may include different information than the first visual guidance information object 820.

The re-execution object 930 may be a virtual key button set to re-execute the multi payment method. When the event of selecting the re-execution object 930 occurs, the control module 120 may re-execute the multi payment method operation described with reference to fig. 8A. Alternatively, according to various embodiments of the present disclosure, while the re-execution object 930 is output, the control module 120 may perform control to re-execute only the MST signaling when the re-execution object 930 is selected in the case of maintaining the NFC method.

Fig. 10A and 10B illustrate handover function execution screens according to various embodiments of the present disclosure.

Referring to fig. 10A and 10B, when the payment application is executed, as shown in a screen 1001, the control module 120 may perform control to output a multi-payment operation screen to the display 150. Alternatively, if the fingerprint authentication is completed after the payment application is executed, the control module 120 may perform control to output a multi-payment operation screen as shown in a screen 1001.

The screen 1001 may be in the following state: as the handover function is executed, a plurality of payment operation screens are provided in the screen lock state. The multi-payment operation screen performing the handover function may include, for example, a signal transmission object 810, a first visual guidance information object 820, a gesture guidance object 850, a barcode switching object 860, and a handover function release guidance object 855.

The barcode switching object 860 may be a toggle switch (toggle) object for barcode switching among objects for switching a barcode method and a multi payment method. The barcode switch object 860 may include at least one of image information and text information for guiding barcode switching. The output position of the barcode switch object 860 may be changed according to user settings. For example, the barcode switch object 860 may be disposed at a position adjacent to the position of the gripped hand.

The handover function release guidance object 855 may include information for guiding a processing operation for handover function release. For example, the handover function release guidance object 855 may include information for guiding that fingerprint detection is required for handover function release.

In the screen 1001, a barcode method operation screen may be output as shown in a screen 1003 in response to selection of the barcode switch object 860. According to various embodiments of the present disclosure, the handover function may allow bar code method switching or multi-payment method switching. Alternatively, the handover function may be set not to allow the operation of switching the object according to user settings. If the handover function can be set not to allow the operation of switching the object, the barcode switching object 860 can be selected in a case where the handover function release function is performed. As described above, the control module 120 may support toggle switch switching of a multi-payment method or a barcode method.

The barcode method operation screen may include a barcode object 870, a multi payment method switching object 880, barcode usage guidance information 890, and a handover function release guidance object 855 as shown. Since the handover function allows the payment method switching function, the handover function can be inherited when the barcode method switching is requested in a state where the handover function is set during the multi-operation screen output. Accordingly, the barcode method operation method may have a state in which the handover function is automatically performed. Further, the control module 120 may perform control to output a handover function release guidance object 855 for guiding the handover function release. When the multi payment method switch object 880 is selected, the control module 120 may perform processing to return to the screen 1001.

As described above, according to various embodiments of the present disclosure, a payment processing method may include: one card among the plurality of virtual cards is selected and displayed when entering the main screen, and guide information for guiding fingerprint recognition is displayed at the lower end of the screen.

According to various embodiments of the present disclosure, the method may further comprise at least one of entering a fast navigation mode by long tapping on the virtual card and changing the order of the virtual cards based on a drag event to the virtual card.

According to various embodiments of the disclosure, the method may further comprise displaying at least one of: information for booting by integrating an NFC method and an MST method of placing a card on a designated reader into one screen, a signaling boot object, a visual boot information object, a card signature object, and a handover function execution related object.

According to various embodiments of the present disclosure, the method may further include processing payment according to the NFC payment method when the card is disposed near the NFC payment processing device after the MST method and the NFC method are activated on the multi-payment operation screen of the MST method and the NFC method.

According to various embodiments of the present disclosure, the method may further comprise: whether the card is in proximity to a magnetic card reader is determined based on at least one of a high frequency transmission method through a proximity sensor, a camera of an electronic device, a heart rate sensor, or a speaker with respect to power and a payment card token, and a high frequency reception method through a microphone, and an MST signal is transmitted when the card is in proximity to the magnetic card reader.

According to various embodiments of the present disclosure, the method may further comprise: the MST signal transmission is performed for a designated time or a designated number of times, and a virtual key button for re-performing the MST signal transmission is output after a designated period of time or a designated number of times. The output of the virtual key button may include displaying the virtual key button in the center of a wavelength representing the signaling.

According to various embodiments of the present disclosure, the method may include automatically terminating payment operations (or payment mode or payment operations) when the card is away from the magnetic card reader by utilizing high frequency transmission through a proximity sensor, a camera of the electronic device, a heart rate sensor, or a speaker, and high frequency reception through a microphone.

According to various embodiments of the present disclosure, the method may further include outputting the barcode object to a plurality of payment operation screens.

According to various embodiments of the present disclosure, the method may further include automatically terminating the payment operation by detecting a payment completion notification sound of the micropayment processing apparatus.

According to various embodiments of the present disclosure, the method may further include automatically terminating the payment operation upon receiving a payment completion related message from at least one of the multi-payment operation screen and the barcode payment operation screen.

According to various embodiments of the present disclosure, the method may further include outputting a barcode switching object from the multi-payment operation screen, outputting a barcode method operation screen including a barcode object larger than a specified size when the barcode switching object is selected, outputting an object for switching the barcode method operation screen to the multi-payment operation screen, and outputting the multi-payment operation screen when the multi-payment operation screen switching object is selected.

According to various embodiments of the present disclosure, the method may further comprise at least one of: switching to a barcode screen when the barcode reader is recognized by a front camera of the electronic device, and automatically terminating the payment operation when it is determined by the front camera of the electronic device that the barcode reader is far from the screen.

According to various embodiments of the present disclosure, the method may further include outputting information for guiding maintenance of a designated posture (e.g., a posture in which a rear surface of the electronic device faces downward) to a user through vibration and voice when it is recognized that the front surface of the electronic device is rotated to a lower end using the gyro sensor and the front proximity sensor.

According to various embodiments of the present disclosure, the method may further include performing a restricting operation to perform payment when gesture information corresponding to a specified operation (e.g., information obtained by digitizing or patterning an operation for moving the wearable device to a specific place (e.g., a point where a reader is located)) is obtained when the electronic device is the wearable device.

According to various embodiments of the present disclosure, the method may further include outputting a handover function object, temporarily stopping a function provided from the electronic device except for a plurality of payment operation screens or a barcode operation screen when the handover function object is selected, and releasing the handover function when the designated fingerprint information is recognized.

11A, 11B, 11C, 11D, and 11E illustrate payment execution-related screen interfaces according to various embodiments of the present disclosure.

Referring to fig. 11A, 11B, 11C, 11D, and 11E, when a specified event occurs, as shown in screen 1101, electronic device 100 may output a payment card image 1110 to display 150. As shown in screens 1101 to 1109, the electronic apparatus 100 may display a payment available state by outputting a designated image effect to one side of the payment card image 1110. For example, the electronic device 100 may output a circle object 1120 having a gradually changing size to one side (e.g., an upper side) of the payment card image 1110. A circle object 1120 of varying size may be disposed on the back of the payment card image 1110. The circle object 1120 of varying size may be changed in a form of gradually increasing radius, for example. While the size of one circle object 1120 is gradually changed in a certain area of the payment card image 1110, when the size of the one circle object 1120 is greater than a certain size, a new circle object 1130 may be displayed. The new circle object 1130 may have a different color than the previous circle object 1120. The new circle object 1130 may be changed at the same speed as the previous circle object 1120. During the payment available state, the electronic apparatus 100 may repeatedly display the screens 1101 to 1109. According to an embodiment of the present disclosure, the electronic apparatus 100 may display the payment status through a pop-up message. According to an embodiment of the present disclosure, the electronic device 100 may notify the user of the payment status by turning on the LED. According to an embodiment of the present disclosure, the electronic apparatus 100 may output the MST signal while displaying the payment available status screen. According to an embodiment of the present disclosure, the electronic apparatus 100 may simultaneously or alternately display at least one of a screen among the screens 1101 to 1109 and a barcode form corresponding to the token-related information.

According to an embodiment of the present disclosure, the electronic apparatus 100 may determine whether the NFC terminal exists within a certain range of the electronic apparatus 100 while displaying the screens 1101 to 1109. For example, the electronic device 100 may determine the presence of an NFC terminal by detecting a signal transmitted from an NFC terminal within a certain range. After confirmation, the electronic device 100 may process the payment by sending a token and encryption information (e.g., password) to the NFC terminal via the NFC communication method.

When approaching or entering a store (that is, an environment where payment POS-related information is collected), the electronic device 100 may previously recognize whether NFC, MST, or barcode of the payment POS is supported, and change UI and operation of the payment application based on the recognized support information. For example, the electronic device 100 may identify a location through the technology of a GPS or an indoor location-based service (LBS) module or identify a location using location information of a short-range or long-range network. Based on the location information, the electronic device 100 may identify whether the NFC, MST, or barcode of the POS is supported. According to various embodiments of the present disclosure, the electronic device 100 may identify whether NFC, MST, or barcode of the payment POS is supported based on beacon information of Bluetooth or Bluetooth Low Energy (BLE) or frame data of Wi-Fi. The payment application may operate only one module of NFC/MST/barcode during the actual payment based on the POS information.

According to embodiments of the present disclosure, electronic device 100 may direct electronic device 100 in the direction of the user during payment. For example, a communication signal for payment may be sent through the back of the electronic device 100. In this case, in order to allow the back of the electronic apparatus 100 to point to the payment reader, the electronic apparatus 100 may guide a direction in which the electronic apparatus 100 is to be aimed or a state to be taken by the electronic apparatus 100 through a screen (e.g., text output, image output, and video output), sound, vibration, or tactile sense. According to an embodiment of the present disclosure, when it is determined that the payment reader is close using a proximity sensor on the front of the electronic device, the electronic device 100 may guide the user that the electronic device 100 should be flipped over by audio or allow the user to recognize the payment reader close by vibration or tactile sensation.

Fig. 12 illustrates a token validity related screen interface in accordance with various embodiments of the present disclosure.

Referring to fig. 12, the electronic apparatus 100 may display a screen on the display 150 when the card-related token is invalid. According to an embodiment of the present disclosure, electronic device 100 may output a pop-up notification 1220 related to card validity to display 150. According to an embodiment of the present disclosure, a pop-up notification 1220 may be displayed on the payment card image 1210. When an event of selecting "OK" (e.g., a user touch input or a user voice input corresponding to the OK selection) occurs, the electronic device 100 may terminate the payment application. According to an embodiment of the present disclosure, the electronic device 100 may determine whether the token is valid depending on whether a specified usage period of the token is exceeded, and may determine that the corresponding token is invalid when the specified usage time is exceeded.

Fig. 13 illustrates a token validity-related screen interface in accordance with various embodiments of the present disclosure.

Referring to fig. 13, according to an embodiment of the present disclosure, when the token is valid, the electronic device 100 may transmit the MST signal and determine whether to continuously transmit the MST signal. Alternatively, the electronic device 100 may transmit the MST signal when the token is valid. When MST signaling terminates, electronic device 100 may output a retry related menu item 1320 to display 150 as shown. According to an embodiment of the present disclosure, a menu item 1320 may be displayed on the payment card image 1310. When an event related to the selection of the menu item 1320 occurs, the electronic apparatus 100 may perform an operation by repeating the screens 1101 to 1109 described with reference to fig. 11.

According to an embodiment of the present disclosure, the electronic apparatus 100 may determine whether a payment completion message is received from the outside while continuously transmitting the MST signal. When the payment completion message is received, the electronic device 100 may determine that the payment is completed. In this case, the electronic device 100 may stop MST signaling and display payment completion.

According to an embodiment of the present disclosure, the payment completion message may be a message sent from the token server. According to an embodiment of the present disclosure, the payment completion message may be a message transmitted from an issuer (e.g., a card server or a financial server). According to embodiments of the present disclosure, the payment completion message may be a message sent from a POS device. According to an embodiment of the present disclosure, when an error occurs during a payment transaction, the electronic apparatus 100 may output a message related to the transaction error through at least one of audio, image, and text.

Fig. 14A and 14B illustrate MST signal processing operations, according to various embodiments of the disclosure.

Referring to fig. 14A and 14B, the electronic device 100 may use at least one method related to the start of MST signaling. In the case of MST, one-way communication may be used in which electronic device 100 sends a signal to POS device 1400. According to an embodiment of the present disclosure, the electronic device 100 may transmit the payment signal by detecting whether the POS device 1400 is disposed at a position for receiving the MST signal transmitted from the electronic device 100. For example, when it is determined with a proximity sensor that there is a proximity body within a certain distance, the electronic device 100 may determine the proximity body as the POS device 1400 as shown in state 1401. The electronic device 100 may initiate MST signaling based on the proximity detection result in a payment processing related scenario. Alternatively, as shown in state 1403, the electronic device can begin MST signaling when a particular image or pattern displayed at a particular location of the POS device 1400 is recognized with the camera.

According to an embodiment of the present disclosure, the electronic device 100 may stop MST signaling using at least one method. The electronic device 100 may determine that the payment is terminated based on the occurrence information. According to an embodiment of the present disclosure, when an event occurring according to the completion of payment is detected from the POS device 1400, the electronic device 100 may stop the payment signal based thereon. For example, when the reception output sound and the payment completion notification sound occurring from the POS device 1400 are detected, the electronic apparatus 100 may determine the detected signal as the signal for payment termination occurring. In connection with this, the electronic apparatus 100 may store and manage an audio database corresponding to receiving the output sound or the payment completion notification sound. The electronic apparatus 100 may determine the occurrence of a reception output sound or a payment completion notification sound collected based on the stored audio database.

According to an embodiment of the present disclosure, the electronic device 100 may determine that the payment is completed through the payment completion related information received from the designated server and may stop the payment-related MST signaling. For example, the electronic apparatus 100 may receive the payment-related message in the form of SMS from a financial server including a bank server or a card server. When receiving the SMS, the electronic apparatus 100 may determine that the payment of the card used is completed by analyzing the content of the received SMS. When it is determined that the card payment is completed, the electronic device 100 may stop the payment-related MST signaling. According to an embodiment of the present disclosure, the electronic device 100 may receive a specified message from a payment process-related specification server. For example, the electronic device 100 may receive the payment completion related message from a mail server or a token server through a cellular network or a data communication network. When receiving a message from a corresponding server, the electronic apparatus 100 may determine that payment of the card used is completed by analyzing the content of the received message. When it is determined that the card payment is completed, the electronic apparatus 100 may stop the payment transmission.

According to an embodiment of the present disclosure, electronic device 100 may stop payment signaling by determining whether POS device 1400 is proximate to electronic device 100. For example, during detection of the POS device 1400 with the proximity sensor, the electronic device 100 may stop transmission of the payment signal (or MST signal associated with the payment signal) when the electronic device 100 is greater than a specified distance away from the POS device 1400. According to an embodiment of the present disclosure, if an image recognized at the start of payment is not recognized, the electronic apparatus 100 may stop the payment signal transmission. In connection with this, the electronic device 100 may capture an image using a camera, transmit a payment signal when an image related to the POS device 1400 is obtained from the captured image, and stop the payment signal transmission when an image related to the POS device 1400 is not obtained.

When executing the payment application, the electronic apparatus 100 may determine the battery status, and may output a message (e.g., a pop-up notification) related to unavailability of the payment progress if the remaining battery does not satisfy a certain level. For example, when the battery remains less than 15%, the electronic apparatus 100 may operate the payment application after notifying the user of the amount of power through a pop-up notification and a sound or vibration, and if the battery remains less than 10% or the current is less than a certain level, may prevent the execution of the payment application itself and provide a warning message to the user.

According to various embodiments of the present disclosure, the electronic device 100 may continuously progress or terminate a payment application by determining whether a network is connected, whether a data transmission/reception speed through the network is greater than a certain speed, and a Subscriber Identity Module (SIM) enabled state. According to various embodiments of the present disclosure, the electronic device 100 may determine, at a specified point in time (e.g., when executing a payment application, launching an electronic device in which the payment application is installed, attempting to pay or access a token), whether a platform or hardware device related to payment progress is operational or stable (e.g., whether a Trusted Execution Environment (TEE) storing the token is operational or stable, whether a Rich Execution Environment (REE) operating from the token encrypted and delivered from the TEE is operational or stable, whether the REE or secure element is stable, whether the payment application is infected with a virus, and whether the payment application is infected with malware or malicious code). When device stability is recognized, the electronic device 100 may execute a payment application. Further, the electronic apparatus 100 may determine whether to execute the payment application and whether to stop the payment application during execution based on the above-described various situations, such as whether a network is connected, whether a combination of a network data transmission speed greater than a certain value is supported, a SIM enabled state, and a battery state. When the payment application cannot be executed, the electronic device 100 may provide this failure to execute the payment application to the user through a message on the display 150, such as a pop-up notification, a sound, a vibration, a flashing LED, and the like.

Fig. 15 illustrates a battery remaining related payment processing screen, in accordance with various embodiments of the present disclosure.

Referring to fig. 15, the electronic device 100 may determine the specified condition before the payment application is executed or before the payment signal is transmitted. For example, as described above, when a payment-related event occurs, the electronic device 100 may determine that a battery remains and progress payment processing when the battery remains more than a specified reference value (e.g., 10%). In connection with this, the electronic apparatus 100 may determine a set power reference value and perform a next payment operation when the determined set battery reference value is greater than the power reference value, and provide a warning message 1520 to the user and cancel the payment operation if the determined set power reference value is less than the power reference value. The warning message 1520 may be displayed on the payment card image 1510, for example. In connection with this, the electronic device 100 may determine the amount of power in real time or based on certain references (e.g., determine each payment progress operation). In the case of a payment progress operation specific decision, the electronic device 100 may determine the amount of power before executing the payment application, after executing the payment application, just before transmitting the MST signal, or after transmitting the MST signal a specified number of times or during a specified time. If the amount of power of the battery is insufficient, the electronic apparatus 100 may generate a warning message 1520 and may not progress the next operation of payment. According to embodiments of the present disclosure, the electronic device 100 may determine battery power prior to a fingerprint payment attempt.

According to various embodiments of the present disclosure, the electronic device 100 may identify the integrity of the device components (e.g., the TEE that stores tokens as hardware or software device components, the REE, REE or secure element that operates the token encrypted in the TEE, and whether the application is infected with a virus and whether the application is infected with malware or malicious code) at a specified point in time (e.g., when executing a payment application, launching an electronic device in which the payment application is installed, attempting to pay or access the token). The electronic device 100 may determine that the battery remains during the process of identifying the stability of the device component and determine whether to perform stability identification of the corresponding device component. Further, the electronic apparatus 100 may determine that the battery is left during the process of identifying whether the network is connected, whether the network data transmission speed is greater than the reference value, and the SIM enabled state with respect to the progress of the payment, and continue the next operation of the payment when the network data transmission speed is greater than the reference value. When the battery remaining is less than the designated reference value, a message such as a pop-up notification may be output to the display 150 or a message may be provided to the user by sound, vibration, or LED blinking.

Fig. 16A and 16B illustrate card selection related screens according to various embodiments of the present disclosure.

Referring to fig. 16A and 16B, as shown in states 1601 to 1605, the electronic apparatus 100 may provide a screen (e.g., a virtual card object image) for selecting a card. For example, when payment application execution is requested, the electronic device 100 may output a user interface to the display 150 with a plurality of card images superimposed on the payment application execution screen, as shown in state 1601. During this operation, the default card image 1610 shown at the top may be associated with the card set as the default card by the user. According to an embodiment of the present disclosure, the default card image 1610 shown at the top may be an image related to a card providing a benefit (benefit) to a user, for example, when a payment application receives information from an external device and provides a benefit such as discount or mileage at a corresponding store during payment. In connection with this, the electronic apparatus 100 may obtain location information or store information and search for a card for receiving a benefit with respect to a corresponding store. Alternatively, after transmitting location information or store information to a designated server and receiving card information for receiving benefits with respect to a corresponding store from the designated server, the electronic apparatus 100 may search for a card corresponding thereto.

The default card image 1610 shown at the top may be related to the most recently registered card, according to an embodiment of the present disclosure. In connection with this, the electronic apparatus 100 may perform a process of setting a newly registered card to be output at the top by default or inquiring whether the card is output at the top during card registration.

According to an embodiment of the present disclosure, the default card image 1610 shown at the top may be related to the most recently used card. In connection with this, the electronic apparatus 100 may store and manage a recently used card history. When the output of the requested card image is performed according to the payment application, the electronic apparatus 100 may display an image related to the corresponding card at the top by referring to the most recently used card history. According to various embodiments of the present disclosure, the electronic device 100 may arrange the card images at the top and second layer positions according to the order in the most recent usage card history.

The default card image 1610 shown at the top may be associated with the most used registration card, according to embodiments of the present disclosure. In connection with this, the electronic apparatus 100 may store and manage a card use history. When requesting card image output, the electronic apparatus 100 may determine card history and display images related to relatively more used cards on the top.

According to an embodiment of the present disclosure, when a user input (e.g., a touch, swipe, or long press) is input to the default card image 1610 shown at the top, the electronic device 100 may arrange the perimeter card image 1620 by expanding the overlapping card image to a certain size beside the default card image 1610 as shown in state 1603. According to an embodiment of the present disclosure, a first card image 1611 corresponding to a default card image 1610 among a perimeter card image 1620 expanded in a certain size beside the default card image 1610 may be displayed differently from the perimeter card image 1620. For example, the electronic device 100 may display an addition line at an outline of the first card image 1611 corresponding to the default card image 1610. According to embodiments of the present disclosure, the electronic device 100 may display the first card image 1611 in a different color than the other peripheral card images 1620. According to embodiments of the present disclosure, electronic device 100 may display first card image 1611 more clearly than other perimeter card images 1620, or display other perimeter card images 1620 dimmer than first card image 1611. According to an embodiment of the present disclosure, the electronic device 100 may display the first card image 1611 larger than the other peripheral card images 1620, or sequentially display the first card image 1611 ahead of the other peripheral card images 1620. According to an embodiment of the present disclosure, if other peripheral card images 1620 are not displayed on one screen of the display 150, the electronic device 100 may provide a menu for additionally viewing the remaining cards. For example, electronic device 100 may display a perimeter card image on display 150 that is not displayed in response to an event occurring that corresponds to a swipe gesture or a scroll gesture. During this operation, the electronic device 100 may display an undisplayed card image on the display 150 by moving the perimeter card image 1620 up or down depending on the direction of the scroll event.

According to an embodiment of the present disclosure, when one of the plurality of expanded card images is selected, the electronic device 100 may set the selected card image as a new default card image 1630, as shown in state 1605. The selection of the card may include a touch of the user, a long press touch, selection of a corresponding card image and dragging and dropping of the card image toward the existing default card image 1610, and selection of a corresponding card image and swiping of the card image toward the existing default card image 1610.

According to an embodiment of the present disclosure, when the card selection operation is completed, the electronic device 100 may change the expanded card image to an overlapped card image as shown in state 1605. During this operation, the electronic apparatus 100 may display the card image on the display 150 such that the selected card is disposed in the card position of the upper layer.

17A, 17B, and 17C illustrate card selection related screens according to various embodiments of the present disclosure.

Referring to fig. 17A, 17B, and 17C, electronic device 100 may provide a screen for selecting a card to second display 1720 adjacent to first display 1710 as shown in state 1701. For example, with respect to a screen on which a payment application is executed, the electronic apparatus 100 may display a state in which a plurality of card images overlap each other on the first display 1710. At this time, the card image shown at the top may be related to the card set as the default card. The top-level card image 1730 shown at the top may correspond to a designated card, according to embodiments of the present disclosure. For example, the upper card image 1730 may be one of the following: cards that are set as mostly used, recently registered cards, recently used cards, and most used cards at a store at a current location or a point where the electronic device is located.

According to embodiments of the present disclosure, when a user event (e.g., a touch, swipe, or long press) is input to the upper layer card image 1730 displayed at the top of the overlapping card image displayed on the first display 1710, the electronic device may expand and display the overlapping perimeter card image 1740 on the second display 1720 adjacent to the first display 1710, as shown in state 1703. According to an embodiment of the present disclosure, the first card image 1731 related to the upper card image 1730 among the peripheral card images 1740 may be displayed differently from the other peripheral card images 1740. For example, the electronic device 100 may provide additional display effects at the periphery of the first card image 1731 displayed on the second display 1720 with respect to the upper layer card image 1730 in the first display 1710. According to an embodiment of the present disclosure, the electronic device 100 may display the first card image 1731 displayed on the second display 1720 in a different color than the other peripheral card images 1740. According to an embodiment of the present disclosure, the electronic device 100 may display at least one of the transparency and the sharpness of the first card image 1731 displayed on the second display 1720 to be different from the other peripheral card images 1740. According to an embodiment of the present disclosure, the electronic device 100 may display the first card image 1731 displayed on the second display 1720 larger than the other peripheral card images 1740. The first card image 1731 may be disposed at a position further above the other peripheral card images 1740 in the second display 1720.

According to an embodiment of the present disclosure, when all other peripheral card images 1740 are not displayed on the second display 1720, the electronic apparatus 100 may provide the first display 1710 or the second display 1720 with a menu for additionally searching for the peripheral card images that are not displayed. For example, electronic device 100 may output an undisplayed peripheral card image to display 150 in response to a swipe gesture input occurring from second display 1720.

According to an embodiment of the present disclosure, when one of a plurality of card images spread on the screen of the second display 1720 is selected, the electronic apparatus 100 may set the selected card image as a default card image. The selection of the card may include a user's touch with respect to the second display 1720, a long press touch, selecting and dragging and dropping the corresponding card image toward the first display 1710, and selecting and swiping the corresponding card image toward the first display 1710.

According to an embodiment of the present disclosure, when the card selection operation is complete, the electronic device 100 may change the expanded card image to an overlapped card image, as shown in state 1705. At this time, the upper card image may be an upper image 1750 corresponding to the card selected from the second display 1720. According to the above-described embodiments of the present disclosure, the electronic apparatus 100 may obtain a point of time when the payment information transmission is required or not by recognizing states and situations through various conditions, efficiently use terminal power and obtain high security by controlling the payment information transmission, and minimize payment processing errors, when controlling the payment information transmission through the mobile terminal.

According to various embodiments of the present disclosure, an electronic device may include: the payment system includes a housing, a display exposed to one surface of the housing, an input device integrally formed with the display, mounted at the housing, or wirelessly connected with the electronic device, a user authentication device integrally formed with the display or mounted at the housing, a conductive pattern (e.g., MST module) disposed in the housing and configured to transmit a magnetic signal to an external payment device, a first communication circuit electrically connected with the conductive pattern, a second communication circuit configured to provide cellular and/or short-range communication, a sensor configured to detect an orientation of the electronic device, a processor electrically connected with the display, the authentication input device, the first communication circuit, the second communication circuit, and the sensor, and a memory electrically connected with the processor and configured to store token information for payment. The memory may store instructions to allow the processor to receive a first user input through the input device, receive authentication information of the user through the user authentication device, transmit a magnetic signal generated based on the token information to the external payment device through the first communication circuit and the conductive pattern based on the first user input and at least a portion of the authentication information, detect an orientation of the electronic device with the sensor, and output guidance to the user to change the electronic device to be in the selected orientation based on a portion of the detection result.

According to various embodiments of the present disclosure, the output may include at least one of an audio output, a text output, an image output, a video output, and a vibratory or tactile output.

According to various embodiments of the present disclosure, the electronic device may further include an image acquisition device (e.g., a sensor, an image sensor, or an optical sensor) electrically connected to the processor. The instructions may set the processor to obtain an image via the image acquisition device and send a transmission of the magnetic signal based on at least a portion of the obtained image (e.g., corresponding to a specified pattern extracted from the obtained image analysis results).

According to various embodiments of the present disclosure, the electronic device may also include an audio collection device (e.g., a microphone) electrically connected with the processor. The instructions may set the processor to obtain sound from outside through the audio collection device, and control (e.g., stop) magnetic signal transmission based on at least a part of the obtained sound (e.g., during audio data collection corresponding to a specified pattern extracted from an analysis result of the collected audio data).

According to various embodiments of the present disclosure, the instructions may set the processor to control the magnetic signaling (e.g., stop the transmission) based on at least a portion of the received message (e.g., analyze the received SMS and determine the analyzed SMS as payment complete based on the analyzed SMS).

According to various embodiments of the present disclosure, the instructions may set the processor to analyze an image obtained by the camera and stop magnetic signaling if the specified pattern is not found.

According to various embodiments of the disclosure, the instructions may set the processor to send the magnetic signal based on payment related feedback received from a designated server (e.g., an acquirer (acquirer) or a Token Service Provider (TSP)).

According to various embodiments of the disclosure, the instructions may set the processor to receive payment completion related information from an external server using the second communication circuit during execution, and send a magnetic signal transmission based on at least a portion of the received information.

According to various embodiments of the present disclosure, an electronic device may include: the payment system includes a housing, a display exposed to one surface of the housing, an input device integrally formed with the display, mounted at the housing, or wirelessly connected with the electronic device, a user authentication device integrally formed with the display or mounted at the housing, a conductive pattern disposed in the housing and configured to transmit a magnetic signal to an external payment device, a first communication circuit electrically connected with the conductive pattern, a second communication circuit configured to provide cellular and/or short-range communication, a processor electrically connected with the display, the authentication input device, the first communication circuit, the second communication circuit, and the sensor, and a memory electrically connected with the processor and configured to store token information for payment. The memory may store instructions to allow the processor to receive a first user input through the input device, receive authentication information of the user through the user authentication device, receive at least one of the first user input and the authentication information, and determine integrity of the information for payment and/or the token, and determine whether to send a magnetic signal generated based on the token information to the external payment device through the first communication circuit and the conductive pattern based on at least a portion of a result of the determination.

According to various embodiments of the present disclosure, the instructions may allow the processor to determine not to transmit the magnetic signal according to the determination result, and output the determined information related to not transmitting the magnetic signal.

According to various embodiments of the present disclosure, an electronic device may include: the payment system includes a housing, a display exposed to one surface of the housing, an input device integrally formed with the display, mounted at the housing, or wirelessly connected with the electronic device, a user authentication device integrally formed with the display or mounted at the housing, a conductive pattern disposed in the housing and configured to transmit a magnetic signal to an external payment device, a first communication circuit electrically connected with the conductive pattern, a second communication circuit configured to provide cellular and/or short-range communication, a processor electrically connected with the display, the authentication input device, the first communication circuit, and the second communication circuit, and a memory electrically connected with the processor and configured to store token information for payment. The memory may store instructions to allow the processor to receive a first user input through the input device, after receiving the first user input, displaying a plurality of images representing a plurality of payment specific cards for payment using the first communication circuit in a selected arrangement, displaying one of the plurality of images as overlapping the other images, receiving a second user input comprising a touch of a selected time or a selected pressure on at least one of the images, displaying at least a portion of the other images as substantially non-overlapping with the at least one image at a size smaller than the at least one image, receiving input for selecting one of the other images displayed at the smaller size, increasing the size of the selected one of the other images, and transmitting a magnetic signal generated based on the token information to the external payment device through the first communication circuit and the conductive pattern based on the second user input and at least a portion of the authentication information.

According to various embodiments of the present disclosure, the display includes a first screen and a second screen, and the instructions may set the processor to display the plurality of images in the selected arrangement on the first screen and display other images displayed in a smaller size on the second screen.

According to various embodiments of the present disclosure, the second screen may be in a form extending from the first screen and being bent.

According to various embodiments of the present disclosure, one image among the plurality of images may include a most recently used payment card, a most frequently used payment card, and a most recently added payment card.

Fig. 18 is a block diagram illustrating a network environment, according to various embodiments of the present disclosure.

Referring to fig. 18, the

electronic devices

1801, 1802, or 1804 or the server 1806 may be connected to each other through a network 1862 or short-range communication 1864. Electronic device 1801 may include a bus 1810, processor 1820, memory 1830, input/output interface 1850, display 1860, and communications interface 1870. In accordance with embodiments of the present disclosure, the electronic device 1801 may omit at least one of these components or may additionally include a different component.

The bus 1810 may include, for example, circuitry to connect the components 1810-1870 to each other and to deliver communications (e.g., control messages and/or data) between the components 1810-1870.

The processor 1820 may include at least one of a CPU, an AP, and a CP. The processor 1820 may, for example, perform computations or data processing for control and/or communication of at least one further component of the electronic device 1801.

The memory 1830 may include volatile and/or nonvolatile memory. The memory 1830 may store, for example, instructions or data related to at least one additional component of the electronic device 1801. The memory 1830 may store software and/or programs 140 in accordance with embodiments of the present disclosure. The programs 140 may include a kernel 1841, middleware 1843, an Application Programming Interface (API) 1845, and/or an application (or application) 1847. At least a portion of the kernel 1841, middleware 1843, or API 1845 may be referred to as the OS.

The core 1841 may, for example, control or manage system resources (e.g., the bus 1810, the processor 1820, the memory 1830, etc.) used to perform operations or functions implemented in other programs (e.g., the middleware 1843, the API 1845, or the application 1847). In addition, the kernel 1841 may provide an interface for controlling or managing system resources from the middleware 1843, the API 1845, or the application 1847 by accessing individual components of the electronic device 1801.

The middleware 1843 may, for example, serve as an intermediary for exchanging data when communicating with the kernel 1841 at the API 1845 or the application 1847.

Further, the middleware 1843 may process at least one job request received from the application 1847 according to the priority. For example, the middleware 1843 may assign a priority of using system resources (e.g., the bus 1810, the processor 1820, or the memory 1830) of the electronic device 1801 to at least one application 1847. For example, the middleware 1843 may perform scheduling or load balancing on the at least one job request by processing the at least one job request according to a priority assigned to the at least one job request.

The API 1845 as an interface for allowing the application 1847 to control functions provided from the kernel 1841 or the middleware 1843 may include at least one interface or function (e.g., an instruction) for file control, window control, image processing, or character control.

Input/output interface 1850 may, for example, serve as an interface for delivering instructions or data input from a user or another external device to additional component(s) of electronic device 1801. In addition, input/output interface 1850 may output instructions or data received from additional component(s) of electronic device 1801 to a user or another external device.

The display 1860 may include, for example, an LCD, LED display, OLED display, MEMS display, or electronic paper display. The display 1860, for example, may display various content (e.g., text, images, videos, icons, symbols, and so on) to the user. The display 1860 may include a touch screen, and may receive touch, gesture, proximity, or hover input with an electronic pen or a body part of a user, for example.

The communication interface 1870 may, for example, provide for communication between the electronic device 1801 and external devices (e.g., the first external electronic device 1802, the second external electronic device 1804, or the server 1806). For example, communication interface 1870 may communicate with external devices (e.g., second external electronic device 1804 or server 1806) connected to network 1862 via wireless or wired communication.

Wireless communication as a cellular communication protocol may use at least one of LTE, LTE-a, CDMA, WCDMA, UMTS, WiBro, GSM, and so on. Further, the wireless communications may include, for example, short-range communications 1864. The short-range communications 1864 may include, for example, at least one of Wi-Fi, bluetooth, NFC, GPS, and so on.

The MST may generate pulses using the magnetic signals according to the transmission data, and the pulses may generate the magnetic signals. The electronic device 1802 may transmit the magnetic signal to the POS and the POS may detect the magnetic signal using the MST reader and recover the data by converting the detected magnetic signal into an electrical signal.

A Global Navigation Satellite System (GNSS) may include at least one of: the GPS, GLONASS and BeiDou navigation satellite systems (hereinafter referred to as BeiDou) and Galileo are also global satellite based navigation systems in europe. Hereinafter, GPS and GNSS may be used interchangeably. The wired communication may include, for example, at least one of USB, HDMI, RS-232, POTS, and the like. Network 1862 may include a telecommunications network, such as at least one of a computer network (e.g., a LAN or WAN), the internet, and a telephone network.

Each of the first and second external

electronic devices

1802 and 1804 may be the same or different type from the electronic device 1801. The server 1806 may include a group of one or more servers in accordance with embodiments of the present disclosure. All or portions of the operations performed on the electronic device 1801 may be performed on another electronic device or devices (e.g., the

electronic devices

1802 or 1804 or the server 1806), in accordance with various embodiments of the present disclosure. According to embodiments of the present disclosure, when the electronic device 1801 performs a function or service automatically or upon request, the electronic device 1801 may request at least a portion of the functionality associated therewith from another device (e.g., the

electronic device

1802 or 1804 or the server 1806) in place of or in addition to performing the function or service itself. Other electronic devices (e.g., external

electronic devices

1802 or 1804 or server 1806) may perform the requested function or additional functions and may deliver the results of the execution to electronic device 1801. The electronic device 1801 may provide the requested function or service as is or by additionally processing the received results. To this end, for example, cloud computing, distributed computing, or client-server computing techniques may be used.

Fig. 19 is a block diagram of an electronic device according to various embodiments of the present disclosure.

Referring to fig. 19, the electronic device 1901 may comprise all or part of the electronic device 1801 shown in fig. 18, for example. The electronic device 1901 may include at least one processor (e.g., AP 1910), a communication module 1920, a SIM 1929, a memory 1930, a sensor module 1940, an input device 1950, a display 1960, an interface 1970, an audio module 1980, a camera module 1991, a power management module 1995, a battery 1996, an indicator 1997, and a motor 1998.

The processor 1910 may control a plurality of hardware or software components connected thereto and may also perform various data processing and operations by executing an operating system or an application program. Processor 1910 may be implemented, for example, in a system on chip (SoC). Processor 1910 may also include a Graphics Processing Unit (GPU) (not shown) and/or an image signal processor, according to embodiments of the present disclosure. Processor 1910 may include at least a portion of the components shown in fig. 19 (e.g., cellular module 1921). Processor 1910 may load and process commands or data received from at least one of the other components (e.g., non-volatile memory) and may store various data in non-volatile memory.

The communication module 1920 may have the same or similar configuration as the communication interface 1870 of fig. 18. The communication module 1920 may include a cellular module 1921, a Wi-Fi module 1922, a bluetooth module 1923, a GNSS module 1924 (e.g., a GPS module, a GLONASS module, a BeiDou module, or a Galileo module), an NFC module 1925, an MST module 1926, and a Radio Frequency (RF) module 1927.

The cellular module 1921 may provide, for example, a voice call, a video call, a text service, or an internet service through a communication network. According to embodiments of the present disclosure, cellular module 1921 may utilize a SIM (e.g., SIM card 1929) to perform discrimination and authentication operations for electronic device 901 in a communication network. In accordance with an embodiment of the disclosure, the cellular module 1921 may perform at least a portion of the functionality provided by the processor 1910. The cellular module 1921 may also include a CP according to an embodiment of the present disclosure.

Each of the Wi-Fi module 1922, BT module 1923, GNSS module 1924, NFC module 1925, and MST module 1926 may include a processor for processing data transmitted/received by the respective module. At least a portion (e.g., two or more) of the cellular module 1921, the Wi-Fi module 1922, the bluetooth module 1923, the GNSS module 1924, the NFC module 1925, and the MST module 1926 may be included in one IC or IC package, according to embodiments of the present disclosure.

The RF module 1927 may transmit/receive a communication signal (e.g., an RF signal), for example. The RF module 1927 may include, for example, a transceiver, a Power Amplifier Module (PAM), a frequency filter, a Low Noise Amplifier (LNA), or an antenna. According to an embodiment of the present disclosure, at least one of the cellular module 1921, the Wi-Fi module 1922, the bluetooth module 1923, the GNSS module 1924, the NFC module 1925, and the MST module 1926 may transmit/receive an RF signal through a separate RF module.

The SIM 1929 may include, for example, a card containing a SIM and/or an embedded SIM, and may also include unique identification information (e.g., an IC card identifier (ICCID)) or subscriber information (e.g., an International Mobile Subscriber Identity (IMSI)).

Memory 1930 (e.g., memory 1830) may include internal memory 1932 or external memory 1934. Internal memory 1932 can include at least one of: volatile memory (e.g., Dynamic Random Access Memory (DRAM)), Static RAM (SRAM), Synchronous DRAM (SDRAM)), and non-volatile memory (e.g., one-time programmable read only memory (OTPROM), PROM, Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM)), mask ROM, flash memory (e.g., NAND flash memory or NOR flash memory), hard disk drive, and Solid State Drive (SSD)).

The external memory 1934 may also include a flash drive, such as a Compact Flash (CF), Secure Digital (SD), micro SD, mini SD, extreme digital (xD), multimedia card (MMC), or memory stick. The external memory 1934 may be functionally and/or physically connected to the electronic device 1901 through various interfaces.

The security module 1936, as a module including a storage space having a relatively higher security level than the memory 1930, may be a circuit for ensuring secure data storage and a protected execution environment. The security module 1936 may be implemented as a separate circuit and may include additional processors. The security module 1936 may be, for example, in a removable smart chip or SD card, or may comprise an eSE embedded in a fixed chip of the electronic device 1901. Further, the security module 1936 may run on a different OS than the electronic device 1901. For example, it may run based on the Java Card Open Platform (JCOP) OS.

The sensor module 1940 measures a physical quantity or detects an operation state of the electronic device 1901, thereby converting the measured or detected information into an electrical signal. The sensor module 1940 may include at least one of: attitude sensor 1940A, gyroscopic sensor 1940B, barometric sensor 1940C, magnetic sensor 1940D, acceleration sensor 1940E, grip sensor 1940F, proximity sensor 1940G, color sensor 1940H (e.g., red, green, blue (RGB) sensor), biometric sensor 1940I, temperature/humidity sensor 1940J, illumination sensor 1940K, and Ultraviolet (UV) sensor 1940M. Additionally or alternatively, sensor module 1940 may include an electronic nose (E-nose) sensor, an Electromyography (EMG) sensor, an electroencephalogram (EEG) sensor, an Electrocardiogram (ECG) sensor, an Infrared (IR) sensor, an iris sensor, and/or a fingerprint sensor. The sensor module 1940 may also include control circuitry for controlling at least one sensor therein. According to embodiments of the present disclosure, the electronic device 1901 may also include a processor configured to control the sensor module 1940 as part of the processor 1910 or separately from the processor 1910, and may thereby control the sensor module 1940 when the processor 910 is in a sleep state.

Input devices 1950 may include a touch panel 1952, a (digital) pen sensor 1954, keys 1956, or an ultrasonic input device 1958. The touch panel 1952 may use at least one of capacitive, resistive, infrared, or ultrasonic methods, for example. In addition, the touch panel 1952 may further include a control circuit. Touch panel 1952 may also include a tactile layer to provide a tactile response to the user.

The (digital) pen sensor 1954 may include a sheet for identification as part of the touch panel or a separate sheet for identification, for example. Keys 1956 may include, for example, physical buttons, optical keys, or a keypad. The ultrasonic input device 1958 may detect ultrasonic waves generated from an input tool through a microphone (e.g., microphone 1988) to determine data corresponding to the detected ultrasonic waves.

A display 1960 (e.g., display 1860) may include a panel 1962, a holographic device 1964, or a projector 1966. The panel 1962 may have the same or similar configuration as the display 1860 of fig. 18. The panel 1962 may be implemented, for example, as flexible, transparent, or wearable. The panel 1962 and the touch panel 1952 can be configured with one module. The hologram device 1964 may display a three-dimensional image in the air using interference of light. The projector 1966 may display an image by projecting light on a screen. The screen may be placed, for example, inside or outside the electronic device 1901. The display 1960 may also include control circuitry for a control panel 1962, a holographic device 1964, or a projector 1966 according to embodiments of the disclosure.

The interface 1970 may include, for example, HDMI 1972, USB 1974, optical interface 1976, or D-subminiature (D-sub) 1978. Interface 1970 may be included, for example, in communication interface 170 shown in fig. 18. Additionally or alternatively, interface 1970 may include a mobile high-definition link (MHL) interface, an SD card/MMC interface, or an infrared data association (IrDA) standard interface.

The audio module 1980 may convert sound into electrical signals and convert electrical signals into sound. At least some of the components of audio module 1980 may be included in input/output interface 145 shown in fig. 18, for example. The audio module 1980 may process sound information input/output through the speaker 1982, the receiver 1984, the headphone 1986, or the microphone 1988.

The camera module 1991 as a device for capturing still images and video may include at least one image sensor (e.g., a front sensor or a rear sensor), a lens, an Image Signal Processor (ISP), or a flash (e.g., an LED or a xenon lamp).

The power management module 1995 may manage power of the electronic device 1901. According to embodiments of the present disclosure, the power management module 1995 may include, for example, a Power Management IC (PMIC), a charger IC, or a battery gauge or a fuel gauge. The PMIC may have wired and/or wireless charging methods. As a wireless charging method, for example, there is a magnetic resonance method, a magnetic induction method, or an electromagnetic method. Additional circuitry for wireless charging may be added, for example, circuitry such as coils, resonant circuits, rectifier circuits, and the like. The battery gauge may measure the remaining amount of the battery 1996 or its voltage, current, or temperature during charging. The battery 1996 can include, for example, a rechargeable battery and/or a solar cell.

The indicator 1997 can display a particular status of the electronic device 1901 or a portion thereof (e.g., the processor 1910), such as a boot status, a message status, or a charge status. The motor 1998 may convert the electrical signal to mechanical vibrations and may generate vibrations or haptic effects. Although not shown in the figure, the electronic device 1901 may include a processing device (e.g., GPU) for mobile TV support. The processing device for mobile TV support may be based on a Digital Multimedia Broadcasting (DMB), Digital Video Broadcasting (DVB), mediaFLO^TMAnd so on, to process the media data.

Each of the above-described components of the electronic device according to various embodiments of the present disclosure may be configured with at least one component, and names of the respective components may vary according to kinds of the electronic device. According to various embodiments of the present disclosure, an electronic device according to various embodiments of the present disclosure may include at least one of the above components, may not include some of the above components, or may further include other components. Furthermore, some of the components in the electronic device according to various embodiments of the present disclosure are configured as one entity, so that the functions of the previous respective components are equally performed.

Fig. 20 is a block diagram of program modules according to various embodiments of the present disclosure.

Referring to fig. 20, program modules 2010 (e.g., programs 1840) may include an OS for controlling resources associated with an electronic device (e.g., electronic device 1801) and/or various applications (e.g., application programs 1847) running on the OS in accordance with embodiments of the present disclosure. The OS may include, for example, android, iOS, windows, symbian, tizen or bada.

The programs may include a kernel 2020, middleware 2030, an API 2060, and/or an application program (or application) 2070. At least a portion of program modules 2010 may be preloaded on an electronic device or downloaded from a server (e.g.,

electronic devices

1802 and 1804 and server 1802).

The kernel 2020 (e.g., kernel 1841) may include, for example, a system resource manager 2021 or a device driver 2023. System resource manager 2021 may perform control, allocation, or retrieval of system resources. According to embodiments of the present disclosure, the system resource manager 2021 may include a process management unit, a memory management unit, or a file system management unit. The device driver 2023 is, for example, a display driver, a camera driver, a bluetooth driver, a shared memory driver, a USB driver, a keypad driver, a Wi-Fi driver, an audio driver, or an inter-process communication (IPC) driver.

The middleware 2030 may provide, for example, functions that are typically required by the application 2070, or may provide various functions to the application 2070 through the API 2060 in order to allow the application 2070 to efficiently use limited system resources within the electronic device. According to embodiments of the present disclosure, the intermediary 2030 (e.g., the intermediary 1843) may comprise at least one of: a runtime library 2035, an application manager 2041, a window manager 2042, a multimedia manager 2043, a resource manager 2044, a power manager 2045, a database manager 2046, a package manager 2047, a connectivity manager 2048, a notification manager 2049, a location manager 2050, a graphics manager 2051, a security manager 2052, and a payment manager 2054.

Runtime libraries 2035 may include, for example, library modules that the compiler uses to add new functionality through the programming language while application 2070 is running. The runtime library 2035 may perform functions related to input/output management, memory management, or arithmetic functions.

The application manager 2041 may manage a lifecycle of at least one application among the applications 2070, for example. The window manager 2042 may manage Graphical User Interface (GUI) resources used in the screen. The multimedia manager 2043 may identify formats for playing various media files and may encode or decode the media files using codecs corresponding to the respective formats. The resource manager 2044 may manage resources, such as source code, memory, storage space, and so forth, of at least any one of the applications 2070.

The power manager 2045 may operate, for example, with a basic input/output system (BIOS) to manage battery or power, and may provide power information necessary for operation of the electronic device. The database manager 2046 may create, search, or modify a database used in at least one application among the applications 2070. The package manager 2047 may manage installation or update of applications distributed in a package file format.

The connectivity manager 2048 may manage wireless connections, such as Wi-Fi or Bluetooth. The notification manager 2049 may display or provide events such as arrival messages, appointments, and proximity reminders to the user in a manner that is not disruptive to the user. The location manager 2050 may manage location information about the electronic device. The graphics manager 2051 may manage graphical effects to be provided to a user or a user interface related thereto. The security manager 2052 may provide various security functions necessary for system security or user authentication. According to an embodiment of the present disclosure, when the electronic device (e.g., the electronic device 1801) includes a phone function, the middleware 2030 may further include a phone manager for managing a voice or video call function of the electronic device. Payment manager 2054 may relay information for payment from application 2070 to application 2070 or kernel 2020. Further, information related to payment received from the external device may be stored in the electronic device or information stored therein may be delivered to the external device.

The middleware 2030 may include a middleware module for forming a combination of various functions of the above-described components. Middleware 2030 may provide modules dedicated to each type of OS to provide differentiated functions. Further, the middleware 2030 can dynamically delete a part of an existing component or add a new component.

An API 2060 (e.g., API 1845) may be provided as another configuration according to the OS, for example, as a set of API programming functions. For example, in the case of android or iOS, one API set may be provided for each platform, and in the case of tizen, at least two API sets may be provided for each platform.

Applications 2070 (e.g., applications 1847) may include, for example, at least one application for providing functionality such as: a home page 2071, a dialer 2072, an SMS/MMS 2073, an instant message 2074, a browser 2075, a camera 2076, an alarm 2077, contacts 2078, a voice dial 2079, an email 2080, a calendar 2081, a media player 2082, an album 2083, a clock 2084, a payment 2085, healthcare (e.g., measuring workout or blood glucose), or environmental information provision (e.g., providing barometric pressure, humidity, or temperature information).

According to an embodiment of the present disclosure, the application 2070 may comprise an application (hereinafter referred to as "information exchange application") for supporting information exchange between an electronic device (e.g., the electronic device 1801) and an external electronic device (e.g., the electronic device 1802 or 1804). The information exchange application may include, for example, a notification relay application for relaying specific information to an external device or a device management application for managing an external electronic device.

For example, the notification relay application may have functionality for relaying notification information occurring from another application of the electronic device (e.g., an SMS/MMS application, an email application, a healthcare application, or an environmental information application) to an external electronic device (e.g., electronic devices 1802 and 1804). Further, the notification relay application may receive notification information from an external electronic device, and may provide the received notification information to the user.

The device management application may, for example, manage (e.g., install, delete, or update) at least one function (turning on/off the external electronic device itself (or some components) or brightness (or resolution) adjustment of a display) of an external electronic device (e.g., electronic devices 1802 and 1804) in communication with the electronic device, an application operating in the external electronic device, or a service (e.g., a call service or a message service) provided from the external device.

According to embodiments of the present disclosure, the applications 2070 may include specified applications (e.g., healthcare applications for ambulatory medical devices) according to attributes of external electronic devices (e.g., the electronic devices 1802 and 1804). According to embodiments of the disclosure, the application 2070 may comprise an application received from an external electronic device (e.g., the server 1086 or the electronic device 1802 or 1804). According to an embodiment of the present disclosure, the application 2070 may include a preloaded application or a third party application downloadable from a server. Names of components in the program module 2010 according to the illustrated embodiment may vary depending on the type of the OS.

According to various embodiments of the disclosure, at least a portion of program module 2010 may be implemented in software, firmware, hardware, or a combination thereof. At least a portion of programming module 2010, for instance, can be implemented (e.g., executed) by a processor (e.g., processor 1820). At least a portion of programming modules 2010 may include, for example, a module, program, routine, set of instructions, or process to perform at least one function.

The term "module" used in various embodiments of the present disclosure may mean, for example, a unit including a combination of at least one of hardware, software, and firmware. The term "module" and the terms "unit," "logic block," "component," or "circuit" may be used interchangeably. A "module" may be the smallest unit or part of an integrally configured component. A "module" may be the smallest unit that performs at least one function or a portion thereof. The "module" may be implemented mechanically or electronically. For example, a "module" according to various embodiments of the present disclosure may include at least one of an application-specific IC (ASIC) chip, a field-programmable gate array (FPGA), or a programmable logic device that performs certain operations, all of which are known or will be developed in the future.

According to various embodiments of the disclosure, at least a portion of an apparatus (e.g., modules or functions thereof) or a method (e.g., operations) according to the disclosure may be implemented with instructions stored in a computer-readable storage medium, e.g., as a programming module. When at least one processor (e.g., processor 1820) executes instructions, it may perform functions corresponding to the instructions. A non-transitory computer readable storage medium may include, for example, the memory 1830.

Certain aspects of the present disclosure may also be embodied as computer readable code on a non-transitory computer readable recording medium. The non-transitory computer readable recording medium is any data storage device that can store data which can be thereafter read by a computer system. Examples of the non-transitory computer-readable recording medium include Read-Only Memory (ROM), Random-Access Memory (RAM), Compact Disc-ROM (CD-ROM), magnetic tapes, floppy disks, and optical data storage devices. The non-transitory computer-readable recording medium may also be distributed over network-coupled computer systems so that the computer-readable code is stored and executed in a distributed fashion. In addition, functional programs, codes, and code segments for accomplishing the present disclosure can be easily construed by programmers skilled in the art to which the present disclosure pertains.

Here, it should be noted that the various embodiments of the present disclosure as described above generally involve the processing of input data and the generation of output data to some extent. This input data processing and output data generation may be implemented in hardware or in a combination of software and hardware. For example, certain electronic components may be employed in a mobile device or similar or related circuitry for implementing the functions associated with the various embodiments of the present disclosure as described above. Alternatively, one or more processors operating in accordance with stored instructions may implement the functions associated with the various embodiments of the disclosure as described above. If so, it is within the scope of the present disclosure that such instructions may be stored on one or more non-transitory processor-readable media. Examples of the processor-readable medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device. The processor-readable medium can also be distributed over network coupled computer systems so that the instructions are stored and executed in a distributed fashion. Furthermore, functional computer programs, instructions, and instruction segments for implementing the present disclosure may be readily understood by programmers skilled in the art to which the present disclosure pertains.

A module or programming module according to various embodiments of the present disclosure may include at least one of the above components, may not include some of the above components, or may also include other components. Operations performed by a module, programmed module, or other component according to various embodiments of the disclosure may be performed in a sequential, parallel, iterative, or heuristic manner. Further, some operations may be performed in a different order or may be omitted. Alternatively, other operations may be added. In addition, the embodiments disclosed in the present specification are proposed for the description and understanding of the technical contents, and do not limit the scope of the present disclosure. Therefore, the scope of the present disclosure should be construed to include all modifications or various other embodiments based on the technical idea of the present disclosure.

Fig. 21 is a block diagram illustrating a REE and a TEE operating in an electronic device, according to various embodiments of the present disclosure.

Referring to fig. 21, an electronic device may operate an execution environment with multiple security levels for security enhancement, according to various embodiments of the present disclosure. The multiple execution environments may include, for example, REE 2110 and TEE 2120. REE 2110 may be, for example, a first execution environment having a first security level. TEE2120 may be, for example, a second execution environment having a second security level different from (e.g., higher than) the first security level. According to an embodiment of the present disclosure, the electronic device 1802 may include an additional another execution environment (e.g., a third execution environment) having a third security level, and the present disclosure is not limited thereto.

TEE2120 may store data requiring a relatively high security level in a secure environment and perform related operations. The TEE2120 may operate on an application processor of an electronic device and may operate based on a reliable hardware structure determined during a manufacturing process. TEE2120 may divide an application processor or memory into a general area and a secure area and operate in the secure area. TEE2120 may set software or hardware requiring security to operate only in a secure region. The electronic device may operate the TEE2120 through physical changes in hardware or logical changes in software.

The TEE2120 may be separated from the REE 2110 by hardware limitations and in terms of software may be separated and operated in the same hardware as the REE 2110. At least one application (e.g., payment, contact, email, or browser) operating in the REE 2110 may use an API (e.g., TEE functionality API or TEE client API) that is allowed to access the TEE 2120. The at least one application may utilize the API to deliver messages from a communication agent (e.g., a REE communication agent) of the TEE2120 to a communication agent (e.g., a TEE communication agent) of the TEE 2120. This message may be implemented to be delivered only to TEE 2120. The communication agent of TEE2120 may receive the message and deliver the message to a Trusted Application (TA) associated with the message (e.g., a Digital Rights Management (DRM), a secure payment module, or a secure biometric module). The TA may perform the operations associated with the message and deliver the results of the operations to the communication agent of the REE 2110 through the communication agent of the TEE 2120. The communication agent of REE 2110 may deliver the result to at least one application operating in REE 2110.

Fig. 22A, 22B, and 22C are block diagrams illustrating a hardware structure of a TEE according to various embodiments of the present disclosure.

Referring to fig. 22A, a case where one processor and one memory are divided into REE and TEE and used in terms of hardware is illustrated (for example,

is/are as follows

(TZ)). According to an embodiment of the disclosure, a hardware architecture of a TEE may include an On-SoC2210 and an external memory 2220. On-SoC2210 may include RAM 2201, microprocessor core 2202, ROM2203, peripherals 2204, cryptographic accelerator 2205, or one-time password (OTP) field 2206. TZ may distinguish between REEs and use them by temporally dividing processors to operate two or more execution environments. In addition, the TZ may divide one memory into an area accessible from the REE and an area accessible from the TEE and use them.

Referring to FIG. 22, a case is illustrated where the processor for the TEE is implemented in on-chip form like the processor for operating the REE, but is implemented with an additional set of processing cores. In addition to the microprocessor core 2202, the On-SoC2210 may additionally include a security-On-chip subsystem 2207, the security-On-chip subsystem 2207 including at least one processor, according to embodiments of the present disclosure. In this case, On-SoC2210 may be set to operate a REE and On-chip security subsystem 2207 may be set to operate a TEE. In the case of fig. 22B, as in fig. 22A, one memory may be divided into an area accessible from the REE and an area accessible from the TEE and used.

Referring to fig. 22C, a case where the processor for the TEE is implemented as an additional chip in terms of hardware, so that it is separated from a chip in which the processor for operating the REE is implemented is illustrated.

Referring to fig. 22C, the On-SoC2210 may be set to operate a REE and at least one external security co-processor 2230 equipped outside the On-SoC2210 may be set to operate a TEE.

Fig. 23 illustrates a payment system, according to various embodiments of the present disclosure.

Referring to fig. 23, a payment system 2300 may include an electronic device 2310 and/or a server, according to various embodiments of the present disclosure. Further, for example, the server may include a payment server 2320, a token server (e.g., token service provider) 2330, or a financial server (e.g., issuer) 2340. The electronic device 2310 can include, for example, a payment application (e.g., wallet application) 2312 and/or a payment manager 2314. Payment server 2320 may include, for example, payment service server 2322 and/or token requestor server 2324.

According to various embodiments of the disclosure, the payment application 2312 may include, for example, a Samsung Pay^TMApplication is carried out. The payment application 2312 may, for example, provide a payment-related user interface (e.g., a User Interface (UI) or user experience (UX)). The payment-related UI may include a wallet UI/UX. For example, the payment application 2312 may provide a UI related to card registration, payment, or transactions. For example, the payment application 2312 may provide an interface related to a character reader (e.g., optical character reader/recognition (OCR)) or an external input (e.g., user input), for example. Further, the payment application 2312 may be identified and verified (ID), for example&V) provide a user authentication related interface.

The payment application 2312 may perform payment transactions according to various embodiments of the present disclosure. For example, the payment application 2312 may provide payment functionality to the user through simple payment, quick payment, or designated application execution. The user may perform a payment function using the payment application 2312 and receive information related to the payment function.

According to various embodiments of the present disclosure, the payment manager 2314 may include card company related information. For example, the payment manager 2314 may include a Software Development Kit (SDK) for card companies.

The payment server 2320 may include a management server for electronic payment or mobile payment, according to various embodiments of the present disclosure. The payment server 2320 may receive payment-related information from the electronic device 2310, for example, and transmit the payment-related information to the outside or process the payment-related information in the payment server 2320.

The payment server 2320 may utilize the payment service server 2322 and/or the token requestor server 2324 to send/receive information between the electronic device 2310 and the token server 2330, according to various embodiments of the present disclosure. The payment service server 2322 may include, for example, a payment server 2320 (e.g., a samsung payment server). The payment service server 2322 may manage the card information with respect to a service account or a user account, for example. Further, the payment service server 2322 may include an API server associated with the payment application 2312. Further, the payment service server 2322 may, for example, provide a payment management module (e.g., account integration or samsung account integration).

Token requestor server 2324 may provide an interface for processing payment-related information, according to various embodiments of the present disclosure. For example, token requestor server 2324 may perform issuance, deletion, or activation of payment-related information (e.g., tokens). Or, it may be functionally connected to the payment manager 2314 and control information necessary for payment.

According to various embodiments of the disclosure, a payment application 2312 in the electronic device 2310 may be functionally connected to a payment service server 2322 in the payment server 2320. For example, the payment application 2312 may send/receive payment-related information to/from the payment server 2320. According to embodiments of the present disclosure, a payment manager 2314 in the electronic device 2310 may be functionally connected to a token requestor server 2324 in the payment server 2320. For example, payment manager 2314 may send/receive payment-related information to/from token requestor server 2324.

The token server 2330 may issue payment-related information (e.g., tokens) or manage payment-related information, according to various embodiments of the present disclosure. For example, the token server 2330 can control the life cycle of the token. The lifecycle may include generating, modifying, or deleting cycles. Further, the token server 2330 can include, for example, a token management server and can perform token provisioning (provisioning), identification and verification (ID & V), replenishment, or lifecycle management. In addition, the token server 2330 can perform integration of information related to financial servers.

The payment server 2320 and/or the token server 2330 may be located in the same or similar area or in separate areas, according to various embodiments of the present disclosure. For example, the payment manager 2320 may be included in a first server and the token server 2330 may be included in a second server. Further, for example, the payment manager 2320 and/or the token server 2330 may be separately implemented in one server (e.g., a first server or a second server).

The financial server 2340 may perform card issuance in accordance with various embodiments of the present disclosure. For example, financial server 2340 may include an issuing bank. In addition, the financial server 2340 may generate the information necessary for payment provided to the user. The user may store information necessary for payment generated from the financial server 2340 in the electronic device 2310 using the payment application 2312. In addition, the financial server 2340 may be functionally connected to the token server 2330 and transmit/receive information necessary for payment to/from the token server 2330.

Fig. 24 is a block diagram illustrating a payment system for performing payments, according to various embodiments of the present disclosure.

Referring to fig. 24, a payment system may include an electronic device 2410 (e.g., electronic device 1801), a payment server 2420 (e.g., server 1806), a TSP 2430 (e.g., server 1806 or another server (not shown)), and a POS 2440 (e.g., electronic device 1802). According to embodiments of the present disclosure, the payment system may include at least one additional

electronic device

2450 or 2460. The at least one additional electronic device may include a wearable device 2450 (e.g., a smart watch) or an accessory 2460 (e.g., from LoopPay)^TMA pocket (fob) form of device) that may be functionally (e.g., communicatively) connected to the electronic device 2410. From LoopPay according to embodiments of the present disclosure^TMMay include an external payment module connected to the electronic device 2410 through a microphone.

The electronic device 2410 may operate payment functions in accordance with embodiments of the present disclosure. The electronic device 2410 may register a card (e.g., a credit card, such as MasterCard or Visa) in the electronic device 2410 or the payment server 2420. In addition to cards registered with the electronic device 2410, the payment server 2420 may manage information on cards registered with another electronic device (e.g., the electronic device 2450) of a user corresponding to the electronic device 2410 or a plurality of registered cards including other cards registered with the electronic device of another user.

According to an embodiment of the disclosure, payment server 2420 may obtain token information corresponding to the registration card information from token service provider 2430 and deliver the token information to electronic device 2410. The payment server 2420 may comprise a payment service server or token requestor server, for example. The payment service server may manage card information of the user. The payment service server may provide payment-related services based on the account. The token requestor server may obtain token information by requesting token information necessary for a payment operation from the token service provider 2430.

Token service provider 2430 may issue tokens for use during the payment process. According to an embodiment of the present disclosure, the token may be a value for replacing a Primary Account Number (PAN) as card information. According to an embodiment of the present disclosure, the token may be generated using a Bank Identification Number (BIN). Further, the generated token may be encrypted by token service provider 2430, or the generated token may be encrypted by payment server 2420 after being sent to payment server 2420 in an unencrypted state. After the encrypted token information is delivered to the electronic device 2410 by the payment server 2420, the encrypted token information may be decoded in the electronic device 2410. According to embodiments of the disclosure, tokens may be generated and encoded from token service provider 2430 and delivered to electronic device 2410 without going through payment server 2420. According to an embodiment of the present disclosure, the payment server 2420 may include a token generation function, and in this case, the additional token service provider 2430 may not be used in the payment system.

The electronic device 2410 can, for example, perform payment utilizing at least one of the at least one additional electronic device 2450 or 760 that is functionally connected based on short-range communication (e.g., bluetooth or Wi-Fi). Other electronic device 2450 may be a wearable device (e.g., a smart watch), and in this case, electronic device 2410 may deliver the token delivered from token service provider 2430 to the wearable device, in accordance with embodiments of the present disclosure. Other electronic devices 250 may be accessories (e.g., pocket form devices from LoopPay^TM) according to embodiments of the disclosure, and in this case, electronic device 2410 may be functionally connected to the accessory (e.g., pocket form devices from LoopPay^TM) through input/output interface 1850 (e.g., headset 1986).

Fig. 25 is a block diagram illustrating a hardware structure of an electronic device for performing a payment function according to various embodiments of the present disclosure.

Referring to fig. 25, an electronic device 2500 may include, for example, a camera module 2501, an acceleration sensor 2503, a gyro sensor 2505, a biometric sensor 2507, an MST module 2510, an NFC module 2520, an MST control module 2530, an NFC control module 2540, a processor 2550, and a memory 2560, according to embodiments of the present disclosure. The camera module 2501 may obtain card information by capturing a card necessary for payment. The camera module 2501 may recognize card information (e.g., card company, card number, card expiration date, or card holder) indicated on the card through the OCR function. Alternatively, the user may input the necessary card information to the electronic device 2500 using an input device (e.g., a touch panel, pen sensor, key, ultrasonic input device, or microphone input device).

According to embodiments of the present disclosure, the acceleration sensor 2503 or the gyro sensor 2505 may obtain the position status of the electronic device 2500 during payment. The obtained location information of electronic device 2500 (e.g., electronic device 1801) may be delivered to processor 2550 and processor 2550 may adjust the strength of the magnetic field sent from MST module 2510 to the POS based on the obtained location state of electronic device 2500. When there are multiple coil antennas, the processor 2550 may select a coil antenna to use. According to an embodiment of the disclosure, the MST control module 2350 may include a data reception module 2531 and an output conversion module 2533. The data reception module 2531 may receive a pulse signal of a logic low/high form including payment information transmitted by the processor 2550 or a security module (e.g., eSE).

The output conversion module 2533 may include circuitry to convert to the necessary form in order to deliver the data identified by the data reception module 2531 to the MST module 2510. The circuit may include an H-bridge for controlling the direction of the voltage provided across the MST module 2510. The H-bridge may have a circuit structure connected in an H-form using four switch structures.

According to an embodiment of the present disclosure, the electronic device 2500 may receive payment information (e.g., the track 1/2/3 or token information) included in a magnetic stripe of a magnetic card from a card company/bank server through a communication module (not shown) based on card information input through the camera module 2501 or an input device (e.g., a touch panel, a pen sensor, etc.). The electronic device 2500 may store the received payment information in the necessary form in the memory 2560 or in an additional security module (e.g., eSE).

26A, 26B, and 26C are hardware (H/W) block diagrams illustrating the interior of an electronic device using wireless short-range communication with at least one of a plurality of MST modules, according to various embodiments of the present disclosure.

Referring to fig. 26A, the electronic device 2600 may include an MST data transmitting unit 2610, an MST control module 2630a, a first output unit 2650, a power control unit 2620, a wireless charging control module 2640, and a second output unit 2660. The MST data transmitting unit 2610 may include a first data receiving module 2631, a first output converting module 2632, a second data receiving module 2633, and a second output converting module 2634. The MST data transmitting unit 2610 may deliver a signal to one of the first and second

data receiving modules

2631 and 2633 and the corresponding signal may be converted by the first and second

output converting modules

2632 and 2634 and transmitted through the first or second output unit 2650 or 2660. The second output unit 2660 may be connected to the wireless charging control module 2650 and used for wireless charging. The power control module 2620 may include a power management module 1995 in the terminal. According to an embodiment of the present disclosure, the MST module corresponding to the first output 2650 may include, for example, a coil antenna having an inductance value of about 10 uH. The wireless charging control module 2640 may include an alternating current/direct current (AC/DC) converter or rectifier.

Referring to fig. 26B, the electronic device 2600 may include an MST data transmitting unit 2610, an MST/wireless charging control module 2630B, a power control unit 2620, a first MST module 2671, and a second MST module 2672. The MST/wireless charging control module 2630b may include a MST driver 2635 and a wireless charging driver 2641. The MST driver 2635 may include a data reception module 2637 and an output conversion module 2638. The wireless charging control driver 2641 may include an AC/DC converter or rectifier. The electronic device 2600 may use at least one MST module among the plurality of

MST output units

2671 and 2672 as a wireless charging-dedicated coil antenna. When the second MST module 2672 is connected to the wireless charging driver 2641 and operates as a wireless charging module (e.g., a wireless charging coil antenna), a switching unit may further be disposed between the second MST module 2672 and the MST driver 2635 to form a selective connection.

Referring to fig. 26C, the electronic device 2600 may include an MST data transmitting unit 2610, an MST control module 2630C, a first MST module 2671, a second MST module 2672, an NFC module 2680, an NFC control module 2681, and a switching circuit 2682. Like the MST control module 2630a shown in fig. 26A, the MST control module 2630c may include a first data receiving module 2631, a second data receiving module 2633, and

output conversion modules

2632 and 2634. The second MST module 2672 may be selectively used for MST data transmission or NFC data transmission. When the second MST module 2672 is used as an NFC coil antenna, the electronic device 2600 may operate the switching circuit 2682 in order to adjust a number of turns or an inductance value of the coil antenna.

Fig. 27 is a block diagram illustrating program modules executed in an execution environment of an electronic device for performing payment functions, according to various embodiments of the present disclosure.

Referring to fig. 27, an execution environment of an electronic device 2700 may include, for example, a REE2710 and a TEE 2720.

For payment, according to embodiments of the present disclosure, for example, REE2710 may include a payment application 2730 (e.g., payment application 2085), a payment manager 2740 (e.g., payment manager 2054), and a kernel 2750 (e.g., kernel 2020). According to an embodiment of the present disclosure, payment applications 2730 may include a payment management module 2731, a server link module 2733, an authentication module 2735, and a peripheral device management module 2737.

According to an embodiment of the present disclosure, the payment management module 2731 may perform operations for card registration, card authentication, card deletion, and payment. The payment management module 2731 may register the user's card. Electronic device 2700 (e.g., electronic device 1801) can receive a card registration request from a user. The electronic device 2700 may obtain the card image using the camera module. The payment management module 2731 may obtain the card image through the OCR module. The payment management module 2731 may receive card information-related information (e.g., a password, a home address, an email address, a phone number, or an account ID) from the user or obtain the card information-related information from the payment server 2420.

According to an embodiment of the present disclosure, payment management module 2731 may display the registered cards to the user through a display (e.g., display 1860). The user may modify at least some of the information in the registration card (e.g., card name, home address, phone number, number of payment attempts, or whether payment notification information is received). The payment management module 2731 may display transaction history per card. The payment management module 2731 may display card information registered in a wearable device (e.g., a smart watch) functionally connected with the electronic device.

According to an embodiment of the present disclosure, the payment management module 2731 may perform a payment operation using a registration card. The user may select one of a plurality of cards registered for payment. A user may take electronic device 2700 to POS 1400. Payment management module 2731 may display product information (e.g., price) delivered from POS1400 through display 1860. The payment management module 2731 may perform user authentication (e.g., fingerprint authentication) through the authentication module 2735 for payment. When the authentication is completed, the payment management module 2731 may display notification information of the completion of the payment through the display 1860.

According to embodiments of the present disclosure, electronic device 2700 may send payment information to POS1400 using at least one of the MST module and the NFC module. To increase the identification rate, both the MST module and the NFC module may be utilized to send payment information to the POS 1400. Alternatively, when the payment information is transmitted using the MST module and the payment fails, the electronic device 2700 may transmit the payment information using the NFC module. Methods of identifying payment failures may include instances where a notification is received from POS1400 or a third party (e.g., a financial institution) or instances where a specified time has elapsed. Various embodiments are not limited to this order and the reverse order thereof is possible.

According to an embodiment of the present disclosure, the electronic apparatus 2700 may receive a request of the user to delete at least one card among the pre-registered cards. The payment management module 2731 may delete information corresponding to the corresponding card from the memory 1830. The payment management module 2731 may request the payment server 2420 to delete the information corresponding to the at least one card.

In accordance with an embodiment of the present disclosure, the payment management module 2731 may determine whether the cardholder is the same as the user of the registration card. The payment management module 2731 may include, for example, an ID & V module. The payment management module 2731 may perform user authentication through SMS, email, ARS, or phone call. Further, authentication may be performed by an application issued by a card company or a bank. The card registered through the payment management module 2731 may be used after authentication.

In accordance with embodiments of the present disclosure, payment management module 2731 may include an OCR module. The OCR module may obtain an image of a human-written or machine-printed character and convert the image of the character into a machine-readable character. The electronic apparatus 2700 may obtain an image of the card owned by the user through the camera module. The OCR module may convert images, characters or numbers written on the card in the card image into machine-readable characters. The OCR module may obtain card information (e.g., card number, user name, or expiration date) of the user through the converted characters. The electronic apparatus 2700 may perform the card registration process by obtaining card information of the user through the OCR module.

According to an embodiment of the present disclosure, the payment management module 2731 may display a barcode generated for payment through the display 1860. For example, payment management module 2731 may receive a command from POS 2440 to generate a barcode through which payment is performed with a barcode reader. The payment management module 2731 may generate a barcode based on the command.

According to an embodiment of the present disclosure, server link module 2733 may receive payment-related messages, device-related messages, or service-related messages from payment server 2420 or token service provider 2430. Server link module 2733 may deliver the message to payment management module 2731.

According to an embodiment of the present disclosure, the server link module 2733 may include, for example, a push management module and an account management module. For example, when the message received from the payment server 2420 is in the form of a token-related push notification, the push management module processes the received message, and when the received message is account-related information (e.g., samsung account), the account management module may process the received message.

According to an embodiment of the present disclosure, the push management module may calculate and process push notification or push message (e.g., push notification or push message) information received from the payment server 2420. The push message may be delivered to the server link module 2733 in the payment application 2730 through the payment relay module 2741 in the

payment manager

2740 or 2054, or may be delivered directly to the payment application 2730. At least a portion of the delivered push message may be delivered to the payment management module 2731 to update card-related information and synchronize with the payment server 2420.

According to an embodiment of the present disclosure, the payment server 2420 may include an account server for managing account-related information or a token requester server for providing payment-related information. The account server and token requestor server may be implemented with additional devices (e.g., server 1806) and included in one device.

According to embodiments of the present disclosure, the message information received by the push management module may include tokens and payment related information, such as authority (authority) settings (e.g., token provisioning), suspension (e.g., token suspension), discard (e.g., token discarding), state switching (e.g., token state change), additional issuance (e.g., token replenishment), and payment decision (e.g., transaction notification), as shown in table 1.

The messages sent/received from/by the account management module may include at least a portion of electronic device-related information, such as lost electronic device determination functionality (e.g., lost device, find my mobile device), remote shutdown (e.g., remote lock/unlock), membership management (e.g., loyalty/membership card), and web linking functionality (e.g., web portal online).

TABLE 1

According to an embodiment of the present disclosure, when the token provisioning ID & V information obtained by the payment management module is successfully delivered to the external server through the payment server 2420 and the delivered token-related information is valid, a message that the "push token { ID } state has changed" may be received by the server link module 2733 and delivered to the payment management module 2731.

According to an embodiment of the present disclosure, card information temporary suspension (e.g., token suspension) information obtained from the payment management module 2731 of the electronic device 2700 may deliver a use suspension instruction of the payment server 2420 to the payment application 2730 so that the payment application 2730 may change a card setting state for mobile payment from an active state to an inactive state.

According to an embodiment of the present disclosure, when the electronic device 2700 is lost, the payment server 2420 may delete or temporarily suspend all token information related to the electronic device 2700 stored in the payment server 2420. Payment server 2420 may send push messages to synchronize deleted or paused information with payment application 2730. For example, the payment server 2420 may deliver information necessary for synchronization to the payment application 2730 through the payment relay module 2731 or the server link module 2733 (e.g., push management module and account management module).

Referring to table 2, the contents of push APIs supported by the electronic device and the payment relay module 2731 may be divided and separately implemented according to the payment relay module 2731.

TABLE 2

API	Description of the invention	Type (B)	Corroboration of
				device.push	Involving a push platform	Json	Is required to
device.push.spp.id	Samsung pushes Id.	Character string	Is required to
				device.push.gcm.id	Google push Id.	Character string	Optionally

According to embodiments of the present disclosure, the account management module may deliver information such as a unique identifier of the user (e.g., samsung account id or device id), card, or membership exchanged with the payment server 2420 to the payment application 2730, and the payment application 2730 may manage the received information. The user identifier may include a user subscription (subscribed) account, an electronic device related portal account, or a unique identifier (e.g., a MAC address, an International Mobile Equipment Identity (IMEI), a serial number, a Universally Unique Identifier (UUID), or an ID) of the electronic device in order to manage cards of several companies (e.g., Visa or MasterCard). Additionally, the unique identifier may be a value generated from the payment server 2420 through an account and received from the payment server 2420.

The account management module may manage registration, addition, deletion, duplicate registration, use suspension, or use resumption of the card using the user's account or the electronic device identifier. Further, even when card information is imported/exported between the electronic device and the wearable device, registration, addition, deletion, duplicate registration determination, use suspension, or use resumption of the card may be managed based on the generated account or the electronic device identifier.

At this time, with the account-based management method, since a plurality of electronic devices or a plurality of users sharing one account are managed, the electronic devices may be managed using an electronic device-specific unique account (e.g., samsung account) or may be managed using one account as a whole.

According to an embodiment of the present disclosure, information about a first card (e.g., Visa) and a second card (e.g., MasterCard) generated by an optical character recognition module (e.g., OCR module) of the payment management module 2731 may be registered based on an account (e.g., registration02@ samsung. At this time, the registered information may be synchronized with the payment server 2420 based on the generated account.

According to an embodiment of the present disclosure, membership information generated through a barcode interface may register a first card (e.g., a samsung card) and a second card (e.g., a CJ membership score card) based on an account (e.g., registration02@ samsung. The registered information may be synchronized with the payment server 2420 based on the generated account.

Further, the user may determine the active/inactive status of the account-based card after logging into the payment application and deliver the active/inactive status of the account-based card to the

payment server

2320 or 2420 using the payment management module 2731, and on the other hand, may manage and switch the account-based card status on a server management web page (e.g., server portal).

Further, the account management module may manage card information (e.g., Visa card ID & V) and membership information (e.g., CJ membership points and registration001@ CJ. com) associated with a service account (e.g., registration01@ registration. com) in linkage with the server. The membership information may be automatically accumulated or deducted during card payment in conjunction with payment processing information (e.g., payment amount) and membership accumulation information (e.g., points, mileage, etc.).

Once the payment application including the account management module is installed, the account management method enables use of the payment application with only one user account login or sign-in process at any device in continuous linkage with the setup state of all or a portion of the existing registration card. Furthermore, the account management method may reduce an additional authentication process because membership information having a relatively low authentication security level is registered and linked based on an account.

According to an embodiment of the present disclosure, the authentication module 2735 may display a UI for performing authentication of a card or a user for payment through the display 1860. The authentication module may comprise, for example, a biometric information module.

According to embodiments of the present disclosure, a biometric information module may obtain biometric information of a user. The biometric information of the user may include, for example, fingerprint, iris, facial image, voice, heart rate, or blood pressure information. The electronic device may obtain biometric information of the user through the sensor module. For example, the electronic device may obtain fingerprint information of the user through a fingerprint sensor. Alternatively, the electronic device may obtain iris information of the user through the camera module. The biometric information module may display a UI for obtaining biometric information of the user through the display 1860.

According to embodiments of the present disclosure, when a user attempts to process a payment with card information registered in an electronic device, the biometric information module may perform authentication to obtain secure data (e.g., a token) from a secure memory (e.g., an eSE or a memory accessible from a secure environment) functionally connected with the electronic device. The electronic device may obtain biometric information (e.g., a fingerprint or iris) of the user through a biometric information module for user authentication. The obtained biometric information may be delivered to the biometric information management module 2743 of the payment manager 2740. According to embodiments of the present disclosure, the secure memory may be a memory that stores data in an encrypted key.

According to an embodiment of the present disclosure, when a user processes an electronic payment on an internet webpage, the biometric information module 2743 may process the payment using card information and biometric information registered in the electronic device. The user can perform authentication to obtain secure data (e.g., a token) from a memory or security module (e.g., an eSE or memory accessible from a secure environment) functionally connected with the electronic device. When user authentication successfully progresses, the electronic device may link the progressing authentication information with an external server to provide fast automatic authentication (e.g., fast identity online (FIDO) without an additional electronic payment process on an internet webpage.

According to an embodiment of the present disclosure, an electronic device may specify a user's fingerprint and a card for payment. For example, when performing authentication in a payment application using a fingerprint, the user may designate a right thumb for Visa and a right index finger for MasterCard, and the electronic device 2700 may classify the information type according to the user authentication and support payment using the associated card based thereon.

According to an embodiment of the present disclosure, peripheral management module 2737 may manage external devices functionally connected with the electronic device. The peripheral management module 2737 may include an MST peripheral module and a wearable device module.

According to embodiments of the present disclosure, the MST peripheral module may determine that the MST accessory is present (e.g., from LoopPay)^TMA pocket form device) and an electronic device, and provides a UI suitable for a user based thereon. When the MST accessory is connected, the UI may output information related to the progress of the card registration, deletion, or payment process. When connected to the MST accessory, the MST peripheral module may store various card information necessary for payment in additional memory of the electronic device or the MST accessory. This allows the electronic device or MST accessory to process payment independently when the electronic device is not connected to the MST accessory.

The wearable device module may determine whether a wired/wireless connection exists between the wearable device (e.g., watch, headset, glasses, or ring) and the electronic device and provide a UI appropriate for the user based thereon. The wired/wireless connection may include various interface connections, such as bluetooth, BLE, Wi-Fi, ZigBee, or Z-wave, and may be implemented by applying a specific accessory protocol (e.g., Samsung Accessory Protocol (SAP)). When the wearable device is connected, the UI may output information related to card registration, deletion, or payment execution processes. During the card registration, deletion, or payment execution process, the wearable device module may output whether a short range based session is established with the wearable device, transmit/receive a user input value on the electronic device or the wearable device, and display the transmission/reception result. The user input may include various card information necessary for payment and additional authentication information in addition thereto (e.g., PIN, user unique pattern related data, fingerprint identification related data, and touch input value of the bezel unit or display 1860 of the wearable device).

According to embodiments of the present disclosure, an electronic device may share one payment information with a wearable device or accessory. For example, information about a Visa card may be stored in both the wearable device and the electronic device. According to an embodiment of the present disclosure, an electronic device may store different card information generated from one card information in each of a wearable device and an accessory. For example, one of the different tokens issued from one Visa card information may be stored in the electronic device and the other may be stored in the wearable device. According to an embodiment of the present disclosure, when one of different tokens issued from one card information is stored in an electronic device and the other is stored in an accessory or wearable device, a payment module of the other device may be deactivated as the payment module of the one device is activated. For example, when one of the different tokens issued from one Visa card information is stored in the electronic device and the other is stored in the accessory or wearable device, the payment of the electronic device may be deactivated as the payment is processed by the wearable device. Additionally, the payment of the wearable device may be deactivated when the payment is processed by the electronic device.

According to embodiments of the present disclosure, payment manager 2740 may include, for example, payment relay module 2741, biometric information management module 2743, and secure environment relay module 2746. According to various embodiments of the present disclosure, payment relay module 2741 may relay the card or card information (e.g., token) corresponding to the card to a payment application, kernel, or payment server 2420. The payment relay module 2741 may process offline payments through communication modules (e.g., NFC module and MST module). The payment method using NFC may be performed through POS and the payment method using MST may be performed by user input. Further, the payment relay module 2741 may process online payments through a communication module (e.g., cellular module, RF module, Wi-Fi module, etc.).

In accordance with embodiments of the present disclosure, payment relay module 2741 may manage the status of the card or information corresponding to the card (e.g., token) (e.g., manage the card/token lifecycle). The payment relay module 2741 may provide at least one API related to payment to the payment application 2730.

According to embodiments of the present disclosure, payment relay module 2741 may further include: a system services interface for providing an interface provided by a system service related to at least one payment, a payment service for accessing a payment module, a Trustzone-based integrity measurement architecture (TIMA) for kernel integrity authentication, a fingerprint identification result view (e.g., supporting both secure and non-secure modes), and a security UI for a Primary Identification Number (PIN) or PAN. The payment relay module 2741 may include an encryption library to deliver messages or instructions to the TEE 2720. The payment relay module 2741 may exchange messages or instructions with the TEE2720 through the encryption vault.

According to an embodiment of the present disclosure, the payment relay module 2741 may process a card management function for providing functions of card addition, deletion, and update as a general card management function. The payment relay module 2741 may include the first payment SDK or the second payment SDK. A first payment SDK (e.g., a samsung SDK) may be embedded in the electronic device. The second payment SDK may be provided from a card company or a bank, and may be installed on the electronic device. The payment relay module 2741 may select a corresponding payment SDK according to the card information using the first payment SDK or the second payment SDK. Further, the payment relay module 2741 may set a default card or another card in addition to the default card.

In accordance with embodiments of the present disclosure, as a general token and key management function, payment relay module 2741 may send messages to

payment server

2320 or 2420 for initial rights setting (e.g., token provisioning), additional issuance (e.g., token replenishment), suspension (e.g., token suspension), resumption (e.g., token resumption), and relinquishing (e.g., token discarding).

The payment module 2721 may obtain a token and a token password from the electronic device or another electronic device external according to an embodiment of the present disclosure. Keys (e.g., Limited Used Keys (LUKs) or single use keys) used to generate the token and token cryptogram may be stored in the REE2710 or the TEE 2720. Additionally, when the token and key are stored in the REE2710, the payment module of the TEE2720 may encrypt or store them using a key of the TEE2720, e.g., a Device Root Key (DRK). When the electronic device processes the payment, the payment relay module 2741 may obtain the encrypted token in a decrypted state through the payment module. When the key or token used to generate the token cryptogram is stored in the TEE2720, the electronic device may store the key or token in encrypted form using the key of the TEE 2720.

In accordance with an embodiment of the present disclosure, payment relay module 2741 may receive a push message from TSP 2430 and deliver the push message to payment application 2730.

According to an embodiment of the present disclosure, when the first payment SDK (provided from the card company or the bank) is provided from the token management function, the payment relay module 2741 may further include a function for relaying the function to the second payment SDK upon receiving the token management function request. For example, a payment relay module that obtains a token or key using the SDK of the Visa card may deliver the key or token to a payment module in the TEE 2720. In accordance with embodiments of the present disclosure, the payment relay module 2741 may further include a host card emulation function on the payment frame for allowing the use of a virtual card in an electronic device without an additional hardware device (e.g., a security module or SE) during payment. The HCE function may deliver the token and the token cryptogram through a communication module (e.g., NFC) using a POS-related message standard (e.g., an Application Protocol Data Unit (APDU)).

According to embodiments of the present disclosure, the payment relay module 2741 may include functionality for processing messages received from the POS. The POS-related message processing functions may include functions for managing payment data in response to the POS. The POS-related message interpretation function may further include a function for relaying the POS-related message to the first payment SDK when the first payment SDK is provided from the POS-related message processing function. In accordance with embodiments of the present disclosure, the payment relay module 2741 may include at least one database for memory card data, token data, or transaction data.

According to an embodiment of the present disclosure, the payment relay module 2741 may select one of a payment method using NFC and a payment method using MST. For example, payment relay module 2741 may select one of the following: a method of performing payment first with NFC and then with MST, a method of performing payment first with MST and then with NFC, and a method of performing payment with both NFC and MST. According to an embodiment of the present disclosure, after payment is performed through one communication module and then through another communication module, if no response to a result from the one communication module that performs payment first or a designated time elapses, the payment relay module 2741 may perform payment through the another communication module.

According to an embodiment of the present disclosure, when both token and PAN information are owned for one card, the payment relay module 2741 may perform payment using at least one of the owned information. The payment relay module 2741 may determine whether payment is to be completed at the POS using the PAN or token. For example, the electronic device may receive payment availability information through BLE and payment relay module 2741 may determine the information. When payment is possible using the token based on the confirmed information, the payment relay module 2741 may perform payment using the token, and when payment is possible using the PAN, the payment relay module 2741 may perform payment using the PAN.

In accordance with embodiments of the present disclosure, payment relay module 2741 may also include an SDK provided from the payment network. The SDK may include token management, POS related message processing, or token/card databases.

According to embodiments of the present disclosure, the secure environment relay module 2746 may further include functionality for performing a relay to allow the payment information to access the biometric information driver module 2751 or the secure environment driver module 2753 in order to use functionality provided from the payment module 2721 or the biometric information module 2725. Payment relay module 2741 may include a cryptographic library to deliver messages or instructions to secure environment relay module 2746. Payment relay module 2741 may exchange messages or instructions with secure environment relay module 2746 through a cryptographic library.

According to various embodiments of the present disclosure, the payment manager 2740 may further include a secure environment relay module 2746 connected to allow use of the functionality of the secure identifier processing module in the TEE2720 in payment applications.

According to embodiments of the present disclosure, the payment relay module 2741 may include functionality for relaying the authentication request to the secure identifier processing module 2723 in the TEE2720 through PIN entry by the payment application 2730.

A general application may obtain from a fingerprint identification request whether the fingerprint identification was successful or failed. A secure payment application (e.g., a payment trusted app) may obtain a secure biometric result (e.g., a secure fingerprint result). The secure biometric result may be in encrypted form by combining the nonce and whether it succeeded or failed. The nonce may be encrypted by a hardware key (e.g., a DRK).

According to an embodiment of the present disclosure, the payment relay module 2741 may deliver a message for payment processing to the payment module 2721 through the secure environment driver module 2753 in order to perform payment. The payment module 2721 may notify the payment relay module 2741 that an authentication operation is necessary through the secure environment driver module 2753. The payment relay module 2714 may issue instructions to the biometric sensor 1940I to obtain biometric information through the biometric information management module 2743 and the biometric information driver module 2741 for authentication operations. Additionally, the payment relay module 2714 may deliver the authentication decision message to the biometric information module 2725 in the TEE2720 through the biometric information management module 2743 and the secure environment driver module 2753.

The biometric sensor 1940I may be obtained from a biometric information module 2725 in the TEE 2720. The biometric information module 2725 may determine whether the same user is present by comparing biometric information of the user and information obtained from biometric sensors. Based on the confirmed information, the biometric information module 2725 may deliver whether the biometric information of the user and the information obtained from the biometric sensor are authenticated to the biometric information management module 2743 through the secure environment driver module 2753, and the biometric information management module 2743 may deliver the biometric information of the user and the information obtained from the biometric sensor to the payment relay module 2741. The payment relay module 2741 and the biometric information management module 2743 may be configured as one module or may be configured as separate modules.

According to an embodiment of the present disclosure, the payment relay module 2741 may perform authentication through an external device. For example, the electronic device 2700 may request authentication for biometric information (e.g., a fingerprint or iris) from a payment server 2420 (e.g., a samsung account server or a token requestor server). The payment server 2420 may perform authentication on the biometric information of the user and deliver the corresponding result to the electronic device 2700. When authentication is complete, payment relay module 2741 may deliver data to the token service provider that includes information about the completion of authentication and perform a token provisioning process. In addition, the electronic device may perform payment when authentication is completed according to the authentication result, and may not perform payment if authentication is not completed or not performed.

According to embodiments of the present disclosure, the core 2750 may include, for example, a biometric information driver module 2751 and a secure environment driver module 2753. The biometric information driver module 2751 may deliver a message delivered from the biometric information management module 2743 of the payment manager 2740 to the biometric sensor 1940I. The biometric information obtained from the biometric sensor may not be delivered to a module in the REE2710, but may be delivered to a biometric information module 2725 in the TEE 2720.

According to embodiments of the present disclosure, secure environment driver module 2753 may serve as an interface for delivering information from modules in REE2710 to modules in TEE 2720. For example, in one embodiment as a TEE

Is/are as follows

When the operations of the REE and TEE are performed by time division, the application processor may implement an additional data path in terms of hardware for delivering messages from the REE to the TEE. In this case, the driver module for accessing this hardware may be the secure environment driver module 2753. The secure environment driver module 2753 may deliver messages to modules in the REE regarding the operation of the modules in the TEE.

The TEE 2720 may include a payment module 2721, a secure identifier processing module 2723, a biometric information module 2725, and a MST driver module 272 according to an embodiment of the present disclosure. The electronic device 2401 may store data requiring relatively high security in a secure environment through the TEE 2720 and perform related operations. With respect to the TEE 2720, a reliable TEE operating on an application processor of an electronic device and determined during a manufacturing process of the electronic device may refer to a secure area in the electronic device. The electronic device may operate on data requiring relatively high security through the TEE based on the secure hardware architecture. The TEE 2720 may divide an application processor and a memory area into a general area and a secure area and operate them. Additionally, the TEE 2720 may allow software or hardware requiring security to operate only in a secure region. When the electronic device is required to perform operations related to sensitive information, the electronic device may access the TEE 2720 only through APIs and drivers that are accessible to the TEE 2720. The TEE 2720 may hand over restricted data about relevant information to the REE. The TEE 2720 may encrypt internally stored data with a hardware key (e.g., DRK). If there is no additional decryption process, the data in the TEE 2720 may not be interpreted in the REE.

With respect to the TEE 2720, an application (e.g., a security application (e.g., a trusted application) or payment module) in the TEE may deliver a message to another electronic device (e.g., the token service provider 243) outside of the electronic device.

According to embodiments of the present disclosure, the TEE 2720 may include a trusted OS and a secure application (e.g., a trusted application). Additionally, the TEE 2720 may include a security-related encryption module and a driver for collecting data from hardware requiring security. The secure application (e.g., trusted application) may include a payment module. In addition, the payment information may be delivered to the outside through the communication module. For example, the payment information may be sent to the MST controller through the MST driver or to the NFC controller through the NFC driver for transmission to the POS.

According to an embodiment of the present disclosure, a determination is made as to whether integrity with REE2710 is provided. The electronic device may store whether the integrity of the image in the REE is provided in the TEE 2720. In the case of TEE-enabled REE boot, when the boot loader is executed, the order of boot may be to first boot the TEE and then boot the REE. If the TEE is initiated, integrity information for the REE in the TEE may be determined and provided to the user after initiation of the REE. According to an embodiment of the present disclosure, if an image of an REE is damaged by hacking or routing, it is determined that there is a problem in integrity. If there is a problem in integrity, the TEE may not be accessed. For example, when the payment relay module 2741 is to deliver a message or instruction to the TEE through the secure environment driver module 2753, the kernel in the TEE may ignore the message or instruction, or deny message reception.

The payment module 2721 may be an application installed from a bank or card company (e.g., Visa or MasterCard), according to an embodiment of the present disclosure. The payment module 2721 may be at least one. When a user of the electronic device accesses the payment server 2420 (e.g., a mobile application platform, a payment gateway, a token requestor, a token service provider, a trusted service manager, or a bank server) or the token service provider 243 via the internet using the payment management module 2731 and approves installation of the payment module 2721, the token service provider 2430 may perform installation-related operations. For example, the payment management module 2731 may perform a card registration operation for installing the payment module 2721 on the server by obtaining the card number and expiration date information of the plastic card through OCR. After receiving the installation file by connecting with token service providers 2430 in the network through the payment relay module 2741 having connection information of each token service provider 2430 according to the card/bank company, the payment relay module 2741 may install the payment module 2721 by delivering the information to the TEE. Such a process may be referred to as a provisioning process or a card registration process. The payment module 2721 in the TEE may be several modules. Each payment module may not exchange data in the TEE and may be configured in a separate form.

The payment module 2721 may be an application for data communication with the payment server 2420 according to an embodiment of the present disclosure. The payment module may include information about credit cards, debit cards, and membership cards. The payment module may exchange communications with another external electronic device through encryption. The encryption process may vary depending on the card manufacturer that delivers the payment module. The server may control the state of the payment module. For example, the server may activate, temporarily suspend, resume, or delete the payment module.

The payment module 2721 may store information related to card information according to an embodiment of the present disclosure. For example, it may be at least one of: a token corresponding to card information (e.g., a PAN), a token reference ID, a portion of a PAN, a PAN product ID, a token requestor ID, a token guarantee level, token guarantee data, an expiration period for the token, an encryption key, and a value provided from token service provider 2430 (e.g., a one-time password (OPT)). The token may be controlled by the state of token service provider 2430. For example, the token may be activated, temporarily suspended, resumed, or deleted. The token may be static information that substantially corresponds to the card information (e.g., PAN).

According to an embodiment of the present disclosure, the payment module 2721 may determine a card for payment when performing payment. For example, a payment module corresponding to a card selected by the user may be determined according to the user's selection in the at least one payment management module 2731. The payment management module may deliver the determined card to the payment relay module 2741. The payment relay module may deliver the determined card information to the payment module 2721 through the secure environment driver module 2753. The payment module may manage a list of cards used for actual payment in the cardholder information. Based on the determined card information, the list of cards used for actual payment may be changed. The change may be a method of increasing priority in the card list with respect to the determined card information or deleting card information other than the determined card information.

According to an embodiment of the present disclosure, when performing payment, the payment module may create information for payment based on the card information-related information. The information for payment as shown in table 3 may be a token, a token reference ID, a portion of a PAN, a PAN product ID, a token requestor ID, a token guarantee level, token guarantee data, an expiration period of the token, a token password, a POS entry mode, and a token requestor indicator.

TABLE 3

The payment module 2721 may receive a key (e.g., a LUK or a single-use key) for generating a token password through the token service provider 2430 or the payment server 2420 (e.g., a payment service server or a token requestor server), according to an embodiment of the present disclosure. The key may be received via a data network or SMS.

Keys may be exchanged between the electronic device and the token service provider 2430 over a secure channel. The secure channel may be a logical channel that encrypts data exchanged with an additional key (e.g., a method using a public key and a private key) other than the key. Additionally, the secure channel may include a module that generates a key for generating a token cryptogram in the payment module. The electronic device may receive the module for generating the key through the token service provider 2430 or the payment server 2420. Alternatively, the key may be included during the manufacturing process of the electronic device.

According to embodiments of the present disclosure, the payment module may generate the token cryptogram using a key (e.g., a limited-use key or a single-use key) used to generate the token cryptogram. The payment module may use different keys according to certain rules, such as each transaction, a certain number of transactions, transactions over a certain time period, etc. Token service provider 2430 may have a key that is paired with the key. The token service provider 2430 may decode the encrypted token cryptogram with the key pair described above.

The payment module 2721 may generate a token password using a key for generating the token password according to an embodiment of the present disclosure. Further description is provided below with reference to fig. 29.

According to an embodiment of the present disclosure, when performing payment, electronic device 2700 may deliver a message to process payment in a payment application to payment relay module 2741. The payment relay module 2741 may determine whether to process payment using MST or NFC. When payment is processed by the MST, information necessary for the payment process (e.g., a token password, a portion of the PAN information, a token expiration period, etc.) may be obtained from the payment module in the TEE and delivered to the MST driver module 2727 in the TEE. The MST driver module 2727 may deliver the information to the MST controller. The MST controller may send this information for use in the payment process.

According to embodiments of the present disclosure, when payment is processed by NFC, electronic device 2700 may send information necessary for the payment process to an NFC driver module in the TEE. The NFC driver module may deliver information necessary for the payment process to the NFC controller. The NFC controller may perform payment based on the information.

According to an embodiment of the present disclosure, in the case where payment is processed by NFC, the electronic device 2700 may perform payment when a specified message is delivered from the POS. For example, when a specified message is delivered from the POS and detected by the NFC module, the NFC controller may deliver it to the NFC driver module. The NFC driver module may notify the payment relay module 2741 in the REE of the message delivered from the POS. The payment relay module 2741 may generate a token cryptogram for performing the payment. The token cryptogram may be generated from the payment module 2721 in the TEE using a key (e.g., a limited-use key or a single-use key) used to generate the token cryptogram. The generated token cryptogram may be delivered to the REE. The payment relay module 2741 may deliver payment related information including a token and a token password through a network module (e.g., NFC related host card emulation). The network module may deliver the payment related information to the POS through the NFC module.

According to an embodiment of the present disclosure, the payment module 1821 may deliver information including a token, a token expiration date, a token requestor ID, and a token password to an external electronic device. For example, the payment module 1821 may deliver payment information to the POS 2450 through the MST communication module. In addition, the payment module 1821 may deliver payment information to the POS through the NFC communication module.

The payment module 1821 may send/receive specified information to/from the POS during a payment operation according to embodiments of the present disclosure. In the case of NFC, the payment module 1821 may perform payment operations by first receiving information from the POS. In the case of MST, payment related information including a token and token password may be sent to the POS based on explicit input by the user or an algorithm in the electronic device.

According to an embodiment of the present disclosure, the biometric information module 2725 may store biometric information of a user using the electronic device, and may authenticate the user by comparing the biometric information with information received from a biometric sensor. The biometric information module 2725 may include a fingerprint information module and an iris information module. The biometric information module may collect information from the biometric sensor 1940I. When the payment application displays content on the display 1860 to authenticate the user's biometric information, the user may deliver the biometric information through the biometric sensor. The authentication module of the payment application may deliver a message for collecting biometric information to the biometric information driver module 2751 through the biometric information management module. The biometric information driver module 2751 may deliver the message to the biometric sensor. The biometric sensor may collect biometric information and deliver the biometric information to the TEE. The biometric information module in the TEE may pass through the secure environment driver module and the biometric information management module in the REE whether it is authenticated for delivery to the authentication module of the payment application after comparing the delivered biometric information to the stored biometric information of the user. The payment application may display on the display whether it is authenticated. The user's biometric information may be stored in the TEE, or in the REE in an encrypted state, or in the security module 236 (e.g., the eSE).

According to an embodiment of the present disclosure, the secure identifier processing module 2723 may obtain an input value necessary from the electronic device or related to payment-related authentication through user input. For example, the input value may be a personal identification number during the payment process. In addition, the input value may be card-related information. For example, the input value may be a primary account number, an expiration date, or a Card Verification Value (CVV). In addition, the input value may be a chip PIN or an ATM PIN. The secure identifier processing module 2723 may be provided in the form of an application. The graphics library necessary to render the application of the secure identifier processing module 2723 on the screen may be stored in the TEE 2720. The graphics library stored in TEE 2720 may be different from that in REE 2710. The secure identifier processing module 2723 may perform user authentication using an input value such as a PIN, and deliver the user authentication result to the payment management module 2731 through the payment relay module 2741. According to an embodiment of the present disclosure, the secure identifier processing module 2723 may receive a one-time random number (e.g., a random number (nonce)) delivered from the secure environment relay module 2746 through the secure environment driver module 2753. The secure identifier processing module 2723 may encrypt an input value obtained from the user input and a one-time random number using an encryption key (e.g., a device root key) in the TEE and deliver the encrypted information to the secure environment relay module 2746. The secure environment relay module 2746 may deliver the encrypted input value and the nonce to the payment module 2721 through the secure environment driver module 2753. The payment module 2721 may decode the input value and the nonce using a hardware key in the TEE. The payment module 2721 may determine that the input value delivered through the REE is good using the fact that the generated value and the received one-time random number have the same value. Based on the input value being intact, the payment module 2721 may perform user authentication through the input value. The payment module 2721 may perform payment through user authentication. According to an embodiment of the present disclosure, factory reset is an operation for restoring a software image of an electronic device to a state in which the electronic device is shipped from an existing factory. This operation may be performed by an application by an explicit operation of the user. In addition, the monitoring module may perform a factory reset by determining hacking behavior under specified conditions (e.g., determining that the system is hacked by a hacker). In the case where this operation is performed, since the data stored in the electronic device is reset, the payment-related information of the user may also be reset. The payment-related information may be stored in the payment server 2420. When the user accesses the payment server 2420 based on the account, the electronic apparatus 2700 may perform card registration and an operation for installing a payment module based on the payment-related information. When reset, the payment related module stored in the electronic device may notify it to token service provider 2430 through payment server 2420 for deactivation. When the network of the electronic device is deactivated, the notification operation may not be performed. In this case, after performing the factory reset, the electronic device may access the payment server 2420 based on the account. Electronic device 2700 may determine the pre-registered card list through payment server 2420 and deactivate the card module or token of the electronic device pre-registered in token service provider 2430. In addition, based on the card list of the payment server 2420, the electronic device may receive a payment module or token by performing card registration again.

28A, 28B, 28C, 28D, 28E, 28F, 28G, 28H, 28I, and 28J illustrate a payment user interface of an electronic device, according to various embodiments of the present disclosure.

Referring to fig. 28A, 28B, 28C, 28D, 28E, 28F, 28G, 28H, 28I, and 28J, electronic device 2800 may execute a payment application by receiving user input, according to an embodiment of the present disclosure. For example, as shown in fig. 28A and 28B, the electronic device 2800 may execute a payment application (e.g., samsung payment) when user input occurs that swipes from a lower bezel area of the electronic device 2800 toward a display direction. In response to the user input, electronic device 2800 may display at least one card 2810 among the cards pre-registered in electronic device 2800 via display 2860 as shown in fig. 28C.

According to an embodiment of the present disclosure, the electronic device 2800 may select a card to be used for payment among a plurality of pre-registered cards by receiving a user input. For example, the electronic device 2800 may enable selection of a card to be used for payment among a plurality of cards by a user input scrolling left/right as shown in fig. 28D or 28E. Alternatively, the electronic apparatus 2800 may display a partial image 2820 related to another card in an area adjacent to the card 2810 as shown in fig. 28F, and support the operation of the card corresponding to the selected image when the partial image 2820 is selected.

The electronic device 2800 can request authentication from the user for payment of the selected card as shown in fig. 28G. The authentication method may use, for example, biometric information of the user. For example, the electronic device may perform a payment operation by scanning a user's fingerprint via the fingerprint detection module. While payment is in progress or on standby, electronic device 2800 may display card 2810 on display 2860 as shown in fig. 28H. When a payment cancellation event occurs (e.g., a swipe event or a back key event for removing card 2810), electronic device 2800 may remove card 2810 from display 2860 as shown in fig. 28I. With card 2810 removed, electronic apparatus 2800 may output a screen with card 2810 removed as shown in fig. 28J.

Fig. 29 illustrates a token password generation method, in accordance with various embodiments of the present disclosure.

Referring to fig. 29, a payment module (e.g., payment module 2721) may generate a token password using a key for generating the token password according to an embodiment of the present disclosure. The payment module may use different keys according to certain rules, such as each transaction, a certain number of transactions, transactions over a certain time period, etc. Token service provider 2430 may have a key that is paired with the key. The token service provider 2430 may decode the encrypted token cryptogram with the key pair described above.

When the payment module generates the token password using the key, data encrypted by the key and the encryption engine may vary according to an encryption method (e.g., Advanced Encryption Standard (AES), Temporal Key Integrity Protocol (TKIP), etc.).

Fig. 30 illustrates a payment system, according to various embodiments of the present disclosure.

Referring to fig. 30, a payment system 3000, for example, may include an electronic device 3010 and/or an external device 3020 (e.g., a server), according to various embodiments of the present disclosure. The electronic device 3010 may include, for example, TEE3030 and/or REE 3040. The external device 3020 may comprise, for example, a server, and the server may comprise, for example, the payment server 3050 and/or the token server 3060. The payment server 3050 may include, for example, a payment service server 3052 or a token requestor server 3054.

According to various embodiments of the present disclosure, the TEE3030 may include a security system associated with the electronic device 3010. For example, the electronic device 3010 may protect information included in or stored by TEE3030 for control related to external requests, modifications, or inputs by utilizing TEE 3030.

TEE3030 may include, for example, security enhancement program modules according to embodiments of the present disclosure. For example, the general world can be distinguished from the secure world using TEE 3030. The world may be generally referred to as REE 3040. Further, the TEE3030 may execute reliable applications or manage encrypted information, for example. For example, the encrypted information may include token or key information.

According to embodiments of the present disclosure, TEE3030 may protect encrypted information from the outside world. The token or key information may be used to encrypt the card information. For example, in providing the card information to the device for payment, at least a portion of the card information may be changed and provided with respect to the token or key information, instead of directly providing the card information to the device for payment. The token or the key information may be used when changing the card information. The key may be obtained, for example, from a service provider that provides the payment service. Further, the key may be managed by the electronic device 3010 or the server. According to embodiments of the present disclosure, the TEE3030 may include a secure application 3032 (e.g., a trusted application). The TEE3030 may, for example, provide an environment in which the secure application 3032 may execute.

According to various embodiments of the present disclosure, the security application 3032 may include, for example, information related to a card company included in the TEE 3030. The information related to the card company may include, for example, an application related to the card company and the application may be provided in a package form. The packet form may be provided as an SDK.

According to various embodiments of the present disclosure, the security application 3032 may include, for example, an application or applet that is necessary to execute in a security enhanced mode, such as TEE 3030. Further, the security application 3032 may include, for example, encryption related functions. For example, the security application 3032 may perform password generation, modification, or deletion functions related to payment.

According to various embodiments of the present disclosure, the REE3040 may include an application layer. For example, the REE3040 may include an application and/or a framework. Unlike TEE3030, REE3040 may allow access and/or control from the outside world. The REE3040 may include, for example, a payment application (e.g., wallet application) 3042 and/or a payment manager 3044. The payment application 3042 may, for example, perform interface, OCR, or recognized functions for payment using the payment application 3042. Further, the payment application 3042 may perform functions related to card registration or payment, for example.

The payment manager 3044 may include, for example, information related to a card company included in the REE3040, according to various embodiments of the present disclosure. The information related to the card company may include, for example, an application related to the card company and the application may be provided in a package form. The packet form may be provided as an SDK. The payment manager 3044 may include, for example, encryption-related functionality. For example, the payment manager 3044 may perform a token ID management or card company channel establishment function. Further, the payment manager 3044 may perform an interface with the external device 3020 (e.g., a server), for example. For example, the payment manager 3044 may provide an interface for the tokenization service with a server (e.g., the payment server 3050).

In accordance with various embodiments of the present disclosure, payment manager 3044 may be functionally connected to security application 3032, for example, such that payment manager 3044 may share information. For example, the payment manager 3044 may execute an interface with the security application 3032 in order to use (or store) a token or key. Further, the security application 3032 may include information related to a network service provider.

In accordance with various embodiments of the present disclosure, payment application 3042 and payment manager 3044 may be functionally connected to each other and security application 3032 and payment manager 3044 may be functionally connected to each other. For example, payment manager 3044 may deliver information received from the outside to payment application 3042 or security application 3032, or deliver information received from payment application 3042 or security application 3032 to the outside. According to embodiments of the present disclosure, payment manager 3044 may share payment-related information with security application 3032 or payment application 3042.

According to various embodiments of the present disclosure, the electronic device 3010 may include additional configurations or modules in addition to TEE3030, security applications 3032, REE3040, payment applications 3042, or payment manager 3044.

According to various embodiments of the present disclosure, the payment server 3050 may send payment-related information (e.g., tokens or keys) from the electronic device 3010 to a management server for electronic or mobile payment. Further, the payment service server 3052 and the token requestor server 3054 included in the payment server 3050 are functionally connected to each other such that they can share payment-related information.

According to various embodiments of the present disclosure, the token server 3060 is functionally connected to the token requestor server 3054 such that they may send/receive payment-related information. For example, the token requestor server 3054 and token server 3060 may provide interfaces for delivering tokens or keys.

Fig. 31 is a flow diagram of token payment, according to various embodiments of the present disclosure.

Referring to fig. 31, a payment system may include an electronic device 3110, a payment server 3170, a token server 3150, a POS3120, a financial server 3160, a transferee server 3130, or a payment network 3140, according to various embodiments of the present disclosure. The electronic device 3110 may include, for example, a payment application, a payment manager, or a secure area (e.g., a secure module or TEE). POS3120 may include, for example, a POS information management system. The POS3120 combines the functions of a cash register (cash register) and computer electronics, for example, and the user can perform a payment function using the POS 3120. Financial server 3160 may comprise, for example, the bank or financial company that issued the card and may perform identification decisions regarding the card. Further, during payment, approval regarding the card may be processed. Transferee server 3130 may comprise, for example, a bank or financial company that purchases credentials for card transactions made at a store (e.g., POS 3120). The payment network 3140 may include, for example, a card network.

According to various embodiments of the present disclosure, electronic device 3110 may deliver a token and/or encrypted information (e.g., a password) to POS 3120. The token may be stored, for example, in the electronic device 3110. Further, the token may be stored in an encrypted area (e.g., a security module or TEE). For example, the electronic device 3110 may generate the encryption information using a key received from the outside or a key generated from the electronic device 3110. The encryption information may include a password. Additionally, electronic device 3110 may deliver a password and/or token to POS 3120.

According to various embodiments of the present disclosure, electronic device 3110 may use various communication connections when delivering passwords and/or tokens to POS 3120. The communication connection may include, for example, NFC, MST, barcode, or Quick Response (QR) code.

According to various embodiments of the present disclosure, POS3120 may deliver at least one of a token, encryption information, and payment information to transferee server 3130. For example, POS3120 may deliver to transferee server 3130 a token and/or password received from electronic device 3110 and/or payment information (e.g., payment history) obtained from POS 3120. Further, the payment information may be obtained from POS3120 or received from an external device, for example, and may include a payment history for a user requesting a payment function. Further, the payment information may include, for example, a history of payments performed with the payment system.

According to various embodiments of the present disclosure, the transferee server 3130 may deliver at least one of the token, the encryption information, and the payment information to the payment network 3140. For example, transferee server 3130 may deliver at least one of the token, password, and payment information received from POS3120 to payment network 3140.

According to various embodiments of the present disclosure, the payment network 3140 may include a card company-related network. Card company may include, for example, VISA^TM、MasterCard^TMOr Amex^TM. According to embodiments of the present disclosure, payment network 3140 may include or operate token server 3150. For example, the payment network 3140 may deliver at least one of a token, password, and payment information from the payment network 3140 to the token server 3150, or may perform the functions of the token server 3150.

According to various embodiments of the present disclosure, token server 3150 may determine information about tokens received from payment network 3140. For example, token server 3150 may determine card information (e.g., a PAN) corresponding to the token using the token. For example, token server 3150 may determine a PAN corresponding to financial server 3160 using information (e.g., data) included in the token. Token server 3150 may, for example, determine a PAN corresponding to financial server 3160 and perform processing to receive payment authentication from financial server 3160 using the PAN. According to various embodiments of the present disclosure, token server 3150 may use a password in determining a PAN. According to an embodiment of the disclosure, token server 3150 may deliver the PAN to payment network 3140.

According to various embodiments of the present disclosure, payment network 3140 may deliver the PAN and payment information to financial server 3160. For example, the payment network 3140 may deliver PAN and/or payment information received from the transferee server 3130 to the financial server 3160. According to various embodiments of the present disclosure, the payment network 3140 may deliver approval to the payment network 3140.

According to various embodiments of the present disclosure, financial server 3160 may utilize PAN and/or payment information to determine payment approval. For example, financial server 3160 may perform payment approval when the PAN and/or payment information is the same as the information included in financial server 3160 (e.g., a valid PAN). For example, financial server 3160 may perform payment denial when the PAN and/or payment information is not the same as the information included in financial server 3160 (e.g., an invalid PAN). According to various embodiments of the present disclosure, financial server 3160 may deliver approval to payment network 3140. According to various embodiments of the present disclosure, the payment network 3140 may deliver approval to the payment network 3140.

According to various embodiments of the present disclosure, the financial server 3160 may deliver the approval to the transferee server 3130. According to various embodiments of the present disclosure, transferee server 3130 may send whether the acceptance was completed to POS 3120. According to various embodiments of the present disclosure, when approval is complete, payment network 3140 may deliver the payment information to token server 3150. According to various embodiments of the present disclosure, token server 3150 may deliver payment information to payment server 3170. According to various embodiments of the present disclosure, payment server 3170 may deliver payment information to electronic device 3110. For example, payment server 3170 may deliver payment information to electronic device 3110 using specified instructions (e.g., push messages).

According to various embodiments of the present disclosure, the electronic device 3110 may display payment information through the electronic device 3110. For example, the electronic device 3110 may display payment information using a payment application included in the electronic device 3110 or display payment information through a payment function-related interface. The payment function related interface may include a notification bar.

According to various embodiments of the present disclosure, the electronic device 3110 may display payment information or payment-related information (e.g., payment status, payment history, or accumulated amount) through a display functionally connected with the electronic device 3110. For example, the electronic device 3110 may utilize a notification module (e.g., the notification manager 2049 of fig. 20) of the electronic device 3110 to display payment information or payment-related information. Further, the electronic device 3110 may display the payment information or payment related information through at least one of a notification, an indicator, a status bar, a task bar, an icon, a floating icon, a tile (tile), and a widget, for example, and may display the payment information in at least a partial area of a home screen, a lock screen, or a curved display.

According to various embodiments of the present disclosure, the electronic device 3110 may output notifications related to payment information or payment related information through sound, vibration, or tactile effects using an audio module (e.g., audio module 1980 of fig. 19), a motor (e.g., motor 1998 of fig. 19), a haptic feedback device (not shown), and/or a friction display (not shown).

Fig. 32 illustrates operation of payment system components in accordance with various embodiments of the present disclosure.

Referring to fig. 32, a payment system may include an electronic device 3210, a payment server 3220, and/or a payment network 3230, according to various embodiments of the present disclosure. The electronic device 3210 may include, for example, a payment manager 3212. The payment server 3220 may include, for example, a payment service server 3222 and/or a token requestor server 3224. Payment network 3230 may include, for example, token server 3232. With respect to the payment system, the token may be for functions performed by each of the electronic device 3210, the payment server 3220, and/or the payment network 3230.

According to various embodiments of the present disclosure, the electronic device 3210 may provide token-related tokenization services using a payment manager 3212 in the electronic device 3210 and a token requestor server 3224 in the payment server 3220.

According to various embodiments of the present disclosure, the payment service server 3222 may provide token-related operation periods (e.g., token life management) using a token requestor server 3224 included in the payment server 3220.

According to various embodiments of the present disclosure, token server 3232 may provide token-related notification services using token requestor server 3224.

According to various embodiments of the present disclosure, the token requestor server 3224 may utilize a payment network solution to provide payment methods to the electronic device 3210. For example, token requestor server 3224 may utilize a tokenization service, a token-related operation period, and/or a token-related notification service to determine a payment method appropriate for the user.

33A, 33B, and 33C illustrate flow diagrams of token issuance operations for electronic devices, in accordance with various embodiments of the present disclosure.

According to various embodiments of the present disclosure, the token issuance operation may vary on a country basis. For example, the token issuance operation may be changed based on the united states, europe, or korea.

Referring to fig. 33A, a flow diagram 3300 of a first token issuance operation of an electronic device is illustrated in accordance with various embodiments of the present disclosure.

Referring to fig. 33A, the first token issuing operation may include, for example, the electronic device 3302, the payment server 3304, or the token server 3306. The electronic device 3302 may include, for example, at least one of a payment application, a payment manager, a security module, and a TEE.

According to various embodiments of the present disclosure, the electronic device 3302 may obtain card-related information through sensors that are functionally connected with the electronic device 3302. The card-related information may be used for card registration operations, for example. The sensor may comprise, for example, OCR. The card-related information may include at least one of a PAN, an expiration date, and a CVV, for example. The sensors may be executed, for example, using a payment application included in the electronic device 3302.

According to various embodiments of the present disclosure, a payment application included in the electronic device 3302 may deliver card-related information to the payment server 3304. The payment server 3304 may include, for example, a payment service server or a token requestor server, and the card-related information may be delivered between the payment service server and the token requestor server.

According to embodiments of the present disclosure, payment server 3304 (e.g., token requestor server) may deliver card-related information and/or information related to electronic device 3302 (e.g., device information or user information) to token server 3306. The information related to the electronic device 3302 may include, for example, a device requesting a first token issuance operation.

According to embodiments of the present disclosure, the token server 3306 may issue (or generate) a token based on information received from the payment server 3304. According to embodiments of the present disclosure, token server 3306 may deliver the token based on information received from payment server 3304. Token server 3306 may, for example, deliver the token to a token requestor server included in payment server 3304.

According to embodiments of the present disclosure, the payment server 3304 may deliver the token to the electronic device 3302. The payment server 3304 may, for example, deliver tokens to the electronic device 3302 from a token requestor server included in the payment server 3304.

According to embodiments of the present disclosure, the electronic device 3302 may store the token received from the payment server 3304 in a security module or TEE. For example, the electronic device 3302 may store the token in a security module or TEE, i.e., a secure area, so that the electronic device 3302 may control access from the outside world.

According to embodiments of the present disclosure, the electronic device 3302 may store the token received from the payment server 3304 in a general memory (e.g., a memory in the REE).

In accordance with embodiments of the present disclosure, with respect to tokens, at least one token may be issued (or generated) based on a payment method (e.g., OTP or call center) performed in the electronic device 3302.

With respect to tokens, according to embodiments of the present disclosure, one token may be issued (or generated) corresponding to the electronic device 3302. For example, a first token may be included in a first electronic device and a second token may be included in a second electronic device. The first and second tokens are different from each other.

According to embodiments of the present disclosure, the token may be activated based on an authentication operation (e.g., ID & V). For example, the token may be stored in the electronic device 3302 and may be activated based on an authentication operation. The authentication operation may include, for example, an identification decision. The identification decision may be performed, for example, by a financial server.

Referring to fig. 33B, a flowchart 3310 of a second token issuance operation of the electronic device is illustrated in accordance with various embodiments of the present disclosure.

Referring to fig. 33B, the second token issuance operation may include, for example, the electronic device 3312, the payment server 3314, or the token server 3316. The electronic device 3312 may include, for example, at least one of a payment application, a payment manager, and a security module. Further, the payment server 3314 may include, for example, a security services management server.

According to various embodiments of the present disclosure, an electronic device or another electronic device may obtain card-related information through a sensor functionally connected with the electronic device or another electronic device. The card-related information may be used for card registration operations, for example. The sensor may comprise, for example, OCR. The card-related information may include at least one of a PAN, an expiration date, and a CVV, for example. The sensor may be executed, for example, using a payment application included in the electronic device or the other electronic device.

According to various embodiments of the present disclosure, a payment application included in the electronic device 3312 may deliver card-related information to the payment server 3314. The payment server 3314 may comprise, for example, a payment service server or a token requestor server, and the card-related information may be delivered between the payment service server and the token requestor server.

According to an embodiment of the present disclosure, the payment server 3314 may deliver the card-related information to a security service management server in the payment server 3314. The security service management server may be included in the payment server 3314 and operate internally, or may be included externally to the payment server 3314, for example. For example, the security service management server may be included in a device (e.g., an external device) different from the payment server 3314 and may be functionally connected to the payment server 3314 and exchange card-related information.

According to an embodiment of the present disclosure, the security service management server may deliver card-related information and/or information related to the electronic device 3312 (e.g., device information or user information) to the token server 3316. The information related to the electronic device 3312 may include, for example, a device requesting a second token issuance operation.

According to an embodiment of the present disclosure, the token server 3316 may perform an authentication operation based on information received from the payment server 3314. The token server 3316 may, for example, perform authentication operations based on card-related information and/or information related to the electronic device 3312.

According to an embodiment of the present disclosure, the token server 3316 may deliver a result (e.g., success or failure) regarding the authentication operation to a security service management server included in the payment server 3314.

According to an embodiment of the present disclosure, the security service management server may issue (or generate) a token based on the card-related information and/or the information related to the electronic device 3312.

According to an embodiment of the present disclosure, the security service management server may store the token in a security area (e.g., a security module) included in the electronic device 3312. For example, the security service management server may have access permissions (e.g., security module access permissions) to secure areas of the electronic device 3312. Further, the security service management server may store the token in a secure area of the electronic device 3312 using the access permission. Further, the token may be delivered from the security service management server to the electronic device 3312.

According to an embodiment of the present disclosure, the electronic device 3312 may store the token in a security module, i.e., a security area, and may control access from the outside.

In accordance with embodiments of the present disclosure, with respect to tokens, at least one token may be issued (or generated) based on a payment method (e.g., OTP or call center) performed in the electronic device 3312.

With respect to tokens, a token may be issued (or generated) corresponding to the electronic device 3312, in accordance with embodiments of the present disclosure. For example, a first token may be included in a first electronic device and a second token may be included in a second electronic device. The first and second tokens are different from each other.

According to embodiments of the present disclosure, the token may be activated based on an authentication operation (e.g., ID & V). For example, the token may be stored in the electronic device 3312 and may be activated based on an authentication operation. The authentication operation may include, for example, an identification decision. The identification decision may be performed, for example, by a financial server.

Referring to fig. 33C, a flow diagram 3320 of a third token issuance operation for an electronic device is illustrated in accordance with various embodiments of the present disclosure.

Referring to fig. 33C, the third token issuing operation may include, for example, the electronic device 3322, the payment server 3324, or the token server 3326. The electronic device 3322 may include, for example, at least one of a payment application, a payment manager, a security module, and a TEE.

According to an embodiment of the present disclosure, the electronic device or the another electronic device may perform an authentication operation (e.g., ID & V). Authentication operations, such as identification determinations, may be performed using a payment application.

According to embodiments of the present disclosure, the electronic device 3322 may perform card registration and/or identification determinations while performing payment functions. For example, to perform the payment function, the electronic device 3322 may perform card registration and identification determination, and card registration and identification determination may also refer to a standby (or ready) state of the payment function.

According to embodiments of the present disclosure, the electronic device 3322, the payment server 3324, or the token server 3326 may share information related to card registration and identification decisions. For example, the electronic device 3322, the payment server 3324, or the token server 3326 may share at least one of a PAN, an expiration date, a CVV, device information, and user information.

According to an embodiment of the present disclosure, the token related to the third token issuance operation may be issued (or generated) during payment using a payment function.

According to various embodiments of the present disclosure, a payment application included in the electronic device 3322 may perform user authentication in order to perform payment functions. For example, the user authentication may include a password, pattern authentication, or biometric information authentication.

According to an embodiment of the present disclosure, when the user authentication is successful (e.g., the authentication is completed), the payment application may perform a third token issuance operation through the payment server 3324. The third token issuance operation may comprise, for example, a token request.

In accordance with embodiments of the present disclosure, the payment server 3324 may deliver card information (e.g., a card identifier) and/or user information to the token server 3326 based on the token request. The information related to the electronic device 3322 may include, for example, a device requesting a third token issuance operation.

According to embodiments of the present disclosure, the token server 3326 may issue (or generate) a token based on information received from the payment server 3324.

According to embodiments of the present disclosure, the token server 3326 may deliver the token based on information received from the payment server 3324.

According to embodiments of the present disclosure, the payment server 3324 may deliver the token to the electronic device 3322.

According to embodiments of the present disclosure, the electronic device 3322 may store the token received from the payment server 3324 in a security module or TEE. For example, the electronic device 3322 may store the token in a security module or TEE, i.e., a secure area, so that the token may control access from the outside world.

According to embodiments of the present disclosure, the electronic device 3322 may store the token received from the payment server 3324 in a general memory (e.g., a memory in the REE).

According to an embodiment of the present disclosure, the electronic device 3322 may not store the token received from the payment server 3324 in a storage area (e.g., memory) in the electronic device 3322. For example, the electronic device 3322 may not store the token in the storage area and may use the token for payment functions.

In accordance with embodiments of the present disclosure, with respect to the token, the storage area of the token may change based on a payment method (e.g., OTP or call center) performed in the electronic device 3322. For example, when the payment method is OTP, the token may be stored in the security module or TEE, and when the payment method is call center, the token may not be stored in the electronic device 3322.

According to various embodiments of the present disclosure, the token may include a use time or an expiration time. For example, the use of the token may be restricted when a specified time (e.g., 3 hours or a day) elapses after the token is issued (or generated).

According to various embodiments of the present disclosure, the token may include card information. For example, the token may include onetime card (OTC) information.

According to various embodiments of the present disclosure, an electronic device may include a sensor configured to detect a position state or an orientation state thereof, a memory configured to store a payment application, and a processor functionally connected to the sensor and the memory. The processor may be configured to detect an orientation of the electronic device using the sensor when execution of the payment application is requested, generate and output a display object indicating that the orientation of the electronic device is in a specified orientation, or read a display object corresponding to the specified orientation from the memory and output the read object.

When the payment application is terminated or an error occurs, the processor may be configured to stop the display object output and output a message corresponding to the termination or the error of the payment application.

When an event related to payment completion is received, the processor may be configured to stop the display object output, or replace the display object with a payment completion related message and display the message.

After the payment application is executed, the processor may be configured to output the display object when a first gesture event (e.g., a gesture event corresponding to an operation of moving the electronic device to the POS) is detected to occur in which an object is approaching or designated.

The processor may be configured to stop the display object output when the electronic device is away from the detected object, the designated pattern image disappears longer than a designated time, or a designated second gesture event (e.g., a gesture event corresponding to an operation of withdrawing the electronic device from the POS) occurs.

The processor may be arranged to output a magnetic signal relating to the progress of payment for at least a part of the output period of the display object, and to stop the magnetic signal output when the display object output stops.

The processor may be configured to stop the display object output when a specified SMS indicating completion of payment is received or a specified message (e.g., a message received over a data network or a cellular network) is received from the server.

After displaying the object output, the processor may be configured to stop displaying the object output when the electronic device has the specified orientation state.

The processor may output audio data corresponding to the display object.

The processor may control the lighting of a lamp arranged at the camera corresponding to the direction to be taken by the electronic device.

According to various embodiments of the present disclosure, an electronic device may include a memory configured to store an object for indicating an orientation of the electronic device and a processor functionally connected with the memory. The processor may be arranged to detect an orientation of the electronic device using the sensor when execution of the payment application is requested, and to output an object indicating that the orientation of the electronic device is in a specified orientation.

According to various embodiments of the present disclosure, an electronic device may include a memory configured to store payment related information of the electronic device and a processor functionally connected with the memory. The processor may be configured to determine an integrity of the payment-related information, determine an integrity of a component of the device for processing the payment-related information, and determine whether to output the payment-related information to the seat selection magnetic signal based on the determination.

When the integrity is compromised, the processor may be arranged to output a message according to the compromised integrity and stop payment progress.

When the integrity is compromised, the processor may be configured to output a message requesting an update of the payment-related information.

When the integrity is compromised, the processor may be configured to automatically send information regarding the compromised integrity to a designated server.

According to various embodiments of the present disclosure, an electronic device may include a memory configured to store payment related information of the electronic device and a processor functionally connected with the memory. The processor may be arranged to output a plurality of images relating to the card for payment, to display one of the plurality of images relatively larger than the other images, and to display the remaining images in the same size and without overlapping them with the relatively larger displayed image.

The processor may be configured to display card images having a frequency of use greater than a certain value so as not to overlap with each other, and to display card images having a relatively higher frequency of use to be larger.

The processor may be configured to display card images having usage histories greater than a certain value so as not to overlap with each other, and to display card images having relatively recent usage card histories larger.

The processor may be configured to display the card images having a usage frequency or usage history greater than a certain value so as not to overlap each other, display the specified card images in a fixed size, and display the remaining card images in different sizes in order of a relatively high usage frequency or recent usage history.

As described above, various embodiments may more conveniently and easily support payment processing by operating a multi-payment method regardless of characteristics of a payment request device.

A module or programming module according to various embodiments of the present disclosure may include at least one of the above components, may not include some of the above components, or may further include additional components. Operations performed by a module, programmed module, or other component according to various embodiments of the disclosure may be performed in a sequential, parallel, iterative, or heuristic manner. Further, some operations may be performed in a different order or may be omitted. Alternatively, other operations may be added.

While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.

Claims

1. An electronic device, comprising:

a secure memory configured to store predetermined fingerprint information;

a display; and

a processor functionally connected with the secure memory and the display and configured to:

acquiring fingerprint information;

comparing the fingerprint information with the predetermined fingerprint information;

when the fingerprint information is valid, controlling a multi-payment operation including a payment operation associated with a Near Field Communication (NFC) method and a payment operation associated with a Magnetically Secure Transmit (MST) method;

the signal processing information operating according to the NFC method and the signal processing information operating according to the MST method are displayed on one screen interface while the NFC method operation and the MST method operation are alternately operated.

2. The electronic device of claim 1, wherein the processor is further configured to display at least one of: an object for indicating a signaling start guidance for payment processing, an object associated with a signaling direction operating according to the NFC method, or an object associated with a signaling direction operating according to the MST method.

3. The electronic device of claim 2, wherein the processor is further configured to:

an object associated with a signaling direction of a payment operation according to the NFC method and an object associated with a signaling direction of a payment operation according to the MST method are differently displayed.

4. The electronic device of claim 1, wherein the processor is further configured to determine, by the sensor, whether the proximity of the specified object is within a specified distance during operation of the NFC method, and

transmitting an MST signal according to the MST method operation when the object is within the specified distance.

5. The electronic device of claim 1, wherein the processor is further configured to:

activating the camera during said multi-payment operation, an

The barcode object is automatically displayed when an image is captured that includes an object associated with barcode recognition.

6. The electronic device of claim 5,

the processor is further configured to:

determining whether a distance between an object and the camera is greater than a certain distance, or whether the object disappears from the image, and

when the object distance is greater than a specific distance, or when the object disappears from the image, it is determined that the payment completion of the multi-payment method has occurred.

7. The electronic device of claim 1, wherein the processor is further configured to display on the screen interface at least one of:

a handover function object for supporting maintenance of a display state of at least a part of the objects included in the current screen interface and prohibiting switching to another function or switching to a barcode method,

an object including operation guidance information related to payment execution,

signature objects associated with the signature input, or

And a bar code method switching object for outputting the bar code.

8. The electronic device of claim 7, wherein the processor is further configured to control a screen interface including at least one of a barcode object or an object for switching to multiple payment operation screens according to a barcode method switch object selection.

9. The electronic device of claim 8, wherein the processor is further configured to output fingerprint detection guidance information related to handover function release during handover function execution according to handover function object selection.

10. The electronic device of claim 1, wherein the processor is further configured to activate the camera and execute a handover function for maintaining a display state of at least a portion of the object included in the current screen interface and inhibiting switching to another function when the designated user face is not recognized.

11. A method of processing payment at an electronic device, the method comprising:

acquiring fingerprint information;

comparing the fingerprint information with predetermined fingerprint information; and

controlling a multi-payment operation including a payment operation associated with a near field communication, NFC, method and a payment operation associated with a magnetically secure transmit, MST, method when the fingerprint information is valid,

12. The method of claim 11, further comprising displaying a signal transmission object for indicating a signal transmission direction operating according to the NFC method or a signal transmission object for indicating a signal transmission direction operating according to the MST method.

13. The method of claim 12, further comprising:

displaying signaling objects associated with payment of the NFC method differently during payment of the NFC method operation and displaying signaling objects associated with payment of the MST method during payment of the MST method operation.

14. The method of claim 11, further comprising:

determining, by a sensor, whether proximity of a specified object is located within a specified distance during a payment operation of the NFC method; and

15. The method of claim 11, further comprising:

activating the camera; and

16. The method of claim 15, further comprising determining whether a distance between an object and the camera is greater than a certain distance, or whether an object disappears from an image, and

17. The method of claim 11, further comprising at least one of:

displaying a handover function object for supporting maintaining a display state of at least a part of objects included in a current screen interface and prohibiting switching to another function or switching to a barcode method;

displaying an object including operation guidance information related to payment execution;

displaying a signature object associated with the signature input; or

And displaying a bar code method switching object for outputting the bar code.

18. The method of claim 17, further comprising displaying a screen interface including at least one of a barcode object or an object for switching to a multi-payment operation screen according to a barcode method switch object selection.

19. The method of claim 17, further comprising outputting fingerprint detection guidance information related to handover function release during execution of the handover function according to the handover function object selection.

20. The method of claim 11, further comprising:

activating the camera; and

a handover function for maintaining a display state of at least a part of the object included in the current screen interface and prohibiting switching to another function is performed when the designated user face is not recognized.